Other Parts Discussed in Thread: AM3359
Hello,
I have problems when I try debugging a PRU on a Beagleboard Black (with AM3359 processor) using the Code Compocer Studio v10 (10.2.0.00009) and XDS110 Debug Probe. I prevented Linux from booting on the Beaglebone (I checked by connecting through UART using Tera Term, there were only 'CCCC's to see)
I followed the instructions from these slides: https://training.ti.com/system/files/docs/debug_pru_using_ccs_slides.pdf . The link to debug initialization script was invalid, I downloaded the script from here: https://git.ti.com/cgit/sitara-dss-files/am335x-dss-files/about/ and proceeded as said on the slides. When I click 'debug' I get following Error:
Error connecting to the target:
(Error -1170 @ 0x4A322000)
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 9.3.0.00032)
(Error -1170 @ 0x4A322000)
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 9.3.0.00032)
I tried different JTAG frequencies as shown in this video: https://www.youtube.com/watch?v=mKxaztkCsYw&t=356s. For every frequency I got a successful connectivity test (as shown here: https://www.youtube.com/watch?v=o_2iMqZ1EbU&feature=youtu.be) , but got the same error while trying to connect to the target, so I stayed at the default 5,5MHz.
After that I followed the instructions from here: http://software-dl.ti.com/ccs/esd/documents/ccsv7_debugging_jtag_connectivity_issues.html#cannot-access-the-dap and accessed the DAP manually as shown in here: https://www.youtube.com/watch?v=-yGmq_VKvTQ&feature=youtu.be. By doing so I also could connect to the CortxA8, but not to PRU.
The debug probe was connected directly to my laptop, the Beagleboard was powered with a smartphone power supply. The debug probe is shown as XDS110 Class Auxiliary Data Port (COM12) and XDS110 Class Application/User UART (COM11) in the windows device manager.
I would be grateful for any suggestions of what could be causing this error and how to fix this, thank you all in advance.
P.S. I'm not sure if I posted it at the right forum, correct me if it's wrong.
I would be grateful for any suggestions of what could be causing this error and how to fix this, thank you all in advance.
P.S. I'm not sure if I posted it at the right forum, correct me if it's wrong.
