I've found out that commit that broke down compatibility with my old Coreboot was:
libpayload/libc/console: Flush input driver buffer on init https://review.coreboot.org/#/c/coreboot/+/19345/
If I revert it with the newest Coreboot, payloads (coreinfo/nvramcui) will work with my old Coreboot version.
Best regards, Aladyshev Konstantin
-----Original Message----- From: Аладышев Константин [mailto:aladyshev@nicevt.ru] Sent: Thursday, January 18, 2018 1:02 PM To: 'Coreboot' Subject: Re: Link layer between "coreboot" - "seabios" - "coreinfo/nvramcui"
Last lines of log from SeaBIOS:
Run img/coreinfo.elf Segment 45444f43 48469@0xfff6a770 -> 405328@0x00100000 Uncompressing data 48469@0xfff6a770 to 405328@0x00100000 Calling addr 0x00100000
Best regards, Aladyshev Konstantin
-----Original Message----- From: Аладышев Константин [mailto:aladyshev@nicevt.ru] Sent: Thursday, January 18, 2018 12:35 PM To: 'Coreboot' Subject: Link layer between "coreboot" - "seabios" - "coreinfo/nvramcui"
Hello! I have a project for my motherboard with coreboot version that I fixed couple years back (so it is pretty old), and now I want to update all payloads to most modern ones. There is no problem with SeaBIOS, but coreinfo and nvramcui don't work. When I try to jump to them from SeaBIOS, nothing happens and screen turns black. So... what is the link layer between those payloads and coreboot? Layer that I should also update for those new payloads to work fine?
Don't forget, this it is not only video problem, there is no output from COM also. So maybe it is connected to CBFS or payload format? What should I check?
Best regards, Aladyshev Konstantin