Try changing device to ATmega328P. Usually if it cant detect the uP there is a connection problem.

#firmware #qcx

When I click on DETECT, AVRDUDESS returns this: ERROR: Unknown signature ffffff Then, if I check off the -F (force) box then click GO, I get this returned: avrdude.exe: Device signature = 0xffffff (pr

#firmware #qcx

Use detect to let the software determine the cpu.This verifies connection is working. Let the software read ( check read) the fuses. Do not click write Uncheck write under EEPROM and check read just i

#firmware #qcx

So I did go to the link you included and did set the fuses as set forth in that link. Still, not working. Here is what I got from AVRDUDESS: -c arduino -p m328 -P COM8 -b 19200 -U flash:w:"C:\Users\w8

#firmware #qcx

Alan: Thank you for your patience with me. Please excuse my ignorance, but how to I "check the fuses" and how will I know if they are correct or not? Also, do I assume correctly that I do not need an

#firmware #qcx

Arnie, Please, I said "Check the fuses FIRST" If the fuses are not correct then that adds a little extra complication. Luckily for some reason it did not identify the chip and did not flash the .hex.

#firmware #qcx

So I followed the directions for using the ArduinoISP sketch with AVRDUDESS. This is what I got, and it looks like it did not work: Does anyone know what I did wrong? Is it the fuses? If so, how do I

#firmware #qcx

Arnie, The Arduino is just a link between Avrdudess or whatever programming tool you use and the QCX. It is the QCX that needs the fuses to be correct whatever way you use to program it. Perhaps if yo

#firmware #qcx

Thanks Alan. I will check that out. Are fuses an issue if I go the Arduino route?

#firmware #qcx

Arnie, There is not really any difference, just the .hex file. BUT to be sure you must first check the fuse settings. Any received from the USA distributor may be wrong. See this https://groups.io/g/Q

#firmware #qcx

Mates: I have a 30m QCX which I built a while ago. I would like to update the firmware to 1.05 but am not sure how to do it using an Arduino. Can someone give me a step-by-step? I did see some instruc

#firmware #qcx

Marek, As Wes has suggested compare the voltages on the two boards first. 73 Alan G4ZFQ

#firmware #qcx40

It is possible that the old uP just needs to be reflashed. Try that first ...

#firmware #qcx40

Thanks guys, I will check voltages on the old board first over the weekend. However, if the old uP (T 1.00g) is cooked and I put it into new fully working v5 board all I will get is no display. New bo

#firmware #qcx40

I had written the firmware V3.12a.hex using the V3.09.eep and all seems to work fine (using AVRDude). Now it is a good piece of mind to know that the eep is not needed anymore as it sounds that the ma

#smoked #firmware #u3s

The only concern would be that your problem is caused by a damaged uP and that was caused by a problem on the board. If so, then the second uP may well receive damage too. Check voltage with original

#firmware #qcx40

Marek, It is compatible - all versions are comptible - certainly for driving the display - it's just the behavior and features that differ. I upgraded one of mine from 1.00g all the way to 1.05. Julin

#firmware #qcx40

Is there any problem with pluging previous version (T 1.00g) microcontroller instead of current T 1.04 on Rev 5 board? I purchased assembled version QCX for 20m band, which has issue with block top li

#firmware #qcx40

Just read all the directions carefully first and make sure you have the fuses set according to the most recent configuration first.

#firmware #qcx40

On Sun, Jul 12, 2020 at 09:50 AM, Alan G4ZFQ wrote: Jack, Avrdudess and a USBasp are used by quite a few. https://sites.google.com/site/g4zfqradio/qrplabs_program_chip_with_USBasp I have been using th

#firmware #qcx40