On 17.09.21 01:41, Andreas Bauer wrote: > Am Fri, Sep 17, 2021 at 01:18:53AM +0200 schrieb Nico Huber: > >> On 16.09.21 17:29, Andreas Bauer wrote: >>> May I suggest the best way forward would be to compile coreboot with >>> debug options and go ahead and flash it. You will find out quickly >>> where the issues are. Obviously backup your current rom ! >> >> Not likely, but you can harm the hardware with such brute-force testing, >> see about GPIOs below. > > Thanks for that heads up. I guess I was just lucky, but when you don't have > schematics, lack experience in hardware development and such, the best I > could do was this "brute force" testing. > > My impression was that the OP is in the same situation as I was (missing > knowledge), and in my case I decided to go ahead and try and eventually > archieved some success.
Don't worry, it's still what most people do. Even with documentation at hand not everything always works out, so we all resort to some trial-by- error at some point. I just wanted to point out that there is at least one point (GPIOs) to always be careful about ;) > > I did delete the GPIO config, though, and good for bringing that up as I > failed to mention that. > >>> - read vendor bios and extract descriptor.bin and me.bin from it >>> (util/ifdtool -x vendor.bios) >> >> Always good to keep a backup, but you don't need to extract these for >> coreboot. Just keep them where they are in flash, no need to extract >> /overwrite anything. > > Well, if you want to clean the ME you obviously need that. I found it > easier to always produce a complete image that can just be flashed as > a whole. Yes, it can be useful eventually of course. But for a start and during coreboot development, we advice to change as little as possible outside of coreboot. Otherwise, it's hard to find out where a problem persists if something doesn't work. Nico _______________________________________________ coreboot mailing list -- [email protected] To unsubscribe send an email to [email protected]
