firmware from edu to regular Tello
- Thread starter santdrone
- Start date
quaddamage
Well-known member
- Joined
- Sep 5, 2019
- Messages
- 72
- Reaction score
- 20
Initial read:
The difference between regular Tello and Tello EDU (with Photos)
TLDR: HW is the same, but a person who tried just flashing EDU FW says it didn't boot the drone. He speculates the issue is in parts of the ROM not updated by FW - some kind of metadata or extra verification block.
From myself, I'd add that the FW is stored encrypted - so it's also possible that Edu has just different decryption key. Then, after update, the drone stays at bootloader because decryption of the FW fails.
Next read:
Problems with firmware update
TLDR: The thread is about bricked drone rather than Std -> Edu switch, but some info on Movidius SDK (MDK) is there. The MDK files are accessible, if you know who to ask. However, analyzing them would take considerable effort, and noone is willing to spend that time for a cheap toy.
The need to analyze MDK was hinted at in the first thread already, and I agree with that - to understand how to decrypt the FW, one needs to understand the FW file formats, and that is only possible to through the MDK.
The post above also links to the next read:
https://github.com/o-gs/dji-firmware-tools/wiki/Firmware-m0802
This is some surface level explanation of how the FW looks like and how it is loaded. Enough to get someone started, if he/she decides to spend the time analyzing MDK.
The difference between regular Tello and Tello EDU (with Photos)
TLDR: HW is the same, but a person who tried just flashing EDU FW says it didn't boot the drone. He speculates the issue is in parts of the ROM not updated by FW - some kind of metadata or extra verification block.
From myself, I'd add that the FW is stored encrypted - so it's also possible that Edu has just different decryption key. Then, after update, the drone stays at bootloader because decryption of the FW fails.
Next read:
Problems with firmware update
TLDR: The thread is about bricked drone rather than Std -> Edu switch, but some info on Movidius SDK (MDK) is there. The MDK files are accessible, if you know who to ask. However, analyzing them would take considerable effort, and noone is willing to spend that time for a cheap toy.
The need to analyze MDK was hinted at in the first thread already, and I agree with that - to understand how to decrypt the FW, one needs to understand the FW file formats, and that is only possible to through the MDK.
The post above also links to the next read:
https://github.com/o-gs/dji-firmware-tools/wiki/Firmware-m0802
This is some surface level explanation of how the FW looks like and how it is loaded. Enough to get someone started, if he/she decides to spend the time analyzing MDK.
