Fixing flash in DM365 chip within Ph3 Pro gimbal

Joined
Jun 30, 2016
Messages
1,507
Reaction score
679
Location
PL
Here is a success story I wanted to share.

I had a Phantom 3 Pro gimbal which didn't allowed me to see the FPV feed. Photos and movies were recorded on sd-card, there was just no live video - only grey background - in Dji Go.

I explained the details, and the road to fixing the issue, here:
 
Last edited:
Time for a final act of the story.

The wiki was recently updated with downloads of all firmware partitions for the Gimbal Top board:
Flashing firmware on DaVinci media processors · mefistotelis/phantom-firmware-tools Wiki · GitHub

Based on that, I was able to fix my board. Details:
 
Last edited:
Hopefully I also helped other people who might want to try their luck at repair.

If the repair would have failed, I'd probably modify the board to demote it from Ph3 Pro to Ph3 Advanced - it looks like this only requires moving a few resistors, plus updating the software within Ambarella.
 
  • Like
Reactions: Bad Andy
Hopefully I also helped other people who might want to try their luck at repair.

If the repair would have failed, I'd probably modify the board to demote it from Ph3 Pro to Ph3 Advanced - it looks like this only requires moving a few resistors, plus updating the software within Ambarella.
How to do that
 
Hopefully I also helped other people who might want to try their luck at repair.

If the repair would have failed, I'd probably modify the board to demote it from Ph3 Pro to Ph3 Advanced - it looks like this only requires moving a few resistors, plus updating the software within Ambarella.
I have been done that way ,but the video delay and the frame is lower as previous,how to solve this problem
 
How to do that [modify from Ph3 Pro to Ph3 Advanced]
Look at schematics:
dji-hardware-schematics/phantom_3_pro_gimbal_top_board at master · mefistotelis/dji-hardware-schematics · GitHub

Just use KiCad, not PDFs - PDFs are often outdated there.

I have been done that way ,but the video delay and the frame is lower as previous,how to solve this problem

Details. What you did, what are you using, where are you testing, what tests you did, what is the issue.
 
I wanna ask, after replace nand flash live feed was laggy? Like only 8fps

No. No issues.

For laggy live feed, I would blame either radio link or mobile device. It is unlikely that such issue originates at compression.
 
No. No issues.

For laggy live feed, I would blame either radio link or mobile device. It is unlikely that such issue originates at compression.
Code:
FPGA[190,100,1,0]-1.000000:19000000
hdmi status is 1
ARM Load: 18% Video fps: 8 fps Video bit rate: 1315 kbps PHY Bandwidth: 19000 kbps Time: 00:00:59 Resolution: 1280x720
Looks like DaVinci receive 8fps video from Ambarella. Why? This happened when replace Dm365 nand. The same happen when replace dm365 nand's between working units
 
Looks like DaVinci receive 8fps video from Ambarella. Why? This happened when replace Dm365 nand. The same happen when replace dm365 nand's between working units

Interesting. I will try to take a look at Ambarella when I'm able. Since we don't have any technical documentation of the chip, I don't know too much about it. I have no idea how this could have happened by change in software.
 
@quaddamage
I'm attempting to repair the boot image on a p3pro top gimbal board as well. Your coverage of this and narrative has been helpful.

I get this response from the 368_u0 serial pins when booting up (below).
However, I am having trouble getting it into Boot flashing mode, aka to return "BOOT ME," so I can send it the proper boot images via Texas Instrument's flashing utilitity...


I've tried tying:

  • BT01 to 3.3VD
  • BT00 to 3.3VD
  • Boot0 to 3.3VD
  • BT01 and BT00 to 3.3VD
  • etc...
to no avail... Thoughts?

Code:
DM36x initialization passed!
UBL Product Vesion : DJI-NOHDMI-WM610-UBL-1.0-rc0(2015-01-13)
Dji UBL Version: 1.51(Jan 13 2015 - 16:42:11)
Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000019.
Valid magicnum, 0xA1ACED66, found in block 0x0000001D.
No valid boot image found!
NAND Boot failed.
Aborting...
 
Check with multimeter whether the wires you soldered really provide 3.3V to the BT00/BT01 pins.

If they do, and the chip doesn't enter the boot mode - that would probably mean that the pins are not connected to the chip.
 
I’m impressed with the work quaddamage did. Congrats.
 
@quaddamage
Thanks for the tip. I checked that both bt00 and bt01 we're getting 3.3v and they were... Darn, guess thateans the pads aren't connected to the pins!

One last follow up: for the serial connection, I should be on the 368_u0_tx/rx pins correct?
 

Recent Posts

Members online

Forum statistics

Threads
143,066
Messages
1,467,357
Members
104,935
Latest member
Pauos31