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.

IWR1642: Is it possible to output lvds and run OOB demo at same time?

Part Number: IWR1642

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,

  • Chris,

    The ability to run the out-of-box demo and output data on LVDS is not supported at this time. Enabling this secondary feature would require an update to the source code. Please reply if you have additional questions.

    Regards,
    Kyle
  • 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?

  • Hello Chris,
    Yes, it is possible to transmit out the raw data along with the DSP processing the data for object detection. There are multiple EDMA channels and separate channels can be used for each of these tasks.

    Regards,
    Vivek
  • Hi,

    I am thinking to add the CBUFF/LVDS config code from capture demo to mmw demo. I have some question and would you pls help?

    1. Current mmw demo will EDMA the adc buffer data to DSP L2 first. I think the edma is triggered manually with ISR post the event. Does I understanding correct?
    2. How about the EDMA to copy the adc buffer data to CBUFF fifo in capture demo? I am not clear it is triggered by manual or event?
    3. The EDMA from adc to CBUFF is configured on R4F in capture demo and EDMA to DSP L2 is configured in dsp in mmw demo. I think they are using different channel, so combine these two EDMA operation should be ok. Pls correct me if I miss anything.
    4. If you have any other suggestion on adding the LVDS output in mmw demo, pls kindly advise.

    Thanks,
  • Hi,

    I tried to add CBUFF/LVDS init/open in MmwDemo_dssDataPathConfigAdcBuf() in dss_main.c. To enable reconfiguration, I need to run cbuff close/deinit if there is sensorStop command. But I found the sensorStop operation is done on mss and the cbuff inif/open is done on dss.
    Any suggestion to add cbuff close/deinit for sensorStop command?

    Thanks,
  • Hi,

    I have modified current mmw demo and now there is LVDS output when OOB demo is running (I detected the LVDS signal when code is running). But I can’t verify if the LVDS data is correct or not. Do you have any comment?
  • 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

  • Chris,

    There are differences in xwr16xx and xwr14xx, for one, the lvds lanes are 2 instead of 4. The data format can not be interleaved for iwr16xx. I looked at the code you modified for lvds + oob. The format need to be set to non-interleaved. The matlab file needs to be modified to be correctly displaying the xwr16xx lvds output based on the differences as mentioned before.

    Thanks and Regards,
    Michelle
  • 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;

  • Michelle,

    In default capture demo of xWR1642 in sdk 1.0, the CBUFF data mode is set as interleaved. Is this a mistake?

    C:\ti\mmwave_sdk_01_00_00_05\packages\ti\demo\xwr16xx\capture\common\capture_common.c
    cbuffCfg.dataMode = CBUFF_DataMode_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