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

TMS320F2800157: Uniflash Issue

Blake Carpenter
Expert 7085 points
Part Number: TMS320F2800157
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Hi Support, 

Let me know if you want me to repost in tools.

Assigned Focus Customer writes:

I have a Uniflash issue. I have checked the forums, no one has asked this. We are in production of the F28027 using Uniflash command line interface to program the chip. Our code space is so tight that we have to program a special Test code to calibrate with, a special tester code to run full power with, and then the production code. 

My issue is every time I call the Uniflash DSLite it spends 10 seconds running initialization scripts for 10 seconds. If I were to do this from the GUI it would only run the initialization once when I open the session. Is there a way to open the session and leave it open to speed up this process. 10 seconds per call would save 30 seconds a board and get me an extra 1000 units through my tester a month.

Thanks!

Blake

  • 0
    TI__Guru**** 474421 points

    Hello Blake,

    Blake Carpenter said:
    My issue is every time I call the Uniflash DSLite it spends 10 seconds running initialization scripts for 10 seconds.

    How are they calling dslite to program the three files? It sounds like they are calling dslite three separate times (once for each program) instead of calling dslite once and then specifying the three file to program?

    ki

  • 0 in reply to Ki
    TI__Expert 7085 points

    Hi Ki,

    Thanks for the note.

    The customer writes:

    That would work if we were programming three things at the same time.
    We are programming Test code, running some tests, programming a different test code, running calibration and pushing those values to EEPROM, Then programming a 3rd time with production code. The time needed between programs is 1 min in the first program to second. And then about 2 and a half minutes  to the third.
     
    Each time dslite is called it re initializes the jtag programmer. But in the uniflash app, it initializes only once in the “session”. If I keep the uniflash app open and even change the hex file to be programmed, as long as I don’t reinitialize the session it saves 10 seconds.
    -------------
    Best Regards,
    Blake
  • 0 in reply to Blake Carpenter
    TI__Guru**** 474421 points

    Ok, I get it now.

    I'm not sure he can use dslite (UniFlash CLI). I would recommend a DSS script. Their DSS script would launch a debug session and do all the actions required in one debug server instance.

    CCS comes with DSS. So does UniFlash. However, DSS requires a JRE and while CCS comes with one, DSS does not. So the customer would need an installation of a JRE if they only wish to have an installation of UniFlash.