I am trying to repair my phantom after having repaired the controller and have a similar problen of uart not connecting. I probably accidentaly removend the two black boxes nearest to the GND pad. Do you know what they are (what kind of resitors?). Should I try replacing them, or is there another method. And can you reupload or send me your diagram, please?Thank you sparkymonkey! After a lot of playing around, I managed to fix it!
I ended up soldering my GND cable to one of the other GND pads, they're all common - this gives you a hell of a lot more space to play with.
I also managed to solder a cable on to the TX pad (but not the RX pad) with a little bit of patience and some solder flux.
Finally, those resistors do in fact map to the TX and RX pads respectively, so if you've managed to rip one off, try soldering the GND to another GND pad, and either the TX or RX on to their respective pads, and then all you have left is to hold one jumper lead against the corresponding resistor.
Hope this helps anyone who got into the same stupid position that I did!
I've added a diagram to explain myself a little more clearly
TX and RX Resistors
- Joined
- Jun 2, 2016
- Messages
- 226
- Reaction score
- 160
Hi everyone!
Thank you all for all your efforts.
I managed to get everything working but I could only "jump-start" the RC with the commands through putty and I could later enter ftp and so forth. However the changes did not stick and as soon as I turned off the remote everything was back to normal. I was able to do this 3-4 times but after last time then I was no longer able to even jump-start it anymore. I now entered the boot loop, and going through all the suggestions for solutions I was able to at least enter the root and directory and find the rcS file in etc/init.d/rcS using the vi command and I can see all the ^M.
Is it possible for me to edit this? I pressed insert after entering through vi command to be able to change and modify which I did (removed all the ^M) however I'm not able to save the changes. Everything just reverts back, I know other people have used kermit and uploaded an working file - how to do that in a guide for dummies like me
This is how it looks for me:
U-Boot 1.1.4 (Mar 24 2016 - 12:37:01)
MI124
DRAM: 32 MB
Flash: 8 MB
In: serial
Out: serial
Err: serial
Press ESC to abort autoboot in 1 seconds
ar7240> setenv bootargs board=DJI-WM305 console=ttyS0,115200 root=/dev/mtdblock5
init=/bin/sh mtdparts=ath-nor0:256k@0k(u-boot),64k@256k(u-boot-env),896k@320k
(kernel1),3008k@1216k(rootfs1),896k@4224k(kernel2),3008k@5120k(rootfs2),64k@8128k
(art),3904k@320k(firmware1),3904k@4224k(firmware2),8192k@0k(all)
ar7240> bootm 0x9f420000
## Booting image at 9f420000 ...
Image Name: MIPS OpenWrt Linux-3.10.49
Created: 2015-08-20 3:19:32 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 905294 Bytes = 884.1 kB
Load Address: 80060000
Entry Point: 80060000
Verifying Checksum at 0x9f420040 ...OK
Uncompressing Kernel Image ... OK
Starting kernel ...
[ 0.000000] Linux version 3.10.49 (yello@ubuntu) (gcc version 4.8.3 (OpenWrt/Linaro
GCC 4.8-2014.04 r2635) ) #14 Thu Aug 20 11:19:19 CST 2015
[ 0.000000] bootconsole [early0] enabled
[ 0.000000] CPU revision is: 0001974c (MIPS 74Kc)
[ 0.000000] SoC: Atheros AR9342 rev 2
[ 0.000000] Clocks: CPU:560.000MHz, DDR:450.000MHz, AHB:225.000MHz, Ref:40.000MHz
[ 0.000000] Determined physical RAM map:
[ 0.000000] memory: 02000000 @ 00000000 (usable)
[ 0.000000] User-defined physical RAM map:
[ 0.000000] memory: 02000000 @ 00000000 (usable)
[ 0.000000] Initrd not found or empty - disabling initrd
[ 0.000000] Zone ranges:
[ 0.000000] Normal [mem 0x00000000-0x01ffffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x00000000-0x01ffffff]
[ 0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
[ 0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128
[ 0.000000] Kernel command line: board=DJI-WM305 console=ttyS0,115200
root=/dev/mtdblock5 init=/bin/sh mtdparts=ath-nor0:256k@0k(u-boot),64k@256k(u-boot-
env),896k@320k(kernel1),3008k@1216k(rootfs1),896k@4224k(kernel2),3008k@5120k
(rootfs2),64k@8128k(art),3904k@320k(firmware1),3904k@4224k(firmware2),8192k@0k(all)
mem=32M rootfstype=squashfs,jffs2 noinitrd
[ 0.000000] PID hash table entries: 128 (order: -3, 512 bytes)
[ 0.000000] Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000000] Writing ErrCtl register=00000000
[ 0.000000] Readback ErrCtl register=00000000
[ 0.000000] Memory: 29180k/32768k available (2102k kernel code, 3588k reserved, 363k
data, 220k init, 0k highmem)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] NR_IRQS:51
[ 0.000000] Calibrating delay loop... 278.93 BogoMIPS (lpj=1394688)
[ 0.070000] pid_max: default: 32768 minimum: 301
[ 0.070000] Mount-cache hash table entries: 512
[ 0.080000] NET: Registered protocol family 16
[ 0.080000] MIPS: machine is DJI WM305
[ 0.290000] ath_usb_init: id: 1122
[ 0.360000] bio: create slab <bio-0> at 0
[ 0.360000] Switching to clocksource MIPS
[ 0.370000] NET: Registered protocol family 2
[ 0.370000] TCP established hash table entries: 512 (order: 0, 4096 bytes)
[ 0.380000] TCP bind hash table entries: 512 (order: -1, 2048 bytes)
[ 0.390000] TCP: Hash tables configured (established 512 bind 512)
[ 0.390000] TCP: reno registered
[ 0.390000] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.400000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.410000] NET: Registered protocol family 1
[ 0.430000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.430000] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c)
2001-2006 Red Hat, Inc.
[ 0.440000] msgmni has been set to 56
[ 0.450000] io scheduler noop registered
[ 0.450000] io scheduler deadline registered (default)
[ 0.460000] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
[ 0.480000] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11) is a 16550A
[ 0.490000] console [ttyS0] enabled, bootconsole disabled
[ 0.490000] console [ttyS0] enabled, bootconsole disabled
[ 0.500000] ar934x-hs-uart.0: ttyATH0 at MMIO 0x18500000 (irq = 14) is a AR934X UART
[ 0.510000] ath79-spi ath79-spi: master is unqueued, this is deprecated
[ 0.520000] m25p80 spi0.0: found s25fl064k, expected m25p80
[ 0.530000] m25p80 spi0.0: s25fl064k (8192 Kbytes)
[ 0.530000] 10 cmdlinepart partitions found on MTD device ath-nor0
[ 0.540000] Creating 10 MTD partitions on "ath-nor0":
[ 0.540000] 0x000000000000-0x000000040000 : "u-boot"
[ 0.550000] 0x000000040000-0x000000050000 : "u-boot-env"
[ 0.560000] 0x000000050000-0x000000130000 : "kernel1"
[ 0.560000] 0x000000130000-0x000000420000 : "rootfs1"
[ 0.570000] 0x000000420000-0x000000500000 : "kernel2"
[ 0.580000] 0x000000500000-0x0000007f0000 : "rootfs2"
[ 0.580000] 0x0000007f0000-0x000000800000 : "art"
[ 0.590000] 0x000000050000-0x000000420000 : "firmware1"
[ 0.600000] 0x000000420000-0x0000007f0000 : "firmware2"
[ 0.600000] 0x000000000000-0x000000800000 : "all"
[ 0.610000] g_ether gadget: using random self ethernet address
[ 0.610000] g_ether gadget: using random host ethernet address
[ 0.620000] usb0: MAC da:2e:c5:00:5e:07
[ 0.630000] usb0: HOST MAC a2:b2:09:b7:4d:7e
[ 0.630000] g_ether gadget: Ethernet Gadget, version: Memorial Day 2008
[ 0.640000] g_ether gadget: g_ether ready
[ 0.640000] TCP: cubic registered
[ 0.650000] NET: Registered protocol family 17
[ 0.650000] 8021q: 802.1Q VLAN Support v1.8
[ 1.440000] jffs2: notice: (1) jffs2_build_xattr_subsystem: complete building xattr
subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
[ 1.460000] VFS: Mounted root (jffs2 filesystem) readonly on device 31:5.
[ 1.470000] Freeing unused kernel memory: 220K (802c9000 - 80300000)
BusyBox v1.22.1 (2015-06-29 19:28:31 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
/bin/sh: can't access tty; job control turned off
/ #
this is how it looks, I can from here enter different directories and so on. Is there a solution to this or should I just go for another remote?
Thank you in advance,
regards,
Maseko
Thank you all for all your efforts.
I managed to get everything working but I could only "jump-start" the RC with the commands through putty and I could later enter ftp and so forth. However the changes did not stick and as soon as I turned off the remote everything was back to normal. I was able to do this 3-4 times but after last time then I was no longer able to even jump-start it anymore. I now entered the boot loop, and going through all the suggestions for solutions I was able to at least enter the root and directory and find the rcS file in etc/init.d/rcS using the vi command and I can see all the ^M.
Is it possible for me to edit this? I pressed insert after entering through vi command to be able to change and modify which I did (removed all the ^M) however I'm not able to save the changes. Everything just reverts back, I know other people have used kermit and uploaded an working file - how to do that in a guide for dummies like me
This is how it looks for me:
U-Boot 1.1.4 (Mar 24 2016 - 12:37:01)
MI124
DRAM: 32 MB
Flash: 8 MB
In: serial
Out: serial
Err: serial
Press ESC to abort autoboot in 1 seconds
ar7240> setenv bootargs board=DJI-WM305 console=ttyS0,115200 root=/dev/mtdblock5
init=/bin/sh mtdparts=ath-nor0:256k@0k(u-boot),64k@256k(u-boot-env),896k@320k
(kernel1),3008k@1216k(rootfs1),896k@4224k(kernel2),3008k@5120k(rootfs2),64k@8128k
(art),3904k@320k(firmware1),3904k@4224k(firmware2),8192k@0k(all)
ar7240> bootm 0x9f420000
## Booting image at 9f420000 ...
Image Name: MIPS OpenWrt Linux-3.10.49
Created: 2015-08-20 3:19:32 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 905294 Bytes = 884.1 kB
Load Address: 80060000
Entry Point: 80060000
Verifying Checksum at 0x9f420040 ...OK
Uncompressing Kernel Image ... OK
Starting kernel ...
[ 0.000000] Linux version 3.10.49 (yello@ubuntu) (gcc version 4.8.3 (OpenWrt/Linaro
GCC 4.8-2014.04 r2635) ) #14 Thu Aug 20 11:19:19 CST 2015
[ 0.000000] bootconsole [early0] enabled
[ 0.000000] CPU revision is: 0001974c (MIPS 74Kc)
[ 0.000000] SoC: Atheros AR9342 rev 2
[ 0.000000] Clocks: CPU:560.000MHz, DDR:450.000MHz, AHB:225.000MHz, Ref:40.000MHz
[ 0.000000] Determined physical RAM map:
[ 0.000000] memory: 02000000 @ 00000000 (usable)
[ 0.000000] User-defined physical RAM map:
[ 0.000000] memory: 02000000 @ 00000000 (usable)
[ 0.000000] Initrd not found or empty - disabling initrd
[ 0.000000] Zone ranges:
[ 0.000000] Normal [mem 0x00000000-0x01ffffff]
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x00000000-0x01ffffff]
[ 0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
[ 0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128
[ 0.000000] Kernel command line: board=DJI-WM305 console=ttyS0,115200
root=/dev/mtdblock5 init=/bin/sh mtdparts=ath-nor0:256k@0k(u-boot),64k@256k(u-boot-
env),896k@320k(kernel1),3008k@1216k(rootfs1),896k@4224k(kernel2),3008k@5120k
(rootfs2),64k@8128k(art),3904k@320k(firmware1),3904k@4224k(firmware2),8192k@0k(all)
mem=32M rootfstype=squashfs,jffs2 noinitrd
[ 0.000000] PID hash table entries: 128 (order: -3, 512 bytes)
[ 0.000000] Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000000] Writing ErrCtl register=00000000
[ 0.000000] Readback ErrCtl register=00000000
[ 0.000000] Memory: 29180k/32768k available (2102k kernel code, 3588k reserved, 363k
data, 220k init, 0k highmem)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] NR_IRQS:51
[ 0.000000] Calibrating delay loop... 278.93 BogoMIPS (lpj=1394688)
[ 0.070000] pid_max: default: 32768 minimum: 301
[ 0.070000] Mount-cache hash table entries: 512
[ 0.080000] NET: Registered protocol family 16
[ 0.080000] MIPS: machine is DJI WM305
[ 0.290000] ath_usb_init: id: 1122
[ 0.360000] bio: create slab <bio-0> at 0
[ 0.360000] Switching to clocksource MIPS
[ 0.370000] NET: Registered protocol family 2
[ 0.370000] TCP established hash table entries: 512 (order: 0, 4096 bytes)
[ 0.380000] TCP bind hash table entries: 512 (order: -1, 2048 bytes)
[ 0.390000] TCP: Hash tables configured (established 512 bind 512)
[ 0.390000] TCP: reno registered
[ 0.390000] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.400000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.410000] NET: Registered protocol family 1
[ 0.430000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.430000] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c)
2001-2006 Red Hat, Inc.
[ 0.440000] msgmni has been set to 56
[ 0.450000] io scheduler noop registered
[ 0.450000] io scheduler deadline registered (default)
[ 0.460000] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
[ 0.480000] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11) is a 16550A
[ 0.490000] console [ttyS0] enabled, bootconsole disabled
[ 0.490000] console [ttyS0] enabled, bootconsole disabled
[ 0.500000] ar934x-hs-uart.0: ttyATH0 at MMIO 0x18500000 (irq = 14) is a AR934X UART
[ 0.510000] ath79-spi ath79-spi: master is unqueued, this is deprecated
[ 0.520000] m25p80 spi0.0: found s25fl064k, expected m25p80
[ 0.530000] m25p80 spi0.0: s25fl064k (8192 Kbytes)
[ 0.530000] 10 cmdlinepart partitions found on MTD device ath-nor0
[ 0.540000] Creating 10 MTD partitions on "ath-nor0":
[ 0.540000] 0x000000000000-0x000000040000 : "u-boot"
[ 0.550000] 0x000000040000-0x000000050000 : "u-boot-env"
[ 0.560000] 0x000000050000-0x000000130000 : "kernel1"
[ 0.560000] 0x000000130000-0x000000420000 : "rootfs1"
[ 0.570000] 0x000000420000-0x000000500000 : "kernel2"
[ 0.580000] 0x000000500000-0x0000007f0000 : "rootfs2"
[ 0.580000] 0x0000007f0000-0x000000800000 : "art"
[ 0.590000] 0x000000050000-0x000000420000 : "firmware1"
[ 0.600000] 0x000000420000-0x0000007f0000 : "firmware2"
[ 0.600000] 0x000000000000-0x000000800000 : "all"
[ 0.610000] g_ether gadget: using random self ethernet address
[ 0.610000] g_ether gadget: using random host ethernet address
[ 0.620000] usb0: MAC da:2e:c5:00:5e:07
[ 0.630000] usb0: HOST MAC a2:b2:09:b7:4d:7e
[ 0.630000] g_ether gadget: Ethernet Gadget, version: Memorial Day 2008
[ 0.640000] g_ether gadget: g_ether ready
[ 0.640000] TCP: cubic registered
[ 0.650000] NET: Registered protocol family 17
[ 0.650000] 8021q: 802.1Q VLAN Support v1.8
[ 1.440000] jffs2: notice: (1) jffs2_build_xattr_subsystem: complete building xattr
subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
[ 1.460000] VFS: Mounted root (jffs2 filesystem) readonly on device 31:5.
[ 1.470000] Freeing unused kernel memory: 220K (802c9000 - 80300000)
BusyBox v1.22.1 (2015-06-29 19:28:31 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
/bin/sh: can't access tty; job control turned off
/ #
this is how it looks, I can from here enter different directories and so on. Is there a solution to this or should I just go for another remote?
Thank you in advance,
regards,
Maseko
My method for rewriting flash and restoring rcS file, if someone needs it.
It works even if you cannot start linux, you only need u-boot.
I set up HyperTerminal like putty (speed =115200, flow control = none), wrote loadb on console, then with the right mouse button uploaded the flash.bin file from I bricked my p3s with ftp range mod - let's fix it together with kermit. Then I looked up the beginning of printenv result. There the two strings (lf and lk) are mixed up, I think. But I extrapolated the adress for the firmware's second copy with the help of information under //Creating 10 MTD partitions on "ath-nor0"// in log and then wrote:
erase 0x9f420000 +0x003d0000
cp.b 0x81000000 0x9f420000 0x003d0000
(File size (## Total Size = 0x003d0000 = 3997696 Bytes) was given by console after file loading.) The second firmware was overwritten. For the first one the first adress is 0x9f050000, I think.
It works even if you cannot start linux, you only need u-boot.
I set up HyperTerminal like putty (speed =115200, flow control = none), wrote loadb on console, then with the right mouse button uploaded the flash.bin file from I bricked my p3s with ftp range mod - let's fix it together with kermit. Then I looked up the beginning of printenv result. There the two strings (lf and lk) are mixed up, I think. But I extrapolated the adress for the firmware's second copy with the help of information under //Creating 10 MTD partitions on "ath-nor0"// in log and then wrote:
erase 0x9f420000 +0x003d0000
cp.b 0x81000000 0x9f420000 0x003d0000
(File size (## Total Size = 0x003d0000 = 3997696 Bytes) was given by console after file loading.) The second firmware was overwritten. For the first one the first adress is 0x9f050000, I think.
Last edited:
Alright guys, i managed finally to recover both rc and the drone.
Thank you all for you hard work and specially thanks to everyone that helped me out personally (Sugotron and Dmitri Feldman). For all of you who have entered the loop mode with the RC, follow Dmitri's guide with the hyperterminal and you will be able to recover it (worked for me). And to recover the drone just follow the steps from Sparkymarky.
Super happy camper over here, thank you all!
//Maseko
Thank you all for you hard work and specially thanks to everyone that helped me out personally (Sugotron and Dmitri Feldman). For all of you who have entered the loop mode with the RC, follow Dmitri's guide with the hyperterminal and you will be able to recover it (worked for me). And to recover the drone just follow the steps from Sparkymarky.
Super happy camper over here, thank you all!
//Maseko
Hi from Moscow!
Cool! Thanks! Worked! UART was connected, and I made kickback of the rcS file! It is good that they used OPEN WRT as an operating system!!
Cool! Thanks! Worked! UART was connected, and I made kickback of the rcS file! It is good that they used OPEN WRT as an operating system!!
I think I have ruined my backup file in the drone. Would you please give step by step guidance for a newbie like me? Thank you.
Can somebody tell me what's wrong with these:
Sorry, still trying to fix the drone. The firmware update method is not working. It writes in the log, when version checking// [07 00][00] device not detected// and then// Packet upgrade failed at version checking//. Maybe I broke something on the board. I don't think someone knows what this part refers to?
P.S. If I won't be able to fix the gimball board, is there a site to by it for Phantom 3 standart? I only found for advanced. Could I use it (maybe with modifications?)
P.S. If I won't be able to fix the gimball board, is there a site to by it for Phantom 3 standart? I only found for advanced. Could I use it (maybe with modifications?)
I'm using a usb-serial ch340 adapter. Attached to the remote control. Get garbled/garbage text that eventually turns to readable code when I let the system boot. My text inputs are readable and fine as well(see log1).
When I click escape the garbled characters continue and my inputs become garbled as well.(see log2) Using Putty on windows 10. I've set the baud rate to 115200, parity set to none, flow control set to none. UTF-8 for character set. Any ideas what's going on? I've tried changing the baud rate, flow control, parity bit and the character set. Nothing seems to work. I've tried using Windows as well as Ubuntu, same result. Is there another way to stop the boot sequence after it has started? Seems it will only work right AFTER it has booted.
When I click escape the garbled characters continue and my inputs become garbled as well.(see log2) Using Putty on windows 10. I've set the baud rate to 115200, parity set to none, flow control set to none. UTF-8 for character set. Any ideas what's going on? I've tried changing the baud rate, flow control, parity bit and the character set. Nothing seems to work. I've tried using Windows as well as Ubuntu, same result. Is there another way to stop the boot sequence after it has started? Seems it will only work right AFTER it has booted.
Hi, I just bricked mine as well, very surprised since I used WinSCP which I normally use when coding in linux.
Have a few quick questions
1. Can I use a Raspberry Pi to connect to the RC's TX and RX? The pi has 3.3v RX and TX but afraid to connect. Don't want to damage the pi
2. Can someone post a picture of the arduino connections to the RC?
3. I just bought CP2102 (CP2102 USB 2.0 to TTL UART Module 6Pin Serial Converter STC Replace FT232 Module) and awaiting arrival but it will take more than a week, hence question 1 and 2.
Hoping to have a successful restoration, terribly depressed over this - only flew it for 2 weeks, living in fear that I won't be able to get it restored
Have a few quick questions
1. Can I use a Raspberry Pi to connect to the RC's TX and RX? The pi has 3.3v RX and TX but afraid to connect. Don't want to damage the pi
2. Can someone post a picture of the arduino connections to the RC?
3. I just bought CP2102 (CP2102 USB 2.0 to TTL UART Module 6Pin Serial Converter STC Replace FT232 Module) and awaiting arrival but it will take more than a week, hence question 1 and 2.
Hoping to have a successful restoration, terribly depressed over this - only flew it for 2 weeks, living in fear that I won't be able to get it restored
I was able to get the remote controller booting again using the PI but I can't seem to get the PI to communicate with the aircraft to fix boot - nothing shows. Can anyone confirm the aircraft TTL is 3.3v or 5v?
The remote is not pairing with the aircraft so now I'm assuming the aircraft needs the rcS fix
The remote is not pairing with the aircraft so now I'm assuming the aircraft needs the rcS fix
I believe he is referring to the serial to TTL device to connect the computer to the drone. My aircraft is still bricked and from a few posts it seems the Arduino or Serial to TTL can fix it. I am hoping that this works since the raspberry pi is not communicated with the aircraft (only got it to work on the RC). Hoping its because the Rx and Tx from the aircraft is using the 5v which explain this issue.
Now I cannot connect to my aircraft via UART by using arduino uno, ruined the system images I guess.
If I replace the gimbal will it work? Is there anyone doing this and then everything is solved?
Thank you
If I replace the gimbal will it work? Is there anyone doing this and then everything is solved?
Thank you
That's strange, the only way you could ruin the system images or the files would be if you edited more than the rcS files. Were you able to connect via UART before and tried to fix the files and now you cannot connect OR you've not been able to connect at all?
I think you should double check your solder connections, post a pic so I can see.
What I did was connect UNO RX to Aircraft TX. Then connection UNO TX to Aircraft RX. There are multiple ground points on the aircraft board so you can solder the ground to an alternative point so you have enough space to work with the U2_RX and U2_TX
Just an update since it seems this thread has been mostly inactive/dead from the previous posters who seemed to fixed theirs.
MY RC AND AIRCRAFT HAS BEEN RESTORED! Thanks to all who posted instructions for solutions!
Just to clarify:
I used the Raspberry PI 2 B model to fix the Remote Controller. It seems the Remote Controller runs at 3.3v ttl since it worked. PI 2 did not work on the drone.
I used the Arduino UNO R3 to fix the Aircraft. It seems the Aircraft runs at 5v ttl (do not use the pi, it could damage your pi)
Both scenarios were the same as suggested in the first post that sums up the process. Commands are the same.
Remember that you are copying/restoring files FROM the /etc/init.d/ directory TO your /tmp/flash/etc/init.d directory (DO NOT... I REPEAT... DO NOT MIX THIS UP!)
I used the following command (because I had edited all my rcS files)
cp /etc/init.d/rc* /tmp/flash/etc/init.d/
Good luck, email me if you have any questions and I will try to help
MY RC AND AIRCRAFT HAS BEEN RESTORED! Thanks to all who posted instructions for solutions!
Just to clarify:
I used the Raspberry PI 2 B model to fix the Remote Controller. It seems the Remote Controller runs at 3.3v ttl since it worked. PI 2 did not work on the drone.
I used the Arduino UNO R3 to fix the Aircraft. It seems the Aircraft runs at 5v ttl (do not use the pi, it could damage your pi)
Both scenarios were the same as suggested in the first post that sums up the process. Commands are the same.
Remember that you are copying/restoring files FROM the /etc/init.d/ directory TO your /tmp/flash/etc/init.d directory (DO NOT... I REPEAT... DO NOT MIX THIS UP!)
I used the following command (because I had edited all my rcS files)
cp /etc/init.d/rc* /tmp/flash/etc/init.d/
Good luck, email me if you have any questions and I will try to help
I already have checked the connection, even I change the jumper cables as well. It connected to my computer before, I thought that editing rcS, rcS_ap, rcS_aphand, and rcS_cli ruined everything. Thanks to everyone here, I have recovered the transmitter, sadly had no luck with the aircraft. I am frustrated and desperate, it has been more than 2 months since I bricked my P3S, and now my aircraft cannot connect with my computer via UART. I was thinking about replacing the gimbal board might solve the problem. Need your advice or anyone here, will replacing gimbal board solve the problem?
Thank you
