ble_app_uart won't advertise as coded from example set

[Alexandre Tessier]

Hello, I am currently trying to program the uart example code from the nRF5_SDK_12.3.0_d7731ad zip file. After dealing with various reference address and device package issues, I am now able to flash the softdevice and progam sets to the chip. However, the chip is not advertising and it does work with the premade hex file. At this point I have no idea what could be wrong, the only noticible difference between the hex file layout in nRF Connect and the flashed softdevice and code from Kiel 5 is shown in the attached image, with hex file on the left covers the register address from 0 to 0x0001E3F7 while the flashed program from Keil goes from 0 to 0x0001E3FF. Other than that the recovery error is shown in the command window, but this occured even for the hex file which would advertise so I am unsure how to proceed.

[Simonr]

Hi

No, an analog signal from positive to negative bias should not crash an nRF5x DK, so that should not be it. Let me know how it goes with this new computer. Did you not have any luck debugging on your end?

Best regards,

Simon

[Alexandre Tessier]

Hello Simon,

Still no luck, however I have started up the process on the lab computer and an potentially intersting development has arose. Following the setup instructions, I used the perliphery example Blinky hex file blinky_pca10028.hex. This worked as intended with the cycling of the four LEDs. However, I then changed the file to blinky_pca10028_s130.hex to include the Softdevice. This caused the LED's to stop working. Is this a different program similar to the experimental_ble_app_blinky_pca10028_s130.hex or should it still run like the previous hex file?

Sincerely,

Alexandre Tessier