Fixing flash in DM365 chip within Ph3 Pro gimbal
- Thread starter quaddamage
- Start date
Ubi File System uses hardware-assisted ECC. So while other partitions can be "just" flashed, UbiFS needs special procedure. I'm not sure if I explained that in detail in any of my tutorials; but you will find it described on the dji-firmware-tools wiki.
Basically you first flash a small root file system which only contains tools to flash the "proper" one.
Basically you first flash a small root file system which only contains tools to flash the "proper" one.
Hi @quaddamage
Quick question: do those NAND IC work with the same driver from the TI Chip? Are those completely interchangeable?
If yes, which one in your opinion is more reliable between Micron and Macronix?
Thanks
You are not changing the TI chip, right?
That's what datasheets are for. Check them to see differences. I'm sure you'll find some.
Samsung.
No, I'm not changing the TI chip, I just want to replace the NAND IC, which in my case is the 5HE12 NW361 which I believe is the Micron NAND IC.
All I wanted to know is if it is worth to replace it with the same device or maybe get a more reliable NAND Memory chip.
Can you share the part number of the Samsung IC you used in your case? Would it work 100% with my P01069.07 board?
So that answers your question on "driver", by which I assume you meant flashing software which talks to TI bootloader.
None of the Phantom enthusiasts has reliability data on specific chip manufacturers. Micron and MXIC are likely coming from the same fab. Samsung has its own fabs.
Sorry, I don't think I kept notes, and I'm not willing to go through the datasheets myself, again.
I'm not even 100% sure it was Samsung, I know for sure only that I did found a 3rd manufacturer for that part with that specific footprint.
Again, that's something you check in the datasheet.
Requirements for the NAND can be found within DaVinci datasheet; they are general/basic, because interfaces are well defined.
I'd worry about selecting a model with proper footprint, not one which looks identical but will turn out to be ie. 2mm smaller. Then you can check if pinouts (names of pins) are identical if you really want to be sure.
Either way - the word is datasheet. Have it. Browse it.
Thanks Quaddamage, I was concerned about the drivers, because this NAND flash memory does not use a Standard SPI, UART or I2C bus, in fact, the DaVinci IC connect to external NAND flash memory through a multiplexed data bus, managed by an on-chip External Memory Interface (EMIF) or a similar GPMC (General Purpose Memory Controller), I was curious to see if there was any constrains in the choice of the NAND Memory among Micron, Micronix and other 3rd-party manufacturers/vendors, due to some specifics of the DaVinci chip.
Hi @quaddamage,
I ended up buying a used and broken DJI Phantom 3 Pro Upper Gimbal part (without the camera), and I took the mainboard from it and put it in my Phantom 3 Pro. It was just $30 so a much faster fix.
I finally have the video feed in my phone, and I can fly it woth no problem, although I only tested it in begginner mode.
The only issue I have now is that the Gimbal calibration would always fails.
I've updated the firmware to the latest version available (P3X_FW_V01.11.0020), the reault was successful and I don't see any "device not found" in the logs, but the calibration of the gimbal is still failing.
Do you have any insight on how to fix this issue?
Thanks in advance!
I ended up buying a used and broken DJI Phantom 3 Pro Upper Gimbal part (without the camera), and I took the mainboard from it and put it in my Phantom 3 Pro. It was just $30 so a much faster fix.
I finally have the video feed in my phone, and I can fly it woth no problem, although I only tested it in begginner mode.
The only issue I have now is that the Gimbal calibration would always fails.
I've updated the firmware to the latest version available (P3X_FW_V01.11.0020), the reault was successful and I don't see any "device not found" in the logs, but the calibration of the gimbal is still failing.
Do you have any insight on how to fix this issue?
Thanks in advance!
Yeah, definitely easier that BGA soldering + flashing.
No, not really. DAT logs may have some info on the reason, or the text log you can get by attaching to the front USB. Also may be important to share at which moment (which move of the gimbal) the calibration stops.
Though if it works, and the gimbal position is not rotated, I'd just leave it.
Hi @quaddamage,
Thanks for getting back to me.
Here attached the video of the gimbal calibration trial and the zip containing all the logs from the micro SD card.
Unfortunately even when I entered the Flight Data mode and connected the USB cable from the PC to the Aircraft microUSB (not the one on the Gimbal), the copy of the dat logs stopped in the middle of the operation, and then the USB Mass Storage was not correctly identified by Windows anymore, and I even changed the USB cable and computer.
So, I'm not able to copy the dat logs anymore. Not sure what I can do a this stage.
Thanks for getting back to me.
Here attached the video of the gimbal calibration trial and the zip containing all the logs from the micro SD card.
Unfortunately even when I entered the Flight Data mode and connected the USB cable from the PC to the Aircraft microUSB (not the one on the Gimbal), the copy of the dat logs stopped in the middle of the operation, and then the USB Mass Storage was not correctly identified by Windows anymore, and I even changed the USB cable and computer.
So, I'm not able to copy the dat logs anymore. Not sure what I can do a this stage.
Last edited:
Similar threads
