Please select Into the mobile phone version | Continue to access the computer ver.
help to read log file
1705 14 2016-11-21
Uploading and Loding Picture ...(0/1)
o(^-^)o
fansfb6041c7
lvl.2

Portugal
Offline

Hi, can someone help to understand if it is something wrong with the log file?
When i press record the camera just reboots.
i tried everything i saw on foruns and from dji support and nothing.
i started after firmware upgrade


      0 IST8303[2:0x18]:Init...
  
      0 IST8303[2:0x18]:set mode failed
  
      0 ist83xx:0 ret:-14
  
      0 IST8303[2:0x1e]:Init...
  
      0 IST8303[2:0x1e]:set mode failed
  
      0 ist83xx:1 ret:-14
  
      0 [BAT]read barcode data success num:1
  
      0 [BAT]read begin:12211232               end:12345678
  
      0 [BAT]barcode[0]:6171152308289
  
      0 eeprom load  0    0   22   32
  
      0 eeprom load  1   32   28   32
  
      0 eeprom load  2   64   34   40
  
      0 eeprom load  3  104   20   24
  
      0 eeprom load  4  128  132  136
  
      0 eeprom load  5  264  128  136
  
      0 eeprom load  6  400   12   16
  
      0 eeprom load  7  416   40   48
  
      0 eeprom load  8  464    9   16
  
      0 eeprom load  9  480    1    8
  
      0 eeprom load 10  488    6   16
  
      0 eeprom load 11  504    4    8
  
      0 eeprom load 12  512   52   56
  
      0 eeprom load 13  568    8   16
  
      0 eeprom load 14  584    7   16
  
      0 eeprom load 15  600   12   16
  
      0 eeprom load 16  616   38   48
  
      0 eeprom load 17  664   12   16
  
      0 eeprom load 18  680   56   64
  
      0 eeprom load 19  744   32   40
  
      0 eeprom load 20  784    1    8
  
      0 eeprom load 21  792   16   24
  
      0 eeprom load 22  816   16   24
  
      0 eeprom load 23  840    1    8
  
      0 eeprom load 24  848    1    8
  
      0 eeprom load 25  856   10   16
  
      0 eeprom load 26  872   36   40
  
      0 eeprom load 27  912   52   56
  
      0 eeprom load 28  968   44   48
  
      0 eeprom load 29 1016   28   32
  
      0 eeprom load 30 1048   18   24
  
      0 eeprom load 31 1072   16   24
  
      0 eeprom load 32 1096   72   80
  
      0 eeprom load 33 1176   24   32
  
      0 eeprom load 34 1208   64   72
  
      0 eeprom load 35 1280   24   32
  
      0 eeprom load 36 1312   96  104
  
      0 mis cali 55 55 103a fff0 cnt:0
  
      0 imu status:0
  
      0 [hardfault]:******************check fault info and trace ************
  
      0 [hardfault]:-----fault is null: addr(0x40024000),flag(0xea63ac40)-----
  
[            0] => fix_send_index[11]_0
  
[            0] => fix_send_index[12]_0
  
[            0] => fix_send_index[13]_0
  
[            0] => fix_send_index[14]_0
  
[            0] => fix_send_index[15]_0
  
[            0] => fix_send_index[16]_0
  
[            0] => fix_send_index[17]_0
  
[            0] => fix_send_index[18]_0
  
[            0] => fix_send_index[19]_0
  
[            0] => fix_send_index[20]_0
  
[            0] => fix_send_index[21]_0
  
[            0] => fix_send_index[22]_0
  
[            0] => fix_send_index[23]_0
  
[            0] => fix_send_index[24]_0
  
[            0] => fix_send_index[25]_0
  
[            0] => fix_send_index[26]_0
  
[            0] => fix_send_index[27]_0
  
Get Alarm Class2: 10% 1
  
[            0] => fix_send_index[28]_0
  
[            0] => fix_send_index[29]_0
  
