Recent content by masterphantom

For now I have Linux boot, I can ping Eth0 at 192.168.10, but dont have any opened port. I need to find solution how video is transmited to WiFi module, is it like a network stream or USB connection, and check how to recive video signal from Ambarella....

Maybe kernel start booting at diff. offset. It is not possible that both kernel are damaged: ** Unknown image type

Dumping NAND is like a having bank account. This is insurance for future, for one day.... We need kernel, and working FileSystem, because all settings is in the FS. But who would like to dump images for P2 Vision and P2 Vision Plus.

Yes, I was use command nand erase.chip and after that Uboot, UBL,...tmp FS, FS, AT88, kernel,... All parts from P3 and LB. I will try to modify, but best solution is to find FS and kernel. Or just File System.

I dont know how to update FC200 camera, I know there is one bin file to update board #1 (with Ambarella SoC.), but not sure is that file update firmware too on board #3. For now only ping is possible, but still without video feed. I was try with kernel from LB and P3 top board. With LB there is...

root@Dji-Pro:~# ifconfig eth0 Link encap:Ethernet HWaddr 1A:D1:01:AC:40:39 inet addr:192.168.1.10 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX...

Finaly got Live LINUX kernel boot, but still need to work on image. 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...

After all day on console and PC, here is result: 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...

Good morning, I was try to fix Phnatom 2 Vision FC200 camera (EGG). When I connect UART to camera Board#3 I got this msg: DM36x initialization passed! TI UBL Version: 1.50 Booting Catalog Boot Loader BootMode = NAND Starting NAND Copy... Valid magicnum, 0xA1ACED66, found in block 0x00000019...

Dji-Pro # nand bad Device 0 bad blocks: 07f80000 07fa0000 07fc0000 07fe0000 Dji-Pro #

I just try to flash with gl300_dm365_recovery_kernel using ZMODEM and here is result: 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...

Many thanks for great info. I will try to find working kernel for this board. If you think or/and have kernel for P3 with smilar HW, pls post it here, so I can try.

Hmm...You mean that I need to find working DaVinci Linux kernel as OS ( at adress 0x900000 uImage_recovery, not included in FW updates; the Linux Kernel which is used when primary kernel gets corrupted ) and flash it with command "sfh_DM36x.exe -nandflash -v -p "COMXX" example.img"? My working...

Finally got BOOTME msg and after flashing here is report: BOOTME BOOTME BOOTME BOOTME BOOTME BOOTMEř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...

Did You find solution to enter BOOTME state, any scheme or pinout?