flashrom

flashrom@flashrom.org

3 participants
9188 discussions

Re: [flashrom] [commit] r695 - trunk
by Carl-Daniel Hailfinger 20 Aug '09

20 Aug '09

On 20.08.2009 20:45, svn(a)flashrom.org wrote: > Author: uwe > New Revision: 695 > > Mark the following boards as non-working for now: > > - ASRock K7VT4A+ (reported by Udu Ogah <putlinuxonit(a)gmail.com>) > Chipset detect, but no chip. > Needs board enable. It's so old that it has parallel flash which sometimes needs the write line enabled to respond to ID commands. > - ASUS M2N68 (reported by Udu Ogah <putlinuxonit(a)gmail.com>) > Chipset detect, but no chip. > Needs nForce SPI support, so it's not a board problem. Please remove again. Regards, Carl-Daniel -- http://www.hailfinger.org/

1 0

[commit] r695 - trunk
by svn＠flashrom.org 20 Aug '09

20 Aug '09

Author: uwe Date: 2009-08-20 20:45:18 +0200 (Thu, 20 Aug 2009) New Revision: 695 Modified: trunk/board_enable.c trunk/print.c Log: Various board status updates (trivial). Mark the following boards as OK (no board-enable needed): - Tyan S2466 (reported by Oliver Niesner <oli(a)servebbs.net>) http://www.flashrom.org/pipermail/flashrom/2009-August/000211.html Mark the following boards as non-working for now: - ASRock K7VT4A+ (reported by Udu Ogah <putlinuxonit(a)gmail.com>) Chipset detect, but no chip. - ASUS M2N68 (reported by Udu Ogah <putlinuxonit(a)gmail.com>) Chipset detect, but no chip. - ASUS A7V600-X (reported by Udu Ogah <putlinuxonit(a)gmail.com>) Chipset and chip detected, writes don't work. Board-enable required. Also, add some missing board URLs and fix incorrect board names. Signed-off-by: Uwe Hermann <uwe(a)hermann-uwe.de> Acked-by: Uwe Hermann <uwe(a)hermann-uwe.de> Modified: trunk/board_enable.c =================================================================== --- trunk/board_enable.c 2009-08-19 15:19:18 UTC (rev 694) +++ trunk/board_enable.c 2009-08-20 18:45:18 UTC (rev 695) @@ -637,7 +637,7 @@ } /** - * Suited for A-Open vKM400 AM-S: VIA KM400 + VT8237 + IT8705F. + * Suited for AOpen vKM400Am-S: VIA KM400 + VT8237 + IT8705F. */ static int board_aopen_vkm400(const char *name) { @@ -866,7 +866,7 @@ } /** - * Suited for Asus P4P800-E: Intel Intel 865PE + ICH5R. + * Suited for Asus P4P800-E Deluxe: Intel Intel 865PE + ICH5R. */ static int board_asus_p4p800(const char *name) { @@ -918,7 +918,7 @@ {0x8086, 0x1130, 0, 0, 0x105a, 0x0d30, 0x105a, 0x4d33, "acorp", "6a815epd", "Acorp", "6A815EPD", board_acorp_6a815epd}, {0x1022, 0x746B, 0x1022, 0x36C0, 0, 0, 0, 0, "AGAMI", "ARUMA", "agami", "Aruma", w83627hf_gpio24_raise_2e}, {0x1106, 0x3177, 0x17F2, 0x3177, 0x1106, 0x3148, 0x17F2, 0x3148, NULL, NULL, "Albatron", "PM266A*", board_epox_ep_8k5a2}, - {0x1106, 0x3205, 0x1106, 0x3205, 0x10EC, 0x8139, 0xA0A0, 0x0477, NULL, NULL, "AOpen", "vKM400 AM-s", board_aopen_vkm400}, + {0x1106, 0x3205, 0x1106, 0x3205, 0x10EC, 0x8139, 0xA0A0, 0x0477, NULL, NULL, "AOpen", "vKM400Am-S", board_aopen_vkm400}, {0x1022, 0x2090, 0, 0, 0x1022, 0x2080, 0, 0, "artecgroup", "dbe61", "Artec Group", "DBE61", board_artecgroup_dbe6x}, {0x1022, 0x2090, 0, 0, 0x1022, 0x2080, 0, 0, "artecgroup", "dbe62", "Artec Group", "DBE62", board_artecgroup_dbe6x}, {0x1106, 0x3189, 0x1043, 0x807F, 0x1106, 0x3177, 0x1043, 0x808C, NULL, NULL, "ASUS", "A7V8X", board_asus_a7v8x}, @@ -1022,6 +1022,7 @@ { "T-Online", "S-100", }, { "Tyan", "iS5375-1U", }, { "Tyan", "S1846", }, + { "Tyan", "S2466", }, { "Tyan", "S2881", }, { "Tyan", "S2882", }, { "Tyan", "S2882-D", }, @@ -1054,6 +1055,9 @@ const struct board_info boards_bad[] = { /* Verified non-working boards (for now). */ { "Abit", "IS-10", }, + { "ASRock", "K7VT4A+", }, + { "ASUS", "A7V600-X", }, + { "ASUS", "M2N68", }, { "ASUS", "M3N78 Pro", }, { "ASUS", "MEW-AM", }, { "ASUS", "MEW-VM", }, Modified: trunk/print.c =================================================================== --- trunk/print.c 2009-08-19 15:19:18 UTC (rev 694) +++ trunk/print.c 2009-08-20 18:45:18 UTC (rev 695) @@ -351,6 +351,7 @@ { "T-Online", "S-100", "http://wiki.freifunk-hannover.de/T-Online_S_100" }, { "Tyan", "iS5375-1U", "http://www.tyan.com/product_board_detail.aspx?pid=610" }, { "Tyan", "S1846", "http://www.tyan.com/archive/products/html/tsunamiatx.html" }, + { "Tyan", "S2466", "http://www.tyan.com/product_board_detail.aspx?pid=461" }, { "Tyan", "S2881", "http://www.tyan.com/product_board_detail.aspx?pid=115" }, { "Tyan", "S2882", "http://www.tyan.com/product_board_detail.aspx?pid=121" }, { "Tyan", "S2882-D", "http://www.tyan.com/product_board_detail.aspx?pid=127" }, @@ -380,10 +381,12 @@ { "Acorp", "6A815EPD", "http://web.archive.org/web/20021206163652/www.acorp.com.tw/English/default.…" }, { "agami", "Aruma", "http://web.archive.org/web/20080212111524/http://www.agami.com/site/ais-600…" }, { "Albatron", "PM266A Pro", "http://www.albatron.com.tw/English/Product/MB/pro_detail.asp?rlink=Overview…" }, /* FIXME */ + { "AOpen", "vKM400Am-S", "http://usa.aopen.com/products_detail.aspx?Auno=824" }, { "Artec Group", "DBE61", "http://wiki.thincan.org/DBE61" }, { "Artec Group", "DBE62", "http://wiki.thincan.org/DBE62" }, { "ASUS", "A7V8X-MX SE", "http://www.asus.com/product.aspx?P_ID=1guVBT1qV5oqhHyZ" }, { "ASUS", "P4B266", "http://www.ciao.co.uk/ASUS_Intel_845D_Chipset_P4B266__5409807#productdetail" }, + { "ASUS", "P4P800-E Deluxe", "http://www.asus.com/product.aspx?P_ID=INIJUvLlif7LHp3g" }, { "ASUS", "P5A", "ftp://ftp.asus.com.tw/pub/ASUS/mb/sock7/ali/p5a/" }, { "Biostar", "P4M80-M4", "http://www.biostar-usa.com/mbdetails.asp?model=p4m80-m4" }, { "Elitegroup", "K7VTA3", "http://www.ecs.com.tw/ECSWebSite/Products/ProductsDetail.aspx?detailid=264&…" }, @@ -420,6 +423,9 @@ /* Verified non-working boards (for now). */ { "Abit", "IS-10", "http://www.abit.com.tw/page/en/motherboard/motherboard_detail.php?pMODEL_NA…" }, + { "ASRock", "K7VT4A+", "http://www.asrock.com/mb/overview.asp?Model=K7VT4A%%2b&s=" }, + { "ASUS", "A7V600-X", "http://www.asus.com/product.aspx?P_ID=L2XYS0rmtCjeOr4k" }, + { "ASUS", "M2N68", "http://www.asus.com/product.aspx?P_ID=iDZQ9yNK2CbKW6Zv"}, { "ASUS", "M3N78 Pro", "http://www.asus.com/product.aspx?P_ID=DVvm9CU0G1bCC4gp" }, { "ASUS", "MEW-AM", "ftp://ftp.asus.com.tw/pub/ASUS/mb/sock370/810/mew-am/" }, { "ASUS", "MEW-VM", "http://www.elhvb.com/mboards/OEM/HP/manual/ASUS%20MEW-VM.htm" },

