Greetings,
I have worked with the MCUBoot and its Serial Recovery feature with success and recently tried to enable the CONFIG_BOOT_SERIAL_WAIT_FOR_DFU option ( as well as the
Greetings,
I have worked with the MCUBoot and its Serial Recovery feature with success and recently tried to enable the CONFIG_BOOT_SERIAL_WAIT_FOR_DFU option ( as well as the
Hi,
Here is my colleague's sample https://github.com/hellesvik-nordic/samples_for_nrf_connect_sdk/tree/main/bootloader_samples/serial_recovery/mcuboot_serial_recovery_cdc_acm_wait
Hope it can help.
Regards,
Amanda H.
Hello Amanda H.,
Unfortunately, I have gone through this sample in detail, and the only thing that this sample has that my application does not are the two lines I added:
# Enable wait for DFU functionality CONFIG_BOOT_SERIAL_WAIT_FOR_DFU=y CONFIG_BOOT_SERIAL_WAIT_FOR_DFU_TIMEOUT=5000
Apart from including the bootloader the main application it is totally bare and the mcuboot.conf overlay for the bootloader has a few basic options enabled along with the two already mentioned that have to do with the wait for DFU functionality, it is extremely simple. So one would expect enabling the two options mentioned above to work but the device remains in bootloader mode forever even when no commands are sent ( or the serial communications are physically disconnected ).
Could you please confirm that this sample builds and works correctly on the nRF52840DK for NCS v2.1.0? I have not been successful in building it as is. It would be extremely helpful to have a mitigation action for this, even if that ultimately is that I have to migrate to a newer version of NCS. But I would like some confirmation that nothing else is possible before I move on to something very time-consuming. I also would like confirmation that a migration to a newer version of NCS would solve this issue.
Thank you and I look forward to hearing from you.
Best regards,
Stavros
Hi Amanda,
So I will need to migrate to a version higher than v2.2.0 to solve this issue, if I understand correctly, there is no other alternative. Is that correct?
That's correct. I would suggest the latest version v2.5.1 if it's possible.
Great! Thank you very much! Have a nice day
I have a similar issue with NCS 3.1.1. Is there a regression. MCUBoot is quite buggy in NCS 3.1.1 :
It contains at least : https://github.com/mcu-tools/mcuboot/issues/2336
Is Nordic expects to release a new NCS to fix mcuboot ?
I have a similar issue with NCS 3.1.1. Is there a regression. MCUBoot is quite buggy in NCS 3.1.1 :
It contains at least : https://github.com/mcu-tools/mcuboot/issues/2336
Is Nordic expects to release a new NCS to fix mcuboot ?
Yes, it will be fixed in the next release, NCS v3.2.0. See this commit https://github.com/nrfconnect/sdk-mcuboot/commit/f1aa499c51c6068d13d1ee63804c2d4f290227c1