lightbridge firmware PROBLEM (and solution) - firmware version not found by dji assistant tool

[gaucho]

i also do ，each pin i have been test

Which 3V3 pin did you shorted it with?
What is the voltage found on the 3V3 identified pin?

 

[andrew_by]

when bt00 bt01 connect 3.3 ，the xterminal not post message

Use B_S pin to 3.3V and board will flashed .
do not use bt00 bt01 , they fron another proccesor

 

[andrew_by]

sfh_DM36x.exe -nandflash -v -p "COM8" dm6467_297_ubl.img u-boot_modifiedByGaucho.img

bin in this script is not good to do it but then nothing in either boot

i flashe same module few minutes ago. all work normally.

 

[2008jiayu]

Use B_S pin to 3.3V and board will flashed .
do not use bt00 bt01 , they fron another proccesor

could you send me the ubl and uboot for phatom 3 pro

 

[2008jiayu]

i flashe same module few minutes ago. all work normally.

you are our god

 

[2008jiayu]

i flashe same module few minutes ago. all work normally.

if you unpack software forphatom 3 pro

 

[2008jiayu]

i flashe same module few minutes ago. all work normally.

where can I download this
ubl_297m.img ubl_432m.img ubl_486m.img

 

[andrew_by]

could you send me the ubl and uboot for phatom 3 pro

i all time use ubl image from Lightbridge . because all *.ubl same, only in a few case i use any other ubl for processors with lower frequency for example 297MHZ

use attach , in most cases 90% it will work , but if you need ubl_297m.img ubl_432m.img ubl_486m.img ill post them

 

[okstuv]

i all time use ubl image from Lightbridge . because all *.ubl same, only in a few case i use any other ubl for processors with lower frequency for example 297MHZ

use attach , in most cases 90% it will work , but if you need ubl_297m.img ubl_432m.img ubl_486m.img ill post them

Andrew, I'm assuming you did this on a P2VP? Did you use this command or flash other bin's too?
"sfh_DM36x.exe -nandflash -v -p "COMXX" dm6467_297_ubl.img u-boot_modifiedByGaucho.img"

 

[andrew_by]

Andrew, I'm assuming you did this on a P2VP? Did you use this command or flash other bin's too?
"sfh_DM36x.exe -nandflash -v -p "COMXX" dm6467_297_ubl.img u-boot_modifiedByGaucho.img"

use sfh_DM36x.exe -nandflash -v -p "COMXX" ubl.img u-boot_modifiedByGaucho.img

 

[car33th]

Hello! Thank you for being a wonderful thread in which there is a real solution. This procedure is valid for the Phantom 2 Vision. (No +) With camera FC200? Greetings and thank you

 

[Phantom_p3]

use sfh_DM36x.exe -nandflash -v -p "COMXX" ubl.img u-boot_modifiedByGaucho.img

Not working command

 

[Phantom_p3]

sfh_DM36x.exe -nandflash -v -p "COM8" ubl1.img u-boot.img

-----------------------------------------------------
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 COM8...
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 0x00000000
Target: Erasing block 0x00000002 through 0x00000002.
Target: Writing header and image data to Block 0x00000002, Page 0x00000000
Target: Erasing block 0x00000003 through 0x00000003.
Target: Writing header and image data to Block 0x00000003, Page 0x00000000
Target: Erasing block 0x00000004 through 0x00000004.
Target: Writing header and image data to Block 0x00000004, Page 0x00000000
Target: Erasing block 0x00000005 through 0x00000005.
Target: Writing header and image data to Block 0x00000005, Page 0x00000000
Target: Erasing block 0x00000006 through 0x00000006.
Target: Writing header and image data to Block 0x00000006, Page 0x00000000
Target: Erasing block 0x00000007 through 0x00000007.
Target: Writing header and image data to Block 0x00000007, Page 0x00000000
Target: Erasing block 0x00000008 through 0x00000008.
Target: Writing header and image data to Block 0x00000008, Page 0x00000000
Target: Erasing block 0x00000009 through 0x00000009.
Target: Writing header and image data to Block 0x00000009, Page 0x00000000
Target: Erasing block 0x0000000A through 0x0000000A.
Target: Writing header and image data to Block 0x0000000A, Page 0x00000000
Target: Erasing block 0x0000000B through 0x0000000B.
Target: Writing header and image data to Block 0x0000000B, Page 0x00000000
Target: Erasing block 0x0000000C through 0x0000000C.
Target: Writing header and image data to Block 0x0000000C, Page 0x00000000
Target: Erasing block 0x0000000D through 0x0000000D.
Target: Writing header and image data to Block 0x0000000D, Page 0x00000000
Target: Erasing block 0x0000000E through 0x0000000E.
Target: Writing header and image data to Block 0x0000000E, Page 0x00000000
Target: Erasing block 0x0000000F through 0x0000000F.
Target: Writing header and image data to Block 0x0000000F, Page 0x00000000
Target: Erasing block 0x00000010 through 0x00000010.
Target: Writing header and image data to Block 0x00000010, Page 0x00000000
Target: Erasing block 0x00000011 through 0x00000011.
Target: Writing header and image data to Block 0x00000011, Page 0x00000000
Target: Erasing block 0x00000012 through 0x00000012.
Target: Writing header and image data to Block 0x00000012, Page 0x00000000
Target: Erasing block 0x00000013 through 0x00000013.
Target: Writing header and image data to Block 0x00000013, Page 0x00000000
Target: Erasing block 0x00000014 through 0x00000014.
Target: Writing header and image data to Block 0x00000014, Page 0x00000000
Target: Erasing block 0x00000015 through 0x00000015.
Target: Writing header and image data to Block 0x00000015, Page 0x00000000
Target: Erasing block 0x00000016 through 0x00000016.
Target: Writing header and image data to Block 0x00000016, Page 0x00000000
Target: Erasing block 0x00000017 through 0x00000017.
Target: Writing header and image data to Block 0x00000017, Page 0x00000000
Target: Erasing block 0x00000018 through 0x00000018.
Target: Writing header and image data to Block 0x00000018, Page 0x00000000
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 0x00000000
Target: Erasing block 0x0000001C through 0x0000001E.
Target: Writing header and image data to Block 0x0000001C, Page 0x00000000
Target: Erasing block 0x0000001F through 0x00000021.
Target: Writing header and image data to Block 0x0000001F, Page 0x00000000
Target: Erasing block 0x00000022 through 0x00000024.
Target: Writing header and image data to Block 0x00000022, Page 0x00000000
Target: Erasing block 0x00000025 through 0x00000027.
Target: Writing header and image data to Block 0x00000025, Page 0x00000000
Target: Erasing block 0x00000028 through 0x0000002A.
Target: Writing header and image data to Block 0x00000028, Page 0x00000000
Target: Erasing block 0x0000002B through 0x0000002D.
Target: Writing header and image data to Block 0x0000002B, Page 0x00000000
Target: Erasing block 0x0000002E through 0x00000030.
Target: Writing header and image data to Block 0x0000002E, Page 0x00000000
Target: Protecting the entire NAND flash.
Target: DONE
Target: DONE

Operation completed successfully.

This command goes all the way, but even so there is no video yet (black screen) I think this is not the solution, NAND flash in other error

 

[Phantom_p3]

sfh_DM36x.exe -nandflash -v -p "COM8" ?????????????????.img u-boot_modifiedByGaucho.img

I'm looking for somebody which has been running P2V +

ubl1.img not working!!
dm6467_297_ubl.img not working!!
u-boot.img not working!!

20x flash not work

 

[andrew_by]

can youy share photo your module that you whant repair.?
may be i thnk about any other module

 

[shomci]

today I got back my P2 v+ from DJI eu repairs. haven't turned it on. if someone wants to play with it remotely i am here.

 

[Phantom_p3]

today I got back my P2 v+ from DJI eu repairs. haven't turned it on. if someone wants to play with it remotely i am here.

what do you mean?

 

[Phantom_p3]

can youy share photo your module that you whant repair.?
may be i thnk about any other module

 

[andrew_by]

i reflash this module with img from my attachment and all ok.

can you share listing after refalsh , when you desolder BOOTME short

 

[shomci]

what do you mean?

you wrote "I'm looking for somebody which has been running P2V +"

Since I have P2 vision actually under warranty and this is the second time i got back this from DJI. I want to know what cause this issue because my warranty is almost gone.
I am intended to fix this and looking for fellow forum members.
Now I have a fully working P2 V+ V3 got back from DJI repairs (haven't turned on, not paired with my android and 1.0.61 DJI vision app)
And I have a spare wifi module (which was listed "black screen issue" and 2 additional RE700.)
And a TTL module.

This is what I have.

What I don't have is practice and proper expertise. I am a computer engineer so if somebody helps me through the process most probably I'll understand and be able to replicate any steps.

My goal is to get the solution, create post with detailed how to like gaucho did in this thread - sorry gaucho for spamming your thread but as you mentioned P2v+ probably has the same issue - and create a youtube video. And next time when it fails again I am going to make steps towards DJI because they are selling basically faulty 1200 EUR drones.