• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 510 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.

Original question:

CCS/AWR1642BOOST: capture demo USER date

CCS/AWR1642BOOST: AWR1642 GPADC

1 11
Intellectual 460 points

Part Number: AWR1642BOOST

Tool/software: Code Composer Studio

We are using SDK1.1.0.2 debugging gpadc acquisition function of external voltage, could you tell me the MmwaveLink_setGpAdcConfig () where is used to correct the output voltage value.Use the demo for high_accuracy_16xx.Error prompt during debugging: rlSetGpAdcConfig retVal=4。

  • 0
    TI__Guru 70480 points

    Hi,

    First I would request you to migrate to SDK 2.1 onward version which is currently supported by us.

    Now, first start testing the default mmwavelink test application (ti\control\mmwavelink\test) without any change, it should work and you will get the GPADC data in form of async-event.

    link_test.c: MmwaveLink_setGpAdcConfig() - invoke API to get the GPADC measurement data from RadarSS. 

    After this call RadarSS send measurement data in form of Async-event message which will be captured 

    link_test.c: MmwaveLink_asyncEventHandler() - case RL_RF_AE_GPADC_MEAS_DATA_SB: rcvGpAdcData.

    And at any point in time, you can map the return value to error type.

    mmwavelink.h: error code, 

    RL_RET_CODE_INVLD_SB_LEN                      (4U)    /* Incorrect Sub-Block Length */

    Regards,

    Jitendra

    Regards,

    Jitendra

  • 0 in reply to Jitendra Gupta
    Intellectual 460 points

    Hello, I have downloaded and debugged test on the board according to your opinion.However, due to the lower version of the board, the results show that SDK1.0 can be used correctly, while SDK2.0 will report an error.
    Debug results for SDK 1.0 is：

    Debug: Finished information related to GPADC Internal Analog Signals monitoring configurations to BSS
    Feature: Set mmWave Link GPADC Internal Analog Signals Config: Passed

    Debug results for SDK 2.0 is：

    Error: rlRfSetDeviceCfg retVal=3
    Feature: Set Async event config: Failed

    I passed the query data using a custom function, as well as the method of adding case in MmwDemo_mssMmwaveEventCallbackFxn function.

    But when the function is selected to call, an error is prompted, and the result of the error is

    I would like to ask you how I can make changes in this version, or do you have any other methods to achieve the collection and display voltage function of GPADC.Looking forward to your reply. Thank you。

    I debugged the open source code and found that the number 4 came from the rlReturnVal_t rlDriverWaitForResponse(rlUInt8_t devIndex, rlDriverMsg_t* outMsg) function in rl_driver.c, with some screenshots and their own comments as shown in the figure below