[flashrom] Green CH341A didn't work, turned out it's a badly soldered CS leg. Fixed now ;-)

2019-05-03 Thread Mike Banon 
My spare green CH341A almost always was unable to find a chip. Luckily
I have another working CH341A, so started comparing them with a
multimeter :

When a "healthy" CH341A is simply plugged into a USB port, without any
chips connected, there is a 3.15V - 3.3V voltage between GND hole and
other 7 holes at 25xx socket. But a "glitchy" CH341A, when put to the
same situation, did not have a ~3V voltage difference between GND and
CS pin.

Then I checked a resistance between CS leg of CH341A chip ( found it
using this document -
https://www.onetransistor.eu/2017/08/ch341a-mini-programmer-schematic.html
) and CS pin at the bottom of programmer (instead of CS hole for
convenience) - it was almost always "infinite", but sometimes - when I
pushed CS leg with a multimeter pin - there was a close to 0 Ohm
resistance, almost zero.

So I did a small soldering of CH341A CS leg, see a picture
https://i.redd.it/mfrgs45beuv21.jpg - luckily this CS leg is at the
corner of chip so was quite convenient to solder - and now this CH341A
is happy and working perfectly! ;-) Will flash many BIOSes :3
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Success in writing to AT29C010A via 3Com 905B

2019-05-03 Thread Quinn Plattel 
Hi,

You probably want a screenshot so here it is.

Quinn


On Fri, May 3, 2019 at 5:21 PM Quinn Plattel  wrote:

> Hi,
>
> Just want to report that I have now had many successes in reading and
> writing to the following roms via the 3Com 905B network card:
>
> ATMEL AT29C010A 120ns
> ATMEL AT29C512 120ns
>
> The ATMEL AT29C010A 70ns do fail probably because of the speed.
>
> I have tested with both the iPXE and XTIDE open source projects.
>
> --
> Best regards/Ystävällisin terveisin/Med venlig hilsen,
> Quinn Plattel
>
>

-- 
Best regards/Ystävällisin terveisin/Med venlig hilsen,
Quinn Plattel
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Re: Success in writing to AT29C010A via 3Com 905B

2019-05-03 Thread Quinn Plattel 
Hi again,

Forgot to add the debug log, so here it is.

Quinn

On Fri, May 3, 2019 at 5:25 PM Quinn Plattel  wrote:

> Hi,
>
> You probably want a screenshot so here it is.
>
> Quinn
>
>
> On Fri, May 3, 2019 at 5:21 PM Quinn Plattel  wrote:
>
>> Hi,
>>
>> Just want to report that I have now had many successes in reading and
>> writing to the following roms via the 3Com 905B network card:
>>
>> ATMEL AT29C010A 120ns
>> ATMEL AT29C512 120ns
>>
>> The ATMEL AT29C010A 70ns do fail probably because of the speed.
>>
>> I have tested with both the iPXE and XTIDE open source projects.
>>
>> --
>> Best regards/Ystävällisin terveisin/Med venlig hilsen,
>> Quinn Plattel
>>
>>
>
> --
> Best regards/Ystävällisin terveisin/Med venlig hilsen,
> Quinn Plattel
>
>

