CCS/IWR6843ISK: IWR6843 3D debug mode

gil albo

Intellectual 725 points

Part Number: IWR6843ISK
Other Parts Discussed in Thread: IWR6843, UNIFLASH, AWR1443, , MMWAVE-SDK

Tool/software: Code Composer Studio

Hi,

I have the IWR6843 board, and i want to use it with mmwave industrial toolbox 3_3_1 lab 20.

At the past i used to use debug mode at previous board of the mmwave.

I experience difficulties when trying to use lab20 at the mentioned toolbox at debug mode.

The lab20 has two sub projects.,both passed compilation.

In order to deal at debug mode,i did the following:

1.load jumper on SOP2

2.connect uniflash

3.power cycle of the board

4.start burning the C:\ti\mmwave_sdk_03_01_01_02\packages\ti\utils\ccsdebug\xwr68xx_ccsdebug.bin

5.it passed successfully->removing the jumper from the SOP2

6.CCS->compiling the projects DSS MSS->successfully

7.creating target configuration file->load the resulting file->gather files to group->connect to target

8,when connecting to target ,the CCS gets stuck.

I've attached the relevant screenshots.

Please assist.

over 5 years ago

0 Akash Gondalia over 5 years ago

TI__Guru 50240 points

Hi Gil,

Can you confirm you have power cycled your board after flashing your board and removing the SOP2 jumper?

Cheers,
Akash

0 gil albo over 5 years ago in reply to Akash Gondalia

Intellectual 725 points

Hi Akash,
I confirm i did it.
tries this scenario three times.
Gil

0 Akash Gondalia over 4 years ago in reply to gil albo

TI__Guru 50240 points

Hi Gil,

It appears your Target Config File (.ccxml) is for AWR1443, make sure you select IWR6843 for this.

Cheers,
Akash

0 gil albo over 4 years ago in reply to Akash Gondalia

Intellectual 725 points

Hi Akash.
I've verified that the target configuration file is for IWR6843.
The image shows the mouse somehow in focus on the AWR1443, but only the IWR6843 is checked.
please assist.

0 Akash Gondalia over 4 years ago in reply to gil albo

TI__Guru 50240 points

Hi Gil,

When you say it is getting stuck, do you mean it is not loading an executable or that it requires an update or something else? Would you be able to post a screenshot of the actual error?

Cheers,
Akash

0 gil albo over 4 years ago in reply to Akash Gondalia

Intellectual 725 points

Hi Akash,

All the pictures that i've attached above show the situation.

anyway,

here are the messages again:

I'm using the IWR6843ISK with lab20 which from the mmwave toolbox 3_3_1

i have the latest mmwave SDK mmwave_sdk_03_01_01_02

the projects MSS and DSS passed compilation.

I've flashed the ccsdebug of the IWR6843 successfully and removed the SOP2 jumper afterwards.

created new target configuration file when selecting only the IWR6843 and XDS110 USB debug mode.

I've saved this ccxml file.

then clicked on the test connection button ,and the result is:

[Start: Texas Instruments XDS110 USB Debug Probe]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]

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

C:\Users\GIL~1.ALB\AppData\Local\TEXASI~1\

CCS\ti\1\0\BrdDat\testBoard.dat

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

This utility has selected a 100- or 510-class product.

This utility will load the adapter 'jioxds110.dll'.

The library build date was 'Jan 24 2019'.

The library build time was '14:27:46'.

The library package version is '8.0.903.6'.

The library component version is '35.35.0.0'.

//////////////////////////////////////////////////////////

Then ,I launched that target file ccxml and grouped the two

then , a message appear:

when clicking updated, the device is stuck forever.

Please assist.

Gil

0 Akash Gondalia over 4 years ago in reply to gil albo

TI__Guru 50240 points

Hi Gil,

Does your "Test Connection" Report have any more information? You may just have a bad USB cable.

Have you been able to run other demos and labs previously?

Cheers,
Akash

0 Akash Gondalia over 4 years ago in reply to Akash Gondalia

TI__Guru 50240 points

Hi Gil,

Since we haven't heard from you I'm going to close this thread but if you still have questions then feel free to open up a new one!

Cheers,
Akash

0 gil albo over 4 years ago in reply to Akash Gondalia

Intellectual 725 points

