Fixing flash in DM365 chip within Ph3 Pro gimbal

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: 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
OK

Starting kernel ...

[ 0.000000] Kernel Product Vesion : DJI-NOHDMI-WM610-Kernel-1.0-rc6(2015-03-3 0)
[ 0.000000] Linux version 2.6.32.17-davinci1 (root@dji) (gcc version 4.3.3 (S ourcery G++ Lite 2009q1-203) ) #16 PREEMPT Mon Mar 30 17:54:38 HKT 2015
[ 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 pa ges: 12192
[ 0.000000] Kernel command line: console=ttyS0,115200n8 rw dm365_imp.oper_mod e=0 video=davincifb:vid0=0,10K:vid1=0,10K:eek:sd0=1920x1080X16,8100K mem=48MB davin ci_enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=pal ubi.mtd=2,2048 ro ot=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: 44452KB available (3640K code, 451K data, 116K init, 0K h ighmem)
[ 0.000000] SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, N odes=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.110000] bio: create slab <bio-0> at 0
[ 0.110000] DM365 IPIPE initialized in Continuous mode
[ 0.110000] SCSI subsystem initialized
[ 0.120000] usbcore: registered new interface driver usbfs
[ 0.120000] usbcore: registered new interface driver hub
[ 0.120000] usbcore: registered new device driver usb
[ 0.120000] vpss vpss: dm365_vpss vpss probed
[ 0.120000] vpss vpss: dm365_vpss vpss probe success
[ 0.130000] dm365_afew_hw_init
[ 0.130000] ch0 default output "COMPOSITE", mode "PAL"
[ 0.130000] VPBE Encoder Initialized
[ 0.130000] cfg80211: Using static regulatory domain info
[ 0.130000] cfg80211: Regulatory domain: US
[ 0.130000] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp )
[ 0.130000] (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
[ 0.130000] (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 0.130000] (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 0.130000] (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 0.130000] (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 0.130000] (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[ 0.130000] cfg80211: Calling CRDA for country: US
[ 0.140000] LogicPD encoder initialized
[ 0.140000] Switching to clocksource timer0_1
[ 0.140000] musb_hdrc: version 6.0, pio, host, debug=0
[ 0.160000] musb_hdrc: USB Host mode controller at fec64000 using PIO, IRQ 12
[ 0.160000] musb_hdrc musb_hdrc: MUSB HDRC host driver
[ 0.160000] musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
[ 0.160000] usb usb1: configuration #1 chosen from 1 choice
[ 0.160000] hub 1-0:1.0: USB hub found
[ 0.160000] hub 1-0:1.0: 1 port detected
[ 0.160000] NET: Registered protocol family 2
[ 0.160000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.160000] TCP established hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.160000] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.160000] TCP: Hash tables configured (established 2048 bind 2048)
[ 0.160000] TCP reno registered
[ 0.160000] NET: Registered protocol family 1
[ 0.160000] RPC: Registered udp transport module.
[ 0.160000] RPC: Registered tcp transport module.
[ 0.160000] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.170000] JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 0.170000] msgmni has been set to 86
[ 0.180000] alg: No test for stdrng (krng)
[ 0.180000] io scheduler noop registered (default)
[ 0.210000] VBUS on (a_wait_vrise), devctl 19
[ 0.220000] davincifb davincifb.0: dm_osd0_fb: Initial window configuration i s invalid.
[ 0.300000] Console: switching to colour frame buffer device 240x67
[ 0.390000] davincifb davincifb.0: dm_osd0_fb: 1920x1080x16@0,0 with framebuf fer size 8100KB
[ 0.390000] davincifb davincifb.0: dm_vid0_fb: 0x0x16@0,0 with framebuffer si ze 10KB
[ 0.390000] davincifb davincifb.0: dm_osd1_fb: 720x576x4@0,0 with framebuffer size 810KB
[ 0.400000] davincifb davincifb.0: dm_vid1_fb: 0x0x16@0,0 with framebuffer si ze 10KB
[ 0.460000] DM365 IPIPEIF probed
[ 0.460000] imp serializer initialized
[ 0.460000] davinci_previewer initialized
[ 0.460000] davinci_resizer initialized
[ 0.470000] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 0.470000] serial8250.0: ttyS0 at MMIO 0x1c20000 (irq = 40) is a 16550A
[ 0.930000] console [ttyS0] enabled
[ 0.940000] serial8250.0: ttyS1 at MMIO 0x1d06000 (irq = 41) is a 16550A
[ 0.950000] brd: module loaded
[ 0.960000] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xf1 (Micron NAND 12 8MiB 3,3V 8-bit)
[ 0.970000] Creating 4 MTD partitions on "davinci_nand.0":
[ 0.970000] 0x000000000000-0x0000004a0000 : "bootloader"
[ 0.980000] 0x0000004a0000-0x000000e00000 : "kernel"
[ 0.990000] 0x000000e00000-0x000007f00000 : "filesystem"
[ 1.000000] 0x000000000000-0x000008000000 : "all"
[ 1.010000] davinci_nand davinci_nand.0: controller rev. 2.3
[ 1.020000] UBI: attaching mtd2 to ubi0
[ 1.020000] UBI: physical eraseblock size: 131072 bytes (128 KiB)
[ 1.030000] UBI: logical eraseblock size: 126976 bytes
[ 1.030000] UBI: smallest flash I/O unit: 2048
[ 1.040000] UBI: sub-page size: 512
[ 1.040000] UBI: VID header offset: 2048 (aligned 2048)
[ 1.050000] UBI: data offset: 4096
[ 1.530000] UBI: attached mtd2 to ubi0
[ 1.530000] UBI: MTD device name: "filesystem"
[ 1.530000] UBI: MTD device size: 113 MiB
[ 1.540000] UBI: number of good PEBs: 904
[ 1.540000] UBI: number of bad PEBs: 0
[ 1.550000] UBI: max. allowed volumes: 128
[ 1.550000] UBI: wear-leveling threshold: 4096
[ 1.560000] UBI: number of internal volumes: 1
[ 1.560000] UBI: number of user volumes: 0
[ 1.570000] UBI: available PEBs: 891
[ 1.570000] UBI: total number of reserved PEBs: 13
[ 1.580000] UBI: number of PEBs reserved for bad PEB handling: 9
[ 1.580000] UBI: max/mean erase counter: 2/1
[ 1.590000] UBI: image sequence number: 0
[ 1.590000] UBI: background thread "ubi_bgt0d" started, PID 331
[ 1.600000] console [netcon0] enabled
[ 1.600000] netconsole: network logging started
[ 1.610000] Initializing USB Mass Storage driver...
[ 1.610000] usbcore: registered new interface driver usb-storage
[ 1.620000] USB Mass Storage support registered.
[ 1.620000] i2c /dev entries driver
[ 1.630000] Linux video capture interface: v2.00
[ 1.640000] davinci_interrupt 370: VBUS error workaround (delay coming)
[ 1.640000] VBUS off (a_wait_vfall) ERROR, devctl 90
[ 1.650000] vpfe_init
[ 1.650000] vpfe-capture: vpss clock vpss_master enabled
[ 1.660000] vpfe-capture vpfe-capture: v4l2 device registered
[ 1.660000] vpfe-capture vpfe-capture: video device registered
[ 1.670000] EVM: switch to ambarella video input
[ 1.670000] vpfe-capture vpfe-capture: v4l2 sub device ambarella registered
[ 1.680000] vpfe_register_ccdc_device: DM365 ISIF
[ 1.690000] DM365 ISIF is registered with vpfe.
[ 1.690000] Trying to register davinci display video device.
[ 1.700000] layer=c105ec00,layer->video_dev=c105ed64
[ 1.710000] Trying to register davinci display video device.
[ 1.710000] layer=c105f000,layer->video_dev=c105f164
[ 1.720000] davinci_init:DaVinci V4L2 Display Driver V1.0 loaded
[ 1.720000] watchdog watchdog: heartbeat 1 sec
[ 1.730000] TCP cubic registered
[ 1.730000] NET: Registered protocol family 17
[ 1.740000] lib80211: common routines for IEEE802.11 drivers
Can you help me with what to do after this point?

