Hardfault at CDC

RE: Hardfault at CDC

Edvin — Tue, 09 Jun 2020 14:38:57 GMT

Yes. That sounds like a possible issue. If you write too long byte arrays into smaller sized buffers, then you will continue to write after the buffer address, changing whatever is behind that in flash. It can typically lead to hard faults. Try increasing the size of the buffer, or lowering the size of the string that you write.

Best regards,

Edvin

RE: Hardfault at CDC

Ted — Tue, 09 Jun 2020 09:04:56 GMT

Edvin Sorry to bother you. It seems the code cause the hardfault as follows. The code prints too long, it prints about 77 characters. But the m_tx_buffer has only 64 bytes. I need to do more test. Thank you very much.

sprintf((char*)m_tx_buffer, "Options: %3dMHz, Try %2d, flash size: 0x%4x, erase: 0xD400, LFID: 0x%4x\r\n"
,CARRIER_FREQ, TRY_TIMES, DEST_CODE_SIZE-4, LF_WAKEUP_ID_APP);
SEND_UART_STRING(m_tx_buffer);

RE: Hardfault at CDC

Edvin — Mon, 08 Jun 2020 14:00:33 GMT

Hello,

You say that you run into a hardfault? I suspect that you mean an app_error? What does it look like? Does the log say anything?

2: When the application isn't running, then the USB is not enumerated, so the computer will not detect it as a USB device before it is running. Usually, USB devices will get power from the USB port, so it will start the application once you plug it in.

BR,

Edvin