Different motherboard burning appear differences

[kenyon]

hi.

SDK:17.1.0
CHIP:nrf52810.
application: ble_app_uart (Added buttonless dfu service and successfully upgraded OTA)
bootloader: secure bootloader ble


#APP_ADV_DURATION changed  0.
init.advdata.flags              = BLE_GAP_ADV_FLAGS_LE_ONLY_GENERAL_DISC_MODE;

when I debug. Found that the program does not seem to run into the mainloop, and the running effect does look like the above, here's why. What do I need to do to get him to run into mainloop and execute nus_data_handler_real()?



I look forward to your answers. Thank you very much!

[Hung Bui]

Hi Zicongkuang, 

Please do a test without the bootloader programmed. 
It could be that the bootloader didn't jump to the application. 

If you have flashed the bootloader, any change to the application need to be done via DFU update. 

If you are doing development, and don't want to do DFU update for any change you make to the application, you would need to disable CRC checking in the bootloader or not to flash the bootloader at all. 

Note that if you change the start address of the bootloader (or change from debug bootloader to release bootloader) you would need to do a full flash erase (eraseall)

[kenyon]

hi hung bui, the problem I'm having is that the mainloop of the application is not running in, but the Bluetooth of the application is running. So he didn't run through all the initialization and he didn't go into the for loop, because the bootloader didn't bootload?

best regard!

[Hung Bui]

 Hi Zicongkuang, 

Could you tell a little bit more about how you find out "Bluetooth of the application is running" ? I assume you find that the device advertise ? Which device name do you find when you scan for it , is it DFUTarg ? 

[kenyon]

hi hung bui. I can find ble_app_uart's Bluetooth and connect and send instructions with no problem. But I'm going to do the flashing light processing in the for loop. It's not going to work.

[Hung Bui]

Hi, 

I would suggest to test without bootloader. Most likely it's not the bootloader issue. But we need to separate it to make sure. 

Please put a breakpoint right before the main loop to see if it can reach those locations. I suspect that it may stuck in other loops and couldn't reach the main loop. You can try to disable some functionalities to see if they were the culprit. Disable them  one by one until you see that the LED starts blinking.