nRF52833 cannot use MCUBoot with usb

I tried to fully replicate the example from DevAcademy (academy.nordicsemi.com/.../) for my project, and added a button and an LED in the overlay. However, once SB_CONFIG_BOOTLOADER_MCUBOOT=y is set, my mcu shows no response when plugged into the usb port on the computer after programming. If I cancel this config, the app can start normally. In addition, I tried to power on by holding down a button, but the specified led does not light up, and the computer does not recognize any new CDC device.

# Enable logging for MCUboot
CONFIG_LOG=y
CONFIG_MCUBOOT_LOG_LEVEL_WRN=y

# Enable Serial Recovery over UART
CONFIG_MCUBOOT_SERIAL=y

# Disable console UART, since Serial Recovery uses UART
CONFIG_UART_CONSOLE=n

# Configure boolader to use two slots
CONFIG_SINGLE_APPLICATION_SLOT=n

# Turn on a LED so we can see when Serial Recovery mode is active
CONFIG_MCUBOOT_INDICATION_LED=y

# STEP 1.1 - Configure serial recovery to use CDC_ACM, which by default uses the USB
CONFIG_BOOT_SERIAL_CDC_ACM=y

# STEP 3.1 - Increase flash space for MCUboot child image, to fit USB drivers
CONFIG_PM_PARTITION_SIZE_MCUBOOT=0x10000

Parents
  • Hello,

    Please confirm if you are using the nRF52833 DK or another board. If it's not a Nordic development kit it may not have the optional 32 KHz crystal mounted, which means you need to change the default clock source to the internal RC oscillator in both the bootloader and application by enabling CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC

    Best regards,

    Vidar

Reply
  • Hello,

    Please confirm if you are using the nRF52833 DK or another board. If it's not a Nordic development kit it may not have the optional 32 KHz crystal mounted, which means you need to change the default clock source to the internal RC oscillator in both the bootloader and application by enabling CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC

    Best regards,

    Vidar

Children
No Data
Related