No image transmission signal - P3P

I just wonder if anyone who re flash their gimbal has made a instructional video for it?
I'm about to do mine, It would be nice to get a walk-trough video made by the pro.
Thanks
 
I have a ton of bad P3P and Advanced boards that are fried. I wish there was someone who repaired them. I think reflashing them on my own mat be over my head.
 
This "update" problem keeps cropping up. My P3A is still on Firmware 1.3.20+ because I'm afraid to do an update.
If it works, don't fix it has become my motto but I am missing out on some of the advanced features!
 
This "update" problem keeps cropping up. My P3A is still on Firmware 1.3.20+ because I'm afraid to do an update.
If it works, don't fix it has become my motto but I am missing out on some of the advanced features!

Stay on that FW. The extra features are peanuts with more restrictions(of course with a reason like geofencing).
I even think, correct me if i’m wrong, P3A has even better performance with yr FW.
 
Stay on that FW. The extra features are peanuts with more restrictions(of course with a reason like geofencing).
I even think, correct me if i’m wrong, P3A has even better performance with yr FW.

I am rapidly coming to that conclusion! What does an 80yo need "follow me" for, bloody drone would get bored but I would like the POI (circle round something)!
 
Ah yes, but Litchi costs MONEY and I ain't got a lot of spare for what is basically a toy :D
 
Hello There
I have the message ubl1.img not found ???
I tried two laptop it's weird
Sometime I got this too >>
Target: Starting UART Boot...
Target: BOOTUBL
any ID??
Thanks
 

Attachments

  • ubl1.JPG
    ubl1.JPG
    55.4 KB · Views: 318
  • BOOTUBL.JPG
    BOOTUBL.JPG
    36.6 KB · Views: 301
  • BOOTME.JPG
    BOOTME.JPG
    62.3 KB · Views: 221
Last edited:
Is there is an alternative to #6 - RXP to TX FTDI for a connection spot?

There are no redundant test pads on the board. If you've lost the pad - skilled technicians can connect wire even to remains of a via or copper path.
 
There are no redundant test pads on the board. If you've lost the pad - skilled technicians can connect wire even to remains of a via or copper path.

Thanks.... that is way above my head as I lost the pad :(.
I will ask a skilled technicians to see if it can be done near me.

I don't even know if I can still flash the nand as "3 post above" I'm getting ubl1.img not found or BOOTUBL boot loop. What do you think, is it worst a shot to even repair the pad?

I put the gimbal as is on the P3P and it flew all right, took pic and video all right. still no live feed.
 
Hello @quaddamage
I had a technician rewire the defective RX pad and re solder all the wires.
I tried to re-flash the nand chip as directed as the ph3pns zip file
And this time It did flash successfully... :)
Thanks a lot for all the help given from you guys with @SunsetCatcher
and all the others as well that contribute Thumb UP...

Now I just need to put the gimbal together and test live feed.

edit:
Live feed test successful.

No help a all from DJI support to resolve this...

But this forum rock really. Thanks all for all the success story


Code:
-----------------------------------------------------
   TI Serial Flasher Host Program for DM36x
   (C) 2009, Texas Instruments, Inc.
   Ver. 1.50
-----------------------------------------------------


Flashing NAND with ubl1.img and u-boot.img.


Attempting to connect to device COM17...
Press any key to end this program at any time.


Waiting for the DM36x...
        Target:  BOOTME
BOOTME commmand received. Returning ACK and header...
ACK command sent. Waiting for BEGIN command...
        Target:   BEGIN
BEGIN commmand received. Sending CRC table...
100% [                                                              ]
                           CRC table sent....



Waiting for DONE...
        Target:    DONE
DONE received.  Sending the UBL...
100% [                                                              ]
                              UBL sent....


        Target:    DONE
DONE received.  UBL was accepted.
UBL transmitted successfully.


Waiting for SFT on the DM36x...
        Target: Starting UART Boot...
        Target: BOOTUBL
BOOTUBL commmand received. Returning CMD and command...
CMD value sent.  Waiting for DONE...
        Target:    DONE
DONE received. Command was accepted.
Sending the UBL image
Waiting for SENDIMG sequence...
        Target: SENDIMG
SENDIMG received. Returning ACK and header for image data...
ACK command sent. Waiting for BEGIN command...
        Target:   BEGIN
BEGIN commmand received.
100% [                                                              ]
                           Image data sent...


Waiting for DONE...
        Target:    DONE
DONE received.  All bytes of image data received...
        Target: Writing UBL to NAND flash
        Target: Unprotecting blocks 0x00000001 through 0x00000018.
        Target: Number of blocks needed for header and data: 0x0x00000001
        Target: Attempting to start in block number 0x0x00000001.
        Target: Erasing block 0x00000001 through 0x00000001.
        Target: Writing header and image data to Block 0x00000001, Page 0x000000
00
        Target: Erasing block 0x00000002 through 0x00000002.
        Target: Writing header and image data to Block 0x00000002, Page 0x000000
00
        Target: Erasing block 0x00000003 through 0x00000003.
        Target: Writing header and image data to Block 0x00000003, Page 0x000000
00
        Target: Erasing block 0x00000004 through 0x00000004.
        Target: Writing header and image data to Block 0x00000004, Page 0x000000
00
        Target: Erasing block 0x00000005 through 0x00000005.
        Target: Writing header and image data to Block 0x00000005, Page 0x000000
00
        Target: Erasing block 0x00000006 through 0x00000006.
        Target: Writing header and image data to Block 0x00000006, Page 0x000000
00
        Target: Erasing block 0x00000007 through 0x00000007.
        Target: Writing header and image data to Block 0x00000007, Page 0x000000
00
        Target: Erasing block 0x00000008 through 0x00000008.
        Target: Writing header and image data to Block 0x00000008, Page 0x000000
00
        Target: Erasing block 0x00000009 through 0x00000009.
        Target: Writing header and image data to Block 0x00000009, Page 0x000000
00
        Target: Erasing block 0x0000000A through 0x0000000A.
        Target: Writing header and image data to Block 0x0000000A, Page 0x000000
00
        Target: Erasing block 0x0000000B through 0x0000000B.
        Target: Writing header and image data to Block 0x0000000B, Page 0x000000
00
        Target: Erasing block 0x0000000C through 0x0000000C.
        Target: Writing header and image data to Block 0x0000000C, Page 0x000000
00
        Target: Erasing block 0x0000000D through 0x0000000D.
        Target: Writing header and image data to Block 0x0000000D, Page 0x000000
00
        Target: Erasing block 0x0000000E through 0x0000000E.
        Target: Writing header and image data to Block 0x0000000E, Page 0x000000
00
        Target: Erasing block 0x0000000F through 0x0000000F.
        Target: Writing header and image data to Block 0x0000000F, Page 0x000000
00
        Target: Erasing block 0x00000010 through 0x00000010.
        Target: Writing header and image data to Block 0x00000010, Page 0x000000
00
        Target: Erasing block 0x00000011 through 0x00000011.
        Target: Writing header and image data to Block 0x00000011, Page 0x000000
00
        Target: Erasing block 0x00000012 through 0x00000012.
        Target: Writing header and image data to Block 0x00000012, Page 0x000000
00
        Target: Erasing block 0x00000013 through 0x00000013.
        Target: Writing header and image data to Block 0x00000013, Page 0x000000
00
        Target: Erasing block 0x00000014 through 0x00000014.
        Target: Writing header and image data to Block 0x00000014, Page 0x000000
00
        Target: Erasing block 0x00000015 through 0x00000015.
        Target: Writing header and image data to Block 0x00000015, Page 0x000000
00
        Target: Erasing block 0x00000016 through 0x00000016.
        Target: Writing header and image data to Block 0x00000016, Page 0x000000
00
        Target: Erasing block 0x00000017 through 0x00000017.
        Target: Writing header and image data to Block 0x00000017, Page 0x000000
