What's new
Aloft Forums

Welcome to Aloft Forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Can't update firmware Taranis X9D+

IRW

New User
The back story. On attending the flying field found my X9D would not connect with the installed X8R Rx. This combination had operated flawlessly the week prior. Inspection showed the Rx showing solid red. Tried to rebind without success. Decided to update/reload the Tx firmware but without success. All attempts were with fresh downloaded updates from FrSky, via the installed SD card. On viewing the card content on my computer only the usual folders could be seen. However, when viewing in the Tx each file was duplicated some with ._. prefix. On trying to delete the extra files the drop down only allowed to rename on some others were able to be deleted. One of the “Firmware” folders had the newly downloaded upgrades duplicated one with the above prefix the other normal. Both seemed to execute - that with the prefix proceeded to about 30% the other to about 10% then both generated “update failed.” Looking at the Tx the bind indicated D8/D16/LR9 (I hadn’t looked at this prior to attempting update), no mention of XJT as is usual with my Horus X12S and 9XE. It appears that the Tx has maintained and reverted to a earlier protocol, despite being recently updated to 2.1.0 (all receivers have also been updated). The immediate thought was that the SD card was corrupted so that was replaced but to no avail. Have also removed and replaced internal 122 coin battery, thinking this may have cleared the cache, again without success.
My question to the wider X9 community is - How do I clear the cache of the residual D8/16/LR9 protocol?
Looking forward to your suggestions.
 
There is no "cache".

If receivers that worked suddenly don't anymore without you doing anything to them then it's more likely some hardware failed than anything firmware related.

But it's most likely mismatched RF firmware if you say you updated things.
 
Last edited:
Hi Konrad thanks for your response.
XJT firmware.
I neglected to mention that I was able to bind the Rx to my other Tx's (all running 2.1.0 firmware). There had been no updating of either the subject Tx or Rx during the period between it operating one week and not the next. I'm confident that both the X9DP and the Rx had been updated earlier (along with 2 other Tx's and 12 or so Rx) and were working in unison. What I cannot understand is why the Tx has reverted to the D8/16/LR9 protocol and will not accept updates. Additionally why the SD card seems to accumulate files when they are not seen on the computer when either directly connected to the Tx or when copying files externally.
If you assume that I hadn't updated the Tx/Rx combination and it had in-fact been operating on the old protocol it still does not give any clue on why it will not accept the 2.1.0 upgrade as well as the strange SD card behaviour.
If it is as you suggest a hardware problem what's the solution.
Cheers
 
What's displayed as choices in the menu is a matter of OpenTX version, it is completely unlinked to the RF firmware you have on.

The junk files on the SD are likely from you using a mac to access the card, they put those hidden junk files, there are programs like cleaneject that get rid of them when ejecting external storage from the OS.
 
Thanks Kilrah, Deleted all files from the SD card, and reloaded fresh downloads of XJT and SD Card content via a PC. Same result - update failed after about 10%.
Any other suggestions?
Cheers
 
Try another SD, and also you never mentioned having one but if you have an external module in the slot remove it.
If that doesn't help it might be a faulty module.
 
Hi Kilrah
the original SD Card was replaced with a new "virgin" one, as initially thought that the original was corrupted.
I'm trying to flash the internal module.
Thanks for your interest.

Cheers
 
Kilrah you are a genius! Re-read your last post and realised you were talking about the "Orange DSM2" module I had installed. Removed it and lo and behold was able to flash the internal module.
If I knew where you live I'd send you a chocolate bar!!
Thanks

Cheers
 
Back
Top