Page 21 of 23

Re: Orange Module running MULTI protocol

Posted: Tue Jul 17, 2018 12:20 pm
by sircrashalot
I tried the com port both ways, along with holding the bins button while booting. I have also watched the led to see what it does while booting and it does not flash either, in fact it does not even light up. I am suppoased to be using the file for the green board correct?

Re: Orange Module running MULTI protocol

Posted: Tue Jul 17, 2018 1:16 pm
by MikeB
What file did you use when you flashed the bootloader?

Mike

Re: Orange Module running MULTI protocol

Posted: Tue Jul 17, 2018 1:39 pm
by sircrashalot
MultiOrangeBoot.bin is the file I used. The firmware i used in the Tx is ersky9xProvR222b4.

Re: Orange Module running MULTI protocol

Posted: Tue Jul 17, 2018 1:59 pm
by sircrashalot
i was careful but did end up lifting the pads. Do those traces run to another component? So far it looks like they just run to the other side of the board to a pad that is not connected to anything but I don't know if there is a layer in the middle of the board.

Re: Orange Module running MULTI protocol

Posted: Tue Jul 17, 2018 2:00 pm
by sircrashalot
I am still trying to find where the two missing resistors are that I need to solder a jumper across

Re: Orange Module running MULTI protocol

Posted: Tue Jul 17, 2018 2:20 pm
by sircrashalot
I am going to bust out the soldering iron and start over and try flashing the bootloader with the pro mini instead of flashing it with the Tx.

Re: Orange Module running MULTI protocol

Posted: Tue Jul 17, 2018 2:27 pm
by MikeB
That board doesn't have/need those "missing" resistors.

I have one of those boards, but I don't think I ever put the bootloader onto it. I'll try going through the process with it, but it will be tomorrow before I have time to do so. I had the board for a different project, and that fell through, so I haven't used it since I flashed it using my AVRISP-II programmer.

When you flashed "MultiOrangeBoot.bin", please confirm you powered the board through the main, 5-way connector.

Good idea to try with the Pro Mini.

Mike

Re: Orange Module running MULTI protocol

Posted: Tue Jul 17, 2018 2:42 pm
by sircrashalot
Yes I did power the board through the 5 pin connector from the radio while I flashed it.

Re: Orange Module running MULTI protocol

Posted: Tue Jul 17, 2018 4:18 pm
by sircrashalot
And... somehow I cooked the 3.3v regulator on the module.I have another regulator floating around somewhere so I might replace it,

Re: Orange Module running MULTI protocol

Posted: Tue Jul 17, 2018 5:45 pm
by sircrashalot
After taking some measurements with my meter, the 3.3v reg and the xmega are fried. time to order another module lol

Re: Orange Module running MULTI protocol

Posted: Fri Feb 01, 2019 2:30 pm
by lucidchaos
Hi there,

Sorry in advance for the necro. Have been combing this thread and the work being done here is awesome.

I have a unique case. Would greatly like to flash my V1.2 ORX module, but I'm using it in a Jeti DS-16. No access to any FRSky or OpenTX hardware.
Any way to flash mine? I have access to a PC, Jeti internal PPM (PPM8+,ppm8-,ppm16), and Arduino Uno.

Image

Image

Re: Orange Module running MULTI protocol

Posted: Fri Feb 01, 2019 11:24 pm
by MikeB
The firmware build for the Orange module does NOT include support for PPM, only the serial protocol. I didn't implement the PPM input when I ported the code to the Orange module.
This means, currently, the module would not work with PPM from the Jeti.

Be aware also that the Orange module only supports those protocols that run on the Cypress RF chip:
DEVO
DSM
J6PRO
WFLY
WK2x01

Mike

Re: Orange Module running MULTI protocol

Posted: Sat Feb 02, 2019 1:20 am
by lucidchaos
Good looking out. Thanks!

Re: Orange Module running MULTI protocol

Posted: Tue Mar 05, 2019 4:41 am
by antlerhanger
I an running the latest fw on my 9xr pro .I used a mini and was able to get the bootloader onto the green module ,,The module is like the one on page 2 . I cut the lead and attached the pro mini to the 4 pads and the mini blinked once a second when finished loading, installed module into the pro and and tried to flash the green and blue hex files ..failed each time I tried it..I tried inverting still the same,,proto is set on mult dsm dsm222 ,,auto bind ,it is blank after the word blind ,,I think I read there should b something there

