0x55c5aa34 (30th June, 2020), bg17aw (19th March, 2019)
Yes there is a way using your programmer.
Step by step:
1. download the latest avrdude .zip archive (for windows) from here http://download.savannah.gnu.org/rel...rdude/?C=M&O=D at the moment it is avrdude-6.3-mingw32.zip
2. extract archive
3. download libusb0.dll driver from here https://www.dll-files.com/libusb0.dll.html better 32-bit i think, place it in folder where you extracted avrdude
4. open cmd and change directory to folder with avrdude. Put cd and right click to paste your path.
5. Now make your backup files executing commands as follows:
avrdude -c usbasp -P com5 -p m162 -b 19200 -U flash:r:backup_flash.bin:r
avrdude -c usbasp -P com5 -p m162 -b 19200 -U eeprom:r:backup_eeprom.bin:r
avrdude -c usbasp -P com5 -p m162 -b 19200 -U hfuse:r:backup_hfuse.bin:r
avrdude -c usbasp -P com5 -p m162 -b 19200 -U lfuse:r:backup_lfuse.bin:r
avrdude -c usbasp -P com5 -p m162 -b 19200 -U efuse:r:backup_efuse.bin:r
avrdude -c usbasp -P com5 -p m162 -b 19200 -U lock:r:backup_lockbits.bin:r
after executing each command you should see something like this:
1.jpg1.jpg
In folder with avrdude you now have backup files of your atmega.
To restore your backup reflash it into your atmega162 proceed likewise but instead :r: for read before the
filenames put :w: for write. For flash you will give a command:
avrdude -c usbasp -P com5 -p m162 -b 19200 -U flash:w:backup_flash.bin:r
Connections are good. To enable bootloader you need to flash it with firmware kolimer's firmware. Put right firmware files 0x44 or 0x46 (for example Flash1.96_HW_0x44.bin and eepromavr_HW_0x44.bin) in your avrdude folder and proceed with the commands given in the info file from kolimer.
Last edited by bradzk; 19th March, 2019 at 02:56 PM.
0x55c5aa34 (30th June, 2020), bg17aw (19th March, 2019)
Success! Thank you for your incredible contributions! I am now running 18.9.0 and my bootloader is UNLOCKED!
I suggest the kolimer zip pack should be updated with a bit more help/documentation, like recommending the following config when installing VCDS to avoid lunching vcds.exe instead of Kolimer's loader, please see picture
I noticed L7805CV is getting incredibly hot even while testing with the plastic covers removed, I can only imagine what happens when the interface is assembled.
Some sort of cooling might be appropriate.
I also found out avrdude says something about not being able to set SCK, and recommends updating firmware on USBASP programmer, however, our cheap USBASP do not have jumper 2 to be able to get into firmware update mode. The original one actually has a 3rd jumper as well. If I would be to do this again, I would buy the original (although postage might be an issue)
Last edited by bg17aw; 19th March, 2019 at 03:32 PM.
bg17aw (19th March, 2019)
FA24, sorry.
Yes, i did remove the two jumpers.
By the way, when is needed to reflash FTDI as well?
For K solution never needed. I suggest desolder AES chip. That chip with 2x4 pins in neighborhoud of that 2 jumpers..
I saw you made tests and test ok.. For Test=OK, driver must installed OK. So..what you done between first test and K upgrade?
Last edited by liviudiaconu; 20th March, 2019 at 07:01 AM.
You can replace the L7805CV with an "Adjustable Step Down Power Module" like this:
https://www.ebay.de/itm/272718624682
It is pin conpatible and so easy to install / solder in.
bg17aw (20th March, 2019)
bg17aw (20th March, 2019)
Simple for someone with skills, for me it was quite hard to solder a few wires to be able to program the thing... and I already had the programming pins.
I don't see any pins on that power module, how do you solder it to the board?
I might try and do it, I think it is getting too hot for a summer drive logging session for example
On cable with ATMEGA162, FT232RL, GAL ... the led is OFF (no green no red) when OBD is connected, which chip may not work?
- on the 7805 there are both 12V and 5V
- the computer knows the cable drivers
- LED on cable ALWAYS OFF
I have to say, after updating from 17.1.0 to 18.9.0 I am getting some "Communication Error" errors... I installed 18.9.1 and still get them.
Randomly and not too often, but I never had a single one while on 17.1
Is there something I could check/do?
I did manage to do a full auto-scan, but still a bit concerned.
Last edited by bg17aw; 20th March, 2019 at 12:46 PM.
Bookmarks