Just thought I would mention, I am making more progress :)
Using the debian release is nice as like when compiling on the RPI, I could
install PCM and espeak, by simply doing apt-get install and the packages
were installed. On Angstrom I had to find sources build and install. No
big deal but it is nice.
Next up is to start connecting it up to hardware. XBee will be easy,
connect to TTL usart like before, as it is 3.3v. But not sure which way I
will go to talk to SSC-32. Could USB to serial adapter or could connect to
another USART through level shifter. The SSC-32 is a 5v ATmega based
board.
Another thing I want to investigate more is in my code, I like to reference
devices by a name such as: /dev/ttyXBee instead of by some actual hardware
name. When it is /dev/ttyUSBn it also had the complication that if you
rearrange things and/or add devices your device may change names. ttyUSB0
today may be ttyUSB1 tomorrow... So I used UDEV rules to do the mapping.
Something like:
SUBSYSTEM=="tty", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001",
ATTRS{serial}=="A800fclo", SYMLINK+="ttyXBEE"
But at the time was not sure of the best way to simply map ttyO1 to
ttyXBee. When I tried it the last time was not sure, so I simply added a
line to my .profile file that did something like: ln -s /dev/ttyO1
/dev/ttyXBee
But my gut tells me there is a cleaner way. So will probably play a little
with this, before I simply fall back to doing what I did before.
Again having fun
Kurt
P.S - the Wifi has stopped twice now. Could be related that I am powering
board through USB (1 amp wall wart) instead of DC power input. Will
change soon
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
