PROCESSOR-SDK-AM64X: AM243X GP EVM (Error -1170 @ 0x0) unable to access the DAP

li zhang

Environment:

Board: TMDS243GPEVM (bought from TI website)
Debugger: onboard XDS110 with microAB USB connector
IDE: CCS 10.3.1
SDK: AM243X/08_01_00_25, AM243X/08_01_00_14, AM243X/08_00_00_21

Use case:

I use AM243X/08_01_00_25 to flash SOC initialization binary to the new board for the first time follow https://software-dl.ti.com/mcu-plus-sdk/esd/AM243X/08_01_00_25/exports/docs/api_guide_am243x/EVM_SETUP_PAGE.html#EVM_FLASH_SOC_INIT,

all commands executed successful. Change boot mode from UART boot mode to OSPI boot mode, then power on, the information shows in UART terminal is correct.

But when I try to connect to core_R5_0_0， CCS popup an error window, see below picture.

I try to use AM243X/08_01_00_14, AM243X/08_00_00_21 to check, but get the same error result.

I try to download DMSC firmware directly by using script in NOBOOT mode, but get the same error result.

I don't know how to resolve this problem.

over 2 years ago

0 li zhang over 2 years ago

Prodigy 130 points

I try to connect to other core, but get the same error result.

bootloader output are same to the guide, all cores are enabled.

0 Frank Livingston over 2 years ago in reply to li zhang

TI__Mastermind 28788 points

Hi Li,

I was able to reproduce this issue. I'm investigating the further and will get back with you shortly.

Regards,
Frank

0 Frank Livingston over 2 years ago in reply to Frank Livingston

TI__Mastermind 28788 points

Hi Li,

Apparently this is a known issue. JTAG should be connected after the board is powered up.

https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1042164/lp-am243-cannot-establish-connection/3857427#3857427

Can you please see if this helps?

Regards,
Frank

0 li zhang over 2 years ago in reply to Frank Livingston

Prodigy 130 points

Hi Frank,

I had connected the JTAG through microAB USB connector.

I had bought 4 pics TMDS243GPEVM, and I tried to verify if all board are good, and found an interesting result, you can get the result from below table.

board 2# and 3# are good, but board 1# and 4# have the same error 1170.

By the way, when I first launch the configuration through CCS, CCS popup an window, and force me to update the XDS110 firmware from 3.0.0.14 to 3.0.0.15, otherwise, I cannot launch the configuration.

I use the same SDK( mcu_plus_sdk_am243x_08_01_00_25), same method, same hardware setting, but get the different results.

Can I assume this is a hardware problem?

+1 Frank Livingston over 2 years ago in reply to li zhang

TI__Mastermind 28788 points

Hi Li,

li zhang said:
I had connected the JTAG through microAB USB connector.

Did you connect the JTAG through the microAB USB connector after powering the board, and not before powering the board?

li zhang said:
By the way, when I first launch the configuration through CCS, CCS popup an window, and force me to update the XDS110 firmware from 3.0.0.14 to 3.0.0.15, otherwise, I cannot launch the configuration.

I observed this behavior, but updating the XDS110 firmware shouldn't result in being unable to connect to the board.

I forgot to mention before that I'm able successfully test the JTAG connection from the CCS target configuration. However, I'm still unable to connect to any core after launching the target.

li zhang said:
Can I assume this is a hardware problem?

Your observations seem to support that conclusion. I'm reassigning this thread to a hardware applications engineer with more expertise in this area.

Regards,
Frank

0 Mike Pridgen over 2 years ago in reply to li zhang

TI__Mastermind 20945 points

Hi Li,

Can you confirm that you are not connecting that XDS110 USB cable until after the board is powered like Frank was asking? This definitely causes intermittent issues similar to what you are seeing.

Also, does it ask you to update the XDS110 firmware every time you connect the board? Are you performing this update?

Thanks,
Mike

0 li zhang over 2 years ago in reply to Mike Pridgen

Prodigy 130 points

Hi Mike,

Mike Pridgen said:
Can you confirm that you are not connecting that XDS110 USB cable until after the board is powered like Frank was asking? This definitely causes intermittent issues similar to what you are seeing.

No, I connect the XDS110 USB cable all the time no matter power on or off.

Mike Pridgen said:
Also, does it ask you to update the XDS110 firmware every time you connect the board? Are you performing this update?

The update warning window only popups on the first connection, it will not popup after update the firmware.

All four boards had updated the firmware.

+1 Mike Pridgen over 2 years ago in reply to li zhang

TI__Mastermind 20945 points

Hi Li,

Can you try disconnecting the XDS110 USB cable when powering on the boards that have the issue and reconnecting after the board has powered on?

Lets just totally eliminate this as a possibility before diving into other potential root causes.

Thanks,
Mike

0 li zhang over 2 years ago in reply to Mike Pridgen

Prodigy 130 points

Hi Mike,

Disconnecting the XDS110 USB cable when powering on the boards and reconnecting after the board has powered on, this method works, board 1# and board 4# can connect target, load and debug program now.

this method resolved my problem, thanks.

Processors

Processors forum

PROCESSOR-SDK-AM64X: AM243X GP EVM (Error -1170 @ 0x0) unable to access the DAP