Controller help; flashing red and beeping

After using a thing too much, I sometimes forget it wasn't obvious to me at some point as well..

Use any serial terminal app - minicom/picocom on Linux, PuTTY on Windows.

Here's some info on the interface, and transmission params to set:
m1300 DaVinci (in RC) - Debug serial interface
m0800 DaVinci (in gimbal) - Debug serial interface 368_U0

Thanks for the info

I'm obviously doing something wrong. (See attached)

Is there a way to do this in windows? I am more familiar with the windows OS.

bootup.png
 
Yes - note I mentioned PuTTY.
The output suggests invalid transmission params. Check them, especially baud rate.

It was the baud rate causing the issues.

Also in looking at the diagnosis graph by @quaddamage it appears that it is booting correctly.....but can someone confirm this for me? Because I still can't connect to the app.
 

Attachments

  • putty1.txt
    12.8 KB · Views: 168
Last edited:
I amazed you did all that,I not seen anyone else do this to sort a can't conect to app issue,,mayby it help mayby it not,your still at square 1 after doing all that,good on you though,best way to learn,,,have you try usb cord,if this is breaking down it won't conect but I'm still stumped on the red and green flashing why it is looping like that,light chart says it is updating when flashing these colours,which remote did you end up with gl300a or gl300c,you said it was cheap ,did seller say it work ok,just curious, 2 remotes and still can't conect,,it should start up straight away,there is a chance usb module bit sic but on both remotes,,have to also ask was this drone new or used
 
I amazed you did all that,I not seen anyone else do this to sort a can't conect to app issue,,mayby it help mayby it not,your still at square 1 after doing all that,good on you though,best way to learn,,,[\QUOTE]

Yes it is a good learning experience. I don't mind troubleshooting with everyones help from this forum. You guys have been great and very helpful.

have you try usb cord,if this is breaking down it won't conect but I'm still stumped on the red and green flashing why it is looping like that,light chart says it is updating when flashing these colours, [\QUOTE]

I did try an different cable but Im going to switch it out for another just in case it is something simple


which remote did you end up with gl300a or gl300c,you said it was cheap ,did seller say it work ok,just curious, 2 remotes and still can't conect,,it should start up straight away,there is a chance usb module bit sic but on both remotes,,have to also ask was this drone new or used

I ended up with a gl300a. Seller did say it works, but who knows if they were telling the truth. The first remote I knew had issues. Drone is used, but at this point I dont even care about the AC. Just want to get the controller working and connected to app.
 
Sorry aswell for some my posts,I'm just trying to eliminate ,such a annoying issue you got that why I was asking if new or used,someone might have just porned their problems on to you,if new get exchanged,could be a fault with the drone,,when all powered on what are your lights telling you,,what colours on drone,we know remote red and green.......OK I read ist post again and says it used,,did you see it go,,,
 
Sorry aswell for some my posts,I'm just trying to eliminate ,such a annoying issue you got that why I was asking if new or used,someone might have just porned their problems on to you,if new get exchanged,could be a fault with the drone,,when all powered on what are your lights telling you,,what colours on drone,we know remote red and green.......OK I read ist post again and says it used,,did you see it go,,,

Yea someone may have sold me their issues. I could probably go through ebay to return it since it was advertised as working condition, but at this point at I would rather just fix the issue if possible.

drone lights are 2 solid red, 2 yellow flashing (cant remember if fast or slow, will have to power up in a bit to check)

Its strange because when I first got the controller and linked it to the AC, the light was solid green. Then once I realized I couldn’t connect to the app, I reset the controller via C1 + C2 + record button, then clicked the camera wheel once I heard the beep. This turned the light to blinking blue, so I linked the RC and AC again. This is when the alternating red/green began.
 
Front always solid red unless turn off,what colour gimble light,is link light on drone red or green,,,green if linked red or orange if not,take note of these colours these say what drone is doing
Screenshot_20180917-163417.jpg
 
Front always solid red unless turn off,what colour gimble light,is link light on drone red or green,,,green if linked red or orange if not,take note of these colours these say what drone is doingView attachment 103572

I will check on the status lights next time I power up.

