Re: Google Embedded Controller blob - how does that get to the EC?

> Since my MrChromebox firmware does not use vboot, I have ported the EC-RW firmware update code from vboot to coreboot, and check if an EC-RW update is needed on each boot as part of EC init in ramstage. This code is in my tree on github for inspection.

Well, there are over 100 files named "ramstage.c" in the github repository.

Do I understand correctly that the MrChromebox firmware generated will have a custom ramstage, different from the stock coreboot ramstage, just to check if an EC-RW update is needed? Coreboot would not typically try to do that? 

> It's not necessary to build your own EC-RW firmware or even update it unless there's a specific issue you're trying to resolve.

But still, to play-around with different payloads, using mostly stock coreboot, the EC firmware could just be completely left out of the coreboot ROM image?

And, if I still needed to update the EC firmware, I could use the Google flashrom fork, as in the Google example, just: flashrom -p internal:bus=lpc -w ec.bin ?

_______________________________________________
coreboot mailing list -- [email protected]
To unsubscribe send an email to [email protected]