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

Reading and writing randomly stops #200

Open DavidGriffith opened 3 years ago

DavidGriffith commented 3 years ago

In GitLab by @AlaskanEmily on Jan 1, 2021, 19:15

When trying to read or write a ROM, I keep having the program just get stuck at a certain percentage.

For instance:

clunky# minipro -p AT2864B@SOIC28 -m test.bin
Found TL866II+ 04.2.86 (0x256)
Warning: Firmware is out of date.
  Expected  04.2.123 (0x27b)
  Found     04.2.86 (0x256)
Reading Code...  56%^C
clunky#

I had to control+C because it would just sit that. It happens at different percentages, and happens with reading, writing, and with -b too.

I would update the firmware, but it seems like the manufacturer website changed location recently and I can't find where to get newer firmware.

DavidGriffith commented 3 years ago

In GitLab by @radiomanV on Jan 2, 2021, 03:30

This kind of error is always produced by some usb communication issue or a firmware problem.
Please first upgrade your firmware as described here: issue #185
The latest xgpro version is 10.55 so use:
wget https://github.com/Kreeblah/XGecu_Software/raw/master/Xgpro/10/xgproV1055_setup.rar to download that file.

If the problem persists after the firmware update please do more tests like leave the ZIF socket blank and issue a blank check like this: minipro -p AT28C64B@SOIC28 -b (btw, there's no AT2864 device in the database but AT28C64). If there are USB communications problems (stuck at a random percent) just wait for the timeout error (up to 20 sec) and paste that error here.

If you have the real chip you should pass the -z switch to check for a bad pin contact.
Also please specify your Linux distro/version and if possible your hardware, USB connection type (USB 2.0, USB 3.0).

And btw, a happy new year!

DavidGriffith commented 3 years ago

In GitLab by @AlaskanEmily on Jan 2, 2021, 15:34

OK, I updated the firmware. Writing seems to work correctly now, but reading still randomly gets stuck.

Trying -z says Pin test passed. I also ran -t and it showed everything as OK.

I'm using VoidLinux. The programmer is plugged into USB3, the entry for my USB controller in lspci is USB controller: VIA Technologies, Inc. VL805 USB 3.0 Host Controller (rev 01) if that helps.

DavidGriffith commented 3 years ago

In GitLab by @radiomanV on Jan 3, 2021, 06:15

OK. Can you please remove the chip and do a dummy blank check? minipro -p AT28C64B@SOIC28 -b
If a stuck happens please don't CTRL-C and wait for an error message. I need that error message.
Alternatively you can try to open a new terminal window and dmesg -w then in another terminal window do a read or a blank check. This way you can catch any hardware issues if any.
Also you can try to change to a USB 2.0 port or a powered USB hub. I suppose we are talking about x86/PC platform not ARM right?

DavidGriffith commented 3 years ago

In GitLab by @AlaskanEmily on Jan 20, 2021, 23:53

I'm using an amd64 PC, yes. uname -rsm says: Linux 5.9.16_1 x86_64

Trying with minipro -p AT28C64B@SOIC28 -b it stops at 0%. I waited for several minutes, no changes or messages on dmesg -w. top shows minipro using no CPU time either. I can wait longer, but it really seems like it's just not doing anything.

If I plug into a USB hub, then it seems to work correctly though, and trying several times in a row the issue doesn't happen. This machine doesn't have USB 2 ports, but the USB hub I tested with is only USB 2.

DavidGriffith commented 3 years ago

In GitLab by @tomstorey on Jan 22, 2021, 03:15

If you have another USB cable, give it a try. I had issues like this when using a seemingly dodgy USB cable. Swapping to another one (the original, in fact) resolved the issues completely, no matter how much I jiggled the cable.

DavidGriffith commented 3 years ago

In GitLab by @radiomanV on Jan 23, 2021, 21:46

If I plug into a USB hub, then it seems to work correctly though, and trying several times in a row the issue doesn't happen

Looks like a hardware/firmware issue here. Not necessarily a faulty part but perhaps some incompatibilities between kernel/firmware/libusb and some motherboard chipsets. Hard to tell which one (i suspect a bad firmware usb stack).

Users reported this kind of issues on Linux since the first TL866 version. You can also read here: issue #148