In the meantime, I booted the board up again and it stopped at "settime failed" 2 times in a row. On the third boot, it went back to normal and finished the boot process. This is strange, unsure if this is part of my issue.

See attached log of settime failed boot.
 

Attachments

  • putty3.txt
    11.2 KB · Views: 176
I will check on the status lights next time I power up.

In the meantime, I booted the board up again and it stopped at "settime failed" 2 times in a row. On the third boot, it went back to normal and finished the boot process. This is strange, unsure if this is part of my issue.

See attached log of settime failed boot.
Yes I download early but my flash device wont read it,useing tab A 10/1 ,3rd time lucky they say,yes could be doing something,,@quaddamage got software to read these files or hopefully someone can fill us in,,,I know this tricky one cause these clever folk here and they not getting involved, we can only try try stuff,,without any spares to try it gets hard,,I'm off searching again,this is killing me,try find i tune back in soon
 
OK this light chart says different again,,did you try usb,any difference,,by this chart it say HD downlink disrupted
Screenshot_20180917-181317.jpg
 
it appears that it is booting correctly

Look at this:
Code:
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 ...

The board clearly boots to recovery kernel.

I booted the board up again and it stopped at "settime failed" 2 times in a row. On the third boot, it went back to normal and finished the boot process. This is strange, unsure if this is part of my issue.

Searching google, I noticed many people have "settime failed" in their log and the board continues to boot, so the issue is not direct result of that message. But it looks troubling. Note that it took 10 seconds to go to next message in the "good" boot - did you waited long enough?
 
Look at this:
Code:
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 ...

The board clearly boots to recovery kernel.



Searching google, I noticed many people have "settime failed" in their log and the board continues to boot, so the issue is not direct result of that message. But it looks troubling. Note that it took 10 seconds to go to next message in the "good" boot - did you waited long enough?

Ok glad you looked over the log for me. So do you think I should flash the primary kernel?

Or what may be the next logical step?
 

Thanks. Can you point me to the correct place or explain how to get the primary kernel, uImage?

I understand it can be extracted from the firmware but Im u sure how to do this and having trouble finding the wiki about it.

Also for the gl300a, can I flash through the usb port already on the board? If so, do I still need to power the board through the 5v service pad?
 
Thanks. Can you point me to the correct place or explain how to get the primary kernel, uImage?

I understand it can be extracted from the firmware but Im u sure how to do this and having trouble finding the wiki about it.

Also for the gl300a, can I flash through the usb port already on the board? If so, do I still need to power the board through the 5v service pad?


FINALLY!!! I can connect to the app. I flashed the primary kernel and I can now connect to the dji go app. Thanks again @quaddamage !!
 
  • Like
Reactions: quaddamage
Quick question though, the app says my RC firmware is mismatched and needs upgrading. The app is telling me to go to www.dji.com/product/inspire-1/download/

I am confused because this is for a Phantom 3 Pro.

Can I just put the usb stick in the controller with the P3P firmware? Or am I actually supposed to install inspire firmware?

The AC has the most current 1.11.20 firmware installed. (My replacement gimbal top board came in today as well, so I was able to load firmware)
 
Quick question though, the app says my RC firmware is mismatched and needs upgrading. The app is telling me to go to www.dji.com/product/inspire-1/download/

I am confused because this is for a Phantom 3 Pro.

Can I just put the usb stick in the controller with the P3P firmware? Or am I actually supposed to install inspire firmware?

The AC has the most current 1.11.20 firmware installed. (My replacement gimbal top board came in today as well, so I was able to load firmware)

Never-mind, I figured out the issue. My RC firmware was pretty old.....it wanted me to upgrade to 1.3.2 via usb stick. Once I did that, I was able to upgrade to the newest firmware via the app.

Only thing left is a compass error which I think can be resolved by calibrating it. I will do that tomorrow and see what the outcome is.

Also, I replaced one of the motors......can someone tell me what kind of glue I can use on the wires?

Now I just need to get some props so I can put it in the air!
 

Members online

No members online now.

Forum statistics

Threads
143,120
Messages
1,467,765
Members
105,007
Latest member
thedrinklabsus