All, I have a small ARM board that I am working with: http://processors.wiki.ti.com/index.php/LAUNCHXL2-RM46 I can build for the board using gcc-arm-none-eabi and flash the firmware with the TI UniFlash software. However I cannot figure out how to connect a serial device to it. The manual says I should be able to: Configure Baud Rate: 19200, Data Bits: 8, Stop Bits: 2 and Parity: None http://processors.wiki.ti.com/index.php/LAUNCHXL2_RM46:_Project_1 When connected there are two /dev/tty devices created: crw-rw-rw- 1 root dialout 166, 0 Oct 12 21:55 /dev/ttyACM0 crw-rw-rw- 1 root dialout 166, 1 Oct 12 21:55 /dev/ttyACM1 These are in some manner related to: /sys/devices/pci0000\:00/0000\:00\:1c.7/0000\:26\:00.0/usb1/1-1 and the character device /dev/char/189:9 I have tried minicom through /dev/ttyACM0, without success. I can find the device and query it through: # udevadm test /sys/devices/pci0000\:00/0000\:00\:1c.7/0000\:26\:00.0/usb1/1-1 calling: test version 228 This program is for debugging only, it does not run any program specified by a RUN key. It may show incorrect results, because some values may be different, or not available at a simulation run. === trie on-disk === tool version: 228 file size: 7007575 bytes header size 80 bytes strings 1743863 bytes nodes 5263632 bytes Load module index <snip> starting '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1c.7/0000:26:00.0/usb1/1-1 1 10' '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1c.7/0000:26:00.0/usb1/1-1 1 10'(out) '0' Process '/usr/lib/udev/mtp-probe /sys/devices/pci0000:00/0000:00:1c.7/0000:26:00.0/usb1/1-1 1 10' succeeded. MODE 0666 /etc/udev/rules.d/71-ti-permissions.rules:10 handling device node '/dev/bus/usb/001/010', devnum=c189:9, mode=0666, uid=0, gid=0 preserve permissions /dev/bus/usb/001/010, 020666, uid=0, gid=0 preserve already existing symlink '/dev/char/189:9' to '../bus/usb/001/010' created db file '/run/udev/data/c189:9' for '/devices/pci0000:00/0000:00:1c.7/0000:26:00.0/usb1/1-1' ACTION=add BUSNUM=001 DEVNAME=/dev/bus/usb/001/010 DEVNUM=010 DEVPATH=/devices/pci0000:00/0000:00:1c.7/0000:26:00.0/usb1/1-1 DEVTYPE=usb_device DRIVER=usb ID_BUS=usb ID_MODEL=XDS110__03.00.00.02__Embed_with_CMSIS-DAP ID_MODEL_ENC=XDS110\x20\x2803.00.00.02\x29\x20Embed\x20with\x20CMSIS-DAP ID_MODEL_ID=bef3 ID_REVISION=0100 ID_SERIAL=Texas_Instruments_XDS110__03.00.00.02__Embed_with_CMSIS-DAP_HLR46000 ID_SERIAL_SHORT=HLR46000 ID_USB_INTERFACES=:020201:0a0000:ff0000:030000: ID_VENDOR=Texas_Instruments ID_VENDOR_ENC=Texas\x20Instruments ID_VENDOR_FROM_DATABASE=Texas Instruments, Inc. ID_VENDOR_ID=0451 MAJOR=189 MINOR=9 PRODUCT=451/bef3/100 SUBSYSTEM=usb TYPE=239/2/1 USEC_INITIALIZED=120561513447 run: '/usr/lib/virtualbox/VBoxCreateUSBNode.sh 189 9 ef' Unload module index Unloaded link configuration context. This is the correct udev rule for the device, but that is where I am stuck. What I need to do is get a serial console open to it so that when I load an executable that reads/writes to stdin/stdout I can see the output and provide the input. (blinking diodes are the board are nice, but worthless for providing user authentication through) Connecting a serial console seems like a simple process, but I must be missing something stupid simple about it. Minicom can be configured for either /dev/ttyACM0 or /dev/ttyACM1 (and N82 19200) but there is nothing ever output on either (even after loading a program that generates output to stdout) Yes, the flash goes fine and I can load different executables to make the diodes respond in varying ways -- so the fact that the code is loaded and running correctly if verified, but how do I interface with the serial terminal on this thing? Anybody been down this road before? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org