I have successfully built a custom desktop image and file system based
off of the pixhawk recipe. I have been running it successfully on the overo
for several weeks but today I powered on the overo and tobi with a caspa fs
camera attached and neither the com or tobi led lights lit up and the com
did not boot at all as seen from the console usb kermit connection. I had
powered the board up in the same configuration several times before but
today it just did not work. Without the camera attached the leds turned on
but the com still would not boot at all. I attached a firestorm to the tobi
with the same sd card (without caspa camera attached) and the com booted
I am thinking that the airstorm got fried when I powered it on with the
caspa attached. I have tried booting the airstorm with several sd cards
that worked perfectly with it before and I tried booting with no card and no
camera with not even a single message from the console.
Does anyone know what I can do to get the airstorm to boot? Or does anyone
know how I could tell if the com is fried?
Thanks a bunch.
View this message in context: http://gumstix.8.n6.nabble.com/Problems-Booting-With-Overo-AirStorm-And-Tobi-Board-tp4680135p4680135.html
Sent from the Gumstix mailing list archive at Nabble.com.
While using ssh with my FireSTORM I recently started getting spurious errors of various kinds that result in dropped ssh sessions. These include "corrupted packet," "failed write," and some error related to the MAC address. The all seem to have to do with sending data to the FireSTORM (like typing in a shell), not receiving data.
After getting the error, another ssh session can be started right up. But the errors happen every 10-15 seconds, making ssh unusable.
It's related to the FireSTORM COM because I can swap in a Fire with the same uSD, and I don't get the error.
Get latest updates about Open Source Projects, Conferences and News.