assuming you've built with CONFIG_COLLECT_TIMESTAMPS=y, you can build/run the cbmem utility and see how long each stage/section of coreboot is taking (up to the point of handing off control to the payload). 30s to boot sounds like either you're not caching the RAM training data (MRC cache) and therefore redoing RAM training each time, or outputting the boot console to a non-existent serial port (which can slow everything down). Whatever it is, looking at the timestamps will go a long way towards identifying the issue
On Sat, Aug 11, 2018 at 2:13 AM Antony AbeePrakash X V < AntonyAbee.PrakashXV@lnttechservices.com> wrote:
Hi,
We have developed a coreboot image for Apollo lake custom board. The time taken for boot up is around 30 seconds.
We would like to reduce the boot time as much as possible.
Following codes are removed:
Non-intel Apollolake specific codes in below folders
- Arch
- Soc
- Mainboard
- Vendorcode
Splash screen loading
SPI support – other than our custom board SPI.
Also we have disabled the COMPRESS_RAMSTAGE. Still we are not able to reduce the boot time.
Please suggest the methods to reduce the boot time.
Thanks & Regards,
Antony
*L&T Technology Services Ltd*
www.LntTechservices.com http://www.lnttechservices.com/
This Email may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system. -- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot