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

Joined
Oct 23, 2019
Messages
9
Reaction score
1
Age
49
How did you know which pin to to pull to ground?. I also found a reset pin on the ground unit.
I tried all pins to find the reset pin. The board seemed to perform a reset and programming startet automatically with the programming tool waiting for the board. I found that holding it down enabled my board to complete the whole programming procedure.
 
Joined
Nov 29, 2018
Messages
10
Reaction score
1
Age
39
just to confirm. Shorting the pin that LB_Victim found to GND, without any resistors works like a charm. I had issues with air unit, updating firmware as we speak :) Thank you 1000 times. A year ago I had issues with ground unit, now air unit went nuts :/
 
Joined
Oct 23, 2019
Messages
9
Reaction score
1
Age
49
Nice to hear, that someone else could use the solution. I tried with a resistor due to safety reasons - it works as current limiter and prevents damages. I reported to use a resistor because it worked for me.
 
Joined
Nov 29, 2018
Messages
10
Reaction score
1
Age
39
I know I should have used one, but none was around. And since it was dead anyway, I tried. 6 months ago I had a dead ground unit, saved it with this procedure, but air unit needed some more work. Now is ok. Im curious how much will it hold. Although ground unit was without the battery for 6 months (battery completely dead, removed it), and it was fine. Maybe it just needs one recovery flash? Anybody had to do it more than once? Once again thank you :) And one question, did anyone ever got the fullhd mode working? mine gives all kind of weird artefacts on the hdmi out, smooth and realtime mode work fine.
 
Joined
Nov 23, 2019
Messages
1
Reaction score
0
Age
38
Hi,

I just bought a 2nd hand lightbridge 1 and i think i'm lucky to have this problem.

Is there anyone here who lives in Europe who could do the firmware flash manipulation for me? Of course, I agree to pay.
Contact me by PM.
 
Joined
Nov 29, 2018
Messages
10
Reaction score
1
Age
39
I'm in Croatia. I succesfully did both ground and air unit recovery. If you need assistance, let me know.
IMG_20191122_153304.jpg
 
Last edited:
  • Like
Reactions: quaddamage
Joined
Apr 14, 2015
Messages
287
Reaction score
31
Age
70
Hi guys,

I found a solution (partly by accident) when I was searching a reset pin for the board. Just to eleminate the chance of transient power issues short after powering up the unit.

To solve the "CORRUPT" message described above, I pulled the marked pin to GND by a 8.5k resistor. No warranty that this will work and not damaga your board. But pulling pins to GND via a resistor like this has only low risks.

After that continue with the procedure of goucho. In my case the board completes flashing the images with no issues. My air unit works again as a new one.
Please let me know if somebody can confirm this procedure.
Good luck!

btw: DJI support told me that the unit will not be reapaired or exchanged anymore. Thanks DJI!! Never will buy a faulty expansive product with this kind of support!!

View attachment 115224
Dear LB_Victim compliments.
Today I powered my air unit since long time and I found exactly the same problem as yours (and the same as Matt too).
Then I read your post and I shorted the pin you found (let's call it RESET) to ground, with also BSEL pin too.
Then I run the command on the terminal,
then I powered on the unit
then the UBL was correctly flashed,
But then the flash process was not proceeding, then I hit CTRL+C and I run again the command: this time the process restarted and continued with success up to the end.

This is the log obtained (unfortunately it saved just the second run of the command, after the CTRL+C):


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

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

Attempting to connect to device COM7...
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\GauchoHP\Desktop>


I will update the first post with this procedure for air unit, if the first attempt don't work.
 
Last edited:
  • Like
Reactions: Mark The Droner
Joined
Dec 14, 2019
Messages
3
Reaction score
0
Age
23
Hello,

I'm a French man trying to fix the problem you had 3 years ago. I've a LB1 which has been completely discharged so nothing happens when I connect my phone via USB on my LB1. I saw your multiple posts (of 2016), I bought a FT232RL 3.3V-5.5V FTDI USB to TTL Serial Adapter and read all your posts but It's quite complicated to understand bc you developped and corrected some glitchs at the same time.
Could you help me to solve my problem explaining me how to do? I prefer speaking in French but I also understand English well so it should be very easy to understand you.
Thanks in advance for you help.
 
Joined
Apr 14, 2015
Messages
287
Reaction score
31
Age
70
Hello,

I'm a French man trying to fix the problem you had 3 years ago. I've a LB1 which has been completely discharged so nothing happens when I connect my phone via USB on my LB1. I saw your multiple posts (of 2016), I bought a FT232RL 3.3V-5.5V FTDI USB to TTL Serial Adapter and read all your posts but It's quite complicated to understand bc you developped and corrected some glitchs at the same time.
Could you help me to solve my problem explaining me how to do? I prefer speaking in French but I also understand English well so it should be very easy to understand you.
Thanks in advance for you help.
You should start executing the procedure detailed on the first post and report here the result and the log obtained before, during and after the procedure.
 
Joined
Dec 14, 2019
Messages
3
Reaction score
0
Age
23
OK thank you "Gaucho" I'm gonna do this today and see what happens. I'll let uou know asap I finish or if I've any problem.
 
Joined
Dec 14, 2019
Messages
3
Reaction score
0
Age
23
First off all, nothing is shown when I connect the ground unit via the usb cable to my PC. Same for the unit on my S900, nothing is shown in my DJI Assistant 2. Is it a problem of firmware or bad blocks in the memory, in all case must I follow your first procedure?
 
Joined
Sep 14, 2017
Messages
9
Reaction score
1
Age
29
Hello

Thank you Gaucho for your work. I allready had to reflash many Phantom 2 Vision+ with no image. It worjed always without any problems.

Actually I need to get my RE700 working again. Until now 3 pieces are bricked thanks to the app update.
Is there a way to flash the wm301_repeater_2g_v1 module from the RE700?
I got one working RE700 and 3 bricked RE700.
I think the ddwrt software wasn't flashed correctly during update and now it won't even boot.

I also use a tplink cpe210 with 24v powermodule and 18650 batteries as alternative. But I can't give this solutions to all my friends ;-) there should be an easier way like the RE700 working again.

Thank you in advance

Fabio
Hi

Is there a solution for the P2V+ ground unit after firmwareproblem done by DJI?

Fabio
 
Joined
Feb 9, 2020
Messages
1
Reaction score
0
Age
33
Thank you! My LB is back to life. Is there a solution to do the same procedure with my dji goggles? After a Firmwareupdate my Goggles are not able to get a new firmware. Is it possible to get the same way?
 
Joined
Jun 30, 2016
Messages
1,022
Reaction score
385
Location
PL
Is there a solution to do the same procedure with my dji goggles?
Dji Goggles are basically a cellphone. Completely different technology.
To do anything with cellphone, you need to root it first. Same with goggles.
 
Joined
Feb 16, 2020
Messages
3
Reaction score
0
Age
45
Hi, I have a P2V+ that was sitting on a shelf for around 3 years. Yesterday I've tried it again, as my son seems no no longer be afraid of it :) The problem is that I don't have FPV. Checking and learning about the issues with the NAND and how to fix the bootloader through USB. I've done all of that and it has worked, but the kernel is not booting, I get:

Code:
M36x 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-04-09  12:21:58 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3823424 Bytes = 3.6 MiB
   Load Address: 80008000
   Entry Point:  80008000
## Booting kernel from Legacy Image at 80700000 ...
   Image Name:   Linux-2.6.32.17-davinci1
   Created:      2014-04-09  12:21:58 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3823424 Bytes = 3.6 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Loading Kernel Image ... OK
OK

Starting kernel ...

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)
So the kernel tries to boot but the system resatarts. Any progress with P2V+ kernel? I've seen instructions to flash it through the DJI boot loader but haven't been able to find the right kneel.

