TMS320F28377D: CPU2 failed to write the s19 program

Tool/software:

Hi Champs,

I ask this for our customer.

At present, there is no problem for customer to load .out files to CPU1 and CPU2 normally, but there is a problem with loading s19 files.

CPU1 can normally obtain the right to use FlashPump and write the S19 program offline, but when CPU2 needs to get the right to use FlashPump and burn the program, the program will be directly stuck, whether it is to assign the IPC_PUMP_KEY register in CPU2 0x01 or the assignment in CPU1 will be stuck, but the assignment 0x02 will be fine. And I had already done ReleaseFlashPump before seizeflashpump

The way to load s19 is: the host computer sends it to cpu1 through TCP, CPU1 enters the bootloader after receiving the loading instruction, and then checks the data, if it is its own CPU1 program, it directly erase flash and then program, if it is a program of CPU2, it is sent to CPU2 through IPC, and CPU2 erase the flash then program.

This method can load the program of CPU1 normally, but CPU2 fails to load, and CPU2 cannot obtain the right to use FlashPump, resulting in the failure to erase Flash

Note: In the bootloader, the default is to send the flashpump to cpu1 first, if it is judged to be a cpu2 program, cpu1 releases the flashpump, and then cpu2 gets the flashpump.

Could you please help to check this issue? Thanks!

Julia