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/TMS320F28379D: Flashing with CCS works, but not with Uniflash

Part Number: TMS320F28379D
Other Parts Discussed in Thread: UNIFLASH, TMDSCNCD28379D

Tool/software: Code Composer Studio

Hello,

I hava a problem with flashing the F28379D with Uniflash.

If I flash with CCS version 7.3.0.00019  and debugprobe XDS110 it works fine.

I can flash and debug.

But if I want to flash with Uniflash version 4.2.1.1562 the program will transmitted succesfully to the µC but do not work.

And if I click Verify Image I get this error:

[ERROR] C28xx_CPU1: File Loader: Verification failed: Values at address 0x80000@Program do not match Please verify target memory and memory map.

I tried it with a .hex file and with a .out file of my program.

Have I to change some options in CCS to prepare my program for Uniflash or have I to change some special options (moreover selecting F28379D) in Uniflash?

best regards

Julian

  • Julian,

    This query will be answered when the expert is available next week. Thanks.
  • Julian,

    What is the output you get in the UniFlash console when you load your program?

    Also, is it possible for you to share the program you are loading? I wanted to see if I can reproduce the problem on my end.

    Thanks,
    Ricky
  • Hi Ricky,

    unfortunatelly I can't share my program, but I tried  it also with the example "blinky_cpu01" from Control Suite and have the same problem.

    But now I know that "Verify Image" just work, if the program is loaded to cpu. And now program load is successful and verify is successful too.

    After reset or restart (power off/on) the verify is sucessful too. I think that means that to program is still at the flash memory.

    As already said at the moment I test with the blinky example. I compile it with CCS and trasnfer it with Uniflash to the TMDSCNCD28379D

    evaluationboard/controlcard. That all works fine, but the program not work at the board (in CCS debugging mode the progam works fine on the board).

    I attached logfile, console screenshort, compiled blinky file and Uniflash config file for f28379D.

    regards,

    Julain

    7853.files.zip

  • Julian,

    To clarify, your original message mentioned that you were getting verification errors in UniFlash, but your last message mentioned that verify is working. Can you clarify if you are getting verification errors or not right now?

    You also mentioned that for UniFlash, the program is not running correctly after program load, but is in CCS. Is this correct?

    The difference between CCS and UniFlash is that in CCS debug, it will load the program, set a breakpoint and run to main. At that time, you can debug your application as needed. For UniFlash, it will load the program, and run the target (default behaviour, you can turn off "run after program load" in the settings), and then disconnect. Is this the part that is not working, or are you power cycling your device after you load your program in UniFlash, and it is not running after power cycling?

    Thanks,
    Ricky
  • Hi Ricky,

    i have done some tests and the state is as follows:

    - the issue that the program didn't start after flashing, was a circuit problem at the evaluationboard/circuit,

     which I unfortunatelly caused by myself

    - the uniflash tool now  flash fine and the program works after flashing

    - if I click verify image after flashing, I get mostly the following verification error:

    It's not fine, but I think there is no problem with the flashingprocess, because the programm works fine after flashing.

    regards,

    Julian

  • Julian,

    It's good to hear that your program is running fine. It's weird that you are getting a verification error though. It's difficult to figure out what the issue is without access to your program. If you are interested in looking at this further, one suggestion I have is to look at the memory at 0x82330 (using the UniFlash or CCS memory view) and see if the data looks suspicious.

    Thanks,
    Ricky