Anyone tried it, what settings are recommended in eepe or companion9x?


TIA!
Code: Select all
=================================================================================
Started AVRDUDE
C:/Program Files (x86)/companion9x/avrdude.exe -c usbasp -p m64 -U eeprom:r:C:/Users/CAJTAR/AppData/Local/Temp/temp.hex:i
=================================================================================
avrdude.exe: error: could not find USB device "USBasp" with vid=0x16c0 pid=0x5dc
=================================================================================
AVRDUDE done - exit code 1
=================================================================================
Code: Select all
Bluetooth AVRCP
HID-compliant device. Logitech. HID\VID_046D&PID_C52B&REV_1201&MI_02&Qid_2011&WI_02&Col03
HID-compliant device. (standard system devices). HID\VID_046D&PID_C52B&REV_1201&MI_01&Col04
HID-compliant device. (standard system devices). HID\VID_046D&PID_C52B&REV_1201&MI_02&Col02
*HID-compliant device. (standard system devices). HID\VID_03EB&PID_C8B4&REV_0100
HID\VID_03EB&PID_C8B4
HID_DEVICE_UP:FF00_U:0001
HID_DEVICE
HID-compliant device. (standard system devices). HID\VID_046D&PID_C52B&REV_1201&MI_01&Col03
HID-compliant device. (standard system devices). HID\VID_046D&PID_C52B&REV_1201&MI_02&Col01
Logitech HID
Logitech HID
Logitech HID
Logitech HID
USB Input Device. (standard system devices). USB\VID_046D&PID_C52B&REV_1201&MI_01
*USB Input Device. (Standard system devices). USB\VID_03EB&PID_C8B4&REV_0100
USB\VID_03EB&PID_C8B4
USB Input Device (Logitech Download Assistant)
This sounds like just a waste of time - even if you could change the VID/PID avrdude is looking for when set to USBASP, it simply wouldn't work because your programmer isn't actually an usbasp, and certainly doesn't use the same protocol.jbeebo wrote:I looked into the avrdude.conf file and could not find references to the port hardware ID's that AVRDUDE is searching for.
Code: Select all
=================================================================================
Started AVRDUDE
C:/Program Files (x86)/companion9x/avrdude.exe -c stk500v2 -p m64 -P avrdoper -U eeprom:r:C:/Users/CAJTAR/AppData/Local/Temp/temp.hex:i
=================================================================================
avrdude.exe: avrdoper_open(): Device not found.
=================================================================================
AVRDUDE done - exit code 1
=================================================================================
No idea, you'd have to recreate the schematic of your programmer to see if it's identical to an USBASP. If yes, then you could certainly flash it with the usbasp firmware indeed.jbeebo wrote:Last question, is there any salvaging the device I have in hand now; can I reflash this programmer with the new programmer and if so, how?
Code: Select all
avrdude: set SCK frequency to 8000 Hz
avrdude: error: programm enable: target doesn't answer. 1
avrdude: initialization failed, rc=-1
avrdude: AVR device initialized and ready to accept instructions
avrdude: Device signature = 0x000000
avrdude: Yikes! Invalid device signature.
avrdude: Expected signature for ATMEGA8 is 1E 93 07
Well, I know the '-F' can do nasty things, but I used it because nothing else worked.jhsa wrote:I'm surprised you didn't kill it by using the -F option. Never, ever use that.
Connection is a regular flat 10-pin cable that comes with a programmer (I tried two different cables, just in case...). I think I don't need to cross MOSI and MISO lines, right?Check connections are correct and that you selected the correct chip.
Yes. The power goes through - the LED on the target programmer lights up. That LED also momentarily switches off when avrdude tries to access the chip - which means the RESET signal goes through, too. But that's just it - avrdude doesn't get anything back from the chip...Also does your other programmer power the one you're trying to flash?
avrdude does support the HID device, the hardware is called avr-doper. It emulates stk500 (-c stk500v2) and the port option (-P avrdoper) is set to 'avrdoper'. The advantage is no drivers are needed for windows. The disadvantage is that avrdoper is several times slower than usbaspandrewju wrote:A friend of mine gave me his MX-USBISP-V3.02 dated 2014-10-08. The device is recognized as a HID in Windows, but is not supported by the avrdude.
Looks like Mike had already mentioned this. Man this is another old resurrected threadMikeB wrote:Don't forget to try:
protocol stk500v2 and port avrdoper.
Mike.