TMS320F28377D: Mass-production programming using Uniflash GUI or CLI.

Hideaki Nambu

Part Number: TMS320F28377D
Other Parts Discussed in Thread: UNIFLASH, C2000-GANG

Hello,
My customer is trying to build a mass production equipment based on Uniflash.
They prefer GUI to CLI if the GUI could satisfy them.

*[GUI] Is it possibe to satisfy the following two requirements?

1) Switch the JTAG cable to a new board, and just press "CPU2" Verify image, without the uniflash restart.
     I'm afraid this is not possible now. e2e.ti.com/.../665574

2) Switch the JTAG cable to a new board, and just press "CPU2" Program image, without the uniflash restart.
     I'm afraid there are no configurations which satisfies both 1) and 2) at the same time.

*[CLI] I think Uniflash CLI can't program CPU2 flash now. Is it correct?

If CLI programs&verifies the CPU2, I would like to suggest CLI to my customer.

* Please assume Windows platform.

over 7 years ago

0 Vamsi Gudivada over 7 years ago

TI__Guru* 87145 points

Hideaki-san,

GUI:

#1. You are correct that standalone verify is not possible.

#2. I need to check on program option with JTAG cable switch.

CLI:

I will ask our tool expert to reply on this.

Thanks and regards,
Vamsi

0 Ricky Lau over 7 years ago in reply to Vamsi Gudivada

TI__Genius 13095 points

Hideaki,

For GUI, if the "remain connected" option is off, you should be able to switch between devices without restarting UniFlash, as long as the device and connection type is the same. Are you seeing an error when doing this?

For GUI verify, there is an issue with verifying CPU2 in the current version of UniFlash, which will be addressed in UniFlash 4.5 coming out around 2 weeks. But it only works for devices without a password programmed. As noted by Vamsi, we still have an issue with devices that have password programmed using the standalone verification.

For CLI, we have an issue with accessing CPU2. This is because for these devices, CPU1 needs to be connected as well to access CPU2, but there is no way to tell UniFlash CLI to do this. We are looking at possible workarounds for UniFlash 4.5 as well.

Thanks,
Ricky

0 Hideaki Nambu over 7 years ago in reply to Ricky Lau

Mastermind 9165 points

Vamsi and Ricky,
Thank you for your responses.
Please let me reconfirm my understandings:

Q.
Uniflash450 GUI will not support "my customer requirement (1)", if the newly attached TGT device is password-protected.
Is it correct?

Q.
Uniflash450 CLI will not support CPU2. Although a workaround will be investigated.
Is it correct?

Q.
Uniflash450 will support my customer requirements (1) and (2) under the same configuration.
Is it correct?

Q.
C2000-GANG will support both of them now.
Is it correct?
This is a new question.

0 Ricky Lau over 7 years ago in reply to Hideaki Nambu

TI__Genius 13095 points

1. For password protected devices, customer will have to manually unlock it (clicking the Unlock button) and then doing a verify. This is assuming the "Remain connected" option is on, and no other steps is locking the device between unlock and verify (ie; do not perform a reset).

2. From my understanding, we are working on a workaround that applies to the generated CLI package feature (the one you generate from "Standalone Command Line" view in the GUI) that will automatically connect to CPU1 as well. The command line that comes with UniFlash install (dslite.bat) will not have this workaround. So if customer is ok with generating the CLI package from the GUI, CPU2 should work for their case.

3. Yes, if device is disconnected, you should be able to switch out the device without restarting UnIFlash.

4. I don't have any info on C2000-GANG (maybe Vamsi has?), but another solution that will satisfy all the customer's requirement is Debug Server Scripting (DSS), which can be added to UniFlash.

More information here:

http://processors.wiki.ti.com/index.php/Debug_Server_Scripting

http://processors.wiki.ti.com/index.php/UniFlashv4_DSS

I can provide more information if you are interested in this solution.

Thanks,

Ricky