openrcforums

Well I wasn't as good at soldering as I remembered so my replacement with a real chip was a fail. I ordered a new motherboard from hobbyking and they sent me a motherboard with a clone chip! Can't win

Are the same firmwares compatible?

...There's no Atmel markings at all, and it's a Green ED040502-H16D Quite a few different processors out there... Last summer I got a spare motherboard from HK for the 9X that is marked with ATMEGA128A-AU Green ED040502-H16D 1104 110404 but with ATMEL-Logo on it. Klaus Agreed. Here is mine. tapatal...

I ordered a real atmega128 so I can send you my clone chip if you want to run some more thorough tests.

I did flash the 128 version. The errors I was getting were: avrdude saying that it failed even though it was still running (successfully) in the background. Another error after 100% saying that the write failed even though it was successful. Some other error during a read that I can't remember but i...

I believe companion may keep the configuration values in a 'profile', and may be using default values from that when you read the EEPROM from the radio. It may also be there is a problem writing to the EEPROM from the computer. Mike. Using eepe worked even though it kept giving all kinds of random ...

MikeB wrote:Was that with er9x/eepe or openTx/companion?

Mike.

OpenTx Companion. I haven't had a chance to try it with eepe. I'll try it after work.

MikeB wrote:As João says, once you have done the stick calibration, always read the EEPROM into eepe/companion, do any changes you need to do, then write the EEPROM back. This preserves all settings you have already done.

Mike.

I tried it that way to and same result.

On the 9x you will have to calibrate the sticks every time you flash the firmware, or change the fuses to protect the eeprom. Another option is to download the eeprom onto eepe/companion, depending on which fw you're using, Flash the firmware, and then burn the eeprom to the radio again. That will ...

If you flash er9x, then you need to use eepe on the computer, not Companion, to read and write the EEPROM. When you first ran er9x, did you get "EEPROM Error", and then have the EEPROM format? The LCD may be blank because the contrast setting is incorrect, which could easily be caused by ...

The <64K er9x firmware flashed fine. When I made a model in OpenCompanion and saved to EEPROM, I got that warning about the EEPROM being 4096 but it is only going to use the first 2048. When it rebooted after that, it beeped really weird and the LCD was blank. Nothing I did could bring it back so I ...

Ok I'll try that. Any particular functions to try? I'm not sure what issues people were having

I would think you can replace the stock firmware and EEPROM OK, so probably worth flashing something. Perhaps try standard er9x first as this is less than 64K, you can find it here: http://www.er9x.com/ . Mike. Yeah, just wanted to know if anyone wanted me to do something to figure out the issue wi...

Does anyone have any ideas on what to try next? Should I flash it with something or keep it "stock" for more forensics?

Well, this is the command I'm running to get the firmware: avrdude.exe -c usbtiny -p m128 -P usb -U flash:r:firmware-filename.hex:r and for the eeprom: avrdude.exe -c usbtiny -p m128 -P usb -U eeprom:r:eeprom-filename.hex:i If anyone has any ideas on what else to try, let me know. The error I get fr...

The EEPROM has read as 4K, the last 2K contains all 0xFF. What are you using to read the flash (programmer and software)? I believe some versions of AvrDude don't read/write more than 64K properly. Mike. For software, I'm using OpenTX companion which is using avrdude ver 5.11-Patch#7610. Is there a...

Based on the firmware being exactly the same as your 2012 version and that it works in ReSt's 9X, is it safe to say that we have the original firmware and can ignore the warning from OpenTX about not being able to "restore them to factory condition"? I'd like to attempt flashing it with op...

Could you please read the signature from the device. A quick look at the hex file shows two blocks of 64K that are the same as each other, as though it is a 64K chip, and you have read 128K, so the 64K has been read twice. It would also be a good idea to read the EEPROM (where the models are stored...

Here it is. I modified a few "models" but the last ones are untouched.

I ordered one from mouser. Email me back if you want me to send you the clone chip. I downloaded the firmware that is currently on there. Do you want me to post it on here somewhere? I'm sure some people might want to get their original back in case they didn't do a backup.

The original chip was Atmega64A-AU. At some point last year they started mixing in Atmega128A-AU - probably going with whatever was available since they weren't utilizing the extra benefits the 128 offers. I'm sure I have extras of both chips in my office, but I've not been able to find them (what ...

I'd also like to compare the stock cloned firmware with the stock atmel firmware. It's likely that it's the same and there are other flaws in the chip that cause the issues. Btw, does anyone know the exact issues? I'd like to see if they are present with the stock firmware. Sent from my Nexus 5 usin...

As far as my plan, I have a programmer soldered in already and according to opentx's website, there is no firmware for restoring the cloned chip. I'd like to get a copy of the firmware to the appropriate people and then I'd like to run tests with the guidance of people who know more about the issue....

I got one from hobbyking with the clone (Green ED040501-H16D). I'm willing to run tests on it. Just let me know what you want me to do. I'm an electrical engineer and I can also solder stuff this small. If someone wants, they can send me a real chip (or show me where I can buy one) so I can do some ...