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.

Target Failed to read 0xFFFFFFF0

Other Parts Discussed in Thread: UNIFLASH

Everything was working fine yesterday and before, but this morning I started receiving this error message that I cannot get rid of. I tried turning off the unit and my desktop, then restarting to no avail. Uniflash will not erase, while CCS will not debug.

CCS Console Message:

CortexR4: GEL Output: Memory Map Setup for Flash @ Address 0x0CortexR4: Error initializing flash programming: Target failed to read 0xFFFFFFF0
CortexR4: Loader: One or more sections of your program falls into a memory region that is not writable. These regions will not actually be written to the target. Check your linker configuration and/or memory map.
CortexR4: File Loader: Verification failed: Values at address 0x0000000000000000 do not match Please verify target memory and memory map.
CortexR4: GEL: File: C:\SoftDev\TiWorkspaces\CCMv3\Versions\Current\CCMv3\Debug\CCMv3.out: a data verification error occurred, file load failed.

Thoughts?

Sarah

  • Sarah,

    Do you have the option 'system reset on connect' set? (it's on the Flash tab of the Debug Properties).

    If you turn on the MPU then especially this is useful.
  • Sorry this may only be available through CCS. I need to install Uniflash to see if the same option is there or not.
    But, if you do not find this option in UniFlash - please try this way through CCS to see if it makes a difference. Usually it will.
  • Anthony F. Seely said:
    Sorry this may only be available through CCS.

    The "System Reset on Connect" option is available on the Flash Settings on Uniflash 3.4.0. The Uniflash Flash Settings are the same as available under CCS 6.1.3 Debug properties.

  • Yes it is - thanks Chester.

  • Sarah Weinberger said:
    Everything was working fine yesterday and before, but this morning I started receiving this error message that I cannot get rid of. I tried turning off the unit and my desktop, then restarting to no avail. Uniflash will not erase, while CCS will not debug.

    CCS Console Message:

    CortexR4: GEL Output: Memory Map Setup for Flash @ Address 0x0CortexR4: Error initializing flash programming: Target failed to read 0xFFFFFFF0

    The address 0xFFFFFFF0 is the Device Identification Register (DEVID) which is read as part of the flash programming (as shown by the CCS debug server log for a successful flash program of a Hercules device) to identify the target device.

    Did that error message start occurring after a software change?

    i.e. maybe related to your other thread RM48L952ZWT: Erasing chip if bad code inside

  • Sarah Weinberger said:
    Everything was working fine yesterday and before, but this morning I started receiving this error message that I cannot get rid of. I tried turning off the unit and my desktop, then restarting to no avail. Uniflash will not erase, while CCS will not debug.

    CCS Console Message:

    CortexR4: GEL Output: Memory Map Setup for Flash @ Address 0x0CortexR4: Error initializing flash programming: Target failed to read 0xFFFFFFF0

    I have found that error can be repeated by loading a program which enables the MPU, but with no access to the System Module - Frame 1 registers.

    After loading such a program, enabling "System Reset on Connect" in the Flash Settings prevents the error message, and allows another program to be flashed.

  • Wow, quite a few replies.

    Yesterday, I suffered with the problem for several hours. After a few hours, I switched to my other board, tried again, and same problem, so I switched back to my original board and the problem thankfully disappeared, but not before soaking up several hours. This morning (maybe the problem knows its morning?) came back with a vengeance!

    I did NOT have that option set in CCS. I set that option, "System Reset on Connect" in Debug properties | Flash, and I am able to debug. Yay!

    I will read the other posts shortly.