adding FDS and more characteristicscauses the dfu service to crash

RE: adding FDS and more characteristicscauses the dfu service to crash

paul — Fri, 17 May 2019 01:24:37 GMT

Looks like I had some issues with the code to add characteristics and then update the values. It is working now

thanks

Paul

RE: adding FDS and more characteristicscauses the dfu service to crash

paul — Thu, 16 May 2019 21:28:03 GMT

Thanks Edvin,

Our client to this device is currently on IOS. Apple work very hard to avoid giving you useful information on that stack eg the Mac address. I am trying to add hardware revision and firmware revision so that the client can be sure that the firmware update matches the device. To do this I was going to add some characteristics that held that information.

I have added DEBUG to the preprocessor defines . There is no error message.

<debug> app: In nrf_bootloader_init
<debug> nrf_dfu_settings: Calling nrf_dfu_settings_init()...
<debug> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend.
<debug> app: Enter nrf_bootloader_fw_activate
<info> app: No firmware to activate.
<debug> app: Enter nrf_dfu_app_is_valid
<debug> app: Return true. App was valid
<debug> app: DFU mode requested via GPREGRET.
<info> nrf_bootloader_wdt: WDT is not enabled
<debug> app: in weak nrf_dfu_init_user
<info> app_timer: RTC: initialized.

Cheers Paul

RE: adding FDS and more characteristicscauses the dfu service to crash

Edvin — Thu, 16 May 2019 10:49:22 GMT

[quote user=""]The error is cause by the on_error handler in main.[/quote]

The error is picked up by the error handler.

Are you sure that you want to add more things to the bootloader project, which is what it is looking like you are doing. The bootloader is usually the part that is only responsible for the update of the application. The application itself should only trigger the nRF to enter DFU mode (the bootloader).

You shouldn't have to add characteristics to the bootloader. However, if you do need to add something, you should use the error handler to figure out where the issue comes from. Define "DEBUG" in your preprocessor defines, and watch the log. Does it say where the APP_ERROR_CHECK(err_code) with an err_code != 0 comes from?

Best Regards,

Edvin