Hi,
Is it possible to output lvds and run OOB demo at same time? Is there any EDMA/L3 bandwidth limitation in this case?
Thanks,
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi,
Is it possible to output lvds and run OOB demo at same time? Is there any EDMA/L3 bandwidth limitation in this case?
Thanks,
Kyle,
I knew that current OOB is not support this feature.
I wants to know from chip resource view (EDMA/L3) if it is possible to support LVDS output and OOB demo at same time?
Hi Chris,
It's great to hear that you made OOB+LVDS working.
Whenever MSS does sensorStop it sends message to DSS over mailbox which is handled 'MmwDemo_dssMmwaveStopCallbackFxn' callback function with event 'MMWDEMO_STOP_EVT' of dss_main.c file .
So you need to close/deinit your modules in the 'MmwDemo_dssDataPathTask' under 'MMWDEMO_STOP_EVT' event condition.
To verify LVDS data in this scenario you need to capture LVDS data usingTSW1400 (HW) and HSDC-pro GUI. And use 'capture_demo.m' matlab script provided for capture demo. You may need to change config parameters in this script which you sending over UART to MMW demo application.
Regards,
Jitendra Gupta
Michelle,
Thanks for your feedback.
1. Lvds lanes are 2
I think I already set the lvds lanes as 2 in below code.
initCfg.u.lvdsCfg.lvdsLaneEnable = 0x3U;
2. Data format to non-interleave
I only found the format setting in CBUFF config. I would like to change as below.
cbuffCfg.dataMode = CBUFF_DataMode_INTERLEAVED;
Change to ->
cbuffCfg.dataMode = CBUFF_DataMode_NON_INTERLEAVED;
Chris,
I've checked with software team and it was not set correctly. The capture demo was tested with 1RX channel only, hense the issue is not exposed. It'll be fixed.
Regards,
Michelle
Sorry for the delay. I thought I've answered but somehow it didn't show.
Anyway, the default capture demo was not setting correctly. The verification was done with only 1 RX only so the issue wasn't exposed.
This has been fixed in the latest SDK development.
Regards,
Michelle