search

DavidGriffith / minipro-import-test

An open source program for controlling the MiniPRO TL866xx series of chip programmers
GNU General Public License v3.0
3 stars 0 forks source link

MX25L with TL866II plus #260

Open DavidGriffith opened 2 years ago

DavidGriffith commented 2 years ago

In GitLab by @kensenjiha on Apr 4, 2022, 21:13

1. Unable to erase MX25L25635E@SOIC16

 % minipro -p MX25L25635E@SOIC16 -E -vvvv  
Found TL866II+ 04.2.128 (0x280)
Invalid Chip ID: expected 0xC22019, got 0xC00008 (unknown)
(use '-y' to continue anyway at your own risk)

but use MX25L25635F@SOIC16 (E -> F)

 % minipro -p MX25L25635F@SOIC16 -w 2b2s3451.bin -E -vvvv
Found TL866II+ 04.2.128 (0x280)
Chip ID OK: 0xC22019
Erasing... 63.76Sec OK

The Flash IC marking is MX25L25635EMi

2. Unable to program MX25L25635E@SOIC16

The "RUN" LED lights for seconds then dies,

 % minipro -p MX25L25635F@SOIC16 -E -vvvv
Found TL866II+ 04.2.128 (0x280)
Chip ID OK: 0xC22019
Erasing... 63.85Sec OK

% minipro -p MX25L25635F@SOIC16 -w 2b2s3451.bin -e -vvvv
Found TL866II+ 04.2.128 (0x280)
Chip ID OK: 0xC22019
Protect off...OK
Writing  Code...   0%
IO Error: Async transfer failed: LIBUSB_TRANSFER_TIMED_OUT

Writing progress can be 0% to 2%

use -p MX25L25635E@SOIC16 by foce

 % minipro -p MX25L25635E@SOIC16 -E -vvvv -y
Found TL866II+ 04.2.128 (0x280)
WARNING: Chip ID mismatch: expected 0xC22019, got 0xC00008 (unknown)
Erasing... 64.06Sec OK

 % minipro -p MX25L25635E@SOIC16 -w 2b2s3451.bin -e -vvvv -y
Found TL866II+ 04.2.128 (0x280)
WARNING: Chip ID mismatch: expected 0xC22019, got 0xC00008 (unknown)
Protect off...OK
Writing  Code...   1%
IO Error: Async transfer failed: LIBUSB_TRANSFER_TIMED_OUT
DavidGriffith commented 2 years ago

In GitLab by @kensenjiha on Apr 4, 2022, 23:17

Update:

TL866A works (with infoic.xml hack, copy ID:0xC22019 devices from TL866II section to TL866A)

 % minipro -p MX25L25633F@SOIC16 -w 2b2s3451.bin -e -vvvv -y
Found TL866A 03.2.86 (0x256)
WARNING: Chip ID mismatch: expected 0xC22019, got 0x0000 (unknown)
Protect off...OK
Writing Code...  1213.73Sec  OK
Protect on...OK

but read test fails.

TL866II+ failes but written first few kBs verified correct.

DavidGriffith commented 2 years ago

In GitLab by @radiomanV on Apr 5, 2022, 01:04

If the chip id mismatch then all operations are wrong after. The -y switch can help in some circumstances (like parallel eproms) but not here. The first sign that something is not right is the chip id mismatch. Don't modify the xml file thinking that if you do so then everything will be ok. That 0xC00008 id is something random/gibberish value read by the firmware.

Are you sure that the chip is properly inserted? (use the -z) switch (for TL866II only) to check for a bad pin contact (minipro -p MX25L25633F@SOIC16 -z. Also, is the chip package specified correctly (soic8/soic16)?
The -vvvv has no meaning here (is not used as verbosity) use only a -v when you want to skip the verify step after the writing.

Prior to any read/write/erase op you can play with that chip to see if can be auto-detected like this: minipro -a 8 for 8 pin devices or minipro -a 16 for 16 pin devices.
Also you can try to clean the chip and/or the soic socket with some alcohol or good contact cleaner/spray. Believe me, this bad contact thing due to oxidation or flux residues can drive you crazy. Also some soic/plcc adapters are just junk.
So you must identify the root cause of why the chip is not detected, and not to try to treat the effect.

DavidGriffith commented 2 years ago

In GitLab by @kensenjiha on Apr 5, 2022, 01:39

strange, on another computer, TL866UU+ works the first time... same version OS. older minipro

DavidGriffith commented 2 years ago

In GitLab by @radiomanV on Apr 5, 2022, 07:12

There's no major differences between minipro 0.4 and 0.5 for the programming logic code. The big change was the xml database addition and the logic chips test feature but i repeat, there's nothing changed inside the read/write/erase protocol.
Maybe a database bug or something else. Can you test the current master branch on that "working" computer? Maybe i can catch what's wrong.
Thanks.