Good morning Carlos, so I have the same problem in lightbridge what is in the drone appears corrupted, I saw that you solved the problem, could you pass me as you solved it? Because I have already reworked the soldes all changed to windows vista 32bits and still giving error , My email is [email protected], I am grateful for the attention, hug !!
lightbridge firmware PROBLEM (and solution) - firmware version not found by dji assistant tool
- Thread starter gaucho
- Start date
Good morning Carlos, so I have the same problem in lightbridge what is in the drone appears corrupted, I saw that you solved the problem, could you pass me as you solved it? Because I have already reworked the soldes all changed to windows vista 32bits and still giving error , My email is [email protected], I am grateful for the attention, hug !!
Hi to all, I just want to share my experience...
With my Ground Units I was able to reflash the firmware with the Assitant Software following this procedure:
- turn it on: only main controller firmware shown - REFLASH MAIN CONTROLLER FIRMWARE
- power cycle and repeat firs step until the assistant shows at least one of the adiitional firmwares (5-20 times) - THEN REFLASH THE NEWLY SHOWN FIRMWARE
- once at least 2 firmwares are shown stable reflash until all three are shown and then REFLASH THAT LAST ONE TOO and you hopefully got it!
With my Air unit I had no luck with the above method, so I followed the instructions with the soldered usb-adapter, but I had no luck with it either...
So in the end I have contacted the european DJI support (in the Netherlands) and shipped the Air Unit, to my surprise they send me a new one without any hesitation for free, even if mine was out of warranty!
With my Ground Units I was able to reflash the firmware with the Assitant Software following this procedure:
- turn it on: only main controller firmware shown - REFLASH MAIN CONTROLLER FIRMWARE
- power cycle and repeat firs step until the assistant shows at least one of the adiitional firmwares (5-20 times) - THEN REFLASH THE NEWLY SHOWN FIRMWARE
- once at least 2 firmwares are shown stable reflash until all three are shown and then REFLASH THAT LAST ONE TOO and you hopefully got it!
With my Air unit I had no luck with the above method, so I followed the instructions with the soldered usb-adapter, but I had no luck with it either...
So in the end I have contacted the european DJI support (in the Netherlands) and shipped the Air Unit, to my surprise they send me a new one without any hesitation for free, even if mine was out of warranty!
Is this the right thread to ask about the p2v flash fix, got a question about a unit that won't flash correctly
Hey I was wondering if you could send me somthing that could help a newbie drone builder build a f550 flame wheel w/ naza m v2, lightbridge, zenmuse h4 3d, isod mini, DT7&DR16, retractable landing gear. so far i have the frame built along with the motors ,esc,and naza mv2. im mounting a gopro 4 black . I have a BTU coming as well. any advise , guidance, or direction would be greatly appreciated!!!
This message is to 'rmhome' . Hi rmhome, I live in Aberdeen and have a Phantom 2 Vision with no FPV. Would you be able to fix this for me if I sent my drone to you. Thanks. Potterman.
Hi! i have a p2vision+ with black screen. have done all the steps needed to connect chip with tera term, i get the boot me option and when i tries to flash using cmd command it shows uart receive error... what could be causing this problem? i was eable to erase nand using "sfh_DM36x.exe -nanderase -v -p "COM10"
But when i tries the full command "sfh_DM36x.exe -nandflash -v -p "COM10" ubl1_editedByGaucho.img uboot_modifiedByGaucho.img" the uart receive error shows up... and it starts to loop...please i need help! Should i buy a new ftdi adapter? and if so wich one?
I'w tried using win10 win7 and winxp... different computers...
/Carl
But when i tries the full command "sfh_DM36x.exe -nandflash -v -p "COM10" ubl1_editedByGaucho.img uboot_modifiedByGaucho.img" the uart receive error shows up... and it starts to loop...please i need help! Should i buy a new ftdi adapter? and if so wich one?
I'w tried using win10 win7 and winxp... different computers...
/Carl
Attachments
Last edited:
For me it's only works with windows xp service pack 3. 32 bits and it doesn't work with windows 7 or 10 64 bit.
Éric
Hi! did you get the same message as me, uart recevie error, in cmd (same om win10,win7 and winxp...)?
And did you follow the post from friend7 step by step, or did you do any modifications?
I'm hopping its a problem with the ftdi adapter or the windows version (not the wi-fi module...)
witch adapter did you use? mine was the cheapest on banggod (not a genuine one).
Geekcreit® FT232RL FTDI USB To TTL Serial Converter Adapter Module For Arduino
Maby some other adapter is better...
/Carl
Last edited:
Yes I have the same adapter on bangood. Do you put the jumper on 3,3v. I followed the gaucho tutorial. I can't remenber the error message that I had during my first test under windows 10 or 7...
Look at the thread of my message.
Sorry for my bad english I'm a frenchy and it's more difficult for me.
Look at the thread of my message.
Sorry for my bad english I'm a frenchy and it's more difficult for me.
Hi again! Tried flashing with win xp 32bit same problem. Uart receive error! Need to know what this means. Anybody? Not enough power (using 11.1 Lipo)? Something wrong with the ftdi( I'm using old drivers)? Please some input, what could be the problem causing this?
I have this same problem on my WM301_DM368_V1 board. I made exactly procedure from: DJI Phantom 2 Vision+ Plus Blank Screen Corrupt NAND fix
everything seems correct in upload, but is still not working, any ideas?
I think i could be problem
in my board is:
Cores: ARM 432 MHz
in tourutial it was:
Cores: ARM 297 MHz
maybe someone have P2V+ as well, and could get a image from wi-fi board module?
Last edited:
Attachments
Hello. So I have been doing a ton of reading and now will be attempting to restore what I believe is a corrupt dm365 chip on my P3P main gimbal board (infamous 08/15 error device not found). Looking for some hand holding from those have attempted a similar journey.
First I will connect my trusty ftdi (3.3v) to the u 386 rx and tx pads, ground and power. Fire my favorite terminal Putty, power up the board and log the output. Not sure what I will find but I take it that some clues may be found during the boot logging. Could use more help on what to look for.
Once I know it is a corrupt Dm365 - I will connect the bt 00 and bt 01 with 3.3v - and try the flash command. I need some clarification on what files and command to use. Is there a different .img for the air side LB and the Gimbal main board of the P3P. Please post or link the correct files and command(s) to flash dm365 on the p3p.
Now I suppose I need to check everything before the painful tedious process of assembling the entire gimbal. Please help with the verification process that everything is working (at least in regards to the dm365 corrupt).
Once everything is back assembled. I suppose I will need to flash to the correct (or best firmware). I could use some suggestion on what firmware (p3p) I need to have installed. thank you,
First I will connect my trusty ftdi (3.3v) to the u 386 rx and tx pads, ground and power. Fire my favorite terminal Putty, power up the board and log the output. Not sure what I will find but I take it that some clues may be found during the boot logging. Could use more help on what to look for.
Once I know it is a corrupt Dm365 - I will connect the bt 00 and bt 01 with 3.3v - and try the flash command. I need some clarification on what files and command to use. Is there a different .img for the air side LB and the Gimbal main board of the P3P. Please post or link the correct files and command(s) to flash dm365 on the p3p.
Now I suppose I need to check everything before the painful tedious process of assembling the entire gimbal. Please help with the verification process that everything is working (at least in regards to the dm365 corrupt).
Once everything is back assembled. I suppose I will need to flash to the correct (or best firmware). I could use some suggestion on what firmware (p3p) I need to have installed. thank you,
I was wondering, if I'm successful restoring the DM365 chip on the P3P board, what will keep it from corrupting itself again? Do we know why it gets corrupted in the first place? Is there some other hardware/software problem that is causing the corruption? I hate fixing just the symptom not the cause.
Does not appear this thread is active. Anyway, I made some progress but still could use a hand.
I flashed the p3p main gimbal board using tools and boot images found on other sights. The the DM chip took that flash and now I can at least see the board trying to boot. Putty log during booting attempt is attached. It gets to the point shown and reboots itself continuously. Seems to be a few errors related to the usb. Suggestions welcome.
oot@Dji-Pro:~#
encode_usb V00.02.02.00(Jul 18 2015 16:52:39).
Entry Encrypt qury mode
init libusb successed!!!
!!!!!!!!!!!!!!!![ 6.720000] EVM: switch to ambarella video input
!!!!!!! open 68013 failed VENDOR_ID = 0x0547 (this cannot be good)
Init libusb faild!
Auto to detect video input type:
Default video input selected:Hdmi_yuv
S[ 6.730000] davinci_resizer davinci_resizer.2: RSZ_G_CONFIG:0:1:124
etting video standard to: 0x1000[ 6.740000] davinci_previewer davinci_previewer.2: ipipe_set_preview_config
00000000000
Cap[ 6.750000] vpfe-capture vpfe-capture: IPIPE Chained
ture input set t[ 6.760000] vpfe-capture vpfe-capture: Resizer present
o Hdmi_yuv:11
Capture videoStd[ 6.770000] EVM: switch to ambarella video input
Old=0000000b
[ 6.770000] vpfe-capture vpfe-capture: width = 1280, height = 720, bpp = 1
[ 6.780000] vpfe-capture vpfe-capture: adjusted width = 1280, height = 720, bpp = 1, bytesperline = 1280, sizeimage = 1382400
[ 6.790000] vpfe-capture vpfe-capture: width = 1280, height = 720, bpp = 1
[ 6.800000] vpfe-capture vpfe-capture: adjusted width = 1280, height = 720, bpp = 1, bytesperline = 1280, sizeimage = 1382400
videoFrameRate=30000, width=1280, height=720
Venc1.c : minNumOutBufs 2, minOutBufSize[0] 1382400, minOutBufSize[1] 800
GOP interval:30, outBufSize:1382400, enAdpBW:1, airRate=0, slice=6, VUI=4,timeScale=60001
osdThrFxn: process ID is 433 ***********
watchdog timeout:5
ctrlThrFxn: process ID is 425 ***********
Frmae:1 Pslice = 0, Islice = 8[44ms]
GetFPGAstatus err!
FPGA[1,0,1,0]-1.000000:0
hdmi status is 1
usblink status check~~~~~~~~~~~~~~~~
GetFPGAstatus err!! (I believe this is from not having the camera connected - edit)
inptVD=0547
USB device go down, need to reboot system
usb bus error dectected! (unknown error stops boot process)
No USB device ID:547
try reset 68013....!
umount: can't remount none read-only
umount: mdev busy - remounted read-only
The system is going down NOW!
Sent SIGTERM to all processes
Sent SIGKILL to all processes
Requesting system reboot
[ 10.470000] Restarting system.
DM36x initialization passed! (yeah DM36 corruption fixed)
UBL Product Vesion : DJI-NOHDMI-WM610-UBL-1.0-rc0(2015-01-13)
Dji UBL Version: 1.51(Jan 13 2015 - 16:42:11)
Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000019.
DONE
Jumping to entry point at 0x81080000.
U-Boot Product Vesion : DJI-WM610-Uboot-1.0-rc4(2014-08-13)
U-Boot 2010.12-rc2-svn-Dji (Aug 13 2014 - 10:55:23)
Cores: ARM 297 MHz
DDR: 270 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 (unclear why there is an error)
** 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-03-30 9:54:39 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4032832 Bytes = 3.8 MiB
Load Address: 80008000
Entry Point: 80008000
Booting kernel from Legacy Image at 80700000 ...
Image Name: Linux-2.6.32.17-davinci1
Created: 2015-03-30 9:54:39 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4032832 Bytes = 3.8 MiB
Load Address: 80008000
Entry Point: 80008000
Loading Kernel Image ... OK (backup Kernel boots, hmmm)
OK
I flashed the p3p main gimbal board using tools and boot images found on other sights. The the DM chip took that flash and now I can at least see the board trying to boot. Putty log during booting attempt is attached. It gets to the point shown and reboots itself continuously. Seems to be a few errors related to the usb. Suggestions welcome.
oot@Dji-Pro:~#
encode_usb V00.02.02.00(Jul 18 2015 16:52:39).
Entry Encrypt qury mode
init libusb successed!!!
!!!!!!!!!!!!!!!![ 6.720000] EVM: switch to ambarella video input
!!!!!!! open 68013 failed VENDOR_ID = 0x0547 (this cannot be good)
Init libusb faild!
Auto to detect video input type:
Default video input selected:Hdmi_yuv
S[ 6.730000] davinci_resizer davinci_resizer.2: RSZ_G_CONFIG:0:1:124
etting video standard to: 0x1000[ 6.740000] davinci_previewer davinci_previewer.2: ipipe_set_preview_config
00000000000
Cap[ 6.750000] vpfe-capture vpfe-capture: IPIPE Chained
ture input set t[ 6.760000] vpfe-capture vpfe-capture: Resizer present
o Hdmi_yuv:11
Capture videoStd[ 6.770000] EVM: switch to ambarella video input
Old=0000000b
[ 6.770000] vpfe-capture vpfe-capture: width = 1280, height = 720, bpp = 1
[ 6.780000] vpfe-capture vpfe-capture: adjusted width = 1280, height = 720, bpp = 1, bytesperline = 1280, sizeimage = 1382400
[ 6.790000] vpfe-capture vpfe-capture: width = 1280, height = 720, bpp = 1
[ 6.800000] vpfe-capture vpfe-capture: adjusted width = 1280, height = 720, bpp = 1, bytesperline = 1280, sizeimage = 1382400
videoFrameRate=30000, width=1280, height=720
Venc1.c : minNumOutBufs 2, minOutBufSize[0] 1382400, minOutBufSize[1] 800
GOP interval:30, outBufSize:1382400, enAdpBW:1, airRate=0, slice=6, VUI=4,timeScale=60001
osdThrFxn: process ID is 433 ***********
watchdog timeout:5
ctrlThrFxn: process ID is 425 ***********
Frmae:1 Pslice = 0, Islice = 8[44ms]
GetFPGAstatus err!
FPGA[1,0,1,0]-1.000000:0
hdmi status is 1
usblink status check~~~~~~~~~~~~~~~~
GetFPGAstatus err!! (I believe this is from not having the camera connected - edit)
inptVD=0547
USB device go down, need to reboot system
usb bus error dectected! (unknown error stops boot process)
No USB device ID:547
try reset 68013....!
umount: can't remount none read-only
umount: mdev busy - remounted read-only
The system is going down NOW!
Sent SIGTERM to all processes
Sent SIGKILL to all processes
Requesting system reboot
[ 10.470000] Restarting system.
DM36x initialization passed! (yeah DM36 corruption fixed)
UBL Product Vesion : DJI-NOHDMI-WM610-UBL-1.0-rc0(2015-01-13)
Dji UBL Version: 1.51(Jan 13 2015 - 16:42:11)
Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000019.
DONE
Jumping to entry point at 0x81080000.
U-Boot Product Vesion : DJI-WM610-Uboot-1.0-rc4(2014-08-13)
U-Boot 2010.12-rc2-svn-Dji (Aug 13 2014 - 10:55:23)
Cores: ARM 297 MHz
DDR: 270 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 (unclear why there is an error)
** 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-03-30 9:54:39 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4032832 Bytes = 3.8 MiB
Load Address: 80008000
Entry Point: 80008000
Booting kernel from Legacy Image at 80700000 ...
Image Name: Linux-2.6.32.17-davinci1
Created: 2015-03-30 9:54:39 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4032832 Bytes = 3.8 MiB
Load Address: 80008000
Entry Point: 80008000
Loading Kernel Image ... OK (backup Kernel boots, hmmm)
OK
Hi jjhdtv,
I'm intrigued that you're trying this on a p3pro. I always wanted to since they tend to have airside lb corruption too.
Can you share any pix of the pin locations and reference to what you successfully flashed on it and the commands?
From the above output, it looks like more than areas of it's flash need flashing. Rmhome and gaucho on this forum have expertise extracting packages from healthy light bridge units for flashing...
I'm intrigued that you're trying this on a p3pro. I always wanted to since they tend to have airside lb corruption too.
Can you share any pix of the pin locations and reference to what you successfully flashed on it and the commands?
From the above output, it looks like more than areas of it's flash need flashing. Rmhome and gaucho on this forum have expertise extracting packages from healthy light bridge units for flashing...
