GL300A Remote Controller help

[Wrecked]

Managed to do the flash, although it was with the files for the gimbal. I just hope they are the same..

Here is the result:

-----------------------------------------------------
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 COM13...
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 0x000000
00
Target: Erasing block 0x00000002 through 0x00000002.
Target: Writing header and image data to Block 0x00000002, Page 0x000000
00
Target: Erasing block 0x00000003 through 0x00000003.
Target: Writing header and image data to Block 0x00000003, Page 0x000000
00
Target: Erasing block 0x00000004 through 0x00000004.
Target: Writing header and image data to Block 0x00000004, Page 0x000000
00
Target: Erasing block 0x00000005 through 0x00000005.
Target: Writing header and image data to Block 0x00000005, Page 0x000000
00
Target: Erasing block 0x00000006 through 0x00000006.
Target: Writing header and image data to Block 0x00000006, Page 0x000000
00
Target: Erasing block 0x00000007 through 0x00000007.
Target: Writing header and image data to Block 0x00000007, Page 0x000000
00
Target: Erasing block 0x00000008 through 0x00000008.
Target: Writing header and image data to Block 0x00000008, Page 0x000000
00
Target: Erasing block 0x00000009 through 0x00000009.
Target: Writing header and image data to Block 0x00000009, Page 0x000000
00
Target: Erasing block 0x0000000A through 0x0000000A.
Target: Writing header and image data to Block 0x0000000A, Page 0x000000
00
Target: Erasing block 0x0000000B through 0x0000000B.
Target: Writing header and image data to Block 0x0000000B, Page 0x000000
00
Target: Erasing block 0x0000000C through 0x0000000C.
Target: Writing header and image data to Block 0x0000000C, Page 0x000000
00
Target: Erasing block 0x0000000D through 0x0000000D.
Target: Writing header and image data to Block 0x0000000D, Page 0x000000
00
Target: Erasing block 0x0000000E through 0x0000000E.
Target: Writing header and image data to Block 0x0000000E, Page 0x000000
00
Target: Erasing block 0x0000000F through 0x0000000F.
Target: Writing header and image data to Block 0x0000000F, Page 0x000000
00
Target: Erasing block 0x00000010 through 0x00000010.
Target: Writing header and image data to Block 0x00000010, Page 0x000000
00
Target: Erasing block 0x00000011 through 0x00000011.
Target: Writing header and image data to Block 0x00000011, Page 0x000000
00
Target: Erasing block 0x00000012 through 0x00000012.
Target: Writing header and image data to Block 0x00000012, Page 0x000000
00
Target: Erasing block 0x00000013 through 0x00000013.
Target: Writing header and image data to Block 0x00000013, Page 0x000000
00
Target: Erasing block 0x00000014 through 0x00000014.
Target: Writing header and image data to Block 0x00000014, Page 0x000000
00
Target: Erasing block 0x00000015 through 0x00000015.
Target: Writing header and image data to Block 0x00000015, Page 0x000000
00
Target: Erasing block 0x00000016 through 0x00000016.
Target: Writing header and image data to Block 0x00000016, Page 0x000000
00
Target: Erasing block 0x00000017 through 0x00000017.
Target: Writing header and image data to Block 0x00000017, Page 0x000000
00
Target: Erasing block 0x00000018 through 0x00000018.
Target: Writing header and image data to Block 0x00000018, Page 0x000000
00
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.
100% [ ]
Image data sent...


Waiting for DONE...
Target: DONE
DONE received. All bytes of image data received...
Target: Writing APP to NAND flash
Target: Unprotecting blocks 0x00000019 through 0x00000032.
Target: Number of blocks needed for header and data: 0x0x00000003
Target: Attempting to start in block number 0x0x00000019.
Target: Erasing block 0x00000019 through 0x0000001B.
Target: Writing header and image data to Block 0x00000019, Page 0x000000
00
Target: Erasing block 0x0000001C through 0x0000001E.
Target: Writing header and image data to Block 0x0000001C, Page 0x000000
00
Target: Erasing block 0x0000001F through 0x00000021.
Target: Writing header and image data to Block 0x0000001F, Page 0x000000
00
Target: Erasing block 0x00000022 through 0x00000024.
Target: Writing header and image data to Block 0x00000022, Page 0x000000
00
Target: Erasing block 0x00000025 through 0x00000027.
Target: Writing header and image data to Block 0x00000025, Page 0x000000
00
Target: Erasing block 0x00000028 through 0x0000002A.
Target: Writing header and image data to Block 0x00000028, Page 0x000000
00
Target: Erasing block 0x0000002B through 0x0000002D.
Target: Writing header and image data to Block 0x0000002B, Page 0x000000
00
Target: Erasing block 0x0000002E through 0x00000030.
Target: Writing header and image data to Block 0x0000002E, Page 0x000000
00
Target: Protecting the entire NAND flash.
Target: DONE
Target: DONE

