Re: USB TRNG - Moonbase Otago - OneRNG

[Gary Palmer]

On Tue, Mar 28, 2017 at 04:11:47PM -0700, Tom wrote:
> Howdy,
> I've got one of these (a v3.0 to be exact) and I'm trying to get data out 
> of it. I found some info on one of their mailing lists but it doesn't 
> really get me anywhere:
> http://lists.onerng.info/groups/onerng-talk/messages/topic/KFurGvvNZPq5dh7XQyX14/
> 
> If I attempt to open the device with tip, the device detaches.
> 
> dmesg output:
> Mar 28 15:50:13 xyz kernel: umodem0 on uhub1
> Mar 28 15:50:13 xyz kernel: umodem0:  httpwww.moonbaseotago.comrandom 00, class 2/0, rev 2.00/0.09, addr 3> on 
> usbus0
> Mar 28 15:50:13 xyz kernel: umodem0: data interface 1, has no CM over 
> data, has break
> 
> Its been a while since I've debugged something like this so I'm hoping I'm 
> missing something simple. I'm in the SFBA if someone wants to borrow this 
> thing to figure it out.

I suggest you download the Linux scripts from

https://github.com/OneRNG/onerng.github.io/blob/master/sw/onerng_3.5.orig.tar.gz?raw=true

and see if the commands in files/onerng.sh make any difference.
A FreeBSD version of the stty command and then using the "echo" and "dd"
commands to set up the device and pull data

Not sure it will make a difference, but the best way to test it is by
doing what is expected in Linux

Regards,

Gary

___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

Re: Digi Watchport/T temperature sensor as /dev/ttyU

[Gary Palmer]

On Tue, Aug 09, 2016 at 08:28:47AM -0500, Karl Denninger wrote:
> 
> On 8/9/2016 01:36, O. Hartmann wrote:
> > On Sun, 24 Jul 2016 13:12:35 -0600
> > Ian Lepore  wrote:
> >
> >> On Sun, 2016-07-24 at 12:52 -0600, Warner Losh wrote:
> >>> On Sun, Jul 24, 2016 at 12:42 PM, Kevin Oberman 
> >>> wrote:  
>  There are several different USB serial drivers. Off-hand I see
>  ubser, ubsa,
>  uchcom, ucom, ucycom, uftdi, ubgensa, umcs, umct, umoscom, uplcom,
>  usb_serial, uslcom, and uvscom. Whether any of these will support
>  the TI
>  chip, I can't say. Most have man pages, but a few, as has been
>  noted, are
>  lacking one.  
> >>> I tried to automate discovery of these things. However, the only way
> >>> you can really know for sure about the TI chip is to read it's
> >>> datasheet
> >>> and compare that with extant drivers. It's actually easier than it
> >>> sounds.
> >>>
> >>> I've often thought of unification of the TTY USB drivers, since they
> >>> are
> >>> most (but not all) based on the standard plus extra bits.
> >>>
> >>> Warner  
> >> To reiterate:  we do not have a driver for TI 5052 chips.
> >>
> >> It's not much like other usb-serial chips.  In fact it's not strictly a
> >> usb-serial chip, it's a multifunction chip that includes a software
> >> -controllable usb hub, 2 serial ports, gpio, an i2c bus master, an MCU
> >> interface, a multichannel DMA controller, and apparently even has the
> >> ability to download your own 8052-compatible microcontroller code into
> >> the 5052 and have it take over from the built-in rom code.
> >>
> >> It would be reasonable enough to write a driver that initially
> >> supported only the uart part of the chip.
> >>
> >> -- Ian
> > Now, that I know that I can not use any of our plenty Digi Watchport/T 
> > sensors
> > with FreeBSD, I'm looking for a cheap alternative of sensor, prefereably 
> > being
> > capable of taking temperature and humidity and being accessed as easy as a
> > serial terminal - as the Digi Watchport/T does with Linux.
> >
> > I still have a "resistance" changing the OS of our infrastructure to Linux 
> > due
> > to ZFS, but the very good support of drivers with the Linux OS is tempting 
> > ...
> > ___
> > freebsd-usb@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-usb
> > To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
> 
> Does hardware platform matter?  If not a very inexpensive alternative
> set is found on Adafruit's site for the Raspberry Pi and FreeBSD can
> easily talk to either some of the options directly or a cheap ($10)
> 4-channel 12-bit analog board.  I am using this approach with the Pi2 as
> a pool controller with multiple temperature inputs and drive (through a
> relay board) to handle both the VFD-controlled pump motor and valves,
> plus spa heater.

