public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: tuxic@posteo.de
To: Gentoo <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] USBasp recognized/not recognized...what?
Date: Wed, 30 Aug 2017 18:46:14 +0200	[thread overview]
Message-ID: <20170830164614.jgpmhqapdhkxlbat@solfire> (raw)
In-Reply-To: <20170830155957.xcganln2q6zhlzmq@solfire>

Hi,

ok, I fixed it myself...an udev-rule was missing a '"'...
(and I am missing a coffee...)

Sorry for the false alert...!
Cheers
Meino




On 08/30 03:59, tuxic@posteo.de wrote:
> Hi,
> 
> for some third party USBasp (ISP flash programmer) clones I got
> some dubious situation:
> 
> These devices mainly consists of an ATmega 8A AU, which USB ports
> connect to a USB connector and smoe GPIOs are used to flash
> an attached microcontroller via ISP.
> 
> That's the theory.
> 
> Now I attach such a device to my Gentoo Linux box.
> 
> dmesg saus:
> [ 1919.948832] usb 7-4: new low-speed USB device number 7 using ohci-pci
> [ 1920.108797] usb 7-4: New USB device found, idVendor=16c0, idProduct=05dc
> [ 1920.108805] usb 7-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> [ 1920.108809] usb 7-4: Product: USBasp
> [ 1920.108812] usb 7-4: Manufacturer: www.fischl.de
> 
> which looks ok to me.
> 
> lsusb says:
> Bus 007 Device 007: ID 16c0:05dc Van Ooijen Technische Informatica shared ID for use with libusb
> Device Descriptor:
>   bLength                18
>   bDescriptorType         1
>   bcdUSB               1.10
>   bDeviceClass          255 Vendor Specific Class
>   bDeviceSubClass         0 
>   bDeviceProtocol         0 
>   bMaxPacketSize0         8
>   idVendor           0x16c0 Van Ooijen Technische Informatica
>   idProduct          0x05dc shared ID for use with libusb
>   bcdDevice            1.02
>   iManufacturer           1 www.fischl.de
>   iProduct                2 USBasp
>   iSerial                 0 
>   bNumConfigurations      1
>   Configuration Descriptor:
>     bLength                 9
>     bDescriptorType         2
>     wTotalLength           18
>     bNumInterfaces          1
>     bConfigurationValue     1
>     iConfiguration          0 
>     bmAttributes         0x80
>       (Bus Powered)
>     MaxPower               50mA
>     Interface Descriptor:
>       bLength                 9
>       bDescriptorType         4
>       bInterfaceNumber        0
>       bAlternateSetting       0
>       bNumEndpoints           0
>       bInterfaceClass         0 
>       bInterfaceSubClass      0 
>       bInterfaceProtocol      0 
>       iInterface              0 
> Device Status:     0x0000
>   (Bus Powered)
> 
> which also looks not that bad.
> 
> ...but...I get no device under /dev/
> like /dev/ttyUSB0 or such...
> 
> there only an entry here
> ls -l /dev/bus/usb/007/007
> crw-rw-r-- 1 root usb 189, 774 2017-08-30 17:56 007
> 
> Do I need more coffee or do I need more....what?
> 
> Any help is much appreciated!
> 
> Cheers
> Meino
> 
> 
> 


      reply	other threads:[~2017-08-30 16:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-30 15:59 [gentoo-user] USBasp recognized/not recognized...what? tuxic
2017-08-30 16:46 ` tuxic [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170830164614.jgpmhqapdhkxlbat@solfire \
    --to=tuxic@posteo.de \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox