• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 621 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.

AWR6843AOP: GPADC VSENSE

Alessandro Schembri
Prodigy 170 points
Part Number: AWR6843AOP
Other Parts Discussed in Thread: IWR6843, ALP, IWR6843ISK

Hi,

In my project on both MSS and DSS I'm using the "mmWave API" (MMWave_init, MMWave_open, ...)
Now I need to read the GPADCx values so I'm trying to use the "mmWaveLink Framework" calling the following api: rlRfAnaMonConfig() and rlRfExtAnaSignalsMonConfig()
The function rlRfAnaMonConfig() returns the error RL_RET_CODE_ANALOG_MONITOR_NOT_SUPPORTED and in the callback function programmed with MMWave_init() no "RL_RF_ASYNC_EVENT_1_MSG" event is received.
Reading better the documentation there is written "This API is not supported in IWR6843 ES1.0".
I'm using the SDK 3.5

Is there any possibility to read the GPADC6/VSENSE input?

Thanks in advance

  • 0
    Prodigy 170 points

    My device is ES2.0 so it seems that should be supported

    If I call the funcitons "rlRfAnaMonConfig() and rlRfExtAnaSignalsMonConfig()" immediately before or after MMWave_open I see the error RL_RET_CODE_ANALOG_MONITOR_NOT_SUPPORTED.
    If I move the calling before MMWave_start i don't have any more the error, but I don't receive the event RL_RF_ASYNC_EVENT_1_MSG.
    Do you have any idea where I'm wrong?

  • 0 in reply to Alessandro Schembri
    TI__Mastermind 23725 points

    Hello

    Can you please list the exact device on the EVM - please look at the Errata for the device to understand the device marking on the EVM.

    As you have notice the Analog signal monitoring is only available on devices that support safety monitoring mechanism we will confirm and get back to you based on the device variant on the board in hand if this operation is supported.

    Thank you,

    Vaibhav

  • 0 in reply to Vaibhav Mahimkar
    Prodigy 170 points

    For current project I'm using this chip: XAWR6843 BG ALP 09ZCMX9 (see photo)
    In another project to see if the chip was "safety compliant" I read the register 0xFFFFe214.

    In that case the value was 0x014540CD while for this chip is 0x03CD40CD

    On my TI evaluation board with IWR6843ISK I read 0x038940CC

  • 0 in reply to Alessandro Schembri
    TI__Genius 17265 points

    Hi,

    So the External signals monitor through GPADC is part of the analog/rf periodic monitoring and tis therefore only allowed on safety-enabled devices. 

    However, you can perform basic GPADC read of the external signals on both Safety and QM devices. Refer to the sub block 0x02D0 AWR_RF_GPADC_CFG_SET_SB in the ICD.

    • When frames are not running, issuing this API would perform the GPADC read in the idle loop of the BSS fireware and report the data in an ASYNC event.
    • When frames are running, issuing this API would schedule the GPADC read to occur in the inter-burst idle time and will be reported in an ASYNC event.


    Let me know if you have any further questions.

    Best Regards,
    Alec

  • 0 in reply to Alec May
    Prodigy 170 points

    Hi,

    Is there a method (API, memory address) to check (at startup) if the device under test has the "safety-enabled" ?

    Thanks a lot

  • 0 in reply to Alessandro Schembri
    TI__Genius 17265 points

    Hi,

    So if you go to <SDK_Location>\packages\ti\drivers\soc\src\soc.c , you can look at the function "SOC_getDevicePartNumber". However, this function does NOT grab the safety bit (Bit 0). You can however look at this function as an example of how to view the safety bit. 

    Let me know if you have any further questions.

    Best Regards,
    Alec