• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 1816 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCS/TMS320C5545: Trouble Writing Memory Block

minkyo seo
Expert 1230 points

Part Number: TMS320C5545

Tool/software: Code Composer Studio

After debug, I always get "

C55xx: Trouble Writing Memory Block at 0x10000 on Page 0 of Length 0x7ff0: (Error -1146 @ 0x10000) Data scanned out of device is corrupt and not valid. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 7.0.48.0)
C55xx: File Loader: Verification failed: Target failed to write 0x010000@PROGRAM
C55xx: GEL: File: C:\Users\smk-pc\workspace_v7\CSL_I2S_AudioCodec_DMA\Debug\CSL_I2S_AudioCodec_DMA.out: Load failed.

" 

sometimes " Trouble Reading"

How can I solve this?

I'm using c5545 dsp

and I'm testing the example "CLS_I2S_DMA_MultipleInstanceExample_out"

and I modified some code 

Please Answer me

thx

  • 0
    TI__Guru**** 169894 points
    Hi,

    Are you using a development kit? If so, which one? Also, which Debug Probe are you using? This would help me try to reproduce the problem here.

    An explanation to the issue is that the debug probe is trying to load the program to valid memory (0x10000 is SRAM) but the verification is returning mismatched data. In this case, I would investigate the following possible root causes:
    - something is incorrect with the Debug Probe configuration
    - the connections between the Debug Probe and the hardware board can be faulty (cable or twisted wires)
    - a problem on the device itself (perhaps it is not properly powered)
    - if there is pre-programmed software that may be causing the device to prevent a proper JTAG communication (for example, a watchdog timer is pre-programmed and resets the device continuously)

    Hope this helps,
    Rafael