Hi Akash.
How are you ?
The problem wasn't solved.
I was provided with new IWR6843 board.
I successfully flashed the device with two bin files(one per trial).
one provided with lab20, and another that i generated from my lab20 project.
in both cases, the GUI was functioning well.

But when trying to debug, the issues mentioned above remained.
i did update to the ccs.
i used another usb cable.
i used new project ,importing lab 20.

directions ?

0 Akash Gondalia over 4 years ago in reply to gil albo

TI__Guru 50240 points

Hi Gil,

Can you try this on a different PC?

This is different from what you had first said, you will need to flash the CCS Debug Firmware in order to debug this on CCS.

Have you tried running the board with any of the prebuilt binaries included in either the mmWave-SDK (recommended starting point) or the Industrial Toolbox?

Cheers,
Akash

0 gil albo over 4 years ago in reply to Akash Gondalia

Intellectual 725 points

Hi Akash,
i dont have the resources to check on another pc.
few months ago, i've worked with the 2Tx isk board for people counting and other labs, and it was good at debug mode.
Can you check on the IWR6843ODS-ISK board with the lab20, if it's possible to work on debug mode ?
BR
Gil

0 Justin Curewitz over 4 years ago in reply to gil albo

TI__Mastermind 28055 points

Hi Gil,

From your last screenshot, you need to update the debug probe. Have you done that? (Click update in the prompt).

Regards,
Justin

0 gil albo over 4 years ago in reply to Justin Curewitz

Intellectual 725 points

Hi Justin.
I did the update stage and while doing this, the CCS got stuck.
I did it several times, and also on the previous IWR6843ISK board .
Also, i checked for updates for the CCS.
The cable is new and arrived at the package of the module.

Can you verify whether the debug mode is functioning at the IWR6843 ?
Thank you
Gil

0 Justin Curewitz over 4 years ago in reply to gil albo

TI__Mastermind 28055 points

Hi Gil,

I can confirm that debug mode works with CCS - I have used it myself yesterday. However, I am using CCS 8.3 - Please check your version by clicking "Help->About Code Composer Studio" in the top left.

Please check some of the hardware settings on the board:
Following the People Counting user's guide, ensure the device is in functional mode. Check both the SOP pins and the Switches.

Regards,
Justin

0 gil albo over 4 years ago in reply to Justin Curewitz

Intellectual 725 points

Hi Justin,
i have the Version: 8.3.0.201810301800
I've followed the instructions as described in the manual, and still it gets stuck .
I'll try again.

Gil

0 Ki over 4 years ago in reply to gil albo

TI__Guru**** 420630 points

Gil,
Please run the JTAG connectivity test and post the results:
dev.ti.com/.../node

Thanks
ki

0 gil albo over 4 years ago in reply to Ki

Intellectual 725 points

Hi Ki-Soo,

I did the Jtag test many times,

0.I'm using the IWR6843ODS-ISK board with XDS110 usb debug mode.

The SDK used is 3_1_1_2

The CCS is Code Composer Studio, Version: 8.3.0.201810301800 ,Build id: N201810301800

1.I've loaded the C:\ti\mmwave_sdk_03_01_01_02\packages\ti\utils\ccsdebug\xwr68xx_ccsdebug.bin

first connected SOP2->openend uniflash->pressed on the reset button->flashed the bin file xwr68xx_ccsdebug.bin->program load completed successfully->turn off the board power->removed the SOP2 jumper.

2.The projects (DSS & MSS of lab20 were built succussfuly)

3.I've created new target configuration file

*Connection:XDS110 usb debug mode.

*Board of device: IWR6843 (just this.I've verified no other board was checked)

*saved the configuration file

*pressed the test connection->Here's the output:

[Start: Texas Instruments XDS110 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]

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

C:\Users\GIL~1.ALB\AppData\Local\TEXASI~1\
CCS\ti\1\0\BrdDat\testBoard.dat

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

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioxds110.dll'.
The library build date was 'Jan 24 2019'.
The library build time was '14:27:46'.
The library package version is '8.0.903.6'.
The library component version is '35.35.0.0'.

Here's the ouput

[Start: Texas Instruments XDS110 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]

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

C:\Users\GIL~1.ALB\AppData\Local\TEXASI~1\
CCS\ti\1\0\BrdDat\testBoard.dat

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

4.The CCS is stuck...

5.When Flashing my device not in debug mode,the board is functioning well->Therefore the cable is ok (it also arrived from TI with the device)

Please direct me.

Gil

0 Ki over 4 years ago in reply to gil albo

TI__Guru**** 420630 points

gil albo said:

Here's the ouput

[Start: Texas Instruments XDS110 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]

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

C:\Users\GIL~1.ALB\AppData\Local\TEXASI~1\
CCS\ti\1\0\BrdDat\testBoard.dat

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

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioxds110.dll'.
The library build date was 'Jan 24 2019'.
The library build time was '14:27:46'.
The library package version is '8.0.903.6'.
The library component version is '35.35.0.0'.

4.The CCS is stuck...

There is no error message? It never returns? Are you forced to terminate the test manually?

Also, please try updating your TI emulators component to the latest version (Chec for CCS Updates)

0 gil albo over 4 years ago

Intellectual 725 points

Hi again,

This is the message.

When debugging with other type of EVM of TI (2Tx antenna board mmwave) ,the message at the test connection ended with success.

This doesn't happen here.

When checking for updates i get the messages:

Some sites could not be found. See the error log for more detail.
No repository found at file:/C:/Users/Gil.Albo/AppData/Local/Temp/traceplugin-Repo/.
No repository found at file:/C:/Users/Gil.Albo/Downloads/CCS8.2.0.00007_win32%20(1)/CCS8.2.0.00007_win32/baserepo/p2appfRepo/.

What do you recommend ?

0 Ki over 4 years ago in reply to gil albo

TI__Guru**** 420630 points

Ah, I see you are using 8.2.0. Could you try updating to 8.3.1? Or better yet, 9.0.1. I believe for the latter, you need to do a clean install of 9.0.1.

0 gil albo over 4 years ago

Intellectual 725 points

Thank you.

I'll try this.

Gil

0 gil albo over 4 years ago

Intellectual 725 points

Hi again,

I've installed ccs Version: 9.0.1.00004 .

I've imported lab20 from the mmwave toolbox.

before,I've flashed the ccsdebug bin of 6843 and removed the SOP2 jumper afterwards,

the compilation of lab20 mss and dss passed succesfuly.

Reminding: board IWR6843ODS-ISK,

mmwave sdk 3112

mmwave toolbox 331

xds100 usb debug

when testing new target configuration file ccxml was according to xds110 usb, and the required device iwr6843.

file was saved .

test connection (jtag) stucked the ccs

test connection output message:

[Start: Texas Instruments XDS110 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]

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

C:\Users\GIL~1.ALB\AppData\Local\TEXASI~1\
CCS\ccs901\0\0\BrdDat\testBoard.dat

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

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioxds110.dll'.
The library build date was 'Mar 25 2019'.
The library build time was '17:36:26'.
The library package version is '8.1.0.00007'.
The library component version is '35.35.0.0'.

didn't solve the issue.

(I repeated on the procedure twice for double check,,,)

Please assist

Gil

0 gil albo over 4 years ago

Intellectual 725 points

Hi Ki-Soo Li.

How are you?

When using the ccs 8.2

I wanted to check the connection to the mss at project build state.

This is what i got.

maybe the solution is here ?

[Start]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]

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

C:\Users\GIL~1.ALB\AppData\Local\TEXASI~1\
CCS\ti\1\0\BrdDat\testBoard.dat

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

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioxds110.dll'.
The library build date was 'Jan 24 2019'.
The library build time was '14:27:46'.
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.

An error occurred while hard opening the controller.

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-260' (0xfffffefc).
The title is 'SC_ERR_XDS110_OPEN'.

The explanation is:
An attempt to connect to the XDS110 failed.
The cause may be one or more of: no XDS110 is connected, invalid
firmware update, invalid XDS110 serial number, or faulty USB
cable. The firmware and serial number may be updated using the
xdsdfu utility found in the .../ccs_base/common/uscif/xds110
directory of your installation. View the ReadMe.txt file there
for instructions.

[End]

[Start]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]

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

C:\Users\GIL~1.ALB\AppData\Local\TEXASI~1\
CCS\ti\1\0\BrdDat\testBoard.dat

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

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioxds110.dll'.
The library build date was 'Jan 24 2019'.
The library build time was '14:27:46'.
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.

An error occurred while hard opening the controller.

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-260' (0xfffffefc).
The title is 'SC_ERR_XDS110_OPEN'.