Operation completed successfully.

C:\BluetoothExchangeFolder\P3X Gimbal fix>

 

[Wrecked]

Does this look right?

This is what I get now when starting the board with the bootpatch:

DM36x initialization passed!
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-02-12 3:09:59 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3665856 Bytes = 3.5 MiB
Load Address: 80008000
Entry Point: 80008000
## Booting kernel from Legacy Image at 80700000 ...
Image Name: Linux-2.6.32.17-davinci1
Created: 2015-02-12 3:09:59 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3665856 Bytes = 3.5 MiB
Load Address: 80008000
Entry Point: 80008000
Loading Kernel Image ... OK
OK

Starting kernel ...

[ 0.000000] Kernel Product Vesion : DJI-GRC-Kernel-1.0-rc8(2014-11-21)
[ 0.000000] Linux version 2.6.32.17-davinci1 (u@dji) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 PREEMPT Thu Feb 12 11:09:57 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 pages: 12192
[ 0.000000] Kernel command line: console=ttyS0,115200n8 rw dm365_imp.oper_mode=0 video=davincifb:vid0=0,10K:vid1=0,10Ksd0=1920x1080X16,8100K mem=48MB davinci_enc_mngr.ch0_output=COMPOSITE davinci_enc_mngr.ch0_mode=pal ubi.mtd=2,2048 root=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: 44836KB available (3304K code, 409K data, 108K init, 0K highmem)
[ 0.000000] SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=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.080000] bio: create slab <bio-0> at 0
[ 0.080000] SCSI subsystem initialized
[ 0.090000] usbcore: registered new interface driver usbfs
[ 0.090000] usbcore: registered new interface driver hub
[ 0.090000] usbcore: registered new device driver usb
[ 0.100000] cfg80211: Using static regulatory domain info
[ 0.100000] cfg80211: Regulatory domain: US
[ 0.100000] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 0.100000] (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm)
[ 0.100000] (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 0.100000] (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 0.100000] (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 0.100000] (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm)
[ 0.100000] (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm)
[ 0.100000] cfg80211: Calling CRDA for country: US
[ 0.100000] Switching to clocksource timer0_1
[ 0.110000] musb_hdrc: version 6.0, pio, host, debug=0
[ 0.130000] musb_hdrc: USB Host mode controller at fec64000 using PIO, IRQ 12
[ 0.130000] musb_hdrc musb_hdrc: MUSB HDRC host driver
[ 0.130000] musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
[ 0.130000] usb usb1: configuration #1 chosen from 1 choice
[ 0.130000] hub 1-0:1.0: USB hub found
[ 0.130000] hub 1-0:1.0: 1 port detected
[ 0.130000] NET: Registered protocol family 2
[ 0.130000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.130000] TCP established hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.130000] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.130000] TCP: Hash tables configured (established 2048 bind 2048)
[ 0.130000] TCP reno registered
[ 0.130000] NET: Registered protocol family 1
[ 0.130000] RPC: Registered udp transport module.
[ 0.130000] RPC: Registered tcp transport module.
[ 0.130000] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.140000] kfile init
[ 0.140000] JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 0.140000] msgmni has been set to 87
[ 0.150000] alg: No test for stdrng (krng)
[ 0.150000] io scheduler noop registered (default)
[ 0.210000] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 0.210000] serial8250.0: ttyS0 at MMIO 0x1c20000 (irq = 40) is a 16550A
[ 0.580000] console [ttyS0] enabled
[ 0.590000] serial8250.0: ttyS1 at MMIO 0x1d06000 (irq = 41) is a 16550A
[ 0.600000] brd: module loaded
[ 0.610000] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xf1 (Micron NAND 128MiB 3,3V 8-bit)
[ 0.620000] Creating 4 MTD partitions on "davinci_nand.0":
[ 0.620000] 0x000000000000-0x0000004a0000 : "bootloader"
[ 0.630000] 0x0000004a0000-0x000000e00000 : "kernel"
[ 0.640000] 0x000000e00000-0x000007f00000 : "filesystem"
[ 0.650000] 0x000000000000-0x000008000000 : "all"
[ 0.660000] davinci_nand davinci_nand.0: controller rev. 2.3
[ 0.660000] UBI: attaching mtd2 to ubi0
[ 0.670000] UBI: physical eraseblock size: 131072 bytes (128 KiB)
[ 0.670000] UBI: logical eraseblock size: 126976 bytes
[ 0.680000] UBI: smallest flash I/O unit: 2048
[ 0.680000] UBI: sub-page size: 512
[ 0.690000] UBI: VID header offset: 2048 (aligned 2048)
[ 0.700000] UBI: data offset: 4096
[ 0.820000] usb 1-1: new high speed USB device using musb_hdrc and address 2
[ 0.970000] usb 1-1: configuration #1 chosen from 1 choice
[ 0.970000] hub 1-1:1.0: USB hub found
[ 0.990000] hub 1-1:1.0: 2 ports detected
[ 1.210000] UBI: attached mtd2 to ubi0
[ 1.210000] UBI: MTD device name: "filesystem"
[ 1.220000] UBI: MTD device size: 113 MiB
[ 1.220000] UBI: number of good PEBs: 904
[ 1.230000] UBI: number of bad PEBs: 0
[ 1.230000] UBI: max. allowed volumes: 128
[ 1.240000] UBI: wear-leveling threshold: 4096
[ 1.240000] UBI: number of internal volumes: 1
[ 1.250000] UBI: number of user volumes: 1
[ 1.250000] UBI: available PEBs: 0
[ 1.250000] UBI: total number of reserved PEBs: 904
[ 1.260000] UBI: number of PEBs reserved for bad PEB handling: 9
[ 1.270000] UBI: max/mean erase counter: 115/1
[ 1.270000] UBI: image sequence number: 268688541
[ 1.280000] UBI: background thread "ubi_bgt0d" started, PID 272
[ 1.280000] console [netcon0] enabled
[ 1.290000] netconsole: network logging started
[ 1.290000] Initializing USB Mass Storage driver...
[ 1.300000] usbcore: registered new interface driver usb-storage
[ 1.300000] USB Mass Storage support registered.
[ 1.310000] usbcore: registered new interface driver usbtest
[ 1.320000] i2c /dev entries driver
[ 1.320000] watchdog watchdog: heartbeat 1 sec
[ 1.330000] TCP cubic registered
[ 1.330000] NET: Registered protocol family 17
[ 1.340000] lib80211: common routines for IEEE802.11 drivers
[ 1.340000] ksocket init
[ 1.370000] encrypt device:atsha204 found
[ 1.460000] mfi_i2c_client addr:17
[ 1.470000] Clocks: disable unused vpss_master
[ 1.470000] Clocks: disable unused mmcsd0
[ 1.470000] Clocks: disable unused mmcsd1
[ 1.470000] Clocks: disable unused spi0
[ 1.470000] Clocks: disable unused spi1
[ 1.470000] Clocks: disable unused spi2
[ 1.470000] Clocks: disable unused spi3
[ 1.470000] Clocks: disable unused spi4
[ 1.470000] Clocks: disable unused pwm0
[ 1.470000] Clocks: disable unused pwm1
[ 1.470000] Clocks: disable unused pwm2
[ 1.470000] Clocks: disable unused pwm3
[ 1.470000] Clocks: disable unused timer1
[ 1.470000] Clocks: disable unused timer3
[ 1.470000] Clocks: disable unused emac
[ 1.470000] Clocks: disable unused voice_codec
[ 1.470000] Clocks: disable unused asp0
[ 1.470000] Clocks: disable unused rto
[ 1.470000] Clocks: disable unused mjcp
[ 1.550000] davinci_emac_probe: using random MAC addr: ce:83:f2:81:d1:52
[ 1.560000] emac-mii: probed
[ 1.600000] UBIFS: recovery needed
[ 1.670000] UBIFS: recovery completed
[ 1.680000] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[ 1.680000] UBIFS: file system size: 110342144 bytes (107756 KiB, 105 MiB, 869 LEBs)
[ 1.690000] UBIFS: journal size: 9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
[ 1.700000] UBIFS: media format: w4/r0 (latest is w4/r0)
[ 1.710000] UBIFS: default compressor: lzo
[ 1.710000] UBIFS: reserved for root: 0 bytes (0 KiB)
[ 1.720000] VFS: Mounted root (ubifs filesystem) on device 0:13.
[ 1.720000] Freeing init memory: 108K