Please
 
This is a board for Advanced. This thread is about fixing Ph3 Pro, ands the chip which is specific to that model - DM365 DaVinci Media Controller. You don't have that chip.

Connecting anything to BT00/BT01 won't matter - these are pads specific to DaVinci chip, which you don't have.

If your board isn't booting, the issue is with Ambarella. Like DaVinci, Ambarella has a separate NAND chip on which its firmware is stored. It also has various boot methods, but since the documentation isn't public, we are not sure how to use them.

Anyway, this thread is about daVinci. It would be best to discuss Ambarella in a separate thread.
Can you turn this process into a video?
Translation is very unsuccessful.
Please explain the software parts from the beginning?
 
Can you turn this process into a video?
I'm pretty sure you quoted a wrong post. No idea what you want. Anyway, no I will not make a video. I'm busy.


Translation is very unsuccessful.
Then learn English. I did, and it helped.
If you can't or don't want to - find a forum in your language.
But if you're interested in technical subjects, you will have to learn English anyway.

Please explain the software parts from the beginning?
Parts of the firmware software (aka partitions) are explained in detail in my tutorial here:


Can you help me with what to do after this point?

Re-flash Primary Kernel.
If your log is truncated by you, that might be all that is required.
If the log really ends where your post ends, you will also have to re-flash Encrypted Partition.
Your Root filesystem is ok.
 
