New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

serial console on drone outputs debug information #32

Closed
maxogden opened this Issue Dec 2, 2012 · 6 comments

Comments

Projects
None yet
5 participants
@maxogden

maxogden commented Dec 2, 2012

this isn't the correct repo for this question but I don't know where else to put it :)

the Tx serial port on the motherboard of the drone is intended as a debug console. so when you connect to it via serial it will spew out a bunch of data. reading data into the drone over serial works just fine but I can't figure out how to disable the drones console debugging.

anyone have any ideas? yesterday I mounted a robot arm to a drone but was unable to teach the drone how to open and close the arm programmatically because of this limitation

@csanz

This comment has been minimized.

Contributor

csanz commented Dec 3, 2012

So cool

Sent from my ifon

On Dec 2, 2012, at 3:23 PM, Max Ogden notifications@github.com wrote:

this isn't the correct repo for this question but I don't know where else to put it :)

the Tx serial port on the motherboard of the drone is intended as a debug console. so when you connect to it via serial it will spew out a bunch of data. reading data into the drone over serial works just fine but I can't figure out how to disable the drones console debugging.

anyone have any ideas? yesterday I mounted a robot arm to a drone but was unable to teach the drone how to open and close the arm programmatically because of this limitation


Reply to this email directly or view it on GitHub.

@bkw

This comment has been minimized.

Collaborator

bkw commented Dec 3, 2012

You may be out of luck with the current /bin/program.elf. It seems to be hardwired to use /dev/ttyO1, which must be the serial port you're seeing. Maybe changing the assignment of device numbers before the program is started is a way to hack around it, but I haven't tried that yet.
There is /dev/ttyO2 and /dev/ttyO3 as well, which are assigned shells by init. We should be able to change that, but you only have access to one console on the motherboard, right?

BTW: While looking through program.elf with strings, I found some undocumented AT commands as well as the commandline switch -webstats, which opens up a webserver on port 80 that prints out statistics in html. Nothing to revealing there, but fun nontheless ;-)

@maxogden

This comment has been minimized.

maxogden commented Dec 3, 2012

whoa cool! nice sleuthing. /dev/ttyO3 is the serial port i'm using and
works for reading data from the Rx pin on the motherboard. there is only 1
set of tx/rx pins though. not sure what ttyO1 and O2 are linked to.

if you check out /proc/cmdline it shows that ttyO3 is the serial console
and shows the initial baud rate.

On Sun, Dec 2, 2012 at 10:35 PM, Bernhard Weißhuhn <notifications@github.com

wrote:

You may be out of luck with the current /bin/program.elf. It seems to be
hardwired to use /dev/ttyO1, which must be the serial port you're seeing.
Maybe changing the assignment of device numbers before the program is
started is a way to hack around it, but I haven't tried that yet.
There is /dev/ttyO2 and /dev/ttyO3 as well, which are assigned shells by
init. We should be able to change that, but you only have access to one
console on the motherboard, right?

BTW: While looking through program.elf with strings, I found some
undocumented AT commands as well as the commandline switch -webstats, which
opens up a webserver on port 80 that prints out statistics in html. Nothing
to revealing there, but fun nontheless ;-)


Reply to this email directly or view it on GitHubhttps://github.com//issues/32#issuecomment-10942914.

@bkw

This comment has been minimized.

Collaborator

bkw commented Dec 3, 2012

Well, in that case, commenting the ttyO3 line in inittab and restarting init should do it. Can't really try it now, AFD (away from drone). Good luck!

@felixge

This comment has been minimized.

Owner

felixge commented Dec 5, 2012

Also, in case you were wondering, /dev/ttyO0 lets you control the rotors and leds:

https://github.com/felixge/go-ardrone-firmware/blob/master/main.go

; )

@andrew

This comment has been minimized.

Collaborator

andrew commented Jun 9, 2014

Closing this as it's not had any activity in over a year, please re-open if it's still affecting you.

@andrew andrew closed this Jun 9, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment