7e repeatedly reboots after power up.

I performed a number of mods to my 7e. I did the diode mode to increase range, and installed the nrf24l01 and a7105 modules. Got it all soldered together and tucked away in tx. It powered up fine so I proceeded to alter the code as directed to enable the new hardware. Once again process seemed to go smoothly. Feeling confident I loaded couple of model files to test tx. After choosing model (v202) the tx rebooted. I switched the power off and back on again and the tx continually reboots unless the ext or ent buttons are pushed then it will go into the usb or other programing mode.

I was hoping someone might have seen this before. Since I did so many mods at once troubleshooting will be more difficult. Is it possible to switch models from pc to check if it is causing problem? Any insight will be appreciated.

Pagres wrote: I performed a number of mods to my 7e. I did the diode mode to increase range, and installed the nrf24l01 and a7105 modules. Got it all soldered together and tucked away in tx. It powered up fine so I proceeded to alter the code as directed to enable the new hardware. Once again process seemed to go smoothly. Feeling confident I loaded couple of model files to test tx. After choosing model (v202) the tx rebooted. I switched the power off and back on again and the tx continually reboots unless the ext or ent buttons are pushed then it will go into the usb or other programing mode.

I was hoping someone might have seen this before. Since I did so many mods at once troubleshooting will be more difficult. Is it possible to switch models from pc to check if it is causing problem? Any insight will be appreciated.

Check again your soldering job. Maybe 2 wires are shortcut somewhere ...

Yeah that's what I'd expect also. I was just hoping that the rebooting was symptomatic of particular wires being crossed. Or a common mistake enabling modules in the code.

Sounds similar to the issue I had when installing a non-PA A7105 module that was pulled from an X1 stock tx. Do not connect the MISO pin from the module. It's unused for A7105 modules, but defaults to an output from the A7105 and will prevent MISO from working for other modules.

Removing that connection fixed the problem.

Agree this is not safe. These protocols set up the nRF in auto-acknowledge mode, and either the data sent or retry timeout bit needs to be set before sending the next packet. The symax protocol can sit in this loop up to 12mS during bind. Probably better to return from the callback without waiting and come back to the same point in the flow until one of the bits is set. Not sure how difficult that will be in the binding process. Not difficult once bound. Will take a look.

For the soldering/mis-wiring type issues I've been noodling a proposal for some type of hardware check. My first thought was to return an error indication from protocol init/bind if nonsensical values are read from the chip. But that would need to be put in every protocol.

Maybe better would be a HWCheck function in the common/protocol files, and a new start-up function that checks each installed module at power-on, shortly before ProtocolInit. The check function could be as simple as reading a register that should not be 00 or FF (which would have caught the mis-wiring I've done). I tried this for the nRF chip and the only problem was the error screen I displayed was overwritten by the binding message when ProcotolInit was called. Not sure what the best behavior would be if a module error is detected.

Perhaps the HWCheck could later be extended to actually test the device. Or even enumerate the installed devices automatically...

Hexfet I think you may have my solution. I know I hooked up the miso on syma x1 module. Did I read correctly that syma x1 module does not have a PA? So that means the PA should be set to zero for the a7105 in the code when using syma x1 module?

The Syma X1 module does not have PA. You can set it to zero or just leave it commented out. Either way you'll still need to remove the MISO connection.

Problem solved. I opened up tx to cut miso connection and noticed the gnd connection had come loose. So I repaired gnd and snipped miso on syma module. When put back together tx not only stopped rebooting but was able to bind to v202 fc. I have yet to shut off pa setting for the a7105 module but will do so before I attempt to use it. Thanks to all for your help!

Anyway, I'll check V202, HiSky, and SLT for potentially infinite loops because of hardware problems. There should be at least a reasonably short retry count after which we can detect hardware failure instead of going to watchdog.

I reworked the YD717 code to remove the tight loop. Instead it reschedules the callback in 500uS and keeps checking for packet send complete before sending the next packet. Updated the pull request.