Issue 115

[GoogleCodeExporter]

why issue 115 was deleted uncommented ?
Issue still exist

Original issue reported on code.google.com by angoliman@ewetel.net on 3 Jan 2013 at 12:07

• Merged into: #115

[GoogleCodeExporter]

I merge the 2 issues.
It's strange I used this tool on all my M64 / M128 boards and it worked!

Original comment by bson...@gmail.com on 3 Jan 2013 at 1:40

• Changed state: Duplicate

[GoogleCodeExporter]

Am 03.01.2013 14:40, schrieb companion9x@googlecode.com:

Thanks for undelete issue 115

Yes, I used it also very often without any trouble. I flashed a lot of 
radios, but I found this issue appears with newer radios very often and 
most with Turnigy brand.
First time it makes me a lot of headache what�s going on and this is how 
it appears :

I flashed the radios with C9x same time with setting low Fuse to EEPROM 
protect. All seems to be nice and normal, but if you switch the radio 
on, some times the display stays blank !! Then, if you switch off again 
and back on it comes up and works normal. So, lets say from 10 times 
switching on and off it will stay blank 3 times. Its a random issue.

So I started some investigation to this issue and it shows me that the 
newer Turnigy radios are set to low Fuse 3F as *factory default.*
All older one have 0E. So why ?

My be its simple. 3F sets processor start up time delay to 1000 CK+4ms 
and 0E sets to 258 CK+4ms. So 0E is more short in time. With 3F the 
crystal oscillation has more time to stabilize before start to execute 
the programm.
This Fuse change to 3F looks like a result coming out of device 
production variation. May be since they changed the Atmega 64 to 64A, or 
change of the crystal vendor, or what ever.

All radios with this issue I had, I set them back to low Fuse 3F with 
another programming tool and the trouble was gone.

That�s why I would say that C9x should not change low Fuse anyway.

Original comment by angoliman@ewetel.net on 3 Jan 2013 at 10:59