On Tue, Apr 07, 2009 at 05:35:28PM -0400, Gene Heskett wrote: > [root@coyote test]# ls -l /dev/rfcomm* > crw------- 1 root root 216, 0 2009-04-07 17:25 /dev/rfcomm0 > > [root@coyote test]# minicom > minicom: cannot open /dev/rfcomm0: No such file or directory > > [root@coyote test]# ls -l /dev/rfcomm* > crw------- 1 root root 216, 0 2009-04-07 17:25 /dev/rfcomm0 Hmmm... Maybe try simply 'cat /dev/rfcomm0'? Or use 'screen' or 'cu'. While the 'cat' process is running, you can adjust terminal settings from another shell using 'stty', e.g. 'stty </dev/rfcomm0 9600 -echo'. I am guessing when you try 'cat /dev/rfcomm0' it will exit immediately, either with an EOF (which will print nothing) or an I/O error, or even with 'Host is down'. > If it doesn't exist, why can I see it in the /dev directory? Because minicom is to testing raw serial connections what Roman numerals are to the square root of Pi. :-P > I didn't even have to pair it to make it work late friday evening, and for > several hours last saturday. But I thought I'd change the default PIN and it > hasn't worked since. It's possible to turn off security on the eb101 device (says the manual). Maybe changing the default PIN turns it on? > >Maybe try 'l2ping' to verify the remote device is still on? > Variations on the theme: > [root@coyote test]# l2ping 00:0c:84:00:86:F8 > Can't connect: Host is down > [root@coyote test]# l2ping -i hci0 00:0c:84:00:86:F8 > Can't connect: Host is down > [root@coyote test]# l2ping -i /dev/rfcomm0 00:0c:84:00:86:F8 > Can't connect: Host is down > > So maybe there is a clue here? Could be that the USB dongle has hung on the Linux side, or the eb101 device has shut itself down or been shut down by the Coco. It would really help to have the eb101's status information.
Attachment:
signature.asc
Description: Digital signature