hello again , i passed by a used gimbal for a p3p, its cheap so i decided to check it the guy who have it pretend that it was working, any way i plugged it into a working p3p, it started the camera body dance correctly leveled, the gimbal started its front led, fan.. i launched the app it showed no vid , but all other communication telemetry info battery ... every thing is fine but vid is not their, is it a the fw on the gimbal board and the transmitter mismatch or a needed to flash gimbal, i recall on my last gimbal flashing fix using your help on this forum that the fw mismatch gives at least a noisy image, what do you suggest?
what happens if a working gimbal was reflashed , could that cause any harm?
 
Hello! What a great thread with so much great information. Thank you!

So I have come to one issue as many others. But I can't find something specific to my situation after reading the entire thread, so I will have do drop a question and hope to god that someone has a solution.

I have successfully soldered my TTL USB adapter to the board, and I did get the "BOTME" message to confirm that it was ready for flashing. I flashed the bootloader using ubl1.img and u-boot.img, and got a confirmation message saying the flashing were successful. But when I desoldered the wire frome the boot pads, it was still in BOOTME mode and it did not return my video feed when I put it all together. The pads are clean and should not be shorted. So I am wondering, what should I try next? I hope the chip isn't broken...
 
Hello! What a great thread with so much great information. Thank you!

So I have come to one issue as many others. But I can't find something specific to my situation after reading the entire thread, so I will have do drop a question and hope to god that someone has a solution.

I have successfully soldered my TTL USB adapter to the board, and I did get the "BOTME" message to confirm that it was ready for flashing. I flashed the bootloader using ubl1.img and u-boot.img, and got a confirmation message saying the flashing were successful. But when I desoldered the wire frome the boot pads, it was still in BOOTME mode and it did not return my video feed when I put it all together. The pads are clean and should not be shorted. So I am wondering, what should I try next? I hope the chip isn't broken...
Have you inserted a sd card and see if the camera controls work, or are they grayed out?
 
Have you inserted a sd card and see if the camera controls work, or are they grayed out?
Camera controls seem to work fine, except no video feed. I don't understand what I am missing here
 

