TDA4VE-Q1: How to profile the DDR access throughput/latency to verify memory starvation event during runtime

Mostafa Hadi

Part Number: TDA4VE-Q1

Tool/software:

Is there a way to profile external DDR memory access using CP Tracer tool, so that I can single out the domain/Core that is causing stalling during the application runtime?

we are using the Soc to capture Lidar images through the CSIrx, and have 20 fps output. I can't find the route Id tables in the TRM to try and narrow down the profiling.

11 months ago

0 Jared McArthur 11 months ago

TI__Mastermind 25460 points

Hi Mostafa,

What core(s) are you trying to profile?

Best,
Jared

0 Mostafa Hadi 11 months ago in reply to Jared McArthur

Prodigy 30 points

Hi Jared,

I am trying to profile the RPU MCU

0 Jared McArthur 11 months ago in reply to Mostafa Hadi

TI__Mastermind 25460 points

Hi Mostafa,

Are the following routes not what you're looking for? They are within the appendix.

Module Name	Initiator Interface	Which CBASS it is connected to	Route ID
R5FSS0	PBDG_RMST0	CBASS_IPPHY_SAFE0	522
R5FSS0	PBDG_WMST0	CBASS_IPPHY_SAFE0	523
R5FSS0	PBDG_RMST1	CBASS_IPPHY_SAFE0	530
R5FSS0	PBDG_WMST1	CBASS_IPPHY_SAFE0	531
R5FSS1	PBDG_RMST0	pulsar1_periph_switch_cbass0	538
R5FSS1	PBDG_WMST0	pulsar1_periph_switch_cbass0	539
R5FSS1	PBDG_RMST1	pulsar1_periph_switch_cbass0	546
R5FSS1	PBDG_WMST1	pulsar1_periph_switch_cbass0	547
R5FSS2	PBDG_RMST0	pulsar1_periph_switch_cbass0	554
R5FSS2	PBDG_WMST0	pulsar1_periph_switch_cbass0	555
R5FSS2	PBDG_RMST1	pulsar1_periph_switch_cbass0	556
R5FSS2	PBDG_WMST1	pulsar1_periph_switch_cbass0	557

Best,
Jared

0 Dave Copeland 10 months ago in reply to Jared McArthur

TI__Guru*** 141356 points

Closing as answered, simply reply to re-open if further support is need, Dave C

Processors

Processors forum

TDA4VE-Q1: How to profile the DDR access throughput/latency to verify memory starvation event during runtime