Those are for the gimbal board. From the link I posted earlier. We need some for the usb board.
If you need only bootloader and kernel, you can get them by extracting any gl300 firmware update package.
If you need the rest as well, there are full flashing instructions with links:
Flashing firmware on DaVinci media processors · mefistotelis/phantom-firmware-tools Wiki · GitHub
Thanks for the reply quaddamage.
I did read the stuff on github, but am still not smart enough to figure out what is needed when, and how to extract the files.
That's why I wished for a package with step-by-step instruction and files, like with the gimbal top board.
I did read the stuff on github, but am still not smart enough to figure out what is needed when, and how to extract the files.
That's why I wished for a package with step-by-step instruction and files, like with the gimbal top board.
If you wish simpler instruction to exist, you will have to create it.
How to extract:
Code:
git clone https://github.com/mefistotelis/phantom-firmware-tools.wiki.git
Code:
./dji_fwcon.py -vv -x -p C1_FW_V01.06.0020.binGuess I need to figure out how to run the git command, and how to run py scripts... Im on windows, and have absolutely no knowledge of Linux.
Thanks though. Hopefully some Linux wiz can make sense of this
Thanks though. Hopefully some Linux wiz can make sense of this
I added the files a few posts back and went to this GitHub post. Flashing firmware on DaVinci media processors · mefistotelis/phantom-firmware-tools Wiki · GitHub
I actually don't know if I did anything the right way. Controller still not showing any firmware.
Those are for the gimbal board. Are you sure the u-boot and ubl1 files are identical to what should be flashed to the USB board?
I am almost certain this is fixable. If you connect the FTDI to PC and open terminal on the UART interface (ie. PuTTY), what do you see?
What you possibly can be seeing is:
- A stream of BOOTME messages - if pins are shorted to allow to write bootloader
- A few messages from U-boot, stopping at some point - if U-boot is still damaged
- Messages from U-boot, then start of a primary or secondary kernel - if it comes to starting kernel
- U-boot, then kernel, then command line - if the Linux is able to boot correctly (either to primary or secondary kernel)
Quaddamage. Is it the same uboot and ubl1 files thats used for both the gimbal board and usb board?
It is very possible that the u-boot images from both gimbal and radio are interchangeable. After all this is the same chip, and works in the same HW configuration. But I doubt any other images (kernel or rootfs) can be switched - the chips are booted to do different (opposite) things on both sides.
But there is no need to mix the u-boot images - we can extract proper ones from any firmware version we want.
If you'd like us to help, you need to provide a description of what you did and explanation on where you're stuck.
Kool. I have the TTL board wired to GL300A USB board (separated from the controller). Now I don't know if I have the right u-boot and ubl1 files. I was able to get to the BOOTME where it just constantly says BOOTME. Did it again where it goes through and stops and says operation completed successfully. That's where I'm stuck. Firmware still will not show in DJIGo app. I don't know if i'm missing a step or there is another step. Thanks
