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

I took a closer look through the older posts in this thread and realized that others had already confirmed that the type of terminal output I was seeing (after re-flashing) was consistent with a working wifi module. I reinstalled the module in the Phantom and the video was working again! Thank you for this solution, very helpful.


pj778 said:
Hello, I'm new to this forum. I ran into a problem with my Phantom 2 Vision+, in which I received telemetry but no video from the quadcopter. I found this post (DJI Phantom 2 Vision+ Plus Blank Screen Corrupt NAND fix) which seemed to match my symptoms exactly, so I gave it a shot. I soldered the serial board, downloaded the files linked, and was successfully able to flash the NAND as described in both Section 2 and Section 3 of the instructions. At the end of both steps, the terminal reported "Operation Completed Successfully," as described in the instructions. However, when I desoldered the 3.3V line and reconnected, I didn't see either of the expected messages, instead the terminal output the following (it seemed to keep looping). Any thoughts on what went wrong, and/or suggestions for how to resolve? I'd love to fix this this instead of buying a new wifi board given I already have it all apart. Thanks in advance!
Click to expand...
 
Hello Mister Gaucho,
I could repair my Lightbridge Groundstation with your perfect tutorial and Files.
It worked on a Win 7 Professional OS, 64 Bit
I thank you verry much for your great job.
Next I will try to repair my second Airstation.
Kind regards, Otto
 
@gaucho
@andrew_by
@rmhome

Thanks for the great work on this so far. I've used Texas Instruments' tool to re-flash the ub1 and u-boot on a bunch of P2VP wifi video transmission modules and put together a tutorial to help others fix that common issue.

About 10% of the modules also suffer from corrupt blocks in their kernels and fail to boot after the u-boot is fixed. Using mefistotelis' github wiki and comments in the associated issues section, I also fixed the kernel on a handful of these modules, only to find another binary, the ecrypted partition, in the NAND is corrupt:

Flashing firmware on DaVinci media processors · mefistotelis/phantom-firmware-tools Wiki · GitHub

