Migrate CLI over CDC/ACM to project open_bootloader_mbr, but stuck in cli_write

Question

Hi support,

Firstly, environment as below,

(1) upon SDK (nRF5_SDK_15.3.0_59ac345)

(2) Nordic Open_Bootloader (example project: Open_bootloader_usb_mbr_pca10056_debug)

(3) Nordic 52840 DK (PCA10056)

What I am doing is just try to migrate CLI over CDC/ACM to project open_bootloader_mbr, but stuck in cli_write and would not get out as below,

Can anyone tell me why please? Thanks a lot.

FYI, I have separate the configuration of CLI_CDC/ACM away from that of DFU_CDC/ACM as below,

(1) Setting of CLI_CDC/ACM

//==========================================================

// <h> nrf_cli_cdc_acm - CDC ACM command line interface transport

//==========================================================
// <q> NRF_CLI_CDC_ACM_ENABLED  - Enable/disable the CLI CDC ACM module.
 

#ifndef NRF_CLI_CDC_ACM_ENABLED
#define NRF_CLI_CDC_ACM_ENABLED 1
#endif

// <o> NRF_CLI_CDC_ACM_COMM_INTERFACE - COMM interface number. 
#ifndef NRF_CLI_CDC_ACM_COMM_INTERFACE
#define NRF_CLI_CDC_ACM_COMM_INTERFACE 0
#endif

// <s> NRF_CLI_CDC_ACM_COMM_EPIN - COMM IN endpoint number.
#ifndef NRF_CLI_CDC_ACM_COMM_EPIN
#define NRF_CLI_CDC_ACM_COMM_EPIN NRF_DRV_USBD_EPIN2
#endif

// <o> NRF_CLI_CDC_ACM_DATA_INTERFACE - DATA interface number. 
#ifndef NRF_CLI_CDC_ACM_DATA_INTERFACE
#define NRF_CLI_CDC_ACM_DATA_INTERFACE 1
#endif

// <s> NRF_CLI_CDC_ACM_DATA_EPIN - DATA IN endpoint number.
#ifndef NRF_CLI_CDC_ACM_DATA_EPIN
#define NRF_CLI_CDC_ACM_DATA_EPIN NRF_DRV_USBD_EPIN1
#endif

// <s> NRF_CLI_CDC_ACM_DATA_EPOUT - DATA OUT endpoint number.
#ifndef NRF_CLI_CDC_ACM_DATA_EPOUT
#define NRF_CLI_CDC_ACM_DATA_EPOUT NRF_DRV_USBD_EPOUT1
#endif

(2) Setting of DFU_CDC/ACM

#define CDC_ACM_COMM_INTERFACE          2//0
#define CDC_ACM_COMM_EPIN               NRF_DRV_USBD_EPIN4//NRF_DRV_USBD_EPIN2
#define CDC_ACM_DATA_INTERFACE          3//1
#define CDC_ACM_DATA_EPIN               NRF_DRV_USBD_EPIN3//NRF_DRV_USBD_EPIN1
#define CDC_ACM_DATA_EPOUT              NRF_DRV_USBD_EPOUT2//NRF_DRV_USBD_EPOUT1

Regards

J.S.

Einar Thorsrud · Accepted Answer

Hi, 
 Can you elaborate on what you would like the bootloader to do, when and how? If the idea is to have a way to recover from faulty application using something like a golden image, then you could think of this as an alternative that requires minimal changes to the bootloader (I don't know how it fits with your product, though): 
 
 If the bootloader detects that the reset reason is watchdog reset or CPU lock-up, enter DFU mode. 
 When nRF enters DFU mode unexpectedly, the host CPU can assume that there is a problem with the application, and do some of the following (whatever is appropriate in your case):
 
 choose to perform a DFU update (if that is what you need to recover) 
 delete flash regions used to store application data (if that is what causes problems). This could be triggered by the bootloader itself if safe, or you could expand the DFU protocol, etc. This is perhaps a task where you would use CLI?

However, depending on your application, it would also make sense to investigate to what degree the application is capable of "messing itself up". Generally, adding more logic (which can potentially introduce more bugs an issues) to fix issues that may never occur is not necessarily a good idea.

Migrate CLI over CDC/ACM to project open_bootloader_mbr, but stuck in cli_write

Top Replies