• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 1480 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.

Original question:

CCS/TMDSEMU110-U: UNIFLASH V4 command line error -programStatusOutput option

CCS/TMDSEMU110-U: UNIFLASH V4 command line error when loading multiple hex files TMS320F28377S

Nestor Estrada
Prodigy 80 points
Part Number: TMDSEMU110-U
Other Parts Discussed in Thread: TMS320F28377S, UNIFLASH

Tool/software: Code Composer Studio

Hello Guys,

Need help.

I am attempting to load mulitple files in TMS320F28377S. The 1st file is the "loader.hex" and the second is the firmware "15.hex".

When I used Uniflash V4 I can successfully load the mulitple files. Here is my snapshot on Uniflash. But when I generated Stand Alone command line package and run the dslite.bat it fails multiple files. I have attached my dslite.bat. May I know what is wrong? thank you.https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/81/dslite.7z

When I run the generated dslite.bat it fails.

  • 0
    TI__Guru**** 472291 points
    I'm not fully sure what is going on. But I can explain a few things. The main error is a data verification error. Basically one of your hex file is configured to be loaded into a program memory address that is not valid on the target (and blocked by the debugger memory map). hence, verification is failing at address 0x78010@Program. Please check that this valid (or not).

    The main question is why it appears to program successfully via the GUI. Can you press the "Verify Images" button and see if that is successful or not?

    thanks
    ki
  • 0 in reply to Ki
    Prodigy 80 points

    Hello Ki,

    I now pressed the "Verify Images" button and it failed. Same failure mode as in the batch file.

    See below.

    [11/13/2018, 10:03:53 AM] [INFO] C28xx_CPU1: Unlocking device...
    [11/13/2018, 10:03:53 AM] [INFO] C28xx_CPU1: Lock status: 0
    [11/13/2018, 10:03:53 AM] [SUCCESS] C28xx_CPU1: Operation completed successfully.
    [11/13/2018, 10:04:03 AM] [INFO] C28xx_CPU1: GEL Output: Memory Map Initialization Complete
    [11/13/2018, 10:04:46 AM] [SUCCESS] Program Load completed successfully.
    [11/13/2018, 10:04:55 AM] [INFO] C28xx_CPU1: GEL Output: Memory Map Initialization Complete
    [11/13/2018, 10:04:56 AM] [ERROR] C28xx_CPU1: File Loader: Verification failed: Memory map prevented reading 0x78010@Program

    Why is this? Kindly advise.

    Thanks,

    Nestor

  • 0 in reply to Nestor Estrada
    TI__Guru**** 472291 points

    Nestor Estrada said:
    I now pressed the "Verify Images" button and it failed. Same failure mode as in the batch file.

    I expected this. The GUI did not automatically do the verification while from the command-line it did.

    Hence there is no real discrepancy between GUI and CLI.

    Hence my prior comment:

    "verification is failing at address 0x78010@Program. Please check that this valid (or not)." 

    Looking at the default cmd file for f28377s, code is usually not allocated at this address. Again, is the address valid for program memory?

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 80 points
    Hello Ki,
    I will discuss this with the firmware engineer. But I need to clear things first.
    If I understand it right I am able to flash the two separate hex file's in my cmd cli. And it is in the verification that it fails. So the question that I should be asking the fw engr is where is the exact start program memory location address? Surely it is not at 0x78010 as you mentioned.

    Ki, when he gives it, where will I place that value setting in the Uniflash GUI and what CLI command to use so I can incorporate it in dslite.bat?

    Thanks in advance.
    Nestor
  • 0 in reply to Nestor Estrada
    TI__Guru**** 472291 points

    Nestor Estrada said:
    If I understand it right I am able to flash the two separate hex file's in my cmd cli. And it is in the verification that it fails

    You can flash two separate hex files, yes. But in your case, one of them did not flash correctly. Hence the verification failed.

    Nestor Estrada said:
    So the question that I should be asking the fw engr is where is the exact start program memory location address? Surely it is not at 0x78010 as you mentioned.

    Again, I am not a device expert so I can't say definitely one way or another if that address is valid or not.

    Nestor Estrada said:
    Ki, when he gives it, where will I place that value setting in the Uniflash GUI and what CLI command to use so I can incorporate it in dslite.bat?

    You need to check the linker command file used to build the project.

    Thanks

    ki

  • 0 in reply to Ki
    TI__Guru**** 472291 points
    Hello,
    I haven’t heard back from you, hence this issue is being closed. If you wish to continue the discussion, please post a reply with an update below (or create a new thread).

    Thanks,
    ki