Get Alarm Class1: 30% 0
  
[            0] => fix_send_index[30]_0
  
[            0] => fix_send_index[31]_0
  
[            0] => fix_send_index[32]_0
  
[            0] => fix_send_index[33]_0
  
[            0] => fix_send_index[34]_0
  
[            0] => fix_send_index[35]_0
  
[            0] => fix_send_index[36]_0
  
[            0] => fix_send_index[37]_0
  
[            0] => fix_send_index[38]_0
  
[            0] => fix_send_index[39]_0
  
     42 ESC0 link up
  
  
[            0] => fix_send_index[40]_0
  
     43 ESC1 link up
  
  
     43 ESC2 link up
  
  
[            0] => fix_send_index[41]_0
  
     44 ESC3 link up
  
  
     44 esc alive info = 0xf
  
  
[            0] => fix_send_index[42]_0
  
[            0] => fix_send_index[43]_0
  
[            0] => fix_send_index[44]_0
  
[            0] => fix_send_index[45]_0
  
[            0] => fix_send_index[46]_0
  
[            0] => fix_send_index[47]_0
  
[            1] => fix_send[0].send_frequency_0
  
[            0] => fix_send[0].send_start_index_0
  
[            0] => fix_send[0].send_size_0
  
[            0] => fix_send[1].send_frequency_0
  
[            0] => fix_send[1].send_start_index_0
  
[            0] => fix_send[1].send_size_0
  
     92 Firmware = [V01.10.00.00]
  
  
[            0] => g_config.aircraft.custom_mix[0][0]_0
  
     93 ESC2 version: Protocol = [V1.0] Hardware = "WM320_FOC_V4"
  
     93 Loader   = [V00.00.01.01]
  
     93 Firmware = [V01.10.00.00]
  
  
     93 ESC3 version: Protocol = [V1.0] Hardware = "WM320_FOC_V4"
  
     93 Loader   = [V00.00.01.01]
  
     93 Firmware = [V01.10.00.00]
  
  
[            0] => g_config.aircraft.custom_mix[0][1]_0
  
[            0] => g_config.aircraft.custom_mix[0][2]_0
  
[            0] => g_config.aircraft.custom_mix[0][3]_0
  
[            0] => g_config.aircraft.custom_mix[1][0]_0
  
[            0] => g_config.aircraft.custom_mix[1][1]_0
  
[            0] => g_config.aircraft.custom_mix[1][2]_0
  
[            0] => g_config.aircraft.custom_mix[1][3]_0
  
[            0] => g_config.aircraft.custom_mix[2][0]_0
  
    101 [FDI AHRS[1]]:ahrs_init begin
  
[            0] => g_config.aircraft.custom_mix[2][1]_0
  
    102 [FDI AHRS[1]]:bias fdi turn on
  
    102 [FDI AHRS[1]]:init fdi turn on
  
    102 [FDI AHRS[1]]:wait for sensor check
  
[            0] => g_config.aircraft.custom_mix[2][2]_0
  
[            0] => g_config.aircraft.custom_mix[2][3]_0
  
[            0] => g_config.aircraft.custom_mix[3][0]_0
  
[            0] => g_config.aircraft.custom_mix[3][1]_0
  
[            0] => g_config.aircraft.custom_mix[3][2]_0
  
[            0] => g_config.aircraft.custom_mix[3][3]_0
  
[            0] => g_config.aircraft.custom_mix[4][0]_0
  
[            0] => g_config.aircraft.custom_mix[4][1]_0
  
    111 [LED] changed: temperature not ready when startup
  
[            0] => g_config.aircraft.custom_mix[4][2]_0
  
    111 Battery barcode:6171152922595
  
[            0] => g_config.aircraft.custom_mix[4][3]_0
  
    112 Battery barcode:6171152922595
  
[            0] => g_config.aircraft.custom_mix[5][0]_0
  
    113 Battery barcode:6171152922595
  
[            0] => g_config.aircraft.custom_mix[5][1]_0
  
