MCU-PLUS-SDK-AM64X: Sniffer for RP messages

Dekel Guterman

Hi,

I'm working on Sitara and I'm implementing the communication between R5 and A53 by RP messages, based on your example - ipc_rpmsg_echo.

To debug the messages I want to know if there is any tool to sniff the traffic on the channel, or any other recommended way to do it.

Please advise.

Thanks,

Dekel

over 2 years ago

0 Aakash Kedia over 2 years ago

TI__Mastermind 26145 points

Hi Dekel Guterman,

Are you sure, you are using the correct device ? The AM263x does not have an A53 CPU.

Best Regards,
Aakash

0 Kowshik Gudimetla over 2 years ago

TI__Genius 15435 points

Hi Dekel,

Currently there is no sniffing or packet recorder for the IPC at the moment. Also there are no A53 cores in the AM263x MCU, can I know what Microcontroller/processor are you using please?

Thanks,
G Kowshik

0 Dekel Guterman over 2 years ago in reply to Kowshik Gudimetla

Intellectual 330 points

Sorry, I wrote AM263 instead of AM64...

Is there an option to edit the title?

Thanks.

0 Kowshik Gudimetla over 2 years ago in reply to Dekel Guterman

TI__Genius 15435 points

Hi Dekel,

Yes I changed it for you and assigned to the MPU team.

Thanks

0 Dekel Guterman over 2 years ago in reply to Kowshik Gudimetla

Intellectual 330 points

Thanks Kowshik!

0 Nick Saulnier over 2 years ago in reply to Dekel Guterman

TI__Guru** 100740 points

Hello Dekel,

Trace buffers

If you use print statements in your MCU+ code, and Linux RPMsg is enabled, those print statements will be written to the trace buffer (in addition to the UART terminal if you have one configured for output from the R5F core). So one low-effort way is to just print any RPMsg messages that you are about to send (or that you have received), and then you can check the trace buffer from Linux. The trace buffer is called "trace0" for all remote cores.

E.g., let's say you are trying to debug communication with remoteproc1.

#: cat /sys/kernel/debug/remoteproc/remoteproc1/trace0

Directly inspecting in CCS

You can also connect CCS to the remote cores while they are running and do things like set breakpoints, read variables, etc. For more details, refer to this FAQ: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1188177/faq-am62x-am64x-how-to-use-ccs-to-debug-a-running-m4f-core-that-was-started-by-linux

Regards,

Nick

0 shachar kaduri over 2 years ago in reply to Nick Saulnier

Prodigy 60 points

Hi Nick I have the problem Dekel described in this open issue, I have tried as you described to use cat, I am currently getting "Trace not available" when trying to use cat on trace0 file, can you please explain to me about that, it would help alot and also if you can to add some explanation on how to solve it ?

Thanks in advance, Shachar

0 Nick Saulnier over 2 years ago in reply to shachar kaduri

TI__Guru** 100740 points

Hello Shachar,

Give us more information

Please attach your Linux terminal output. Please include this information in your output:

1) Linux version (uname -a)

2) which core is which remoteproc instance (head /sys/class/remoteproc/remoteproc*/name)

3) what is the state of each core (head /sys/class/remoteproc/remoteproc*/state)

4) what is the trace status (cat /sys/kernel/debug/remoteproc/remoteprocX/trace0, where X is your instance)

5) what do you see when you connect CCS to the remote core, as detailed here? https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1188177/faq-am62x-am64x-how-to-use-ccs-to-debug-a-running-m4f-core-that-was-started-by-linux

Helpful resources

Since we have not chatted before, I assume you are new to using RemoteProc. Please make sure you have gone through our training in the Linux Academy: https://dev.ti.com/tirex/explore/node?a=7qm9DIS__LATEST&node=A__ANKEb6LZY6VAX.9xvGwQ-g__linux_academy_am64x__7qm9DIS__LATEST

You can find a "known good" RPMsg project prebuilt and included in the default Linux image. I usually suggest making sure that you can do something with that "known good" project & filesystem first. Once you get it working there, you can try debugging your own code.

Information about the "known good" project is here:
https://dev.ti.com/tirex/explore/node?a=7qm9DIS__LATEST&node=A__AAtN.uvfmDSx4mvQ7f4R.w__linux_academy_am64x__7qm9DIS__LATEST

Regards,

Nick

Arm-based microcontrollers

Arm-based microcontrollers forum

MCU-PLUS-SDK-AM64X: Sniffer for RP messages