Go Down

Topic: Loop Back Test - Sticky? (Read 35 times) previous topic - next topic

Coding Badly


@retrolefty:  Thanks.  What does Linux do to acknowledge a device insertion?  MacOS?

retrolefty



@retrolefty:  Thanks.  What does Linux do to acknowledge a device insertion?  MacOS?



Don't have a clue, but I'm sure somone around here can tell us.  ;)

Lefty

madworm

#7
Jul 25, 2011, 11:27 pm Last Edit: Aug 04, 2011, 05:33 pm by madworm Reason: 1
Re: linux

Unless it is a mass storage device (camera, sd-card, disk...) usually nothing at all. I can't speak for ubuntu though. Of course it will be logged to system log, but the common user usually doesn't care much about that.

And simple things like serial adapters usually just work out of the box anyway ;-)

An FTDI adapter will create something like this in the syslog:

Code: [Select]

07/25/11 11:25:08 PM linuxbox kernel [25248.700042] usb 2-4: new full speed USB device number 3 using ohci_hcd
07/25/11 11:25:08 PM linuxbox kernel [25248.928051] usb 2-4: New USB device found, idVendor=0403, idProduct=6001
07/25/11 11:25:08 PM linuxbox kernel [25248.928062] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
07/25/11 11:25:08 PM linuxbox kernel [25248.928069] usb 2-4: Product: FT232R USB UART
07/25/11 11:25:08 PM linuxbox kernel [25248.928075] usb 2-4: Manufacturer: FTDI
07/25/11 11:25:08 PM linuxbox kernel [25248.928079] usb 2-4: SerialNumber: A6007nZC
07/25/11 11:25:08 PM linuxbox mtp-probe checking bus 2, device 3: "/sys/devices/pci0000:00/0000:00:02.0/usb2/2-4"
07/25/11 11:25:08 PM linuxbox mtp-probe bus: 2, device: 3 was not an MTP device
07/25/11 11:25:09 PM linuxbox kernel [25250.009207] usbcore: registered new interface driver usbserial
07/25/11 11:25:09 PM linuxbox kernel [25250.009240] USB Serial support registered for generic
07/25/11 11:25:09 PM linuxbox kernel [25250.009298] usbcore: registered new interface driver usbserial_generic
07/25/11 11:25:09 PM linuxbox kernel [25250.009302] usbserial: USB Serial Driver core
07/25/11 11:25:09 PM linuxbox kernel [25250.036587] USB Serial support registered for FTDI USB Serial Device
07/25/11 11:25:09 PM linuxbox kernel [25250.037636] ftdi_sio 2-4:1.0: FTDI USB Serial Device converter detected
07/25/11 11:25:09 PM linuxbox kernel [25250.037741] usb 2-4: Detected FT232RL
07/25/11 11:25:09 PM linuxbox kernel [25250.037747] usb 2-4: Number of endpoints 2
07/25/11 11:25:09 PM linuxbox kernel [25250.037753] usb 2-4: Endpoint 1 MaxPacketSize 64
07/25/11 11:25:09 PM linuxbox kernel [25250.037758] usb 2-4: Endpoint 2 MaxPacketSize 64
07/25/11 11:25:09 PM linuxbox kernel [25250.037763] usb 2-4: Setting MaxPacketSize 64
07/25/11 11:25:09 PM linuxbox kernel [25250.042236] usb 2-4: FTDI USB Serial Device converter now attached to ttyUSB0
07/25/11 11:25:09 PM linuxbox kernel [25250.042286] usbcore: registered new interface driver ftdi_sio
07/25/11 11:25:09 PM linuxbox kernel [25250.042291] ftdi_sio: v1.6.0:USB FTDI Serial Converters Driver


The relevant files are:

'/var/log/messages' on openSUSE
'/var/log/syslog' on ubuntu (probably debian as well)

They can be viewed in a text console/terminal with (start this before inserting the device!):

Code: [Select]
sudo tail -f /var/log/syslog

I'm sure there are GUI tools to show this information as well, but they will vary (drastically) between distributions.
• Upload doesn't work? Do a loop-back test.
• There's absolutely NO excuse for not having an ISP!
• Your AVR needs a brain surgery? Use the online FUSE calculator.
My projects: RGB LED matrix, RGB LED ring, various ATtiny gadgets...
• Microsoft is not the answer. It is the question, and the answer is NO!

Coding Badly

Quote
Between steps 3 and 4 one might consider adding something about listening/checking for proper acknowledgment (the nice gong sound) that the PC detected a new USB device connection.


How about a brief description of what to expect added to step #3?

retrolefty


Quote
Between steps 3 and 4 one might consider adding something about listening/checking for proper acknowledgment (the nice gong sound) that the PC detected a new USB device connection.


How about a brief description of what to expect added to step #3?



Well considering now that not all OS make a new usb connection sound, how about this?

3. With board still not plugged in, open the arduino IDE and check the Tools/Serial Port menu and write down the avalible comm ports, and then close the IDE. Plug in the arduino board, open the IDE and again check the Serial Port menu, there should be a new port number avalible that wasn't listed before, and that is the port number you should select. Failure to see a new port number means either a PC USB driver software problem, or a hardware failure with the FTDI or 8u2 serial converter chip on the board, and no need to proceed any further with this test.


Go Up