Flashing Eddystone Firmware on Custom Board

[Rishabh Agnihotri]

Hello Folks,

Nice to see an active developer community out here! I ran into some issues last night which I hope could be resolved. We procured nRF52840 SoCs and have developed a low-cost custom board recently. As its a very initial prototype we don't have any LEDs or a USB port on the board, and only four connectors that are SWDCLK, SWDIO, GND and VTG. Now we made the right connections for flashing the firmware on custom board using the nRF52840 PDK and we were able to see the board using this command:

nrfjprog --memrd 0x1000005c --n 12

And the result was we were getting different identifiers so yes the custom board was connected. I am trying to flash multiprotocol Eddystone firmware which is available in Thread SDK 10.0.0. The flashing is pretty much successful as there are no errors, but we aren't unable to see any Bluetooth advertisement pop-up. I have also tried a different firmware like blinky. We also read that we can disable log_init functions to solve this problem and tried that too but nothing seems to work. Can anyone help us out here, please?

[Hung Bui]

My suggestion is that you test with simple example first. For example ble_app_hrs example. Make sure you flash the softdevice before you flash the example (or you can flash the pre-compiled hex which includes the softdevice already).

You may have to modify the source code if you don't have the 32kHz crystal on your custom board.

Did the blinky example work for you ?