On Sat, Oct 19, 2019 at 05:53:12PM +0200, Cédric Le Goater wrote: > On 19/10/2019 17:31, Marty E. Plummer wrote: > > On Sat, Oct 19, 2019 at 03:46:59PM +0200, Cédric Le Goater wrote: > >> On 18/10/2019 19:28, Marty E. Plummer wrote: > >>> Hello, > >>> > >>> First off, thank you for the work you've done on the ppc64 support, it > >>> has been very useful. I'm currently working on a coreboot port for the > >>> talos ii line of systems (which means more ppc64 support, support > >>> specifically for the power9 sforza chip, and specific mainboard support. > >>> My plate is very full lol) and have been using qemu to debug the > >>> bootblock. > >>> > >>> It has been very useful for that, but I'm now at the point where I need > >>> to jump to romstage, and that's where it gets tricky. qemu parses the rom > >>> image and looks for a ffs header, locates skiboot on it, and jumps > >>> straight > >>> to that. Not exactly ideal for debugging something not produced from > >>> op-build. > >> > >> yes. I suppose you are using my branch powernv-4.2 which adds PNOR support > >> and a way to boot directly from PNOR. In that case, QEMU parses the PNOR > >> file to extract the PAYLOAD partition (skiboot). skiboot also detects the > >> flash and extract the kernel and initramfs from the PNOR. > >> > >> However, you can bypass all this internal boot process by simply passing > >> a -bios option and not passing a MTD device. > >> > > Doing so gives me the following error: > > qemu-system-ppc64: Could not load OPAL firmware 'build/coreboot.rom' > > (this is after I patched the 4mb size limit up) > > Could you make that rom available ? > Sure, I think. Not sure about how sending files works in my current mail client but will see. Its more or less a 'stock' (as stock as can be for a new coreboot target) coreboot.rom file, but I've added some logic into the build to fake a pnor ffs header at the end in order to trick hostboot bootloader into loading it. > Thanks, > > C.
coreboot.rom.gz
Description: Binary data