openrcforums

Regardless of what the seller of your radio told you, there's no way to know what version your board is until you open it up and check. Our products work with all but the earliest "V1" boards. If you bought your radio since around 2011, you probably don't have to worry about it, but you should confirm your version. Most people refer to there being only 2 versions ("V1" and "V2"), when in fact FlySky is at least up to V15. But for our purposes, there's "V1" and then there's everything else. The "everything else" works. If you do have a V1 board, it can still work but soldering will be required and that sort of defeats the purpose.

s_mack wrote:When you say "Eurgle branded", my first thought... is it a V1 circuit board? I don't really hear the Eurgle name much anymore since the first years of the 9X's release.

From the FAQ:

Regardless of what the seller of your radio told you, there's no way to know what version your board is until you open it up and check. Our products work with all but the earliest "V1" boards. If you bought your radio since around 2011, you probably don't have to worry about it, but you should confirm your version. Most people refer to there being only 2 versions ("V1" and "V2"), when in fact FlySky is at least up to V15. But for our purposes, there's "V1" and then there's everything else. The "everything else" works. If you do have a V1 board, it can still work but soldering will be required and that sort of defeats the purpose.

Suncoaster wrote: so I cleaned them up using solder braid so they are now bright and shiny.

ProZak wrote:

Suncoaster wrote: so I cleaned them up using solder braid so they are now bright and shiny.

Did you clean those connections with isopropyl alcohol after doing that? Using (de)solder braid typically still leaves a hard layer of rosin on the surface which must be washed off in this case.

MikeB wrote:Please try once more just plugging the USB cable in with the power off. This should power the processor, and cause it to start in STM DFU bootloader mode, and the PC should recognise a device has been connected.
This should work even if the 9Xtreme is not installed in the radio, and uses a minimum of hardware on the 9Xtreme to operate.

OK, that worked Windows recognised that a device had been connected but it couldn't find a driver for the device. I found and installed Zadig and the device now shows as working properly in Device manager. Excuse the dumb question but what if anything can I do with this.

There are several things that appear odd. It seems the 9Xtreme is receiving serial data from the original board, suggesting the original; board has been flashed correctly, but then the original board should put "9Xtreme" on the display, whether the 9Xtreme is running or not. You could check this but removing the 9Xtreme and powering the original board on.

I think I tried that but I don't remember if anything happened, I will try it again tomorrow.

It is also odd that, in bootloader mode, the drives are recognised, but cannot be accessed, and it doesn't seem to respond to STM DFU mode.

Mike.

MikeB wrote:With the STM DFU (Device Firmware Uploader) bootloader, it is possible to flash new firmware to the 9Xtreme. This would allow, for example, a version with some tests in it to be flashed.

You might try powering up in 'normal' bootloader mode (trims inwards) again, and seeing if the two drives work now.

Mike.

MikeB wrote:When the two drives appear on the PC, one is the SD card and the other is a drive that maps the flash and EEPROM to appear as a drive. In windows explorer, this second drive should have a name of "9XTREME", be of size 1Mbyte and have 0 bytes free.

In Windows Explorer on my Win10 machine they just appear as drives E: and F: with no labels and any attempt to access them indicates that they are not formatted.

What revision of eepskye are you using? It is worth going here: viewtopic.php?f=7&t=4676#p65894, downloading "eepskye.zip" from 31-Jul-2016 21:14, unzipping the eepskye.exe and placing this in your eepe directory.

I was using revision 419, I have downloaded and installed the version from 31-Jul-2016 21:14 and will test that when I put the 9Xtreme board back into the transmitter.

Mike.

MikeB wrote:Are the USB ports USB3?

Mike.

MikeB wrote:Oops, I forgot the MENU button press in the sequence, please try this.
Power on and wait 10 seconds.
Press EXIT twice, to make sure any warnings are cleared.
Press LEFT LONG to get to the Radio Setup menu.
Press MENU to enter the display menu.
Press DOWN once to get to the red backlight brightness.
Assuming the backlight is white, press and hold LEFT. This should reduce the red brightness to 0 so the backlight colour changes to cyan.

Yes, that works, I now have a cyan backlight

Please confirm what you see on the backlight at power up.
Do you see the backlight come on RED for about a quarter of a second, go off for a quarter of a second, then on and off again, both for a quarter of a second, then the backlight comes on WHITE?

No there are no red flashes, the backlight comes on white and remains that way

If this is the case, then no data is getting to the 9Xtreme over the spring pins. Now to allow for this, we have a backup method of sending the button data from the original processor to the 9Xtreme. If the backlight flashes as I describe, then this backup method is working, or you would see some other colours after the two red flashes.

As I said no flashes at all just a steady white display

I'm still wondering if there is a poor connection between the spring pins and the pads, worth a triple check that both the pads a clean and the spring pins are clean.

I will give them another clean and I will check that the spring pins are clean also.

Mike.

MikeB wrote:Please go back to checking the contrast setting, either by the method used earlier with the buttons, or since eepskye seems to be talking, read the EEPROM and check the contrast value, you want about 30 as a start.

Mike.

jhsa wrote:Hmm, see if the LCD Ribbon is not damaged, it is well inserted and locked in place in the connector.

João