IWR6843: Error -1170 w/ XDS200

Erik Bolton

Part Number: IWR6843
Other Parts Discussed in Thread: UNIFLASH, MMWAVEICBOOST,

Hey All:

I'm trying to get code stepping/debugging to work on custom IWR6843 hardware connected to a XDS200. I'm getting error -1170 when I try to run in Debug mode. Here's some background:

I've imported the "out of box" mmwave demo from the 3.06 SDK into CCS 12 as a test project.
We DO NOT have an EEPROM populated on our board. Our production IWR firmware is loaded over SPI into RAM on each boot.
I've fixed the SOP lines to 011 as described in the IWR6843 Bootloader Flow
Here are the config options I'm using and the error window:

The connection test passes

[Start: Texas Instruments XDS2xx 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\ERIKBO~1\AppData\Local\TEXASI~1\
    CCS\ccs1200\0\0\BrdDat\testBoard.dat

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

This utility has selected a 560/2xx-class product.
This utility will load the program 'xds2xxu.out'.
The library build date was 'Jun 18 2022'.
The library build time was '03:06:08'.
The library package version is '9.8.0.00235'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '13' (0x0000000d).
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]-----------------------------

This emulator does not create a reset log-file.

-----[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.

[End: Texas Instruments XDS2xx USB Debug Probe]

After doing some research on this forum and elsewhere it appears this error comes up often and doesn't point to the root cause at all. Two fixes are often mentioned:

Set the SOP pins correctly (I think I have).
Set the image to "development" mode in either CCS or Uniflash.
1. We don't use Uniflash because we load the image into RAM over serial.
2. I can't find ANY mention of "development mode" in CCS or the utilities that assemble the image (out2rprc and MulticoreImageGen)
3. There is no image.syscfg generated when I import the mmwave demo into CCS.

Any help would be much appreciated.

Thanks.

-Erik Bolton

over 3 years ago

0 Angie Mitchell over 3 years ago

TI__Genius 10730 points

Hi Erik,

Our team is looking into this and will be getting back to you in the next 24 hours.

Thanks,

Angie

0 Erik Bolton over 3 years ago in reply to Angie Mitchell

Prodigy 40 points

Thanks Angie. I also have an IWR6843ISK on a MMWAVEICBOOST carrier board as a sanity check.

I can get code stepping to work on the ISK/BOOST combo when SOP[2:0] is set to 001. I also ran into this post on the forum:

https://e2e.ti.com/support/tools/code-composer-studio-group/ccs/f/code-composer-studio-forum/966694/ccs-awr6843isk-ccs-connection-failed-error-code--2062/3572615?tisearch=e2e-sitesearch&keymatch=error%2525202062#3572615

Hi PJ,
What are the settings of your SOP jumpers? Only SOP0 should be set to ON if you wish to connect with CCS.
Are you using the on-board XDS110 debug probe?

Thanks
ki

I tried SOP[2:0] = 001 on our hardware, and I get the same result (error -1170).

0 Angie Mitchell over 3 years ago in reply to Erik Bolton

TI__Genius 10730 points

Hi Erik,

First, why are you looking to use the debug mode? When developing with our products customers usually use functional or flashing mode. With the ccsdebug image in our SDK you can debug in CCS in functional mode. (see instructions here)

Secondly, the debug mode is supported by our mmwave studio program, there are some register modifications that need to be made to enable CCS to work in this mode.

Thank you,

Angie

0 Erik Bolton over 3 years ago in reply to Angie Mitchell

Prodigy 40 points

Angie:

I may have confused the issue by using the word EEPROM. Again, we load our production image over SPI into RAM on each boot.

We have pads for the QSPI flash, but it isn't populated for the production board.

I assumed I could use debug mode to step through the Cortex side (MSS) without using flash (and the CCS debug firmware).

Is there a way to do this? If not, I can request another board with the flash part populated.

Thanks.

-Erik

0 Angie Mitchell over 3 years ago in reply to Erik Bolton

TI__Genius 10730 points

Hi Erik,

No problem!

By step though the MSS, do you mean step through the code as if you were in debug mode but without using the flash?

Thanks,

Angie

0 Angie Mitchell over 3 years ago in reply to Angie Mitchell

TI__Genius 10730 points

Hi Erik, your reply was not showing up properly so I am going to repeat it

Erik replied something similar to: "Yes! We need to step through the mss to see an issue we are having"

0 Erik Bolton over 3 years ago in reply to Angie Mitchell

Prodigy 40 points

Correct. I need to step through the MSS code for the out of box demo to diagnose an issue and I'd like to do it without the QPSI flash image.

0 Angie Mitchell over 3 years ago in reply to Angie Mitchell

TI__Genius 10730 points

Hi Erik,

This can be done in functional mode. You would need to send the code to RAM via SPI and then have the project files on hand (I prefer to do this by having the project built in CCS).

You would load code, switch to functional, (do not send the .cfg yet) and then connect to the target configuration in CCS as if you are about to do CCS debug. Once you have connected to the device you will be prompted to load symbols, these will be from the projects you already have built in CCS.

Following this method you can step through the code in functional mode with the image loaded to RAM via SPI.

Thanks,

Angie

0 Erik Bolton over 3 years ago in reply to Angie Mitchell

Prodigy 40 points

Hey Angie:

I have a modified version of the mmwave demo building in CCS. I added an infinite loop early in main() to spin the processor so I can connect it at a known point before it fails or asserts. Here's my steps so far:

build the demo in CCS (Debug mode) and generate a new image (xwr68xx_mmw_demo.bin)
reset the board with the SOP pins set to functional
copy the debug image to RAM over SPI
open CCS
right click on the target Config -> Debug As -> Code Composer Debug Session
same error

I'm not switching to functional mode after I load code. I have to be in functional to load code.

I'm not sure what you mean by "send the .cfg".

I'm never prompted to load symbols. I've set the Debug config to only load the symbols from the project and not the program itself. I can't connect to the target manually (Run -> Connect to Target in the Debug window).

software-dl.ti.com/.../ccs_debug-main.html

Can you point me to a reference for your steps or lay them out in more detail?

-Erik

0 Angie Mitchell over 3 years ago in reply to Erik Bolton

TI__Genius 10730 points

Hi Erik,

Thank you for your patience, we do not have documentation for this but I am going to point you to the closest thing we have: Using CCS Debug. These are the instructions for using CCS debug in development mode with the ccs debug image flashed. This can be used when code is in development.

However to specifically debug the code loaded to the RAM over SPI you would instead load the code to RAM over SPI. The steps would be

build the demo in CCS (Debug mode) and generate a new image (xwr68xx_mmw_demo.bin)
reset the board with the SOP pins set to functional
copy the debug image to RAM over SPI
open CCS
right click on the target Config -> Launch Selected Configuration (if this is not an option yet -- set up your target configurations according to the guide linked above)

Thank you,

Angie

0 Erik Bolton over 3 years ago in reply to Angie Mitchell

Prodigy 40 points

same error, immediately after I try to connect to the CortexR4

0 Angie Mitchell over 3 years ago in reply to Erik Bolton

TI__Genius 10730 points

Hi Erik,

What error do you get when you select Run -> connect to target?

Thank you,

Angie

0 Erik Bolton over 3 years ago in reply to Angie Mitchell

Prodigy 40 points

(Error -1170 @ 0x0)
Unable to access the DAP

0 Angie Mitchell over 3 years ago in reply to Erik Bolton

TI__Genius 10730 points

Hi Erik,

Would you be able to test using CCS debug with flash? I see you stated "We DO NOT have an EEPROM populated on our board. Our production IWR firmware is loaded over SPI into RAM on each boot.", would it be possible to populate for debug purposes?

Thanks,

Angie

0 Erik Bolton over 3 years ago in reply to Angie Mitchell

Prodigy 40 points

I'm trying to get a board with the flash populated. I'll post updates here when it arrives.

0 Angie Mitchell over 3 years ago in reply to Erik Bolton

TI__Genius 10730 points

Hi Erik,

Sounds good, I will be here ready to help when it arrives.

Angie

Sensors

Sensors forum

IWR6843: Error -1170 w/ XDS200