• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 29 subscribers
  • Views 355 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.

Trouble Writing Memory Block at 0x8003300 for TMS570LC4357 HDK using FREE RTOS.

Kalyani Shirole31
Prodigy 10 points
Other Parts Discussed in Thread: TMS570LC4357, HALCOGEN, UNIFLASH

Initially I was able to flash TMS570LC4357 using CCS but recently code is not getting flashed. Following error is generated :

CortexR5: Trouble Writing Memory Block at 0x8003300 on Page 0 of Length 0x7ff0: (Error -1065 @ 0x0) Unable to access device memory. Verify that the memory address is in valid memory. If error persists, confirm configuration, power-cycle board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 5.1.641.0)
CortexR5: File Loader: Memory write failed: Target failed to write 0x08003300
CortexR5: GEL: File: D:\Halcogen\HDK_Slot_Detection_Position_Estimation\Debug\HDK_Slot_Detection_Position_Estimation.out: Load failed.

Please guide on same.

Thanks in advance

  • 0
    TI__Mastermind 18320 points
    Kalyani,

    This question does not really seem to be specific to TI-RTOS, so I moved this thread over to the device forum in hopes that it will get a faster response there.
  • 0
    TI__Mastermind 49120 points
    Kalyani,

    This normally happens when code executing in the part causes exceptions that are a higher priority than halting the CPU in a debug state. The flash erase and programming sequence requires the CPU to be halted so the first thing it tries to do is halt the CPU. This could be prevented by the code causing higher-priority exceptions (reset, data abort, FIQ, IRQ, undefined instruction, prefetch abort in descending order of priority). A debug halt request has the same priority as the prefetch abort.

    So you need to erase the part by halting the CPU before it executes any code that causes any of these higher-priority exceptions. I am afraid you will have to play with the system reset button and the flash erase command via CCS (or Uniflash) for this. Which board are you working with?

    Also, please check the .map file to see if you have any sections actually mapped to the CPU SRAM (0x08003300 is in this memory) for initialization upon loading the code.

    Regards,
    Sunil