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.

TMS320F2809: Memory export on Uniflash v3.4.1

Part Number: TMS320F2809
Other Parts Discussed in Thread: UNIFLASH, TMS320F28035

Dear Champs,

I am asking this for our customer.

The user downloaded Uniflash V3.4.1 on

http://www.ti.com/tool/UNIFLASH?keyMatch=UNIFLASH&tisearch=Search-EN-everything&usecase=part-number

The user wanted to export memory content and configured like below

Start Address = 0x3D8000,Length words = 0x1FFFF

But the result were all 0.

Questions:

1. They use XDS510LC USB. Can Uniflash V.3.4.1 supports Spectrum Digital XDS510USB?

From 

https://processors.wiki.ti.com/index.php/CCS_UniFlash_v3.4.1_Release_Notes#List_of_Communication_Interface_.28Emulator.29_Support

It is not very clear if XDS510LC USB is supported or not, but the option in the Uniflash does have XDS510 USB.

2. Do you think if there is anything wrong with their setting? Is there any doc to show them how to use memory export on Uniflash V3.4.1?

PS. They have only XDS510LC USB now, and their WIndows is Windows 10.

Wayne Huang

  • Wayne Huang said:

    1. They use XDS510LC USB. Can Uniflash V.3.4.1 supports Spectrum Digital XDS510USB?

    From 

    https://processors.wiki.ti.com/index.php/CCS_UniFlash_v3.4.1_Release_Notes#List_of_Communication_Interface_.28Emulator.29_Support

    It is not very clear if XDS510LC USB is supported or not, but the option in the Uniflash does have XDS510 USB.

    There should be an option for XDS510LC also:

    Wayne Huang said:
    2. Do you think if there is anything wrong with their setting? Is there any doc to show them how to use memory export on Uniflash V3.4.1?

    Wayne Huang said:
    But the result were all 0.

    It sounds like the flash may be protected/locked. Can the customer confirm that it is readable? Can they read the contents and export fine using CCS IDE?

    Thanks

    ki

  • Dear Ki,

    Yes, the user could use CCS 5.2.0.00069 for memory export, but we are still confused why the user could not use Uniflash_3.4.1.00012 for memory export. 

    They were suspecting the CSM, and tried not to use any CSM (leaving it as default all 0xFFFF), but they still failed on Uniflash_3.4.1.00012.

    If they want to try with newer Uniflash with XDS510LC support, which version do you suggest?

    BTW, should they use the Wordsize on the flash export of Uniflash as 8-bit or 16-bit? Or it does not matter? 

    Wayne Huang

  • Wayne Huang said:
    If they want to try with newer Uniflash with XDS510LC support, which version do you suggest?

    3.4.1 is the last UniFlash version to support XDS510. If they customer wishes to use that debug probe, they need to stick to this old version of UniFlash.

    Wayne Huang said:
    BTW, should they use the Wordsize on the flash export of Uniflash as 8-bit or 16-bit? Or it does not matter? 

    The word size will make a difference in how the data is formatted. But assuming the contents of memory being exported is not all 0, the contents of the exported data should have some non 0 data. Can the customer try a binary export?

    Thanks

    ki

  • Dear Ki,

    Now, the user can export the memory on CCS no matter it's locked or not.

    And when they use a device without locking on Uniflash V3.4.1, they can export it, too.

    But when they use a device with CSM locking on Uniflash V3.4.1, they still have this issue.

    It seems there is something wrong during their unlocking....

    Do you have any doc to detail how to unlock with Uniflash?

    It's better if the doc is directly related to Uniflash V3.4.1.

    Wayne Huang 

  • Hi Wayne,

    The Flash options in the UniFlash 3.4.1 GUI should mimic what is seen when using CCS. Are the same steps being followed between the two GUIs but only the CCS option works?

    ki

  • Dear Ki,

    Note that the user can use CCS 5.2 to unlock the device and export the memory.

    The use can also use Uniflash V3.4.1 to unlock the device and then erase and program the flash and export the memory.

    (If they do not successfully unlock the device, they should not be able to erase the flash, right?)

    They just cannot use Uniflash V3.4.1 to export the memory with unlocking it first.

    It sounds there is a bug on Uniflash V3.4.1 to export the memory after trying to unlock it.

    Do you think so?

    The reason they have to use Uniflash V3.4.1 is that they have bought several XDS510 before and want to use them.

    Do you have any other suggestion for them?

    Wayne Huang

  • Hi Wayne,

    Thanks for the additional information. I believe I understand what the issue is. Basically there is a known issue with UniFlash where it auto-disconnects after each flash operation. Hence what is happening is that after the unlock, UniFlash disconnects. Then when the export is attempted, UniFlash reconnects but the device is locked again. See the related post below:

    https://e2e.ti.com/support/tools/ccs/f/81/p/592733/2180041#2180041

    For UniFlash v4 and greater, there is a workaround as described in the post above. That workaround does not exist in UniFlash v3 unfortunately. 

    The only way to unlock and export with UniFlash 3 is to use the command-line interface and have both operations on the same command like the below example:

    > uniflash -log myLog.xml -ccxml ../configs/TMS320F28035.ccxml -setOptions FlashKey0=AAAA FlashKey1=BBBB -operation Unlock Erase -program ../programs/F28035_Prog1.out ../programs/F28035_Prog2.out ../programs/F28035_Prog3.out -operation "CalculateChecksum" -export COFF 0x3E8000 0xC000 ../programs/export2.out

    There is no way to set this up in the UniFlash v3 GUI

    ki