• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 4 answers
  • Subscribers 29 subscribers
  • Views 464 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AWR2243BOOST: Some questions about SDK4203 TDM code

Gmsy Bryant
Expert 1650 points
Part Number: AWR2243BOOST
Other Parts Discussed in Thread: AWR2243, AM2732

Hello,TI's engineers:

  I read the code about sdk4203 tdm mode.We use AWR2243 and AM2732 evm to develop radar.

  Now i meet a question,see as follow:

#define DPU_RangeProcHWA_InputMode_MAPPED (uint32_t) 0U
#define DPU_RangeProcHWA_InputMode_ISOLATED (uint32_t) 1U
#define DPU_RangeProcHWA_InputMode_HWA_INTERNAL_MEM (uint32_t) 2U

There have three mode,but i can not understand what different about DPU_RangeProcHWA_InputMode_ISOLATED and DPU_RangeProcHWA_InputMode_HWA_INTERNAL_MEM .If we use AWR2243+AM2732，which mode should we selected. 

Thank you very much!

BR

Bryant

  • 0
    Expert 1650 points

    Hello,

    Let me ask you one more question.In the comments of the code,see as follow:(we use AWR2243+AM2732)

    // /*! @brief Range input is integrated with DFE input
    // ADC buffer is not mapped to HWA memory,
    // DMA data from ADCBuf to HWA memory is
    // needed in range processing */
    //

    Is the ADCBUFFER in AWR2243, not in 2732?

    BR

    Bryant

  • 0 in reply to Gmsy Bryant
    TI__Guru*** 148974 points

    Hi,

    The ADCBuf is in 27xx.

    Gmsy Bryant said:
    #define DPU_RangeProcHWA_InputMode_MAPPED (uint32_t) 0U
    #define DPU_RangeProcHWA_InputMode_ISOLATED (uint32_t) 1U
    #define DPU_RangeProcHWA_InputMode_HWA_INTERNAL_MEM (uint32_t) 2U

    Please use the same mode that is used in the 27xx demo

    thank you

    Cesar

  • 0 in reply to Cesar
    Expert 1650 points

    Hello,Cesar, 

        AM2732 do not have adcbuffer.2243's datesheet says adcbuffer is on 2243.Please check it.

        At the same time,we use sdk4203 and 2243+2732,so which input mode is selected?

        What means about you say"Please use the same mode that is used in the 27xx demo"?

    Thank you very much.

    BR

    Bryant

  • 0 in reply to Gmsy Bryant
    TI__Guru*** 148974 points

    Yes,

    You are correct, sorry for the confusion. The ADC buffer is on 2243.

    Gmsy Bryant said:
    "Please use the same mode that is used in the 27xx demo"

    Yes, please use the mode that is used by the demo provided in the

    C:\ti\mmwave_mcuplus_sdk_04_02_00_02\mmwave_mcuplus_sdk_04_02_00_02\ti\demo\am273x\mmw

    Thank you

    Cesar

  • 0 in reply to Cesar
    Expert 1650 points

    Hello,Cesar,

    The TI offered demo you said, is offering three mode in the demo,I don't know which model is reasonable for 2243+2732,so I came to ask you.

    Thank you

    Bryant

  • 0 in reply to Gmsy Bryant
    TI__Guru*** 148974 points

    Hi,

    Gmsy Bryant said:
    The TI offered demo you said, is offering three mode in the demo

    This understanding is not correct. The AM273x demo does not support all modes.

    See code below in objectdetection.c

    The mode used in the demo is "DPU_RangeProcHWA_InputMode_HWA_INTERNAL_MEM"

    #ifdef SOC_AM273X
        #if defined (DPC_SKIP_CSI_TRIGGER) || defined (LVDS_STREAM)
            /* In this case HWA hardware trigger source is equal to HWA param index value*/
            hwaCfg->dataInputMode = DPU_RangeProcHWA_InputMode_ISOLATED;
        #else
            hwaCfg->dataInputMode = DPU_RangeProcHWA_InputMode_HWA_INTERNAL_MEM;
            hwaCfg->hardwareTrigSrc = DPC_OBJDET_HWA_HARDWARE_TRIGGER_SOURCE;
        #endif

    Thank you

    Cesar

  • 0 in reply to Cesar
    Expert 1650 points

    Hello,Cesar

    #ifdef SOC_AM273X
        #if defined (DPC_SKIP_CSI_TRIGGER) || defined (LVDS_STREAM)
            /* In this case HWA hardware trigger source is equal to HWA param index value*/
            hwaCfg->dataInputMode = DPU_RangeProcHWA_InputMode_ISOLATED;
        #else
            hwaCfg->dataInputMode = DPU_RangeProcHWA_InputMode_HWA_INTERNAL_MEM;
            hwaCfg->hardwareTrigSrc = DPU_RangeProcHWA_InputMode_ISOLATED;
        #endif

    Why not select DPU_RangeProcHWA_InputMode_ISOLATED mode if we define DPC_SKIP_CSI_TRIGGER or LVDS_STREAM?

    And what the different between the DPU_RangeProcHWA_InputMode_ISOLATED and DPU_RangeProcHWA_InputMode_HWA_INTERNAL_MEM?

    Thanks.

    Bryant

  • 0 in reply to Gmsy Bryant
    TI__Guru*** 148974 points

    Hi,

    If you are using DPC_SKIP_CSI_TRIGGER or LVDS_STREAM you should use DPU_RangeProcHWA_InputMode_ISOLATED in the same way as the provided demo.

    Please seefor description of input modes

    C:\ti\mmwave_mcuplus_sdk_04_02_00_02\mmwave_mcuplus_sdk_04_02_00_02\ti\datapath\dpu\rangeproc\rangeprochwa.h

    enum DPU_RangeProcHWA_InputMode_e

    Thank you

    Cesar