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

oceank said:
I use the dji lightbridge assistant 1.3(latest) and yes I see all 3 firmware and I installed them , one by one. no problem there at all.

hmm ok then I have to resolder the usb to ttl device and get the boot log if u still want it?
btw how do I get the bootlog?
Click to expand...
no, you could also try another thing.
connect the upgrade port to pc via usb cable, open my tool (annexed to the zip file on the first post), enable the virtual serial port, close the tool and open a hyperterminal or equivalent tool, type some linux commands (type the following commands):
ls
pwd
ps -ax
ps -ef

post here the result

p.s.:read about my tool on the first post. i wrote a more accurate sentence there
 
anyway i think your smartphone or your cable or your android app has some problem.
i suggest you to use a smartphone that you are sure that previously worked (some android device have problems with LB)
change usb cable
 
gaucho said:
i found ios app one time as offline download then i lost it.
no, i don't have your problem.
I converted the hex print (read previous posts) to binary file. So we could understand what and where to write data to memory, by means of uboot and not only via windows tool sfh. this because sfh exe is less flexible and if also have a bug that does not allow you to write memory location where you want.
anyway this should be usefull just in particular cases. most of the cases it will be fine the procedure reported on the first post.
Click to expand...


ohhh OK. shame you lost the ios app. I would like to try it but nowhere to be found.
I dont have any android devices but one nvidia tvshield. I then use a usb to usb cable(shile device to lightbridge), maybe thats the problem? or it doesnt matter? Because I guess if I had a android cellphone it would have been usb to micro usb cable.
 
All ther different command as you todl gave me this log:




Port opened at 2017-02-11 12:18:26
0D 0A 55 BB 55 BB FF 00 00 00 FF 0D 0A

root@Dji-Pro:~#
root@Dji-Pro:~#
root@Dji-Pro:~#
root@Dji-Pro:~# ls