The explanation is:
An attempt to connect to the XDS110 failed.
The cause may be one or more of: no XDS110 is connected, invalid
firmware update, invalid XDS110 serial number, or faulty USB
cable. The firmware and serial number may be updated using the
xdsdfu utility found in the .../ccs_base/common/uscif/xds110
directory of your installation. View the ReadMe.txt file there
for instructions.

[End]

0 gil albo over 4 years ago in reply to Akash Gondalia

Intellectual 725 points

Hi,
I've installed everything on another computer.
all the updated versions:
CCS 9.0.1.00004
mmwave sdk 3204
mmwave industrial toolbox 340
uniflash 5002289

I've flashed the ccsdebug of IWR6843 from the mentioned above sdk.(jumper mounted on SOP2 before->power cycle->flashing ccsdebug->success->turn on device->remove SOP2 jumper->turn on.

compiled the dss/mss projects when choosing mmwave sensors and IWR6843 device, and XDS 110 usb are chosen at the show build settings.
compiled successfuly

creating target configuration file when mmwave sensors ,IWR6843,XDS110 usb all are selected.
Then,save the target configuration file.
Then test connection->
[Start: Texas Instruments XDS110 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]

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

C:\Users\User\AppData\Local\TEXASI~1\CCS\
ccs901\0\0\BrdDat\testBoard.dat

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

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioxds110.dll'.
The library build date was 'Mar 25 2019'.
The library build time was '17:36:26'.
The library package version is '8.1.0.00007'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.

An error occurred while hard opening the controller.

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-260' (0xfffffefc).
The title is 'SC_ERR_XDS110_OPEN'.

The explanation is:
An attempt to connect to the XDS110 failed.
The cause may be one or more of: no XDS110 is connected, invalid
firmware update, invalid XDS110 serial number, or faulty USB
cable. The firmware and serial number may be updated using the
xdsdfu utility found in the .../ccs_base/common/uscif/xds110
directory of your installation. View the ReadMe.txt file there
for instructions.

[End: Texas Instruments XDS110 USB Debug Probe_0]

0 gil albo over 4 years ago in reply to Akash Gondalia

Intellectual 725 points

Hi again,
I've installed eveything on another PC
still not possible to debug.

1. environment
uniflash 5002289
CCS 90100004
mmwave SDK 3204
mmwave industrial toolbox 340

2.ccsdebug loading
connected the IWR6843ODS-ISK board when the SOP2 jumper is mounted.
power cycle
uniflash
connected the relevant com port
flashing the ccsdebug of the iwr6843
success
turn off the board.remove SOP2 jumper.

3.projects compilation
compile both projects of lab20 (mss ,dss) with the following, at the show build settings per project
XDS110 usb debugger
mmwave sensors
IWR6843

dss->build successfuly
afterwards->mss->build successfuly

4.target configuration file
create new target configuration file with the following specifications:
XDS110 usb debugger
mmwave sensors
IWR6843

save the created target configuration file.\
test connection shows:
Start: Texas Instruments XDS110 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]

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

C:\Users\User\AppData\Local\TEXASI~1\CCS\
ccs901\0\0\BrdDat\testBoard.dat

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

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioxds110.dll'.
The library build date was 'Mar 25 2019'.
The library build time was '17:36:26'.
The library package version is '8.1.0.00007'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.

An error occurred while hard opening the controller.

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-260' (0xfffffefc).
The title is 'SC_ERR_XDS110_OPEN'.

The explanation is:
An attempt to connect to the XDS110 failed.
The cause may be one or more of: no XDS110 is connected, invalid
firmware update, invalid XDS110 serial number, or faulty USB
cable. The firmware and serial number may be updated using the
xdsdfu utility found in the .../ccs_base/common/uscif/xds110
directory of your installation. View the ReadMe.txt file there
for instructions.

[End: Texas Instruments XDS110 USB Debug Probe_0]

0 Ki over 4 years ago in reply to gil albo

TI__Guru**** 420630 points

Hello,
The root issue is a communication failure between the PC (running CCS) and the XDS110 debug probe on the target.

software-dl.ti.com/.../ccsv7_debugging_jtag_connectivity_issues.html

Can you try checking the serial number for the XDS110 to see if it is valid. And if so, try manually updating the XDS110 firmware with the xdsdfu utility. Please see the below link:
software-dl.ti.com/.../emu_xds110.html

Thanks
ki

0 gil albo over 4 years ago in reply to Ki

Intellectual 725 points

Hi Ki-Soo,