1 0

[PATCH] Documentation update
by Stefan Reinauer 20 Aug '09

20 Aug '09

See patch -- coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br. Tel.: +49 761 7668825 • Fax: +49 761 7664613 Email: info(a)coresystems.de • http://www.coresystems.de/ Registergericht: Amtsgericht Freiburg • HRB 7656 Geschäftsführer: Stefan Reinauer • Ust-IdNr.: DE245674866

3 2

comprehensive dumps for the Asus A7v600-x
by Putlinuxonit 20 Aug '09

20 Aug '09

Hi Luc, Sorry i didn't include the #superiotool -dV output last time. here is everything in one file. Udu E. Ogah .~~~~~~~~~~.

1 0

[Patch] Board enable for Asus P4P800-E Deluxe.
by Luc Verhaegen 20 Aug '09

20 Aug '09

First time i successfully dug one out of an AMI Bios. int16h ax=0xE0 is indeed the ticket. This one has its int16h vector at the standard location it seems: 0xF000:0xE82E. Not sure how general this is for AMI. It does seem that i will require dumps of the F segment for this to work though. Luc Verhaegen.

4 3

"lspci -vvnnxx" and "superiotool -d" dumps from an Asus m2n68 motherboard needing a board enable
by Putlinuxonit 20 Aug '09