Filesystem Product Vesion : DJI-Filesystem-1.0-rc2
Runing /etc/init.d/rcS
[ 3.460000] CMEMK module: built on Jul 30 2014 at 10:21:45
[ 3.480000] Reference Linux version 2.6.32
[ 3.480000] File /home/u/work/svn/dec_grc/src/dvsdk/dvsdk_dm368_4_02_00_06/linuxutils_2_26_01_02/packages/ti/sdo/linuxutils/cmem/src/module/cmemk.c
[ 3.500000] allocated heap buffer 0xc7000000 of size 0x4400000
[ 3.530000] heap fallback enabled - will try heap if pool buffer is not available
[ 3.530000] CMEM Range Overlaps Kernel Physical - allowing overlap
[ 3.540000] CMEM phys_start (0x1000) overlaps kernel (0x80000000 -> 0x83000000)
[ 3.550000] cmemk initialized
[ 3.580000] IRQK module: built on Jul 30 2014 at 10:21:09
[ 3.580000] Reference Linux version 2.6.32
[ 3.600000] File /home/u/work/svn/dec_grc/src/dvsdk/dvsdk_dm368_4_02_00_06/linuxutils_2_26_01_02/packages/ti/sdo/linuxutils/irq/src/module/irqk.c
[ 3.620000] irqk initialized
[ 3.670000] EDMAK module: built on Jul 30 2014 at 10:19:34
[ 3.670000] Reference Linux version 2.6.32
[ 3.690000] File /home/u/work/svn/dec_grc/src/dvsdk/dvsdk_dm368_4_02_00_06/linuxutils_2_26_01_02/packages/ti/sdo/linuxutils/edma/src/module/edmak.c
[ 3.910000] exFAT: Version 1.2.9
settime failed
[ 7.340000] UBI: scrubbed PEB 162 (LEB 0:160), data moved to PEB 639
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[ 8.600000] UBI: scrubbed PEB 540 (LEB 0:468), data moved to PEB 667
[ 11.600000] usbcore: registered new interface driver usb_applehid
[ 11.610000] usb applehid module init ok
[ 11.680000] usbcore: registered new interface driver usb_68013
[ 11.690000] usb 68013 module init ok
sulogin: no password entry for root
login[407]: root login on 'ttyS0'
#Process /etc/profile...
root@Dji-Pro:~# encrypt check ok
init libusb successed!!!
usbmuxd disabled
usbsocket_init OK
usbsocket_create_handle ok, port:22345, bCanRecv:1
usbsocket_create_handle ok, port:22346, bCanRecv:0
watchdog timeout:5
DummyRead68013 0.000000kb
umount: can't umount /mnt/usb: No such file or directory
rmdir: '/mnt/usb': No such file or directory
DummyRead68013 0.000000kb
DummyRead68013 0.000000kb
DummyRead68013 0.000000kb
DummyRead68013 0.000000kb
DummyRead68013 0.000000kb
encrypt chip exist
DummyRead68013 0.000000kb
DummyRead68013 0.000000kb
DummyRead68013 0.000000kb
DummyRead68013 0.000000kb
DummyRead68013 0.000000kb
DummyRead68013 0.000000kb
DummyRead68013 0.000000kb
DummyRead68013 0.000000kb
DummyRead68013 0.000000kb
DummyRead68013 0.000000kb
DummyRead68013 0.000000kb
DummyRead68013 0.000000kb
DummyRead68013 0.000000kb
DummyRead68013 0.000000kb
DummyRead68013 0.000000kb
DummyRead68013 0.000000kb
DummyRead68013 0.000000kb
DummyRead68013 0.000000kb
DummyRead68013 0.000000kb
DummyRead68013 0.000000kb
DummyRead68013 0.000000kb
DummyRead68013 0.000000kb
DummyRead68013 0.000000kb

 

