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

[gaucho]

Hi Gaucho, thanks for the great job.
I am also from Italy and yesterday I checked all your suggestion to open the diagnostic port ( upgrade port for now ) of the GS and play with embedded DJI linux-davinci.
I am interested in the wireless configuration, especially in the "zone". With P3, and other devices, the region where the device resides makes a great difference in terms of output power. If you are in the USA you have FCC regulations, outside it is ETSI.
I bought a used LB ad immediately upgraded the firmware, it was an error! The reange decreased. So I am searching now some informations my wireless configuration. Attached you will find my log at boot. It seems that US country is selected, thus the maximum output power, but, where it is selected? It is embedded in a load module? I am referencing to this post regarding the output power:
Phantom 3 Standard range mod , let's do it together...
Thanks for all
Alex

I understood that your log comes from a phantom3 and not from a lightbridge product. So i suppose that that print is not available in my device. In your log i can see that the module printing "regulation US" is the
cfg80211. en:developers:documentation:cfg80211 [Linux Wireless]
Read this entire link, try the manual commands to change the wireless setting (find those concerning the regulation country), then come back Here.

 

[kurkovda]

The log is incomplete. Are you able to send Linux commands ON the serial line? Are you able to update the 3 firmware components by means of the dji update tool?

No, i'm not able to update 3 firmware components by DJI tool, only the first part of ground component is visible.
The log is a part with an error, if it's important I can upload the whole log.
And yes, i can send the linux comands, but nothing hapens - the kernal is down.

 

[gaucho]

No, i'm not able to update 3 firmware components by DJI tool, only the first part of ground component is visible.
The log is a part with an error, if it's important I can upload the whole log.
And yes, i can send the linux comands, but nothing hapens - the kernal is down.

So you flashed the lb ground unit according to my detailed instructions and now you get a boot loop. Does this means that the unit continuously reboots? Can you post a complete log? What does it was the original problem? Do you have the original log of the broken unit?

You can retry to flash the unit 2 more Times.

you can Also check if you see, during boot time, AN option that gives to you the ability to break the boot and enter in another mode

 

[carlos eduardo diaz]

IMAGEN LIGHTBRIDGE

• carlos eduardo diaz
• Jan 1, 2017

[Quote = "danielh, de la publicación: 1015495, miembro de: 77032"] mismo que este
[ATTACH = completo] 70706 [/ attach] [attach = completo] 70707 [/ attach] [/ quote]

hola hola buen día, tengo el mismo problema y no he conseguido resolverlo, si se las arregló para solucionarlo, usted me puede ayudar, indicando los pasos a seguir

 

[kurkovda]

So you flashed the lb ground unit according to my detailed instructions and now you get a boot loop. Does this means that the unit continuously reboots? Can you post a complete log? What does it was the original problem? Do you have the original log of the broken unit?

You can retry to flash the unit 2 more Times.

you can Also check if you see, during boot time, AN option that gives to you the ability to break the boot and enter in another mode

Here's the complete log:

Spoiler: log

Port opened at 01.01.2017 21:57:58
DM36x initialization passed!
UBL Product Vesion : DJI-GSP-UBL-1.0-rc10(2014-08-15)
Dji UBL Version: 1.51(Aug 15 2014 - 17:05:12)
Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000019.
Uboot Checksum:0x7E25B44B
Actua Checksum:0x7E25B44B

U-Boot Product Vesion : DJI-GSP-Uboot-1.0-rc4(2014-07-23)
U-Boot 2010.12-rc2-svn-Dji (Jul 23 2014 - 11:14:40)
Cores: ARM 432 MHz
DDR: 297 MHz
I2C: ready
DRAM: 128 MiB
NAND: 128 MiB
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
*** Warning - bad CRC, using default environment

Net: Ethernet PHY: GENERIC @ 0xff
DaVinci-EMAC
Press ESC to abort autoboot in 1 seconds

Loading from nand0, offset 0x4a0000
** Unknown image type
Wrong Image Format for bootm command
ERROR: can't get kernel image!

Loading from nand0, offset 0x900000
Image Name: Linux-2.6.32.17-davinci1
Created: 2014-05-30 6:44:26 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4034816 Bytes = 3.8 MiB
Load Address: 80008000
Entry Point: 80008000
## Booting kernel from Legacy Image at 80700000 ...
Image Name: Linux-2.6.32.17-davinci1
Created: 2014-05-30 6:44:26 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4034816 Bytes = 3.8 MiB
Load Address: 80008000
Entry Point: 80008000
Loading Kernel Image ... OK
OK


Starting kernel ...

[ 0.000000] Kernel Product Vesion : DJI-GSPv2-Kernel-1.0-rc3(2014-05-30 14:45)
[ 0.000000] Linux version 2.6.32.17-davinci1 (root@dji) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #8 PREEMPT Fri May 30 14:44:25 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,10Ksd0=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: 44456KB available (3644K code, 446K 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.110000] 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] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 0.330000] serial8250.0: ttyS0 at MMIO 0x1c20000 (irq = 40) is a 16550A
[ 0.810000] console [ttyS0] enabled
[ 0.810000] serial8250.0: ttyS1 at MMIO 0x1d06000 (irq = 41) is a 16550A
[ 0.820000] brd: module loaded
[ 0.830000] at24 1-0050: 32768 byte 24c256 EEPROM (writable)
[ 0.890000] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xf1 (Micron NAND 128MiB 3,3V 8-bit)
[ 0.900000] Creating 4 MTD partitions on "davinci_nand.0":
[ 0.910000] 0x000000000000-0x0000004a0000 : "bootloader"
[ 0.910000] 0x0000004a0000-0x000000e00000 : "kernel"
[ 0.920000] 0x000000e00000-0x000007f00000 : "filesystem"

[ 0.930000] 0x000000000000-0x000008000000 : "all"
[ 0.940000] davinci_nand davinci_nand.0: controller rev. 2.3
[ 0.950000] UBI: attaching mtd2 to ubi0
[ 0.950000] UBI: physical eraseblock size: 131072 bytes (128 KiB)
[ 0.960000] UBI: logical eraseblock size: 126976 bytes
[ 0.970000] UBI: smallest flash I/O unit: 2048
[ 0.970000] UBI: sub-page size: 512
[ 0.980000] UBI: VID header offset: 2048 (aligned 2048)
[ 0.980000] UBI: data offset: 4096
[ 1.110000] usb 1-1: new high speed USB device using musb_hdrc and address 2
[ 1.260000] usb 1-1: configuration #1 chosen from 1 choice
[ 1.260000] hub 1-1:1.0: USB hub found
[ 1.270000] hub 1-1:1.0: 2 ports detected
[ 1.500000] UBI: attached mtd2 to ubi0
[ 1.500000] UBI: MTD device name: "filesystem"
[ 1.510000] UBI: MTD device size: 113 MiB
[ 1.510000] UBI: number of good PEBs: 904
[ 1.520000] UBI: number of bad PEBs: 0
[ 1.520000] UBI: max. allowed volumes: 128
[ 1.530000] UBI: wear-leveling threshold: 4096
[ 1.530000] UBI: number of internal volumes: 1
[ 1.540000] UBI: number of user volumes: 1
[ 1.540000] UBI: available PEBs: 0
[ 1.540000] UBI: total number of reserved PEBs: 904
[ 1.550000] UBI: number of PEBs reserved for bad PEB handling: 9
[ 1.560000] UBI: max/mean erase counter: 60/1
[ 1.560000] UBI: image sequence number: 782088511
[ 1.570000] UBI: background thread "ubi_bgt0d" started, PID 349
[ 1.570000] console [netcon0] enabled
[ 1.580000] netconsole: network logging started
[ 1.580000] Initializing USB Mass Storage driver...
[ 1.590000] usbcore: registered new interface driver usb-storage
[ 1.590000] USB Mass Storage support registered.
[ 1.600000] usbcore: registered new interface driver usbtest
[ 1.610000] i2c /dev entries driver
[ 1.610000] Linux video capture interface: v2.00
[ 1.620000] ths7303 1-002c: chip found @ 0x58 (DaVinci I2C adapter)
[ 1.620000] ths7303 1-002c: ths7303 write failed
[ 1.630000] ths7303: probe of 1-002c failed with error -121
[ 1.630000] tvp5150_init
[ 1.640000] vpfe_init
[ 1.640000] vpfe-capture: vpss clock vpss_master enabled
[ 1.650000] vpfe-capture vpfe-capture: v4l2 device registered
[ 1.650000] vpfe-capture vpfe-capture: video device registered
[ 1.660000] tvp5150_probe
[ 1.660000] tvp5150 1-005d: tvp5150 1-005d decoder driver registered !!
[ 1.670000] vpfe-capture vpfe-capture: v4l2 sub device tvp5150 registered
[ 1.680000] vpfe-capture vpfe-capture: v4l2 sub device cat6023 register fails
[ 1.690000] vpfe_register_ccdc_device: DM365 ISIF
[ 1.690000] DM365 ISIF is registered with vpfe.
[ 1.700000] Trying to register davinci display video device.
[ 1.710000] layer=c17f7000,layer->video_dev=c17f7164
[ 1.710000] Trying to register davinci display video device.
[ 1.720000] layer=c17f7400,layer->video_dev=c17f7564
[ 1.720000] davinci_initaVinci V4L2 Display Driver V1.0 loaded
[ 1.730000] watchdog watchdog: heartbeat 1 sec
[ 1.740000] TCP cubic registered
[ 1.740000] NET: Registered protocol family 17
[ 1.740000] lib80211: common routines for IEEE802.11 drivers
[ 1.750000] ksocket init
[ 1.780000] Clocks: disable unused mmcsd0
[ 1.780000] Clocks: disable unused mmcsd1
[ 1.780000] Clocks: disable unused spi0
[ 1.780000] Clocks: disable unused spi1
[ 1.780000] Clocks: disable unused spi2
[ 1.780000] Clocks: disable unused spi3
[ 1.780000] Clocks: disable unused spi4
[ 1.780000] Clocks: disable unused pwm0
[ 1.780000] Clocks: disable unused pwm1
[ 1.780000] Clocks: disable unused pwm2