[            0] => g_config.aircraft.custom_mix[5][2]_0
  
[            0] => g_config.aircraft.custom_mix[5][3]_0
  
[            0] => g_config.aircraft.custom_mix[6][0]_0
  
[            0] => g_config.aircraft.custom_mix[6][1]_0
  
[            0] => g_config.aircraft.custom_mix[6][2]_0
  
[            0] => g_config.aircraft.custom_mix[6][3]_0
  
[            0] => g_config.aircraft.custom_mix[7][0]_0
  
[            0] => g_config.aircraft.custom_mix[7][1]_0
  
[            0] => g_config.aircraft.custom_mix[7][2]_0
  
[            0] => g_config.aircraft.custom_mix[7][3]_0
  
[            8] => g_config.aircraft.custom_num_of_motor_0
  
[           15] => g_config.imu_gps.imu_offset_x_0
  
[            0] => g_config.imu_gps.imu_offset_y_0

2016-11-21
Use props
DJI Mindy
Administrator
Flight distance : 7 ft
Offline

Could you please clarify which Phantom model you have?
Please try to update the firmware again.
Please let me know if this helps.
2016-11-21
Use props
fansfb6041c7
lvl.2

Portugal
Offline

DJI Mindy Posted at 2016-11-22 10:37
Could you please clarify which Phantom model you have?
Please try to update the firmware again.
Plea ...

Phantom 3 Pro.
I updated the firmaware for the last version, and it started this malfunction.
if i try to install it says abort: the version i try to install is the same

Everything ok until i press record, the camera just fails.
easier to see:


live throuhg facebook no problem
view in iphone without rec, no problem.

i already tried to downgrade and upgrade again, problem continues.
open it and took out every single cable, checked them, plugged them again and nothing.
Format SD, new SD, other new SD, nothing.

I work Africa, so i cant receive a new one sended by you, and i need it to work.
I really need your help.
2016-11-22
Use props
DJI Mindy
Administrator
Flight distance : 7 ft
Offline

fansfb6041c7 Posted at 2016-11-22 18:37
Phantom 3 Pro.
I updated the firmaware for the last version, and it started this malfunction.
if  ...

Sorry, it's probably a hardware issue.
I'd suggest you to send it in for fixing.
Please send an e-mail to support@dji.com with the following info, the subject should be " Forum support" . We'll help you create a case.
Case illustration:
Country:
Full name:
Email address:
Phone number:
Shipping Address:
Zip Code:
Forum link for your case:
2016-11-22
Use props
fansfb6041c7
lvl.2

Portugal
Offline

DJI Mindy Posted at 2016-11-22 18:51
Sorry, it's probably a hardware issue.
I'd suggest you to send it in for fixing.
Please send an e- ...

i am actually in Africa, and u dont pick up there.

its too much coincidence hardware issue exctly when i update firmware
2016-11-22
Use props
digdat
Second Officer
Flight distance : 11896378 ft
United States
Offline

Is the firmware BIN file still on the SD card? If so, try deleting it from the SD card and try again.

have you tried to format the SD card first? Or, tried a different SD card?

Does it do the same thing if you try and take a picture/photo?

Have you tried turning down the resolution / frame rate to see if it helps?

If none of this works, i'd remove the app, reboot device and re-download/install it. If that doesn't fix, I would try and reverting back to the earlier version of the firmware. Possibly something didn't "take" when you upgraded. I'd also check all of the cables/ribbons on the camera and ensure that they are firmly plugged in. Shouldn't be this, but could be.

Keep us posted! (you may also get better troubleshooting over at phantompilots.com forums)
2016-11-22
Use props
fansfb6041c7
lvl.2

Portugal
Offline

digdat Posted at 2016-11-23 05:20
Is the firmware BIN file still on the SD card? If so, try deleting it from the SD card and try again ...

