BL653 firmware not fully rebooting on power reset

RE: BL653 firmware not fully rebooting on power reset

Menon — Wed, 02 Aug 2023 11:50:40 GMT

Hello,

Sorry, I missed this case in between the large inflow of cases during the summer vacation time.

Is there any update on this issue?

[quote user="Dagan Raviv"]This type of image loading seems to always prevent the issue, so ideally I would like to modify my DFU bootloader configuration so that each POR during runtime will be followed by this image swap type if possible, and not only after choosing "Confirm" from the Device Manager app.[/quote]

The swap type you are seeing here is one of the Boot swap types you select during a DFU. By giving "Confirm," the new firmware is now permanently in the primary slot.

You could try giving test and confirm from the firmware itself by giving boot_is_image_confimed and confirm it by giving boot_write_image _confirmed().

Kind Regards,

Abhijith

RE: BL653 firmware not fully rebooting on power reset

Menon — Tue, 11 Jul 2023 13:01:22 GMT

Hello,

Sorry for the long response time I am taking here. We are thinly staffed due to the summer vacation here in Norway.

Letting you know that I am still on this case and will get back to you soon.

Kind Regards,

Abhijith

RE: BL653 firmware not fully rebooting on power reset

Menon — Fri, 30 Jun 2023 10:49:36 GMT

Hello,

Sorry, I was bit occupied last days and didn't get enough time to check this. I will get back to you on Monday next week.

Kind Regards,

Abhijith

RE: BL653 firmware not fully rebooting on power reset

Dagan Raviv — Mon, 26 Jun 2023 09:31:04 GMT

I also add a full booting sequence log output received following an image switch to the DFU bootloader and back to my firmware image (using the Nordic's Device Manager mobile app) for comparison. Note that in the logs from the Zephyr OS (all logs before "STARTING DEVICE") the Secondary image values are different, and also the Swap Type. This type of image loading seems to always prevent the issue, so ideally I would like to modify my DFU bootloader configuration so that each POR during runtime will be followed by this image swap type if possible, and not only after choosing "Confirm" from the Device Manager app.

*** Booting Zephyr OS build v2.7.99-ncs1-1  ***
I: Starting bootloader
I: Primary image: magic=good, swap_type=0x3, copy_done=0x1, image_ok=0x1
I: Secondary image: magic=good, swap_type=0x3, copy_done=0x3, image_ok=0x1
I: Boot source: none
I: Swap type: perm
I: Bootloader chainload address offset: 0xc000
I: Jumping to the first image slot
*** Booting Zephyr OS build v2.7.99-ncs1-1  ***
STARTING DEVICE
= Versions Information
  ####################
FPGA date: 23052023
FPGA Version: 1
HSID Version: 15
Powerup data from flash: SN: 42, role: 0, channel: 11
206237 - discovery state reached
Device connected to RF Channel 11
Device connected to RF Channel 11
Device connected to RF Channel 11
Device connected to RF Channel 11

Kind regards,
Dagan

RE: BL653 firmware not fully rebooting on power reset

Dagan Raviv — Sun, 25 Jun 2023 15:28:44 GMT

Hello,

[quote userid="115767" url="~/f/nordic-q-a/100944/bl653-firmware-not-fully-rebooting-on-power-reset/432687"]Are you coming to this assumption just because of the missing logs or is there another reason for this?[/quote]

Beside the partial initialization log output (which I could live with BTW, had it been the only issue) I also encounter some undefined behavior from SPI read/write commands (specifically from/to a FPGA component) - in some boards the POR result in garbage output from these functions in one or more following attempts. My guess is some unflushed buffer remaining from an asynchronous power cycle and improper booting sequence which would have cleaned the buffer if done correctly, but I'm not sure.
Attached an example of a "proper" booting sequence logs output, followed by a partial one:

*** Booting Zephyr OS build v2.7.99-ncs1-1  ***
I: Starting bootloader
I: Primary image: magic=good, swap_type=0x3, copy_done=0x1, image_ok=0x1
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Swap type: none
I: Bootloader chainload address offset: 0xc000
I: Jumping to the first image slot
*** Booting Zephyr OS build v2.7.99-ncs1-1  ***
STARTING DEVICE
= Versions Information
  ####################
FPGA date: 23052023
FPGA Version: 1
HSID Version: 15
Powerup data from flash: SN: 42, role: 0, channel: 11
206237 - discovery state reached
Device connected to RF Channel 11
Device connected to RF Channel 11
Device connected to RF Channel 11
Device connected to RF Channel 11

Powerup data from flash: SN: -1, role: 0, channel: 1
206237 - discovery state reached
Device connected to RF Channel 1
Device connected to RF Channel 1
Device connected to RF Channel 1
Device connected to RF Channel 1

Due to invalid SPI output, the data received from flash is parsed to wrong values, resulting in undefined behavior...

Thanks again for your help,
Dagan

RE: BL653 firmware not fully rebooting on power reset

Menon — Fri, 23 Jun 2023 12:13:19 GMT

Hello,

[quote user=""]I assume this feature is enabled by storing the internal state of the firmware in the non-volatile memory and using it to resume after power reset. This configuration skips some necessary initiation sequence, resulting in unwanted firmware behavior following power reset.[/quote]

AFAIK, the entry point after a reset in handled by the reset_handler.

I am not sure why this is happening. Are you coming to this assumption just because of the missing logs or is there another reason for this?

So apart from the log messages is your application working properly after a power on reset? Will be nice if you share both (working and failing ) the logs. Could you also try increasing the log_buffer?

Kind Regards,

Abhijith

RE: BL653 firmware not fully rebooting on power reset

Dagan Raviv — Tue, 20 Jun 2023 14:52:33 GMT

Hi,

Sure, my main method for debug and tests for the booting sequence is currently logs to console through a UART port, in which I do not see the correct initiation logs I expect to get after reset, but logs from advanced points in the flow. This happens only following a power cycle, after commanding an image switch to the DFU and back (either if I uploaded a different image or simply switched back to the exiting one) the flow I see is the correct initiation sequence through all the necessary steps for my firmware to operate properly.

Thanks,

Dagan

RE: BL653 firmware not fully rebooting on power reset

Menon — Tue, 20 Jun 2023 13:21:35 GMT

Hello,

[quote user=""]when resetting the power supply to the board the firmware resumes running from some advanced point in the application and not performing a full software and hardware reboot from the beginning. I [/quote]

Would be nice if you could brief a little more on this, like how do you test that the Application is booting incorrectly? Also, are you seeing this behavior when you are doing a DFU, or does this happen only when you power cycle the board?

Kind Regards,

Abhijith