Topping HS01 doesnt work with my "self powered" USB DAC

[fatoldgit]

According to the diagram below....

... a "self powered" device will work...which my DAC is... its USB circuits are powered via a clean line inside the DAC.

But my Linux endpoint doesnt see my DAC (used both USB 2 and 3 ports on the PC).

There were no messages in the dmesg log indicating that the OS saw the device (i.e. wasnt a case of it being discovered then disconnected for some reason)

If I plug in my Topping D10B into the same PC USB ports, the D10B is found (using the cables supplied with the HS01/D10B).

Now... I use a custom made "data only" USB cable (i.e. where the 5V line isnt active, noting I used the Topping supplied cable from the PC -> HS01) so maybe the HS01 needs to "see" the 5V pin on the DAC to register there is a device there.

Will see if that is the root cause and report back but as I wont be replacing my "data only" USB cable, the HS01 is a paper weight (which given its size it also wont be very effective at)

Peter

 

[fatoldgit]

nope.. not related to the "data only" cable.

Used Topping supplied cables into/from the HS01 between by PC and main DAC and no joy.

Below we see my main DAC seen via my "data only" cable on the EHCI PC bus (which is USB 2 root hub)

/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
|__ Port 2: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 480M
|__ Port 3: Dev 7, If 3, Class=Application Specific Interface, Driver=, 480M
|__ Port 3: Dev 7, If 1, Class=Audio, Driver=snd-usb-audio, 480M
|__ Port 3: Dev 7, If 4, Class=Human Interface Device, Driver=usbhid, 480M
|__ Port 3: Dev 7, If 2, Class=Audio, Driver=snd-usb-audio, 480M
|__ Port 3: Dev 7, If 0, Class=Audio, Driver=snd-usb-audio, 480M
|__ Port 5: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 5: Dev 5, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 5: Dev 5, If 2, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 6: Dev 6, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 6: Dev 6, If 0, Class=Human Interface Device, Driver=usbhid, 12M

Bus 001 Device 006: ID 046d:c52f Logitech, Inc. Unifying Receiver
Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 007: ID 20b1:2017 XMOS Ltd
Bus 001 Device 003: ID 13fe:4200 Kingston Technology Company Inc.
Bus 001 Device 002: ID 8087:8001 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Below we see unused D10B DAC seen via topping supplied cabled on the EHCI PC bus (which is USB 2 hub)

/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
|__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
|__ Port 2: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 480M
|__ Port 3: Dev 8, If 1, Class=Audio, Driver=snd-usb-audio, 480M
|__ Port 3: Dev 8, If 2, Class=Application Specific Interface, Driver=, 480M
|__ Port 3: Dev 8, If 0, Class=Audio, Driver=snd-usb-audio, 480M
|__ Port 5: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 5: Dev 5, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 5: Dev 5, If 2, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 6: Dev 6, If 1, Class=Human Interface Device, Driver=usbhid, 12M
|__ Port 6: Dev 6, If 0, Class=Human Interface Device, Driver=usbhid, 12M

Bus 001 Device 006: ID 046d:c52f Logitech, Inc. Unifying Receiver
Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 008: ID 152a:8750 Thesycon Systemsoftware & Consulting GmbH
Bus 001 Device 003: ID 13fe:4200 Kingston Technology Company Inc.
Bus 001 Device 002: ID 8087:8001 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

So am dead in the water.... not that I had any audible issue... just viewed the HS01 as icing on the cake.

Peter

 

[JSmith]

my DAC

Which DAC is that and does it support USB 2.0?

Topping HS01 is compatible with the USB 2.0 transmission protocol. It doesn't work with previous versions including the USB 1.0 or USB 1.1. With its exclusive USB 2.0 transmission, the HS01 provides support for high-end DAC systems that support 32Bit/768kHz and native DSD512 decoding.

TOPPING HS01 USB 2.0 High Speed Audio Isolator

Buy Topping HS01 USB 2.0 High-Speed Audio Isolator Low Latency Eliminate the Ground Loop Noise on HiFiGo, you can enjoy a year warranty and the best after-sales service.

hifigo.com

MEASUREMENTS: Topping HS01 - USB 2.0 Isolator & Ground Loop Eliminator (and a listen to Santana's "Blessings and Miracles")

A blog for audiophiles about more objective topics. Measurements of audio gear. Reasonable, realistic, no snakeoil assessment of sound, and equipment.

archimago.blogspot.com

JSmith

 

[fatoldgit]

does it support USB 2.0?

JSmith

Yes... as per above "lsusb" outputs, the DAC works fine under USB 2.0 as its connected to "Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub".

The fact that it is never seen by the OS when connected thru the HS01 (as determined by looking at dmesg), means the HS01 doesnt see the DAC at all.

The difference between my main DAC and my unused D10B, when using two Topping supplied USB cables (PC -> HS01 and HS01 -> DAC), is the D10B is bus powered while my main DAC uses its own internal power supply to power the USB circuits.

So for whatever reason (maybe some handshake doesnt occur due to my DAC's self powered USB circuits) the first connection model in the topology diagram above isnt universally applicable.

Peter

 

[Gradius]

Must be related to power management:

Linux Kernel Documentation :: usb : power-management.txt

Linux Kernel Documentation

mjmwired.net

This file contains one of three words: "on", "auto", or "suspend". You can write those words to the file to change the device's setting.

"on" means that the device should be resumed and autosuspend is not allowed. (Of course, system suspends are still allowed.)

"auto" is the normal state in which the kernel is allowed to autosuspend and autoresume the device.

"suspend" means that the device should remain suspended, and autoresume is not allowed. (But remote wakeup may still be allowed, since it is controlled separately by the power/wakeup attribute.)

Example:
echo on > /sys/bus/usb/devices/usb1/power/level

 

[fatoldgit]

Must be related to power management:

Linux Kernel Documentation :: usb : power-management.txt

Linux Kernel Documentation

mjmwired.net

This file contains one of three words: "on", "auto", or "suspend". You can write those words to the file to change the device's setting.


Example:
echo on > /sys/bus/usb/devices/usb1/power/level

Currently we see:

cd /sys/bus/usb/devices/usb1/power
cat level
auto

Will try "on" tomorrow and report back.

Thanks for the tip

Peter

 

[staticV3]

@fatoldgit the D10B probably draws more current than what the HS01 can supply on its own.
Have you tried plugging an external power supply like a power bank into the HS01's Type-C port, then plugging your D10B into the HS01?