takilara wrote:A couple of question comes to mind:
- After powering up the Rx in "programming mode" by linking signal on ch 7 and 8, should this link be removed, or should it stay there untill after you power back down?
I found you could remove the link and the Rx would stay in program mode. You can also leave the link in place. remove the link and power cycle the Rx and it then runs the new firmware.
takilara wrote:- Will the Rx give any indication regarding the flashing progress? (i.e. flashing in progress, flashing complete?)
No LEDs, but the Rx does send out an ID on the UART output so on my USB adapter this caused a LED to flash briefly when the USB adapter received the serial data that makes up the ID.
takilara wrote:- Will the upgrade software give indication regarding the flashing progress? (i can see the progress bar, i just don't trust it to move
)
Yes, it works just like programming the Tx module. The PC upgrade software waits for a ID from the Rx or Tx before it uploads the ROM image.
takilara wrote:- How can I (if i can) use the schematics from the protocol document together with the USB cable from FrSky to make a cable to flash the Rx with?
If you use a 3.3V I/O USB<>UART cnverter then no inverter is needed, the FrSky instructions are misleading here!
WARNING: Be aware that some USB<>UART adapters use 5V signal levels and this will blow up the rather senstive microcontroller inside the Rx!!!!!!!Yes, that one looks good and is cheap.
Check it outputs 3.3V levels though because the programming inputs on the receiver have
NO protection, hence the Receiver microcontroller can be zapped into oblivion...
Lastly do use a connector with insulated pins such as the JR style servo conector I used as this will help stop inadvertant shorts and reduce the chances that static will zap the microcontroller inputs.
ATB,
Bodmer