i tried all of that and lots more, and it is the same. on that forun no solution worked as well until now
2016-11-28
Use props
Daroga
Captain
Flight distance : 3517287 ft
  • >>>
United States
Offline

fansfb6041c7 Posted at 2016-11-28 06:52
i tried all of that and lots more, and it is the same. on that forun no solution worked as well un ...

fansfb6041c7 (Albano),

There's nothing notable in the log message file you posted in your original post. However, since the issue began after a firmware upgrade, we need to check the detailed firmware upgrade log to see if all components were successfully upgraded, including the camera modules and the Air End USB. Do you perhaps still have the SD Card that you performed your last upgrade with?

There's a text file summary called P3X_FW_RESULT_AB.txt left on the SD Card after an update. There's also a detailed component upgrade summary that's written to a hidden MISC/LOG folder on the SD Card.

If you still have the upgrade SD Card, the procedure to get to to the detailed summary is to take the SD Card to a MAC or Windows computer and "show hidden files and folders".
Just in case, here's links to a MAC Howto tutorial and a Windows Howto turorial. Navigate into MISC/LOG and open the P3X_FW_LOG_AB.txt file. The log is sequential, so your last upgrade will be at the end of the log file. The camera is component [01 00] and [01 01]; the Air End USB is component [08 00]. Please post the upgrade portion of this file showing all component numbers and upgrade versions....

Regardless of the previous upgrade, there are two possible actions that you can try -> 1) force a reinstallation of the current firmware; or 2) downgrade to the previous version of firmware.

1) To force a reinstallation of the current firmware, you format a clean SD Card and place the downloaded BIN file on the root of the SD Card. With everything powered off, you press and hold the P3 Pro LINK button on the side of the VPS module and while pressing the button, you power on the P3.  This video from Sploodge provided in this thread shows the procedure:

After the reinstallation, immediately check the detailed log for success and post the results here.

2) You could alternately try to downgrade to the previous firmware that was previously working. The P3 will allow you to downgrade to one previous version of firmware. Format a clean SD Card and place the previous firmware BIN file on the root of the card. Insert the SD Card into the camera with everything powered down. Power on the P3 and wait for the downgrade to finish. Immediately check the detailed summary file and post the results here...

Good luck and always fly safely....




2016-11-28
Use props
fansfb6041c7
lvl.2

Portugal
Offline

Daroga Posted at 2016-11-28 23:07
fansfb6041c7 (Albano),

There's nothing notable in the log message file you posted in your original ...

HI. thank you very much for your support. I tried that as well.

[00012850]Delete history success.

[00013106]========== remo-con disconnect. boot(0) ============
[00013179]Packet [C:\P3X_FW_V01.08.0080.bin] detected, card sn [0x0013a241].
[00013263]Packet upgrade start...

[00013344]Packet checking...
[00013416]Packet vlink 01.08.0080 <-> 01.07.0060.
[00013495]Record vlink 01.09.0060 <-> 01.08.0080 (flow = 1).
[00013566]Done.

[00013645]Version checking[1]...
[00013762][03 05][00] v34.2.0.9 -> v34.2.0.9
[00013877][03 06][00] v2.4.20.18 -> v2.4.14.5 need upgrade.
[00013964][04 00][00] v1.44.0.0 -> v1.44.0.0
[00014119][11 00][00] v1.8.0.0 -> v1.7.15.1
[00014246][12 00][00] v1.10.0.0 -> v1.10.0.0
[00014366][12 01][00] v1.10.0.0 -> v1.10.0.0
[00014518][12 02][00] v1.10.0.0 -> v1.10.0.0
[00014651][12 03][00] v1.10.0.0 -> v1.10.0.0
[00014826][15 00][00] v1.1.2.0 -> v1.1.2.0
[00014947][17 00][00] v1.1.1.7 -> v1.1.1.7
[00015111][17 01][00] v1.0.2.7 -> v1.0.2.7
[00015198][19 00][00] v1.0.8.96 -> v1.0.8.96
[00015277][01 00][00] v1.30.5036 -> v1.30.5036
[00015352][01 01][00] v1.30.5036 -> v1.30.5036
[00015457][08 00][00] v0.13.0.7 -> v0.13.0.7
[00015556][09 00][00] v3.0.0.10 -> v3.0.0.10
[00015633]Done.

