• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 54 subscribers
  • Views 761 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCSv5.2.0 troubles when programming EEPROM bank of TMS570LS2125

Eugene K
Expert 1685 points

Following errors are reported when loading program with EEPROM data from within CCS GUI:

CortexR4: Trouble Writing Memory Block at 0xf0208000 on Page 0 of Length 0x7ff0
CortexR4: GEL: File: ....\EepromData.out: Load failed.

There is also another error when EEPROM data is the part of another bigger file:

CortexR4: Error during Flash verification (Flash algorithm timed out). Operation cancelled.
CortexR4: Flash verification returned error condition. Operation cancelled.
CortexR4: Trouble Writing Memory Block at 0xf020ffe0 on Page 0 of Length 0x20
CortexR4: GEL: File: ....\application.out: Load failed

Non EEPROM flash ranges seems to work fine.

The same set of files programs just fine with nowFlash.

Eugene

  • 0
    TI__Guru**** 171104 points

    Eugene,

    Are these areas written through registers or are they memory mapped? In a recent past someone posted a very similar question... I just don't recall if it was a R4 or something else. Let me find it. 

    Regards,

    Rafael

  • 0 in reply to desouza
    Expert 1685 points

     Is there a need for support from target custom JS or GEL files? My memory map is set up like this

      session.memory.map.add(0x00000000, Memory.Page.PROGRAM, 0x300000, true, false),
      session.memory.map.add(0x08000000, Memory.Page.PROGRAM, 0x40000, true, true),
      session.memory.map.add(0x08400000, Memory.Page.PROGRAM, 0x40000, true, true),
      session.memory.map.add(0x20000000, Memory.Page.PROGRAM, 0x300000, true, false),
      session.memory.map.add(0xF0000000, Memory.Page.PROGRAM, 0x200000, true, false),
      session.memory.map.add(0xF0200000, Memory.Page.PROGRAM, 0x10000, true, false),
      session.memory.map.add(0xFC000000, Memory.Page.PROGRAM, 0x4000000, true, true)

    Eugene

  • 0 in reply to Eugene K
    TI__Guru**** 171104 points

    Eugene,

    I checked the device's datasheet and the EEPROM regions are indeed memory mapped (the post I mentioned was for M4). The range goes from 0xF0200000 through 0xF020FFFF. Therefore, I created a small Hello world program that allocates itself entirely on the EEPROM memory space and I am able to reproduce the same issue you are seeing in my LS3137 board.

    The GEL file provided with CCSv5.2 correctly maps the EEPROM memory region.

    LS3137GEL said:

        GEL_MapAdd(0xF0200000, 0, 0x00010000, 1, 0); /* EEPROM                      */

    Therefore I suspect it is a bug. I will check some additional details and get back.

    Regards,

    Rafael

    TMS570_Hello.zip
  • 0 in reply to desouza
    TI__Guru**** 171104 points

    Eugene,

    Filed a bug today: SDSCM00044221

    Please check its status at the link SDOWP in my signature below.

    Cheers,

    Rafael

  • 0 in reply to desouza
    Prodigy 70 points

    Hi!

    Is there any update on this topic?

    I have the same problem with CCS 5.2.1.00018

    thx.

    Valentin

  • 0 in reply to Valentin Ecker
    Expert 1685 points

    I do not seem to have that problem anymore with Version: 5.2.1.00018. At least I do not see the errors. This does not imply that it has been fixed.

    I have not looked in depth into it because I was working on something else.

    Eugene

  • 0 in reply to Eugene K
    Expert 1685 points

    Well, It appears that the issue is still there. The error I get falls into EEPROM bank ECC:

    CortexR4: Error during Flash verification (Flash algorithm returned error condition). Operation cancelled.
    CortexR4: Flash verification returned error condition. Operation cancelled.
    CortexR4: Trouble Writing Memory Block at 0xf0101800 on Page 0 of Length 0x2

    The worst part is that it comes and goes. Programming never fails on other areas of flash no matter how big ELF files are. Does not look like it is something related to my PC.

    Eugene