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

CCS/RM57L843: Uniflash Standalone command line with Daisy Chain

Holly Gu
Intellectual 2750 points

Part Number: RM57L843
Other Parts Discussed in Thread: UNIFLASH

Tool/software: Code Composer Studio

Hi team,

    There’re two RM57L843 in customer’s boards, RM57L843_CPU and RM57L843 _DSP, they use JTAG as Daisy chain and want to download FW using Uniflash command line. But when they run dslite.bat, only RM57L843_CPU can be download FW correctly, RM57L843_DSP one doesn’t work.Uniflash version is 4.2.0.1435, Emulator is XDS200.

1. Customer was able to down load FW correcly to RM57L843_CPU and RM57L843 _DSP separately under CCS environment. Meanwhile, by generating two uniflash sessions using RM57L8xx_cpu.ccxml and RM57L8xx_dsp.ccxml, FW can also be downloaded correctly using Program->Load Image with Uniflash, that’s why I think the daisy chain HW and both .ccxml files are correct.

2. We generate packages using stand alone command line in Uniflash, but if run the .bat files, the problems turns up. Although I run two different dslite.bat under separate folders, both FW was downloaded to the CPU board, not the DSP one. Even the erase, also execute in CPU board. I don’t know why.

 

I put related files may needed as attached.

1) Bat_CPU_Log & Bat_CPU_Log are captured from dos when run .bat.

2) RM57L8xx_cpu.ccxml & RM57L8xx_dsp.ccxml

3) Also two sessions rm57l8xx_cpu.uniflash & rm57l8xx_dsp.uniflash


I think it is a issue with Uniflash, does run .bat really support daisy chain? How to solve it?




  • 0
    TI__Genius 13245 points
    Holly,

    I don't see an attachment in your post; can you try attaching it again?

    Also, to clarify, did you mean that the customer was able to program the RM57L843_DSP with the UniFlash GUI, but was not able to program it via the command line? And when running the command line, it was programming the RM57L843_CPU instead?

    Thanks,
    Ricky
  • 0 in reply to Ricky Lau
    TI__Intellectual 2750 points

    Hi Ricky,

        Try to attach again.Sessions.zip

        Yes, I did several round of tests, and quite sure it is CORRECT when program by use UniFlash GUI, as below. Both CPU and DSP can be programmed correctly.

       

     But when running the command line, it was programming the RM57L843_CPU instead.

        

  • 0 in reply to Holly Gu
    TI__Genius 13245 points
    Holly,

    Looking at the files you attached, I'm actually a little confused on how RM57L8xx_dsp.ccxml is able to talk to the DSP core using the GUI. The only different between RM57L8xx_cpu.ccxml and RM57L8xx_dsp.ccxml seems to be the order of the 2 cores, and unless you are changing the order of the daisy chain, I would have expected that it would always talk to the first core in the chain.

    As for the DSLite command line, you should be able to talk to both cores using the same package. Let's take the package you generate using RM57L8xx_cpu.ccxml. The default command will talk to the first core. But there is a command line parameter for you to specify another core to talk to; specifically the -n option, which takes an index to the core you want to talk to (defaults to 0, which is probably why it always talks to the CPU core).

    Can you try the following command:
    > dslite -c <pathToYourCCXML> -n 1 -e -f -v <pathToProgram>

    Please let me know if this works for you.

    Thanks,
    Ricky
  • 0 in reply to Ricky Lau
    TI__Intellectual 2750 points
    Hi Ricky,

    Thanks for your suggstions, with adding -n, we were able to download FW to the DSP core. Now both CPU and DSP can be downloaded with .bat successfully.

    I plan to write a appnote to share how to use Daisy chain with Uniflash :)