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

gaucho · May 30, 2017

raven8 said:
Weldings is ok. Cleaned with alcohol from soldering paste and not shorted with ground.
Ascii characters comes with one of the spare FTDI what i test.
3,3v jumped on the FTDI.. and i also test voltage btw vcc and ground on FTDI outbut - 3.3v, so, should be ok.
When i hit ctrl+с and relaunch nothing happen. No bootme command, so i have to restart LB. After restart everything is same.

Here is with good FTDI... just try again now.

Did you also tried power cycling your device when it stops? Leave the command running on pc , don't touch the pc

What is your windows version? Try with 32 bit version

raven8 · May 30, 2017

When i power cycling LB after stop i have BOOTME message.
Will try today with 32 bit windows version... now i am on Win7 64bit

carlos eduardo diaz · May 31, 2017

gaucho said:
Did you also tried power cycling your device when it stops? Leave the command running on pc , don't touch the pc

What is your windows version? Try with 32 bit version

hi gaucho

As I can correct the message of target corrupt, check the connections and the welds, everything is ok. I managed to recover the earth unit but I have not managed to correct the air. Can you tell me the way to go

gaucho · Jun 1, 2017

@carlos : if you follow exactly what I wrote on the procedure, I don't know why you get the corrupt message. I remember you had the same problem on the ground unit. How did you solved the problem for the ground unit?
What serial adapter are you using?
Post a picture of the serial adapter

raven8 · Jun 1, 2017

I try another computers... win32.. sadenly with no result...
program stop at - Waiting sendimg sequence.
Any suggestions?
Maybe someone have spare ground station in this thread? Will be happy to buy...

Marlow · Jun 1, 2017

Hi,

3 of my 4 air modules have failed (all Lightbridge 1). All with above failure. Now, not quite. One I bought 2nd hand and it arrived in that state.

Here's the odd one. I've followed the instructions and I can see console output etc.

Two of the modules fail on daVinci i2c bus timeouts. Very similar error messages to eachother. Both report 2 bad blocks during boot and then boot into default environment.

The 3rd is an oddball. It simply tells me, that there was NO valid NAND image to boot. That's it.

When I try to flash them, the initial bar progresses to 100%, then I get this:

-----------------------------------------------------
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 COM45...
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: CORRUPT
Target: BOOTME

Waiting for the DM36x...
Target: BOOTME
BOOTME commmand received. Returning ACK and header...
ACK command sent. Waiting for BEGIN command...
Target: BOOTME

Waiting for the DM36x...
Target: BOOTME
BOOTME commmand received. Returning ACK and header...
ACK command sent. Waiting for BEGIN command...
Target: BOOTME

It's the same for all three. I've tried to restart the script, power cycling the unit, doesn't matter. Neither of the 3 will flash.

Any ideas ?

Oh .. and I've tried both on Windows XP 32-bit and Windows 7 64-bit. It doesn't seem to make a difference. The USB to Serial board i use is the exact same as in the first post.

/M

carlos eduardo diaz · Jun 4, 2017

gaucho said:
@carlos : if you follow exactly what I wrote on the procedure, I don't know why you get the corrupt message. I remember you had the same problem on the ground unit. How did you solved the problem for the ground unit?
What serial adapter are you using?
Post a picture of the serial adapter

Hello my friend thank you very much, I have achieved it after many attempts, you are a genius

giannihsd · Jun 5, 2017

@gaucho Hi,

I have order a new module, and I have replaced.
I think the one I have is old model but if you want I can post some photos.

The new is this:

$_57

giannihsd
Jun 5, 2017

Avijobo · Jun 6, 2017

wtercato said:
Hi.

I checked the wires, connections, drivers, did the same processing on another computer, but the result was the same as the images I sent earlier.

As I said, the ground unit worked perfectly whit this procedure, but the air unit is giving this problem.
I see the .bin file that was created, in the main folder, after the procedure and inside it has a log:
----
initialization passed!
TI SFT Version: 1.50
Booting Catalog Serial Flasher
DONE Unprotect failed
NAND is write protected!
Number of blocks needed for header and data: 0x NAND block is bad!!!
No good blocks in allowed range!!!
Attempting to start in block number 0x Erase failed
Writing header and image data to Block , Page Write failed!
Write verify failed!
Write failed, skipping block!
Write verify failed, skipping block!
SENDIMG ACK 0000 BADCNT BADADDR BEGIN
UART Receive Error
Starting UART Boot...
BOOTUBL CMD NAND_open() failed! Writing UBL to NAND flash
Writing failed! Writing APP to NAND flash
Erase failed.
Erase completed successfully.
Boot command not supported! H6 DM36x Protecting the entire NAND flash.
Unprotecting blocks through Erasing block Bad Block NO
Erasing is skipped
Erase verification failed! Block: page: . First Failing Byte: Data verification failed! Block:
----

Accompanied by several indecipherable characters.

thank you

I have exactly the same problem... LB ground unit procedure worked like a charm, LB air unit procedure does not work here, tried everything as described... no success

Avijobo · Jun 7, 2017

Avijobo said:
I have exactly the same problem... LB ground unit procedure worked like a charm, LB air unit procedure does not work here, tried everything as described... no success

No ideas anymore... anyone? I use a Windows XP 32b computer, by the way.

bortoman · Jun 26, 2017

Hi,
first of all I want to thank the guys who put so much effort in analyzing this issue and finding a solution!

I have the issue with my air-unit and I'm not able to get it to work...
(maybe I have done something wrong)

Here are my weldings:

This is what i see in the command prompt:

when i power cycle the air-unit two lines "Target:" are added, but nothing else happenes, I am on a Win7 32bit OS

If anyone has a suggestion/solution for me I would be very grateful!

Kind regards
Manuel

mazo78 · Jun 26, 2017

my phantom 2 vision plus redy for fly with live view

mazo78 · Jun 26, 2017

Some modification in my phantom 2 vision plus for Easy NAND Flashing

Andrejka · Jun 30, 2017

giannihsd said:
hi,

after flash and remove jumper, in teraterm I have:

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
** Unknown image type
Wrong Image Format for bootm command
ERROR: can't get kernel image!
Dji-Pro #

I must replace the board????

Hello,

After reflashing I have same message as above. This mean that NAND chip is totally unusable?

Thanks

Andrej

MacGyver · Jul 1, 2017

Hi Gaucho,

We have taken notice of the exceptional LB reverse engineering you've done and would like to discuss an opportunity to involve you in short-term or long-term lucratively paid LB consulting. Due to the open nature of this posting we can not post direct contact info. Drop a note to us at [email protected]. I hope you take this request very seriously.

All the best,
M.

poohnap4el · Jul 3, 2017

Gaucho, hi!

After reflashing, error occurs: ERROR: can't get kernel image

What i can to do with it?
From the topic, I realized that we need to clear the memory, but how - I did not find it.

jdpowell · Jul 3, 2017

I just thought I would post that I received the USB to serial adapter today, reflashed the board per the instructions here and my video is working again. I had to run the command line entries a few times before the memory actually was flashed. I have to wonder if heat is really the problem because my Phantom was just setting in the case for several months and when I got it out the video feed was gone.