• State Verified Answer
  • Replies 2 replies
  • Subscribers 87 subscribers
  • Views 667 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 271503
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Porting a Segger BLE SoftDevice project from nRF52840 DK to nRF52840 Dongle works but no LED

brianreinhold

I have a working code using SoftDevice 140 7.2.0 and Segger ES on the nRF52840 DK. I made the single adjustment of the preprocessor variable BOARD_PCA10056 to BOARD_PCA10059 as indicated by the tutorial. I used the nRFConnectProgrammer to flash the dongle. I must admit it is very confusing as when one follows the instructions one gets all kinds of error messages in the log which looks like it failed. If you don't do anything after pressing the reset and doing the flash write, the dongle appears dead. THe log says to hit the reset so I do. Then the red led flashes again. Not what I expected. In any case, if I pull the dongle and re-insert it, there is no LED lit at all. The dongle looks dead. However, it turns out that it is working.

Previously I had a version of SoftDevice and the pc-ble-driver installed on the dongle, and when I plugged it in the green LED lit. With my program flashed on the dongle, there is no green LED even though it is working (it is sending advertisements). That is bad for the user. Why is that? What did I NOT do? I expected the green LED to light when the program was flashed as with the pc-ble-driver. Alas, not so.

  • +1

    Hi

    What kinds of error messages are you referring to? The nRFConnect programmer will give some errors when the DFU is disabled and the application is running, as it will no longer be able to communicate with the PC when the USB DFU firmware is no longer running, so that part is expected behavior.

    The green LED you're not seeing is likely because the application you're now running is not turning this LED on. This is not an indicator that an application is running, but will only be on if your application says so.

    Best regards,

    Simon

  • 0 in reply to Simonr

    I figured that out. It just must of been the case the pc-ble-driver turned on the LED. I thought it was a power on LED.. What was confusing me were the error messages in the nRFConnect app and the fact it told me to press the reset button (which I did). If this is always the case, it would be very helpful to say in the log 'programming successful DFU now disabled". instead of all these error messages? 

Related
Terms of service