ls
[1;32mVend_Ax.iic[0m [1;32meth0config[0m [1;32mmtdwritefile[0m [1;32mupdate[0m [1;32musbupdate[0m
[1;32madb[0m [1;32mfxload[0m [1;32msetsecurity[0m [1;32mupdate68013[0m
[1;32mdevgpio[0m [1;32mloadmodule-rc[0m [1;32msshenable[0m [1;32musbclient[0m
[1;32menable68013[0m [1;32mmtderase[0m [1;32mstop[0m [1;32musbmuxd[0m
root@Dji-Pro:~#
root@Dji-Pro:~# pwd

pwd
/opt/dji/bin
root@Dji-Pro:~#
root@Dji-Pro:~# ps -ax

ps -ax
ps: invalid option -- 'x'
BusyBox v1.21.1 (2013-11-14 14:07:22 CST) multi-call binary.

Usage: ps [-o COL1,COL2=HEADER] [-T]

Show list of processes

-o COL1,COL2=HEADER Select columns for display
-T Show threads

root@Dji-Pro:~#
root@Dji-Pro:~# ps -ef

ps -ef
PID USER TIME COMMAND
1 root 0:02 init
2 root 0:00 [kthreadd]
3 root 0:00 [ksoftirqd/0]

4 root 0:00 [events/0]

5 root 0:00 [khelper]
8 root 0:00 [async/mgr]
141 root 0:00 [sync_supers]
143 root 0:00 [bdi-default]
145 root 0:00 [kblockd/0]
159 root 0:00 [khubd]
162 root 0:00 [kseriod]
200 root 0:00 [rpciod/0]
209 root 0:00 [kswapd0]
210 root 0:00 [aio/0]
211 root 0:00 [nfsiod]
212 root 0:00 [crypto/0]
310 root 0:00 [hdmi_timer_kthr]
327 root 0:00 [mtdblockd]
349 root 0:00 [ubi_bgt0d]
386 root 0:00 [ubifs_bgt0_0]

475 root 0:00 /usr/local/sbin/sshd
479 root 0:00 adb -P 5037 fork-server server
484 root 0:00 usbmuxd -v -v
485 root 0:04 usbclient
486 root 0:00 usbupdate
489 root 0:00 {autologin} /bin/sh /sbin/autologin
491 root 0:00 -sh
518 root 0:00 [flush-ubifs_0_0]
587 root 0:00 ps -ef
root@Dji-Pro:~#
root@Dji-Pro:~#
 
It seems to me that everything is working. Find one or two android phones and do a test.
It must work.
 
gaucho said:
It seems to me that everything is working. Find one or two android phones and do a test.
It must work.
Click to expand...
my unit is Phantom 3p ，have same problem
bu I didn't have the software ，can u help me


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...
 
2008jiayu said:
my unit is Phantom 3p ，have same problem
bu I didn't have the software ，can u help me


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...
Click to expand...
Read few last pages of this thread, there is more than one guy in your situation that solved the problem and posted the solution. Don't ask more if you didn't read the entire thread.
 
gaucho said:
It seems to me that everything is working. Find one or two android phones and do a test.
It must work.
Click to expand...

You´re AWESOME!, thanx mate! I did borrow my neighbours cellphone/android with a usb-micro usb cable and BOOOOM! it all works =)
So no I have configured it like I want it to be!

anways good tutorial and info Mr Gaucho!

regards K
 
  • Like
Reactions: gaucho
gaucho said:
Read few last pages of this thread, there is more than one guy in your situation that solved the problem and posted the solution. Don't ask more if you didn't read the entire thread.
Click to expand...
i readed it at all,is the file can be used for 3p? i am so silly，teach me ,i do not have the uboot and uimage
 
gaucho said:
It seems to me that everything is working. Find one or two android phones and do a test.
It must work.
Click to expand...
you means just use the file you post ,dont care aboat the version ,do this when the dm365 start up, system can find the hardware ,then use the firmwera for a update
 
username said:
Hi Okstuv,

powered on the module on your workbench with external 12VDC from a power supply, or powered on after returning into Phantom and powering on Phantom?

Thanks.
Click to expand...

Since I burned up my previous module by using 2 power supplies (USB and 12V) I bought a "bad" p2vp wifi video transmission module on eBay and successfully reflashed it today. The main difference was that I didn't hook up 12V from the quad to the unit - instead hooked up just 5V, GND, UART TX, UART RX and shorted 3V to BOOT on the board. After a few times hitting CTRL-C when it kicked out to "Boot me" in CMD prompt and kicking off the DM36X process again, I got the following result:

Code: 
tpg successful_flash log take 2.txt
Details
Activity
tpg successful_flash log take 2.txt
Sharing Info
Not shared
General Info
Type
Text
Size
7 KB (7,653 bytes)
Storage used
7 KB (7,653 bytes)
Location
My Drive
Owner
me
Modified
9:49 PM by me
Opened
9:58 PM by me
Created
9:49 PM with Google Drive Web
Description
Add a description
Download permissions
Viewers can download
Closed
New Team Drive

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


Flashing NAND with dm6467_297_ubl.img and u-boot_modifiedByGaucho.img.


Attempting to connect to device COM3...
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.

C:\Users\Turner\Desktop\reflash\LB_hack>

I haven't rebinded it and confirmed that all functionality is back, since I'm waiting on a new camera. Once that comes in, I'll post the results net weekend. So far it look good. If anyone sees issues in the log, plx let me know. At least nothing burned up this time :)
 
  • Like
Reactions: shomci
rmhome said:
Hi,

I will get something typed up but it's a matter of connecting a TTL USB serial module to the UART0 pads and then shorting BSEL and 3.3V together then power up (pads are clearly marked which is a bonus). You will then use the same instructions that have been posted here by Gaucho for the LB units - You will see the same wording scrolling accross the serial console (BOOT ME) and then run the EXE with:

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

You should then see the update happening (see screenshot in my above post).

After that, reboot device without BSEL/3.3V shorted and you should be good!
Click to expand...
hi rmhome，can I use the file you post on phatom 3 pro
 

Similar threads

M
DJI Phantom 2 Vision FC200 EGG camera - Black video FPV solution to fix
Replies
245
Views
52K
Phantom 2 Vision Discussion
DenysTim
D

Recent Posts

Members online

No members online now.
Total: 578 (members: 0, guests: 578)

Forum statistics

Threads
143,086
Messages
1,467,528
Members
104,965
Latest member
Fimaj