20 Aug '09

Hi All, This board has it's chipset detected but the eeprom flash chip isn't even though it's an MXIC25L8005 chip which is listed in "flashrom -L" Just thought i'll put up the dumps. Do let me know if you need further testing. Udu E. Ogah

1 0

Not sure where to put this?
by Marko Kraljevic 20 Aug '09

20 Aug '09

Hi, I'm new to the list. I've been playing with flashrom some, and it's great. Thanks for the work guys. I've put a ZIF socket on a 3com NIC, for external programming. It seems to be working great. I've taken a picture, maybe it would be useful for the wiki or something. I'm not a terribly good programmer, but I'm pretty good with hardware generally... I'm going to be doing some more hardware work in the future. I think I'll make an ISA card with 32 and 28pin ZIF, and PLCC socket, on the 440BX board I have, addr is off the ISA bus, so I'll just buffer that. Data seems to go to the superIO chip, so I'll have to have a cheater socket under the stock BIOS ROM to steal /CS D0:7, etc. I think I'll buffer all the lines on the card, so that the bus doesn't get fried in case of a fried chip or whatnot. It will be a sort of general purpose flashing board. I think I'll try and implement support for the older 27xxx EPROMs at some point, which shouldn't be too difficult I don't think? anyways, here's the picture if anyone wants it: http://electrontube.org/img/3com_prog.jpg Mark

2 3

Asus A7v600-X works with stable v0.9.0 but not with bleeding edge
by Putlinuxonit 20 Aug '09

20 Aug '09

Hi All, I'd like to report than an Asus A7V600-X with bios 1009 works with flashrom 0.9.0 stable. The stock version found on the latest stable realease of systemrescuecd 1.2.3. There are some caveats however... find below a few dumps for your review. root@sysresccd% ./flashrom *flashrom v0.9.0* No coreboot table found. *Found chipset "VIA VT8237"*, enabling flash write... OK. This chipset supports the following protocols: Non-SPI. Calibrating delay loop... OK. *Found chip "PMC Pm49FL002" (256 KB, LPC,FWH)* at physical address 0xfffc0000. No operations were specified. The strange thing is that when i tried using the bleeding edge r694 i get the following root@sysresccd /root % ./flashrom -w fimrwarea7v600-x.old *flashrom v0.9.0-r694* No coreboot table found. Found chipset "VIA VT8237", enabling flash write... OK. This chipset supports the following protocols: Non-SPI. Calibrating delay loop... OK. Found chip "PMC Pm49FL002" (256 KB, LPC,FWH) at physical address 0xfffc0000. Flash image seems to be a legacy BIOS. Disabling checks. Writing flash chip... Programming page: ERASE FAILED at 0x00000000! Expected=0xff, Read=0x03, failed byte count from 0x00000000-0x00003fff: 0x33a6 ERASE FAILED! ERASE FAILED! FAILED! Your flash chip is in an unknown state. Get help on IRC at irc.freenode.net channel #flashrom or mail flashrom(a)flashrom.org ------------------------------------------------------------ DO NOT REBOOT OR POWEROFF! i then use the stock 0.9.0 version to reprogramme and i get this root@sysresccd /root % flashrom -w fimrwarea7v600-x.old Calibrating delay loop... OK. No coreboot table found. Found chipset "VIA VT8237", enabling flash write... OK. Found chip "PMC Pm49FL002" (256 KB) at physical address 0xfffc0000. Flash image seems to be a legacy BIOS. Disabling checks. Programming page: 0015 at address: 0x0003c000 i* verify if it's written ok* root@sysresccd /root % flashrom -v fimrwarea7v600-x.old Calibrating delay loop... OK. No coreboot table found. Found chipset "VIA VT8237", enabling flash write... OK. Found chip "PMC Pm49FL002" (256 KB) at physical address 0xfffc0000. Flash image seems to be a legacy BIOS. Disabling checks. Verifying flash... VERIFIED. root@sysresccd /root % flashrom -R *flashrom v0.9.0* so basically, When i use the stock v0.9.0 to dump and write back the firmware on my A7v600-x, everything is fine. when i try to use the current svn. r694, it fails. i had to reflash with stable 0.9.0 after the r694 failed. I've successfully rebooted and verified no damage done to motherboard. interestingly, I downloaded the latest version of the bios (1009) off asus website, same version as i'm running and when i unzip it yeilds an *.awd ( i guess award) file. This file is supposed to be the same version as the one i'm running but when i try both stock v0.9.0 and r694 on it. they both fail. Beats me. maybe the awardflasher file format is different from what I get when i do* "flashrom -r firmware-old.bin"* * * I've also compared md5 checksums on both the firmware-old.bin and the one downloaded off the asus website but they both give different results even though they are meant to be the same version (1009). Anyway, hats-off to the devs for all the good work. idlogin -- Udu E. Ogah .~~~~~~~~~~. attachments I've attached flashrom -V dumps for both 0.9.0 and r694 latest Asus bios for A7v600-X

