S112 crash at address 0x18808

RE: S112 crash at address 0x18808

Hung Bui — Wed, 18 Aug 2021 10:07:45 GMT

You can use the RTT Viewer application to see the log without having to "attach to debugger" in SES.

RE: S112 Fix at address 0x18808

Gaétan — Wed, 18 Aug 2021 10:04:27 GMT

[quote userid="2121" url="~/f/nordic-q-a/77657/s112-fix-at-address-0x18808/325420#325420"]When you are running in debug mode did you stop at any breakpoint and then continue ? [/quote]

Never. But I download firmware in flash memory. and after I use "attach to debbuger" menu for connect Jlink RTT to debug terminal in SES.

I continue to investigate... and send feedback.

RE: S112 Fix at address 0x18808

Hung Bui — Wed, 18 Aug 2021 08:14:05 GMT

Hi Gaetan,
When you are running in debug mode did you stop at any breakpoint and then continue ?

Have you built your application so that it's friendly for debugging ? (build with no optimization )
The app_error_fault_handler() only handle assertion that thrown by the softdevice or the SDK, not the hardfault. It's not possible to return to the application from the softdevice when you have a hardfault.

Please try to narrow down the issue by comparing to our DFU Buttonless example. Please try to test if you can reproduce the issue with the example.

RE: S112 Fix at address 0x18808

Gaétan — Wed, 18 Aug 2021 07:27:50 GMT

Hi,
I'm back from holiday...

I have make some tests with

[quote userid="2745" url="~/f/nordic-q-a/77657/s112-fix-at-address-0x18808/321529#321529"]Firmware: BL+Settings+App+SD.zip[/quote]

and the crash occur only if SES is in debug mode !

Thanks for confirmation:

[quote userid="2121" url="~/f/nordic-q-a/77657/s112-fix-at-address-0x18808/321499#321499"]The error at 0x18808 and 0x188D4 pointing us to the hardfault handler in the softdevices. [/quote]

Please can you explain why softdevice don't fire the function app_error_fault_handler() when hard fault is catched ?

Thanks

RE: S112 Fix at address 0x18808

Hung Bui — Fri, 23 Jul 2021 13:44:44 GMT

Hi Gaetan,

I have just tested your BL+Settings+App+SD.hex file on my nRF52810 dev kit and it worked fine.
You can see the screen recording here:

devzone.nordicsemi.com/.../20210723_5F00_154105.mp4

This is quite strange. Do you have any other hardware board to test ?
Could you record the screen when you test ? What exactly you meant by "connecting to NUS"
If you test with the buttonless example (no NUS) do you have any trouble ?

RE: S112 Fix at address 0x18808

Gaétan — Fri, 23 Jul 2021 09:49:24 GMT

[quote userid="2121" url="~/f/nordic-q-a/77657/s112-fix-at-address-0x18808/321499#321499"]I know that it's the same with or without the bootloader. But from what I can see even with the bootloader installed you still receive "error : No bootloader was found" , is this correct ? [/quote]

No, when I have bootaloder, I don't have the message "error : No bootloader was found". All is ok with bootloader.

[quote userid="2121" url="~/f/nordic-q-a/77657/s112-fix-at-address-0x18808/321499#321499"]Please confirm if you test the NUS example without the DFU buttonless service implemented you don't have any issue. [/quote]

I confirm, all is ok with NUS example.

[quote userid="2121" url="~/f/nordic-q-a/77657/s112-fix-at-address-0x18808/321499#321499"]If you don't flash the application did the softdevice + bootloader works (can do DFU ) ?[/quote]

I all is OK

[quote userid="2745" url="~/f/nordic-q-a/77657/s112-fix-at-address-0x18808/321083#321083"]Firmware: BL+Settings+App+SD.zip[/quote]

Here this Bootloader + Application + Sodtdevice with services (NUS +DFU) If you connect to NUS -> crash in softdevice

I send all source file in private message...

RE: S112 Fix at address 0x18808

Hung Bui — Fri, 23 Jul 2021 08:03:40 GMT

Hi Gaetan,

The error at 0x18808 and 0x188D4 pointing us to the hardfault handler in the softdevices.

I know that it's the same with or without the bootloader. But from what I can see even with the bootloader installed you still receive "error : No bootloader was found" , is this correct ?

Please confirm if you test the NUS example without the DFU buttonless service implemented you don't have any issue.

If you don't flash the application did the softdevice + bootloader works (can do DFU ) ?

If it's the case, please send us your bootloader project file so we can compile here, as well as the NUS + DFU buttonless project.

RE: S112 Fix at address 0x18808

Gaétan — Thu, 22 Jul 2021 16:28:04 GMT

The issue is the same with the bootloader installed or not.

