We changed the NAND on the board, the first time the load exceeded 90%, but ended in failure. The second time they started to flash and again the download reaches 90% and stops. I do everything according to the instructions, but again failure. Don't know what to do anymore? Try to put another NAND?
lightbridge firmware PROBLEM (and solution) - firmware version not found by dji assistant tool
- Thread starter gaucho
- Start date
If you're powering the board from USB, try using normal supply instead.
You may also try reflow the Davinci chip.
Other than that - figuring this out would require checking on which specific instruction the flashing stopped, and what that means. Not an easy route.
You may also try reflow the Davinci chip.
Other than that - figuring this out would require checking on which specific instruction the flashing stopped, and what that means. Not an easy route.
Hi, I´ve got a problem with downloading the annexed file, site report it´s not longer available.
- Joined
- Apr 14, 2015
- Messages
- 294
- Reaction score
- 36
- Age
- 74
It works. Try to change browser or follow the instructions on the post by replacing https with http
Hey, anyone who Can repair my groundstation in the european area? I am from germany. Best greethings
- Joined
- Apr 14, 2015
- Messages
- 294
- Reaction score
- 36
- Age
- 74
Hi MCHammer, yes i can, I am in the euro zone. Write to me in private.
So sorry to bother you guys but I have a problem!!
I was doing the repair and soldered all the cables in place. When I turned the unit over the weight of one cable was enough to totally rip off the Tx pad on the air unit
I should have taped them down!
Question is does anyone know which of the two boards hold the nand chip? I was thinking if I'm lucky and chip is on undamaged bottom part board i could use my second air unit and borrow its board for the flash procedure. Or is there any other spot I can get to the Tx
I'm kicking myself here.
Thanks!
I was doing the repair and soldered all the cables in place. When I turned the unit over the weight of one cable was enough to totally rip off the Tx pad on the air unit
I should have taped them down!Question is does anyone know which of the two boards hold the nand chip? I was thinking if I'm lucky and chip is on undamaged bottom part board i could use my second air unit and borrow its board for the flash procedure. Or is there any other spot I can get to the Tx
I'm kicking myself here.
Thanks!
thanks, gaucho for your availability to all of us. I have two lightbridges, one of which I broke the rx pin during soldering. Is it possible to take the rx contact from another part of the card? thank you Francis
Hello,
i tried to use my LB today after years…without succes.
I guess the firmware on both the ground and air unit needs to be flashed.
Can anyone in EU do this?
I will send the LB in original packing, it looks like at the first day.
It would be a pain to throw away the precious gadget of 2015 ;-)
please reply by email to [email protected]
i tried to use my LB today after years…without succes.
I guess the firmware on both the ground and air unit needs to be flashed.
Can anyone in EU do this?
I will send the LB in original packing, it looks like at the first day.
It would be a pain to throw away the precious gadget of 2015 ;-)
please reply by email to [email protected]
- Joined
- Apr 14, 2015
- Messages
- 294
- Reaction score
- 36
- Age
- 74
Did you solved it? When i will open it again I will let you know. For sure we will Find the new point to solder. Ground unit or air unit? I can Also do it for you at the same price of a repair mentioned in the first post.
Anybody had any success running assistant on windows 10? i did reflash few times, every time everything was ok, now both ground and air unit are not recognized in Windows 10. Disabled LUA, installed DJI drivers, disabled driver signature.....
- Joined
- Apr 14, 2015
- Messages
- 294
- Reaction score
- 36
- Age
- 74
May be something changed in Windows10. I used it on windows10. Did you try my tool? Can you see data flowing on the serial usb port? May be something related to usb
Hello everyone,
Thank you Gaucho for your great work.
I was able to get my two Lightbridge Ground Units and the Air Unit working again. The flashing process worked without any issues on Windows 10 64-bit. After flashing, the HDMI output and the USB output have worked and displaying an image. However, I now have the problem that the Assistant Software doesn't recognize the Ground Unit or the Air Unit. This making it impossible for me to calibrate and assign the channels.
Does anyone have an idea of what could be causing this? The serial port appears when I plug them in and I also have access to the Linux system through the console.
At the beginning of the thread it was said that all boards with image processing use the same boot image. So I removed the defective HDMI/AV board from my Zenmuse Z15 A7 and searched for the correct pins. When I saw the same error in the terminal as initially with the LB (Doesn't boot because the boot image wasn't found), I promptly flashed it with the LB's image. Following the motto, it couldn't get any worse. To my delight, the flashing process worked without any issues and the AV/HDMI board is now functioning properly and visible in the Assistant Software. Attached is a picture of the contacts on the A7 HDMI/AV board, as well as the boot log and flash log after flashing.
Since this worked so well, I also tried flashing the board from the broken Zenmuse Z15 5D III (HD). However, it seems to have a bigger problem as after about 15 seconds, the console displays garbled characters. After the board is disconnected from the power supply for a longer period of time (approx. 2 hours), it works again for 15 seconds before it ends in garbled characters. Maybe someone here also has an idea of what could be causing that. The pins on the board are labeled and the debug pins are U1_RX and U1_TX.
Thank you Gaucho for your great work.
I was able to get my two Lightbridge Ground Units and the Air Unit working again. The flashing process worked without any issues on Windows 10 64-bit. After flashing, the HDMI output and the USB output have worked and displaying an image. However, I now have the problem that the Assistant Software doesn't recognize the Ground Unit or the Air Unit. This making it impossible for me to calibrate and assign the channels.
Does anyone have an idea of what could be causing this? The serial port appears when I plug them in and I also have access to the Linux system through the console.
At the beginning of the thread it was said that all boards with image processing use the same boot image. So I removed the defective HDMI/AV board from my Zenmuse Z15 A7 and searched for the correct pins. When I saw the same error in the terminal as initially with the LB (Doesn't boot because the boot image wasn't found), I promptly flashed it with the LB's image. Following the motto, it couldn't get any worse. To my delight, the flashing process worked without any issues and the AV/HDMI board is now functioning properly and visible in the Assistant Software. Attached is a picture of the contacts on the A7 HDMI/AV board, as well as the boot log and flash log after flashing.
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
** 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-11-12 6:42:26 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3840448 Bytes = 3.7 MiB
Load Address: 80008000
Entry Point: 80008000
## Booting kernel from Legacy Image at 80700000 ...
Image Name: Linux-2.6.32.17-davinci1
Created: 2014-11-12 6:42:26 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3840448 Bytes = 3.7 MiB
Load Address: 80008000
Entry Point: 80008000
Loading Kernel Image ... OK
OK
Starting kernel ...
[ 0.000000] Kernel Product Vesion : DJI-Kernel-1.1-rc1
[ 0.000000] Linux version 2.6.32.17-davinci1 (root@u-desktop) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #5 PREEMPT Wed Nov 12 14:42:20 CST 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,10K:osd0=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: 44640KB available (3472K code, 439K data, 112K 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: HD imager video input
[ 0.030000] sw gpio29 value:0
[ 0.100000] bio: create slab <bio-0> at 0
[ 0.100000] DM365 IPIPE initialized in Continuous mode
[ 0.110000] usbcore: registered new interface driver usbfs
[ 0.110000] usbcore: registered new interface driver hub
[ 0.110000] usbcore: registered new device driver usb
[ 0.110000] vpss vpss: dm365_vpss vpss probed
[ 0.110000] vpss vpss: dm365_vpss vpss probe success
[ 0.110000] dm365_afew_hw_init
[ 0.120000] ch0 default output "COMPOSITE", mode "PAL"
[ 0.120000] VPBE Encoder Initialized
[ 0.120000] cfg80211: Using static regulatory domain info
[ 0.120000] cfg80211: Regulatory domain: US
[ 0.120000] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 0.120000] (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
[ 0.120000] (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 0.120000] (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 0.120000] (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 0.120000] (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 0.120000] (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[ 0.120000] cfg80211: Calling CRDA for country: US
[ 0.120000] LogicPD encoder initialized
[ 0.120000] Switching to clocksource timer0_1
[ 0.130000] musb_hdrc: version 6.0, pio, host, debug=0
[ 0.150000] musb_hdrc: USB Host mode controller at fec64000 using PIO, IRQ 12
[ 0.150000] musb_hdrc musb_hdrc: MUSB HDRC host driver
[ 0.150000] musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
[ 0.150000] usb usb1: configuration #1 chosen from 1 choice
[ 0.150000] hub 1-0:1.0: USB hub found
[ 0.150000] hub 1-0:1.0: 1 port detected
[ 0.150000] NET: Registered protocol family 2
[ 0.150000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.150000] TCP established hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.150000] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.150000] TCP: Hash tables configured (established 2048 bind 2048)
[ 0.150000] TCP reno registered
[ 0.150000] NET: Registered protocol family 1
[ 0.150000] RPC: Registered udp transport module.
[ 0.150000] RPC: Registered tcp transport module.
[ 0.150000] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.160000] JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 0.160000] msgmni has been set to 87
[ 0.170000] alg: No test for stdrng (krng)
[ 0.170000] io scheduler noop registered (default)
[ 0.210000] davincifb davincifb.0: dm_osd0_fb: Initial window configuration is invalid.
[ 0.290000] Console: switching to colour frame buffer device 240x67
[ 0.380000] davincifb davincifb.0: dm_osd0_fb: 1920x1080x16@0,0 with framebuffer size 8100KB
[ 0.380000] davincifb davincifb.0: dm_vid0_fb: 0x0x16@0,0 with framebuffer size 10KB
[ 0.380000] davincifb davincifb.0: dm_osd1_fb: 720x576x4@0,0 with framebuffer size 810KB
[ 0.390000] davincifb davincifb.0: dm_vid1_fb: 0x0x16@0,0 with framebuffer size 10KB
[ 0.450000] DM365 IPIPEIF probed
[ 0.450000] imp serializer initialized
[ 0.450000] davinci_previewer initialized
[ 0.450000] davinci_resizer initialized
[ 0.450000] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 0.460000] serial8250.0: ttyS0 at MMIO 0x1c20000 (irq = 40) is a 16550A
[ 0.920000] console [ttyS0] enabled
[ 0.920000] serial8250.0: ttyS1 at MMIO 0x1d06000 (irq = 41) is a 16550A
[ 0.930000] brd: module loaded
[ 0.940000] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xf1 (Micron NAND 128MiB 3,3V 8-bit)
[ 0.950000] Creating 4 MTD partitions on "davinci_nand.0":
[ 0.960000] 0x000000000000-0x0000004a0000 : "bootloader"
[ 0.970000] 0x0000004a0000-0x000000e00000 : "kernel"
[ 0.970000] 0x000000e00000-0x000007f00000 : "filesystem"
[ 0.980000] 0x000000000000-0x000008000000 : "all"
[ 0.990000] davinci_nand davinci_nand.0: controller rev. 2.3
[ 1.000000] UBI: attaching mtd2 to ubi0
[ 1.000000] UBI: physical eraseblock size: 131072 bytes (128 KiB)
[ 1.010000] UBI: logical eraseblock size: 126976 bytes
[ 1.020000] UBI: smallest flash I/O unit: 2048
[ 1.020000] UBI: sub-page size: 512
[ 1.020000] UBI: VID header offset: 2048 (aligned 2048)
[ 1.030000] UBI: data offset: 4096
[ 1.510000] UBI: attached mtd2 to ubi0
[ 1.520000] UBI: MTD device name: "filesystem"
[ 1.520000] UBI: MTD device size: 113 MiB
[ 1.530000] UBI: number of good PEBs: 904
[ 1.530000] UBI: number of bad PEBs: 0
[ 1.540000] UBI: max. allowed volumes: 128
[ 1.540000] UBI: wear-leveling threshold: 4096
[ 1.550000] UBI: number of internal volumes: 1
[ 1.550000] UBI: number of user volumes: 1
[ 1.550000] UBI: available PEBs: 0
[ 1.560000] UBI: total number of reserved PEBs: 904
[ 1.560000] UBI: number of PEBs reserved for bad PEB handling: 9
[ 1.570000] UBI: max/mean erase counter: 60/1
[ 1.570000] UBI: image sequence number: 1231824996
[ 1.580000] UBI: background thread "ubi_bgt0d" started, PID 313
[ 1.620000] UBI: scrubbed PEB 168 (LEB 2147479551:0), data moved to PEB 900
[ 1.650000] UBI: scrubbed PEB 169 (LEB 2147479551:1), data moved to PEB 899
[ 1.660000] console [netcon0] enabled
[ 1.670000] netconsole: network logging started
[ 1.670000] i2c /dev entries driver
[ 1.680000] Linux video capture interface: v2.00
[ 1.680000] vpfe_init
[ 1.690000] vpfe-capture: vpss clock vpss_master enabled
[ 1.690000] vpfe-capture vpfe-capture: v4l2 device registered
[ 1.700000] vpfe-capture vpfe-capture: video device registered
[ 1.710000] EVM: switch to tvp5151 cvbs video input
[ 1.710000] vpfe-capture vpfe-capture: v4l2 sub device tvp5150 registered
[ 1.720000] EVM: switch to it6604 hdmi video input
[ 1.730000] vpfe-capture vpfe-capture: v4l2 sub device cat6023 registered
[ 1.740000] vpfe_register_ccdc_device: DM365 ISIF
[ 1.750000] DM365 ISIF is registered with vpfe.
[ 1.750000] Trying to register davinci display video device.
[ 1.760000] layer=c106c400,layer->video_dev=c106c564
[ 1.770000] Trying to register davinci display video device.
[ 1.770000] layer=c106c800,layer->video_dev=c106c964
[ 1.780000] davinci_init:DaVinci V4L2 Display Driver V1.0 loaded
[ 1.780000] watchdog watchdog: heartbeat 1 sec
[ 1.790000] TCP cubic registered
[ 1.790000] NET: Registered protocol family 17
[ 1.800000] lib80211: common routines for IEEE802.11 drivers
[ 2.440000] encrypt device:at88 found
[ 2.480000] Clocks: disable unused mmcsd0
[ 2.480000] Clocks: disable unused mmcsd1
[ 2.480000] Clocks: disable unused spi0
[ 2.480000] Clocks: disable unused spi1
[ 2.480000] Clocks: disable unused spi2
[ 2.480000] Clocks: disable unused spi3
[ 2.480000] Clocks: disable unused spi4
[ 2.480000] Clocks: disable unused pwm0
[ 2.480000] Clocks: disable unused pwm1
[ 2.480000] Clocks: disable unused pwm2
[ 2.480000] Clocks: disable unused pwm3
[ 2.480000] Clocks: disable unused timer1
[ 2.480000] Clocks: disable unused timer3
[ 2.480000] Clocks: disable unused emac
[ 2.480000] Clocks: disable unused voice_codec
[ 2.480000] Clocks: disable unused asp0
[ 2.480000] Clocks: disable unused rto
[ 2.480000] Clocks: disable unused mjcp
[ 2.550000] nnnn===0
[ 2.550000] davinci_emac_probe: using random MAC addr: ca:20:be:26:b0:40
[ 2.560000] emac-mii: probed
[ 2.600000] UBIFS: recovery needed
[ 2.660000] UBIFS: recovery completed
[ 2.670000] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[ 2.670000] UBIFS: file system size: 110342144 bytes (107756 KiB, 105 MiB, 869 LEBs)
[ 2.680000] UBIFS: journal size: 9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
[ 2.690000] UBIFS: media format: w4/r0 (latest is w4/r0)
[ 2.700000] UBIFS: default compressor: lzo
[ 2.700000] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 2.710000] VFS: Mounted root (ubifs filesystem) on device 0:13.
[ 2.710000] Freeing init memory: 112K
Filesystem Product Vesion : DJI-Filesystem-1.0-rc2
Runing /etc/init.d/rcS
[ 3.110000] UBI: scrubbed PEB 165 (LEB 0:163), data moved to PEB 514
[ 4.600000] CMEMK module: built on Jan 14 2014 at 19:23:51
[ 4.620000] Reference Linux version 2.6.32
[ 4.620000] File /home/u/dm368/dvsdk_dm368_4_02_00_06/linuxutils_2_26_01_02/packages/ti/sdo/linuxutils/cmem/src/module/cmemk.c
[ 4.640000] allocated heap buffer 0xc7000000 of size 0x15e2000
[ 4.670000] heap fallback enabled - will try heap if pool buffer is not available
[ 4.670000] CMEM Range Overlaps Kernel Physical - allowing overlap
[ 4.690000] CMEM phys_start (0x1000) overlaps kernel (0x80000000 -> 0x83000000)
[ 4.690000] cmemk initialized
[ 4.720000] IRQK module: built on Jan 14 2014 at 19:23:57
[ 4.740000] Reference Linux version 2.6.32
[ 4.740000] File /home/u/dm368/dvsdk_dm368_4_02_00_06/linuxutils_2_26_01_02/packages/ti/sdo/linuxutils/irq/src/module/irqk.c
[ 4.760000] irqk initialized
[ 4.810000] EDMAK module: built on Jan 14 2014 at 19:24:08
[ 4.830000] Reference Linux version 2.6.32
[ 4.830000] File /home/u/dm368/dvsdk_dm368_4_02_00_06/linuxutils_2_26_01_02/packages/ti/sdo/linuxutils/edma/src/module/edmak.c
sulogin: no password entry for root
login[421]: root login on 'ttyS0'
#Process /etc/profile...
root@Dji-Pro:~#
Switch V00.02.00.00(Feb 3 2015 11:02:17).
usb or cvbs output switch:0 cvbs
hdmi2tv V00.01.01.00(Feb 3 2015 11:02:17).
calling cmem utilities for allocati[ 5.300000] davinci_resizer davinci_resizer.2: RSZ_G_CONFIG:0:1:124
ng frame buffers[ 5.310000] davinci_previewer davinci_previewer.2: ipipe_set_preview_config
Allocating cap[ 5.320000] davinci_previewer davinci_previewer.2: ipipe_set_preview_config
ture buffers :buf size = 4149248[ 5.330000] vpfe-capture vpfe-capture: IPIPE Chained
Got 0x401ae00[ 5.330000] vpfe-capture vpfe-capture: Resizer present
0 from CMEM, phy[ 5.340000] EVM: switch to it6604 hdmi video input
= 0x86d97000
G[ 5.350000] hdmi is not online
ot 0x405a3000 from CMEM, phy = 0x869a2000
Allocating display buffers :buf size = 4149248
Got 0x40998000 from CMEM, phy = 0x865ad000
Got 0x40d8d000 from CMEM, phy = 0x861b8000
opening resize device
Successfully set mode to continuous in resizer
default configuration setting in Resizer successfull
Resizer initialized
Operating mode changed successfully to continuous in previewerSetting default configuration in previewer
default configuration setting in previewer successfull
previewer initialized
setting data format
Detecting if driver supports Hdmi_yuv
input.name = Composite
input.name = S-Video
input.name = Hdmi_yuv
InitDevice:ioctl:VIDIOC_G_INPUT, selected input Hdmi_yuv
[ 7.350000] hdmi is not online
[ 9.350000] hdmi is not online
[ 11.360000] hdmi is not online
[ 13.360000] hdmi is not online
[ 15.360000] hdmi is not online
[ 17.370000] hdmi is not online
[ 19.370000] hdmi is not online
[ 21.380000] hdmi is not online
[ 23.380000] hdmi is not online
[ 25.380000] hdmi is not online
[ 27.390000] hdmi is not online
[ 29.390000] hdmi is not online
[ 31.390000] hdmi is not online
[ 33.400000] hdmi is not online
[ 35.400000] hdmi is not online
[ 37.400000] hdmi is not online
[ 39.410000] hdmi is not online
[ 41.410000] hdmi is not online
[ 43.410000] hdmi is not online
[ 45.420000] hdmi is not online
[ 47.420000] hdmi is not online
[ 49.420000] hdmi is not online
[ 51.430000] hdmi is not online
[ 53.430000] hdmi is not online
[ 55.430000] hdmi is not online
[ 57.440000] hdmi is not online
[ 59.440000] hdmi is not online
[ 61.440000] hdmi is not online
[ 63.450000] hdmi is not online
[ 65.450000] hdmi is not online
[ 67.450000] hdmi is not online
[ 69.460000] hdmi is not online
[ 71.460000] hdmi is not online
[ 73.470000] hdmi is not online
[ 75.470000] hdmi is not online
[ 77.470000] hdmi is not online
[ 79.480000] hdmi is not online
[ 81.480000] hdmi is not online
[ 83.480000] hdmi is not online
[ 85.490000] hdmi is not online
[ 87.490000] hdmi is not online
[ 89.490000] hdmi is not online
[ 91.500000] hdmi is not online
[ 93.500000] hdmi is not online
[ 95.500000] hdmi is not online
[ 97.510000] hdmi is not online
[ 99.510000] hdmi is not online
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 COM5...
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.Since this worked so well, I also tried flashing the board from the broken Zenmuse Z15 5D III (HD). However, it seems to have a bigger problem as after about 15 seconds, the console displays garbled characters. After the board is disconnected from the power supply for a longer period of time (approx. 2 hours), it works again for 15 seconds before it ends in garbled characters. Maybe someone here also has an idea of what could be causing that. The pins on the board are labeled and the debug pins are U1_RX and U1_TX.