Thanks!
 
Joined
Jun 30, 2016
Messages
1,022
Reaction score
385
Location
PL
The kernel which starts booting is a recovery kernel.

Some details on that you'll find in "Finding issues in logs from terminal" chapter in my post:

Recently someone posted a FW which he claimed was from P2Vp. That included kernel and rootfs. Try searching for that post.
 
Joined
Feb 16, 2020
Messages
3
Reaction score
0
Age
45
The kernel which starts booting is a recovery kernel.

Recently someone posted a FW which he claimed was from P2Vp. That included kernel and rootfs. Try searching for that post.
Thank you! I found it at DJI Phantom 2 Vision FC200 EGG camera - Black video FPV solution to fix but it seems that it didn't solve my problem. I was able to flash it using YMODEM and seems to work as now I'm loading the non-recovery kernel:

Code:
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
   Image Name:   Linux-2.6.32.17-davinci1
   Created:      2014-04-09  12:21:58 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3823424 Bytes = 3.6 MiB
   Load Address: 80008000
   Entry Point:  80008000
## Booting kernel from Legacy Image at 80700000 ...
   Image Name:   Linux-2.6.32.17-davinci1
   Created:      2014-04-09  12:21:58 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3823424 Bytes = 3.6 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Loading Kernel Image ... OK
OK

Starting kernel ...

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
But as you see I still get the Starting kernel... and then reboot. I understand that the kernel is not booting as I don't see any message, or could it be the rootfs? Another question. I'm testing all of that with the wifi module alone, I understand that I don't need to connect it to the "other" wifi module in the metal case? Right?
 
Joined
Jun 30, 2016
Messages
1,022
Reaction score
385
Location
PL
I still get the Starting kernel... and then reboot.
Then this must be a hardware issue. Maybe with the RAM chip? I'd try a reflow.

I'm testing all of that with the wifi module alone, I understand that I don't need to connect it to the "other" wifi module in the metal case?
No, definitely not at this time. Some of DJI boards restart when not connected to the rest, but that would happen much later, after basic initialization of internal devices is done and RootFS is mounted. Only then the kernel goes with loading things which may depend on external components.

The bootloader loaded kernel into RAM, and gave it control. If it restarted just after, the kernel in RAM got damaged in the meantime, or some initial hardware initialization failed.
 
Joined
Feb 16, 2020
Messages
3
Reaction score
0
Age
45
In fact looking in detail, the big chip next to the boot select solder points seems to have strange bulges, so probably it is damaged. I don't think that nowadays the drone value is enough to justify replacing that, so probably will have to learn to fly without FPV :/ I'm really disappointed with DJI, the reliability of this thing is appalling. Flight it maybe ten times, and was stored with the batteries out for 3-4 years. The temperature was not fully controlled but was never above or below comfortable limits. Having the hardware failing like that is something I've never seen before in a $1000+ product.

Thanks everybody here, as always the community is orders of magnitude better that then product.
 
Joined
Jun 30, 2016
Messages
1,022
Reaction score
385
Location
PL
the big chip next to the boot select solder points seems to have strange bulges, so probably it is damaged
Maybe. Or maybe it's just the black resin DJI uses to make it harder to figure out the chips they use.
(that's the first time I've seen a large corporation trying to hide the chip models that way; before, I've only seen that done by students when they thought their circuit is so unique and valuable..)

The chips on the usual wiki are covered in resin as well:
 

New Threads

Forum statistics

Threads
137,406
Messages
1,420,249
Members
99,794
Latest member
The scientist