If you go down that path the DS 18B20 is a digital temperature probe
that can be tied to the GPIO pins on a PI and read from python
quite easily.  Don't think it does humidity, but as the temp. probes
have a hardware address you can hook multiple up to the same GPIO pin.

If you want humidity also then there is the DHT22 or DHT11, both
of which can be tied to the PI but need a GPIO pin per sensor.  I 
haven't tried either of them personally.

Regards,

Gary
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

Re: USB and loader.conf hints

[Gary Palmer]

On Sun, Jul 03, 2016 at 02:42:46AM +0100, Gary Palmer wrote:
> Hi,
> 
> Is it possible to wire a disk device to a particular USB port
> via loader.conf hints?
> 
> My problem is that my root device appears via USB.  If I leave my 3g
> dongle attached, then it competes for the root device for what gets
> da0, and the two times I've tried the dongle wins and gets da0 and
> the boot stops as it can't find the root partitions.
> 
> This is in a nanobsd install, so I'm not sure if labels would work
> as nanobsd is set up to use device names.

More specifically, I see from dmesg 

  "umass1: at uhub1, port 1, addr 4 (disconnected)"

  (why that isn't also available on probe I don't know).  

How do I represent that in loader.conf?  e.g.

hints.umass.1.at="uhub1" 

doesn't exactly communicate what is needed, I also need the port number
in there somehow, and "hint.umass.1.port" would seem to be reserved for
the I/O address according to device.hints(5)


FYI the usbconfig output is:

ugen0.1:  at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) 
pwr=SAVE (0mA)
ugen0.2:  at usbus0, cfg=0 md=HOST spd=HIGH 
(480Mbps) pwr=SAVE (0mA)
ugen0.3:  at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) 
pwr=ON (96mA)
ugen0.4:  at usbus0, cfg=0 
md=HOST spd=HIGH (480Mbps) pwr=ON (500mA)

Thanks,

Gary
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

USB and loader.conf hints

[Gary Palmer]

Hi,

Is it possible to wire a disk device to a particular USB port
via loader.conf hints?

My problem is that my root device appears via USB.  If I leave my 3g
dongle attached, then it competes for the root device for what gets
da0, and the two times I've tried the dongle wins and gets da0 and
the boot stops as it can't find the root partitions.

This is in a nanobsd install, so I'm not sure if labels would work
as nanobsd is set up to use device names.

Thanks,

Gary
___
freebsd-usb@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"

Re: forcing the device to be 1.1

[Gary Palmer]

On Wed, Apr 15, 2015 at 11:45:44AM +0500, Eugene M. Zheganin wrote:
 Hi.
 
 I need to force the device to work in 1.1 mode, because I need to make
 it visible to the virtualbox-ose, which supports only 1.1 devices.
 By default my device is in 2.0 I guess (usbconfig shows FULL speed).

LOW or FULL = USB 1 speed
HIGH = USB 2 speed
SUPER = USB 3 speed

Regards,

Gary
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org

ZTE MF730M 3G dongle help please

[Gary Palmer]

Hi,

I have a ZTE MF730M.  When first connected to my 9.3-RELEASE-p7 box
it takes a few seconds (approximately 7) and then shows up as:

% usbconfig -d ugen2.7 dump_device_desc
ugen2.7: ZTE Mobile Broadband Station ZTE,Incorporated at usbus2, cfg=1 
md=HOST spd=HIGH (480Mbps) pwr=ON (500mA)

  bLength = 0x0012 
  bDescriptorType = 0x0001 
  bcdUSB = 0x0200 
  bDeviceClass = 0x 
  bDeviceSubClass = 0x 
  bDeviceProtocol = 0x 
  bMaxPacketSize0 = 0x0040 
  idVendor = 0x19d2 
  idProduct = 0x1420 
  bcdDevice = 0xf0f7 
  iManufacturer = 0x0001  ZTE,Incorporated
  iProduct = 0x0002  ZTE Mobile Broadband Station
  iSerialNumber = 0x0004  1234567890ABCDEF
  bNumConfigurations = 0x0003 

with the following config:

% usbconfig -d ugen2.7 dump_all_config_desc
ugen2.7: ZTE Mobile Broadband Station ZTE,Incorporated at usbus2, cfg=1 
md=HOST spd=HIGH (480Mbps) pwr=ON (500mA)


 Configuration index 0

