Strange phenomena

Status
Not open for further replies.
arikb

arikb

New member
Hello,

I am a Teensy newbie. I got one today and plugged it in, after adding the udev rules (Linux Ubuntu 12.4) Nothing happens. Tried disconnecting and connecting, nothing happens.

Tried pushing the button - the OS detected it fine. Downloaded the program and uploded blink, blink slow, blink fast, blink at90usb1286.... nothing.

So I grabbed a multimeter and connected it to D6. Yep, goes up to 5v and down as expected. The LED must be disconnected. I left it connected while I started looking for the warrenty info... and then as it sits here next to me - the LED starts blinking. I didn't even touch it. I tried uploading the fast blink and the blinky and decoded some of the morse code. All works now.

Looking closely it looks like the solder is flowed correctly and there's nothing loose, I can't mechanically reproduce it.

Very strange.

-- Arik
 
In a secondary terminal (xterm, etc.) do:

Code: 
sudo tail -f /var/log/messages

This should give you an indication of whether the device is connecting or not.

For example, this is the log message on my Fedoria 14 system:

Code: 
Jan  9 10:10:21 wogglebug kernel: [1066586.000097] usb 3-2: new full speed USB device using uhci_hcd and address 19
Jan  9 10:10:22 wogglebug kernel: [1066586.153101] usb 3-2: New USB device found, idVendor=16c0, idProduct=0483
Jan  9 10:10:22 wogglebug kernel: [1066586.153106] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan  9 10:10:22 wogglebug kernel: [1066586.153132] usb 3-2: Product: USB Serial
Jan  9 10:10:22 wogglebug kernel: [1066586.153135] usb 3-2: Manufacturer: Teensyduino
Jan  9 10:10:22 wogglebug kernel: [1066586.153138] usb 3-2: SerialNumber: 12345
Jan  9 10:10:22 wogglebug kernel: [1066586.156769] cdc_acm 3-2:1.0: This device cannot do calls on its own. It is not a modem.
Jan  9 10:10:22 wogglebug kernel: [1066586.156863] cdc_acm 3-2:1.0: ttyACM0: USB ACM device
Jan  9 10:10:22 wogglebug mtp-probe: checking bus 3, device 19: "/sys/devices/pci0000:00/0000:00:1d.1/usb3/3-2"
Jan  9 10:10:22 wogglebug mtp-probe: bus: 3, device: 19 was not an MTP device

At this point, I run the Arduino program, and compile/upload my program:

Code: 
Jan  9 10:10:23 wogglebug kernel: [1066587.955071] usb 3-2: USB disconnect, address 19
Jan  9 10:10:24 wogglebug kernel: [1066588.698328] usb 3-2: new full speed USB device using uhci_hcd and address 20
Jan  9 10:10:24 wogglebug kernel: [1066588.831113] usb 3-2: New USB device found, idVendor=16c0, idProduct=0478
Jan  9 10:10:24 wogglebug kernel: [1066588.831118] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jan  9 10:10:24 wogglebug kernel: [1066588.837617] generic-usb 0003:16C0:0478.0009: hidraw1: USB HID v1.11 Device [HID 16c0:0478] on usb-0000:00:1d.1-2/input0
Jan  9 10:10:24 wogglebug mtp-probe: checking bus 3, device 20: "/sys/devices/pci0000:00/0000:00:1d.1/usb3/3-2"
Jan  9 10:10:24 wogglebug mtp-probe: bus: 3, device: 20 was not an MTP device
Jan  9 10:10:25 wogglebug kernel: [1066589.762330] usb 3-2: USB disconnect, address 20
Jan  9 10:10:25 wogglebug kernel: [1066589.969091] usb 3-2: new full speed USB device using uhci_hcd and address 21
Jan  9 10:10:26 wogglebug kernel: [1066590.126130] usb 3-2: New USB device found, idVendor=16c0, idProduct=0483
Jan  9 10:10:26 wogglebug kernel: [1066590.126157] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan  9 10:10:26 wogglebug kernel: [1066590.126162] usb 3-2: Product: USB Serial
Jan  9 10:10:26 wogglebug kernel: [1066590.126164] usb 3-2: Manufacturer: Teensyduino
Jan  9 10:10:26 wogglebug kernel: [1066590.126189] usb 3-2: SerialNumber: 12345
Jan  9 10:10:26 wogglebug kernel: [1066590.129363] cdc_acm 3-2:1.0: This device cannot do calls on its own. It is not a modem.
Jan  9 10:10:26 wogglebug kernel: [1066590.129483] cdc_acm 3-2:1.0: ttyACM0: USB ACM device
Jan  9 10:10:26 wogglebug mtp-probe: checking bus 3, device 21: "/sys/devices/pci0000:00/0000:00:1d.1/usb3/3-2"
Jan  9 10:10:26 wogglebug mtp-probe: bus: 3, device: 21 was not an MTP device

If you just loaded the udev rules, you may need to restart the udev process (simplest to reboot, there may be a Ubuntu specific command to restart it).
:cool:

I should mention that it may your cable is wonky. I have a cable that has both micro and mini USB connections on it (which isn't covered by the USB spec), and at times it will not connect the device.
 
Last edited:
Hi Michael,

Thank you for your response.

My problem was not programming the device. It got programmed nicely.

My problem was that the on-board LED wasn't blinking, even when the programming code seemed to function just fine. And then, just leaving it aside, it started to blink.

-- Arik
 
Hi Paul,

When I plug the board - it doesn't output anything to the logs. Also lsusb shows nothing.

When I press the button, I see this on the kernel log (dmesg):
Code: 
[384360.355938] usb 3-2: new full-speed USB device number 30 using xhci_hcd
[384360.374258] generic-usb 0003:16C0:0478.001F: hidraw2: USB HID v1.11 Device [HID 16c0:0478] on usb-0000:06:00.0-2/input0

and lsusb shows:
Code: 
Bus 003 Device 031: ID 16c0:0478 VOTI Teensy Halfkay Bootloader

and of course when disconnected:
Code: 
[384387.748551] usb 3-2: USB disconnect, device number 30

This is normal behaviour with only the blink*.hex programs loaded, correct?

Also, this is the result of the loader:

Code: 
arikb@kuroii:~/teensy/teensy_loader_cli$ ./teensy_loader_cli -mmcu=at90usb1286 -w blink_fast.hex -v
Teensy Loader, Command Line, Version 2.0
Read "blink_fast.hex": 54 bytes, 0.0% usage
Found HalfKay Bootloader
Programming.
Booting
arikb@kuroii:~/teensy/teensy_loader_cli$

-- Arik
 
Last edited:
Yes, that's normal with blink_slow.hex and blink_fast.hex. Those examples only blink the LED. They do not turn the USB on at all, so it's as if there is no USB device plugged in, as far as your computer can tell.
 
So, in all respects this is functioning normally now; as it did before - with the exception of the LED wasn't functioning.

My local hack-space is buying a reflow oven and I thought about just throwing it in for a round... the board may have read my mind about the expected torture it was to undergo and decided that the LED is functioning after all ;)

Thanks for your help!

-- Arik
 
Status
Not open for further replies.
Back
Top