flashrom

flashrom@flashrom.org

7 participants
9163 discussions

Re: [flashrom] Unsupported 3com device (3c905 100BaseTX [Boomerang])
by Idwer Vollering 22 Oct '13

22 Oct '13

2013/10/22 san <san(a)plusnet.pl>: > Hi! > > I own: > 02:00.0 Ethernet controller [0200]: 3Com Corporation 3c905 100BaseTX > [Boomerang] [10b7:9050] > > It's unsupported: > ---[code]--- > Error: No supported PCI device found. > Error: Programmer initialization failed. > ---[/code]--- > > I would love to help You to get it to work with flashrom. > Do You need it? > > Regards! Yes, we would appreciate some testing. Do you have a parallel DIP32 chip that you can insert into its socket? Either SST39SF512, CAT28F125 or AT29C512 should work: http://www.ebay.com/sch/i.html?_nkw=SST39SF512 http://www.ebay.com/sch/i.html?_nkw=CAT28F512 http://www.ebay.com/sch/i.html?_nkw=AT29C512 When you have that set up, apply this patch: Index: nic3com.c =================================================================== --- nic3com.c (revision 1760) +++ nic3com.c (working copy) @@ -37,6 +37,9 @@ static uint16_t id; const struct dev_entry nics_3com[] = { + /* 3C905 */ + {0x10b7, 0x9050, NT, "3COM", "3c905: Fast EtherLink XL PCI (3c905-TX)"}, + /* 3C90xB */ {0x10b7, 0x9055, OK, "3COM", "3C90xB: PCI 10/100 Mbps; shared 10BASE-T/100BASE-TX"}, {0x10b7, 0x9001, NT, "3COM", "3C90xB: PCI 10/100 Mbps; shared 10BASE-T/100BASE-T4" },

1 0

Re: [flashrom] Riva TNT 2, What is max chip size
by san 22 Oct '13

22 Oct '13

Both are OTP, but why they are not supported (for read)? 2013/10/22 Donovan Lavinder <drmario2007(a)gmail.com> > I think some are OTP, others are flashable. You can check the datasheet to > be sure. > On Oct 22, 2013 1:08 PM, "san" <san(a)plusnet.pl> wrote: > >> Same here for Vanta (Atmel AT27LV512A). >> Or it is intentionally to not support those 27's chips which are >> One-Time-Programmable? >> >> Regards! >> >> >> 2013/10/22 san <san(a)plusnet.pl> >> >>> Thanks for the info. >>> I've found that it MIGHT be supported by flashrom. It does look for >>> memory (see log). >>> >>> I checked the chip and it's Holtek ht27c512 (it's 64k - good sign?) >>> which seems to be, simply, unsupported by flashrom. >>> Can You add its support? >>> >>> Best regards! >>> >>> >>> 2013/10/22 Donovan Lavinder <drmario2007(a)gmail.com> >>> >>>> 32KB, I think. I do remember owning that card a long time ago. The BIOS >>>> image may be 16KB, however, due to very simple pipeline architecture. The >>>> only way to find out is to pull the BIOS copy and verify its size. >>>> On Oct 22, 2013 12:44 AM, "san" <san(a)plusnet.pl> wrote: >>>> >>>>> I ani going to buy riva to program some bioses with it. But first i >>>>> would like to know what chip sizes i can use. Parallel ofcourse. >>>>> >>>>> Regards! >>>>> >>>>> _______________________________________________ >>>>> flashrom mailing list >>>>> flashrom(a)flashrom.org >>>>> http://www.flashrom.org/mailman/listinfo/flashrom >>>>> >>>> >>> >>> >>> -- >>> [ e-San.info | San(a)plusnet.pl ] >>> >> >> >> >> -- >> [ e-San.info | San(a)plusnet.pl ] >> > -- [ e-San.info | San(a)plusnet.pl ]

1 0

Re: [flashrom] Riva TNT 2, What is max chip size
by san 22 Oct '13

22 Oct '13

Same here for Vanta (Atmel AT27LV512A). Or it is intentionally to not support those 27's chips which are One-Time-Programmable? Regards! 2013/10/22 san <san(a)plusnet.pl> > Thanks for the info. > I've found that it MIGHT be supported by flashrom. It does look for memory > (see log). > > I checked the chip and it's Holtek ht27c512 (it's 64k - good sign?) which > seems to be, simply, unsupported by flashrom. > Can You add its support? > > Best regards! > > > 2013/10/22 Donovan Lavinder <drmario2007(a)gmail.com> > >> 32KB, I think. I do remember owning that card a long time ago. The BIOS >> image may be 16KB, however, due to very simple pipeline architecture. The >> only way to find out is to pull the BIOS copy and verify its size. >> On Oct 22, 2013 12:44 AM, "san" <san(a)plusnet.pl> wrote: >> >>> I ani going to buy riva to program some bioses with it. But first i >>> would like to know what chip sizes i can use. Parallel ofcourse. >>> >>> Regards! >>> >>> _______________________________________________ >>> flashrom mailing list >>> flashrom(a)flashrom.org >>> http://www.flashrom.org/mailman/listinfo/flashrom >>> >> > > > -- > [ e-San.info | San(a)plusnet.pl ] > -- [ e-San.info | San(a)plusnet.pl ]

1 0

Re: [flashrom] Riva TNT 2, What is max chip size
by san 22 Oct '13

22 Oct '13