-- 
Best regards/Ystävällisin terveisin/Med venlig hilsen,
Quinn Plattel
flashrom v0.9.9-r1954 on Linux 4.15.0-39-generic (x86_64)
flashrom was built with libpci 3.3.1, GCC 5.3.1 20160424, little endian
Command line (6 args): flashrom -p nic3com -w /home/user/plattel.128 -o /tmp/at29c0101a.log
Calibrating delay loop... OS timer resolution is 1 usecs, 3004M loops per second, 10 myus = 10 us, 100 myus = 100 us, 1000 myus = 999 us, 1 myus = 1 us, 4 myus = 4 us, OK.
Initializing nic3com programmer
Found "3COM 3C90xB: PCI 10/100 Mbps; shared 10BASE-T/100BASE-TX" (10b7:9055, BDF 04:04.0).
Requested BAR is of type I/O
Requested BAR is of type I/O
The following protocols are supported: Parallel.
Probing for AMD Am29F010, 128 kB: probe_jedec_common: id1 0x5f, id2 0x1f, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29F010A/B, 128 kB: probe_jedec_common: id1 0x5f, id2 0x1f, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29F002(N)BB, 256 kB: probe_jedec_common: id1 0x5f, id2 0x1f, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29F002(N)BT, 256 kB: probe_jedec_common: id1 0x5f, id2 0x1f, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29F016D, 2048 kB: probe_jedec_common: id1 0x5f, id2 0x1f, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29F040, 512 kB: probe_jedec_common: id1 0x5f, id2 0x1f, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29F040B, 512 kB: probe_jedec_common: id1 0x5f, id2 0x1f, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29F080, 1024 kB: probe_jedec_common: id1 0x5f, id2 0x1f, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29F080B, 1024 kB: probe_jedec_common: id1 0x5f, id2 0x1f, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV001BB, 128 kB: probe_jedec_common: id1 0x5f, id2 0x1f, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV001BT, 128 kB: probe_jedec_common: id1 0x5f, id2 0x1f, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV002BB, 256 kB: probe_jedec_common: id1 0x5f, id2 0x1f, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV002BT, 256 kB: probe_jedec_common: id1 0x5f, id2 0x1f, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV004BB, 512 kB: probe_jedec_common: id1 0x5f, id2 0x1f, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV004BT, 512 kB: probe_jedec_common: id1 0x5f, id2 0x1f, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV008BB, 1024 kB: probe_jedec_common: id1 0x5f, id2 0x1f, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV008BT, 1024 kB: probe_jedec_common: id1 0x5f, id2 0x1f, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV040B, 512 kB: probe_jedec_common: id1 0x5f, id2 0x1f, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMD Am29LV081B, 1024 kB: probe_jedec_common: id1 0x5f, id2 0x1f, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMIC A29002B, 256 kB: probe_jedec_common: id1 0x5f, id2 0x1f, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMIC A29002T, 256 kB: probe_jedec_common: id1 0x5f, id2 0x1f, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for AMIC A29040B, 512 kB: probe_jedec_common: id1 0x5f, id2 0x1f, id1 parity violation, id1 is normal flash content, id2 is normal flash content
Probing for Atmel AT29C512, 64 kB: probe_jedec_common: id1 0x1f, id2 0xd5
Probing for Atmel AT29C010A, 128 kB:

[flashrom] Success in writing to AT29C010A via 3Com 905B

2019-05-03 Thread Quinn Plattel 
Hi,

Just want to report that I have now had many successes in reading and
writing to the following roms via the 3Com 905B network card:

ATMEL AT29C010A 120ns
ATMEL AT29C512 120ns

The ATMEL AT29C010A 70ns do fail probably because of the speed.

I have tested with both the iPXE and XTIDE open source projects.

-- 
Best regards/Ystävällisin terveisin/Med venlig hilsen,
Quinn Plattel
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org

[flashrom] Outdated command-line stability warning

2019-05-03 Thread Charles Daffern 

Hello flashrom people,

I just wanted to bring a small triviality to your attention: currently, 
`flashrom --help' warns the user that the command line interface is due 
to change before v1.0, but we have already passed that version.


It is a very trivial change, but for convenience's sake I will attach a 
patch for `git apply'.
diff --git a/cli_classic.c b/cli_classic.c
index ced08c6..4f6719f 100644
--- a/cli_classic.c
+++ b/cli_classic.c
@@ -31,9 +31,6 @@
 
 static void cli_classic_usage(const char *name)
 {
-	printf("Please note that the command line interface for flashrom has changed between\n"
-	   "0.9.5 and 0.9.6 and will change again before flashrom 1.0.\n\n");
-
 	printf("Usage: %s [-h|-R|-L|"
 #if CONFIG_PRINT_WIKI == 1
 	   "-z|"
___
flashrom mailing list -- flashrom@flashrom.org
To unsubscribe send an email to flashrom-le...@flashrom.org