CCS/AM3358: JTAG connection error

Timothy Cleveland

Part Number: AM3358

Tool/software: Code Composer Studio

I am having issues connecting to the Sitara AM3358 on a Rev C Beaglebone Black development board. I'm using CCS 7 and an XDS110 Debug Probe. I am able to connect fine when using my Rev B Beaglebone Black, but when I attempt to connect with a Rev C, I get the following error:

CortxA8: 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 7.0.100.0)

I have reviewed multiple threads on e2e with similar issues people have experienced. I am digging through the GEL file to see if there is anything which needs to be tweaked due to any changes between the boards.

Can you provide me details as to exactly what Error -1170 means? Without additional information about the error, establishing root cause and thus a solution is proving very, very time consuming.

Regards,

- Tim Cleveland

over 6 years ago

0 Timothy Cleveland over 6 years ago

Prodigy 165 points

I have additional information to revise my problem statement. It turns out I have all Rev C Beaglebone blacks, but made by different manufacturers. Same rev pcb, same revision device, but when I connect with ones from manufacturer "B" the JTAG fault is generated.

I really do need details with regards to the fault being displayed by CCS to aid in debugging this. I look forward to your reply.

Thanks.

- Tim

0 Hossein Forouzani over 6 years ago

Genius 3030 points

Hi Tim,

Can you add a screenshot so I 'll be able to help you.

Regards,
Hossein

0 Ki over 6 years ago

TI__Guru**** 421230 points

Hi Tim,

Timothy Cleveland said:
Can you provide me details as to exactly what Error -1170 means? Without additional information about the error, establishing root cause and thus a solution is proving very, very time consuming.

That error is described in the link below:

http://software-dl.ti.com/ccs/esd/documents/ccsv7_debugging_jtag_connectivity_issues.html#cannot-access-the-dap

Hope this helps

0 Alexander Frick over 6 years ago in reply to Ki

Intellectual 645 points

Hey guys - I am working with Tim on this and have more information.

First off, we have a batch of Beaglebone Blacks (rev C) that were manufactured by element14. Those connect perfectly and we have been using those without issue.

Now, we ordered a batch of BBB and they are manufactured by GHI electronics and those are the board we are having issues connecting with. We have not changed anything between the boards, the GHI boards just don't connect via Jtag.

What is really odd is that i can hook up the GHI boards and connect to the DAP manually and look at memory in the memory browser. Even after doing that though, when I try to connect to the A8 core, I get the error Tim had (-1170 @ 0x0).

0 desouza over 6 years ago in reply to Alexander Frick

TI__Guru**** 168367 points

Hi,

If you are getting all the way down to the DAP, the JTAG circuitry is fully functional. You can get a bit more information about the status of the cores by checking the reference below:

processors.wiki.ti.com/.../GSG:Connecting_to_slave_cores_in_SoC_devices_v5

There is a chance the A8 core is not being powered properly or do not have a good active clock, thus it fails only on it.

Even with the A8 core powered, there is a chance the newer boards have different pre-loaded Software. In certain cases either pre-running Linux or U-boot can prevent JTAG access, but that used to be more common in earlier kernels (3.1, 3.2).

I will try to think about additional details that may be influencing this and report back.

Hope this helps,
Rafael

0 Alexander Frick over 6 years ago in reply to desouza

Intellectual 645 points

It was an issue with the bootloader. I blew it away (I am booting of an SD card anyway in my application), and it works great.

0 Timothy Cleveland over 6 years ago in reply to Alexander Frick

Prodigy 165 points

Yes, this addressed the error and I consider this issue closed.

Code Composer Studio™︎

Code Composer Studio forum

CCS/AM3358: JTAG connection error