• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 2 answers
  • Subscribers 29 subscribers
  • Views 710 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

UNIFLASH: Arch Linux + UniFlash + CC3220S flash problems

Youri Klaassens
Prodigy 110 points
Part Number: UNIFLASH
Other Parts Discussed in Thread: CC3220S, , CCSTUDIO, CC3200

Dear E2E community,

I recently ordered the TI SimpleLink CC3220S and I wanted to program and flash it. When I try to read the memory using dslite command line utility it says that there are errors setting up an connection. I changed the permissions of /dev/ttyACM0 wihout success.

I tried the graphical UniFlash aswell but it keeps stuck after I pressed "start". It could recognize that the connected device is an CS3220S tho, whih is remarkable because some communication must have taken place to detect that.

Here are my udev rules

And just to show as a prove, this is when I execute detect-device.sh

Does anyone have a clue why reading memory or flashing memory does not work?

With kind regards,

Xhendos.

  • 0
    TI__Guru**** 168207 points

    Xhendos,

    Error 2083 is shown in the Debugging JTAG page below (just search for the error number)

    https://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html 

    That said, this code is related to XDS200/XDS560v2 and not XDS110, which is the Debug Probe used by the Launchpad. Are you sure the .ccxml is properly configured?

    To double-check this, issue the command below and see if the probe responds with the proper integrity tests:

    [user@host ~]$ cd ~/ti/uniflash_5.1.0/deskdb/content/TICloudAgent/linux/ccs_base/common/uscif
    [user@host uscif]$ ./dbgjtag -f @xds110 -rv -S pathlength -S integrity

    This should return a proper connection to the launchpad. 

    A few things worth of notice:

    - The CC3200S does not have internal Flash. You will have to use the Image Creator via Serial (UART) communications to store your code on the board.
    - Uniflash does not officially support Arch Linux, but hopefully this should work fine.  

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Prodigy 110 points 

    -----[Print the board config pathname(s)]------------------------------------

xds110.i

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'libjioxds110.so'.
The library build date was 'Jan 24 2019'.
The library build time was '14:17:55'.
The library package version is '8.0.903.6'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '5' (0x00000005).
The controller has an insertion length of '0' (0x00000000).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.

-----[Print the reset-command hardware log-file]-----------------------------

The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the XDS110 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for XDS110 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).

-----[Perform the standard path-length test on the JTAG IR and DR]-----------

This path-length test uses blocks of 64 32-bit words.

The test for the JTAG IR instruction path-length succeeded.
The JTAG IR instruction path-length is 6 bits.

The test for the JTAG DR bypass path-length succeeded.
The JTAG DR bypass path-length is 1 bits.

-----[Perform the Integrity scan-test on the JTAG IR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG IR Integrity scan-test has succeeded.

-----[Perform the Integrity scan-test on the JTAG DR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG DR Integrity scan-test has succeeded.

    Above you can find the result of the dbgjtag. Everything seems fine on that side. I used to try it using the Onboard Debug Probe before which caused the connection issues (this is the .ccxml file)

    Whenever I try to switch the connection to UARTconnection I get the following error from ccstudio

    Is there any download place I can get the device driver for a uart connection?

    With kind regards,

    Xhendos.

  • 0 in reply to Youri Klaassens
    TI__Guru**** 168207 points

    Xhendos, 

    Sorry about the delay; are you still having this issue?

    As I mentioend earlier, the Test Connection is correctly identified with a XDS110 Debug Probe (part of the Launchpad). However, your first screenshot above shows a Texas Instruments XDS2xx USB Onboard debug probe, which is not the correct one. Can you select the Texas Instruments XDS110 USB debug probe and try to connect? Also, the device you are typing is CC3200 and not CC3220.

    The UART connection is expected, as it is not suitable for this target. 

    Hope this helps,

    Rafael