Anyway if you can help me again I would appreciate it

Allen

Re: Orange Module running MULTI protocol

Posted: Fri Sep 20, 2019 2:24 am
by peldridge
Hi there, I purchased an OrangeRX telemetry module for my 9XR Pro, the one that uses the radios internal aerial and it was DOA. It has the green PCB. I thought I may as well try and flash it with Multi Orange bin file and it appears to have flashed ok. The module now at least does something. Although it seems quite fussy, I can get it to bind to an OrangeRx DSM2 receiver (the model number appears missing). However having been bound, no servos respond and the light in the receiver stays off. I have checked and double checked the settings but cannot get it to work. I also bound it to a Storm S603 DSMX receiver with the same problem. I read that it only supports a serial data stream. Is that related to a setting?

Re: Orange Module running MULTI protocol

Posted: Fri Sep 20, 2019 9:10 am
by MikeB
If it flashed OK, then you should have the protocol on the 'PRO set to "MULTI", and then you start the bind from the protocol menu. Is that what you did?

Mike

Re: Orange Module running MULTI protocol

Posted: Sat Sep 21, 2019 5:44 am
by peldridge
No, binding from the Protocol menu doesn't work. It only works when you turn the transmitter on holding down the Bind button on the module.
As an aside I also have a OrangeRx module with its own aerial V1.2 and that binds ok but the servos will only work with the Protocol set to PPM (not DSM); this uses the standard firmware from HobbyKing.

Re: Orange Module running MULTI protocol

Posted: Sat Sep 21, 2019 6:34 am
by Kilrah
If it was DOA there's likely something wrong with the hardware that will also prevent it from working with another firmware. What was wrong with it?

Re: Orange Module running MULTI protocol

Posted: Sat Sep 21, 2019 9:20 pm
by peldridge
It was completely dead when it arrived. I had nothing to lose flashing the Multi binary. As you say, maybe the board has some fault.

Re: Orange Module running MULTI protocol

Posted: Mon Sep 23, 2019 12:10 am
by antlerhanger
So I have a orange module that uses the internal antenna and is for the 9xpro only . It never received telemetry so bangood sent me a new one. I flashed the bootloader to it and used update multi and now it binds and has telemetry ..It will also bind to my convergence which it wouldn't before Thanks so much Mike !!!

Allen

Re: Orange Module running MULTI protocol

Posted: Sat Nov 16, 2019 9:54 pm
by palkina
Just want to thank Mike for the code contribution and instructions and others who posted on this thread.

I've succeed installing the Multi-protocol firmware v1.2.1.85 on an Orange Green V1.2 module.

After flashing the boot-loader on the Orange Module via the pdimini sketch, I used a Taranis (X9D) with OpenTX 2.3.1 to flash the module using the Application from http://www.er9x.com/Ersky9xapps.html enabled by the Taranis boot-loader that comes in the ersky9xProvR222.zip file from 07-Jul-2019 20:23 posted on the first page of this thread.

I tested with two Orange receivers: And old one with DSM and the R720X (telemetry capable). I got greatly surprised to hear the "telemetry lost" announcement when I disconnected the R720X receiver.

One caveat, to change models, select first the model and power-cycle the Taranis.

Thank you again.

Re: Orange Module running MULTI protocol

Posted: Tue Nov 26, 2019 9:18 am
by DWiskow
I have an old OrangeRX (blue) Transmitter and have been reading through this thread to learn how to update to the latest/greatest firmware . . .

