-
-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Anyone with any experience on increasing SPI size? #547
Comments
This is probably a good place to start https://www.coreboot.org/Board:lenovo/x220#Bigger_SPI_ROM My problem was my SPI was a different manufacturer. Despite changing the correct parts of the ROM to use the new chips identifiers and sizes. i got some Winbonds on backorder and will update this when i figure it out. closing for now |
So this was achieved. My P8H61-m pro now rocks coreboot on a 16MB SPI. There was a problem using the method linked above, but the correct result was not far off. A word of warning, when using ifdtool to --newlayout, it likes to copy the data not just adjust the layout. Which means if you build a 16MB coreboot image and then ifdtool the layout, you are likely going to get a CBFS full of nothing but 0xFF What i did was as follows;
Voila. One 16 MB capacity upgrade. Note: you may want to play with the CBFS size rather than stick with the standard. Mainboard->Size of CBFS filesystem in ROM coreboot menu item. I set mine to CONFIG_CBFS_SIZE=0x700000 |
Following on from #545 im trying to get a larger SPI chip working with the P8H61-M Pro. Swapping out the chip and setting coreboot to a 16mb image, along with modification of the VSCC table to include the new JID0 does not seem to be working well for me. have validated opcodes and granularity in VSCC0 are correct.
Does anyone have any pointers or references they could point me to? I thought id ask here before asking upstream in coreboot.
thanks folks.
The text was updated successfully, but these errors were encountered: