P3 Firmware Phantom 3 Pro Firmware Update Error

Joined
Mar 25, 2017
Messages
10
Reaction score
1
Age
44
hi guys,

For months, I've been trying to upgrade my firmware of my P3X but after unzipping the file on my computer and copying it to the root folder of the SD card followed by switching on the drone and waiting for firmware upgrade to begin. It never does. I even bought an expensive Fast SD card and a USB 3 but still no luck.

Please please help.

cheers,
Deven
 
Joined
Jun 28, 2019
Messages
48
Reaction score
24
Age
57
Have you tried connecting the bird (USB) to your computer with the SD card in its slot? What firmware are you downloading?
 
  • Like
Reactions: KachemakDiver
Joined
Jun 30, 2016
Messages
971
Reaction score
339
Location
PL
Get the log. Share the log.

 
Joined
Mar 25, 2017
Messages
10
Reaction score
1
Age
44
Have you tried connecting the bird (USB) to your computer with the SD card in its slot? What firmware are you downloading?
Yes, I have tried connecting the bird to the computer with the SD card in the slot. I got no change.
The phone where I am using for the upgrade is

P3X_FW_V01.11.0020
 
Joined
Mar 25, 2017
Messages
10
Reaction score
1
Age
44
Get the log. Share the log.

Delete history success.

Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2019.09.24 22:08:54 =====================
Packet: P3X_FW_V01.11.0020.bin
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2019.09.24 22:10:55 =====================
Packet: P3X_FW_V01.11.0020.bin
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2019.09.24 22:12:03 =====================
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:05:11 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2019.09.27 11:21:13 =====================
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:05:49 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2019.09.27 16:09:16 =====================
Packet: P3X_FW_V01.11.0020.bin
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:01:39 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2019.09.27 18:53:47 =====================
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:43 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Corrupted.
Firmware bin file is corrupted, download it again from the DJI offical website.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:11 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.
 

Oso

Premium Pilot
Joined
May 19, 2015
Messages
4,378
Reaction score
3,150
Location
Western US
Delete history success.

Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2019.09.24 22:08:54 =====================
Packet: P3X_FW_V01.11.0020.bin
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2019.09.24 22:10:55 =====================
Packet: P3X_FW_V01.11.0020.bin
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2019.09.24 22:12:03 =====================
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:05:11 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2019.09.27 11:21:13 =====================
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:05:49 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2019.09.27 16:09:16 =====================
Packet: P3X_FW_V01.11.0020.bin
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Failed.
Reboot the aircraft and try to upgrade the firmware again.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:01:39 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2019.09.27 18:53:47 =====================
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:43 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Corrupted.
Firmware bin file is corrupted, download it again from the DJI offical website.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:13 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.

========== 2014.01.01 00:00:11 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Result: Abort.
The firmware on the SD card is identical to or older than the current firmware on the aircraft.

========== 2014.01.01 00:00:12 remo-con disconnect======
Packet: P3X_FW_V01.11.0020.bin
Upgrading ...
Result: Success.
So I’m sure you see what we see. You already have at least 1.11.20 installed on your AC. What is leading you to believe that you need to install it again?

It would be helpful to see the log that @quaddamage asked you to post. Info is in the link he provided earlier in this thread.

Once you’ve located the correct log, it’s much easier if you attach it here rather than doing a copy/paste of the entire contents.
 
Last edited:
  • Like
Reactions: JoBe
Joined
Mar 25, 2017
Messages
10
Reaction score
1
Age
44
So I’m sure you see what we see. You already have at least 1.11.20 installed on your AC. What is leading you to believe that you need to install it again?

It would be helpful to see the log that @quaddamage asked you to post. Info is in the link he provided earlier in this thread.
This log that I just sent is the one that @quaddamage asked for yes? Or am I confused. :)

MY DJI GO doesn't even recognize the P3P. It thinks it's an Inspire Raw. I've reinstalled the app many times but still the same.
 

Oso

Premium Pilot
Joined
May 19, 2015
Messages
4,378
Reaction score
3,150
Location
Western US
This log that I just sent is the one that @quaddamage asked for yes? Or am I confused. :)
You posted the RESULTS_AB log. @quaddamage gave you a link to find your LOG_AB file. It would have been much less confusing if you had followed his link above, but here is the this very same link for you to follow now. :)

Once you’ve located the correct log, it’s much easier if you attach it here rather than doing a copy/paste of the entire contents.
 
  • Haha
Reactions: JoBe
Joined
Mar 25, 2017
Messages
10
Reaction score
1
Age
44
Get the log. Share the log.

[00089068]Delete history success.

[00089376]========== remo-con disconnect. boot(15) ============
[00089445]Packet [C:\P3X_FW_V01.11.0020.bin] detected, card sn [0x34d8dbdd].
[00089519]Packet upgrade start...

[00089592]Packet checking...
[00089664]Packet vlink 01.11.0020 <-> 01.11.0020.
[00089733]Record vlink 01.11.0020 <-> 01.11.0020 (flow = 0).
[00089799]Done.

[00089875]Version checking[1]...
[00089976][03 06][00] v2.4.20.50 -> v2.4.20.50
[00090096][03 05][00] v34.2.0.9 -> v34.2.0.9
[00090179][04 00][00] v1.48.0.0 -> v1.48.0.0
[00090356][11 00][00] v1.8.0.0 -> v1.8.0.0
[00090516][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.
[00090585][11 01][00] v1.8.0.0 -> v2.0.0.33
[00090715][12 00][00] v1.12.0.0 -> v1.12.0.0
[00090835][12 01][00] v1.12.0.0 -> v1.12.0.0
[00090955][12 02][00] v1.12.0.0 -> v1.12.0.0
[00091095][12 03][00] v1.12.0.0 -> v1.12.0.0
[00091264][15 00][00] v1.1.2.0 -> v1.1.2.0
[00091395][17 00][00] v1.1.1.7 -> v1.1.1.7
[00091556][17 01][00] v1.0.2.7 -> v1.0.2.7
[00012509]========== remo-con disconnect. boot(15) ============
[00012578]Packet [C:\P3X_FW_V01.11.0020.bin] detected, card sn [0x34d8dbdd].
[00012645]Packet upgrade start...

[00012729]Packet checking...
[00012797]Packet vlink 01.11.0020 <-> 01.11.0020.
[00012871]Record vlink 01.11.0020 <-> 01.11.0020 (flow = 0).
[00012943]Done.

[00013017]Version checking[1]...
[00013154][03 06][00] v2.4.20.50 -> v2.4.20.50
[00013269][03 05][00] v34.2.0.9 -> v34.2.0.9
[00013352][04 00][00] v1.48.0.0 -> v1.48.0.0
[00013509][11 00][00] v1.8.0.0 -> v1.8.0.0
[00013654][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.
[00013725][11 01][00] v1.8.0.0 -> v2.0.0.33
[00013850][12 00][00] v1.12.0.0 -> v1.12.0.0
[00013969][12 01][00] v1.12.0.0 -> v1.12.0.0
[00014109][12 02][00] v1.12.0.0 -> v1.12.0.0
[00014269][12 03][00] v1.12.0.0 -> v1.12.0.0
[00014440][15 00][00] v1.1.2.0 -> v1.1.2.0
[00014569][17 00][00] v1.1.1.7 -> v1.1.1.7
[00014730][17 01][00] v1.0.2.7 -> v1.0.2.7
[00027443][19 00][00] device not detected.
[00027554][01 00][00] v1.32.5432 -> v1.32.5432
[00027657][01 01][00] v1.32.5432 -> v1.32.5432
[00027782][08 00][00] v0.13.0.7 -> v0.13.0.7
[00027911][09 00][00] v0.0.0.0 -> v4.1.0.0 need upgrade.
[00028017]Done.

[00030119]Waiting for user confirm...
[00040219]Timeout, start upgrade automatically.

[00040381]Firmware upgrading[1]...
[00040476][09 00] Firmware checksum failed.
[00040578]Packet upgrade failed at firmware upgrade.



[00012609]========== remo-con disconnect. boot(15) ============
[00012715]Packet [C:\P3X_FW_V01.11.0020.bin] detected, card sn [0x34d8dbdd].
[00012819]Packet upgrade start...

[00012933]Packet checking...
[00013036]Packet vlink 01.11.0020 <-> 01.11.0020.
[00013143]Record vlink 01.11.0020 <-> 01.11.0020 (flow = 0).
[00013256]Done.

[00013359]Version checking[1]...
[00013537][03 06][00] v2.4.20.50 -> v2.4.20.50
[00013715][03 05][00] v34.2.0.9 -> v34.2.0.9
[00013827][04 00][00] v1.48.0.0 -> v1.48.0.0
[00014035][11 00][00] v1.8.0.0 -> v1.8.0.0
[00014235][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.
[00014341][11 01][00] v1.8.0.0 -> v2.0.0.33
[00014515][12 00][00] v1.12.0.0 -> v1.12.0.0
[00014676][12 01][00] v1.12.0.0 -> v1.12.0.0
[00014836][12 02][00] v1.12.0.0 -> v1.12.0.0
[00015015][12 03][00] v1.12.0.0 -> v1.12.0.0
[00015232][15 00][00] v1.1.2.0 -> v1.1.2.0
[00015395][17 00][00] v1.1.1.7 -> v1.1.1.7
[00015595][17 01][00] v1.0.2.7 -> v1.0.2.7
[00028200][19 00][00] device not detected.
[00028309][01 00][00] v1.32.5432 -> v1.32.5432
[00028411][01 01][00] v1.32.5432 -> v1.32.5432
[00028531][08 00][00] v0.13.0.7 -> v0.13.0.7
[00028656][09 00][00] v0.0.0.0 -> v4.1.0.0 need upgrade.
[00028755]Done.

[00030864]Waiting for user confirm...
[00040969]Timeout, start upgrade automatically.

[00041142]Firmware upgrading[1]...
[00041268][09 00] Firmware upgrade start...
[00093508][09 00] Firmware upgrade finished successfully.
[00093754]Done.

[00093866]Version checking[2]...
[00094003][03 06][00] v2.4.20.50 -> v2.4.20.50
[00094143][03 05][00] v34.2.0.9 -> v34.2.0.9
[00094288][04 00][00] v1.48.0.0 -> v1.48.0.0
[00094463][11 00][00] v1.8.0.0 -> v1.8.0.0
[00094648][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.
[00094764][11 01][00] v1.8.0.0 -> v2.0.0.33
[00094912][12 00][00] v1.12.0.0 -> v1.12.0.0
[00095061][12 01][00] v1.12.0.0 -> v1.12.0.0
[00095216][12 02][00] v1.12.0.0 -> v1.12.0.0
[00095401][12 03][00] v1.12.0.0 -> v1.12.0.0
[00095629][15 00][00] v1.1.2.0 -> v1.1.2.0
[00095776][17 00][00] v1.1.1.7 -> v1.1.1.7
[00095977][17 01][00] v1.0.2.7 -> v1.0.2.7
[00096116][19 00][00] v255.255.255.254 -> v1.0.8.96
[00096232][01 00][00] v1.32.5432 -> v1.32.5432
[00096340][01 01][00] v1.32.5432 -> v1.32.5432
[00096457][08 00][00] v0.13.0.7 -> v0.13.0.7
[00096592][09 00][05] v4.1.0.0 -> v4.1.0.0
[00096707]Packet upgrade finish successfully.
 
Joined
Jun 30, 2016
Messages
971
Reaction score
339
Location
PL
Your drone is functional. All modules announce that they work, and are at proper versions.
No idea what exactly you want to achieve.

In regard to the only line which might look suspicious to some:
Code:
[00096116][19 00][00] v255.255.255.254 -> v1.0.8.96
Here's an explanation:

There are two major revisions of the OFDM board. Older one, sometimes called "OFDMv1", uses FPGA (which is a chip which can become anything), and newer one, "v2", which uses so-called ASIC - a chip which cannot become anything other than it was created for.

Some explanation of FPGA vs. ASIC:
FPGA requires information about what it should become (in Ph3, that info is in firmware module m1900). When the chip is powered, it loads so-called "bitstream" from a Serial Flash chip, and that bitstream makes it do a specific function. It may sound similar to programming a microprocessor, but it really isn't - this does not load a program into a processor, it fundamentally tells the chip what it is. From the digital circuit point of view, you may tell that FPGA contains a lot of transistors, connected into logic gates, and everything is connected to everything (well.. almost, the reality is more complex but it doesn't matter here). So the bitstream tells the chip which connections should be removed for the FPGA to start doing a specific function. For example, FPGA could become microprocessor - if proper connections are removed, it may start being a device which fetches assembly instructions and executes them. In case of Ph3, the FPGA is used for encoding digital data with redundancy (for radio transmission) and digital error correction (when receiving data from the radio).
ASIC is a chip which requires no bitstream. It just does what it is made to do; may accept programming or configuration options, but it can't become something else. ASICs are much cheaper to produce than FPGAs, and often are faster. Every chip which is not FPGA - is really ASIC. If you'll make ASIC with a bug - there is no way to correct it. You just need to make a new chip (again, simplifying a bit).

So back to the log line - OFDMv2 does not require m1900, as it always does it function, without any firmware. The Serial Flash chip is still on the board, but it is unused - this is why it returns the version of v255.255.255.254 - it simply means that chip doesn't store anything at all. Because it doesn't need to.

Forcing firmware update with "*FW_DEBUG" file will make that Serial Flash programmed with the module from update file; but that data will still be unused.
 
Last edited:
  • Like
Reactions: JoBe and Oso
Joined
Mar 25, 2017
Messages
10
Reaction score
1
Age
44
Your drone is functional. All modules announce that they work, and are at proper versions.
No idea what exactly you want to achieve.

In regard to the only line which might look suspicious to some:
Code:
[00096116][19 00][00] v255.255.255.254 -> v1.0.8.96
Here's an explanation:

There are two major revisions of the OFDM board. Older one, sometimes called "OFDMv1", uses FPGA (which is a chip which can become anything), and newer one, "v2", which uses so-called ASIC - a chip which cannot become anything other than it was created for.

Some explanation of FPGA vs. ASIC:
FPGA requires information about what it should become (in Ph3, that info is in firmware module m1900). When the chip is powered, it loads so-called "bitstream" from a Serial Flash chip, and that bitstream makes it do a specific function. It may sound similar to programming a microprocessor, but it really isn't - this does not load a program into a processor, it fundamentally tells the chip what it is. From the digital circuit point of view, you may tell that FPGA contains a lot of transistors, connected into logic gates, and everything is connected to everything (well.. almost, the reality is more complex but it doesn't matter here). So the bitstream tells the chip which connections should be removed for the FPGA to start doing a specific function. For example, FPGA could become microprocessor - if proper connections are removed, it may start being a device which fetches assembly instructions and executes them. In case of Ph3, the FPGA is used for encoding digital data with redundancy (for radio transmission) and digital error correction (when receiving data from the radio).
ASIC is a chip which requires no bitstream. It just does what it is made to do; may accept programming or configuration options, but it can't become something else. ASICs are much cheaper to produce than FPGAs, and often are faster. Every chip which is not FPGA - is really ASIC. If you'll make ASIC with a bug - there is no way to correct it. You just need to make a new chip (again, simplifying a bit).

So back to the log line - OFDMv2 does not require m1900, as it always does it function, without any firmware. The Serial Flash chip is still on the board, but it is unused - this is why it returns the version of v255.255.255.254 - it simply means that chip doesn't store anything at all. Because it doesn't need to.

Forcing firmware update with "*FW_DEBUG" file will make that Serial Flash programmed with the module from update file; but that data will still be unused.
Thank you for the info. I am having a number of other problems with this firmware update. Firstly, I was formatting the SD card using FAT32. Then, after putting the sd card back into the drone and switching on the machine, i got no firmware updating happening. So then I would switch off the Drone, press the button close to the flashing red light and while holding it in, switch the drone on. I would have to hold this button in for about 5 seconds after switching on the Drone and then let it go. The Drone would then finally give me the four beep sounds to show that the firmware is upgrading but this upgrading only took 3 minutes. Then, after switching the Drone off again, I inserted the second battery and switched on the Drone. I did not see any updating happening for the battery. After this, I tried connecting the Drone to the controller to update the controller but again, no updating happened. When I tried formatting the SD card using NTFS I did not get any reaction from the Drone. No matter what I did in switching the drone on and off and pressing the lights at different timings, nothing happened. So after the 3 minutes update and the failure to update the batteries and the failure to update the controller, I downloaded the DJI Go app. after switching on all systems and connecting my phone to the controller, and switching on the DJI Go app, the DJI go would recognize my drone as an Inspire Raw, not as a P3P. So I could not select P3P. I then went into my drawer and pulled out one of my old phones. I had used this phone when I first bought the P3P and everything worked fine but that was two years ago. So this time when I pulled out the old phone and started it everything seemed fine in the beginning for about 10 minutes I was even able to fly the Drone. Thenjoy my phone slowly started losing communication. Now none of my phone are helping.
 
Joined
Jun 30, 2016
Messages
971
Reaction score
339
Location
PL
everything seemed fine in the beginning for about 10 minutes I was even able to fly the Drone. Thenjoy my phone slowly started losing communication. Now none of my phone are helping.
You need to be more specific in what "losing communication" means.

In general, if you had issues with mobile device or cable - you should first try as many of these as you can, to make sure the issue isn't on that side.
 
Joined
May 15, 2019
Messages
120
Reaction score
70
Age
57
Location
Homer,Alaska
Don’t know if this helps, but my Android tablet says that all of my P3P’s are Inspire Raw when I am first connected to the Go app. When I turn the a/c battery on the camera camera icon on the app turns blue. Tap the camera button, when the app shows you are ready to go, start up the bird and fly. Afterwards, sync the flight in your app account. Then when you tap the flight log to view it, in the top left corner of the screen, it tells you it is a Phantom 3 Professional and the name of the P3P.
I think DJI just doesn’t list the phantom 3’s in the app where it says to choose which model you are connecting.
 
Joined
Jun 30, 2016
Messages
971
Reaction score
339
Location
PL
my Android tablet says that all of my P3P’s are Inspire Raw when I am first connected to the Go app.
That's because you're starting things in a wrong order.
But it doesn't matter that much, everything will work either way.

I think DJI just doesn’t list the phantom 3’s in the app
No, you're just trying to confuse the app by making it not able to tell which drone you'll be working with.
In the manual, there is a specific order of turning things on. But unless there is another issue with the mobile device, that won't affect any functionality.

If the drone starts flying, then this is not related to connection issues in any way.
 
  • Like
Reactions: JoBe
Joined
May 15, 2019
Messages
120
Reaction score
70
Age
57
Location
Homer,Alaska
I actually log into the Go app first,then turn on the remote, then the Phantom.
It always recognizes the drone once they connect. So I don’t pay any attention to what the app says before it connects.
As you said quaddamage, it works anyway. Thanks for the information, it had me curious so I went back and looked into the quick start guide 👍
 
Joined
Mar 25, 2017
Messages
10
Reaction score
1
Age
44
You need to be more specific in what "losing communication" means.

In general, if you had issues with mobile device or cable - you should first try as many of these as you can, to make sure the issue isn't on that side.
Yes, you were right. I tried numerous android phones and failed with all of them but when I connected an ipad, everything seems fine.

Thank you!!
 

New Threads

Forum statistics

Threads
136,140
Messages
1,408,067
Members
99,058
Latest member
Cherry