On Tue, 2004-07-27 at 00:30, John Carmack wrote: > Are you absolutely sure the flight computer is initializing the serial port > correctly? Have you had it talking to a laptop over a null modem > cable?
Yes. > Are you sure it isn't something silly like having an unkeyed 10 pin > ribbon connector on upside down to the CPU board? Make sure you can cat > junk to /dev/ttyS0 and see it on a laptop hyperterminal session. No problem in serial output to the laptop. I've even ran the imutest code with the serial line connected via null modem to my laptop with a terminal attached, it sends the right stuff at the right time. My first thought after making sure the code works for other machines was that some pinout wasn't right somewhere - but we are using an I/O breakout with DB9 connectors on the flight computer, the I/O breakout board came with the PC/104 development kit. Also we rechecked the connectors and such, everything is as it should be. > Every sensor and actuator I use has built in test-on-port functionality in > the flight computer executable that is separate from the normal flightcode, > which is very useful when you are reconfiguring your flight systems. Just > a few hours ago, I was using the -testIgnition function to work on a balky > ignition system that we changed around, for instance. I'm doing something similar, just compiled into different executables: ~/bin/motortest runs up the motors. ~/bin/imutest initializes the imu, then reads and prints it to stdout. ~/bin/fctp-fc tests the network stack ~/bin/gizmo is the actual flight code That's all we have to test right now. All the tests are actually wrappers around functions used in the actual flight code. > > Out of curiosity, do you treat your flight computer like a traditional > embedded system that you cross compile for, or do you have a full > development environment on it? It is an embedded system, except that the build server doesn't cross compile for it but is actually very similar environment. Both are built from the same Linux distribution and version, just a very minimal install vs. full development install. > I really like doing my builds and debugging > directly on the flight computer, but I don't use a linux laptop like some > of the ERPS folks do. I like the 0 apparent time to 'make all; scp * gizmo:' from the build server. hmmm... I'm not where I can test it out. I don't see any real difference between your code and what I'm doing. I'll try it tonight. Thanks, Dave -- David Masten <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
_______________________________________________ ERPS-list mailing list [EMAIL PROTECTED] http://lists.erps.org/mailman/listinfo/erps-list
