• State Resolved
  • Locked Locked
  • Replies 15 replies
  • Subscribers 54 subscribers
  • Views 6344 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/TMS320F28375D: Running UniFlash in Ubuntu 14.04, no XDS200 auto connection, and errors when trying to flash

Jerry Morrow
Prodigy 140 points
Part Number: TMS320F28375D
Other Parts Discussed in Thread: UNIFLASH,

Tool/software: Code Composer Studio

Hello,

Some system info first:

1. Ubuntu 14.04
2. Run UniFlash with sudo privileges

When I do lsusb, the debugger is there. 

Bus 002 Device 011: ID 0451:bef0 Texas Instruments, Inc.

Here's the commands I used to install UniFlash:

wget http://software-dl.ti.com/ccs/esd/uniflash/uniflash_sl.4.2.1435.run

sudo ln -sf /lib/x86_64-linux-gnu/libudev.so.1 /lib/x86_64-linux-gnu/libudev.so.0

chmod 776 uniflash_sl.4.2.1435.run

sudo ./uniflash_sl.4.2.1435.run
Installed to /opt/ti/uniflash_4.2
When I run UniFlash (the GUI looks nice!), it doesn't auto detect my JTAG xds200 probe.
Then, when trying to load image (after selecting right probe and processor), I get some error messages that I don't understand.
It gets past the ICE_Pick, but then on CPU2_CLA1, errors out.
[7/31/2017, 11:32:37 AM] [INFO] C28xx_CPU2: GEL Output: Memory Map Initialization Complete
[7/31/2017, 11:32:37 AM] [INFO] C28xx_CPU1: GEL Output: Memory Map Initialization Complete
[7/31/2017, 11:32:37 AM] [INFO] C28xx_CPU2: If erase/program (E/P) operation is being done on one core, the other core should not execute from shared-RAM (SR) as they are used for the E/P code. Also, CPU1 will be halted to determine SR ownership for the CPU which will run the Flash Plugin code, after which CPU1 will be set to run its application. User code execution from SR could commence after both flash banks are programmed.
[7/31/2017, 11:32:37 AM] [INFO] C28xx_CPU1: If erase/program (E/P) operation is being done on one core, the other core should not execute from shared-RAM (SR) as they are used for the E/P code. Also, CPU1 will be halted to determine SR ownership for the CPU which will run the Flash Plugin code, after which CPU1 will be set to run its application. User code execution from SR could commence after both flash banks are programmed.
 
Any info helpful.
thanks
Jerry
Chicago
 

 

  • 0
    TI__Guru**** 171094 points
    Jerry,

    Apart from the auto-detect glitch, the other informational messages are common to all F28x dual core devices (they can also be seen from CCS when launching a debug session) and provide warnings for the flash programming operation.

    They can be safely ignored if you are not relying on the scenarios shown on the message.

    Hope this helps,
    Rafael
  • 0 in reply to desouza
    Prodigy 140 points
    OK, but we still get a big red ERROR box, regardless of the warnings. We don't see it even attempt to program.
  • 0 in reply to Jerry Morrow
    TI__Guru**** 171094 points
    Jerry,

    Can you post a screenshot of the error box? The message you sent does not contain any errors, only informational messages.

    Regards,
    Rafael
  • 0 in reply to desouza
    Prodigy 140 points

    On a related note, we had another coworker try UniFlash 4.0 and 4.2 on his Window machine.  It did get through the erase operation, but failed part way through the program operation.  

  • 0 in reply to Jerry Morrow
    TI__Genius 13095 points
    Jerry,

    1) On Auto-Detection, we don't currently support detecting XDS200 right now. We only support XDS110 Debug Probe, and the following list of LaunchPads (processors.wiki.ti.com/.../CCS_UniFlash_v4.2.0_Release_Notes

    2) On the case where you are getting the error box, can you try generating the Debug Server logs?

    You can do this in UniFlash by:
    1) Configuring your device
    2) Go to the Settings menu (top-right corner)
    3) Go to the 'Debug Server Logging' section and click on Enable (note the location where the log is generated)
    4) Try loading your program now
    5) After getting the error dialog, disable logging and browse to the location of the log

    Attach the generated log and I can analyze it to try to figure out the cause of the error.

    Thanks,
    Ricky
  • 0 in reply to Ricky Lau
    Prodigy 140 points

    3513.ds.log

    Hello,

    A couple of notes. 

    I have less error messages on my linux console when I start UniFlash with sudo.  It is able to autodetect.

    We were able to test the JTAG connection to TMS320 today using CCS 7 on the same machine. 

    When we tried to load the debugger with CCS (which in turn flashes the device), it crashed the application quickly.

    thanks

    Jerry

  • 0 in reply to Jerry Morrow
    Prodigy 140 points

    DevTest.zipAlso, here's the .out file (coff?) we're trying to program.  IT is NOT a zip file, i had to change the extension from .out to .zip to get this website to accept the upload.  Change back to .out if you download.

  • 0 in reply to Jerry Morrow
    TI__Genius 13095 points
    Jerry,

    Thank you for provide this information. I started looking at this and I seem to be able to reproduce the issue. I will be looking at the cause of the problem and providing a fix for this as soon as possible.

    As a workaround, we recommend that you rollback to use an older version of UniFlash (4.1.2 or older), as I do not see the red error box when using TMS320F28375D with older UniFlash builds.

    Thanks,
    Ricky
  • 0 in reply to Ricky Lau
    Prodigy 140 points
    thanks for looking into this, i'll try with 4.1.2
  • 0 in reply to Jerry Morrow
    Prodigy 140 points
    Hello, different error with 4.1.2:

    Executing startup scripts: CPU2_CLA1 (not sure why doing anything with CPU2 ..)

    Error! undefined is not a function
  • 0 in reply to Jerry Morrow
    Prodigy 140 points
    Also, i have to start application as sudo to get it to work at all.
  • 0 in reply to Jerry Morrow
    TI__Genius 13095 points
    Jerry,

    I'm sorry that my suggested workaround did not work; it looks like there might be a bug with previous builds as well. The only other workaround I can suggest right now is to use the command line interface instead of the GUI to program your device.

    You get either use the command line (dslite.sh) that comes with UniFlash (located in the install directory), or generate a standalone command line package using the UniFlash GUI (by going to the "Standalone Command Line" tab). Please let me know if you need more information on this.

    Also, to update you on the original error. We were able to identify the problem and have implemented a fix. We are looking at releasing a fix next week (aiming for Tuesday if no issues comes up).

    Thanks,
    Ricky
  • 0 in reply to Ricky Lau
    Prodigy 140 points

    Hello,

    Using the dslite shell script worked, thank you!  I actually prefer command line anyway, in general.    

    Note, looks like dslite.sh wasn't in the UniFlash 4.2 package?

    Here was my Ubuntu linux command:

    /opt/ti/uniflash_4.1/dslite.sh -c <path>/TMS320F28375D.ccxml -f -e <coff image file>.out

    I didn't need to use sudo, either!

    thanks

    Jerry

  • 0 in reply to Jerry Morrow
    TI__Genius 13095 points
    Jerry,

    Glad to hear that you have a workaround that is working for you.

    Are you saying that dslite.sh is not available on your UniFlash 4.2 install? I'm looking at my installation folder, and I can see dslite.sh in mine.

    Thanks,
    Ricky
  • 0 in reply to Ricky Lau
    TI__Genius 13095 points
    Note that the latest UniFlash update (v4.2.0.1490) is now available. This should fix the original issue you were seeing with the error box.

    Thanks.