Hi all, I'm an FreeBSD user for many years (since 1.x) and decided to try DragonFlyBSD on a Latop that I need in the futire to do some mobile microcontroller development work.
I had an LG R710 Notebook laying around here, which has 2 disks, an Core2Duo CPU and 4 Gig RAM...should do the work. I've got the 5.0.2 live CD and installed from there to the 2nd disk, installed X and mate..so far so good. thre where several "glitches" that preventing booting after detecting acpi_ec ..but not every time. -Mailed to Matt and he suggeseted toat least try master instead of release. Hm..don't even knew what this means..but I've pulled the sources from git, build a world and a kernel rebooted and now have a 5.1 Development system..not exactly what I wanted, but at least the acpi Problems seemed to be gone for now. There are (still) those ugly messages every second (or so) on the console, related tothe cdrom drive if it is empty..but this is for later. My biggest problem at the moment is, that I can't get my MSP-FET430UIF JTAG Interface for MSP430 CPUs to get to work. Normally I've used mspdebug on FreeBSD like this: $ make program /usr/local/bin/mspdebug -v 3300 tilib "prog main.elf" MSPDebug version 0.23 - debugging tool for MSP430 MCUs Copyright (C) 2009-2015 Daniel Beer <[email protected]> This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Chip info database from MSP430.dll v3.3.1.4 Copyright (C) 2013 TI, Inc. Using new (SLAC460L+) API MSP430_GetNumberOfUsbIfs MSP430_GetNameOfUsbIf Found FET: mspfet0010 MSP430_Initialize: mspfet0010 Firmware version is 31001600 MSP430_VCC: 3300 mV MSP430_OpenDevice MSP430_GetFoundDevice Device: MSP430F2619 (id = 0x0074) 8 breakpoints available MSP430_EEM_Init Erasing... Programming... Writing 2 bytes at fffe [section: __reset_vector]... Writing 12 bytes at 2100 [section: .rodata2]... Writing 4 bytes at 210c [section: .data]... Writing 102 bytes at 2110 [section: .lowtext]... Writing 460 bytes at 2176 [section: .text]... Done, 580 bytes total MSP430_Run MSP430_Close $ That "tilib" is using libusb to find the interface $ usbconfig ugen0.1: <Intel UHCI root HUB> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen1.1: <Intel UHCI root HUB> at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen2.1: <Intel UHCI root HUB> at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen3.1: <Intel EHCI root HUB> at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen4.1: <Intel UHCI root HUB> at usbus4, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen5.1: <Intel UHCI root HUB> at usbus5, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen6.1: <Intel UHCI root HUB> at usbus6, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen7.1: <Intel EHCI root HUB> at usbus7, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen0.3: <C-Media Electronics Inc. USB PnP Sound Device> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) ugen7.2: <vendor 0x0424 product 0x2514> at usbus7, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (2mA) ugen0.2: <Texas Instruments Texas Instruments MSP430-JTAG> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) $ which is on ugen0.2 here (on FreeBSD). Tried the same on Dragonfly with mspdebug from pkg install: /usr/local/bin/mspdebug -v 3300 tilib "prog main.elf" MSPDebug version 0.23 - debugging tool for MSP430 MCUs Copyright (C) 2009-2015 Daniel Beer <[email protected]> This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Chip info database from MSP430.dll v3.3.1.4 Copyright (C) 2013 TI, Inc. Using new (SLAC460L+) API MSP430_GetNumberOfUsbIfs No unused FET found. *** Error code 255 Stop. make: stopped in /home/holm/src/MICROS/TI/1611 $ usbconfig ugen0.1: <Intel UHCI root HUB> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen1.1: <Intel UHCI root HUB> at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen2.1: <Intel UHCI root HUB> at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen3.1: <Intel EHCI root HUB> at usbus3, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen4.1: <Intel UHCI root HUB> at usbus4, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen5.1: <Intel UHCI root HUB> at usbus5, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen6.1: <Intel UHCI root HUB> at usbus6, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA) ugen7.1: <Intel EHCI root HUB> at usbus7, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA) ugen7.2: <LG Innotek LG Webcam> at usbus7, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (168mA) ugen2.2: <Broadcom Corp BT-253> at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (0mA) ugen4.2: <Texas Instruments Texas Instruments MSP430> at usbus4, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) (gnerated an /etc/devfs.conf to get permission for the /dev/ugen devices) In a ktrace I can see that mspdebug can successfully open the device, so that doesn't seem to be a permission problem. I an see that ucom/umodem attaches the interface and provides serial lines, what isn't the case on FreeBSD so far as I know, so may be that's the cause for that "No unused FET found." above. I've tried mspdebug uif /dev/ttyU0 (ttyiU0,ttylU0) also, but always get the message: $ mspdebug uif /dev/ttyU0 MSPDebug version 0.23 - debugging tool for MSP430 MCUs Copyright (C) 2009-2015 Daniel Beer <[email protected]> This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Chip info database from MSP430.dll v3.3.1.4 Copyright (C) 2013 TI, Inc. usbutil: unable to find a device matching 0451:f430 ...not that satisfying at all. (BTW: what are that ttyi ttyl devices at all? the ucom(4) manual mentiones cua and tty ..which I know of, but what exactly do the tty* device here on Dragonfly?) mspdebug sees the device: $ mspdebug --usb-list Devices on bus 000: 000:000 2047:0010 FET430UIF (V3 firmware) [serial: 57FF54F75EC51E10] 000:000 0b05:1751 [serial: 002243C4B61A] 000:000 1d74:0003 [serial: ] 000:000 0000:0000 [serial: ] 000:000 0000:0000 [serial: ] 000:000 0000:0000 [serial: ] 000:000 0000:0000 [serial: ] 000:000 0000:0000 [serial: ] 000:000 0000:0000 [serial: ] 000:000 0000:0000 [serial: ] 000:000 0000:0000 [serial: ] $ But what the heck are that numbers? I can specify an Bus:Device mit -U .. (seems to 4:2) $ mspdebug tilib -U 4:2 MSPDebug version 0.23 - debugging tool for MSP430 MCUs Copyright (C) 2009-2015 Daniel Beer <[email protected]> This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Chip info database from MSP430.dll v3.3.1.4 Copyright (C) 2013 TI, Inc. Using new (SLAC460L+) API MSP430_GetNumberOfUsbIfs No unused FET found. $ Hmm.... I run out of ideas now. How can I prevent ucom or umodem from attaching a specified device? Has someone ever tried to use that mspdebug thing on Dragonfly with an USB FET430? Regards from germany, Holm -- Technik Service u. Handel Tiffe, www.tsht.de, Holm Tiffe, Freiberger Straße 42, 09600 Oberschöna, USt-Id: DE253710583 [email protected] Fax +49 3731 74200 Tel +49 3731 74222 Mobil: 0172 8790 741
