• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 30 subscribers
  • Views 800 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.

AWR1443Boost: How can I fix radiation-related parameters to pass the governmental certification test ?

user4916662
Prodigy 120 points
Part Number: AWR1443BOOST
Other Parts Discussed in Thread: AWR1443

Thank you, support team.

This question may be very and very important for all the people who wish to drive AWR1443Boost in public space.

I myself plan to drive it in an exhibition this year.

In such case, in every country, we mush receive certifications from the government.

And in order to pass the tests, we must prove

radiation-related parameters of AWR1443Boost are fixed and protected inside the firmware.

We must prove they will not change by any config files with careful parameter values.

In my understanding, such parameters of AWR1443Boost are determined

inside "CLI_open" function in "radarss".

It's not opened to us and we cannot customize it.

So, how can I fix such parameters and pass the certification tests ?

  • 0
    TI__Guru 58035 points
    Hello ,
    All the chirp parameters, TX power etc. are controllable from the user via his embedded code you develop on the R4F cortex core of AWR1443. The radarss does all the configurations based on the values passed to it via these APIs. As long as your code is fixed the configuration would remain the same.

    regards,
    Vivek
  • 0 in reply to Vivek Dham
    Prodigy 120 points
    I'm sorry. I don't think so.
    I imagine you mentioned to the functions like the bellow one in the SDK examples.

    bool MmwDemo_parseProfileAndChirpConfig(MmwDemo_DataPathObj *dataPathObj);

    But in such function, the code only read and parse the config file parameters.
    I have never seen the code writes back any parameter to the chip.

    For example, the "start frequency" (normally somewhere around 76-77GHz) will influence many internal parameters.
    It's very dangerous to change any parameters without knowing the safe examples.
    How can I change such parameters safely ?
  • 0 in reply to user4916662
    TI__Guru 58035 points
    Hello,
    These parameters are parsed from the config file and then programmed back to the AWR device. For example the "CLI_MMWaveProfileCfg" function in the demo application sets the chirp profiles where you can set parameters that impact the emissions and regulatory parameters. These include chirp start frequency , TX start time , chirp time/slope , TX power backoff etc. You can adjust these parameters incase there are any issue with emissions.

    Regards,
    Vivek
  • 0 in reply to Vivek Dham
    Prodigy 120 points
    Dear Vivek,

    I have read only CCS examples before.
    After hearing about "CLI_MMWaveProfileCfg", I dived deeply into the sources of the SDK components, and found it.
    Thank you.
  • 0 in reply to user4916662
    TI__Guru 58035 points
    Hello,
    I hope this helped resolve your query regarding the programmability options for passing the regulatory standards ?

    Regards,
    vivek