• State Suggested Answer
  • Replies 31 replies
  • Answers 1 answer
  • Subscribers 75 subscribers
  • Views 9157 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 208097
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

flashing problem with some nrf52832 shields using the DK-nrf52

PhilippeG

Hello

i just bought my DK-nrf52 to move to BLE after playing few months with arduino. I have connected various nrf52832 shields from China (from Holyiot 17095, which is very small). 

after learning the basics from Keil and your board. i finally compile and flashed correctly the blinky example using the s132. 

first i have to report this has been a very long time consuming because i might not have found the community to help for that. is there any links that you might share from people doing simple tutorials? the one i have seen from you are very generic and doesnt go far enough for beginers like me. 

saying so. i do have problem flashing more complexe example on my nrf52832, for instance the proximity_ble example compiles and is flashed on the device without any error on Keil. but no phone can detect this device? 

i have also noticed, that sometimes, flashing from Keil is mentionning that the content is flashed successfully as well as the program is running, while (either on the DKnr52 board or the external devices, the former program is still running. 

Sorry for asking all my questions in the same message. but i try to move fast because i noticed that the nrf52832 seems having a low distance of fonctionning (few meters) the proximity app on my phone is mentionning that the signal is lost after few meters. Is that normal? if so, i might have to come back to my arduino and HC06 Bluetooth. I hope i misunderstood something about that. 

thanks a lot

Philoppe

Parents
  • 0

    there are other blog post links bellow that helps to make it easier to write BLE firmware.

    Eclipse GCC environment development for nRF51 & nRF52 series. Eclipse is totally free without restrictions. 

    BLE programming the easy way.  Many example code to write BLE firmware with Eclipse as easy as Arduino

  • 0 in reply to Nguyen Hoan Hoang

    Oh thanks a lot.. i will look at that. Is Eclipse free? because Keil is extremely expensive for what i need to do.

  • 0 in reply to Martin Lesund

    Hi Martin, thanks a lot for this detailed answer. Sorry for my late response. I have bought a nrf52 DK it works perfectly with the chip on board. but there are some issues with the Holyiot 17095 . it flashes it ok, the blinky or any simple peripheral programms are working great on it. but no ble examples works. the devices is shown as a proximity, blinky ble etc... but my phone cannot connect to the Holyiot. 

    Thanks for the uart, this is exactly what i would need but working on an external module flashed with my nrf52 DK. any ideas of incompatibilities with some modules (since you mentionned holyiot in yout list of provider of nrf52832 modules?)

    Ok thanks for you warning regarding the sdk v10, i am using the v15. 

    the purpose of the module is to controle a small motor with various speed using an app in ble on my phone. 

    the next step is to programm an app that can controle a ble module. what would be your best suggestion for me to start programming such an app (IOS and Android)

    thanks a lot

  • 0 in reply to Martin Lesund

    Dear Martin

    I compiled and flashed ble_app_uart on the DK-nrf52 but i cannot connect using any terminal. i am using the "bluetooth terminal" for Android. i am using a Huawei Y7. What UART terminal would you advise me to use. I am getting really lost with so many troubles just to use your examples. 

  • 0 in reply to PhilippeG

    Hi Philippe,

    Please use the app referred to in the example documentation.

    On the Android side you can either use "nRF Connect" or "nRF Toolbox".

    On the PC side you can use your prefered serial terminal. (I like to use "termite")

  • 0 in reply to Martin Lesund

    Hi Martin, this is the kind of information that are very helpful for a beginner. thanks. I use termite and configure as mentionned on the example documentation. i connected with nRF Connect or nRF Toolbox on my android phone.  It connects perfectly. I have differencies with the documentation though. if write 30 31 32 33 ... either in nRF Connect or nRF Toolbox, i see the same text appearing in Termite (running on my PC). it is said i should read 123 ... 

    Then, the text i wrote into termite never appeared on my nRFconnect or nRF Toolbox. is there a specific set up to get the communication bi-directional? thank you

    One more question: (on the top of  all above working perfectly: bi-directional text), the only thing i would need to do is a similar app to the nRF UARTv2.0 for Android and IOS.. Does it exist a documentation on this app? What IDE is used to write such an app? is there  a source code somewhere or information?

    Sorry for so many questions. I wish there was low level video tutorial for people like me. ;-(

  • 0 in reply to PhilippeG

    Hi Philippe,

    Your experience is expected. The nRF Connect app has been updated after the "testing" text in the documentation. 

    Before you could send hex, but now if you send "01234" you would get "01234" on the other side. So the documentation is outdated.

    If you swipe right, you should get up the "terminal" log window in 'nrf Connect' app, so you can see what you send from your computer to the device.

    (so it works both ways)

    similar to this:

    For your last question:

    You have the UART app in the nRF Toolbox app which you can use instead of the deprecated "nRF UARTv2.0".

    The source code and documentation can be found here:

Reply
  • 0 in reply to PhilippeG

    Hi Philippe,

    Your experience is expected. The nRF Connect app has been updated after the "testing" text in the documentation. 

    Before you could send hex, but now if you send "01234" you would get "01234" on the other side. So the documentation is outdated.

    If you swipe right, you should get up the "terminal" log window in 'nrf Connect' app, so you can see what you send from your computer to the device.

    (so it works both ways)

    similar to this:

    For your last question:

    You have the UART app in the nRF Toolbox app which you can use instead of the deprecated "nRF UARTv2.0".

    The source code and documentation can be found here:

Children
Related
Terms of service