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.

IWR1443BOOST: code for boot and load time in high accuracy lab?

Part Number: IWR1443BOOST

Hi Michelle,

Could you tell us which section of the code in "high accuracy lab" set the boot and the image loading time of IWR1443boost (time for setting the hardware)? the first frame time now is around 310ms during the power on, the frame time is about 35ms with our chirp profile after the first frame time, we try to reduce the time for the first frame for our application

Thanks and best regards,

  • Feng,

    The boot and image loading is part of the device power up. Boot and images are transferred through QSPI to the chip. The frame however is after sensor start which means boot and images have been loaded. For the chirp configuration, frame period is always fixed. I guess by "first frame" you mean to include power up sequence? Please confirm.

    Thanks!
    Regards,
    Michelle
  • Hi Michelle,
    Yes, the first frame time include the power up sequence, that is recorded from the power "on" to the first data has been transferred. When I run the level_sense_demo, the boot time 157 ms, config time 57 ms, I am wondering how to achieve this in high_accuracy_lab.

    Thanks and best regards,
  • Feng,

    For level sensing demo, my understanding is that work has been done in terms of reducing binary size to increasing QSPI speed. I'll ask our level sensing expert to comment on this.

    Thanks and Regards,
    Michelle

  • Hi Feng,

    Here's what I found from our level sensing expert. The following was done to reduce power consumption:

    1. Power on sequence can be modified to save on power-on power consumption: Replace power up scheme -- different PMIC, replace the LDO with ferrite beads. See swra577 www.ti.com/.../swra577.pdf for Low Cost LC Filter Solution.
    2. The calibration on the first frame is usually long. To reduce it, there's a calibration step in level sensing and the result was save into QSPI. Therefore each time calibration parameters are directly loaded in and the calibration time is significantly reduced.

    If you have any question in terms how that's handled, please issue ticket related to level sensing demo.

    Thanks and Regards,
    Michelle
  • Thanks Michelle!