EEVblog > EEVblog Specific
EEVblog #411 - MiniPro TL866 Universal Programmer Review
kerouanton:
Some feedback about my current tests:
- I've checked how XgPro defines the IC list. It's not a text nor a binary file, but an executable DLL called InfoIC2Plus.dll that seems to contain all IC references. Disassembling it shows some function exports (GetDllInfo, GetIcList, GetIcMFC, GetIcStru, GetMfcStru) that seem related to setting the right parameters. So it's not really convenient to alter the DLL and change any parameters (but should be possible in theory).
- The PIC16F1938 has a flash size of 0x4000, but the only similar MCU that I found and used to create the Custom IC is a PIC16F1829 that has only 0x2000 for Flash. That explains why my firmware doesn't work as expected.
- I've checked on the Microchip which PIC MCUs have 0x4000 flash, but all the references I found are not listed on XgPro (16F1519, 16F1939, 16F1527, 16F1947, 16F1518, and 16F1938).
So, has anyone succeeded in flashing a PIC MCU with a flash size > 0x2000 ? I'm beginning to believe the TL866-II Plus and T-56 don't support this flash size, but that seems weird because it's not so difficult to implement.
Quench1:
A new model of TL866 (3rd generation) has just been released - the "TL866-3G" aka the "T48":
It's supported in software version starting from v12.01
https://www.aliexpress.com/item/1005004434848306.html
Looks like the TL866ii+ will be killed off considering the price.
tokyoskies:
--- Quote from: Quench1 on June 22, 2022, 05:24:57 pm ---A new model of TL866 (3rd generation) has just been released - the "TL866-3G" aka the "T48":
It's supported in software version starting from v12.01
https://www.aliexpress.com/item/1005004434848306.html
Looks like the TL866ii+ will be killed off considering the price.
--- End quote ---
Seems to be the market strategy. I got mine 3 days ago for a steal. Should I be worried???
On that note, I am worried, as my TL866II Plus is not really working! I posted my issue on XGECU forums and got some responses, but its just basically telling me that all my EEPROMs are too old and possibly faulty.
Hard to believe that, since I got some of them from Digitec on Wednesday. Anyway, I went through this thread and some folks seem to have had a similar issue. I am trying to program SST39VF020@PLCC32 with a bin I just read of my 2 "Master" EEPROMS (also SST39VF020).
I can read master and the "blank" EEPROMS fine. I saved the bin files of both masters. Now, I cannot seem to write the master bin to the blank chips. I cannot erase the blank chips either. I then thought "what the heck, I saved the master bin file, so lets erase the master eeprom".
It does not erase that either, in fact I cannot erase any chip. When trying to program a chip with the Air_Master.bin I get the following error:
APP Version : 12.05 Model : TL866II Plus
Device : SST39VF020 @ PLCC32
Pins Detected Passed!
ID: 0x FF FF ......OK!
Erase ...Succeeded. Time : 0.390 S
Programming FLASH ...
ERROR! Address:0x000000 Buffer Data:0xA0 Verify:0xFF
Programming ...Failed
I did create a new chip with ID FF FF, as I always get a Chip ID error when reading or writing, no matter what chip I use.
I tried:
1. Different USB Cable
2. Different PC with Windows 7
3. Downgrading the firmware from 12.05 to 10.13, 10.35, 11.90
4. Re-flashing 12.05 several times
5. Checked the ZIF PLCC32 socket adapter
6. Bought a new PLCC32 socket adapter
7. Bought 6 new SST39VF020 (in total I have 10 now and none can be programmed)
8. Tried a similar chip profile (Cat28F020 and Cat28C256) - Cat28F020 seemed to work at first. The erasing took much longer than on the native profile. Programming then took about 5 min, but failed in the end anyway.
9. I tried several USB ports and hubs
10. Self-Check is OK on all pins and OC protection
I am now thinking to send this back and get myself a Batronix.. Much more expensive, but if it works....
CRC:
--- Quote from: tokyoskies on July 22, 2022, 12:03:16 pm ---
--- Quote from: Quench1 on June 22, 2022, 05:24:57 pm ---A new model of TL866 (3rd generation) has just been released - the "TL866-3G" aka the "T48":
It's supported in software version starting from v12.01
https://www.aliexpress.com/item/1005004434848306.html
Looks like the TL866ii+ will be killed off considering the price.
--- End quote ---
Seems to be the market strategy. I got mine 3 days ago for a steal. Should I be worried???
On that note, I am worried, as my TL866II Plus is not really working! I posted my issue on XGECU forums and got some responses, but its just basically telling me that all my EEPROMs are too old and possibly faulty.
Hard to believe that, since I got some of them from Digitec on Wednesday. Anyway, I went through this thread and some folks seem to have had a similar issue. I am trying to program SST39VF020@PLCC32 with a bin I just read of my 2 "Master" EEPROMS (also SST39VF020).
I can read master and the "blank" EEPROMS fine. I saved the bin files of both masters. Now, I cannot seem to write the master bin to the blank chips. I cannot erase the blank chips either. I then thought "what the heck, I saved the master bin file, so lets erase the master eeprom".
It does not erase that either, in fact I cannot erase any chip. When trying to program a chip with the Air_Master.bin I get the following error:
APP Version : 12.05 Model : TL866II Plus
Device : SST39VF020 @ PLCC32
Pins Detected Passed!
ID: 0x FF FF ......OK!
Erase ...Succeeded. Time : 0.390 S
Programming FLASH ...
ERROR! Address:0x000000 Buffer Data:0xA0 Verify:0xFF
Programming ...Failed
I did create a new chip with ID FF FF, as I always get a Chip ID error when reading or writing, no matter what chip I use.
I tried:
1. Different USB Cable
2. Different PC with Windows 7
3. Downgrading the firmware from 12.05 to 10.13, 10.35, 11.90
4. Re-flashing 12.05 several times
5. Checked the ZIF PLCC32 socket adapter
6. Bought a new PLCC32 socket adapter
7. Bought 6 new SST39VF020 (in total I have 10 now and none can be programmed)
8. Tried a similar chip profile (Cat28F020 and Cat28C256) - Cat28F020 seemed to work at first. The erasing took much longer than on the native profile. Programming then took about 5 min, but failed in the end anyway.
9. I tried several USB ports and hubs
10. Self-Check is OK on all pins and OC protection
I am now thinking to send this back and get myself a Batronix.. Much more expensive, but if it works....
--- End quote ---
I am having exactly the same result.
It's bizarre because it worked great the firsrt few days. I wonder if they are knockoffs and there is some sort of software detection going on that's bricking them.
Black Phoenix:
I know that is a working tool but heck the T48 is ugly as hell in terms of design. The MiniPro looked okay, but this one I can't go by the design.
It almost makes me try to design an alternative case for it in Solidworks. That and the font that Chinese like to use in their products, that kinda Times New Roman like called Zhongyi Songti.
But that's just small gripes I had, not regarding the tool itself since I've used in the last gig I done.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version