• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 1272 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.

An error when using UniFlash on TMS570LS1227 via XDS100v2

Hiroyasu Matsubara
Expert 1405 points

Other Parts Discussed in Thread: UNIFLASH, TMS570LS1227

Hello,

I tried to write a program binary data by using UniFlash to TMS570LS1227 via XDS100V2 on our custom board,

but the error message was shown:

[16:26:52] Start operations on multiple programs on the target core...
[16:26:53] CortexR4: GEL Output:  Memory Map Setup for Flash @ Address 0x0
[16:26:53] Loading program: C:\Users\140301\workspace_v5_3\TMS570LS1227_instaspin_bldc\Debug\TMS570LS1227_instaspin_bldc.out
[16:26:53] WARNING >> 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.

[16:27:02] FATAL >> CortexR4: Trouble Reading Memory Block at 0x0 on Page 0 of Length 0x7308: (Error -154 @ 0x0) One of the FTDI driver functions used to write data returned bad status or an error. (Emulation package 6.0.83.1)

[16:27:02] ERROR >> CortexR4: File Loader: Verification failed: Target failed to read 0x00000000

What should I do to solve this problem ?

I would appriciate if someone could reply to my question.

Regards,

Hiroyasu

  • 0
    TI__Guru 72500 points
    Can you attach the ".map" file and the ".out" file?
  • 0 in reply to Bob Crosby
    Expert 1405 points

    Hello,

    I attached the .map and .out file.5808.TMS570LS1227_instaspin_bldc.zip

    Hiroyasu

  • 0 in reply to Hiroyasu Matsubara
    TI__Guru 72500 points
    I had no problem using UniFlash with an XSDS100V2 to program the .out file you provided into a TMS570LS1227. (I did not even get the warning message.) I suspect a hardware problem. Double check power, nPORRST, nRST, TEST, the crystal and all of the JTAG pins.
  • 0 in reply to Bob Crosby
    Expert 1405 points

    Hello Bob,

    Thank you for your reply.

    I solved this problem.

    Once the Q&A watchdog communication has started between Hercules and TPS65381,I couldn't write a software(*.out) to Hercules,

    So,I made a software that would become TPS65381 to be stayed in Diag state when I would like to write to Hercules MCU.

    The hint was written in the application note "SPNA176A" :

    In the control card, a DIP switch is placed between the TPS65381 (Pin NRES, ENDRV) and the
    Hercules device (Pin nPORRST, GIOA4) so that the user can choose ON (connect) or OFF
    (disconnect).
    This DIP switch is for debug purpose only. If the watchdog in TPS65381 is not served correctly, the
    TPS65381 might keep resetting the MCU. With this DIP switch, during debug stage, you can
    disconnect the NRES and MCU nPORRST if this saturation occurs.
    In production, this DIP switch is not necessary since the correct Flash image has been programmed
    into the device. If reprogramming a system after production is required, the application bootloader can
    force the TPS65381 to stay in diagnostic mode, re-program the Flash, and go to active mode after the
    program completes.

    Regards,

    Hiroyasu