How can i get/extract/find the "DM365_secret.bin" to fix this issue (per Flashing firmware on DaVinci media processors · mefistotelis/phantom-firmware-tools Wiki · GitHub

As you can see, the boot-up stalls at "encrypt device:at88 found" just as Mefistotelis says it will when the ecypted partition is corrupt. Terminal output from stalled boot below:
:
Code: 
Dji-Pro # ## Booting kernel from Legacy Image at 80700000 ...
   Image Name:   Linux-2.6.32.17-davinci1
   Created:      2014-09-15   5:24:12 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4043296 Bytes = 3.9 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Loading Kernel Image ... OK
OK

Starting kernel ...

[    0.000000] Kernel Product Vesion : DJI-GSP-Kernel-1.1-rc1(2014-09-15)
[    0.000000] Linux version 2.6.32.17-davinci1 (root@dji) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #3 PREEMPT Mon Sep 15 13:24:10 HKT 2014
[    0.000000] CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: DaVinci DM36x EVM
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] DaVinci dm36x_rev1.2 variant 0x8
[    0.000000] Built 1 zonelists in Zone order, mobility grouping off.  Total pages: 12192
[    0.000000] Kernel command line: console=ttyS0,115200n8 rw dm365_imp.oper_mode=0 video=davincifb:vid0=0,10K:vid1=0,10K:osd0=1920x1080X16,8100K mem=48MB davinci_enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=pal ubi.mtd=2,2048 root=ubi0:rootfs rootfstype=ubifs ip=off lpj=1077248
[    0.000000] PID hash table entries: 256 (order: -2, 1024 bytes)
[    0.000000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Memory: 48MB = 48MB total
[    0.000000] Memory: 44448KB available (3648K code, 447K data, 116K init, 0K highmem)
[    0.000000] SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS:245
[    0.000000] Console: colour dummy device 80x30
[    0.000000] Calibrating delay loop (skipped) preset value.. 215.44 BogoMIPS (lpj=1077248)
[    0.000000] Mount-cache hash table entries: 512
[    0.000000] CPU: Testing write buffer coherency: ok
[    0.000000] DaVinci: 8 gpio irqs
[    0.000000] NET: Registered protocol family 16
[    0.030000] EVM: tvp5146 SD video input
[    0.110000] bio: create slab <bio-0> at 0
[    0.120000] DM365 IPIPE initialized in Continuous mode
[    0.120000] SCSI subsystem initialized
[    0.120000] usbcore: registered new interface driver usbfs
[    0.120000] usbcore: registered new interface driver hub
[    0.120000] usbcore: registered new device driver usb
[    0.130000] vpss vpss: dm365_vpss vpss probed
[    0.130000] vpss vpss: dm365_vpss vpss probe success
[    0.130000] dm365_afew_hw_init
[    0.140000] ch0 default output "COMPOSITE", mode "PAL"
[    0.140000] VPBE Encoder Initialized
[    0.140000] cfg80211: Using static regulatory domain info
[    0.140000] cfg80211: Regulatory domain: US
[    0.140000]  (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[    0.140000]  (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
[    0.140000]  (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[    0.140000]  (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[    0.140000]  (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[    0.140000]  (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[    0.140000]  (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[    0.140000] cfg80211: Calling CRDA for country: US
[    0.140000] LogicPD encoder initialized
[    0.140000] Switching to clocksource timer0_1
[    0.150000] musb_hdrc: version 6.0, pio, host, debug=0
[    0.170000] musb_hdrc: USB Host mode controller at fec64000 using PIO, IRQ 12
[    0.170000] musb_hdrc musb_hdrc: MUSB HDRC host driver
[    0.170000] musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
[    0.170000] usb usb1: configuration #1 chosen from 1 choice
[    0.170000] hub 1-0:1.0: USB hub found
[    0.170000] hub 1-0:1.0: 1 port detected
[    0.170000] NET: Registered protocol family 2
[    0.170000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.170000] TCP established hash table entries: 2048 (order: 2, 16384 bytes)
[    0.170000] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
[    0.170000] TCP: Hash tables configured (established 2048 bind 2048)
[    0.170000] TCP reno registered
[    0.170000] NET: Registered protocol family 1
[    0.170000] RPC: Registered udp transport module.
[    0.170000] RPC: Registered tcp transport module.
[    0.170000] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.180000] kfile init
[    0.180000] JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[    0.180000] msgmni has been set to 86
[    0.190000] alg: No test for stdrng (krng)
[    0.190000] io scheduler noop registered (default)
[    0.220000] davincifb davincifb.0: dm_osd0_fb: Initial window configuration is invalid.
[    0.230000] davincifb davincifb.0: dm_osd0_fb: 1920x1080x16@0,0 with framebuffer size 8100KB
[    0.230000] davincifb davincifb.0: dm_vid0_fb: 0x0x16@0,0 with framebuffer size 10KB
[    0.250000] davincifb davincifb.0: dm_osd1_fb: Initial window configuration is invalid.
[    0.250000] davincifb davincifb.0: dm_osd1_fb: 1920x1080x4@0,0 with framebuffer size 4050KB
[    0.250000] davincifb davincifb.0: dm_vid1_fb: 0x0x16@0,0 with framebuffer size 10KB
[    0.310000] venc off init
[    0.310000] hdmi status init
[    0.310000] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[    0.310000] DM365 IPIPEIF probed
[    0.320000] imp serializer initialized
[    0.320000] davinci_previewer initialized
[    0.320000] davinci_resizer initialized
[    0.320000] HDMI chip id incorrect: 0-0
[    0.320000] hdmi_i2c_probe err:-5
[    0.320000] it66121-hdmi: probe of 1-004d failed with error -5
[    0.320000] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    0.330000] serial8250.0: ttyS0 at MMIO 0x1c20000 (irq = 40) is a 16550A
[    0.820000] console [ttyS0] enabled
[    0.820000] serial8250.0: ttyS1 at MMIO 0x1d06000 (irq = 41) is a 16550A
[    0.830000] brd: module loaded
[    0.840000] at24 1-0050: 32768 byte 24c256 EEPROM (writable)
[    0.900000] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xf1 (Micron NAND 128MiB 3,3V 8-bit)
[    0.910000] Creating 4 MTD partitions on "davinci_nand.0":
[    0.920000] 0x000000000000-0x0000004a0000 : "bootloader"
[    0.920000] 0x0000004a0000-0x000000e00000 : "kernel"
[    0.930000] 0x000000e00000-0x000007f00000 : "filesystem"
[    0.940000] 0x000000000000-0x000008000000 : "all"
[    0.950000] davinci_nand davinci_nand.0: controller rev. 2.3
[    0.960000] UBI: attaching mtd2 to ubi0
[    0.960000] UBI: physical eraseblock size:   131072 bytes (128 KiB)
[    0.970000] UBI: logical eraseblock size:    126976 bytes
[    0.970000] UBI: smallest flash I/O unit:    2048
[    0.980000] UBI: sub-page size:              512
[    0.980000] UBI: VID header offset:          2048 (aligned 2048)
[    0.990000] UBI: data offset:                4096
[    1.470000] UBI error: vtbl_check: volume table check failed: record 0, error 9
[    1.480000] UBI error: ubi_init: cannot attach mtd2
[    1.480000] UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
[    1.490000] console [netcon0] enabled
[    1.490000] netconsole: network logging started
[    1.500000] Initializing USB Mass Storage driver...
[    1.500000] usbcore: registered new interface driver usb-storage
[    1.510000] USB Mass Storage support registered.
[    1.520000] usbcore: registered new interface driver usbtest
[    1.520000] i2c /dev entries driver
[    1.530000] Linux video capture interface: v2.00
[    1.530000] ths7303 1-002c: chip found @ 0x58 (DaVinci I2C adapter)
[    1.540000] ths7303 1-002c: ths7303 write failed
[    1.550000] ths7303: probe of 1-002c failed with error -121
[    1.550000] tvp5150_init
[    1.560000] vpfe_init
[    1.560000] vpfe-capture: vpss clock vpss_master enabled
[    1.560000] vpfe-capture vpfe-capture: v4l2 device registered
[    1.570000] vpfe-capture vpfe-capture: video device registered
[    1.580000] tvp5150_probe
[    1.580000] tvp5150 1-005d: tvp5150 1-005d decoder driver registered !!
[    1.590000] vpfe-capture vpfe-capture: v4l2 sub device tvp5150 registered
[    1.600000] vpfe-capture vpfe-capture: v4l2 sub device cat6023 register fails
[    1.610000] vpfe_register_ccdc_device: DM365 ISIF
[    1.610000] DM365 ISIF is registered with vpfe.
[    1.620000] Trying to register davinci display video device.
[    1.620000] layer=c17f6c00,layer->video_dev=c17f6d64
[    1.630000] Trying to register davinci display video device.
[    1.630000] layer=c17f7000,layer->video_dev=c17f7164
[    1.640000] davinci_init:DaVinci V4L2 Display Driver V1.0 loaded
[    1.650000] watchdog watchdog: heartbeat 1 sec
[    1.650000] TCP cubic registered
[    1.660000] NET: Registered protocol family 17
[    1.660000] lib80211: common routines for IEEE802.11 drivers
[    1.670000] ksocket init
[    2.310000] encrypt device:at88 found

How can i get the "DM365_secret.bin" to fix this issue (per Flashing firmware on DaVinci media processors · mefistotelis/phantom-firmware-tools Wiki · GitHub
 
Hi Everyone,

Ive soldered everything as it says and am trying to flash the image but continue to get BOOT ME (air unit)

Notice Target:curropt

I've tried Win vista 64 bit, 7 32bit and 10 64bit

Ive tried Crtl + C and restart CMD/redo command

To get the "BEGIN" command i have to keep the exe running and reboot the phantom like in the description. However it just changes to "curropt" and goes back to "BOOTME"

Anyone have any ideas? been stuck on this for a long time!


upload_2018-1-17_21-31-2.png
 
Late to the party, but just recently was able to get a P2V (not the PLUS) for my son. I am having the no live video issue as described here...Everything works fine on the camera (photos, video and movement), just no live feed. My question: Does this fix work for P2V (non-plus) with the older egg shaped camera? Thought I’d ask even though this is a fairly old thread. May just end up mounting a cheap 5.8ghz FPV on it instead so he’s not flying completely blind.

Thanks for any help you can provide.

Andrew
 
Hi,
Yesterday i maked the procedure with one of my two couple of lightbridge.
now, the video in the monitor is ok, but there is solid red led in the air unit and the LB Android App doesn't connect wilth LB. Any suggestion please?

Thank's a lot
 
erouch said:
You make the procedure on the ground station or on the air unit? Whose red light, video?
Click to expand...
i have done the procedure on ground and air unit. video red led is on air unit, but with monitor hdmi the video is ok, but with the android app doesn't connect
 
Android app is on smartphone by micro usb. It's send "connexion broken"? The app is dji lightbridge or dji go?
 
You are sure that on the ground station you see the 3 firmware versions: controler, transmitter and decoder?
 
Personally I never flash the air unit but always the ground station. Because the air unit has always shown its firmwares up to date with the good Version. Have you disactivated the wifi on your smartphone?
 
erouch said:
Personally I never flash the air unit but always the ground station. Because the air unit has always shown its firmwares up to date with the good Version. Have you disactivated the wifi on your smartphone?
Click to expand...
In my air unit, before the flash, there was only one firmware shown. After the flash there are 3. Yes, i have disactivated wifi....i will tray to downgrade ground unit firmware..maybe it can be the solution...
 
ghirla said:
the last
Click to expand...
When I try to flash LB air unit, I see these messages. Reboot and CTRL + C do not give any results. LB ground unit works after firmware update.
what am I doing wrong? Thanks
 

Attachments

  • lb.jpg
    lb.jpg
    205 KB · Views: 467

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: 380 (members: 1, guests: 379)

Forum statistics

Threads
143,092
Messages
1,467,577
Members
104,975
Latest member
cgarner1