After reading your recommendations ,I did the following:

0. Board settings

I did eveything while the original USB cable supplied by TI in use.

Device with power supply

SOP2 SOP0 are with jumpers on.

SOP1 without jumper

didn't changed any other jumper/switch

used OS: win10

1.Updating the XDS110 Firmware

Here's the cmd text

C:\Users\Gil.Albo>cd C:\ti\ccsv8\ccs_base\common\uscif\xds110

C:\ti\ccsv8\ccs_base\common\uscif\xds110>xdsdfu -e

USB Device Firmware Upgrade Utility

Scanning USB buses for supported XDS110 devices...

<<<< Device 0 >>>>

VID: 0x0451 PID: 0xbef3

Device Name: XDS110 Embed with CMSIS-DAP

Version: 2.3.0.14

Manufacturer: Texas Instruments

Serial Num: R0081038

Mode: Runtime

Configuration: Standard

Found 1 device.

/////////////////////////////////////////////////////////////////

C:\ti\ccsv8\ccs_base\common\uscif\xds110>xdsdfu -m

USB Device Firmware Upgrade Utility

Scanning USB buses for supported XDS110 devices...

<<<< Device 0 >>>>

VID: 0x0451 PID: 0xbef3

Device Name: XDS110 Embed with CMSIS-DAP

Version: 2.3.0.14

Manufacturer: Texas Instruments

Serial Num: R0081038

Mode: Runtime

Configuration: Standard

Switching device into DFU mode.

C:\ti\ccsv8\ccs_base\common\uscif\xds110>xdsdfu -f firmware.bin -r

USB Device Firmware Upgrade Utility

Scanning USB buses for supported XDS110 devices...

The requested device was not found on the bus.

/////////////////////////////////////////////////////////////////

2. Reinstall the Windows device drivers

I did the following to the com port for XDS110 ,and for Texas instuments debug probes

4. Problem.

After all of this update, the problem remains.

I repeated "Updating the XDS110 Firmware" again after "Reinstall the Windows device drivers" and the same message remained at xdsdfu -f firmware.bin -r(The requested device was not found on the bus.)

When flashing bin file of the lab20 project, the GUI is is functioning OK, the targets appear.

Please assist,

Gil

0 Ki over 4 years ago in reply to gil albo

TI__Guru**** 420630 points

Thanks Gil. I've escalated this issue to out emulation experts. We are investigating and will keep you posted of our progress.

0 Ki over 4 years ago in reply to Ki

TI__Guru**** 420630 points

Hi Gil,

Just following up with you to see if you were able to get the Tiva Device Firmware Update to succeed on your PC.

Thanks

0 gil albo over 4 years ago

Intellectual 725 points

Hi ki,

Eventually it works !!!

Thank you all for the support.

Gil

בתאריך יום ה׳, 6 ביוני 2019, 15:52, מאת Ki ‏<bounce-1043327@mail.e2e.ti.com>:

A Message from the TI E2E™ Community

Ki replied to CCS/IWR6843ISK: IWR6843 3D debug mode.

Hi Gil,

Just following up with you to see if you were able to get the Tiva Device Firmware Update to succeed on your PC.

Thanks

ki

-----------------------------------

Did you read the CCS Forum Guidelines & FAQ? If not, PLEASE read it. If you haven't read it in awhile, please read it again to see if any updates were made.

Having CCS problems? Check out the CCS Troubleshooting Guide

Looking for CCS Training/Documentation? Check out the CCS Resources page

Curious about the status of a bug and know the tracking ID? Track it via the public bug tracking portal

NOTE: When a bug is filed and a tracking ID is provided, the thread may then be suggested as "TI Thinks Resolved". Why? Please read the first FAQ of the CCS Forum Guidelines & FAQ

You received this notification because you subscribed to the forum. To unsubscribe from only this thread, go here.

Flag this post as spam/abuse.
refid:d45b132f-9a28-4bf4-980f-5f617bd07b56

0 Ki over 4 years ago in reply to gil albo

TI__Guru**** 420630 points

Excellent! Great to hear and thank you for your patience!

As for others following the thread, this issue was resolved off-line. The root cause for the connection failure was because a required windows driver for the debug probe was not installed. The user did not have the correct permissions and had to escalate the action for IT to handle.

Thanks

Sensors

Sensors forum

CCS/IWR6843ISK: IWR6843 3D debug mode