Thanks for the info. I've found that it MIGHT be supported by flashrom. It does look for memory (see log). I checked the chip and it's Holtek ht27c512 (it's 64k - good sign?) which seems to be, simply, unsupported by flashrom. Can You add its support? Best regards! 2013/10/22 Donovan Lavinder <drmario2007(a)gmail.com> > 32KB, I think. I do remember owning that card a long time ago. The BIOS > image may be 16KB, however, due to very simple pipeline architecture. The > only way to find out is to pull the BIOS copy and verify its size. > On Oct 22, 2013 12:44 AM, "san" <san(a)plusnet.pl> wrote: > >> I ani going to buy riva to program some bioses with it. But first i would >> like to know what chip sizes i can use. Parallel ofcourse. >> >> Regards! >> >> _______________________________________________ >> flashrom mailing list >> flashrom(a)flashrom.org >> http://www.flashrom.org/mailman/listinfo/flashrom >> > -- [ e-San.info | San(a)plusnet.pl ]

1 0

Unsupported 3com device (3c905 100BaseTX [Boomerang])
by san 22 Oct '13

22 Oct '13

Hi! I own: 02:00.0 Ethernet controller [0200]: 3Com Corporation 3c905 100BaseTX [Boomerang] [10b7:9050] It's unsupported: ---[code]--- Error: No supported PCI device found. Error: Programmer initialization failed. ---[/code]--- I would love to help You to get it to work with flashrom. Do You need it? Regards! -- [ e-San.info | San(a)plusnet.pl ]

1 0

Re: [flashrom] Riva TNT 2, What is max chip size
by Stefan Tauner 22 Oct '13

22 Oct '13

On Tue, 22 Oct 2013 11:12:42 +0200 san <san(a)plusnet.pl> wrote: > On page http://flashrom.org/Supported_hardware we can find information that > it is OK. > So it is not correct? Let's say it is very misleading: it means that everything the driver is able to do works with the PCI card in question. Normally we do not commit such incomplete drivers, but I guess Uwe has slipped it in (NB: way before I was around :) and there is no way to express "read-only" in the hardware tables (yet). -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Re: [flashrom] Riva TNT 2, What is max chip size
by san 22 Oct '13

22 Oct '13

On page http://flashrom.org/Supported_hardware we can find information that it is OK. So it is not correct? 2013/10/22 san <san(a)plusnet.pl> > I ani going to buy riva to program some bioses with it. But first i would > like to know what chip sizes i can use. Parallel ofcourse. > > Regards! > -- [ e-San.info | San(a)plusnet.pl ]

1 0

Re: [flashrom] Riva TNT 2, What is max chip size
by Stefan Tauner 22 Oct '13

22 Oct '13

On Tue, 22 Oct 2013 08:39:08 +0200 san <san(a)plusnet.pl> wrote: > I ani going to buy riva to program some bioses with it. But first i would > like to know what chip sizes i can use. Parallel ofcourse. I could be wrong, but I think the gfxnvidia driver is not able to write/erase at all. -- Kind regards/Mit freundlichen Grüßen, Stefan Tauner

1 0

Riva TNT 2, What is max chip size
by san 22 Oct '13

22 Oct '13

I ani going to buy riva to program some bioses with it. But first i would like to know what chip sizes i can use. Parallel ofcourse. Regards!

1 0

[PATCH] Make delay values unsigned.
by Stefan Tauner 21 Oct '13

21 Oct '13

There is no reason for negative delays in our use cases: - We don't need it (to work around any quirks). - sleep() (POSIX) uses an unsigned argument. - usleep() (POSIX) uses an unsigned argument. - Sleep() (Windows) uses an unsigned argument. Signed-off-by: Stefan Tauner <stefan.tauner(a)student.tuwien.ac.at> --- flash.h | 2 +- flashrom.c | 2 +- programmer.h | 10 +++++----- serprog.c | 2 +- udelay.c | 10 +++++----- 5 files changed, 13 insertions(+), 13 deletions(-) diff --git a/flash.h b/flash.h index e320ced..bfb0a49 100644 --- a/flash.h +++ b/flash.h @@ -56,7 +56,7 @@ typedef uint32_t chipsize_t; /* Able to store the number of bytes of any support int register_shutdown(int (*function) (void *data), void *data); void *programmer_map_flash_region(const char *descr, uintptr_t phys_addr, size_t len); void programmer_unmap_flash_region(void *virt_addr, size_t len); -void programmer_delay(int usecs); +void programmer_delay(unsigned int usecs); #define ARRAY_SIZE(a) (sizeof(a) / sizeof((a)[0])) diff --git a/flashrom.c b/flashrom.c index 092572e..23728f6 100644 --- a/flashrom.c +++ b/flashrom.c @@ -485,7 +485,7 @@ void chip_readn(const struct flashctx *flash, uint8_t *buf, chipaddr addr, flash->pgm->par.chip_readn(flash, buf, addr, len); } -void programmer_delay(int usecs) +void programmer_delay(unsigned int usecs) { if (usecs > 0) programmer_table[programmer].delay(usecs); diff --git a/programmer.h b/programmer.h index ef96c9e..b3df981 100644 --- a/programmer.h +++ b/programmer.h @@ -120,7 +120,7 @@ struct programmer_entry { void *(*map_flash_region) (const char *descr, uintptr_t phys_addr, size_t len); void (*unmap_flash_region) (void *virt_addr, size_t len); - void (*delay) (int usecs); + void (*delay) (unsigned int usecs); }; extern const struct programmer_entry programmer_table[]; @@ -248,10 +248,10 @@ extern const struct board_info laptops_known[]; #endif /* udelay.c */ -void myusec_delay(int usecs); +void myusec_delay(unsigned int usecs); void myusec_calibrate_delay(void); -void internal_sleep(int usecs); -void internal_delay(int usecs); +void internal_sleep(unsigned int usecs); +void internal_delay(unsigned int usecs); #if CONFIG_INTERNAL == 1 /* board_enable.c */ @@ -654,7 +654,7 @@ int register_programmer(struct registered_programmer *pgm); /* serprog.c */ #if CONFIG_SERPROG == 1 int serprog_init(void); -void serprog_delay(int usecs); +void serprog_delay(unsigned int usecs); #endif /* serial.c */ diff --git a/serprog.c b/serprog.c index 237db7d..8a952d4 100644 --- a/serprog.c +++ b/serprog.c @@ -865,7 +865,7 @@ static void serprog_chip_readn(const struct flashctx *flash, uint8_t * buf, sp_do_read_n(&(buf[addrm-addr]), addrm, lenm); // FIXME: return error } -void serprog_delay(int usecs) +void serprog_delay(unsigned int usecs) { unsigned char buf[4]; msg_pspew("%s usecs=%d\n", __func__, usecs); diff --git a/udelay.c b/udelay.c index e3cf3e3..ee858b8 100644 --- a/udelay.c +++ b/udelay.c @@ -30,7 +30,7 @@ /* loops per microsecond */ static unsigned long micro = 1; -__attribute__ ((noinline)) void myusec_delay(int usecs) +__attribute__ ((noinline)) void myusec_delay(unsigned int usecs) { unsigned long i; for (i = 0; i < usecs * micro; i++) { @@ -63,7 +63,7 @@ static unsigned long measure_os_delay_resolution(void) return timeusec; } -static unsigned long measure_delay(int usecs) +static unsigned long measure_delay(unsigned int usecs) { unsigned long timeusec; struct timeval start, end; @@ -170,7 +170,7 @@ recalibrate: } /* Not very precise sleep. */ -void internal_sleep(int usecs) +void internal_sleep(unsigned int usecs) { #ifdef _WIN32 Sleep((usecs + 999) / 1000); @@ -181,7 +181,7 @@ void internal_sleep(int usecs) } /* Precise delay. */ -void internal_delay(int usecs) +void internal_delay(unsigned int usecs) { /* If the delay is >1 s, use internal_sleep because timing does not need to be so precise. */ if (usecs > 1000000) { @@ -199,7 +199,7 @@ void myusec_calibrate_delay(void) get_cpu_speed(); } -void internal_delay(int usecs) +void internal_delay(unsigned int usecs) { udelay(usecs); } -- Kind regards, Stefan Tauner

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

flashrom