Please look my code. APP_ERROR_CHECK is comment for my dev in DEBUG...

    // Initialize the async SVCI interface to bootloader.
    err_code = ble_dfu_buttonless_async_svci_init();
#ifndef DEBUG
    //En DEBUG on a pas le bootloader, il est donc normal d'avoir une erreur
    APP_ERROR_CHECK(err_code);
#endif

SoftDevice is always loaded and I have make a lot of projects with SD and bootloader and I always use this code...

Please can you run the firmare in a nRF52810 and check the crash at 0x18808 or 0x188D4 ?

RE: S112 Fix at address 0x18808

Hung Bui — Thu, 22 Jul 2021 08:09:17 GMT

Please step into the nrf_dfu_svci_vector_table_set() function in your application and check why it says "error : No bootloader was found"
Without properly detecting the bootloader the application will fail when there is any activity related to the bootloader. It's most likely the reason of the crash.

To be able to detect the bootloader, either the bootloader address need to be written in to MBR or into UICR.

RE: S112 Fix at address 0x18808

Gaétan — Wed, 21 Jul 2021 14:20:30 GMT

Yes, with or without bootlader in memory, this the same.

Bootloader source files:devzone.nordicsemi.com/.../secure_5F00_bootloader_5F00_ble.zip

RE: S112 Fix at address 0x18808

Hung Bui — Wed, 21 Jul 2021 14:09:10 GMT

Hi,
I noticed that there is a log saying "error : No bootloader was found"
Is this log with or without bootloader ?
How did you create the bootloader for nRF52810?

RE: S112 Fix at address 0x18808

Gaétan — Wed, 21 Jul 2021 10:37:48 GMT

Hi,

Yes, without charger, we have the issue when I try to connect with NUS (nRFToolBox)

Please found the log on device:

I have no tested with NUS example because if DFU service is not initialized ->all is OK !

static void services_init(void)
{
    uint32_t           err_code;
    ble_nus_init_t     nus_init;
    nrf_ble_qwr_init_t qwr_init = {0};

#ifdef WITH_DFU

    ble_dfu_buttonless_init_t dfus_init =
    {
        .evt_handler = ble_dfu_evt_handler
    };

    // Initialize the async SVCI interface to bootloader.
    err_code = ble_dfu_buttonless_async_svci_init();
#ifndef DEBUG
    //En DEBUG on a pas le bootloader, il est donc normal d'avoir une erreur
    APP_ERROR_CHECK(err_code);
#endif

    err_code = ble_dfu_buttonless_init(&dfus_init);
    APP_ERROR_CHECK(err_code);

#endif

    // Initialize Queued Write Module.
    qwr_init.error_handler = nrf_qwr_error_handler;

    err_code = nrf_ble_qwr_init(&m_qwr, &qwr_init);
    APP_ERROR_CHECK(err_code);

    // Initialize NUS.
    memset(&nus_init, 0, sizeof(nus_init));

    nus_init.data_handler = nus_data_handler;

    err_code = ble_nus_init(&m_nus, &nus_init);
    APP_ERROR_CHECK(err_code);
}

Firmware: devzone.nordicsemi.com/.../BL_2B00_Settings_2B00_App_2B00_SD.zip

RE: S112 Fix at address 0x18808

Hung Bui — Wed, 21 Jul 2021 10:19:09 GMT

Hi Gaetan,

Could you please confirm that even without the charger you still have the issue when you are trying to connect with NUS ?

Could you check if you have any log on the device ? Any assertion ? Could you send the full log ?
If you test with unmodified NUS example do you have the same issue ?

RE: S112 Fix at address 0x18808

Gaétan — Wed, 21 Jul 2021 07:06:05 GMT

Hi,

The batterie charger is :

I have found a current injection on a pin "LED" connected directly to nrf52810.

When bootloader software is present -> sometime fix at adresse 0x18808

When bootloader software is not in flash -> sometime firmwre restart

Now I make multiple tests with nRF52810 pin forced to ouput whith high current configuration...

Regards,

Gaétan

EDIT:

Now, without charger...

I allways have the same fix at address 0x18808 when I connected to NUS !

Last log is : <info> app: Data len is set to 0xB6(182)

NrfToolBox:

With s112_nrf52_7.3.0_softdevice.hex address is 0x188D4

EDIT 2:

When I put the firmware compiled for nRF52810 directly in a PCA10040 (NnRF52832) all is OK no fix but in a nRF52810 allways fix when etablish a NUS connection. No problem when using DFU service.

RE: S112 Fix at address 0x18808

Hung Bui — Tue, 20 Jul 2021 14:13:39 GMT

Hi Gaetan,

Could you please explain a little bit more what happened when you plug the battery charger ? How is it connected to the nRF52 ?
Is there any interrupt ? Do you see any assertion in the log ?