Documentation needs update

[dioannidis]

• How to build the firmware ( avr-gcc version, ... )
• How to flash the firmware ( especially regarding the eeprom eep file )
• Add to the USBaspHIDUART utility section informations regarding the dependencies needed for it to work on non Windows systems ( hidapi library with libusb backend . Didn't test with hidraw )

[tomj321]

Speaking of documentation - what is the eeprom.eep.hex file used for? There is no mention of this file anywhere and none of the many discussions / tutorials I have found on the topic of upgrading the USBASP firmware mention anything about this file. I took a chance on flashing both the main code hex file and then renamed the eeprom.eep.hex -> eeprom.eep using avrdude. Is this correct? Thanks.

[elfmimi]

I suppose "eeprom eep file" is referring to USBasp_EEPROM.eep.hex in the release zip.
it is meant to be flashed like this.
avrdude -c usbasp -p atmega8 -P usb -U flash:w:USBasp_ATMega8_12MHz_TPI_HIDUART_SNWRITE.hex:i -U eeprom:w:USBasp_EEPROM.eep.hex:i
as it is done at this line of the Makefile.

usbasp/firmware/Makefile

Lines 93 to 94 in 1255367

	flash:
	avrdude -c ${ISP} -p ${TARGET} -P ${PORT} -U flash:w:main.hex:i -U eeprom:w:main.eep.hex:i

eeprom is being used to store SerialNumber. and eep hex file provides initial value for SerialNumber which is "0000" .
USBaspHIDUART tool can be used to modify SerialNumber if you need to.

[tomj321]

I believe that I accomplished the same thing by using the AVRDUDESS gui to burn the eep file to the eeprom (although it wanted the file ext to be eep). However, while the USBASP successfully programs other chips and the USBDeview utility shows the fw version has been updated to 1.11 with serial 0000, the usbasphiduart utility fails to recognize the usbasp device.

As long as I can successfully program chips, I don't really care about the serial numbers, though it bothers me when things do not work as they are described to work - makes me wonder if things really are correct.

EDIT - I also note that neither USBDeview or checking the driver with Zadig indicate the upgraded USBASP to be WCID compliant, which appears to be a feature of the improved firmware... Although I have verified the eeprom was correctly flashed, perhaps I did something wrong in the process...

[elfmimi]

@tomj321
Wow, it was pretty hard to understand the implication and what should have been different in your case.
I suppose you are still using libusb driver installed with Zadig. so your USBasp must be enumerated as non composite device. in this situation Zadig won't show that USBasp as WCID compliant. and USBaspHIDUART tool won't recognize it.
try uninstalling the driver. or you may try plugging it into another computer.
reminder: you need to use MINGW build of avrdude as it is described here.