[ 1.780000] Clocks: disable unused pwm3
[ 1.780000] Clocks: disable unused timer1
[ 1.780000] Clocks: disable unused timer3
[ 1.780000] Clocks: disable unused emac
[ 1.780000] Clocks: disable unused voice_codec
[ 1.780000] Clocks: disable unused asp0
[ 1.780000] Clocks: disable unused rto
[ 1.780000] Clocks: disable unused mjcp
[ 1.860000] nnnn===0
[ 1.860000] davinci_emac_probe: using random MAC addr: ea:99:a4:54:32:f2
[ 1.870000] emac-mii: probed
[ 1.910000] UBIFS: recovery needed
[ 1.960000] UBIFS error (pid 1): ubifs_recover_leb: corrupt empty space LEB 3:2048, corruption starts at 67584
[ 1.970000] UBIFS error (pid 1): ubifs_scanned_corruption: corruption at LEB 3:67584
[ 1.990000] UBIFS error (pid 1): ubifs_recover_leb: LEB 3 scanning failed
[ 2.000000] VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)
[ 2.010000] Please append a correct "root=" boot option; here are the available partitions:
[ 2.020000] 1f00 4736 mtdblock0 (driver?)
[ 2.020000] 1f01 9600 mtdblock1 (driver?)
[ 2.030000] 1f02 115712 mtdblock2 (driver?)
[ 2.030000] 1f03 131072 mtdblock3 (driver?)
[ 2.040000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 2.050000] Rebooting in 1 seconds..DM36x initialization passed!
UBL Product Vesion : DJI-GSP-UBL-1.0-rc10(2014-08-15)
Dji UBL Version: 1.51(Aug 15 2014 - 17:05:12)
Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000019.
Uboot Checksum:0x7E25B44B
Actua Checksum:0x7E25B44B

I've flashed 3 times acording to your instructions, and this is the onle result I got
The problem was that in assistat only main unit was visible for upgrading firmware, and no video signal arrived from transmitter.

 

[gaucho]

Kurkovda You can see during boot "Press ESC to abort autoboot in 1 seconds"
You can enter that mode and reflash the nand.
Actually i don't have a procedure for you. Let me search. Meanwhile do some tests in that mode.

 

