AWR2243BOOST: Disabling CSI-Lanes not working Properly

Tim Teuber

Part Number: AWR2243BOOST
Other Parts Discussed in Thread: AWR2243

Hi Team,

I ported the mmWave Link Library on a Linux Based Embedded System, to communication is handled with I2C. Everything works fine. I can Start Up the AWR, enable RF, Trigger Frames and so on. Now i wanted to call the rlDeviceSetLaneConfig API, to disable Lane 3 and 4.

Therefor i am writing 0x3 to the rlDevLaneEnable_t.laneEn Variable, to only enable lane 0 and lane 1. When I start my application, everything still looks good, to message gets transferred correctly and the correct answer of the AWR2243 comes back. I already checked alignment of the messages with the AWR_DEV_RX_DATA_PATH_LANEEN_SET_SB Message from the Radar Interface Control Document.

When I probe the CSI-Lanes of the AWR2243 with my Oscilloscope, it seems like all Lanes are still enabled. There are CSI-Signals being send on all 4 CSI-Lanes. Unfortunately, I currently cant really decode the Data that is being send, but the Waveforms I observed with the Oscilloscope follow the MIPI CSI Standard.

Is this normal, and the Signals of Lane 3 and 4 just don't contain any data? Or is this wrong behavior. If so, what did I do wrong, or Is my device damaged?

Best regards

Tim

9 months ago

0 aozer 9 months ago

TI__Mastermind 26925 points

Hello,

I believe you need to us rlDeviceSetCsi2Config to disable the lanes. You should set the lane position to zero for disabled lanes.

The rlDeviceSetLaneConfig is for LVDS only.

(+) AWR1243BOOST: Issues about setting the lanes of CSI2 on AWR1243BOOST - Sensors forum - Sensors - TI E2E support forums

Regards,

Adrian

0 Tim Teuber 9 months ago in reply to aozer

Intellectual 350 points

Hello Adrian,

I will try this Function. But in the Radar Interface Control Document, it says that AWR_DEV_RX_DATA_PATH_LANEEN_SET_SB, is used for LVDS and CSI, this causes confusing.

Thank you,

Tim

0 Tim Teuber 9 months ago in reply to aozer

Intellectual 350 points

Hi,

I now tried the Function and it works fine, but when the application is done, it get a AWR_AE_MSS_CPUFAULT_SB Error Message, which indicates a MSS Chirp Error.

What could be the Issue

0 Tim Teuber 9 months ago in reply to aozer

Intellectual 350 points

I just figured out: When i use the command, to enable all lanes, it workes fine. Could it be, that there is just to much data to be send over only 2 lanes and that i have to configure that in a different way?

0 aozer 9 months ago in reply to Tim Teuber

TI__Mastermind 26925 points

Hello,

You can always calculate the needed throughput based on your config to make sure it is not exceeding the CSI2 throughput.

#RX * # ADC bits * Sampling rate = max throughput i.e. 4RX * 16 bits * 25 Msps = 1600 Mbps

Do you have any ability to try this board with mmWave Studio to confirm it is not a hardware issue?

Regards,

Adrian

0 Tim Teuber 9 months ago in reply to aozer

Intellectual 350 points

Hello aozer,

Thank you for the reply. Unfortunately i cant confirm it with mmWave Studio, because I don't have the DCA1000, which I think is required for mmWave Studio to work with AWR2243. But I think the issue was that i was trying to send to much data over all.

Where do have the Max throughput Number from? Is that the maximal Throughput defined in the MIPI Spec? Is this for one Lane or for all?

Thank you,

Tim

0 aozer 9 months ago in reply to Tim Teuber

TI__Mastermind 26925 points

Hello,

Max throughput is dependent on what you set as the data rate. If you set 600 Mbps with 4 lanes it will be 2400 Mbps. If you enable one lane it will be 600 Mbps.

Regards,

Adrian