Thank you for the hint, I have 'installed' cbmem by making tthe appropriate menuconfig changes and in util/cbmem "$make LD_FLAGS=-static". Though (and I apologize for my nieve-ness) how exactly to I use the "$ cbmem -c" command, specifically wher exactly in boot/start up process should I call it- I cant call it from the OS, and I haven't been able to find anything on google relating to how to access coreboot userspace...
HN ________________________________________ From: Idwer Vollering vidwer@gmail.com Sent: Wednesday, December 14, 2016 5:46 PM To: Haleigh Novak Cc: coreboot@coreboot.org Subject: Re: [coreboot] post_code to text file
cbmem, in util/cbmem/, should be what you are looking for.
2016-12-15 2:35 GMT+01:00 Haleigh Novak haleigh@edt.com:
Hello All,
I was wondering if it would be possible to add a few lines in the post_code method so it also writes all the codes to a text file and then keep that text file around so it could be read once the system is running - for debugging purposes because a post_code reader is currently unavailable to me. I know that the BIOS handles the post codes and my chosen BIOS is coreboot and I have added just a couple lines to the post code method right after mainboard_post() is called in order to print the codes to a file in / as well. But I don't have any idea how to pass a small text file along from coreboot up to yocto jethro during boot - is this even possible?
Any comments, thoughts, ideas, guidance would be greatly appriciated. Thank you.
HN
-- coreboot mailing list: coreboot@coreboot.org https://www.coreboot.org/mailman/listinfo/coreboot
Haleigh Novak wrote:
how exactly to I use the "$ cbmem -c" command, specifically where exactly in boot/start up process should I call it-
Not at all. Run cbmem once you have booted Linux.
I cant call it from the OS,
Why not?
I haven't been able to find anything on google relating to how to access coreboot userspace...
There isn't really any such thing. coreboot does minimal hardware init and is then eager to get out of the way, letting your OS run.
//Peter