I have a little project building an UAV autopilot prototype using an overo
and an ardupilot mega 2. I have a few random bits of description of what
I'm up to here if anyone cares (with a picture!) :-)
Running with the Open Embedded system (self compiled from scratch from
gumstix.org direction a while back) and running the 2.6.36 kernel,
everything works. I'm communicating between the APM2 and the Overo
/dev/ttyS0 @ 500,000 baud and talking in both direction. Everything is
Today I tried building up an SD card image based on the Sakoman Gnome-r13
distribution. This is the first time I've tried updated images in a long
time -- I'm interested in keeping up with the latest and greatest I guess.
So I downloaded the little sakoman mksdcard.sh script, ran it and
everything works as advertised and I was quickly up and running.
However, my code isn't talking to the APM2 on this new system. I did
switch to using /dev/ttyO0. I can run minicom on /dev/ttyO0 and see the
APM2 transmitting @ 500,000 baud, but the APM2 cannot see anything the
Overo sends. This is running the Sakoman stuff, from today.
As a test I went back to my 2.6.36 openembedded system on a different SD
card, and that still happily runs and jabbers back and forth with the APM2
just fine -- so as far as I know, my hardware is good, the APM2 is good,
the TTL level translation is good, and it all works as expected on the
openembedded 2.6.36 kernel version system.
But going back to the sakoman-gnome-r13 system, the two sides can't talk.
Any ideas? Could this be a case where 500,000 baud isn't really, but
being set to something similar (some clock rate / some constant
multiplier), but not similar enough for the APM2 to understand?
Can any one help? I'd love to move forward with my root/kernel and not be
stuck in the 2 year old past forever.
http://www.atiak.com - http://aem.umn.edu/~uav/http://www.flightgear.org - http://gallinazo.flightgear.org
Get latest updates about Open Source Projects, Conferences and News.