2 4

[RFC] flashrom 0.9.1
by Carl-Daniel Hailfinger 19 Aug '09

19 Aug '09

Hi, there are no more pending flashrom patches for 0.9.1 and I would like to release it today or tomorrow. Draft 0.9.1 announcement is at http://www.coreboot.org/Flashrom/0.9.1 . Please test! Regards, Carl-Daniel -- http://www.hailfinger.org/

1 0

[PATCH] Fix romentry layout for programmers
by Carl-Daniel Hailfinger 19 Aug '09

19 Aug '09

Flashrom has the ability to use layout files with romentries, but this feature was not adapted to the programmer infrastructure and had undefined behaviour for flasher!=internal. The romentry handling had an off-by-one error which caused all copies to end up one byte short. Fix these issues. Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006(a)gmx.net> Index: flashrom-romentries_programmer/flash.h =================================================================== --- flashrom-romentries_programmer/flash.h (Revision 692) +++ flashrom-romentries_programmer/flash.h (Arbeitskopie) @@ -422,7 +422,7 @@ int show_id(uint8_t *bios, int size, int force); int read_romlayout(char *name); int find_romentry(char *name); -int handle_romentries(uint8_t *buffer, uint8_t *content); +int handle_romentries(uint8_t *buffer, struct flashchip *flash); /* cbtable.c */ int coreboot_init(void); Index: flashrom-romentries_programmer/flashrom.c =================================================================== --- flashrom-romentries_programmer/flashrom.c (Revision 692) +++ flashrom-romentries_programmer/flashrom.c (Arbeitskopie) @@ -930,8 +930,7 @@ // This should be moved into each flash part's code to do it // cleanly. This does the job. - /* FIXME: Adapt to the external flasher infrastructure. */ - handle_romentries(buf, (uint8_t *) flash->virtual_memory); + handle_romentries(buf, flash); // //////////////////////////////////////////////////////////// Index: flashrom-romentries_programmer/layout.c =================================================================== --- flashrom-romentries_programmer/layout.c (Revision 692) +++ flashrom-romentries_programmer/layout.c (Arbeitskopie) @@ -196,11 +196,11 @@ return -1; } -int handle_romentries(uint8_t *buffer, uint8_t *content) +int handle_romentries(uint8_t *buffer, struct flashchip *flash) { int i; - // This function does not safe flash write cycles. + // This function does not save flash write cycles. // // Also it does not cope with overlapping rom layout // sections. @@ -220,10 +220,9 @@ if (rom_entries[i].included) continue; - /* FIXME: Adapt to the external flasher infrastructure. */ - memcpy(buffer + rom_entries[i].start, - content + rom_entries[i].start, - rom_entries[i].end - rom_entries[i].start); + flash->read(flash, buffer + rom_entries[i].start, + rom_entries[i].start, + rom_entries[i].end - rom_entries[i].start + 1); } return 0; -- http://www.hailfinger.org/

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom