LP-MSPM0G3507: secondary_BSL

Hi Pakho,

Want to make it clear, If you configurate GPIO through SYSCONFIG?

If yes, try not through Sysconfig and SYSCFG_DL_init();  And just init GPIO manually(You can copy the init function code generated by sysconfig, but just GPIO part).

Regards,

Zoey

How about the I2C communication? I need MCU to be able to control I2C peripherals during the upgrade process.

Sorry to say that, once you jump into secondary BSL, you can not receive other message via I2C or any other which need CPU.

Regards,

Zoey

No need to receive, only need to send. Is that possible to upgrade data can be received through UART and data control devices can be sent externally through I2C under BSL?

It is the same. To send message, you need to use CPU to put message into UART/I2C FIFO, which can not be realized while BSL.

Regards,

Zoey

Emm... This makes me confused. Below is the sample from CCS(secondary_bsl_i2c_LP_MSPM0G3507_nortos_ticlang). And you also can see UART interface demo after I2C one.

So I think I2C/Uart should work under BSL. Can you please check these two?

Sorry for confusing. I am not sure whether I have got what you want.

I mean you can use BSL via UART or I2C or SPI to update your code. But you can not use this peripherals to work for your self application while BSL.

Thanks,

Zoey

So the MCU only can be the slave under BSL, not the host.

Not exactly.

Under BSL, the CPU can only run the code of BSL, and I2C/UART will receive command or send response to finish programming. In this process, the MCU's communication peripherals can't do anything else

What I mean by BSL is a secondary BSL, not ROM, so there should be no problem, right?

It is the same. If you need to transfer your own message not related to BSL message in secondary BSL code, the timing is easily misaligned, resulting in unsuccessful upgrades.