Topics

QCX firmware upgrade from 1.00g to 1.05.


João Cunha Lopes
 

Hi all.

I have been trying to upgrade my QCX firmware from 1.00g to 1.05.
Due to the world wide pandemic there are huge delays in mail, so I opted to buy a couple of ATMEGA328 locally.
Chips are branded ATMEL and they are "ATMEGAS328P U". Chip ID, when read by my programming software, is (hex) 1E950F.
I have read that this may be a problem when using avrdude:

avrdude.exe: Device signature = 0x1e950f
avrdude.exe: Expected signature for ATmega644P is 1E 96 0A
Double check chip, or use -F to override this check.

I'm using an old generic programmer (GQ-4X) with ISP interface to the chip. For my programmer the 1E950F is not a problem and it can work fine with this chip.
I've loaded firmware 1.05 into the "ATMEGAS328P U" and all when well.
When I tried the chip on the QCX all I got was a line with "##########################". The radio does not boot.
I checked the programming again and the firmware is in the chip.

There are a couple more things that I would like to try before giving up on this.
Fuses?

My programmer allows me to set the following:



Also, I have read that:

"There are a total of 19 fuse bits that are used in the ATmega328P, and they are separated into three different fuse bytes. Three of the fuse bits are contained in the "Extended Fuse Byte", eight are contained in the "Fuse High Byte," and eight more are contained in the "Fuse Low Byte".

From the above image its seems that I can set each and every fuse.
Can someone please point me in the right direction regarding the correct fuse setup?

Also I have noticed the OSC calibration bytes, 4MHz, 8MHz. How important is ths?

Anyway, If someone could point me to all the correct fuse values I would appreciate it.
Thank you.

John, CT2HME


N3MNT
 

The problem is you are trying to program generic parts.  The parts from QRP-Labs are protected to protect the firmware from clones. 


Richard G4TGJ
 

There's nothing special about the ATMega used in the QCX, you just need to program the correct fuse bits. Hans will supply the file for this.
--
73
Richard
G4TGJ


Alan G4ZFQ
 

Can someone please point me in the right direction regarding the correct fuse setup?
John,

The fuses are wrong. https://sites.google.com/site/g4zfqradio/qrplabs_program_chip_with_USBasp

BUT as Bob says you cannot flash a new chip without Hans' help.

73 Alan G4ZFQ


Richard G4TGJ
 

You also need the EEPROM file from Hans.
--
73
Richard
G4TGJ


Wes AE6ZM
 

You can upgrade the chip that came with the QCX. There would be no issues with doing that.
--
> I finally got it all together...now I can't remember where I put it<

VY 73,
Wes

AE6ZM

Sierra Vista, AZ

 


João Cunha Lopes
 

On Sun, Jun 14, 2020 at 04:49 AM, Alan G4ZFQ wrote:
BUT as Bob says you cannot flash a new chip without Hans' help.
Hi Alan,

thank you for help.
So, for the AT328MEGA, the correct fuse settings would be:

"Make absolutely sure you have the values correct. All QRP Labs Atmel328s L 0xD7, H 0xD1, E 0xFC"

I got the 1.05 hex file from the QRP Labs site:

http://qrp-labs.com/images/qcx/firmware/T1.05.zip

And regarding Hans, help: what kind of help?
Thank you.

John, CT2HME


João Cunha Lopes
 

> The problem is you are trying to program generic parts.  The parts from QRP-Labs are protected to protect the firmware from clones.

I'm confused. So, I can't program the 1.05 firmware on a ATMEL, blank, brand new "ATMEGAS328P U" chip?
Is this true? And if so, why is that?
Thanks.

John, CT2HME


Alan G4ZFQ
 

"Make absolutely sure you have the values correct. All QRP Labs Atmel328s *L 0xD7, H 0xD1, E 0xFC*"
Yes,

regarding Hans, help: what kind of help?
John,

You need a file, the firmware is protected so people can not copy it just by flashing the .hex.
I guess if you explain your problem to Hans he will help.
Or, as someone said, why not update your original chip?

73 Alan G4ZFQ


João Cunha Lopes
 

> There's nothing special about the ATMega used in the QCX, you just need to program the correct fuse bits. Hans will supply the file for this.

