MSPM0C1104: How should I implement flah_BSL function on project of MSPM0C1104.

I can not find my device on I2C bus, and it seems like bsl does not work correct.

I do debug run,and I got an error message"Trouble Writing Memory Block at 0x41c00100 on Page 0 of Length 0x40: Flash download failed! ...
File Loader: Verification failed: Target failed to write 0x41C00100
GEL: File: C:\Users\834076\AppData\Local\Temp\ti_cloud_storage\flash_bsl_LP_MSPM0C1104_nortos_ticlang.out: Load failed."

It's the reason why the BSL function does not work correctly to jump to application code?

Hello Jin Guan-Lin,

Jin Guan-Lin said:

Can I modify start address of application code by change the value of MAIN_APP_START_ADDR which define in flashBSL_defines.h as picture show below

Yes, in your BSL project, modify the MAIN_APP_START_ADDR to match the memory location where the application will be placed in FLASH main memory.

Jin Guan-Lin said:

I can not find any syscfg file to define I2C in the flash_bsl project reference from SDK. Is it necessary to add syscfg to define I2C ?

  There is no sysconfig file for the BSL project.  The I2C and UART driver configuration for the BSL is configured in flashBSL.h.  Set the ->  #define I2C_INTERFACE ENABLE.  And keep in mind that after POR there is a 10 second timeout, which means you have 10 seconds to connect to the BSL else the device will enter low power mode.  This may also explain why you cannot connect to the BSL if you wait too long.

Jin Guan-Lin said:

I got an error message"Trouble Writing Memory Block at 0x41c00100 on Page 0 of Length 0x40: Flash download failed

The issue here is most likely the debugger configuration to perform erase of both MAIN and NONMAIN memory sections. Refer to MSPM0 Bootloader (BSL) Implementation, section 2.2 step 3.

*IMPORTANT* - The BSL boot configuration modifies the NONMAIN section by setting the static write protection to protect the BSL code memory from modification or erasure. After NONMAIN has been programmed for the very first time, any attempt afterwards to erase and re-program NONMAIN or MAIN, the programmer will erase NONMAIN but fail to erase MAIN memory due to the write protection.  This will cause a programming error, leaving NONMAIN blank and will brick the device on the next device reset because NONMAIN is blank  So, to prevent the device from being bricked, please make sure to ALWAYS perform a factory reset on the device each time before erasing and programming the FlashBSL program code.  Refer to the MSPM0 MCU developer's guide , section 7.1.2.

I disable "Perform CRC verification" to load image and then  I can not connect device anymore.

I try to do the factory reset through uniflash but it still fail and the message as show below.

Is there anyway to unblock low power mode?

This is the dev board I use.

Hello Jin Guan-Lin,

Ok, let me check with our development tools engineer on this.