• State Answer Suggested
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 34 subscribers
  • Views 516 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.

IWRL6432: ADC Buffer Control Registers

Daniel
Prodigy 205 points
Part Number: IWRL6432


Tool/software:

Hi TI experts,

I am using SDK 5.4.0.1, and in the mmwave_control_config.c file for motion and presence detection, there is CSL_FINS(ptrAdcBufCtrlRegs->ADCBUFCFG1, APP_HWA_ADCBUF_CTRL_ADCBUFCFG1_ADCBUFCFG1_RX0EN, 0);. However, the IWRL6432 TRM does not have the ADCBUFCFG1 Register Field Descriptions, and I cannot find the file where APP_HWA_ADCBUF_CTRL_ADCBUFCFG1_ADCBUFCFG1_RX0EN is defined.

Is there any document that contains the field description for each ADC buffer register and in which file is APP_HWA_ADCBUF_CTRL_ADCBUFCFG1_ADCBUFCFG1_RX0EN defined?

Best regards,
Daniel

  • 0
    TI__Genius 9870 points

    Hi Daniel,

    Please allow me some time till early next week to follow up with you on this query.

    Regards

    Ankit

  • 0 in reply to Ankit Mohanty
    TI__Genius 9870 points

    Hi Daniel,

    Could you please recheck the TRM. I could find the below description in section 8.1 Functional Description of ADC Buffer.

    ADCBUFCFG1_RX0EN will be Enable for Rx0 write. 

    Regards

    Ankit

  • 0 in reply to Ankit Mohanty
    Prodigy 205 points

    Hi Ankit,

    Let me clarify my questions again:

    1. Is there any document that describes the ADCBUFCFG1, ADCBUFCFG2, ADCBUFCFG3, and ADCBUFCFG4 register field descriptions, similar to Table 4-735. ADCBUFCFG1 Register Field Descriptions in the SWRU522E TRM?

    2. In which file in the source code is APP_HWA_ADCBUF_CTRL_ADCBUFCFG1_ADCBUFCFG1_RX0EN defined?

    Best regards,
    Daniel

  • 0 in reply to Daniel
    TI__Genius 9870 points

    Hi Daniel,

    Please allow us 24 hours to get back to you. I have passed the thread to the software expert.

    Regards

    Ankit

  • 0 in reply to Daniel
    Prodigy 107 points

    Hi Daniel,

    Mostly commenting as I am having a similar challenge to you.

    I suspect the file you're looking for is {SDK_LOCATION}/source/drivers/adcbuf/v0/cslr_app_hwa_adcbuf_ctrl.h

    I have been using this file alongside SWRU522E to determine the functionality of each field. Though I currently haven't had much success with this route. Hopefully an updated TRM for the IWRL6432 is on its way...

  • 0 in reply to Daniel
    Prodigy 107 points

    Hi Daniel,

    I've made a bit more progress on understanding the registers today. There are XML files describing the registers in the following folder;

    MMWAVE_L_SDK_05_05_00_02\tools\device_csp\xwrl64xx

    You'll see APP_HWA_ADCBUF_CTRL.xml in there. 

    A more legible version can be accessed via the CCS debugger. When connected to the board (with a breakpoint set up in the code). Go to View > Registers. Typically used to view the register values whilst debugging, but it also includes a description for them from the XML files. On here you can navigate to APP_HWA_ADCBUF_CTRL and you'll find a description for the register fields you're after.

  • 0 in reply to Peter Adams
    Prodigy 205 points

    Hi Peter,

    I tried referencing the contents of cslr_app_hwa_adcbuf_ctrl.h together with SWRU522E, but found that there are still some differences between the 6432 and 6843 in the ADC buffer control.

    Based on your description, it indeed solves my current problem, thank you. However, this also highlights the insufficiency of the TI documentation. I hope TI can provide a more complete 6432 TRM soon.

    Best regards,
    Daniel

  • 0 in reply to Daniel
    TI__Mastermind 21511 points

    Hi Daniel, 

    Thanks for the feedback on the TRM documentation. I'll make sure it gets passed along to the relevant folks. I think your question is answered so I will close the thread for now. If your question is not answered you can reply here and the thread will reopen. 

    Best Regards,

    Josh