BEAGL-BONE-BLACK: AM335x

Hello Sarath,

Our group has not recently tested debugging Linux with CCS. The resources I am aware of are linked here:
https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1108360/sk-am62-code-composer-studio-failed-to-connect-to-xds-110-probe/4155604#4155604

Regards,

Nick

I went through your recommend the post.Currently I am using linux 6.1 version .In that they used device trees.I am getting following error in kernel logs.The error indicate that the device or resource is busy.How can i rectify the following error.

[    2.536309] ti-sysc: probe of 44e31000.target-module failed with error -16 

[    2.552968] ti-sysc: probe of 48040000.target-module failed with error –16 

Hello Sarath,

1) Double-checking, are you using the beaglebone black board, or a different board? If so, what board are you using?

2) Are you using an AM335x Linux Processor SDK? If so, are you using SDK 9.1, or 9.3?

0x44e31000 is the address of DMTIMER1, and 0x48040000 is the address of DMTIMER2. I see the same thing on my beaglebone black running SDK 9.3:

U-Boot SPL 2023.04-ti-g0893e693e08f (Nov 13 2024 - 21:2
8:34 +0000)
Trying to boot from MMC1
...
Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 6.1.112-ti-g4ef41ca7ad95 (oe-user@oe-host) (arm-oe-linux-gnueabi-gcc (GCC) 11.5.0
, GNU ld (GNU Binutils) 2.38.20220708) #1 PREEMPT Wed Nov 13 13:49:51 UTC 2024
...

[    1.551838] ti-sysc: probe of 44e31000.target-module failed with error -16
[    1.591726] ti-sysc: probe of 48040000.target-module failed with error -16

Are you specifically trying to use these hardware timers instead of the Linux system timer?
https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1121806/processor-sdk-am64x-how-to-configure-ticks-in-linux/4161795#4161795

Or are you just trying to get rid of any errors during boot time?

Regards,

Nick

Hello Nick,

I am using Beaglebone black board with AM335x Linux Processor SDK 9.3.

I was trying to debug Beaglebone black with XDS110 USB Debug Probe JTAG. I was able to set break point of linux kernel after watching this tutorial video https://www.youtube.com/watch?v=JpXJ-F5QqOo .But after some point the DEBUGSS clock is getting reset and I got the following error in Code Composer Studio.

By using the command $cat /sys/kernel/debug/clk/clk_summary | grep l3-aon .I was able to find that DEBUGSS Clock was not enabled or getting reset during boot.

After that when i checked Kernel log for timer errors I was able to find the following error.

[    2.536309] ti-sysc: probe of 44e31000.target-module failed with error -16 

[    2.552968] ti-sysc: probe of 48040000.target-module failed with error –16 

Hello Sarath,

I see. So you are not trying to use the dmtimers, you are just trying to figure out how to connect to Linux to debug.

I added an additional note on April 17 to the e2e response that I linked on April 14. Did you try following these steps?
https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1108360/sk-am62-code-composer-studio-failed-to-connect-to-xds-110-probe/4155604#4155604

AM335x note: in addition to the above video, please make the changes discussed in e2e thread CortxA8: Error connecting to the target: (Error -1204 @ 0x3D5B) Unable to access the DAP. 

Regards,

Nick

Hello Nick,

Thanks for the references ,after going through it I found the following code snippet in /arch/arm/mach-omap2/omap_hwmod_3xxx_data.c.In this code I modified omap3xxx_debugss_hwmod .flag 

but still getting same error:

Hello Sarath,

We are getting outside the scope of where I can offer support here - I will not have bandwidth to experiment myself with connecting CCS to Linux on AM335x within the next couple of weeks.

This was a recent thread with a similar issue, perhaps there is something there that will be helpful:
https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1490649/am3358-connect-jtag-after-entering-linux

Regards,

Nick