Is there a solution to do the same procedure with my dji goggles?
Dji Goggles are basically a cellphone. Completely different technology.
To do anything with cellphone, you need to root it first. Same with goggles.
Is there a solution to do the same procedure with my dji goggles?
M36x 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: 2014-04-09 12:21:58 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3823424 Bytes = 3.6 MiB
Load Address: 80008000
Entry Point: 80008000
## Booting kernel from Legacy Image at 80700000 ...
Image Name: Linux-2.6.32.17-davinci1
Created: 2014-04-09 12:21:58 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3823424 Bytes = 3.6 MiB
Load Address: 80008000
Entry Point: 80008000
Loading Kernel Image ... OK
OK
Starting kernel ...
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)
The kernel which starts booting is a recovery kernel.
Recently someone posted a FW which he claimed was from P2Vp. That included kernel and rootfs. Try searching for that post.
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
Image Name: Linux-2.6.32.17-davinci1
Created: 2014-04-09 12:21:58 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3823424 Bytes = 3.6 MiB
Load Address: 80008000
Entry Point: 80008000
## Booting kernel from Legacy Image at 80700000 ...
Image Name: Linux-2.6.32.17-davinci1
Created: 2014-04-09 12:21:58 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3823424 Bytes = 3.6 MiB
Load Address: 80008000
Entry Point: 80008000
Loading Kernel Image ... OK
OK
Starting kernel ...
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
Starting kernel...
and then reboot. I understand that the kernel is not booting as I don't see any message, or could it be the rootfs? Another question. I'm testing all of that with the wifi module alone, I understand that I don't need to connect it to the "other" wifi module in the metal case? Right?I still get theStarting kernel...
and then reboot.
I'm testing all of that with the wifi module alone, I understand that I don't need to connect it to the "other" wifi module in the metal case?
the big chip next to the boot select solder points seems to have strange bulges, so probably it is damaged
Hi
Is there a solution for the P2V+ ground unit after firmwareproblem done by DJI?
Fabio
still would like to repair my ground units from the p2v+. The RE700 are broken after update via android app. Is there no way to reflash them with openwrt/ddwrt/lucie?
but when I run the program (step 6) the program gets stuck in the message:
Waiting for the DM36x ...
When I turn on LB it only gives:
Target:?
What did u do my doing the same thing ?Hi All,
I want to say thank you to all the hard work with this. There's a number of Vision Plus units that have no live view. It's a corrup NAND in the WiFi transmitter board that responds to 192.168.1.10. Using the sfh_DM36x tool I was able to resolve this and I now have my live view back!