J784S4XEVM: Unable to access DAP

Hi Joseph,

Could you clarify if you using the SK-AM69 device?

Thank you,

Fabiana

I talked to my hardware guy and I guess the AM69 are not available yet, so our boards have a XJ784A4 on them. So my question still stands.

Hi Joseph,

Joseph Dobesh said:

The failure happens when I run the launch script on line:

Can you please share the error logs that you are getting with launch.js?

Joseph Dobesh said:

I talked to my hardware guy and I guess the AM69 are not available yet, so our boards have a XJ784A4 on them. So my question still stands.

I am not clear on the board that you are using? Are you using TI-EVM/SK board or is this a custom board? 

Also, I don't see any part number with XJ784A4, can you please confirm if that is correct?

Regards,
Parth

The board we are using is a proprietary board we designed. I will get back to you on the error logs. Sorry, my mistake. The part number is XJ784S45.

The following is from the popup window:

Error connecting to the target:
(Error -1170 @ 0x0)
Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 12.7.0.00105)

This is from the console:

CORTEX_M4F_0: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00105)

Hi,

Can you please confirm if the gel files are configured for M4 core?

If configured, can you please try and connect directly to M4 core rather than using the launch.js and see if you are able to connect?

Regards,
Parth

confirmed.

ccs1270\ccs\ccs_base\emulation\gel\J784S4_TDA4VH\J7AHP.gel

has the following comment in it:

/*
* Platform: Keystone 3 SoCs
* - Jacinto 7 (J7AHP)
* Usage: This GEL will be run from CCS upon connection to the Cortex-M4F
* CPU.
* History:
* See History.txt
*/

Cannot connect. I get hte following in a popup window:

Error connecting to the target:
(Error -1170 @ 0x0)
Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 12.7.0.00105)

And the following in the console window:

CORTEX_M4F_0: Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 12.7.0.00105)

FYI, I lowered the TCK frequency to it's lowest value with no change.

One last bit before heading out today. CS_DAP Router Properties:

DAP TAP ID: 0x0

Device Management: Power-AP

DAP AP Configuration: 0x00000073

I am trying to find where in documentation these things are defined with no luck.

Update: I started over and reset all the settings for my target configuration. I still can't connect to CORTEX_M4F_0, but I was able to connect to MCU_Cortex_R5_0. I am unable connect to any other cores.

Hi Joseph,

Do you have another board with you? Can you please try it on a different board?

Also, is this is a TI board or a custom board?

Regards,
Parth

Yes, we have a couple boards we are testing. All with the same issue. We are in the process of getting some evaluation boards from TI.

Let me check this internally and get back to you

Regards,
Parth

Update: We got the SK-AM69 eval boards in and we are getting the same issue.

I'm checking on this.  Not sure if its related to the device security.

The device you listed is a secure device (HS-FS) - similar to  the device mounted on the SK-AM69 EVMs.  My understanding is the M4 cores are not accessible via JTAG (by default).  You should be able to access R5F cores.

This does not make sense. The setup info on the webpage for the J784S4 runs a launch.js script which tries to connect with the M4

J784S4EVM ship with GP silicon (non secure).  Thus it will behave differently with regards to JTAG, booting, etc.  The device you are using is a secure device (similar to the SK-AM69 EVM). 

Did you try connecting with a different core (R5F)?

Are you referring to the XJ784A45 that is on our board? Because both boards show the same behavior.

You mentioned the device used on custom board is XJ784S45AALY.   That is the same device used on SK-AM69.

The J784S4EVM uses a different device XJ784S4GAALY.   As mentioned - the device you are is a secure device.  The J784S4EVM device does not have security features enabled.  If you are using scripts design for the J784S4EVM - that may explain some of your issues.  I'm not a security expert - but my understanding is certain areas of the device are not accessible via JTAG by default.   That is why I requested trying to connect to R5F rather than M4 (which is locked on secure devices)

So, how does one debug the A72 and C7 cores if the only cores accessible are MCU R5s? Is there another way to debug on them other than using JTAG? Can we expect more documentation in the future.

Hi Joseph Dobesh

If you are using a HS-FS device you wont be able to use the no boot mode as the JTAG of  M4_0 where the TIFS is runs is locked , so you wont be able to load the tifs binary with JTAG interface this is what the gel script is doing.

on HS-FS only M4 cores are locked but other core are unlocked so you can connect to them.

Joseph Dobesh said:

software-dl.ti.com/.../quote]

The steps mentioned in this document is with respect to the GP

You can use other boot mode as mentioned in the SDK documentation.

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

Regards
Diwakar