Attachments

  • Screenshot_20210411-202506.jpg
    Screenshot_20210411-202506.jpg
    242 KB · Views: 158
Okay so I tried one more time with the manual mode, and it would not even flash succesfully:
-----------------------------------------------------
TI Serial Flasher Host Program for DM36x
(C) 2009, Texas Instruments, Inc.
Ver. 1.50
-----------------------------------------------------


Flashing NAND with ubl1.img and u-boot.img.


Attempting to connect to device COM6...
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
File ubl1.img is not present.


Interfacing to the DM36x via UART failed.
Please reset or power-cycle the board and try again...

And this is what I get with the flashing tool/script. I could not get the last bit because it closes the cmd when it is finished flashing:
-----------------------------------------------------
TI Serial Flasher Host Program for DM36x
(C) 2009, Texas Instruments, Inc.
Ver. 1.50
-----------------------------------------------------


Flashing NAND with ubl1.img and u-boot.img.


Attempting to connect to device COM6...
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.
28% [ ------------------------------------------- ]
Sending Image data...

But even though I desolder the bootloop pins I still get the BOOTME output in ZOC8 terminal. Seems to me like the pins are still shorted. but don't they need a 3.3v signal? or do I only need to short them?
 

Attachments

  • soldering.jpg
    soldering.jpg
    63.2 KB · Views: 164
  • Boot_pins.jpg
    Boot_pins.jpg
    208.5 KB · Views: 173
  • BOOTME.PNG
    BOOTME.PNG
    28.1 KB · Views: 169
You typically use a multimeter to check voltage on a pin.

...

Maybe you've damaged one of such resistors?
Yes, but should BT00 and BT01 have a 3.3v signal from the FTDI, or should they just be shorted between each other? Because I may hvae read the instructions wrong and fed them with 3.3v.

I might have to look for some other damage then, or simply accept that the board or chip is unrecoverable. This is starting to go beyond my set of skills. Perhaps there is a circuit diagram available?
 
Does the image data not finish sending?
Yes it does with the tool I am using. I just could not copy the entire thing because the terminal closes automaticaly when it finishes.
I’ve been using this tool from @SunsetCatcher to flash the P3P’s. ph3pns.zip
That is the "manual" tool that does'n work at all for me.
(Interfacing to the DM36x via UART failed.
Please reset or power-cycle the board and try again...)
 
@quaddamage

from yuor post number 82

Further to my message this is the issue im having, when i flash a P3P board a board that works once flashed shows this in the putty output

sulogin: no password entry for root
login[433]: root login on 'ttyS0'
#Process /etc/profile...
root@Dji-Pro:~#
encode_usb V00.02.02.00(Apr 11 2015 17:26:13).
Entry Encrypt qury mode
init libusb successed!!!
!!!!!!!!!!!!!!!![ 6.390000] EVM: switch to ambarella video input

The line INIT LIBUSB is the important one.

Now when they dont work they show

Entry Encrypt qury mode
Init libusb faild!

From reading the previous posts its something to do with encryption as i mentioned in my message to you and you posted a possible fix, which I've tested but hasnt worked, can you shed anymore light on this as I have a load of boards with this issue.
 
from yuor post number 82

Further to my message this is the issue im having, when i flash a P3P board a board that works once flashed shows this in the putty output

My post #82 is about so-called "8 fps issue". After I solved that issue, I updated post #5 with the solution.
That was a long time ago, but I don't remember "Init libusb faild!" having any relation to that issue.

What is the issue you're trying to solve?
 
My post #82 is about so-called "8 fps issue". After I solved that issue, I updated post #5 with the solution.
That was a long time ago, but I don't remember "Init libusb faild!" having any relation to that issue.

What is the issue you're trying to solve?
When this error occurs the app shows a black screen with DJI on it
 

Recent Posts

Members online

Forum statistics

Threads
143,066
Messages
1,467,352
Members
104,933
Latest member
mactechnic