[00017705]Waiting for user confirm...
[00027781]Timeout, start upgrade automatically.

[00027923]Firmware upgrading[1]...
[00028176][03 06] Firmware upgrade start...
[00361239][03 06] Firmware upgrade finished successfully.
[00361314]Done.

[00361387]Version checking[2]...
[00361511][03 05][00] v34.2.0.9 -> v34.2.0.9
[00361611][03 06][05] v2.4.14.5 -> v2.4.14.5
[00361695][04 00][00] v1.44.0.0 -> v1.44.0.0
[00361851][11 00][00] v1.8.0.0 -> v1.7.15.1
[00361964][12 00][00] v1.10.0.0 -> v1.10.0.0
[00362091][12 01][00] v1.10.0.0 -> v1.10.0.0
[00362200][12 02][00] v1.10.0.0 -> v1.10.0.0
[00362352][12 03][00] v1.10.0.0 -> v1.10.0.0
[00362543][15 00][00] v1.1.2.0 -> v1.1.2.0
[00362674][17 00][00] v1.1.1.7 -> v1.1.1.7
[00362815][17 01][00] v1.0.2.7 -> v1.0.2.7
[00362920][19 00][00] v1.0.8.96 -> v1.0.8.96
[00363076][01 00][00] v1.30.5036 -> v1.30.5036
[00363153][01 01][00] v1.30.5036 -> v1.30.5036
[00363266][08 00][00] v0.13.0.7 -> v0.13.0.7
[00363361][09 00][00] v3.0.0.10 -> v3.0.0.10
[00363435]Packet upgrade finish successfully.


[00343132]========== 2016.11.22 23:49:22. boot(15) ============
[00343205]Packet [C:\P3X_FW_V01.09.0060.bin] detected, card sn [0x50ce4cf4].
[00343365]Packet upgrade start...

[00343456]Packet checking...
[00343531]Packet vlink 01.09.0060 <-> 01.08.0080.
[00343608]Record vlink 01.09.0060 <-> 01.08.0080 (flow = 0).
[00343685]Done.

