openrcforums

Posted: **Thu Nov 26, 2015 11:23 am**

Hi everyone,

it seems like I bricked my Turnigy 9x.

A while ago I did the telemetry mod and it seems like I screwed up. At one point during the mod I did a mistake when cutting the trace on the backplate which led to a burned trace on the third pin. I replaced that trace and redid the correct cutting and though everything would be fine.

Since then I tried to reflash my Turnigy 9x with my USBASP and with my Arduino, but I always get the following error at the end:

Code: Select all

avrdude: verifying ...
avrdude: verification error, first mismatch at byte 0x0100
         0xff != 0x3a
avrdude: verification error; content mismatch

Now I know that there's a certain bug with avrdude on the mac, but this is not it. I tried with Linux and Windows -> same behaviour.

What scares me off now is the fact that while flashing my remote doesn't power up like it used to be.
Normally when I attached my 10 pin cable and the 5V came through, my remote powered up. This isn't the case anymore.

When attaching the battery to the remote, the remote powers up but the screen stays blank.

I don't see anything else burned or faulty on my remote that could cause this!

Any help is highly appreciated!

Thanks

Posted: **Thu Nov 26, 2015 11:41 am**

hmm, I don't see how cutting a track would damage something, Unless you had the radio ON when you did it?

Please post some pictures of what you did. We need to know exactly what you did.

What firmware are you trying to flash?
try typing -B 100 in the extra arguments field
João

Posted: **Thu Nov 26, 2015 12:09 pm**

Okay let's see.

The problem is that I was trying to get the telemetry mod working where you attach the two 220 Ohm resistors on to the ATMega64 chip (and remove the two smd resistors instead) and you connect RX and TX to the back plate so the telemetry data from the module will be displayed.

After doing this and not properly cutting the traces on the back plate I had a little short circuit which burned a trace on the back plate (see picture attached).

I fixed all that (cutted the trace properly, redid the connection that burned down) and was able to reflash the Turnigy 9x back then. I got an error message about two of the back switched though, I think it was ID2 and AIL, that they were on even though they weren't. (I figured that's part of the Telemetry mod, but if not, I might have screwed up(if so, tell me).

The -B 100 option doesn't fix my problem unfortunately. I tried that before with different values in the -B range to no success...

Thanks

Posted: **Thu Nov 26, 2015 12:30 pm**

The track that burnt seems to be the switched Battery voltage that powers the RF module. Are you sure you didn't solder the wire to the wrong pin? or maybe there was a short between those pins? the track that burnt has nothing to do with the telemetry mod as far as I know. It looks like that you somehow shorted the battery voltage to something else. Please post also a picture of your mainboard, we would like to see what you have done there..
If you connected the telemetry wires to battery voltage you could have fried the processor. But it is too early to conclude that..

Try to read the firmware or the eeprom to a file instead of trying to flash. See if it works. You still didn't say which firmware are you trying to program.

João

Posted: **Thu Nov 26, 2015 12:40 pm**

Did you cut the tracks on the pins the blue and yellow wires connect to? On BOTH sides of the board for the yellow wire.
The telemetry signals on those wires are also signals used while programming. You might try removing the blue and yellow wires and checking if you can read/flash the processor then.

Mike.

Posted: **Thu Nov 26, 2015 1:07 pm**

Attached are two pictures of the current state of the PCB's.

Here's some more info:

I'm trying to flash the latest ER9X from the "next" branch as I'm using the multimodule from RCGroups.

I'm also able to read and then verify the flash memory on the RC.

What most likely happened is that the yellow cable touched the pin underneath which ended up in the short circuit I mentioned...

Let me know if these pictures work, otherwise I'll make some more.

Posted: **Thu Nov 26, 2015 1:12 pm**

I can't see any pictures

If the yellow wire touched the pin underneath on the backplate, then it had battery voltage on it and straight into the processor.. What battery are you using?

João

Posted: **Thu Nov 26, 2015 1:13 pm**

please post the version of avrdude using 'avrdude -v' from the command line

Posted: **Thu Nov 26, 2015 1:19 pm**

Code: Select all

avrdude -v

avrdude: Version 6.1, compiled on Oct 15 2015 at 01:54:34
         Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
         Copyright (c) 2007-2014 Joerg Wunsch

Posted: **Thu Nov 26, 2015 1:22 pm**

jhsa wrote:I can't see any pictures

If the yellow wire touched the pin underneath on the backplate, then it had battery voltage on it and straight into the processor.. What battery are you using?

João

I've updated the pictures, my bad.