. . . I also have an Olimex AVR-ISP-MK2 (3.3/5V switchable - https://www.olimex.com/Products/AVR/Pro ... e-hardware) and a FT232 USB adaptor (FTDI 232rl 3.3/5V switchable - https://www.amazon.co.uk/Serial-Convert ... B075N82CDL) to load/update firmware.

By temporarily soldering 4 wires to the GND, VCC, Clock & Data pads, I was able to flash the 'April 2016 - MultiOrange bootloader' to the board, but could not then get it to update/flash from my FrSky Taranis X9D (OpenTX 2.3.1 with Mike's bootloader/app installed on the X9D). I also struggled a little with the flashing in that, with the AVR-ISP-MK2 set to 3.3v and Target ON, it wouldn't power the board (and I didn't want to set the AVR to 5v !).

I solved this by powering the board from a 4 x 1.2v NiMh battery pack to the +BATT & GND of the 5 pin socket on the board (and then only connecting GND, Clock & Data pads to the AVR) and with the AVR set to 3.3v and Target OFF I then managed to flash the board . . . this didn't actually work until I linked the battery pack and AVR with a common GND.

SUCCESS - the green LED flashed at about 1 second intervals when the board was powered . . . I then added the wire for telemetry output, fitted the board back into it's case and slotted it into the X9D. This was not quite so good as it wasn't reporting the MultiProtocol version number and was only semi-successful in binding to a Spektrum receiver.

So. I read through the forum again . . . thought about it a bit . . . and re-flashed the board using the AVR-ISP-MK2 (with 3 temporary wires & 4 x 1.2v NiMh battery pack) with the OrangeRX Build from Pascals GitHub (v1.3.044 - https://github.com/pascallanger/DIY-Mul ... 3.0.44.bin)

BIG SUCCESS - everything fully working when slotted into my X9D . . . reporting the "v1.3.0.44 AETR" MultiProtocol version number, binding to DSM2/x receivers, full telemetry . . . WOW!

However, I still couldn't get it to update/flash from my FrSky Taranis X9D . . . So. I read through the forum again . . . thought about it a bit . . . and have a couple of questions;
  • Did I overwrite the MultiOrangeBlue Bootloader when I flashed the OrangeRX Build from Pascals GitHub? . . . I think that might be my issue !
It would be great if someone could confirm that I am on the right track . . . before I dissemble the MultiOrangeBlue, re-solder the temporary wires and, hopefully, flash one last time with my AVR-ISP-MK2.

PS: I also tried to update/flash the board with my FT232 USB adaptor using AVRdudess/AVDdude, but get the following error "avrdude.exe: Error: no libftdi or libusb support. Install libftdi1/libusb-1.0 or libftdi/libusb and run configure/make again." when I try and program, having selected the 'FT232D Based Generic Programmer' . . . any help regarding what I am doing wrong here would be great.

Re: Orange Module running MULTI protocol

Posted: Tue Nov 26, 2019 5:40 pm
by MikeB
It's been a long time since I've done anything with my Orange module(s). I don't even know what I have on them!
However, a quick test of my "blue" module shows it is not flashing from a X9Dplus or a 9XR-PRO. I'm not sure if I have ever put the bootloader on that module. I did test another module (green with the 9XR-PRO internal antenna connector) and that flashed OK.
I'll try to find time to investigate this further.
I have an ATMEL AVRISP-II programmer and that doesn't power the target device. That is done so the signal are guaranetted to be at the correct voltage for the target device when the target is correctly powered.

Mike

Re: Orange Module running MULTI protocol

Posted: Wed Nov 27, 2019 12:13 am
by palkina
Just to confirm that I was able to upgrade the firmware to a blue module.

This one was more tricky. I had to repeat the boot loader installation twice as the first attempt to upgrade the MultiProtocol firmware using the X9D failed.

The issue, I discovered during the second attempt when I retried flashing the boot loader with the pdimini sketch, was that I accidentally shorted a very small resistor that is in front of the ground pad with solder. After cleaning the bridged resistor and retrying flashing the firmware with the X9D it worked fine.

After reading a bit more, I was able to recompile the 1.3.0.44 and changed the order of the channels to TAER. I gave it a try and tested on a plane for a range test. I am very happy with the outcome.
BlueModule.jpg

Re: Orange Module running MULTI protocol

Posted: Wed Nov 27, 2019 12:38 am
by MikeB
DWiskow: One thing you may try is to watch the LED as you power on.
Normally it flashes slowly until the Tx is sending the serial data. However, if you hold the bind button pressed at power on, this is supposed to force the module to stay in the bootloader, resulting in the LED coming on solid. This helps test if the bootloader is present and the fuses are set correctly to start in the bootloader.
The Orange modules use an AVR XMEGA device that has a dedicated 4K bootloader area in addition to the normal 32K flash memory, so flashing the normal 32K should not erase the bootloader.

Mike

Re: Orange Module running MULTI protocol

Posted: Wed Nov 27, 2019 7:32 pm
by MikeB
DWiskow:
My Orange "blue" board is now working as required.
I did at one time have the bootloader on it, but it was erased when I read the flash contents.
The multi firmware I had on it was very old, it didn't even report what version it was.
I put the bootloader on it, in my case I used my AVRISP-II as I had that wired to the board already in order to read the existing flash contents.
Even with the bootloader a 9XR-PRO didn't flash the multi firmware as the existing firmware didn't include the "CHECK_FOR_BOOTLOADER" option, however by holding the bind button in at power on to force the module to stay in bootloader mode (while holding the trims as well!), I did then manage to flash the multi firmware (to 1.3.0.44).
I then put the module in an early Taranis an was able to flash it via the bootloader and app.

My guess is the bootloader was erased when you flashed the multi firmware. I think if you flash the bootloader again, using the Pro Mini, all will then work. The Pro mini will only flash the bootloader area and set the fuse to make the processor start in the bootloader.

Mike

Re: Orange Module running MULTI protocol

Posted: Thu Nov 28, 2019 7:20 pm
by DWiskow
Mike

Your input and observations have been most helpful . . . I now have my OrangeRX Transmitter (blue) all working perfectly. It is loaded with the latest MPM MultiOrangeBlue v 1.3.0.45 from Pascals Github together with your bootloader and was flashed/updated on my FrSky X9D / QX7 (via your bootloader/app) . . .

. . . this has been part of a broader project to get an old Turnigy 9XR functioning and operational as a 'vintage radio'. This is now complete, with the 9XR running "er9x-frsky v1.743-Mike" (2016 11 30 / er9x-820 / FrSky NT), which I think is the latest version of er9X for the 9XR. I also have it linked to my computer running eePe 422 and also working perfectly (although I had to update AVRdude and use the -F force option with the M64 to get it communicating via my Olimex AVR-ISP-MK2)

I have attached some pictures of the finished project . . . thank you for the time and effort you put into maintaining this software, not forgetting the time and patience you also apply to supporting people on-line. I will provide a fuller description of the issue I finally identified (with your help) and how I got this to work in a subsequent post.

Thanks
Dorian
Turnigy 9XR with OrangeMultiBlue (emulating a Spektrum DX5e)
Turnigy 9XR with OrangeMultiBlue (emulating a Spektrum DX5e)
Turnigy 9XR with OrangeMultiBlue
Turnigy 9XR with OrangeMultiBlue
OrangeMultiBlue v1.3.0.44/v1.3.0.44
OrangeMultiBlue v1.3.0.44/v1.3.0.44

Re: Orange Module running MULTI protocol (part II - FIXED)

Posted: Thu Nov 28, 2019 11:38 pm
by DWiskow
Mike

A more detailed breakdown of the solution to my bootloader problem, as promised;

Having originally managed to get my OrangeRX (blue) Transmitter working with MPM MultiOrangeBlue v 1.3.0.44, but completely failing to get a working bootloader that would enable me to flash/update the module from a radio in future (as set out in my post above, on Tuesday) . . . I went back to basics.

I tried to manually force the module into bootloader mode by holding the 'bind' button when powering on (with my NiMh battery pack) as you suggested, and never managed to get a solid LED (only a slow flash) ! This confirmed that there was definitely a problem related to the bootloader.

I re-soldered the Data, Clock, VCC (3.3v) and GND temporary wires to the OrangeRX Blue board, loaded an Arduino Pro Mini I had with the 'PDImini.ino' sketch, hooked it up to the Orange Blue board (which I powered via a 4 x 1.2v NiMh battery pack) . . . but just couldn't make it work (fast rather than slow flashes every time) after multiple attempts and carefully checking the correct wiring each time.

The Pro Mini I have is a 3.3v 8MHz version and I wondered if there were timing differences that were causing the flash of the bootloader to fail . . . I looked through the code and it didn't seem like this would be an issue given the use of 'delayMicroseconds()' in the 'PDI.ino' code (i.e. no obvious areas where timing could be an issue, to me) . . . but I did find a clue as to why my previous attempt with the Olimex AVR-ISP-MK2 might not have worked. The code in the 'PDImini.ino' sketch sets BOOTRST in FUSE2 before flashing the 3 pages of bootloader code (and I never did this when previously flashing the bootloader and/or MPM MultiOrangeBlue v 1.3.0.44 to the OrangeRX Blue board with my Olimex AVR-ISP-MK2 and AVRdude/AVRdudess).

So, I disconnected the Arduino Pro Mini and hooked the OrangeRX Blue board up to my Olimex AVR-ISP-MK2. I then used AVRdude/AVRdudess three times;

Code: Select all

1. avrdude -u -c avrisp2 -p x32a4u -P usb -v -e -U flash:w:"C:\multi-orangerx-aetr-blue-inv-v1.3.0.45.bin":a -U lock:w:0xFF:m

2. avrdude -u -c avrisp2 -p x32a4u -P usb -v -U flash:w:"C:\OrangeMultiBoot.hex":a

3. avrdude -c avrisp2 -p x32a4u -P usb -u -U fuse2:w:0xBF:m
The first of these flashes the latest version of MPM MultiOrangeBlue v 1.3.0.45 from Pascals Github into the 32Kb of normal flash memory after first fully erasing both the Flash and EEPROM (-e option).

The second of these then flashes your bootloader OrangeMultiBoot.hex (again from Pascals Github) into the 4Kb of bootloader flash memory (and does not erase anything first).

As a belt and braces check between steps 2 and 3, I dumped the full 36Kb of flash into an Intel Hex file with AVRdude and inspected address 0x8000 onward to confirm that the bootloader code matching that in your 'PDImini.ino' sketch was present (and it was).

Clearly, the bootloader code was present, but the bootloader was not being executed ! I had a look through the XMEGA A MANUAL and found the answer/details in section 4.16.3 where FUSE2 and BOOTRST is described.

So, the third and final step, was to set bit 0x40 of FUSE2 properly to tell the AVR Xmega to set BOOTRST (Boot Loader Section Reset Vector - to point to the first address in the boot loader flash section). The device will then start executing from the boot loader flash section after a reset.

SUCCESS . . . holding the 'bind' button when powering on (with my NiMh battery pack) generated a solid LED (your bootloader was running)

The rest, as they say is just detail, I removed the temporary wires, put it all back in its case and tested binding/controlling a model and re-flashing on a couple of radios (X9D & QX7) . . . it all worked perfectly.

In summary, the main issue/problem here was between user and keyboard (i.e. me) ! That is to say I didn't spot the clue you provided in a post in this thread back in April 2017 where you said "Lock bits should be 0xFF (nothing locked). Fuse 2 should have the 0x40 bit cleared to 0" . . . although I did read through the entire thread (but just didn't clock it) . . . it might be worth adding this information to your 'PDIflashing3.pdf' document for the benefit of those, like me, that read your document but use a PDI programmer rather than Arduino to flash the bootloader.

I may also be guilty of indiscriminately using the AVRdude/AVRdudess -e option to fully erase both the Flash and EEPROM when flashing both the MPM MultiOrangeBlue v 1.3.0.45 and your bootloader (and therefore inadvertently wiping one piece of code out while flashing the other) . . . also something for those following this path to watch out for !

However, I finally worked it out and it's all working correctly now. So thank you once again for your help.

Regards
Dorian

Re: Orange Module running MULTI protocol

Posted: Fri Feb 07, 2020 7:38 pm
by bionicbone
Can i just check that there is no new ways to flash the boot loader to the green board except using a pro mini? I have lots of others, Nano, Uno, Teensy v3.2, ESP8266, ESP32, 5v FTDI but not a pro mini :(

Re: Orange Module running MULTI protocol

Posted: Sat Feb 08, 2020 8:16 am
by bionicbone
OK, i figured that the uno is just a large mini so went for attempting to get the boot loader on the OrangeRx.

I think it worked, very faint led flashing 1 per sec on the Arduino Uno and when I power up the module with 3.3v while holding the bind button I get a solid LED on the module.
2020-02-08_08-09-33.jpg