We measure in our sys time, after button wake-up to get LCM icon words where we put icon write to LCM in
hello_sensor_create() and once after I2C init, it takes about 4~5sec to get that word.
It may be not common and rational to user. Is any possible newer SDK to improve this or any possibility
to have customer build at lower SDK side to do the plot after wake up. Then it may solve the current problem
our testing report. TKS.
he suggests us to modify BCM20737A1.cgs with adding below,
ENTRY "I2C Speed"
"Speed" = "400 KHz" or 800K/1M.
to increase power-on speed by using SDK2.2.1.
After testing, it seems it's workable to reduce 1~2sec, however, from previous investigation
with BrCM, the delay is due to some SDK buffering for loading patch/codes. It seems
there is a conflict after using I2C modification. Any idea about it?
So is it ok for us to configure it like that?
No issue at all, our datasheet also specified 400KHz as one of the supported speeds.
Thanks, so we will configure 400K as the init setting and
after app. FW gets the hand, we will re-tune it lower for I2C-compatible devices.
However, based on 400K setting, boot time is still around at 2~3 sec by checking.
he estimates at 1 sec (no buffering at all now?) and can we try to reduce to near 1s?