EEVblog #411 - MiniPro TL866 Universal Programmer Review

[PA0PBZ]

OTP means One Time Programmable, once they are set there's nothing you can do.

[aissaok]

there is a programateur (nandprog) when you  can be erased serial number
this option is Q64FVS8_SRegister

[aissaok]

helo
here is th site of nandprog
http://www.freewebs.com/easyflash/

[rastro]

...

that would indeed be great! Currently I'm using OSX and the only way to use this programmer is by using a virtual machine on my computer running Window$. Until the last update, VirtualBox would refuse to connect the TL866 to the virtual machine, so I had to use Parallels to make any use out of it.
...

TL866 does work, just use the Oracle virtualbox install, not the repository version. The repo one does not handle the USB passthrough correctly, though it will do media and HID devices perfectly, it will not do other classes of device. All you lose is the automatic update, you will have to watch kernel versioning, though if you install the repository version first it does then keep the kernel updated, as the Oracle one uninstalls it partially during install.

I'm currently trying to get my TL866 running under virtualbox but can not get the virtual machine to attach to the usb. I think this is referred to as "USB pass through".  According to prior blog comments this may be due to the software source.  Could someone explain the difference between "Oracle virtualbox install" and "repository version".  More specifically where do I go to get the correct install.

My Setup:
Virtualbox: 4.3.6 r91406 (from:https://www.virtualbox.org/wiki/Downloads)
HOST: OSX 10.9.1
VM:   W2K

Thanks
Rastro

[SeanB]

Install the extensions pack from there as well, and it will do the usb passthrough with no problems.

I am having issues with the latest, so use the 4.22 version and packs.

https://www.virtualbox.org/wiki/Download_Old_Builds_4_2

[rastro]

Install the extensions pack from there as well, and it will do the usb passthrough with no problems.

I am having issues with the latest, so use the 4.22 version and packs.

https://www.virtualbox.org/wiki/Download_Old_Builds_4_2

Thanks for the recommendations.  Unfortunately I was not successful. 

I tried using 2 older Virtual box revisions (4.2.22 and 4.2.20 ) along with their respective extension pack but I still could not get it to "usb pass through".  I can see the MiniPro as a choice in the device drop down menu, but when selected it will not put a check mark next to the device.  If I return to the drop down menu and try enable it again I get an error message stating that the device is servicing another request - I assume it's referring to the initial request.  If I replug in the usb I can repeat the process with the same results.

I also tried the above attempts with "Enable USB 2 (EHCI) controller" ON/OFF with both VB revisions.

My system information shows the USB:
MiniPro TL-866 Programmer  :

  Product ID:   0xe11c
  Vendor ID:   0x04d8  (Microchip Technology Inc.)
  Version:    0.00
  Speed:   Up to 12 Mb/sec
  Manufacturer:   www.autoelectric.com     
  Location ID:   0x14400000 / 1
  Current Available (mA):   500
  Current Required (mA):   100

The only other thing that I can think of is OSX Maverick compatibility or security feature.

Any further guidance would be welcome.

Thanks
rastro

[Bimmeristi]

Hi!


Is there tutorial or how to read 29F400xx etc chips with this tool?

[radioman]

The new 6.0 version of minipro software was released: http://www.autoelectric.cn/minipro/minipro_setup.rar

From manufacturer changelog:

2014.01.07 V6.00
Support Chip count: 13183

New chips:
MD25D40/80/16 GD25Q128C GD25Q128B
N25Q032A N25Q064A AT25DF641
Micropchip 93LC46X/56X/66X/76X etc.

Correction: Micropchip 24LC65

Improvements:
Windows 8 support.
Up to four programers simultaneously.
Improved Gui for different  display DPI.

Also my firmware updater/generator still working    the update.dat file structure was not changed, this is good for me!

I will release an advanced version of my tool with the ability to change bootloader version, device serial number and copy protect bit on the fly; one of forum member tested this new version and the result was good.

[BravoV]

Hey radioman, thanks for the news ! 

Also my firmware updater/generator still working    the update.dat file structure was not changed, this is good for me!

I will release an advanced version of my tool with the ability to change bootloader version, device serial number and copy protect bit on the fly; one of forum member tested this new version and the result was good.

    

[Florin9doi]

@radioman
I used your tool to update CS to A. Now can I use official software to update firmware for v6??

[radioman]

@radioman
I used your tool to update CS to A. Now can I use official software to update firmware for v6??

Yes, you can Florin!
 
Da-mi un pm te rog!

[radioman]

Here is the new version of my firmware updater: TL866 firmware updater
Now you can transform your device version (by changing bootloader version) on the fly, without need of an external programmer. In my previous version the bootloader remained unchanged, and firmware upgrades from minipro software was not possible. 

Also you can change code protection bit and device serial number, just in case, who knows what autoelectric is planning, but from what i seen in their "new redesigned interface" probably not.

[casinada]

Thanks Radioman for your magic software. I don't need to use because I have the A version but your dedication is appreciated.
I downloaded the new version and it told me to update "Firewire" I assume they meant firmware. Went to tools, reflash firmware and everything is good
Now it supports the chips I needed to program to repair an HP Envy 20 motherboard last month a little bit late ......
I hope they keep supporting the unit for a long time.

[radioman]

I downloaded the new version and it told me to update "Firewire" I assume they meant firmware.

Well, this is better than "Update your 1394" 

[ElektroQuark]

Mine has updated "fireware".

[mladen82]

Hello!
I have problems with programming bios chip MX29LV800CTTC (from an notebook)
I can read and erase chip, but when i try to programm with new BIOS rom file i getting error


There is NO error when i tried to program with FFFFFs!!!

I tried both adapters  adapter with soldering the chip and adapter without soldering needed so i assume is not ''bad connection'' issue.

Is there problem with the chip or something else?

Thanks in advance.

[radioman]

Click Read ID button first and see if the chip is detected in the product identification field.

Oh, now i see in the screenshot the 00C2 22DA chip ID.

Erase memory first and do a blank check to see if is erased.

[mladen82]

Device is blank for sure, when is erased.

[radioman]

Fill the buffer with different data patterns like 5555 and AAAA and write to see if the memory is good.

[mladen82]

I getting errors with 5555 and with AAAA, only with FFFFs no error.
Sometimes i get erro on 0x0002 adress, and sometimes on 004020 or something like that.

[radioman]

Must be a bad pin contact or something to zif40 adapter, if you get verify errors at random addresses. Also you don't have verify errors with FF's because of pull-up resistors on the data bus, so if a pin has a bad contact then that pin will be always read as 1.

Try to insert TSOP48 adapter in another position in the ZIF40 socket maybe is a bad contact.

[aissaok]

hello
Please show the operation of transforming minipro cs minipro tl866 tl866 A
step by step
thanks

[radioman]

@aissaok, what kind of transformation, hardware or software?

In hardware yo must solder a 6-pin connector to unpopulated ICSP header:

After that you must reflash your device with A firmware and this can be done in different ways depending on if you have an pic programmer or not.

[aissaok]

transformation software
I do not have a PIC programmer

[mladen82]

Must be a bad pin contact or something to zif40 adapter, if you get verify errors at random addresses. Also you don't have verify errors with FF's because of pull-up resistors on the data bus, so if a pin has a bad contact then that pin will be always read as 1.

Try to insert TSOP48 adapter in another position in the ZIF40 socket maybe is a bad contact.

probably TSOP48 adapter is poor quality