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 again

I have discussed this issue with my colleagues and we're not sure what could cause this.

I think you will have to debug this on your end since we're able to run the ble_app_uart project on our end programmed with Keil. Make sure that logging is enabled in the sdk_config.h header file so you're sure you can see the debug log either over UART or RTT. There must be a crash somewhere before the advertising starts since you're not able to see it sniffing when flashing it. As far as I can see both build and flash logs are correct in your latest attempt.

You can also try flashing the SoftDevice before the application if you haven't although I don't think the order should affect the application.

Best regards,

Simon

[Alexandre Tessier]

Hello Simonr,

Still working on it, will try a different computer to see if that helps. In passing, if I pass an anolog signal with a positive to negative bias, has that been known to cause the system to crash?

Sincerely,

Alexandre Tessier