Ok, did some more digging and my TX only works with Original FS-i6-Update-20151015 updater firmware and RCLogger Nova X350 firmware. Any other Uploader and firmware gives Throttle warning and no secret menu also. Flysky USB Flight Simulator Adapter Cable for Flysky FS-i6 FS-i4 FS-TH9X FS-T6 FS-T4B FS-GT3 FS-GT2 Remote Controller. 4.1 out of 5 stars 45. Flysky Data Cable USB Download Line for FS-i6 FS-T6 FS-GT6B FS-T4B FS-I4 Transmitter Controller Firmware Update. 4.1 out of 5 stars 21. Get it as soon as Sat.

Hey guys,I have been following the progress of the github page. I would just like to know if you think that an update will ever be realeased (it seems to me that you're going strong). Also, do you think that the update may be able to solve the memory issues and the range issues that sometimes the transmitter has? I'll be honest, I am considering buying this transmitter but some of the comments I read are not very promising and as such I am trying to decide between the FS-i6 and the FS-T6.

I prefer the T6 because of the LiPo mod, the switches are on top, the scroll wheel and the overall look of it. But its issues, specially the range issue really puts me off. Can any of you give me any info about any of the things above mentioned (both the range with stock firmware and the progress of the custom firmware)? Thanks and keep up the good work!Cheers. But its issues, specially the range issue really puts me offThe FW has no bearing on the range - this is a property of the transmitter module itself (and antenna). It's hardware limitation.I have been flying my 2 T6es to the limit of my sight and i did not see any range problems (no pun intended. Perhaps other tx are better but I have no comparison.

Perhaps one of 9x with removable tx module would suit you?AFAIK the memory problems have been fixed in latest original fw (ca 2012).The custom fw is in 'alpha' - not all features are implemented (vs 9x.). Is it 128KiB flash CPU or not?

Unfortunately it does not appear so.The CPU on the board is STM32F100R8T6B.This decodes as follows (according to )STM32F100R8T6B:STM32 - 32 bit arm micro-controllerF - general purpose100 - value lineR - 64 pins8 - 64KiB flash (128KiB would be marked as 'B' here)T - LQFP package6 - Industrial temperature range, –40 to 85 °CB - Internal codeThe 128KiB rumor started with the use of stm32flash utility. It reports a 128KiB flash. Both of my T6es have the same chip and the utility reports 128KiB flash. Martin's Tx also reports so. Likely, this is bug in the utility.Oh well we will have to compress the code more then. Michkrom wrote:Is it 128KiB flash CPU or not?

Unfortunately it does not appear so.The CPU on the board is STM32F100R8T6B.This decodes as follows (according to )STM32F100R8T6B:STM32 - 32 bit arm micro-controllerF - general purpose100 - value lineR - 64 pins8 - 64KiB flash (128KiB would be marked as 'B' here)T - LQFP package6 - Industrial temperature range, –40 to 85 °CB - Internal codeThe 128KiB rumor started with the use of stm32flash utility. It reports a 128KiB flash. Both of my T6es have the same chip and the utility reports 128KiB flash. Martin's Tx also reports so.

Likely, this is bug in the utility.Oh well we will have to compress the code more then.I'm pretty sure my stm32f100r8t6b has 128kb (even though the datasheet says otherwise). I managed to flash 130kb to it (a little over that generated flash overflow) and then I also managed to print the data out to a serial port and boot my firmware. It all looked nice, so the data had to go somewhere. It could be that the datasheet has a typo in it or it could be that my chip has the wrong numbers printed on it.Try flash yours with firmware over 64k and see if it works. Perhaps it will just like it does for me.

Pretty sure it is an 8. Looks like a snowman. B in the end is more flat on one side. Perhaps they just put 128k into them just to avoid reprogramming the production line for two different chips or something - maybe cheaper that way. I'm rather surprised as well, I must say. But I haven't looked deeper into what is actually happening.

All I can say is that after writing 130k fw with stm32flash, I could read both the huge data array back and run my firmware. So at least it didn't overwrite anything. May look further into it later if I experience any problems along the way.

Or maybe my board is one in a million that got 128k indeed.I would suggest anyone who has the fst6 board to try and burn 128k firmware to it using the ST bootloader and stm32flash utility and report back on the results. Would be interesting to know. Right Martin. It's a snowman's 8! Certainly an 8. The B is at the end and looks different.And, right you are - the flash does write and read all 128KiB!

Verified by concatenating two FWs (FS and AR) and flashing it in. The write then read back checks out.

Also, it boots to the first one (and it would not if the addresses simply had wrapped on the begining).Perhaps STM makes a single chip silicon but then bins it into 16, 32, 64 and 128 KiB options. Likely testing flash takes time and time is big money on IC testers so they only test a part of the flash. I suppose they would not bin it based on actual failures in the flash itself as it would be to costly at these price points.Great that I was wrong.We have flash to splurge and we are not afraid to use it! Hello.Here is one enthusiast reporting for duty. I am quite new for the whole embed scene and specially for ST's ARM's.

Genius Colorpage Vivid Pro Driver for Windows 7 32 bit, Windows 7 64 bit, Windows 10, 8, XP. Uploaded on 4/17/2019, downloaded 9830 times, receiving a 84/100 rating by 4490 users. Suited for 2020 OS and PCs. Genius colorpage vivid pro ii Easy Driver Pro registered version I can’t remember how to recreate that. Ancient scanner Genius Colorpage Vivid Pro II CNET’s Forum on PC hardware is the best source for finding help, troubleshooting, and getting buying advice from a community of experts. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer. GENIUS Series GENIUS ColorPage-Vivid Pro USB Scanner Driver GENIUS ColorPage Scanner Vivid Pro USB. Genius color page vivid pro drivers for mac. Genius product support helps you to download Drivers, Manuals and Applications. You can find FAQ here about how to use the product. ColorPage-Vivid Pro II.

I have been messing about with the TI's micros for some time now. So I have some knowledge in C programming and micros, but I am in quite early stages still.The thing that got me interested in the embed world, was that I wanted to make my own RC RX/TX. I found out that there was quite bit bigger hill for me to clime, that I had first expected. Now over two years later, I am still intrigued by the embed world and all of it's possibilities. As I am doing this as a hobby with no previous education in the subject my progress is quite slow sometimes. Still I have managed to complete some simple projects and started lots of not so simple ones, that have progressed quite well.But enough about me.I found about AR-T6 from art103's blog page in last fall. I have since bought a second FS-T6 and I have soldered wires to it to be able to flash the firmware with stflash.

(Yes I know that one can flash the firmware now days with USB cable, but I have not found it in my self to make one. Yet.)I really would like to contribute to this project anyway I can. I am still quite hesitant to take the source and just mess with it, as I don't trust my skills enough to make anything than a big mess, but if anyone has some trivial and/or boring things for me to do or try (testing ect.) I am more than willing to help.I also have couple of questions.I would like to try flashing the original FW back to my transmitter, do I have to flash or erase the eeprom chip? Also does anyone know how to calibrate the sticks in the original FW?

As the transmitter had a issue with the sticks not being centred with the original FW. The custom AR-T6 FW had no issues calibrating the sticks. I am asking because I would like to use my second transmitter as trainer TX with my friend, while I am not doing any testing of the AR-T6. Is there sum one that can help me please. I have a fly sky fst6 transmitter.i switched it on last week and the back light will light up to show the power is on. But there is no programs showing on the led screen no righting comes up nothing at all just a plain back light.

This transmitter is only 2 year old and as been used 6 or 7 times. I paid 50£ for this but now they are only 37£ on e bay is it possible that this can be repaired buy my self. Or if not is it worth having it repaired.

Please help thanks for your time Steve.

A cross-platform open source command-line firmware updater for the FlySky i6.Precompiled binaries for Windows and Linux can be found on the releases page.

To my best understanding, it is not possible to accidentally brick the remote by flashing firmware; the initial bootloader is never overwritten.

Usage: Place a firmware image next to the updater and double-click the updater.
Alternatively, use the command line interface:

Firmware Update Mode

If the remote does not start anymore, one can access the firmware update mode as follows:

Protocol details

The serial communication between computer and remote follows a simple protocol.Messages sent by the computer are constructed as follows:

Messages sent by the remote are simply prefixed with 0x55:

Length

The message length is a little-endian two-byte integer. It accounts for the full message, including optional prefix and checksum.

Payload

The payload is the actual message. From observing the original updater (see serial-port-dump.txt), we can deduce the following message types (written in hexadecimal notation):

Ping Command

The response seems to contain the firmware version, but I did not investigate this any further.

Restart Command

This command just restarts the remote, e.g. after a successful firmware update.

'Can we write?' Command

The updater sends a 'can we write now?' message every 1024 bytes, which, after confirmation, is followed by four write commands à 256 bytes.

where AD DR denotes the offset we want to start writing to (little-endian two-byte integer).

Write command

where AD DR is the offset (see above), SI ZE the number of bytes (little-endian two-byte integer, usually 256), and DATA the bytes that should be written to memory.If the updater does not receive a response quickly, it will re-send the write command. Interestingly, this results in a race condition in the original updater: If the updater does not receive a confirmation for WRITE 0x1800 in time (the timeout here is very low), it will re-send the same command. The remote may however process both commands successfully and then return two confirmations. The updater treats the second confirmation for 0x1800 as a confirmation for the next offset, which however may not have been transmitted properly. This updater addresses the problem with very conservative timeouts.

Checksum

The checksum is a little-endian two-byte integer that is computed as follows:

Example

The ping message is simply c0 - including prefix and checksum it has a total length of 5: 05 00 c0 XX XX
We can now compute the checksum: 0xFFFF - 0x05 - 0x00 - 0xc0 = 0xff3a
Thus, the complete ping message is: 05 00 c0 3a ff