Connecting to Beablebone

[Ganbold Tsagaankhuu]

On Fri, May 10, 2013 at 9:47 AM, hiren panchasara <
hiren.panchasara at gmail.com> wrote:

> Hi list,
>
> I've built img using crotchet scripts (great work!) a few days back
> from HEAD and followed instructions at
> https://wiki.freebsd.org/FreeBSD/arm/BeagleBoneBlack.
>
> Now,
>
> After powering up I connected the debug USB cable from BB to my laptop
> (running HEAD).
>
> dmesg shows:
>
> ugen0.5: <Texas Instruments> at usbus0
> umodem0: <Texas Instruments AM335x USB, class 2/0, rev 2.00/0.00, addr
> 5> on usbus0
> umodem0: data interface 1, has no CM over data, has no break
>
> /dev shows following new entries:
>
> crw-rw----  1 uucp    dialer     0x97 May  9 18:13 cuaU0
> crw-rw----  1 uucp    dialer     0x98 May  9 18:13 cuaU0.init
> crw-rw----  1 uucp    dialer     0x99 May  9 18:13 cuaU0.lock
> crw-------  1 root    wheel      0x94 May  9 18:13 ttyU0
> crw-------  1 root    wheel      0x95 May  9 18:13 ttyU0.init
> crw-------  1 root    wheel      0x96 May  9 18:13 ttyU0.lock
> lrwxr-xr-x  1 root    wheel        9B May  9 18:13 ugen0.5 -> usb/0.5.0
> crw-rw-rw-  1 root    wheel       0xe May  9 18:11 null
> crw-------  1 root    wheel      0x1b May  9 18:10 bpf
>
> Trying to connecting to it:
>
> % sudo cu -l /dev/cuaU0
> Connected
>


No need to set speed?

Ganbold



>
> Its stays stuck there without doing anything. Same with ttyU0. Is that
> not how you connect to this thing?
>
> In my quest of understanding /dev entries, I found: ttyU0 is actual
> tty device and cuaU0 is a callback device?
>
> Also,  I am not getting those blue usb lights turned on. Not sure if
> that means something.
>
> I am sure I must be doing something really silly. Any help would be great.
>
> cheers,
> Hiren
> _______________________________________________
> freebsd-arm at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org"
>