Hi...
But in the data sheet they have mentioned like the SST49LF00xB detects whether it is being
accessed via a FWH or LPC protocol by detecting the START field contents; a 1101b or 1110b
indi-cates a Firmware Memory cycle and a 0000b indicates an LPC memory cycle.
but when i checked the content in the empty SST chip it shows like this
[root at localhost ~]# hexdump sst_after_erase.binfrom this i came to know that SST chip is working in LPC mode as
0000000 ffff ffff ffff ffff ffff ffff ffff ffff
*
0080000
Hello,
But the content after writing by using below command shows result like this....
[root@localhost ~]# /usr/local/sbin/flashrom -r | hexdump
0000000 6143 696c 7262 7461 6e69 2067 6564 616c
0000010 2079 6f6c 706f 2e2e 202e 4b4f 0a2e 6f4e
0000020 6320 726f 6265 6f6f 2074 6174 6c62 2065
0000030 6f66 6e75 2e64 460a 756f 646e 6320 6968
0000040 7370 7465 2220 4956 2041 5456 3238 3733
0000050 2c22 6520 616e 6c62 6e69 2067 6c66 7361
0000060 2068 7277 7469 2e65 2e2e 4f20 2e4b 530a
0000070 5453 3934 464c 3030 4134 422f 6620 756f
0000080 646e 6120 2074 6870 7379 6369 6c61 6120
0000090 6464 6572 7373 3020 6678 6666 3038 3030
00000a0 2e30 460a 616c 6873 7020 7261 2074 7369
00000b0 5320 5453 3934 464c 3030 4134 422f 2820
00000c0 3135 2032 424b 2e29 450a 7272 726f 203a
00000d0 6f4e 6620 6c69 6e65 6d61 2065 7073 6365
00000e0 6669 6569 2e64 000a
00000e7
************************************
But using only hexdump i got result like this ...
[root@localhost ~]# hexdump sst_after_write05.bin
0000000 ffff ffff ffff ffff ffff ffff ffff ffff
*
0080000Thanks.
Malatesh
On 04/04/2008, malatesh kamatad <malateshkamat@gmail.com> wrote:Ya .. after checking that file i got result like this ...it shows that there is a content in that file
[root@localhost ~]# hexdump sst_after_erase.bin
0000000 ffff ffff ffff ffff ffff ffff ffff ffff
*
0080000
I think erasing is not happened properly..
Thanks..
malateshOn 04/04/2008, Corey Osgood <corey.osgood@gmail.com> wrote:Ok, so if you open up the sst_after_erase.bin with a hex editor, is there anything in it? Does that match the data from the diff, or is it a binary ORing of the data from the diff? Do you have any other flash chips you can try on the board?
On Fri, Apr 4, 2008 at 8:41 AM, malatesh kamatad <malateshkamat@gmail.com> wrote:Ya i got result like this after comparing
[root@localhost ~]# diff -us original.bin sst_after_write.bin
Binary files original.bin and sst_after_write.bin differ
but its showing that there is a difference in between to files ....
i think write is not happening proper ....
Thanks .
malateshOn 04/04/2008, Corey Osgood <corey.osgood@gmail.com> wrote:what's the output of diff -us original.bin sst_after_write.bin? Can you download the bios from the manufacturer and see if flashing that works?
-Corey
On Fri, Apr 4, 2008 at 7:03 AM, malatesh kamatad <malateshkamat@gmail.com> wrote:
I worked with the step by step this is the output......--
[root@localhost ~]# flashrom -r original.binPm49FL004 found at physical address 0xfff80000.
Calibrating delay loop... OK.
No coreboot table found.
Found chipset "VIA VT8237", enabling flash write... OK.
Flash part is Pm49FL004 (512 KB).
Reading Flash...done[root@localhost ~]# flashrom -r sst_after_erase.bin
[root@localhost ~]# flashrom -E
Calibrating delay loop... OK.
No coreboot table found.
Found chipset "VIA VT8237", enabling flash write... OK.
SST49LF004A/B found at physical address 0xfff80000.
Flash part is SST49LF004A/B (512 KB).
Erasing flash chip[root@localhost ~]# flashrom -w original.bin
Calibrating delay loop... OK.
No coreboot table found.
Found chipset "VIA VT8237", enabling flash write... OK.
SST49LF004A/B found at physical address 0xfff80000.
Flash part is SST49LF004A/B (512 KB).
Reading Flash...done[root@localhost ~]# flashrom -r sst_after_write.bin
Calibrating delay loop... OK.
No coreboot table found.
Found chipset "VIA VT8237", enabling flash write... OK.
SST49LF004A/B found at physical address 0xfff80000.
Flash part is SST49LF004A/B (512 KB).
Flash image seems to be a legacy BIOS. Disabling checks.
Programming page: 0007 at address: 0x00070000Thanks,
Calibrating delay loop... OK.
No coreboot table found.
Found chipset "VIA VT8237", enabling flash write... OK.
SST49LF004A/B found at physical address 0xfff80000.
Flash part is SST49LF004A/B (512 KB).
Reading Flash...done
Malatesh.On 04/04/2008, malatesh kamatad <malateshkamat@gmail.com> wrote:Hi..
We are having two BIOS i.e, PM49FL004( motherboard's BIOS) and empty flashrom
SST49LF004B ..
We are trying to flash the content of PM49FL004 to SST49LF004B flashrom
according to your suggestion we have done ..we are getting output as bellow..
[root@localhost ~]# flashrom -E
Calibrating delay loop... OK.
No coreboot table found.
Found chipset "VIA VT8237", enabling flash write... OK.
SST49LF004A/B found at physical address 0xfff80000.
Flash part is SST49LF004A/B (512 KB).
Erasing flash chip
Erasing page: 0007 at address: 0x00070000
[root@localhost ~]# flashrom -r malateh.bin
Calibrating delay loop... OK.
No coreboot table found.
Found chipset "VIA VT8237", enabling flash write... OK.
SST49LF004A/B found at physical address 0xfff80000.
Flash part is SST49LF004A/B (512 KB).
Reading Flash...done
[root@localhost ~]# flashrom -w malateh.bin
Calibrating delay loop... OK.
No coreboot table found.
Found chipset "VIA VT8237", enabling flash write... OK.
SST49LF004A/B found at physical address 0xfff80000.
Flash part is SST49LF004A/B (512 KB).
Flash image seems to be a legacy BIOS. Disabling checks.
Programming page: 0007 at address: 0x00070000
[root@localhost ~]# flashrom -v malateh.bin
Calibrating delay loop... OK.
No coreboot table found.
Found chipset "VIA VT8237", enabling flash write... OK.
SST49LF004A/B found at physical address 0xfff80000.
Flash part is SST49LF004A/B (512 KB).
Flash image seems to be a legacy BIOS. Disabling checks.
Verifying flash... VERIFIED.
After that we tried to boot the system by SST49lf004B but system is not rebooting....
So we want to flash the content of the Pm49fl004 to SST49lf004 so that our system can boot
using SST49lf004....
thanks,
Malatesh..
On 04/04/2008, bari <bari@onelabs.com> wrote:Try Peters suggestion of reading the flash after an erase and see what is there.
If it is erased, read back after you have tried to write and compare.
See what is or is not happening.
-Bari
malatesh kamatad wrote:
Hi...
I am working on ASRock motherboard .....in FWH mode...
with regards.
Malatesh
On 03/04/2008, *bari* <bari@onelabs.com <mailto:bari@onelabs.com>> wrote:
malatesh kamatad wrote:
Hi all..
I have worked with PM49fl00x.diff patch ,its worked fine
and i got the output as below
The PM49fl00x can work in LPC and FWH modes. Do you know which
mode is being used?
What mainboard did you test this in?
Now i am working on SST49LF004B 33-4C-NHE
0710022-CA with the
motherboard K8Upgrade-VM800
The flashrom detect flash device on this
board, But the erasing and writting operation is not happening
properly
hier flashrom output :
Is this the board by ASRock?
-Bari
coreboot mailing list
coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot