Forums - mini-dm on Linux

5 posts / 0 new
Last post
mini-dm on Linux
joes
Join Date: 28 Jan 16
Posts: 7
Posted: Wed, 2016-06-01 08:40

mini-dm on Linux doesn't seem to work on DragonBoard 820, both with Hexagon SDK 2.0 and 3.0.

All it does is to print this:

Running mini-dm version: 3.0

Device found with Product ID 0x901d. Continuing...
mini-dm is waiting for a DMSS connection...
but no message appears e.g. when running the calculator example
like "/data/calculator 0 0 10" or playing audio like the
Debugging_Message Logs.html doc page suggests.
 
Is there something that needs to be done on DB820 to enable mini-dm output?
 
Also, when calling mini-dm with any argument starting with a dash,
like -h or --help, it just crashes (segmentation fault).
 
  • Up0
  • Down0
Edith
Join Date: 16 Mar 16
Posts: 11
Posted: Wed, 2016-06-01 08:49


I have just succesfully run mini-dm on VirtualBox, Ubuntu 14_04. What I did was to run USB1.0 port for USB connection. I have also installed usb driver from SDK 2.0: ../tools/libusb/libusb-1.0.so 

zugaj@ezugaj-VirtualBox:/tools/Qualcomm/Hexagon_SDK/2.0/tools/mini-dm/Linux_Debug$ ./mini-dm 
Device found with Product ID 0x901d. Continuing...
mini-dm is waiting for a DMSS connection...
DMSS is connected. Running mini-dm...
[08500/02]  50:07.831  test enabled  0559  sigverify.c
...
  • Up0
  • Down0
joes
Join Date: 28 Jan 16
Posts: 7
Posted: Wed, 2016-06-01 09:17

Thanks for letting me know. Is your platform also DB820?

The libusb-1.0 in both SDK 2.0 and 3.0 is actually a HTML error page saying "301 Moved Permanently"...

mini-dm already found the device on the PC but nothing connects to it from the device side, if I interpret the messages correctly.

Checking with LIBUSB_DEBUG=4 confirms the device is found but the bulk URBs complete with error -71 (EPROTO).

 

  • Up0
  • Down0
Edith
Join Date: 16 Mar 16
Posts: 11
Posted: Wed, 2016-06-01 23:55

I am using DB810. I had met similar problems with mini-dm. It was correctly finding the device but nothing happened later. Then I moved to usb1.0.

BTW, have you tried running Windows version? I started from Windows one and after the installation of Qm drivers mini-dm started working w/o additional steps.

Attached my logs from Linux:

