Bad Eeprom error. 9xtreme/encoder.
Re: Bad Eeprom error. 9xtreme/encoder.
Message edited, experimenting...
https://radindustries.wordpress.com/
Re: Bad Eeprom error. 9xtreme/encoder.
I have some news here. I flashed the latest software you sent me in private message, and I have been switching On and Off the radio for a while. I lost the count of times I did it and it worked until I said; "Last time and I call it a day" then it failed and got the usual error.
Then I restored the Eeprom, unplugged the arduino module following your instructions and I spent like 10 minutes switching on and off and it seems the radio does not fail anymore. So yep, maybe the issue is comming from the module itself...
Then I restored the Eeprom, unplugged the arduino module following your instructions and I spent like 10 minutes switching on and off and it seems the radio does not fail anymore. So yep, maybe the issue is comming from the module itself...
https://radindustries.wordpress.com/
- MikeB
- 9x Developer
- Posts: 17993
- Joined: Tue Dec 27, 2011 1:24 pm
- Country: -
- Location: Poole, Dorset, UK
Re: Bad Eeprom error. 9xtreme/encoder.
Two possibilities come to mind:
1. The MISO signal is being driven at the wrong time, causing data corruption. (Not so likely as it should be an input while the EEPROM is selected, controlled by hardware).
2. The SCK (clock) signal is being loaded by the Arduino causing missed clocks. This is the more likely as I see there is a green LED on the Arduino connected to this signal.
Possibly disconnecting the LED on the Arduino would solve the problem. On the Arduinos I have, there is a resistor in series with the LED (marked 102, so 1K). The LED is beside IO9, with the resistor beside that. A circuit I have suggests the resistor should be 330 ohms (would be marked 331). Removing this resistor would be a useful test. Before doing that, just disconnecting the wire to IO13 (the SCK signal) and plugging the module in is worth a test to check the other signals are not causing the problem.
Mike
1. The MISO signal is being driven at the wrong time, causing data corruption. (Not so likely as it should be an input while the EEPROM is selected, controlled by hardware).
2. The SCK (clock) signal is being loaded by the Arduino causing missed clocks. This is the more likely as I see there is a green LED on the Arduino connected to this signal.
Possibly disconnecting the LED on the Arduino would solve the problem. On the Arduinos I have, there is a resistor in series with the LED (marked 102, so 1K). The LED is beside IO9, with the resistor beside that. A circuit I have suggests the resistor should be 330 ohms (would be marked 331). Removing this resistor would be a useful test. Before doing that, just disconnecting the wire to IO13 (the SCK signal) and plugging the module in is worth a test to check the other signals are not causing the problem.
Mike
erskyTx/er9x developer
The difficult we do immediately,
The impossible takes a little longer!
The difficult we do immediately,
The impossible takes a little longer!
Re: Bad Eeprom error. 9xtreme/encoder.
So, if I understood correctly:
I should flash the ersky from march 16th version and discard the two versions you sent me in private message,
And remove the resistor I marked in red here: But before doing that, disconnect IO13, which is the red wire right side down. Right?
If yes, I will do it tonight.
I should flash the ersky from march 16th version and discard the two versions you sent me in private message,
And remove the resistor I marked in red here: But before doing that, disconnect IO13, which is the red wire right side down. Right?
If yes, I will do it tonight.
https://radindustries.wordpress.com/
- MikeB
- 9x Developer
- Posts: 17993
- Joined: Tue Dec 27, 2011 1:24 pm
- Country: -
- Location: Poole, Dorset, UK
Re: Bad Eeprom error. 9xtreme/encoder.
Yes.
Test 1. Disconnect the IO13 wire, use the currently installed firmware and check if EEPROM works OK.
Test 2. Remove the resistor (you circled in red), re-connect the IO13 wire, and check if EEPROM works OK.
Test 3. Revert to the March 16th firmware and check if EEPROM and encoder both work OK.
Mike
Test 1. Disconnect the IO13 wire, use the currently installed firmware and check if EEPROM works OK.
Test 2. Remove the resistor (you circled in red), re-connect the IO13 wire, and check if EEPROM works OK.
Test 3. Revert to the March 16th firmware and check if EEPROM and encoder both work OK.
Mike
erskyTx/er9x developer
The difficult we do immediately,
The impossible takes a little longer!
The difficult we do immediately,
The impossible takes a little longer!
Re: Bad Eeprom error. 9xtreme/encoder.
Hello,
I am in the phase 3 now. Resistor has been removed, firmware flashed and I switched it on and off about 60 times. So far it seems to work now! I will update if it fails. Hope to not to have to update this thread, lol.
I am in the phase 3 now. Resistor has been removed, firmware flashed and I switched it on and off about 60 times. So far it seems to work now! I will update if it fails. Hope to not to have to update this thread, lol.
https://radindustries.wordpress.com/
Re: Bad Eeprom error. 9xtreme/encoder.
Try saying again that "it is the last time"
Last time it failed when you said it
João
Last time it failed when you said it
João
My er9x/Ersky9x/eepskye Video Tutorials
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW
https://www.youtube.com/playlist?list=PL5uJhoD7sAKidZmkhMpYpp_qcuIqJXhb9
Donate to Er9x/Ersky9x:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=YHX43JR3J7XGW