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

Joined
Nov 29, 2018
Messages
10
Reaction score
1
Age
39
ok.so that would be usb controller.that explains no connection at all.but also on the air unit there is no info on any firmware.but they link fine, both leds on air unit go to green, here is the 5th usb cable on 3rd pc :(
 
Joined
Nov 29, 2018
Messages
10
Reaction score
1
Age
39
that was weird. I tried 5-6 USB cables, none worked on lightbridge, but worked just fine on other stuff. I think 7th cable worked, only on rear USB port of the motherboard. Quite sensitive to USB cables :((
 
Joined
Dec 7, 2018
Messages
2
Reaction score
0
Age
35
I used a serial analyzer to see the communication between windows assistant software and the lightbridge. This software helps me a lot to read data: serial port sniffer
 
Last edited:
Joined
Jun 30, 2016
Messages
1,022
Reaction score
385
Location
PL
I used a serial analyzer to see the communication between windows assistant software and the lightbridge
Really? A simple capture tool, which can be easily replaced by free and open-source programs, helped you with understanding the communication?
I can't see information about it supporting DJI protocols; how do you interpret the binary packets?

Here is a free tool which can really read the data, and store individual packets in PCAP file:
comm_serial2pcap.py - o-gs/dji-firmware-tools

The PCAP can then be opened in Wireshark for analysis. You can load DJI dissectors into Wireshak and then _properly_ see the data transferred - packets have types, fields have names etc.
 
Joined
Dec 8, 2018
Messages
1
Reaction score
0
Age
40
Hi all,
All of them desolate for my English I had to use the google translator.

here I use the soft and flash nothing to say the LB works great. By cons I ask myself a question not as much to know that you in the programming is it possible to change the code to connect it on DJI GO or DJI GO 4 with osmo interface or inspire? Because I also use the PI zero version of cosmostreamer that works great too and managed to send them back and the video on the DJI GO app
 
Joined
Oct 31, 2014
Messages
2,008
Reaction score
353
Age
49
Location
Manchester UK
Watching
 
Joined
Jul 13, 2018
Messages
3
Reaction score
0
Age
30
Unfortunately, the Rx pad came off of my ground unit. I tried using the second set of Rx/Tx/GND pads down by the antenna, but the flashing process (which had worked in the past) just repeatedly says "Target:". Can the second set of Rx/Tx/GND pads be used for this process?

Also, I'm connecting the Tx pin on the FT232RL to the Tx pin on the LB -- can someone please confirm that this is correct?
 
Joined
Jan 31, 2019
Messages
2
Reaction score
0
Age
47
CAMERA FC200 (Phantom 2)
Hi i flashed the phantom2 vision fc200 camera but it wasn't good, what image file did you upload to it?

it does not work: sfh_DM36x.exe -nandflash -v -p "COM8" ubl1_editedByGaucho.img u-boot_modifiedByGaucho.img

you have some working img file for you?
 

Attachments

Joined
Jul 13, 2018
Messages
3
Reaction score
0
Age
30
I've used that same image successfully in the past, but only for the standalone Lightbridge ground unit. I've never tried it with any modules from the Phantom...sorry.
 
Joined
Jan 31, 2019
Messages
2
Reaction score
0
Age
47
I've used that same image successfully in the past, but only for the standalone Lightbridge ground unit. I've never tried it with any modules from the Phantom...sorry.
p3P camera board work ,P2V+ work ,this is a smooth fc200 vision cam does not work
 
Joined
Feb 16, 2019
Messages
1
Reaction score
0
Age
32
Hi guys, Lightbridge 1 Air Unit issue here
when trying to run according to steps on page #1 we get this.. (there is mentioned a line containing Target: CORRUPT - what can this mean??)

Code:
-----------------------------------------------------
  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 COM2...
Press any key to end this program at any time.


Waiting for the DM36x...
       Target:
       Target:
       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

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

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

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
When trying to run without bootpin it gives us this. Appears like the NAND is empty.. what can we try to do?

Code:
Target: DM36x initialization passed!
      Target: UBL Product Vesion : DJI-ABP-SUPER-UBL-1.0-rc0(2014-08-25)
      Target: Dji UBL Version: 1.51(Aug 26 2014 - 16:00:24)
      Target: Booting Catalog Boot Loader
      Target: BootMode = NAND
      Target: Starting NAND Copy...
      Target: Valid magicnum, 0xA1ACED66, found in block 0x00000019.
      Target: Valid magicnum, 0xA1ACED66, found in block 0x0000001B.
      Target: Valid magicnum, 0xA1ACED66, found in block 0x0000001D.
      Target: Valid magicnum, 0xA1ACED66, found in block 0x0000001F.
      Target: No valid boot image found!
      Target: NAND Boot failed.
      Target: Aborting...
THANKS IN ADVANCE
 
Joined
Mar 30, 2019
Messages
2
Reaction score
0
Location
Texas Hill Country
I too am having similar issues with the DJI N1 Video Encoder with no video being processed, the solid red/green light and the "no image transmission signal" in the DJI Go App of course. I have this problem on two custom gimbals with DJI N1 Video Encoders, one with a Flir VuePro camera and the other with a 10x optical zoom camera. I have used both numerous times in years past with my Inspire 1. At some point in 2018 they both just stopped working with the first sign being the "no image transmission signal" message in DJI Go and of course, no live video stream. The DJI X3 camera connected to the Inspire 1 gimbal does however still provide video and works as it always had. In researching this I found the no image transmission signal mentioned on numerous forums back into late 2016 but related to the Inspire 1 and no video signal from standard X3 and X5 cameras attached to the Inspire 1 gimbal. The recurrent themes in these threads was that DJI Inspire 1 firmware upgrades were either causing this as a permanent problem or in even more cases what was reported as degraded video performance or reduced range or interference or the like. Most of these threads related to firmware downgrade processes trying to get back to Inspire 1 firmware where the belief was that this problem would be resolved. As the symptoms were similar for me (at least with the N1 encoders no longer providing a video signal out and hence not in the DJI Go app for sure.

So I have spent a bunch of time downgrading trying to see if this would get the two N1 video encoders working again with my Inspire 1 and the DJI Go app. This has not solved my problem with the N1 video encoders nor have I noticed any positive or negative impact on the video signal/video quality in the DJI Go app.

I have heard several comments from developers of recent, coupled with all of the N1 video encoder problems mentioned in this forum as well in several other forums as well, that the problem likely has nothing to do with Inspire 1 firmware versions or Matrice 100 firmware versions for that matter.

What I believe may be happening here is not at all firmware related but perhaps just an expiration of functionality in the DJI N1 Video Encoders. I heard that DJI was not obligated, specifically with the N1 Video Encoder on Inspire 1's, to allow them to function for perpetuity but instead perhaps had some fixed life and have since expired. If these encoders are not working for all of us who have isolated them to ensure they have either a guaranteed analog video signal and/or working/proper HDMI video input and no green light is returned any longer, that the N1 encoders have stopped functioning at least in many reported situations including my own.

Would someone from DJI or other with specific insight into this area please advise, as many of us are chasing our tails here and without the N1 Video Encoders, many of our non DJI solutions (non DJI cameras) no longer work, at least with the Inspire 1. This would a plausible scenario if DJI was interested in limiting 3rd party camera use with the Inspire and/or other DJI platforms.

Thanks in advance!
 
Joined
Jun 30, 2016
Messages
1,022
Reaction score
385
Location
PL
What I believe may be happening here is not at all firmware related but perhaps just an expiration of functionality in the DJI N1 Video Encoders.
Nope. Have you read all the threads you found?

I heard that DJI was not obligated, specifically with the N1 Video Encoder on Inspire 1's, to allow them to function for perpetuity but instead perhaps had some fixed life and have since expired.
No manufacturer is obliged for lifetime warranty, and every device has expected lifespan. Planned obsolescence is an issue with some companies; it is hard to prove though. But companies avoid it nowadays due to serious image losses. I see no evidence of planned obsolescence in Phantoms; though the NAND chips used are definitely not top tier, and someone might have noticed during development that they're a weak spot.

Would someone from DJI
I don't think we have DJI support folks here. Write on DJI forum.

Would someone [...] with specific insight into this area please advise
If you have the ability to fix electronics - diagnose and fix it.
If you don't - pay for a fix or buy a new device.

I made a diagnosis diagram and fix instructions for the issue on Ph3; you can make one for stand-alone lightbridge based on it:
 
Joined
Sep 12, 2019
Messages
16
Reaction score
1
Age
34
Hi i flashed the phantom2 vision fc200 camera but it wasn't good, what image file did you upload to it?

it does not work: sfh_DM36x.exe -nandflash -v -p "COM8" ubl1_editedByGaucho.img u-boot_modifiedByGaucho.img

you have some working img file for you?
I have same problem with Phantom 2 Vision - FC200 camera. If I connect UART Rx TX to Board #3 and run TeraTerm got this msg:

DM36x initialization passed!
TI UBL Version: 1.50
Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000019.
Valid magicnum, 0xA1ACED66, found in block 0x0000001C.
Valid magicnum, 0xA1ACED66, found in block 0x0000001F.
Valid magicnum, 0xA1ACED66, found in block 0x00000022.
Valid magicnum, 0xA1ACED66, found in block 0x00000025.
Valid magicnum, 0xA1ACED66, found in block 0x00000028.
Valid magicnum, 0xA1ACED66, found in block 0x0000002B.
Valid magicnum, 0xA1ACED66, found in block 0x0000002E.
No valid boot image found!
NAND Boot failed.
Aborting...

But there is no chance to run BOOTME on this board. How to get BOOTME state?
 
Joined
Sep 12, 2019
Messages
16
Reaction score
1
Age
34
Finally got BOOTME msg and after flashing here is report:

BOOTME BOOTME BOOTME BOOTME BOOTME BOOTMEř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 #




So, still no working .IMG for FC200 camera?
 
Joined
Jun 30, 2016
Messages
1,022
Reaction score
385
Location
PL
So, still no working .IMG for FC200 camera?
The O-Gs from Github have a lot of old firmwares. You can ask them - they have a Slack group.
Extracting kernel from it would need similar steps to the ones from Phantom 3 described here:
o-gs wiki: Firmware module m0800 structure

And if that won't work - maybe just using kernel from Ph3 would be ok?

For flashing the whole IMG - don't do that; that will damage AT88 data and root file system. You're missing kernel only.
 
Joined
Sep 12, 2019
Messages
16
Reaction score
1
Age
34
The O-Gs from Github have a lot of old firmwares. You can ask them - they have a Slack group.
Extracting kernel from it would need similar steps to the ones from Phantom 3 described here:
o-gs wiki: Firmware module m0800 structure

And if that won't work - maybe just using kernel from Ph3 would be ok?

For flashing the whole IMG - don't do that; that will damage AT88 data and root file system. You're missing kernel only.
Hmm...You mean that I need to find working DaVinci Linux kernel as OS ( at adress 0x900000 uImage_recovery, not included in FW updates; the Linux Kernel which is used when primary kernel gets corrupted ) and flash it with command "sfh_DM36x.exe -nandflash -v -p "COMXX" example.img"?
My working CPU frequency is 432MHz, so it must be DM386.
 
Joined
Jun 30, 2016
Messages
1,022
Reaction score
385
Location
PL
Hmm...You mean that I need to find working DaVinci Linux kernel
Yes.

kernel as OS
Kernel is integral part of every OS, though we usually can't say kernel is the OS. DaVinci Linux is an OS, and it uses Linux kernel.

and flash it with command "sfh_DM36x.exe -nandflash -v -p "COMXX" example.img"?
I don't think `sfh_DM36x` can be used to write anything beyond bootloader. But maybe I'm wrong - you could look in its source and check what it can actually do.
I never tried that. If you somehow could provide it with the destination offset, it would work.

Here's a detailed guide I made for a different board which also has DaVinci:
Fixing flash programming in DM365 chip within GL300 remote controller
 
Joined
Sep 12, 2019
Messages
16
Reaction score
1
Age
34
Yes.



Kernel is integral part of every OS, though we usually can't say kernel is the OS. DaVinci Linux is an OS, and it uses Linux kernel.



I don't think `sfh_DM36x` can be used to write anything beyond bootloader. But maybe I'm wrong - you could look in its source and check what it can actually do.
I never tried that. If you somehow could provide it with the destination offset, it would work.

Here's a detailed guide I made for a different board which also has DaVinci:
Fixing flash programming in DM365 chip within GL300 remote controller
Many thanks for great info. I will try to find working kernel for this board. If you think or/and have kernel for P3 with smilar HW, pls post it here, so I can try.
 
Joined
Sep 12, 2019
Messages
16
Reaction score
1
Age
34
I just try to flash with gl300_dm365_recovery_kernel using ZMODEM and here is result:

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: 2015-02-12 3:09:59 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3665856 Bytes = 3.5 MiB
Load Address: 80008000
Entry Point: 80008000
## Booting kernel from Legacy Image at 80700000 ...
Image Name: Linux-2.6.32.17-davinci1
Created: 2015-02-12 3:09:59 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3665856 Bytes = 3.5 MiB
Load Address: 80008000
Entry Point: 80008000
Loading Kernel Image ... OK
OK

Starting kernel ...

[ 0.000000] Kernel Product Vesion : DJI-GRC-Kernel-1.0-rc8(2014-11-21)
[ 0.000000] Linux version 2.6.32.17-davinci1 ([email protected]) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 PREEMPT Thu Feb 12 11:09:57 HKT 2015
[ 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:eek:sd0=1920x1080X16,8100K mem=48MB davinci_enc_mngr.ch0_out
[ 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: 44836KB available (3304K code, 409K data, 108K 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.080000] bio: create slab <bio-0> at 0
[ 0.080000] SCSI subsystem initialized
[ 0.090000] usbcore: registered new interface driver usbfs
[ 0.090000] usbcore: registered new interface driver hub
[ 0.090000] usbcore: registered new device driver usb
[ 0.100000] cfg80211: Using static regulatory domain info
[ 0.100000] cfg80211: Regulatory domain: US
[ 0.100000] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 0.100000] (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
[ 0.100000] (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 0.100000] (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 0.100000] (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 0.100000] (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 0.100000] (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[ 0.100000] cfg80211: Calling CRDA for country: US
[ 0.100000] Switching to clocksource timer0_1
[ 0.110000] musb_hdrc: version 6.0, pio, host, debug=0
[ 0.130000] musb_hdrc: USB Host mode controller at fec64000 using PIO, IRQ 12
[ 0.130000] musb_hdrc musb_hdrc: MUSB HDRC host driver
[ 0.130000] musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
[ 0.130000] usb usb1: configuration #1 chosen from 1 choice
[ 0.130000] hub 1-0:1.0: USB hub found
[ 0.130000] hub 1-0:1.0: 1 port detected
[ 0.130000] NET: Registered protocol family 2
[ 0.130000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.130000] TCP established hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.130000] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.130000] TCP: Hash tables configured (established 2048 bind 2048)
[ 0.130000] TCP reno registered
[ 0.130000] NET: Registered protocol family 1
[ 0.130000] RPC: Registered udp transport module.
[ 0.130000] RPC: Registered tcp transport module.
[ 0.130000] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.140000] kfile init
[ 0.140000] JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 0.140000] msgmni has been set to 87
[ 0.150000] alg: No test for stdrng (krng)
[ 0.150000] io scheduler noop registered (default)
[ 0.210000] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 0.210000] serial8250.0: ttyS0 at MMIO 0x1c20000 (irq = 40) is a 16550A
[ 0.580000] davinci_interrupt 368: VBUS error workaround (delay coming)
[ 0.590000] console [ttyS0] enabled
[ 0.590000] serial8250.0: ttyS1 at MMIO 0x1d06000 (irq = 41) is a 16550A
[ 0.610000] brd: module loaded
[ 0.610000] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xf1 (Micron NAND 128MiB 3,3V 8-bit)
[ 0.620000] Creating 4 MTD partitions on "davinci_nand.0":
[ 0.630000] 0x000000000000-0x0000004a0000 : "bootloader"
[ 0.640000] 0x0000004a0000-0x000000e00000 : "kernel"
[ 0.650000] 0x000000e00000-0x000007f00000 : "filesystem"
[ 0.650000] 0x000000000000-0x000008000000 : "all"
[ 0.660000] davinci_nand davinci_nand.0: controller rev. 2.3
[ 0.670000] UBI: attaching mtd2 to ubi0
[ 0.680000] UBI: physical eraseblock size: 131072 bytes (128 KiB)
[ 0.680000] UBI: logical eraseblock size: 126976 bytes
[ 0.690000] UBI: smallest flash I/O unit: 2048
[ 0.690000] UBI: sub-page size: 512
[ 0.700000] UBI: VID header offset: 2048 (aligned 2048)
[ 0.700000] UBI: data offset: 4096
[ 0.710000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 0:0, read 64 bytes
[ 0.720000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 0:2048, read 512 bytes
[ 0.730000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 1:0, read 64 bytes
[ 0.740000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 1:2048, read 512 bytes
[ 0.750000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 2:0, read 64 bytes
[ 0.760000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 2:2048, read 512 bytes
[ 0.770000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 3:0, read 64 bytes
[ 0.770000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 3:2048, read 512 bytes
[ 0.780000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 4:0, read 64 bytes
[ 0.790000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 4:2048, read 512 bytes
[ 0.800000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 5:0, read 64 bytes
[ 0.810000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 5:2048, read 512 bytes
[ 0.820000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 6:0, read 64 bytes
[ 0.830000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 6:2048, read 512 bytes
[ 0.840000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 7:0, read 64 bytes
[ 0.850000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 7:2048, read 512 bytes
[ 0.860000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 8:0, read 64 bytes
[ 0.870000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 8:2048, read 512 bytes
[ 0.880000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 9:0, read 64 bytes
[ 0.890000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 9:2048, read 512 bytes
[ 0.900000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 10:0, read 64 bytes
[ 0.910000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 11:0, read 64 bytes
[ 0.920000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 11:2048, read 512 bytes
[ 0.930000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 12:0, read 64 bytes
[ 0.930000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 12:2048, read 512 bytes
[ 0.940000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 13:0, read 64 bytes
[ 0.950000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 13:2048, read 512 bytes
[ 0.960000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 14:0, read 64 bytes
[ 0.970000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 14:2048, read 512 bytes
[ 0.980000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 15:0, read 64 bytes
[ 0.990000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 15:2048, read 512 bytes
[ 1.000000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 16:0, read 64 bytes
[ 1.010000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 16:2048, read 512 bytes
[ 1.020000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 17:0, read 64 bytes
[ 1.030000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 17:2048, read 512 bytes
[ 1.040000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 18:0, read 64 bytes
[ 1.050000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 18:2048, read 512 bytes
[ 1.060000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 19:0, read 64 bytes
[ 1.070000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 19:2048, read 512 bytes
[ 1.080000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 20:0, read 64 bytes
[ 1.090000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 20:2048, read 512 bytes
[ 1.100000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 21:0, read 64 bytes
[ 1.110000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 21:2048, read 512 bytes
[ 1.120000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 22:0, read 64 bytes
[ 1.120000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 22:2048, read 512 bytes
[ 1.130000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 23:0, read 64 bytes
[ 1.140000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 23:2048, read 512 bytes
[ 1.150000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 24:0, read 64 bytes
[ 1.160000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 24:2048, read 512 bytes
[ 1.170000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 25:0, read 64 bytes
[ 1.180000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 25:2048, read 512 bytes
[ 1.190000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 26:0, read 64 bytes
[ 1.200000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 26:2048, read 512 bytes
[ 1.210000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 27:0, read 64 bytes
[ 1.220000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 27:2048, read 512 bytes
[ 1.230000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 28:0, read 64 bytes
[ 1.240000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 28:2048, read 512 bytes
[ 1.250000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 29:0, read 64 bytes
[ 1.260000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 29:2048, read 512 bytes
[ 1.270000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 30:0, read 64 bytes
[ 1.280000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 30:2048, read 512 bytes
[ 1.290000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 31:0, read 64 bytes
[ 1.300000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 31:2048, read 512 bytes
[ 1.310000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 32:0, read 64 bytes
[ 1.320000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 32:2048, read 512 bytes
[ 1.320000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 33:0, read 64 bytes
[ 1.330000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 33:2048, read 512 bytes
[ 1.340000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 34:0, read 64 bytes
[ 1.350000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 34:2048, read 512 bytes
[ 1.360000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 35:0, read 64 bytes
[ 1.370000] UBI error: ubi_io_read: error -74 while reading 512 bytes from PEB 35:2048, read 512 bytes
[ 1.380000] UBI error: ubi_io_read: error -74 while reading 64 bytes from PEB 36:0, read 64 bytes
[ 1.390000] UBI error: process_eb: bad image sequence number 248044948 in PEB 36, expected 1667215269
[ 1.400000] UBI error: ubi_init: cannot attach mtd2
[ 1.410000] UBI error: ubi_init: UBI error: cannot initialize UBI, error -22
[ 1.420000] console [netcon0] enabled
[ 1.420000] netconsole: network logging started
[ 1.420000] Initializing USB Mass Storage driver...
[ 1.430000] usbcore: registered new interface driver usb-storage
[ 1.440000] USB Mass Storage support registered.
[ 1.440000] usbcore: registered new interface driver usbtest
[ 1.450000] i2c /dev entries driver
[ 1.450000] watchdog watchdog: heartbeat 1 sec
[ 1.460000] TCP cubic registered
[ 1.460000] NET: Registered protocol family 17
[ 1.470000] lib80211: common routines for IEEE802.11 drivers
[ 1.470000] ksocket init
[ 2.400000] encrypt device:at88 found
[ 2.730000] davinci_interrupt 368: VBUS error workaround (delay coming)
[ 4.880000] davinci_interrupt 368: VBUS error workaround (delay coming)
[ 7.030000] davinci_interrupt 368: VBUS error workaround (delay coming)
 

New Threads

Forum statistics

Threads
137,417
Messages
1,420,334
Members
99,799
Latest member
cwarren2485