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.

TMS320F28P650DH: use uniflash to load CPU2

Part Number: TMS320F28P650DH
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

CPU1 bank0 and bank1, CPU2 banks4

Use uniflash to load image.

CPU1 can be loaded successfully.  But load CPU2,report bank4 erasing error.

[8/13/2024, 2:55:10 PM] [INFO] C28xx_CPU2: GEL Output: RAM initialization done
[8/13/2024, 2:55:10 PM] [INFO] C28xx_CPU2: GEL Output: Memory Map Initialization Complete
[8/13/2024, 2:55:12 PM] [ERROR] C28xx_CPU2: Flash Programmer: Error erasing Bank 4 FMSTAT (STATCMD on some devices) value = 65 (decimal). Operation Cancelled (0).
[8/13/2024, 2:55:12 PM] [ERROR] C28xx_CPU2: File Loader: Memory write failed: Unknown error

I already replace the dll and xml that local FAE provide.  it still reports this error.

  • Hi Sheldon,

    After loading CPU1 image, are you clicking the 'Configure Clock' button in the Uniflash tool so that CPU2 image can be loaded? CPU1 target needs to configure the Flash Banks for CPU2 by clicking the 'Configure Clock' button.

    Thanks and regards,

    Charles

  • Yes, I have clicked 'configure clock'. 

  • Sheldon,

    Does the same behavior occur when using a generated package from the Uniflash tool and using the command line interface? What does the DLL and XML folder structure look like for the generated package?

    Thanks,

    Charles

  • Yes. It is same.   Erase fail.    Seems that CPU2 is not running.       

    Yesterday I tried to debug with local FAE, found CPU2 can be programmed successfully if click the configure clock of CPU1 manually.       Seems that after load CPU1 successfully, CPU2 clock is not configured, Need to configure cpu2 clock manually.   

    It is strange that FAE's computer don't need to click the "configure clock".  step1: load CPU1, step2: load CPU2.   Both CPU1 and CPU2 can be programmed successfully.

    I check the DLL and XML.  It is new.   DLL is created on  Aug 2th,   XML is created on July 11th.

    I check the VCC, it is 3.3V. And try use DC source to provide the VCC.  It has same problem.

  • Add more information.   I use laptop computer to create the script.  It can work on desktop computer.

  • Ok, thanks Sheldon. I've asked Bliss to set up a meeting to discuss with you offline on the issue further.

    Thanks and regards,

    Charles