[loonie01]

I also kept getting the Dummyread.

 

[quaddamage]

I also kept getting the Dummyread.

Use "stop" command to make the console more clean and responsive.

Check in the log whether your primary kernel is damaged. If it is - re-flash it. If not - the board is ready to put back into RC.

 

[loonie01]

Use "stop" command to make the console more clean and responsive.

Check in the log whether your primary kernel is damaged. If it is - re-flash it. If not - the board is ready to put back into RC.

That's the thing, I'm not sure how to flash the kernel.

 

[quaddamage]

That's the thing, I'm not sure how to flash the kernel.

And how come you are sure you should flash it, then?

 

[loonie01]

And how come you are sure you should flash it, then?

I'm not but flashing the kernel won't hurt

 

[loonie01]

I'm done with this USB board. I there are some being sold on Ebay for $25. I'm just going to try them.

 

[quaddamage]

Does this look right?

[...]

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-02-12 3:09:59 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3665856 Bytes = 3.5 MiB
Load Address: 80008000
Entry Point: 80008000
## Booting kernel from Legacy Image at 80700000 ...
Image Name: Linux-2.6.32.17-davinci1
Created: 2015-02-12 3:09:59 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3665856 Bytes = 3.5 MiB
Load Address: 80008000
Entry Point: 80008000
Loading Kernel Image ... OK
OK

