9XR(AT128) bricked, HVPP unbriked and then briked again.

[danielvc]

I'll try to summarize everything I've done so far ...


I tried flashing my 9XR radio with an old usbasp it had, but I had never used it.
During the process, usbasp gave some connection errors, but I tried to flash the microcontroller anyway.
It gave some error (I did not save the error) and the bricked the microcontroller, I could not communicate anymore.

I thought it was the usbasp I had, and I bought a new one. Without success with the new one.

I tried to recover by following the link below, without success.
https://www.rcgroups.com/forums/showatt ... id=3531567

I removed the microcontroller and was able to communicate using HVPP by following the link below:
https://www.instructables.com/id/HV-Rescue-Simple/
Soldering the wires was easier than I thought it would be ...

I changed the fuses to the standard L-E1, H-99 and E-FD, with a small change in code also proceeded with a "Chip Erase"

I was able to communicate with the chip via USBASP again.
https://www.youtube.com/watch?v=iJUCiUd ... e=youtu.be

I soldered the chip on the motherboard, and I was able to communicate normally with the chip.

I uploaded the file "er9x-128.hex" and uploaded my settings (my_setings.eepe).

With "eXtreme Burner", I just changed the Extended Fuse to "FF". I continued with the USBASP connection running.

I turned the USBASP off and placed a fully charged battery, the radio turned on and worked, got really slow, but it worked.

When I entered the main screen, the voltage dropped considerably by up to 3v. and kept swaying. I found this oscillation in voltage very strange.

When I tried "reset fuses to factory defalt" ( L 0E, H 89 and E FF ) in the EEPE, it briked again.

Any suggestion?
Is the chip faulty? Or can it be any problem with cystal?

Something about oscillation in voltage?
I do not understand brown out detection, but I know it has something to do with the voltage ...
The voltages on the mais board is 5v and 3.3v...

[jhsa]

The normal procedure to un-brick a radio is to use a 1MHz oscillator connected to the crtstal, not with HV..
You can use an arduino to generate the 1MHz pulse.
Also use eepe to set the fuses, not other program. Eepe will set the correct fuses. Select the option "set fuses to protect the eeprom" (I think)

When using eepe, make sure that the correct chip is selected (m128), as well as the correct programmer.
Make sure the path to "avrdude" points to eepe installation directory.
In the "extra arguments" field try -B100.
Never use the -F option. That bricks your radio.

João

Sent from my BLN-L21 using Tapatalk

[danielvc]

Hi João..

Thank you for your help.

The normal procedure to un-brick a radio is to use a 1MHz oscillator connected to the crtstal, not with HV..
You can use an arduino to generate the 1MHz pulse.

I tried doing this before removing the chip from the motherboard. Unsuccessfully.

Also use eepe to set the fuses, not other program. Eepe will set the correct fuses.

the second time that bricked it was exactly what I did. With "eXtreme Burner", I just changed the Extended Fuse to "FF" for testing only.
I only managed to communicate with the chip after a "High voltage Chip Erase".
Just changing the fuses in high voltage, still could not connect by usbasp.

Select the option "set fuses to protect the eeprom" (I think)

I used the "Reset fuses to factory default" option do you think this might be the problem?

When using eepe, make sure that the correct chip is selected (m128), as well as the correct programmer.

I think all the fields are correct.

In the "extra arguments" field try -B100.

=================================================================================
Started AVRDUDE
C:/Program Files (x86)/eePe/avrdude.exe -c usbasp -p m128 -B100 -P usb -U lfuse:r:-:i -U hfuse:r:-:i -U efuse:r:-:i
=================================================================================

avrdude.exe: set SCK frequency to 8000 Hz
avrdude.exe: warning: cannot set sck period. please check for usbasp firmware update.
avrdude.exe: error: programm enable: target doesn't answer. 1
avrdude.exe: initialization failed, rc=-1
Double check connections and try again, or use -F to override
this check.


avrdude.exe done. Thank you.


=================================================================================
AVRDUDE done - exit code 1
=================================================================================

No success too.

Never use the -F option. That bricks your radio.

Never used.



At the moment I think the problem should be the Crystal Oscillator circuit or something with pin of the controller to read the Crystal Oscillator(pin 23 and 24).

The second time the microcontroller bricked when I changed the fuses to the 9xr standard using eepe, which reading in the datasheet (page 56) changes the clock source to the Crystal Oscillator.
http://ww1.microchip.com/downloads/en/D ... oc2467.pdf

eXtreme burner have an easier way to understand the fuses for clock source.

have any way to test the cystal?

