• State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 86 subscribers
  • Views 610 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 274622
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

NCS v1.6.0 Mucboot issue

zero

Dear friends:
I am based on the following link:
devzone.nordicsemi.com/.../device-firmware-update-dfu-with-mcuboot-bootloader
Operation steps test the function of mcuboot.
According to the steps, dfu can be done normally on 52840-dk in ncs v1.4.0 version, but I want to do dfu on ncs v1.6.0 according to the above steps, in "18. Press the reset button on the DK and observe the output on the terminal: "There is a problem in this step: after downloading the merged hex, restarting the device will not jump to the application, the log is as follows:

[15:03:48.692] *** Booting Zephyr OS build v2.6.0-rc1-ncs1 ***
[15:03:48.953] I: Starting bootloader
[15:03:48.953] I: Enter the serial recovery mode
[15:03:48.953] I: Device suspended
[15:03:48.960] I: Device resumed
[15:03:49.059] I: from suspend
[15:03:49.059] I: Device configured

Please help analyze the reason?

Parents Reply
  • 0 in reply to Charlie

    Hi Charlie,

    Tried the solution you linked: Add CONFIG_UART_CONSOLE=n in usb_cdc_acm_log_recovery.conf, it can run normally on 1.6.0, but I still have a question: Why should CONFIG_UART_CONSOLE be set to n to jump to the application? (Have tried not to add CONFIG_UART_CONSOLE=n, can not jump to the application)

    Best regards,

    Zero

Children
No Data
Related
Terms of service