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

AWR1642: Power Consumption and Measurements

Antonio Faggio
Expert 7960 points
Part Number: AWR1642
Other Parts Discussed in Thread: IWR1443, MMWAVE-SDK

Hello All,

My customer has some concerns after using AWR1642.

He was present at mmwave seminar.

Customer is testing AWR1642, but this does not have a sleep function that greatly reduces the consumption (the ideal is to have a sleep mode with consumption much lower than 1mA or a function of switch-on much faster.

This is the biggest limit for customer right now.

May be IWR1443 can reduce consumption in a significant way?

These are the measurements customer found:


Total duration of start, setting and measurement of radar board: 440ms
There is a second time that could be associated with the actual measure, equal to 95ms.
So it may be that about 340ms of difference are just for the start and configuration of the system, and disappear in the presence of a sleep.

Any comments/advice here?

Many Thanks,

Antonio

  • 0
    TI__Guru 69990 points

    Hi Antonio,

    Currently, there is no sleep mode available in AWR1642 what you are looking for, although there are few workarounds to minimize the system configuration duration.

    1. If the customer is using the mmwave layer from mmWave-SDK in the application then better to remove this layer and use directly mmWaveLink to configure RadarSS. Please refer TI-Rex Non-OS application which uses directly mmWaveLink from DSS and removed mmWave from MSS & DSS core.

    2. Use inbuilt configuration parameters instead of receiving over CLI.

    3. Removing the OS from DSS core will minimize the image size significantly which effectively has the direct effect on Application bootup time from sFlash.

    4. Combine multiple sub-ID of mmwavelink API into single API which is having same Msg-ID will reduce multiple Mailbox communication from DSS to RadarSS to a single call. RadarSS supports max size of 2KB of message size from MSS/DSS core but for this customer needs to modify mmWaveLink to combine multiple Sub-ID of same Msg-ID into single packet. (mmwavelink.h: RL_EXTENDED_MESSAGE).

    Regards,

    Jitendra