00
        Target: Erasing block 0x00000018 through 0x00000018.
        Target: Writing header and image data to Block 0x00000018, Page 0x000000
00
        Target: Protecting the entire NAND flash.
        Target:    DONE
Sending the Application image
Waiting for SENDIMG sequence...
        Target: SENDIMG
SENDIMG received. Returning ACK and header for image data...
ACK command sent. Waiting for BEGIN command...
        Target:   BEGIN
BEGIN commmand received.
100% [                                                              ]
                           Image data sent...


Waiting for DONE...
        Target:    DONE
DONE received.  All bytes of image data received...
        Target: Writing APP to NAND flash
        Target: Unprotecting blocks 0x00000019 through 0x00000032.
        Target: Number of blocks needed for header and data: 0x0x00000003
        Target: Attempting to start in block number 0x0x00000019.
        Target: Erasing block 0x00000019 through 0x0000001B.
        Target: Writing header and image data to Block 0x00000019, Page 0x000000
00
        Target: Erasing block 0x0000001C through 0x0000001E.
        Target: Writing header and image data to Block 0x0000001C, Page 0x000000
00
        Target: Erasing block 0x0000001F through 0x00000021.
        Target: Writing header and image data to Block 0x0000001F, Page 0x000000
00
        Target: Erasing block 0x00000022 through 0x00000024.
        Target: Writing header and image data to Block 0x00000022, Page 0x000000
00
        Target: Erasing block 0x00000025 through 0x00000027.
        Target: Writing header and image data to Block 0x00000025, Page 0x000000
00
        Target: Erasing block 0x00000028 through 0x0000002A.
        Target: Writing header and image data to Block 0x00000028, Page 0x000000
00
        Target: Erasing block 0x0000002B through 0x0000002D.
        Target: Writing header and image data to Block 0x0000002B, Page 0x000000
00
        Target: Erasing block 0x0000002E through 0x00000030.
        Target: Writing header and image data to Block 0x0000002E, Page 0x000000
00
        Target: Protecting the entire NAND flash.
        Target:    DONE
        Target:    DONE

Operation completed successfully.

C:\ph3pns>
.
 
Last edited:
It is obvious this issue will drive us nuts until we can find an electronics geek, (I love them guys and gals and wish I was one), who can tell us what electronic SMD, (surface mount device), controls video, on the main circuit board. I have been repairing these P3Pro/A cams ever since they came out and have at least 2 dozen main boards marked, good giimbal, No Video. I just had one sent in today that had been in storage for "months" and the video quit working. The rest of the camera is perfect, all app functions work, but has a black screen.

I have come across a few "Pilots" who seem to have a deeper knowledge of the electronics, so my call goes out to any of you to drop us a post. Maybe we can figure out a way to out fox DJI and restore our video feed on our, otherwise, perfect cameras.

Cheers,
Jim
Jim, do you repair these for people, if so can you send me information regarding contacting you for shipping and repair cost.
Thanks,
Shawn
 
Jim, do you repair these for people, if so can you send me information regarding contacting you for shipping and repair cost.
Thanks,
Shawn


I just responded to your other post and now see the extensive work xjmdrone has done. Have you attempted to reflash the NAN chip? If you have been successful with this procedure, are you interested in doing some more? Like I mentioned, I have several dozen boards that have no video.

Cheers,
Jim
 
I just responded to your other post and now see the extensive work xjmdrone has done. Have you attempted to reflash the NAN chip? If you have been successful with this procedure, are you interested in doing some more? Like I mentioned, I have several dozen boards that have no video.

Cheers,
Jim
I'm in the process of flashing the chip, my cousin is really good at stuff like that. So hopefully we can get mine up and going, if we manage to get it fixed we may be interested in doing it, I'll check with him and see what he thinks.
 

Members online

No members online now.

Forum statistics

Threads
143,066
Messages
1,467,355
Members
104,934
Latest member
jody.paugh@fullerandsons.