Thanks for the info. I've tracked down an XP laptop so will be trying the flash tool this weekend.
lightbridge firmware PROBLEM (and solution) - firmware version not found by dji assistant tool
- Thread starter gaucho
- Start date
Hello!
Im runnig windows 10 aswell 64bits without any problem when I did all this to get my lightbridge working.
@gaucho this is what I got on my console:
Is my board completely toast?
Waiting for the DM36x...
Target:
Target: WV???k→j???:jZ???
Target: →?????T??+?U{g?_←!7§9↨?S5↓-!#???wkm?}{_?YU_u[?U{g?????←9???????
???????w+-?U{g?S5←↓-!#???????}§1??????????????????????{!!↨-#1?y=↨='!1?{!!↨?g!=7
←??{!!↨e!75???c}cw??Y↨=←↨-#1?c}cw?y!▼
Target: ?????
Target: ?:j??+??j?→?~:????u????M???3!§#7?-#?;'!9)??☼???????????
Target: ?OR??+??j?→?~:????u}yuw????3!§#7?-#?;'!9)??☼???????{???
Target: ?OR??+??j?→?T:????u????M?;??
Target: ?4??k→??:
Target: ?J??????????v?+?
Target: ?OR??+??j?→?T:????u????M?;??
Target: ?4??k→??:
Target: ?J??????????6?+?
Target: ?H??:j???
Target: ??k*?????
Target: ?4??+?c}cw?{!!↨?3=-'57???};!←↨-#1?????
Aborting program...
Thanks that's odd. It should be 115200 right? I set that in device manager on the serial device. Does it need setting somewhere else?
- Joined
- Apr 14, 2015
- Messages
- 294
- Reaction score
- 36
- Age
- 74
I wrote to you what to do.
I think you are not using my app.
Usually target is printed by TI app..
I am following precise numbered instructions from first post of this thread. Using the linked zip archive and commands within those instructions. I have no idea what the TI app even is, apart from the passing references in this thread.
I'll work it out with assistance I've received from others. Appreciate you taking the time to work this fix out and write the post, but I won't bother you with any further requests for help.
- Joined
- Apr 14, 2015
- Messages
- 294
- Reaction score
- 36
- Age
- 74
No, you are not following my suggestion neither the procedure on first post.
TI means Texas Instruments.
Start describing your hardware modifications with pictures, continue posting a log and the tool that you used to obtain it.
If you want help follow my requests.
You should also search previous posts and find my previous suggestion for you. Up to know I didn't understood your real situation then I can't help you
Hi All, firstly sorry to hijack this post with Phantom Vision 2 Info but I just wanted to report that I have successfully restored another users "no video in the app" issue with the reflash tool - This is great news for all others having the issue and I will type up a seperate post dedicated to the Phantom Vision 2 units - I will also provide a repair service in the UK to help others struggling with this.
More to come and thanks again for all the info and hard work!
More to come and thanks again for all the info and hard work!
- Joined
- Apr 14, 2015
- Messages
- 294
- Reaction score
- 36
- Age
- 74
Hello Gaucho, are you Brazilian?
I need to have this adapter usb -> serial, or if my computer has a native serial port also? I did the procedure, the program seems to connect, but only a series of characters appears ...
I need to have this adapter usb -> serial, or if my computer has a native serial port also? I did the procedure, the program seems to connect, but only a series of characters appears ...
- Joined
- Apr 14, 2015
- Messages
- 294
- Reaction score
- 36
- Age
- 74
Don't connect LB directly to your pc serial port. You need 3,3V serial adapter or you risk to fry your LB
Buy one on eBay or amazon
No, I'm from Italy
Cool!
I'll be in Italy at the end of April!
Well, I bought the FTDI232 and did the procedures as directed in the topic. My LB Ground went live perfectly. The three firmware appears, including one of them. I have "image" (not of camera) on android, and on hdmi port.
However, my LB Air is not working. I opened the AIR module, soldares the wires and connected to the FTDI, executed the command, as before with LB ground, but the command does not finish, it appears Target: Bootme.
When I run the command with the 3.3v->bsel connection open, NAND Boot failed appears.
What should I do?
The images are below...
Tnks
I'll be in Italy at the end of April!
Well, I bought the FTDI232 and did the procedures as directed in the topic. My LB Ground went live perfectly. The three firmware appears, including one of them. I have "image" (not of camera) on android, and on hdmi port.
However, my LB Air is not working. I opened the AIR module, soldares the wires and connected to the FTDI, executed the command, as before with LB ground, but the command does not finish, it appears Target: Bootme.
When I run the command with the 3.3v->bsel connection open, NAND Boot failed appears.
What should I do?
The images are below...
Tnks
Attachments
- Joined
- Apr 14, 2015
- Messages
- 294
- Reaction score
- 36
- Age
- 74
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 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
- Joined
- Apr 14, 2015
- Messages
- 294
- Reaction score
- 36
- Age
- 74
This is new to me. It's like the nand is write protected. Could this be the log obtained without bsel shorted to 3V3?
- Joined
- Apr 14, 2015
- Messages
- 294
- Reaction score
- 36
- Age
- 74
