Downgrade Problem after Craft was at Repair at DJI about dji-firmware-tools HOT 13 OPEN

Tried that already

No difference. It dont update the module. Because wrong Version. ;-)

from dji-firmware-tools.

Im sure m1900 is the Problem!!!
P3X_FW_LOG_AB (1).txt

from dji-firmware-tools.

Here comes the Problem with 1.9 Not 1.8

from dji-firmware-tools.

Same Problem next Copter!
But this one wasnt at DJI

Only 1.10 was installed once.
(m1900) V255.255.255.254

Will send LOG File as fast as i can.

from dji-firmware-tools.

if your target is FW 1.7.60, then I think the safest way is to cook its special version that doesn't contain package for m1900 and flash it with debug file
then - if you still have compass problems, I believe downgrade is not possible, so it will be wise to upgrade back to 1.10

from dji-firmware-tools.

I don't think dji_fwcon.py is able to correctly build a firmware without one of the modules.

I recently used it to extract and re-pack all the DJI firmwares listed in CSV file (you can do this by changing EXEC_FLAG to 0x02 in test_all.sh), and the firmwares which had NULL modules failed the test because checksums were invalid. Looks like null modules have some kind of special influence on checksums.

But - you won't be sure until you try.

from dji-firmware-tools.

Would it be possible to take module 1900 from 1.10 and put it in 1.7 or so?

from dji-firmware-tools.

In case of some modules, having different versions could make them unable to communicate and therefore brick your drone; but for FPGA module like m1900 I don't think bricking is possible - the serial NAND memory is likely programmed without use of the FPGA chip itself.

So yes, you can merge modules from two versions, I can't see any problem with that.

from dji-firmware-tools.

So gone step by step up.

At 1.9 Problem goes away
P3S_FW_LOG_AB(2).txt

from dji-firmware-tools.

Would it be possible to take module 1900 from 1.10 and put it in 1.7 or so?

But I don't think this will help you because m1900 doesn't have that 255.255.255.254 version in FW 1.10

from dji-firmware-tools.

Why don't you try renaming M1900 target bin to "PFPGAFw3.bin" and put that on your card and load it that way to see if it clears up the version "255.255.255.254" ...It shouldn't matter what bin you get it from because what I'm seeing is they're the same version from at least fw ver 1.03 to 1.10...This is the way I downgraded my spare batteries...It acts a little differently while loading but it does work for THEM at least...Of course it's at your own risk but what isn't doing this stuff...

'target': 'm1900', Stores firmware for FPGA air model 0 version=01.00.2144

from dji-firmware-tools.

Strange
People are downgrading from 1.10 since long time.
https://phantompilots.com/threads/downgrading-firmware-on-p3p-from-1-10-9-to-1-7-6.105384/

Maybe you was on 1.11 and that caused a problem?

You tried to 'refresh' firmware after downgrading?

from dji-firmware-tools.

Can we revisit the m1900 issue now that we have keys tri look at newer fw? Can we tell what the problem stems from now? Is it possible to add a module by itself?

from dji-firmware-tools.