OK. I was avoiding bothering Hans with this.
First I'll try following what's written on this message:

https://groups.io/g/QRPLabs/message/24845

"So for clarification, these are the correct fuse settings for all current QRP Labs products using the ATmega328:

Low: 0xF7
High: 0xD1
Ext: 0xFC or equivalently, 0x04 (see above)"

Thank you.

John, CT2HME


João Cunha Lopes
 

On Sun, Jun 14, 2020 at 12:19 PM, Alan G4ZFQ wrote:
someone said, why not update your original chip

Txs, I'll give it a go with the original. Hope I don't brick the radio... 
73.

John, CT2HME


 

John,

Because the firmware is proprietary, not open source. If you could program completely blank chips you could easily replicate the hardware, produce chip copies, and sell clones. I believe there have been problems in that area. That would also be copyright infringement.

Julian N4JO.

On 6/14/2020 2:14 PM, João Cunha Lopes wrote:
> The problem is you are trying to program generic parts.  The parts from QRP-Labs are protected to protect the firmware from clones.

I'm confused. So, I can't program the 1.05 firmware on a ATMEL, blank, brand new "ATMEGAS328P U" chip?
Is this true? And if so, why is that?
Thanks.

John, CT2HME


João Cunha Lopes
 

On Sun, Jun 14, 2020 at 12:59 PM, Julian Opificius wrote:
I believe there have been problems in that area. That would also be copyright infringement
Oh I see. OK, got it.
Well, all I want is to upgrade my radio. That's it. :-)
73s.

John


 

Of course :-)

So, starting with the original chip, use the AvrDude programmer or adapted Arduino Uno, make sure the fuses are set as state in this thread, and use the Hex file. If you do everything according to instructions, it will go well.

I haven't read all the of the branches of the tree for this thread, so might not have answered all your questions. f there is something you don't know/have/understand, please reply; there are quite a few of us who have done this correctly.

Did I say "check the fuses" ? : -)

Julian, N4JO.

On 6/14/2020 3:02 PM, João Cunha Lopes wrote:
On Sun, Jun 14, 2020 at 12:59 PM, Julian Opificius wrote:
I believe there have been problems in that area. That would also be copyright infringement
Oh I see. OK, got it.
Well, all I want is to upgrade my radio. That's it. :-)
73s.

John


Arv Evans
 

John, CT2HME

After experience with others trying to clone his systems (stealing his design and software) 
Hans has implemented a software control scheme that is keyed to his file information.  If trying 
to install new software (or trying to re-install old or modified software) you need to contact Hans 
to get the install information that is keyed to your specific hardware.  The protection method 
seems to be a multi-level calculated comparison.

This was caused by clone builders selling poorly performing systems and expecting Hans to 
repair or replace their broken systems at his own cost.

Arv  K7HKL
_._

On Sun, Jun 14, 2020 at 1:14 PM João Cunha Lopes <joao.cunha.lopes@...> wrote:
> The problem is you are trying to program generic parts.  The parts from QRP-Labs are protected to protect the firmware from clones.

I'm confused. So, I can't program the 1.05 firmware on a ATMEL, blank, brand new "ATMEGAS328P U" chip?
Is this true? And if so, why is that?
Thanks.

John, CT2HME


Jacques - ZS1PL
 

See this thread that describes the upgrade process:
Upgrading to firmware 1.05

You CAN use a blank chip if you're worried about bricking your original chip, but then you need to burn both the hex file and the eep (EEPROM) file, and  make sure the fuse settings are correct.
I did this successfully a week ago.

Hans is very helpful and will supply you with the correct files if you email him and explain your situation. However you should note that the supplied files are for your use only and you should not distribute it to someone else.


João Cunha Lopes
 

Thank you all that pointed me in the right direction.
Couldn't have done it without Hans support.
All done.



73.

John, CT2HME


Dave
 

Looks great!  Now get it on the air!

Dave


On Jun 15, 2020, at 16:28, João Cunha Lopes <joao.cunha.lopes@...> wrote:

Thank you all that pointed me in the right direction.
Couldn't have done it without Hans support.
All done.

<IMG_20200615_211526.jpg>


73.

John, CT2HME