This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

LAUNCHXL-F28379D: CPU2 seems to stuck at _system_post_cinit() 0x3FE44F while the CPU1 stuck waiting to sync with cpu2

Part Number: LAUNCHXL-F28379D
Other Parts Discussed in Thread: C2000WARE

Tool/software:

I'm trying to create a dual cpu project that read adc, send it to cpu2 then send it through can, it works. But, when i try the standalone mode in flash the cpu2 seems to stuck in the address 0x3FE44F even after reset or power cycle ( i use blinking led as an indicator if cpu2 is working ).

i already call the IPCBootCPU2 like this

 

The cpu 1 stuck in trying to sync with cpu 2, but since the cpu2 stuck they seems to be in deadlock.