Deep dive into Inspire 1 Firmwares... Trying to debunk the funk...

Donnie Frank said:
Which software are you using to unpack the .bin files in that manner?

D
Click to expand...

That listing is from the log files in the MISC/LOG directory on the MicroSD card used for the update.

Turns out that every time you do an update it logs the process into internal memory of the aircraft. Every update you do amends to that log and writes the new version to the MicroSD card.

You can tell if an aircraft is a refurb or has a new N-Core in that the log will be quite short (usually only 1 update before the one you are doing). My Osmo+ is a refurb and it didn't have a scrubbed log, which means it was sent back for either an issue that had nothing to do with the camera (like a handle/battery malfunction), or someone returned it saying there was a problem and none existed they could tell. In my case I think it had to do with the cooling fan since it has started making noise on me. Doesn't matter since when you start recording it shuts the fan off, but it is still annoying to have a "new"/"refurb" product have any sort of defect.

Back on topic, there *is* a utility that breaks out the firmware modules into individual .bin files, but it is far too complicated for *most* users to get going, thus why I won't post it here (it also might be frowned upon).
 
Hi.
I downgraded my Inspire 1, v2, X3 to 1.8.1.00 direct from v01.11.01.50+ (see attached files) and it seems ok until I look att the .txt file.
I also downgraded the controls to 1.6.0

Does this look ok?

========== 2014.01.01 00:00:04 remo-con disconnect======
Packet: WM610_FW_V01.03.00.00.bin
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2015.12.13 14:01:09 =====================
Packet: WM610_FW_V01.04.00.10.bin
Upgrading ...
Result: Success.

========== 2015.12.13 15:36:02 =====================
Packet: WM610_FW_V01.04.00.10.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2015.12.13 16:08:28 =====================
Packet: WM610_FW_V01.05.00.30.bin
Upgrading ...
Result: Success.

========== 2015.12.13 18:11:57 =====================
Packet: WM610_FW_V01.05.00.30.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:06 remo-con disconnect======
Packet: WM610_FW_V01.06.00.40.bin
Upgrading ...

========== 2014.01.01 00:00:06 remo-con disconnect======
Packet: WM610_FW_V01.06.00.40.bin

========== 2014.01.01 00:00:06 remo-con disconnect======
Packet: WM610_FW_V01.06.00.40.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:06 remo-con disconnect======
Packet: WM610_FW_V01.11.01.50.bin
Upgrading ...

========== 2014.01.01 00:00:06 remo-con disconnect======
Packet: WM610_FW_V01.11.01.50.bin
Upgrading ...
Result: Success.

========== 2018.04.04 10:57:52 =====================
Packet: WM610_FW_V01.11.01.50.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the device.

========== 2018.04.04 10:58:54 =====================
Packet: WM610_FW_V01.11.01.50.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the device.

========== 2018.04.04 11:08:02 =====================
Packet: WM610_FW_V01.11.01.50.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the device.

========== 2018.04.06 10:16:32 =====================
Packet: WM610_FW_V01.11.01.50.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the device.

========== 2014.01.01 00:00:06 remo-con disconnect======
Packet: WM610_FW_V01.11.01.50.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the device.

========== 2018.04.06 10:30:34 =====================
Packet: WM610_FW_V01.11.01.50.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the device.

========== 2018.06.13 09:48:51 =====================
Packet: WM610_FW_V01.11.01.50.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the device.

========== 2019.03.06 09:15:46 =====================
Packet: WM610_FW_V01.11.01.50.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the device.

========== 2014.01.01 00:00:06 remo-con disconnect======
Packet: WM610_FW_V01.08.01.00.bin
Upgrading ...


, Bison
 

Attachments

  • Inspire_Firmware.jpg
    264.7 KB · Views: 13
  • Inspire_Downgrade.jpg
    274.2 KB · Views: 13
Bison, I take it you used the force file to downgrade?

If so, and the second picture is what it shows you should be all good.

Since your log file is so extensive, why did you attempt to do so many 1.11.1.50 upgrades?

Honestly, you grabbed the wrong .txt file. You grabbed the status file not the actual update log file. Look in the directories on the microSD card and you will see another logfile that has the details of what modules got changed. That will tell you exactly what changed from what to what.
 
Revisiting this topic...

If I'm reading you correctly, I can use an X3 running FW v1.08.xx to roll back an Inspire 1 running FW v1.11.xx??? I conclude this because, as you said, it's the latest *camera* FW that hamstrings the roll back. Is this correct thinking?

Note: I'm okay with the camera's legacy FW. So I don't require the latest modules for my cameras.

D
 
Actually I have not found them able to "brick" a X3 via a firmware rollback. Only the X5 series can be brick because of a firmware rollback.

So, in essence, ANY X3 camera firmware can be used to rollback an aircrafts firmware. What you end up with is the camera also running the rolled-back firmware revision.

Ultimately, the "ideal" camera firmware you want is the LATEST firmware revision due to "fixes" made in the cameras firmware.

If you are happy with the legacy camera firmware, then by all means run it. I just know that DJI made a number of "fixes" to the cameras themselves with later firmware revisions.

I might be able to put together a "camera update" that would ONLY update a cameras firmware to the latest. If there is any interest in that I will pull the camera firmware modules and package them in a separate firmware image. Just let me know.
 
Reactions: Donnie Frank
Do you know specifically what DJI fixed on the cameras? Honestly, both my cameras work well and without trouble. Very curious to hear your answer...

D
 
Actually, I do believe I have a technical brief that outlines the camera fixes themselves here somewhere...

I know the changes for the X5 series included white balance, aperture and color map fixes. ie, for the X5 they are more or less "required" to get the best possible image out of the X5 series.

In regards to the X3/Z3 I do believe it was white balance, color mapping and for the Z3 it included gimbal control and zoom fixes.

I will look through my research a little later tonight and see if I can find the tech info I downloaded.
 
Thanx. Your efforts are appreciated, but don't put yourself out. I just thought you might have that information readily available.

D
 
Nice info, thanks.

I still fly a couple of Inspire 1 + X5R commercially, with custom FW parameters (like 60° tilt, no NFZ or limits, calmer BMS, manual mode, etc). It's both amazingly fast now, and less picky about all sort of stuff.

I've got 6 crafts, some being modified hardware-wise (mostly replaced leg mechanics for lighter weight).

I'm at the latest FW though. Would a FW rollback bring the FCC, RF power, channel hacks via config files etc back, with an older Android DJI GO app?

I'm an engineer, but crappy at programming

Thanks in advance /Peter
 
Brian and the gang, I plan to use either an X3 or a FC350Z to roll back my 1.11.50 to 1.8.01

Is there a way, and mentioned above, to then bring the camera only back to current and have the extra camera functions associated with 1.11.50? I have the Python software which will disassemble the main bin file into the component parts but after that I’m a bit sketchy about which module bin’s the camera needs and how to create a new camera only bin file ? Ta in advance
 
You must log in or register to reply here.

Similar threads

R
Inspire 1 Firmware Fail (module 19 00 anybody??)
Replies
15
Views
3K
Inspire 1 Help
Donnie Frank
K
Inspire 1 firmware downgrade issues
Replies
23
Views
11K
Inspire 1 Help
MrMR
M
K
Inspire 1 repair story.
Replies
5
Views
4K
Inspire 1 Discussion
kevbac
K
Decoding the firmware upgrade log file
Replies
6
Views
5K
Inspire 1 Discussion
Tesla
S
No signal after update firmware
Replies
29
Views
10K
Inspire 1 Help
Jpearce87
J
Menu
Log in
Register