bLength = 0x0009 
bDescriptorType = 0x0002 
wTotalLength = 0x0020 
bNumInterfaces = 0x0001 
bConfigurationValue = 0x0001 
iConfiguration = 0x0003  Self Powered
bmAttributes = 0x00c0 
bMaxPower = 0x00fa 

Interface 0
  bLength = 0x0009 
  bDescriptorType = 0x0004 
  bInterfaceNumber = 0x 
  bAlternateSetting = 0x 
  bNumEndpoints = 0x0002 
  bInterfaceClass = 0x0008 
  bInterfaceSubClass = 0x0006 
  bInterfaceProtocol = 0x0050 
  iInterface = 0x0005  Mass Storage

 Endpoint 0
bLength = 0x0007 
bDescriptorType = 0x0005 
bEndpointAddress = 0x0081  IN
bmAttributes = 0x0002  BULK
wMaxPacketSize = 0x0200 
bInterval = 0x 
bRefresh = 0x 
bSynchAddress = 0x 

 Endpoint 1
bLength = 0x0007 
bDescriptorType = 0x0005 
bEndpointAddress = 0x0001  OUT
bmAttributes = 0x0002  BULK
wMaxPacketSize = 0x0200 
bInterval = 0x0001 
bRefresh = 0x 
bSynchAddress = 0x 



 Configuration index 1

bLength = 0x0009 
bDescriptorType = 0x0002 
wTotalLength = 0x0020 
bNumInterfaces = 0x0001 
bConfigurationValue = 0x0002 
iConfiguration = 0x0003  Self Powered
bmAttributes = 0x00c0 
bMaxPower = 0x00fa 

Interface 0
  bLength = 0x0009 
  bDescriptorType = 0x0004 
  bInterfaceNumber = 0x 
  bAlternateSetting = 0x 
  bNumEndpoints = 0x0002 
  bInterfaceClass = 0x0008 
  bInterfaceSubClass = 0x0006 
  bInterfaceProtocol = 0x0050 
  iInterface = 0x0005  Mass Storage

 Endpoint 0
bLength = 0x0007 
bDescriptorType = 0x0005 
bEndpointAddress = 0x0081  IN
bmAttributes = 0x0002  BULK
wMaxPacketSize = 0x0200 
bInterval = 0x 
bRefresh = 0x 
bSynchAddress = 0x 

 Endpoint 1
bLength = 0x0007 
bDescriptorType = 0x0005 
bEndpointAddress = 0x0001  OUT
bmAttributes = 0x0002  BULK
wMaxPacketSize = 0x0200 
bInterval = 0x0001 
bRefresh = 0x 
bSynchAddress = 0x



the kernel reports:

