Hi guys when I try to program with usbasp my cable I have a message that show "chip enable program error". May be because first time I try to erase chip and then to write atmega by usbasp but I missed to give 12V. So now if I try to program correctly with 12V I have this message and I can do nothing. Can you help me what I have to do to repair cable?
Почему у вас есть 35-36,
Last edited by Roma77; 23rd August, 2018 at 09:13 AM.
Hello all
I'm new to this forum, I have read a lot of posts including in the thread and I probably still need help.
hardware as in the pictures
IMG_20180823_092706.jpgIMG_20180823_092724.jpg
atmega 162 16AU
ATF16V8BQL
STC11F01
FT232BL
MCP2515
MCP255
I am asking for info on how to upgrade to newer versions, I have a usb programmer.
Thanks in advance for your help.
first download from here kolimer v6.3 https://www.sendspace.com/file/em3y1f
AV or Windows Defender off
plug in your cable into OBD socket car
run VAGCOM_HWType as admin and report
Last edited by belkor; 23rd August, 2018 at 10:01 AM.
He has STC chip. Need to sort that out before. Read info.pdf from archive but he have to do it anyway.
Last edited by kaalis; 23rd August, 2018 at 10:08 AM.
belkor (23rd August, 2018)
belkor (23rd August, 2018)
fatal error.PNG
So, why I receive this error and how can I fix it?
Educated guess: USB cable malfunction or FTDI chip (almost) dead
edit: after reviewing your pictures, i agree 100% with kaalis
Last edited by networkers; 23rd August, 2018 at 05:01 PM.
I will order I FTDI Chip.
Sent from my Mi A1 using Tapatalk
Use multimeter to find pads(near to usb 4 wires) coresponding to Atmega 1.2.3.4.
For this interface you do not need to worry about STC. Just read with usb programmer just to check if you find the rigth pads and than write x46 dumps using the corect bits as are described in info.pdf.
Use mprog to write eeprom to ftdi.
You don't need to add 12V when you flashing with USPASP / USBISP. It needs only 5V through USB port.
I got the same "chip enable program error" when I try to use this cheap ($1.25) programmer under Windows 10 (64-bit):
usbasp.jpg
For this the solution for me was a good driver: USBasp Driver (libusbK v3.0.7.0)
With this the Windows device manager recognized the programmer. Works proper with ProgISP 1.72
Previously I tied an another programmer and I can offer this one ($2.30), what was recognised automatically by the Windows. No extra driver needed.
Windows device manager recognized the programmer. Works proper with ProgISP 1.72 and it recognised the programmer as "ZF-008 HV Programmer Ver: 1.6"
usbisp.jpg
Bookmarks