USB not found
f6itu
Sid Boyce
I use this version:-
svn checkout http://usbsoftrock.googlecode.com/svn/trunk/
usbsoftrock-read-only
From dmesg
========
[111161.444050] usb 1-3: new high-speed USB device number 3 using ehci-pci
[111161.577730] usb 1-3: New USB device found, idVendor=16c0, idProduct=05dc
[111161.577741] usb 1-3: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[111161.577748] usb 1-3: Product: DG8SAQ-I2C
[111161.577754] usb 1-3: Manufacturer: www.obdev.at
[111161.577759] usb 1-3: SerialNumber: 1.0.0.0.0.0.A
[111161.874788] usbcore: registered new interface driver snd-usb-audio
root@sdrbox:~# lsusb
Bus 001 Device 003: ID 16c0:05dc VOTI shared ID for use with libusb
root@sdrbox:~# cat /proc/asound/cards
0 [NVidia ]: HDA-Intel - HDA NVidia
HDA NVidia at 0xfae78000 irq 22
1 [DG8SAQI2C ]: USB-Audio - DG8SAQ-I2C
www.obdev.at DG8SAQ-I2C at usb-0000:00:04.1-3,
high speed
root@sdrbox:~# widget-control -g
10 37 widget uac2_dg8saq normal normal ak5394a cs4344 hd44780 500ms
If MoboControl is seeing it, probably none of the above are the problem.
Still worth trying and also the svn version of usbsoftrock and some
usbsoftrock commands.
73 ... Sid.
On 21/03/13 19:16, f6itu wrote:
> Hi
> I'm stuck for more than 4 days on the same problem : my USB port is
> not seen.
> I've setup three linux machines.
> - two with the M8MDP procedure and USBSoftrock 1.0.2 "alex's mobo
> changes" version using a "pure debian" without any X11 interface (for
> a plain and unique GHPSDR3 character based Stream server without qt5),
> the second one on an Ubuntu 12.04.2 LTS with all the graphical stuff
> - the third one with the "quick" GHPSDR3-USB-Boot. and the
> "softrock_start" script" (with Jackd or PulseAudio configuration)
> All of these configuration give me the same error : USB not found
>
> BUT
> moboControl, I can change my image and reset my widget WidgetControl,
> USB VendorID and ProductID are OK.
> On the Widget side, board type is set on "Widget", image is set on
> "uac2_DG8SAQ", /in normal, /out normal, ADC, DAC and LCD configured
> for what's on the widget...
> I should have missed something obvious but I frankly don't know when
> or where
>
> Hope someone knows where is my gremlin :- (
>
> Marc
>
> ---
> You received this message because you are subscribed to the Google
> Groups "MOBOKITS" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to MOBOKITS+u...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
f6itu
Hi Sid
At last, I could find the time to look at my USB port.
Lsusb gives me
Bus 001 Device 015: ID 16c0:05dc VOTI shared ID for use with libusb
Seems to be in conflict with libusb.
Lsusb –t said
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/8p, 480M
|__ Port 5: Dev 15, If 0, Class=>ifc, Driver=, 480M
|__ Port 5: Dev 15, If 1, Class=audio, Driver=snd-usb-audio, 480M
|__ Port 5: Dev 15, If 2, Class=audio, Driver=snd-usb-audio, 480M
|__ Port 5: Dev 15, If 3, Class=audio, Driver=snd-usb-audio, 480M
It seems to be a “classical” in the AVR literature
Trying to change the udev rules with 666
(SUBSYSTEMS=="usb", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="05dc", GROUP="users", MODE="0666")
Still gives a
“Could not open USB device "DG8SAQ-I2C" with vid=0x16c0 pid=0x5dc, retrying
Could not open USB device "DG8SAQ-I2C" with vid=0x16c0 pid=0x5dc, retrying
Permanent problem opening usb device. Giving up.”
(after restarting service udev, unplugging and plugging the usb)
And
dmesg | grep -i usb gives
/…/
[ 0.561451] hub 5-0:1.0: >USB hub found
[ 0.561585] usbcore: registered new interface driver libusual
[ 1.152070] usb 1-5: >new high-speed USB device number 5 using ehci_hcd
[ 1.285569] usb 1-5: >New USB device found, idVendor=16c0, idProduct=05dc
[ 1.285586] usb 1-5: >New USB device strings: Mfr=1, Product=2, SerialNumber= 3
[ 1.285589] usb 1-5: >Product: Yoyodyne SDR-Widget
[ 1.285592] usb 1-5: >Manufacturer: SDR-Widget
[ 1.285594] usb 1-5: >SerialNumber: 1.0.0.0.0.0.0
/…/
[ 558.064691] usb 1-5: >USB disconnect, device number 5
[ 562.792096] usb 1-5: >new high-speed USB device number 7 using ehci_hcd
[ 562.926092] usb 1-5: >New USB device found, idVendor=16c0, idProduct=05dc
[ 562.926102] usb 1-5: >New USB device strings: Mfr=1, Product=2, SerialNumber= 3
[ 562.926109] usb 1-5: >Product: Yoyodyne SDR-Widget
[ 562.926115] usb 1-5: >Manufacturer: SDR-Widget
[ 562.926120] usb 1-5: >SerialNumber: 1.0.0.0.0.0.0
Sid Boyce
[111161.577741] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[111161.577748] usb 1-3: Product: DG8SAQ-I2C
[111161.577754] usb 1-3: Manufacturer: www.obdev.at
[111161.577759] usb 1-3: SerialNumber: 1.0.0.0.0.0.A
This is the source code I used.
"git clone git://github.com/amontefusco/sdr-widget.git && cd sdr-widget && git checkout sdr-widget-2 && git pull origin"
Looks like settings are wrong or audio-widget firmware loaded.
# widget-control -g
10 37 widget uac2_dg8saq normal normal ak5394a cs4344 hd44780 500ms
"widget-control -s 8 27 widget uac2_dg8saq normal normal ak5394a cs4344"
If you need any of that stuff, I can supply ones I just built
widget.hex
64-bit dfu-programmer and widget-control.
73 ... Sid.
--
---
You received this message because you are subscribed to the Google Groups "MOBOKITS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to MOBOKITS+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
marc olanie
your datas
[111161.577754] usb 1-3: Manufacturer: www.obdev.at
>This is the source code I used.
>"git clone git://github.com/amontefusco/sdr-widget.git && cd sdr-widget && git checkout sdr-widget-2 && git pull origin"
>Looks like settings are wrong or audio-widget firmware loaded.
Sid Boyce
Mine is an older Widget with the cs4344.
The widget.hex code is the latest and widget-control is a 64-bit binary.
The command below will say what how it's currently set up.
# ./widget-control -g
10 37 widget uac2_dg8saq normal normal ak5394a cs4344
# ./widget-control -s 8 27 widget uac2_dg8saq normal normal ak5394a cs4344
See what you get from the commands below.
root@sdrbox1:/opt/quisk-3.6.8/softrock# widget-control -g
10 37 widget uac2_dg8saq normal normal ak5394a cs4344
usage: sudo ./widget-control [options] [values]
options: -d = print the default feature values.
-g = get the feature values from the widget nvram.
-l = list the possible feature values.
-m = get the feature values from the widget ram.
-r = reboot the widget.
-s = set the feature values in the widget nvram.
Only -s takes values, in the form printed by -d or -g or -m.
The acceptable values for each feature are listed by -l.
The major and minor version numbers are optional to -s, but
if provided they must match the ones printed by -d, -g, -l, and -m,
which must all match each other, or your widget-control is out of
sync with your widget.
root@sdrbox1:/opt/quisk-3.6.8/softrock# widget-control -l
major 8
minor 27
board = none widget dib ab1 test
image = flashyblinky uac1_audio uac1_dg8saq uac2_audio uac2_dg8saq hpsdr test
in = normal swapped
out = normal swapped
adc = none ak5394a
dac = none cs4344 es9022
root@sdrbox1:/opt/quisk-3.6.8/softrock# widget-control -m
10 37 widget uac2_dg8saq normal normal ak5394a cs4344
--
---
You received this message because you are subscribed to the Google Groups "MOBOKITS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to MOBOKITS+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Alex Lee
See quoted message
Marc,
You are using a new version of firmware with a different vid/pid that old software cannot find unless they are modified.
So try to use old version firmware:
http://code.google.com/p/sdr-widget/downloads/detail?name=sdr-widget-2012-10-22.elf&can=2&q=
which has the traditional vid/pid .
Alex
On 25 Mar 2013 19:10, <MOBO...@googlegroups.com> wrote:Group: http://groups.google.com/group/MOBOKITS/topics
- USB not found [2 Updates]
marc olanie <marc....@gmail.com> Mar 24 02:15PM +0100
Hi Sid
Many tnks for you time and patience
your datas
[111161.577748] usb 1-3: Product: DG8SAQ-I2C
my datas
[ 1.285589] usb 1-5: >Product: Yoyodyne SDR-Widget
****
Sid Boyce <boyc...@gmail.com> Mar 24 03:11PM
You received this message because you are subscribed to the Google Group MOBOKITS.
You can post via email.
To unsubscribe from this group, send an empty message.
For more options, visit this group.
marc olanie
In fact, I'm using the sdr-widget-2012-10-22.elf which seems to be the very last one on the googlecode repo
Which versions of the firmware is considered having the compatible Pid Vid ?
Anyhow, as soon as I have some spare time, I’ll follow Sid’s advices and I’ll build the most recent version of the CLI & dsp servers
73’
Marc