-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[db410c] 10 Second delay #20
Comments
localhost:/home/moctaviano/Downloads/Lenovo_Yoga_Tab_3_10_YT3-X50FQDL/Firmware # qdl --debug --storage emmc --include '/home/moctaviano/Downloads/Lenovo_Yoga_Tab_3_10_YT3-X50FQDL/Firmaware/' '/home/moctaviano/Downloads/Lenovo_Yoga_Tab_3_10_YT3-X50FQDL/Firmware/prog_emmc_firehose_8909_ddr.mbn' '/home/moctaviano/Downloads/Lenovo_Yoga_Tab_3_10_YT3-X50FQDL/Firmware/rawprogram_unsparse.xml' '/home/moctaviano/Downloads/Lenovo_Yoga_Tab_3_10_YT3-X50FQDL/Firmware/patch0.xml' ERROR: n = -1, errno = 19 (No such device) |
I'm finding some odd interactions with timing. I suspect it's related to the programmer (target flash stub) used. Meaning it will vary depending on SoC target.
Once the flash stub is pushed via sahara it jumps into it's entry point. Depending on the flash stub used it may need to train the DDR, etc. So completion time varies on flash stub implementation (target implementation).
The current timeout/delay: https://github.com/andersson/qdl/blob/master/firehose.c#L617
I find dropping this timeout to 500 ms works reliably. This delay corresponds to the first entry of the listed log.
Then a default configuration is sent with a big default value. In the case of the apq8016 emmc flash stub it causes a timeout after re-config. Seems it might be better to read then modify, which would eliminate this additional timeout/delay.
Delay is ~10 seconds
Putting on my factory hat - that's really expensive :)
I'll look at this a bit more later.
The text was updated successfully, but these errors were encountered: