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

[Artur73]

and here is log from hiperterminal

 BOOTDM36x initialization passed!
UBL Product Vesion : DJI-GSPv2-UBL-1.0-rc6(2014-08-15)
Dji UBL Version: 1.51(Aug 15 2014 - 16:40:46)
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...
DM36x initialization passed!
UBL Product Vesion : DJI-GSPv2-UBL-1.0-rc6(2014-08-15)
Dji UBL Version: 1.51(Aug 15 2014 - 16:40:46)
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...

 

[canemo]

hi Gaucho, i realized you are the wizard of ground stations.... cool. Maybe you could fix an air unit... can you help us ?? What's the state-of-art about that ? thanks anyway...

 

[gaucho]

Artur in the procedure i wrote : hit Ctrl +c and relaunch the command. Check it and do it right. Let me know

 

[Artur73]

Gaucho I relaunch many time , but it same results.

 

[gaucho]

Gaucho I relaunch many time , but it same results.

I can tell you to try with older pc and with Windows xp.
I can tell you to check your serial interface device
I can tell you to launch the command, then power it on, then if it stops, hit Ctrl+C and relaunch the command. If the command goes fine you Will see a slow file upload on a progress bar inside the command prompt window . Slow upload.

 

[danielh]

Ground unit has been fixed.
But my air unit has the same problem. following the same way.it doesn't work.
I'm sure all the pin is in the right place. I can get message from the serial port. But firmware can't be upload.
Same as Artur73.
Know a little linux and electric. I'm sure it is the uboot firmware is not the same.
I hope some people can help.

 

[gaucho]

If you have time, try what i suggested: find how to backup the upgrade file. If you get that file, We Will decrypt it. When i Will have time i Will do it if no one else meanwhile have done it.

 

[danielh]

I don't have a working air unit. So I can't get the upgrade file.

 

[Artur73]

Danielh I slove my problem. I do this type. I run launch the command and power on LB. When the tool continues to print BOOTME BOOTME, turn off LB ,but dont close terminal and power on LB. that way it begin upload firmware

 

[danielh]

Thank You.
But What I got is different.
Always show target corupt.

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

 

[danielh]

without shorting the bsel and 3v3.
I got

DM36x initialization passed!
UBL Product Vesion : DJI-UBL-1.0-rc2
Dji UBL Version: 1.51(Jan  7 2014 - 18:30:59)
Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000019.
Valid magicnum, 0xA1ACED66, found in block 0x0000001B.
Valid magicnum, 0xA1ACED66, found in block 0x0000001D.
Valid magicnum, 0xA1ACED66, found in block 0x0000001F.
No valid boot image found!
NAND Boot failed.
Aborting...

bsel and 3v3 shorting I got

BOOTME BOOTME BOOTME BOOTME BOOTME BOOTME BOOTME BOOTME BOOTME BOOTME BOOTME BOOTME BOOTME BOOTME BOOTME BOOTME BOOTME BOOTME BOOTME BOOTME BOOTME BOOTME

 

[danielh]

Danielh I slove my problem. I do this type. I run launch the command and power on LB. When the tool continues to print BOOTME BOOTME, turn off LB ,but dont close terminal and power on LB. that way it begin upload firmware

How do you wire the cable? Same as "ceejay"?
Your result is different from mine. Maybe we have different problem.

 

[SimSim]

Seems that DJI is using a broadcast OFDM for Video TX and FHSS for control commands.
Any leads regarding the communication protocols implemented in HW and Chip-sets used, will be more than welcomed.
Some initial discussions can be seen here:
RC Radio Frequency

Many thanks in Advance.

 

[Artur73]

How do you wire the cable? Same as "ceejay"?
Your result is different from mine. Maybe we have different problem.

Danielh share your connections pictures I will check

 

[danielh]

Danielh share your connections pictures I will check

same as this

 

[alex998r]

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

 

[Vanni Mastrantonio]

Ok, I got a question.
Can I be able to flash NAND, by the upgrade USB port if I make short circuit with 3.3 and bsel?
I try without the short circuit and the program find the unit, so if I make the short circuit it have to work, right?

 

[kurkovda]

Hi!
Got the same issue with my LB, made all the neccessary actions with hardware and software, but when the LB starts after flashing i get a strange log in the terminal with a bootloop:

Spoiler: Termial log

[ 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

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)

Could you please help with this, or it's a problem on my side?
Thanks!

 

[gaucho]

Ok, I got a question.
Can I be able to flash NAND, by the upgrade USB port if I make short circuit with 3.3 and bsel?
I try without the short circuit and the program find the unit, so if I make the short circuit it have to work, right?

No, because the upgrade serial port is a virtual port enabled by the firmware only if everything works.
Moreover that serial line is not available during boot phase

 

[gaucho]

Hi!
Got the same issue with my LB, made all the neccessary actions with hardware and software, but when the LB starts after flashing i get a strange log in the terminal with a bootloop:

Spoiler: Termial log

[ 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

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)

Could you please help with this, or it's a problem on my side?
Thanks!

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?