Jan 10 16:38:10 noop kernel: usb_alloc_device: Found possible auto-install disk 
(trying next config)
Jan 10 16:38:10 noop kernel: ugen2.7: ZTE,Incorporated at usbus2
Jan 10 16:38:10 noop kernel: umass0: Mass Storage on usbus2
Jan 10 16:38:10 noop kernel: umass0:  SCSI over Bulk-Only; quirks = 0x
Jan 10 16:38:10 noop kernel: umass0: Get Max Lun not supported (USB_ERR_STALLED)
Jan 10 16:38:10 noop kernel: umass0:8:0:-1: Attached to scbus8
Jan 10 16:39:24 noop kernel: (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 
00 24 00 
Jan 10 16:39:24 noop kernel: (probe0:umass-sim0:0:0:0): CAM status: CCB request 
completed with an error
Jan 10 16:39:24 noop kernel: (probe0:umass-sim0:0:0:0): Retrying command
Jan 10 16:40:38 noop kernel: (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 
00 24 00 
Jan 10 16:40:38 noop kernel: (probe0:umass-sim0:0:0:0): CAM status: CCB request 
completed with an error
Jan 10 16:40:38 noop kernel: (probe0:umass-sim0:0:0:0): Retrying command
Jan 10 16:41:51 noop kernel: (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 
00 24 00 
Jan 10 16:41:51 noop kernel: (probe0:umass-sim0:0:0:0): CAM status: CCB request 
completed with an error
Jan 10 16:41:51 noop kernel: (probe0:umass-sim0:0:0:0): Retrying command
n 10 16:43:05 noop kernel: (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 00 
24 00 
Jan 10 16:43:05 noop kernel: (probe0:umass-sim0:0:0:0): CAM status: CCB request 
completed with an error
Jan 10 16:43:05 noop kernel: (probe0:umass-sim0:0:0:0): Retrying command
Jan 10 16:44:19 noop kernel: (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 00 00 
00 24 00 
Jan 10 16:44:19 noop kernel: (probe0:umass-sim0:0:0:0): CAM status: CCB request 
completed with an error
Jan 10 16:44:19 noop kernel: (probe0:umass-sim0:0:0:0): Error 5, Retries 
exhausted


nothing shows up in camcontrol devlist.

If I do

Re: FreeBSD and unidentified iPod Touch

[Gary Palmer]

On Thu, Sep 08, 2011 at 10:44:05PM +0200, Zahemszky G?bor wrote:
 Hi!
 
 My son has got an iPod Touch (3rd generation, 8GB). We van use iTunes
 on Windows, bu we cannot reach it on FreeBSD 8.2R, amd64. When we connect it, 
 we
 got the following output:
 
 Sep  8 22:22:29 Picasso root: Unknown USB device: vendor 0x05ac product 
 0x1293 bus uhub2
 Sep  8 22:22:29 Picasso kernel: ugen2.2: Apple Inc. at usbus2
 
 # usbconfig
 ...
 ugen2.2: iPod Apple Inc. at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON
 
 # usbconfig -d ugen2.2 dump_device_desc
 ugen2.2: iPod Apple Inc. at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON
 
   bLength = 0x0012 
   bDescriptorType = 0x0001 
   bcdUSB = 0x0200 
   bDeviceClass = 0x 
   bDeviceSubClass = 0x 
   bDeviceProtocol = 0x 
   bMaxPacketSize0 = 0x0040 
   idVendor = 0x05ac 
   idProduct = 0x1293 
   bcdDevice = 0x0001 
   iManufacturer = 0x0001  Apple Inc.
   iProduct = 0x0002  iPod
   iSerialNumber = 0x0003  63160800ecbe33eb705dd1291c8a0f78547ea5b3
   bNumConfigurations = 0x0003 
 
 Is it possible to use some of the usb_quirks, or something other to see that 
 machine az an umass device?

iPod Touch is no longer a mass storage device, unlike earlier iPod models
with the hard drives inside.  It uses a proprietary communications system
for updates from iTunes.

There might be something in ports which allows communication

Regards,

Gary
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org

Re: problem with bluetooth dongle

[Gary Palmer]

On Sun, Feb 20, 2011 at 01:01:19PM +0200, Volodymyr Kostyrko wrote:
 20.02.2011 11:31, Hans Petter Selasky wrote:
 On Sunday 20 February 2011 01:47:33 Volodymyr Kostyrko wrote:
 I have something like:
 
 Feb 20 02:43:16 limbo kernel: ugen2.3:Broadcom  at usbus2
 Feb 20 02:43:16 limbo kernel: uhub4:Broadcom BCM2035B0, class 9/0, rev
 1.10/1.00, addr 3  on usbus2
 Feb 20 02:43:16 limbo kernel: uhub4: 3 ports with 0 removable, bus powered
 Feb 20 02:43:17 limbo kernel: ugen2.4:vendor 0x0a12  at usbus2
 Feb 20 02:43:17 limbo kernel: ubt0:vendor 0x0a12 product 0x0001, class
 224/1, rev 1.10/1.01, addr 4  on usbus2
 Feb 20 02:43:17 limbo root: Unknown USB device: vendor 0x0a12 product
 0x0001 bus uhub4
 Feb 20 02:43:18 limbo root: Unknown USB device: vendor 0x0a5c product
 0x3502 bus uhub4
 Feb 20 02:43:18 limbo kernel: ugen2.5:vendor 0x0a5c  at usbus2
 Feb 20 02:43:18 limbo kernel: ugen2.6:vendor 0x0a5c  at usbus2
 Feb 20 02:43:18 limbo kernel: ums1:vendor 0x0a5c HIDM, class 0/0, rev
 1.10/1.00, addr 6  on usbus2
 Feb 20 02:43:18 limbo kernel: ums1: 3 buttons and [XY] coordinates ID=0
 
 And it almost works. I can register devices with it, but I can't do
 anything more. Any phone connected shows that this device doesn't
 provide any services despite sdpd is running.
 
 How did you start the bluetooth daemons? Did you load the required netgraph
 modules?
 
 1. kldload ng_ubt
 2. insert dongle
 (above output in /var/log/messages)
 3. /etc/rc.d/bluetooth start ubt0
 /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device ubt0
 (and there's no /dev/ubt0 also)

Normally there isn't a /dev node for ubt0 (although I'm not sure what version
of FreeBSD you're running) as its hooked through netgraph - try 
running ngctl list as root and see if there is a ubt0 node there.

Regards,

Gary

___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org

Re: trackballs support

[Gary Palmer]

On Wed, Dec 08, 2010 at 09:13:39AM +0200, Zeus V Panchenko wrote:
 Hi All,
 
 i'm thinking of purchasing trackbal and would like to ask, wheather
 somebody has experience of getting trackball working under FreeBSD
 xorg?
 
 i think of:
 Kensington trackballs
 http://us.kensington.com/html/1436.html
 
 is it be possible to use these models?

I cannot speak to the Kensington models, but I've been using the
Logitech TrackMan Marble series on my desktops running FreeBSD for
over a decade with no problems.  The Logitech's show up as a mouse and
works as a mouse in X with no problems.

FreeBSD 7 boot message:

ums0: Logitech USB-PS/2 Trackball, class 0/0, rev 1.00/2.00, addr 3 on uhub3
ums0: 3 buttons and Z dir.

Regards,

Gary
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to freebsd-usb-unsubscr...@freebsd.org

Re: Panic on connecting external harddrive

[Gary Palmer]

Ben Stuyts wrote:

Hi Gary,

On 12 Feb 2008, at 23:13, Gary Palmer wrote:


On Tue, Feb 12, 2008 at 07:15:21PM +0100, Ben Stuyts wrote:

I have a consistent panic when I connect a 2.5 LaCie 250 GB drive to
a SuperMicro 6015P-TR. This server is running amd64 with ZFS. Not
being able to connect external harddrives is kind of a show stopper
for putting this server into production.


Has anyone pointed you at

http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html 



No, but I've read about it. I can supply a kernel dump if that helps.


Ben,

You might get someone who knows the USB stack to spot a problem if you 
are able to supply a full backtrace with variables and line numbers for 
the functions.  If you feel the need to file a PR, that level of 
information will be required.


Regards,

Gary

P.S. I am not a USB guru, just trying to help

___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Panic on connecting external harddrive

[Gary Palmer]

On Tue, Feb 12, 2008 at 07:15:21PM +0100, Ben Stuyts wrote:
 Hi,
 
 I posted this to amd64 and current mailing lists, but can't get any  
 help. I looked through this list's archive but no solution either.  
 Maybe somebody here can help me?
 
 I have a consistent panic when I connect a 2.5 LaCie 250 GB drive to  
 a SuperMicro 6015P-TR. This server is running amd64 with ZFS. Not  
 being able to connect external harddrives is kind of a show stopper  
 for putting this server into production.
 
 Here is the panic message:
 
 Fatal trap 12: page fault while in kernel mode
 cpuid = 0; apic id = 00
 fault virtual address = 0x290
 fault code= supervisor read data, page not present
 instruction pointer   = 0x8:0x803ff8aa
 stack pointer = 0x10:0xd72eed70
 frame pointer = 0x10:0xd72eedb0
 code segment  = base 0x0, limit 0xf, type 0x1b
   = DPL 0, pres 1, long 1, def32 0, gran 1
 processor eflags  = interrupt enabled, resume, IOPL = 0
 current process   = 48 (usb3)
 [thread pid 48 tid 100047 ]
 Stopped at  usb_transfer_complete+0x10a:movq0x290(%rax),%rax
 db tr
 Tracing pid 48 tid 100047 td 0xff00034fe350
 usb_transfer_complete() at usb_transfer_complete+0x10a
 usbd_start_transfer() at usbd_start_transfer+0x1a1
 bus_dmamap_load() at bus_dmamap_load+0x453
 usbd_transfer() at usbd_transfer+0xae
 usbd_sync_transfer() at usbd_sync_transfer+0xe
 usbd_do_request_flags_pipe() at usbd_do_request_flags_pipe+0x96
 usbd_do_request_flags() at usbd_do_request_flags+0x25
 usbd_get_string_desc() at usbd_get_string_desc+0x88
 usbd_get_string() at usbd_get_string+0xcd
 usbd_devinfo_vp() at usbd_devinfo_vp+0x80
 usbd_devinfo() at usbd_devinfo+0x46
 usbd_new_device() at usbd_new_device+0x68b
 uhub_explore() at uhub_explore+0x295
 usb_discover() at usb_discover+0x38
 usb_event_thread() at usb_event_thread+0x9f
 fork_exit() at fork_exit+0x12b
 fork_trampoline() at fork_trampoline+0xe
 --- trap 0, rip = 0, rsp = 0xd72efd30, rbp = 0 ---

Has anyone pointed you at

http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html

?

Regards,

Gary
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to [EMAIL PROTECTED]