This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

BLE Thread Multiprotocol Example for nRF52840 Dongle

Hello,

I am trying to run the BLE Thread Dynamic Template example on a nRF52840 dongle. I'm using Segger Embedded Studio to generate an hex file. I flash the hex file to the Dongle using nRF Connect, along the softdevice s140 (the one required for this example).

The only thing I changed in the project is the macro BOARD_PCA10056 that I replaced with the macro BOARD_PCA10059 to match the dongle board.

A couple notes:

    1. The BLE Thread Switched Template example is working fine on the dongle after I apply the new macro

    2. The dynamic example works fine on a dongle if I flash the firmware with a J-link.

    3. The dynamic example does not reach while(true) if I call any ot function (as otInstanceInitSingle).

Please help! Thanks!

Parents
  • Hello,

     

      2. The dynamic example works fine on a dongle if I flash the firmware with a J-link.

    Does this mean that you have a JLink connection on the dongle that you try to flash over nRF Connect? Does that mean that you have the possibility to debug this dongle? If so, can you see whether it reaches main() at all?

  • When I program or debug the dongle connected to the J-link everything works fine. The problem described at point (3) happens if I program a dongle which does not have a connection to J-link: in this case I press the dongle reset button to enter the bootlaoder mode and I use nRF Connect to flash the s140 softdevice along the hex file of my project.

  • It is difficult to debug on the dongle without a debugger attached. Have you tried to upload using nRF Connect and debug with a JLink after that to see whether the main() is reached?

    Alternatively, can you attach some UART pins to monitor the LOG?

    If that is not possible either, try to see if you can set an LED at certain points in the application, to see whether they are reached.

Reply
  • It is difficult to debug on the dongle without a debugger attached. Have you tried to upload using nRF Connect and debug with a JLink after that to see whether the main() is reached?

    Alternatively, can you attach some UART pins to monitor the LOG?

    If that is not possible either, try to see if you can set an LED at certain points in the application, to see whether they are reached.

Children
Related