I'm using a 3Cell 11.1V battery.

Wouldn't that mean that the processor would be gone completely? Because like I said, it's been working before I tried to flash it and right after that stuff happened.

Posted: **Thu Nov 26, 2015 1:23 pm**

Evils wrote:

Code: Select all

avrdude -v

avrdude: Version 6.1, compiled on Oct 15 2015 at 01:54:34
         Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
         Copyright (c) 2007-2014 Joerg Wunsch

It appears you have hardware issues as well ( burned up a trace myself at one time ), but this could very well be the cause of your mismatch at 0x0100

viewtopic.php?f=94&t=5036&p=105621#p105621

Posted: **Thu Nov 26, 2015 1:35 pm**

Try what Mike suggested, disconnect the wires from the backplate and try flashing the radio..

João

Posted: **Thu Nov 26, 2015 1:38 pm**

It worked!!!

I just updated through homebrew to the latest HEAD version and it worked perfectly. The remote works again (I assume). I got a "BAD EEPROM" alarm at first.

Now before we end this, I have a few questions regarding this:

1.) normally the remote powered up when I attached the programmer, why isn't that the case anymore?!
2.) I still get the error message that THR, ID2 and AIL are on, no matter what their state is. Is that normal?! I assumed that's due to the Telemetry mod!

Thanks a lot guys for the help here

avrdude: Version 6.2-20151117, compiled on Nov 26 2015 at 14:30:47
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2014 Joerg Wunsch

System wide configuration file is "/usr/local/Cellar/avrdude/HEAD/etc/avrdude.conf"
User configuration file is "/Users/evils/.avrduderc"
User configuration file does not exist or is not a regular file, skipping

Using Port : usb
Using Programmer : usbasp
Overriding Baud Rate : 19200
avrdude: seen device from vendor ->www.fischl.de<-
avrdude: seen product ->USBasp<-
AVR Part : ATmega64
Chip Erase delay : 9000 us
PAGEL : PD7
BS2 : PA0
RESET disposition : dedicated
RETRY pulse : SCK
serial program mode : yes
parallel program mode : yes
Timeout : 200
StabDelay : 100
CmdexeDelay : 25
SyncLoops : 32
ByteDelay : 0
PollIndex : 3
PollValue : 0x53
Memory Detail :

Block Poll Page Polled
Memory Type Mode Delay Size Indx Paged Size Size #Pages MinW MaxW ReadBack
----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
eeprom 4 20 64 0 no 2048 8 0 9000 9000 0xff 0xff
flash 33 6 128 0 yes 65536 256 256 4500 4500 0xff 0xff
lfuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00
hfuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00
efuse 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00
lock 0 0 0 0 no 1 0 0 9000 9000 0x00 0x00
calibration 0 0 0 0 no 4 0 0 0 0 0x00 0x00
signature 0 0 0 0 no 3 0 0 0 0 0x00 0x00

Programmer Type : usbasp
Description : USBasp, http://www.fischl.de/usbasp/

avrdude: auto set sck period (because given equals null)
avrdude: AVR device initialized and ready to accept instructions

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

avrdude: Device signature = 0x1e9602 (probably m64)
avrdude: safemode: hfuse reads as 89
avrdude: safemode: efuse reads as FF
avrdude: NOTE: "flash" memory has been specified, an erase cycle will be performed
To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: auto set sck period (because given equals null)
avrdude: reading input file "er9x.hex"
avrdude: input file er9x.hex auto detected as Intel Hex
avrdude: writing flash (61358 bytes):

Writing | ################################################## | 100% 24.80s

avrdude: 61358 bytes of flash written
avrdude: verifying flash memory against er9x.hex:
avrdude: load data flash data from input file er9x.hex:
avrdude: input file er9x.hex auto detected as Intel Hex
avrdude: input file er9x.hex contains 61358 bytes
avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 15.91s

avrdude: verifying ...
avrdude: 61358 bytes of flash verified

avrdude: safemode: hfuse reads as 89
avrdude: safemode: efuse reads as FF
avrdude: safemode: Fuses OK (E:FF, H:89, L:0E)

avrdude done. Thank you.

Posted: **Thu Nov 26, 2015 1:43 pm**

Evils wrote: I just updated through homebrew to the latest HEAD version and it worked perfectly.
--snip--
2.) I still get the error message that THR, ID2 and AIL are on, no matter what their state is. Is that normal?! I assumed that's due to the Telemetry mod!

Great. I'll leave the hardware issue to the experts on that .

