• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 173 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.

IWR6243: Possibility to embed own Meta Data in ADC Samples?

Tim Teuber
Intellectual 390 points
Part Number: IWR6243

Tool/software:

Hi Team,

i am currently working in with a System which uses multiple IWR6243 Cascaded Setups. The different CSI Signals run through multiplexers that switch between the Signals before they get to the processing unit. Is it possible to embed self defined Meta Data (for a example a self defined Chip ID) in the ADC Samples of each Frame / Chirp to get the processing unit to know which Sensor is currently transferring data. One Byte would be more than enough.

Best regards,

Tim

  • 0
    TI__Mastermind 19400 points

    Hello Tim.

    I don't know if the meta data in the ADC is easy implementation; it might involve messing around with the firmware itself.  But there is a function called rlSetAdcOutConfig that allows you to configure the ADC format and takes the deviceMap as an input, so maybe you could use this to configure the ADC formats for each device differently as way to identify which data is coming from which device?  There is documentation on this function in the rl_sensor.c file in the DFP.

    Sincerely,

    Santosh

  • 0 in reply to Santosh Krishnan
    Intellectual 390 points

    Hello Santosh,

    i am not sure if changing the ADC Output would be fitting to my needs. It seems like i can only change the sample type (real / complex) and size, which are both values I want to be consistent across all sensors. I just found the AWR_DEV_DEV_HSI_DELAY_DUMMY_CFG_SET_SB API by which i could add Delay or Dummy Data to the Chirp Data transfered via CSI. But as far as I understand the documentation, I could only define the amount of dummy data but not the precise content. One Idea that i had was to enable the Chirp Parameter Transfer and play around with different Profile IDs for each Sensorsystem (but the different Profiles have the same content)

    Sincerely,

    Tim

  • 0 in reply to Tim Teuber
    TI__Mastermind 19400 points

    Hello Tim.

    Tim Teuber said:
    I just found the AWR_DEV_DEV_HSI_DELAY_DUMMY_CFG_SET_SB API by which i could add Delay or Dummy Data to the Chirp Data transfered via CSI. But as far as I understand the documentation, I could only define the amount of dummy data but not the precise content.

    If you look for the rlHsiDelayDummyCfg_t struct, it looks like you can define the delay count, delay val, and dummy count for the dummy data like you said, but could you not make this unique for each device?  It would ultimately achieve what you are trying to accomplish, even if you can't specifically define the dummy data itself.

  • 0 in reply to Santosh Krishnan
    Intellectual 390 points

    Hi Santosh,

    yes this maybe could be an option. But i have to test if the different Frame Sizes resulting from this could cause problems with the CSI Receiving Unit i am using. But if it works this is a good workaround.

    Thanks,

    Tim

  • 0 in reply to Tim Teuber
    TI__Mastermind 19400 points

    No problem.  Feel free to post new E2E questions if you have any other questions!

    Sincerely,

    Santosh