Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs

ble_app_uart won't advertise as coded from example set

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.

Parents
  • Hi Alexandre

    I don't think the 2V signal should have anything to say here. If the application flashes successfully I think you need to debug what is going wrong when the application is running. I also see that you have tagged this ticket with "Bluetooth 5", which the nRF51 series does not support. So if you have added any features that aren't supported by the nRF51, that might be why you're having issues.

    Best regards,

    Simon

Reply
  • Hi Alexandre

    I don't think the 2V signal should have anything to say here. If the application flashes successfully I think you need to debug what is going wrong when the application is running. I also see that you have tagged this ticket with "Bluetooth 5", which the nRF51 series does not support. So if you have added any features that aren't supported by the nRF51, that might be why you're having issues.

    Best regards,

    Simon

Children
Related