Starting kernel ...

Recovery kernel is booting. Primary kernel should be at NAND address 0x4a0000, but it's damaged.
Do you have the kernel image extracted from C1_FW ?

 

[Wrecked]

Quaddamage, I just used the files from the p3p gimbal package. I dont know how to get the kernel file for the usb board.

 

[Wrecked]

I'm done with this USB board. I there are some being sold on Ebay for $25. I'm just going to try them.

Tried that, and it didnt work. Those on ebay doesnt fit the gl300a controller. You need a usb board with 3 chips like the original, and they are nowhere to be found.

 

[quaddamage]

Quaddamage, I just used the files from the p3p gimbal package. I dont know how to get the kernel file for the usb board.

If you are looking for help, describe the issue.

 

[Wrecked]

I do not know where to find the firmware files for the GL300A remote controller, and I do not know how to extract the files I need. Im on a win7 box, and do not know anything about linux commands.

 

[quaddamage]

I do not know where to find the firmware files for the GL300A remote controller

Here:
phantom-firmware-tools/supported_firmwares.csv at master · mefistotelis/phantom-firmware-tools · GitHub

I do not know how to extract the files I need.

I believe I already provided you with instructions on that:
GL300A Remote Controller help

Im on a win7 box, and do not know anything about linux commands.

You can install Linux in many ways which would give you access to these tools, ie. USB drive or VM. Or you can use Windows port of the toolchain - msys2.

 

[Wrecked]

Here:
phantom-firmware-tools/supported_firmwares.csv at master · mefistotelis/phantom-firmware-tools · GitHub



I believe I already provided you with instructions on that:
GL300A Remote Controller help


You can install Linux in many ways which would give you access to these tools, ie. USB drive or VM. Or you can use Windows port of the toolchain - msys2.

Thanks for your help. Much appreciated!

Hmm: I can't see firmware for GL300A in your link.

I believe you did send me some links earlier to github regardig how to extract the files, but when I found out the commands required was linux, I got stuck.

Guess I will have to learn some linux to make this happen. At least until someone does the work for us, like in the step-by-step guide for the P3P gimbal board

 

[Wrecked]

Recovery kernel is booting. Primary kernel should be at NAND address 0x4a0000, but it's damaged.
Do you have the kernel image extracted from C1_FW ?

Does it really matter what kernal is booting? Maybe recovery kernal works just as fine?

So the C1_FW is for the GL300A controller? Then I guess I can find it in your link. But should I go with lowercase v or uppercase V. C1_FW_V01.06.0020.bin or C1_FW_v01.09.0000.bin.

 

[quaddamage]

Hmm: I can't see firmware for GL300A in your link.

Note what I wrote here:

Do you have the kernel image extracted from C1_FW ?

EDIT: ok, you found it, good. The size of your "V" does not matter.

Guess I will have to learn some linux to make this happen.

Linux is an OS which everyone should know. I believe it is easier to use than Windows.

But what you really need to learn is how to use command line. In any OS. Note that I mentioned msys2 if you want to do it in Windows. If you don't know the thing I'm mentioning, you should google it.

 

[quaddamage]

Does it really matter what kernal is booting? Maybe recovery kernal works just as fine?

Depends on what you want to do within it. It is very useful, without it you wouldn't have access to many tools during recovery.

 

[Wrecked]

Ahh right, sorry I missed that. My brain is smoking from all this information...

Will have a look at msys2 and see if that will work for me

Thanks!

 

[Wrecked]

Depends on what you want to do within it. It is very useful, without it you wouldn't have access to many tools during recovery.

Ohh, I really just want my USB board to talk with my phone. When I plugged in my phone, it would not do anything. Usually it would start Dji GO