Watch this before you buy an XGecu T48 or T56

Просмотров 2 тыс.

% 20

Recently purchased the XGecu T48 USB programmer to program some Microchip 12F509 chips. Discovered after it arrived that even though it said it supported the 12F509 the software did not actually work correctly loading the Intel Hex files for the 12F509. It would load the code portion (I believe...) but would not set the config registers. Contacting support got a promise it would be fixed in the next release of the software. They also suggested I manually set the config registers which might work for a one off, but if you are doing any debugging that gets old fast. I waited 2 months for the next release and it was not fixed. I contacted support again and they sent a HEX2BIN program that I presume was to convert my Intel Hex files to BIN format that might have worked with the programmer but this would add steps to the process and the utility was totally in Chinese so I wasn't sure exactly how to use it.
I realized I could have avoided the whole experience by trying their software in demo or simulation mode before purchasing the programmer and I would have discovered their support for my particular chips does not work. So before buying, download the software. When you run it without a programmer attached it will run in simulation mode. See if it loads your code in simulation mode correctly. I also learned that there is no real way to add your own device to their program nor does there seem to be a way to modify existing devices in their support list... it LOOKS like you can add but all it seems to do is copy an existing device. Unsure of the purpose of that feature.
I should add that this did not seem to be a code issue. I tried Intel Hex files produced by multiple different compilers like Microchip MPXLAB and Great Cow Basic and others. All the hex files produced failed, and all the hex files produced worked when I used my PICkit5 programmer.
I liked the device and when programming chips that it properly supported it worked well but the main two devices I now use were not correctly supported and their software release schedule is quite slow and do it yourself options are unavailable. Always sad to see good hardware limited by the software.
I purchased directly from XGecu and found them unwilling to provide return instructions but fortunately I had used PayPal so I opened a dispute and got a quick response and a return shipping label.

Наука

Опубликовано:

17 фев 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 8

@georgec7798 20 дней назад

I think you're forgetting about the update that they give you for free. Every time they update the software they add another part number BGA/ NAND / IC Etc..... I have the t-56 and when I type my part number into the box it always shows up and I'm able to read it right to it. Maybe the t48 had more problems then the t-56

@tjones99 20 дней назад

The problem is the software not the T48 (or T56). You can run the software in demo mode without a programmer attached (which is what I advise before buying) and select your chip type and load your Intel HEX file. No I did not forget about the update they give you. I tried the update, I contacted support, I waited for the NEXT update where they promised to fix the issue and it was still an issue. I tried t5yhe following versions and NONE of them loaded my HEX files properly. 705, 1250, 1263, 1266, and since you reminded me I just downloaded 1267 and tried it and guess what? Out of Address of Device. (And for yuks I selected T56 as my programmer in demo mode). So no, I didn't forget the update and here we are 8 months later and they still haven't fixed the software. Like I said, great hardware... but the software and support sucks.

@tjones99 20 дней назад

Oh and I have no trouble SELECTING the chip type 12F509... it is when I load an Intel HEX file that was made FOR the 12F509 that the software says the Intel HEX file is invalid. Compiled using multiple versions of MPLAB and MPLABX and also with Great Cow Basic and other compilers that support the 12F509. The Intel HEX files work with my other programmers.

@georgec7798 19 дней назад

@@tjones99 Where can I get my hands on one of those chips that you are having trouble with I can test it for you in my t-56 and see what happens but you will have to tell me what to do or what to write to it, unless you just want to read it for now.

@steveholvoet6058 3 месяца назад

So their software has a hex parsing limitation. Seems like a minor bug. As they advised, hex to bin is easy. Did you try exporting from their software with the config bits set and comparing to the original? Did you actually try debugging the rootcause? How much was it to ship the (non defective) unit back? The device supports the chip, so yes they are correct in stating it does so. That is not to say the software that drives the device is perfect.

@tjones99 3 месяца назад

I agree it seems like a minor bug and after pointing it out to XGECU support and them saying they would fix it in the next release and waiting 2 months for that next release to find it not fixed is pretty sad and also an indicator of their support level in my opinion. Here it is 4 months from contacting support and no new release since the one at the 2 month mark... I have been watching. As I said in the video, I do LIKE the device, if they fixed the software I would likely purchase it again... The device works only with their software and their software so exactly how are they correct in stating it supports the devices I use when it does not correctly load a code file to program the devices? It has a 40 pin ZIF socket, does that mean it supports any chip you can plug into that socket? No. Supporting a chip means you can load a code file and program the chip... without errors. I do not disagree that hex to bin is easy and yes, if you import the file, manually set the config bits and save the file and reload it, it APPEARS to be correct, but when you are writing and testing code and there are multiple iterations happening do you really want to have to be manually setting the config bits for every iteration? The chances of making a mistake and testing defective code go up and the time spent goes up. Do you actually trust that the software is going to do the right thing when programming? The only way to be sure it is programmed correctly would be to program it with the XGECU unit then verify it using a different programmer that loads the code correctly. If it gives you and error message and fails to load the config bits, how else are you supposed to verify that the device is programmed correctly including the config bits? What exactly do you suggest for debugging the root cause. I tried producing HEX files using 4 completely different development environments as well as multiple versions of the MicroChip development environment. All produced very different looking hex files. All produced the error. I tried making my own "device" in the software (which as far as I can tell simply allows you to copy an existing device and name it something else so I am not really sure what the purpose of that is). I just tried loading the hex file and manually setting the Config bits and saving the hex file and then comparing the hex files and there appear to be differences in the hex files that makes me not trust that process. I also went back and gave their Hex2BIN utility another shot and was not able to get it to open a hex file without a program exception (and the all Chinese menus do not work as normal and the only way I found to open a hex file was to right click and select what I think is Open)

@steveholvoet6058 3 месяца назад

@@tjones99not sure what is going on, but I just picked some random PIC12F509 project from github (/tanahome/S2DP_PIC12F509), loaded the source in MPLAB X IDE v6.20, and compiled with MPLAB XC8 Compiler. The resulting hex file loaded no problem at all in MiniPro (TL866), but as you found out Xgpro (T48/T56/TL866II Plus) spits out that error. the older MiniPro software also gives the option to enable or disable the CONFIG region. whereas Xgpro only shows the "FLASH" region. So i just think they did not implement parsing the CONFIG bits in their software. That is a serious regression.