[gaucho]

Kurkovda,

few months ago Andrew suggested to me:
"....at this moment press ESC and you go to the U-BOOT
when you boot to U-BOOT you can load uImage via nandwrite command."

I never needed to do this because that part of the fash was not corrupted in my case.

 

[carlos eduardo diaz]

Someone has a video tutorial. Or the youtube link on how to make the fix. ?

 

[carlos eduardo diaz]

Kurkovda,

few months ago Andrew suggested to me:
"....at this moment press ESC and you go to the U-BOOT
when you boot to U-BOOT you can load uImage via nandwrite command."

I never needed to do this because that part of the fash was not corrupted in my case.

Hi good day. How much would a video tutorial cost to fix the air unit ?. I am located in Colombia and the repair center dji does not make this repair.

 

[carlos eduardo diaz]

same as this
View attachment 70706 View attachment 70707

hi daniel can you help me . i have the same proble. can you fix it. how do yoo make it. please help.

 

[gaucho]

Hi Gaucho, thanks for the great job.
I am also from Italy and yesterday I checked all your suggestion to open the diagnostic port ( upgrade port for now ) of the GS and play with embedded DJI linux-davinci.
I am interested in the wireless configuration, especially in the "zone". With P3, and other devices, the region where the device resides makes a great difference in terms of output power. If you are in the USA you have FCC regulations, outside it is ETSI.
I bought a used LB ad immediately upgraded the firmware, it was an error! The reange decreased. So I am searching now some informations my wireless configuration. Attached you will find my log at boot. It seems that US country is selected, thus the maximum output power, but, where it is selected? It is embedded in a load module? I am referencing to this post regarding the output power:
Phantom 3 Standard range mod , let's do it together...
Thanks for all
Alex

Can't you just use an american proxy to mask your italian ip address with american ip address during upgrade?
There are a lot of tools equivalent to TOR that you can use for this scope

Moreover i read on the first Page of the linked thread that the script resides in the rc.local file. The problem seems to be found and solved. Am I wrong?

 

[kurkovda]

Kurkovda,

few months ago Andrew suggested to me:
"....at this moment press ESC and you go to the U-BOOT
when you boot to U-BOOT you can load uImage via nandwrite command."

I never needed to do this because that part of the fash was not corrupted in my case.

Thanks, i will surely try this, but not earlier then 9 jan - all devices and software on my workplace =\

 

[gaucho]

Read on page 5 of this thread the information received from Texas instruments

 

[carlos eduardo diaz]

[Quote = "gaucho, de la publicación: 1040569, miembro de: 24023"] Lea en la página 5 de este hilo de la información recibida de Texas Instruments [/ quote]
http://www.tr3ma.com/Dati/LB_hack.zip
Tiene otro enlace de descarga, esto no trabaja

 

[skyguide]

http://www.tr3ma.com/Dati/LB_hack.zip

Is not available at this time. Can anyone upload or send me the file again? I have the same problem with my air unit. Thanks!

 

[gaucho]

The procedure is for the ground unit. Did anyone successfully recovered an air unit with my file?

There is something strange,
If i open the link with the pc i can successfully download the file while from my iphone i can't

 

[skyguide]

The procedure is for the ground unit. Did anyone successfully recovered an air unit with my file?

Oh that's bad. I need it for my Air Unit...

Anyway, server is up again. Thanks!

 

[carlos eduardo diaz]

Someone can help me, what am I doing wrong ?. I'm following the steps of the post

 

[carlos eduardo diaz]

Oh that's bad. I need it for my Air Unit...

Anyway, server is up again. Thanks!

Dropbox - Join Dropbox to view this file.

I managed to download them, try on this link in my dropbox

 

[gaucho]

Someone can help me, what am I doing wrong ?. I'm following the steps of the post

First of all you need a procedure for the air unit while my procedure is for the ground unit.
Second: you must unzip the file on a folder and then you must open that folder with the dos command cd (cd folderName) and then run the executable otherwise you will get the error prompted in your snapshots.

Ps: did you tried to open the serial line and check what is it prompted on it during the boot?
This is always a good practice, in order to check what is your device error