[timestamp] [threadID] facility level [function call] <message>
--------------------------------------------------------------------------------
[ 0.000004] [000039a1] libusbx: debug [libusb_init] created default context
[ 0.000053] [000039a1] libusbx: debug [libusb_init] libusbx v1.0.17.10830
[ 0.000076] [000039a1] libusbx: debug [find_usbfs_path] found usbfs at /dev/bus/usb
[ 0.000089] [000039a1] libusbx: debug [op_init] bulk continuation flag supported
[ 0.000095] [000039a1] libusbx: debug [op_init] zero length packet flag supported
[ 0.000106] [000039a1] libusbx: debug [op_init] sysfs can relate devices
[ 0.000111] [000039a1] libusbx: debug [op_init] sysfs has complete descriptors
[ 0.000481] [000039a2] libusbx: debug [linux_udev_event_thread_main] udev event thread entering.
[ 0.000638] [000039a1] libusbx: debug [linux_get_device_address] getting address for device: usb1 detached: 0
[ 0.000702] [000039a1] libusbx: debug [linux_get_device_address] scan usb1
[ 0.000740] [000039a1] libusbx: debug [linux_get_device_address] bus=1 dev=1
[ 0.000797] [000039a1] libusbx: debug [linux_enumerate_device] busnum 1 devaddr 1 session_id 257
[ 0.000805] [000039a1] libusbx: debug [linux_enumerate_device] allocating new device for 1/1 (session 257)
[ 0.000881] [000039a1] libusbx: debug [linux_get_device_address] getting address for device: 1-1 detached: 0
[ 0.000938] [000039a1] libusbx: debug [linux_get_device_address] scan 1-1
[ 0.001072] [000039a1] libusbx: debug [linux_get_device_address] bus=1 dev=2
[ 0.001127] [000039a1] libusbx: debug [linux_enumerate_device] busnum 1 devaddr 2 session_id 258
[ 0.001134] [000039a1] libusbx: debug [linux_enumerate_device] allocating new device for 1/2 (session 258)
[ 0.001167] [000039a1] libusbx: debug [linux_get_parent_info] Dev 0x6a82b0 (1-1) has parent 0x6a81f0 (usb1) port 1
[ 0.001273] [000039a1] libusbx: debug [linux_get_device_address] getting address for device: 1-2 detached: 0
[ 0.001330] [000039a1] libusbx: debug [linux_get_device_address] scan 1-2
[ 0.001364] [000039a1] libusbx: debug [linux_get_device_address] bus=1 dev=29
[ 0.001421] [000039a1] libusbx: debug [linux_enumerate_device] busnum 1 devaddr 29 session_id 285
[ 0.001428] [000039a1] libusbx: debug [linux_enumerate_device] allocating new device for 1/29 (session 285)
[ 0.001506] [000039a1] libusbx: debug [linux_get_parent_info] Dev 0x6a8390 (1-2) has parent 0x6a81f0 (usb1) port 2
[ 0.001583] [000039a1] libusbx: debug [usbi_add_pollfd] add fd 6 events 1
[ 0.001594] [000039a1] libusbx: debug [usbi_add_pollfd] add fd 8 events 1
[ 0.001601] [000039a1] libusbx: debug [usbi_io_init] using timerfd for timeouts
[ 0.001606] [000039a1] libusbx: debug [usbi_add_pollfd] add fd 10 events 1
[ 0.001612] [000039a1] libusbx: debug [libusb_get_device_list] 
[ 0.001621] [000039a1] libusbx: debug [libusb_get_device_descriptor] 
[ 0.001631] [000039a1] libusbx: debug [libusb_open] open 1.29
[ 0.001646] [000039a1] libusbx: debug [usbi_add_pollfd] add fd 11 events 4
[ 0.001656] [000039a1] libusbx: debug [libusb_get_configuration] 
[ 0.001671] [000039a1] libusbx: debug [libusb_get_configuration] active config 1
[ 0.001767] [000039a1] libusbx: debug [add_to_flying_list] arm timerfd for timeout in 1000ms (first in line)
[ 0.001829] [000039a1] libusbx: debug [submit_bulk_transfer] need 1 urbs for new transfer with length 8
[ 0.002065] [000039a1] libusbx: debug [libusb_handle_events_timeout_completed] doing our own event handling
[ 0.002134] [000039a1] libusbx: debug [handle_events] poll() 4 fds with timeout in 60000ms
[ 0.014085] [000039a1] libusbx: debug [handle_events] poll() returned 1
[ 0.014136] [000039a1] libusbx: debug [reap_for_handle] urb type=3 status=0 transferred=8
[ 0.014143] [000039a1] libusbx: debug [handle_bulk_completion] handling completion status 0 of bulk urb 1/1
[ 0.014149] [000039a1] libusbx: debug [handle_bulk_completion] last URB in transfer --> complete!
[ 0.014154] [000039a1] libusbx: debug [disarm_timerfd] 
 
  • Up0
  • Down0
joes
Join Date: 28 Jan 16
Posts: 7
Posted: Thu, 2016-06-02 06:25

Found the problem: DB820 has a USB3.0 connector and I actually used it and it works fine with adb.

But fails with mini-dm.  Using a USB2.0 cable works around the problem.

 

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.