I have only one aneng 8008 multimeter...
I'm thinking of buying another Atmega128 and try again.

Any suggestion?

[jhsa]

I wouldn't use anything else but eepe.

For the eepe configurations go to "Burn" menu and then "Configure". Change the settings there.

Also, eepe is reporting this:

avrdude.exe: set SCK frequency to 8000 Hz
avrdude.exe: warning: cannot set sck period. please check for usbasp firmware update.

This warning means that your programmer cannot set the SCK period. That means the -B100 option is doing nothing as the programmer cannot slow down. It needs another firmware. Also check the resistors on the programmers data lines. Anything above 100 Ohm might not work. Many have a resistor array, not individual resistors. Please post some good pictures from your programmer, both sides. I bet that it is the cause of the problem..

João

[danielvc]

For the eepe configurations go to "Burn" menu and then "Configure". Change the settings there.

Ok.

That means the -B100 option is doing nothing as the programmer cannot slow down. It needs another firmware.

How can I flash it?

Also check the resistors on the programmers data lines.

I did not find any resistors.
measured with the multimeter MOSI, MISO, SCK and / RST and they are directly connected to usbasp atmega8A pins 15(mosi), 16(miso), 17(sck) and 14(ss/oc1b).

[jhsa]

There is a post somewhere on this forum with the firmware for the USBASP. Found it

viewtopic.php?f=95&t=7804&p=104609&hili ... lo#p104404

You flash it with another programmer, or an arduino with an ISP sketch. or any other ISP programmer.
By the way, you could also try to flash the radio with an arduino..

João

[danielvc]

You flash it with another programmer, or an arduino with an ISP sketch. or any other ISP programmer.

I will try tomorrow.

By the way, you could also try to flash the radio with an arduino..

I just tried...

=================================================================================
Started AVRDUDE
C:/Program Files (x86)/eePe/avrdude.exe -c avrisp -p m128 -b 19200 -P com9 -U eeprom:r:C:/Users/Daniel/AppData/Local/Temp/temp.hex:i
=================================================================================

avrdude.exe: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.02s

avrdude.exe: Device signature = 0x000000
avrdude.exe: Yikes! Invalid device signature.
Double check connections and try again, or use -F to override
this check.


avrdude.exe done. Thank you.


=================================================================================
AVRDUDE done - exit code 1
=================================================================================



I thought I might have some problem with wiring.
I tried connecting the same wiring in my arduino mega2560, just to test, and the programmer(Uno) was able to read device signature = 0x1e9801
So I think the wiring is OK.



=================================================================================
Started AVRDUDE
C:/Program Files (x86)/eePe/avrdude.exe -c avrisp -p m128 -b 19200 -P com9 -U eeprom:r:C:/Users/Daniel/AppData/Local/Temp/temp.hex:i
=================================================================================

avrdude.exe: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.02s

avrdude.exe: Device signature = 0x1e9801
avrdude.exe: Expected signature for ATMEGA128 is 1E 97 02
Double check chip, or use -F to override this check.

avrdude.exe done. Thank you.


=================================================================================
AVRDUDE done - exit code 1
=================================================================================

[jhsa]

Is the chip on the radio??

João

[danielvc]

Is the chip on the radio??

João

Yes

[ReSt]

0x1e9801 seams to means ATmega 2560 ????

Reinhard

[jhsa]

Yes, he tested the programmer on a m2560 to check if it was working. It looks like the m128 is refusing to respond. But with the arduino I think it went a bit further than with the USBASP.. it didn't read the signature though

One thing I don't understand is why -b 19200 instead of -B100??

João

[Kilrah]

-b is the baudrate for the serial port, nothing to do with the -B.

[jhsa]

I never used an arduino as a programmer, never needed it, so I didn't know that we have to use a baudrate setting when using an arduino as an ISP programmer?

João

[Kilrah]

The arduino emulates an avrisp, and the connection to the computer is through the arduino's serial port. Hence needing to set the baudrate appropriately.

[jhsa]

Ok understood, thanks.. but what about slowing the programming down? Could he still use the -B100 option?

João

[Kilrah]

I don't know if it supports that command, but would be worth putting it too..

[danielvc]

I don't know if it supports that command, but would be worth putting it too..

=================================================================================
Started AVRDUDE
C:/Program Files (x86)/eePe/avrdude.exe -c avrisp -p m128 -b 19200 -B100 -P com9 -U eeprom:r:C:/Users/Daniel/AppData/Local/Temp/temp.hex:i
=================================================================================

avrdude.exe: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.02s

avrdude.exe: Device signature = 0x000000
avrdude.exe: Yikes! Invalid device signature.
Double check connections and try again, or use -F to override
this check.


avrdude.exe done. Thank you.


=================================================================================
AVRDUDE done - exit code 1
=================================================================================


unfortunately it did not work

[jhsa]

Please try to slow it down even more.. Not sure if it is a bigger number, perhaps -B1000? or is it a smaller number??

João

[danielvc]

There is a post somewhere on this forum with the firmware for the USBASP. Found it

viewtopic.php?f=95&t=7804&p=104609&hili ... lo#p104404

You flash it with another programmer, or an arduino with an ISP sketch. or any other ISP programmer.
By the way, you could also try to flash the radio with an arduino..

João

I was able to upgrade my USBASP ...
but without success in communicating with the chip.

any other ideas?


=================================================================================
Started AVRDUDE
C:/Program Files (x86)/eePe/avrdude.exe -c usbasp -p m128 -B100 -P usb -U eeprom:r:C:/Users/Daniel/AppData/Local/Temp/temp.hex:i
=================================================================================

avrdude.exe: set SCK frequency to 8000 Hz
avrdude.exe: error: programm enable: target doesn't answer. 1
avrdude.exe: initialization failed, rc=-1
Double check connections and try again, or use -F to override
this check.


avrdude.exe done. Thank you.


=================================================================================
AVRDUDE done - exit code 1
=================================================================================

[danielvc]

Please try to slow it down even more.. Not sure if it is a bigger number, perhaps -B1000? or is it a smaller number??

João

-B1000
=================================================================================
Started AVRDUDE
C:/Program Files (x86)/eePe/avrdude.exe -c usbasp -p m128 -B1000 -P usb -U eeprom:r:C:/Users/Daniel/AppData/Local/Temp/temp.hex:i
=================================================================================

avrdude.exe: set SCK frequency to 1000 Hz
avrdude.exe: error: programm enable: target doesn't answer. 1
avrdude.exe: initialization failed, rc=-1
Double check connections and try again, or use -F to override
this check.


avrdude.exe done. Thank you.


=================================================================================
AVRDUDE done - exit code 1
=================================================================================




-B50
=================================================================================
Started AVRDUDE
C:/Program Files (x86)/eePe/avrdude.exe -c usbasp -p m128 -B50 -P usb -U eeprom:r:C:/Users/Daniel/AppData/Local/Temp/temp.hex:i
=================================================================================

avrdude.exe: set SCK frequency to 16000 Hz
avrdude.exe: error: programm enable: target doesn't answer. 1
avrdude.exe: initialization failed, rc=-1
Double check connections and try again, or use -F to override
this check.


avrdude.exe done. Thank you.


=================================================================================
AVRDUDE done - exit code 1
=================================================================================


-B200
=================================================================================
Started AVRDUDE
C:/Program Files (x86)/eePe/avrdude.exe -c usbasp -p m128 -B200 -P usb -U eeprom:r:C:/Users/Daniel/AppData/Local/Temp/temp.hex:i
=================================================================================

avrdude.exe: set SCK frequency to 4000 Hz
avrdude.exe: error: programm enable: target doesn't answer. 1
avrdude.exe: initialization failed, rc=-1
Double check connections and try again, or use -F to override
this check.


avrdude.exe done. Thank you.


=================================================================================
AVRDUDE done - exit code 1
=================================================================================

[jhsa]

That chip is refusing to talk to the programmer. You don't have many options.
I can think of two at the moment.
Check your connections again
Use a 1MHz oscillator connected to the crystal pins on the processor. An arduino running a sketch to generate a 1MHz signal will do.
Then try slowing the programmer down while you try to talk to the chip. If it responds, change the fuses using eepe. You can use "Set the fuses to protect the eeprom", this prevents the chip's eeprom from being erased when you flash the fw, and you won't lose your settings and models.
After you set the fuses, the radio should be able to be flashed without the oscillator. I would still keep the programming slow the first couple times..
If this fails, I have no more ideas, perhaps the chip is dead then..

João

Sent from my BLN-L21 using Tapatalk

[MikeB]

Check the connections to the board. I can't see where the black wire is connected, but I believe it should be connected to the pad beside the text "C16". I think it may currently be connected to ANALOG ground. This has an inductor in the connection to digital ground that would show as short on a meter but would block the high speed programming signals.

Mike

[danielvc]

Finally some good news.

The problem was actually with the Crystal circuit.
I was suspicious of Crystal since when I used the "Reset fuses to factory default" option in eePe and the chip became incommunicable.
From what I understood from the datasheet of the microcontroller, among other things, the change of the High / Low Bites changed from Internal RC Oscillator to the External Crystal.

The problem was in the path(red line in the picture) that connected one of the capacitors to the crystal.

I do not know how it happened ... maybe when I removed the chip... or when I tried to connect to 1MHz oscillator, before removing the chip from the motherboard.

I fixed the connection and now I can communicate with the chip again.

Finally!!!

=================================================================================
Started AVRDUDE
C:/Program Files (x86)/eePe/avrdude.exe -c usbasp -p m128 -P usb -U lfuse:r:-:i -U hfuse:r:-:i -U efuse:r:-:i
=================================================================================

avrdude.exe: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude.exe: Device signature = 0x1e9702
avrdude.exe: reading lfuse memory:

Reading | ################################################## | 100% 0.00s

avrdude.exe: writing output file "<stdout>"
avrdude.exe: reading hfuse memory:

Reading | ################################################## | 100% 0.00s

avrdude.exe: writing output file "<stdout>"
avrdude.exe: reading efuse memory:

Reading | ################################################## | 100% 0.00s

avrdude.exe: writing output file "<stdout>"

avrdude.exe done. Thank you.


=================================================================================
AVRDUDE done - SUCCESSFUL
=================================================================================
=================================================================================
FUSES: Low=0e High=89 Ext=ff
=================================================================================

I was able to flash the chip.

but now the following message appears.
"ALERT Bad EEprom Data press any Key"

But no button works.
I'll start looking for a solution to the problem.

Any suggestion?

[MikeB]

The "Alert" waits for all buttons to be released before continuing. My guess is one of the buttons is being detected as always pressed.
The 6 buttons connect to pins 11 through 16 of the processor. Check none of these are shorted to ground. Particularly note that pin 11 is the SCK programming signal, so has a wire connecting to it.

Mike

[jhsa]

Hey, some progress here

João

[danielvc]

Hi Mike.

Thanks for your help.

Check none of these are shorted to ground.

I just checked... they are not shorted to ground...

I tried to follow this answer from erazz, from the following post:
viewtopic.php?t=465

Hi Earl,

To download the latest version you need to right click and choose "save link as".

Please follow these instructions and tell us exactly what you see on the screen during and after each step.
1) Flash the latest FW.
2) With the programmer still attached. Create a new file in eePe and write that to memory (Burn->Write Model Memory).
3) Watch the screen and tell us exactly what you see. Do you see a spash screen? Does it go directly into a menu? Give it a minute or so just to make sure nothing exciting happens.
4) After waiting a bit, try pressing and holding down the left button. Does something happen? If not, try pressing and holding (1-2 seconds) the right button. Does something happen?

Now I'm stuck on the splash screen.

I'm not sure if this was a breakthrough or a setback.

[danielvc]

Hey, some progress here

João

slowly, but progressing ...

[jhsa]

Please check the fuses. Eepe has an option in the "Burn" menu to read them only.

João

Sent from my BLN-L21 using Tapatalk

[MikeB]

OK, still the same problem, one of the startup checks is waiting for a button to be released.
I note you have flashed er9x.hex. This is the version for '64 processor. You could flash er9x-128.hex. If you flash this (you will need to flash the EEPROM again as the '128 has more EEPROM available), then you have a "quick model select" feature that loads one of the model slots from 1 to 6 depending on which of the buttons is pressed at power on.

MIke

[danielvc]

Please check the fuses. Eepe has an option in the "Burn" menu to read them only.

João

Sent from my BLN-L21 using Tapatalk

=================================================================================
Started AVRDUDE
C:/Program Files (x86)/eePe/avrdude.exe -c usbasp -p m128 -P usb -U lfuse:r:-:i -U hfuse:r:-:i -U efuse:r:-:i
=================================================================================

avrdude.exe: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude.exe: Device signature = 0x1e9702
avrdude.exe: reading lfuse memory:

Reading | ################################################## | 100% 0.00s

avrdude.exe: writing output file "<stdout>"
avrdude.exe: reading hfuse memory:

Reading | ################################################## | 100% 0.00s

avrdude.exe: writing output file "<stdout>"
avrdude.exe: reading efuse memory:

Reading | ################################################## | 100% 0.00s

avrdude.exe: writing output file "<stdout>"

avrdude.exe done. Thank you.


=================================================================================
AVRDUDE done - SUCCESSFUL
=================================================================================
=================================================================================
FUSES: Low=0e High=89 Ext=ff
=================================================================================