TMS320F2800157: Flash Memory error erasing Bank 0 FMSTAT

Part Number: TMS320F2800157
Other Parts Discussed in Thread: LAUNCHXL-F2800157, UNIFLASH

Tool/software:

Dear Sir,

I encountered the error below on Kit LAUNCHXL-F2800157 when I debug, please help me fix it
Thanks!


C28xx_CPU1: Flash Programmer: Error erasing Bank 0 FMSTAT (STATCMD on some devices) value = 33. Operation Cancelled (0).
C28xx_CPU1: File Loader: Memory write failed: Unknown error
C28xx_CPU1: GEL: File: D:\bootloadersolar\CPU1_FLASH\bootloader.out: Load failed.

  • Hi TI support team,

    please help me this case!

  • Cong,

    If you connect to the device with CCS, and bring up the flash tools, are you able to execute the erase command from that dialogue box?  I don't want to try and load the .out file just yet, let's see if the standalone erase can work first.

    If this doesn't work, can you open a memory window to the flash address space and reply back what values you see?  I'm trying to determine if the code security module is active and protecting the flash region.

    Best,

    Matthew

  • Thanks for your support!

    I tried to use Uniflash to flash firmware, the same error as I sent above. And I have a build code on RAM and run debug, I checked that the Flash partition was not deleted, still between the data I had previously recorded.

    I have replaced the new MCU on Kit and work normally. Now I can't debug to read the Flash area as you want

  • Cong,

    Are you seeing the same issue on the new MCU, or are you saying that flash is programming OK now?

    Best,
    Matthew

  • Hi Matthew

    I just had a long holiday, on the new MCU, everything worked normally. I mean, I can't read the flash memory area on the old MCU that has a flash error as you want.

  • Cong,

    Thanks for clarifying, I think the older device the DCSM got activated and locked the device.  Unless we can unlock it, we won't be able to re-program etc.

    Best,

    Matthew

  • Hi Matthew ,

    In the event that the DCSM got activated, which actions lead to device lock?