[coreboot] flashrom issues found??

[joe at smittys.pointclark.net]

Quoting joe at smittys.pointclark.net:

>>>> So maybe there is an issue with erase_chip_jedec than??
>>>
>>> Indeed. Have you tried to erase only, then read back the result
>>> immediately? That would be very interesting. If the readback is all
>>> 0xff, try commenting out erase_chip_jedec(flash) in write_jedec() and
>>> leave the "dumb check if erase successful" in place, erase the memory
>>> with flashrom -E, wait 30 seconds, write to the memory with the flashrom
>>> version which does not call erase_chip_jedec(flash) in write_jedec(). I
>>> would be very interested in the result.
>>>
> Well, I did just want you said above and the readback is not 0xff it
> looks like a coreboot image. Then I commented out
> erase_chip_jedec(flash) in write_jedec()
> and did this:
>
> [root at localhost flashrom]# flashrom -E
> Calibrating delay loop... OK.
> Found coreboot table at 0x00000530.
> Vendor ID: RCA, part ID: RM4100
> Found chipset "ICH4/ICH4-L", enabling flash write... OK.
> NOT FOUND RCA:RM4100
> M50FW080 found at physical address 0xfff00000.
> Flash part is M50FW080 (1024 KB).
> Erasing flash chip
> [root at localhost flashrom]# flashrom -wv test.rom
> Calibrating delay loop... OK.
> Found coreboot table at 0x00000530.
> Vendor ID: RCA, part ID: RM4100
> Found chipset "ICH4/ICH4-L", enabling flash write... OK.
> NOT FOUND RCA:RM4100
> M50FW080 found at physical address 0xfff00000.
> Flash part is M50FW080 (1024 KB).
> ERASE FAILED @0, val 55!
> Verifying flash... VERIFIED.
> [root at localhost flashrom]#
>
>
> There is definatly something funky going on with
> erase_chip_jedec(flash) here. I don't think it is a GPIO or anything, I
> have them setup just like the original bios and uniflash is able to
> write to it just fine with the original bios.........please help:-(
>
>
>
>
> Thanks - Joe



Thanks - Joe