It's Thanksgiving here today so Happy Thanksgiving !

Posted: **Thu Nov 26, 2015 1:49 pm**

Evils wrote:It worked!!!

I just updated through homebrew to the latest HEAD version and it worked perfectly. The remote works again (I assume). I got a "BAD EEPROM" alarm at first.

You are a very very lucky man..

2.) I still get the error message that THR, ID2 and AIL are on, no matter what their state is. Is that normal?! I assumed that's due to the Telemetry mod!

You would have to flash the telemetry version of er9x Otherwise AIL and THR won't be recognized as they are now on different pins of the processor.
That doesn't explain your ID2 switch problem though.. It needs investigating. Go to Radio Setup/DiagSwtch, and move your switches. when they are off the number in front will be "0". when they are ON, the number will be "1".
What do AIL, THR and ID1 and ID2 show when you move them?

João

Posted: **Thu Nov 26, 2015 1:58 pm**

jhsa wrote:
Evils wrote:It worked!!!

I just updated through homebrew to the latest HEAD version and it worked perfectly. The remote works again (I assume). I got a "BAD EEPROM" alarm at first.
You are a very very lucky man..

2.) I still get the error message that THR, ID2 and AIL are on, no matter what their state is. Is that normal?! I assumed that's due to the Telemetry mod!
You would have to flash the telemetry version of er9x Otherwise AIL and THR won't be recognized as they are now on different pins of the processor.
That doesn't explain your ID2 switch problem though.. It needs investigating. Go to Radio Setup/DiagSwtch, and move your switches. when they are off the number in front will be "0". when they are ON, the number will be "1".
What do AIL, THR and ID1 and ID2 show when you move them?

João

AIL and THR don't move at all when watching the values in the DiagSwtch menu.

I compiled my version of ER9x with "make EXT=FRSKY-NOHT" (NOHT cause otherwise it claimed to use 101.xx% of my memory. That should be the right version or not?!

Posted: **Thu Nov 26, 2015 2:04 pm**

Go to www.er9x.com, download the file "er9x for M64-FrSky (right click and select 'save as')" and flash it.

João

Posted: **Thu Nov 26, 2015 2:05 pm**

Use:
make EXT=FRSKY TEMPLATES=NO
or, go here: viewtopic.php?f=5&t=4598#p64969, and download "er9x-r819Prov.zip", extract er9x-frsky.hex and flash that.

Mike.

Posted: **Thu Nov 26, 2015 2:43 pm**

So, after flashing the version from er9x.com, AIL works, but THR still doesn't.

Is that supposed to be the case?

Edit: On another note, I still don't get why I don't have any power during flashing as I was used to be.

Posted: **Thu Nov 26, 2015 2:56 pm**

No, both should work. The THR switch is on the red wire. Check at the processor pin there isn't a solder short to the pin to the other side of the black wire.

Mike.

Posted: **Thu Nov 26, 2015 3:26 pm**

Apparently it wasn't the pins that connected but the lower connections...

Everything seems to work now! Thanks guys

With this whole soldering, I learned a hell lot, but I feel like it's with a house "You build the first one for your enemy and the second for yourself."

Btw. I intend to put hot glue over the PINs where I soldered as they feel weak, any reason I should not do that?

Posted: **Thu Nov 26, 2015 5:30 pm**

No problem, and a good idea. I use fine, single strand wire (kynar wire) for connecting to processor pins. It is easier to solder, no chance of stray strands, and puts much less strain on the soldered joint.

Mike.

openrcforums

No power during flashing and "Verification failed"

No power during flashing and "Verification failed"

Re: No power during flashing and "Verification failed"

Re: No power during flashing and "Verification failed"

Re: No power during flashing and "Verification failed"

Re: No power during flashing and "Verification failed"

Re: No power during flashing and "Verification failed"

Re: No power during flashing and "Verification failed"

Re: No power during flashing and "Verification failed"

Re: No power during flashing and "Verification failed"

Re: No power during flashing and "Verification failed"

Re: No power during flashing and "Verification failed"

Re: No power during flashing and "Verification failed"

Re: No power during flashing and "Verification failed"

Re: No power during flashing and "Verification failed"

Re: No power during flashing and "Verification failed"

Re: No power during flashing and "Verification failed"

Re: No power during flashing and "Verification failed"

Re: No power during flashing and "Verification failed"

Re: No power during flashing and "Verification failed"

Re: No power during flashing and "Verification failed"

Re: No power during flashing and "Verification failed"

Re: No power during flashing and "Verification failed"