[00343761]Version checking[1]...
[00343873][03 05][00] v34.2.0.9 -> v34.2.0.9
[00343993][03 06][00] v2.4.20.18 -> v2.4.20.18
[00344078][04 00][00] v1.44.0.0 -> v1.44.0.0
[00344512][11 00][00] v1.8.0.0 -> v1.8.0.0
[00344672][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.
[00344744][11 01][00] v1.8.0.0 -> v2.0.0.33
[00344881][12 00][00] v1.10.0.0 -> v1.10.0.0
[00345001][12 01][00] v1.10.0.0 -> v1.10.0.0
[00345134][12 02][00] v1.10.0.0 -> v1.10.0.0
[00345263][12 03][00] v1.10.0.0 -> v1.10.0.0
[00345459][15 00][00] v1.1.2.0 -> v1.1.2.0
[00345578][17 00][00] v1.1.1.7 -> v1.1.1.7
[00345763][17 01][00] v1.0.2.7 -> v1.0.2.7
[00345871][19 00][00] v1.0.8.96 -> v1.0.8.96
rd sn [0x50ce4cf4].
[00012870]Packet upgrade st [00012803]========== 2016.11.22 23:49:44. boot(0) ============
[00012880]Packet [C:\P3X_FW_V01.09.0060.bin] detected, card sn [0x50ce4cf4].
[00012959]Packet upgrade start...

[00013037]Packet checking...
[00013116]Packet vlink 01.09.0060 <-> 01.08.0080.
[00013188]Record vlink 01.09.0060 <-> 01.08.0080 (flow = 0).
[00013269]Done.

[00013345]Version checking[1]...
[00013461][03 05][00] v34.2.0.9 -> v34.2.0.9
[00013556][03 06][00] v2.4.20.18 -> v2.4.20.18
[00013645][04 00][00] v1.44.0.0 -> v1.44.0.0
[00013798][11 00][00] v1.8.0.0 -> v1.8.0.0
[00013958][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.
[00014032][11 01][00] v1.8.0.0 -> v2.0.0.33
[00014172][12 00][00] v1.10.0.0 -> v1.10.0.0
[00014332][12 01][00] v1.10.0.0 -> v1.10.0.0
[00014472][12 02][00] v1.10.0.0 -> v1.10.0.0
[00014607][12 03][00] v1.10.0.0 -> v1.10.0.0
[00014783][15 00][00] v1.1.2.0 -> v1.1.2.0
[00014908][17 00][00] v1.1.1.7 -> v1.1.1.7
[00015095][17 01][00] v1.0.2.7 -> v1.0.2.7
[00015193][19 00][00] v1.0.8.96 -> v1.0.8.96
[00015382][01 00][00] v1.30.5036 -> v1.30.5036
[00015464][01 01][00] v1.30.5036 -> v1.30.5036
[00015551][08 00][00] v0.13.0.7 -> v0.13.0.7
[00015657][09 00][00] v3.0.0.10 -> v3.0.0.10
[00015732]Packet upgrade cancelled at version checking.
2016-11-28
Use props
fansfb6041c7
lvl.2

Portugal
Offline

Daroga Posted at 2016-11-28 23:07
fansfb6041c7 (Albano),

There's nothing notable in the log message file you posted in your original ...

It seems that there is some kind of problem here:

[00344672][11 01][00] v1.8.0.0 -> v2.0.0.33, firmware v1.8.0.0 not support.
2016-11-28
Use props
Daroga
Captain
Flight distance : 3517287 ft
  • >>>
United States
Offline

fansfb6041c7 Posted at 2016-11-28 18:50
It seems that there is some kind of problem here:

[00344672][11 01][00] v1.8.0.0 -> v2.0.0.33, f ...

No, your upgrade is good.

Component [11 00] is the battery. Some of the newer batteries have a SmartBatery sub-component that is [11 01]. Your battery doesn't have or need the [11 01] firmware. So you're good with the upgrade. If the GO App continues to reboot, then you might try uninstalling and reinstalling the GO App. Also check your cable and its connection.
2016-11-28
Use props
fansfb6041c7
lvl.2

Portugal
Offline

Daroga Posted at 2016-11-29 09:38
No, your upgrade is good.

Component [11 00] is the battery. Some of the newer batteries have a S ...

It is not the go app that fails, if i do not connect the phone, when press record on the remote, the camera reboots as well.

i already changed cables, and it continues.

THANKS GOD DJI already shipped new one, bcause i cant wait more. I will send this one for repair and wait for an answer
2016-11-29
Use props
fansfb6041c7
lvl.2

Portugal
Offline

Daroga Posted at 2016-11-29 09:38
No, your upgrade is good.

Component [11 00] is the battery. Some of the newer batteries have a S ...

Daroga, u understand this things more than the average, are u from DJI?
2016-11-29
Use props
Daroga
Captain
Flight distance : 3517287 ft
  • >>>
United States
Offline

fansfb6041c7 Posted at 2016-11-29 04:30
Daroga, u understand this things more than the average, are u from DJI?

No, thank DJI-Mindy for solving your issue! Sometimes,only DJI support can make things right. Glad you're on track to get working again!
Good luck and always fly safely..
2016-11-29
Use props
scottyduzitbest
lvl.1

United States
Offline

weve seen gimbal main boards fail during update of firmware due to overheating on p3p, temps reaching 109f. your gimbal has most liklely failed and needs replacing
2016-11-29
Use props
Advanced
You need to log in before you can reply Login | Register now

Credit Rules