LinuxQuestions.org - Trouble mounting my Timex Run Trainer watch

- Linux - Hardware (https://www.linuxquestions.org/questions/linux-hardware-18/)

- - Trouble mounting my Timex Run Trainer watch (https://www.linuxquestions.org/questions/linux-hardware-18/trouble-mounting-my-timex-run-trainer-watch-4175446366/)

Trouble mounting my Timex Run Trainer watch

I have a Timex run trainer watch that is made to work with a TImex Device agent, made for Win.

The watch, when plugged in the USB port in Linux, does not register as a file system (fdisk -l dosen't show it), however it does, when the "lsusb" command is entered, show on the output (

Is it possible to mount the watch as a filesystem somehow? If I install the Device manager in Wine, it runs, but does not register that the watch is plugged in and so I cannot download any data.

Cheers!

Could be a fun RE experiment...

So there's now ay to make it work under a Linux environment, or to mount it as a mass storage device?

There's always a way, it just depends on how much effort you're willing to expend. You could start reading Linux Device Drivers for example .. :)

So what would the procedure to realize the possibilitiy of mounting the watch as a USB stroage device entail? How do I read thsoe drivers, how much prior knowledge is required to make it work?

Hi,

First, please provide the output for 'lsusb' and relative section for 'lspci -vv' along with 'lsmod'. That way we can hopefully help you diagnose the problem.

If you do have a module loaded then use;

Quote:

excerpt from 'man modinfo';
NAME
modinfo - Show information about a Linux Kernel module

SYNOPSIS
modinfo [-0] [-F field] [-k kernel] [modulename|filename...]

modinfo -V

modinfo -h

DESCRIPTION
modinfo extracts information from the Linux Kernel modules given on the command line. If the module name is not a filename, then the
/lib/modules/version directory is searched, as is also done by modprobe(8) when loading kernel modules.

modinfo by default lists each attribute of the module in form fieldname : value, for easy reading. The filename is listed the same way (although it's
not really an attribute).

This version of modinfo can understand modules of any Linux Kernel architecture.

OPTIONS
-V --version
Print the modinfo version.

-F --field
Only print this field value, one per line. This is most useful for scripts. Field names are case-insensitive. Common fields (which may not be in
every module) include author, description, license, parm, depends, and alias. There are often multiple parm, alias and depends fields. The special
field filename lists the filename of the module.

-k kernel
Provide information about a kernel other than the running one. This is particularly useful for distributions needing to extract information from a
newly installed (but not yet running) set of kernel modules. For example, you wish to find which firmware files are needed by various modules in a
new kernel for which you must make an initrd/initramfs image prior to booting.

-0 --null
Use the ASCII zero character to separate field values, instead of a new line. This is useful for scripts, since a new line can theoretically appear
inside a field.

-a -d -l -p -n
These are shortcuts for author, description, license. parm and filename respectively, to ease the transition from the old modutils modinfo.

Please look at the following FYIs' to help you with future posts;

Quote:

FYI: Netiquette is a set of social conventions that facilitate interaction over networks, ranging from Usenet and mailing lists to blogs and forums.

FYI: I suggest that you look at 'How to Ask Questions the Smart Way' so in the future your queries provide information that will aid us in diagnosis of the problem or query.

Plus;

Quote:

"Knowledge is of two kinds. We Know a subject ourselves, or we know where we can find information upon it."- Samuel Johnson

“A tool is but the extension of a man's hand and a machine is but a complex tool. He that invents a machine augments the power of man and the well being of mankind.” - Henry Ward Beecher

“Man is a tool-using animal.”- Carlyle

HTH!

I would say that getting the watch to work with WINE might be a long shot.

http://wine-wiki.org/index.php/Drivers#USB_drivers
http://wiki.winehq.org/USB

The two most common USB protocols are USB storage and MTP typically used by MP3 players and cameras. However there are many devices that use proprietary protocols and without any way to access them natively from within linux. I've never tried but
but you would need to reverse engineer the watches communication protocol. There are many articles that can be found by searching like the following. Using libusb to write the driver and create a fuse file system so the watch can be mounted like a USB storage device.

http://matthias.vallentin.net/blog/2...wn-usb-device/

Thank you for all your answers, I will try to post all the relevant info tomorrow, when I'll finally have some free time on my hands. I'm already looking forward to what you will make of it.

michaelk: I tried installing the Timex device agent through Wine and everything worked ... except recognizing the watch, that is - I was checking out the links you provided and it seems that the only way of possibly making it work would be to snatch the files from the Win registry?
Note that even in Windows, Timex cannot be used as a Mass storage device (in contrast to Garmin), it just downloads files through the Device agent software

Here are outputs from the lsusb, dmesg, syslog and others:

Quote:

lsusb:
Bus 006 Device 004: ID 0cc2:d702 Timex Corp.

syslog:
Jan 27 19:26:20 xxxx kernel: [22674.536112] usb 6-1: new full-speed USB device number 4 using uhci_hcd
Jan 27 19:26:20 xxxx kernel: [22674.719829] usb 6-1: New USB device found, idVendor=0cc2, idProduct=d702
Jan 27 19:26:20 xxxx kernel: [22674.719837] usb 6-1: New USB device strings: Mfr=2, Product=3, SerialNumber=0
Jan 27 19:26:20 xxxx kernel: [22674.719843] usb 6-1: Product: Timex Ironman Run Trainer GPS Watch
Jan 27 19:26:20 xxxx kernel: [22674.719847] usb 6-1: Manufacturer: Timex Corporation
Jan 27 19:26:20 xxxx mtp-probe: checking bus 6, device 4: "/sys/devices/pci0000:00/0000:00:1d.0/usb6/6-1"
Jan 27 19:26:20 xxxx mtp-probe: bus: 6, device: 4 was not an MTP device
Jan 27 19:26:20 xxxx kernel: [22674.731000] hid-generic 0003:0CC2:D702.0004: hiddev0,hidraw0: USB HID v1.11 Device [Timex Corporation Timex Ironman Run Trainer GPS Watch] on usb-0000:00:1d.0-1/input0

fdisk -l; blkid -o list -c /dev/null:
returns nothing which would pertain to the watch.

dmesg|grep Timex:
[ 1.751212] usb 6-1: Product: Timex Ironman Run Trainer GPS Watch
[ 1.751216] usb 6-1: Manufacturer: Timex Corporation
[ 2.303403] hid-generic 0003:0CC2:D702.0001: hiddev0,hidraw0: USB HID v1.11 Device [Timex Corporation Timex Ironman Run Trainer GPS Watch] on usb-0000:00:1d.0-1/input0
[22529.651141] usb 6-1: Product: Timex Ironman Run Trainer GPS Watch
[22529.651146] usb 6-1: Manufacturer: Timex Corporation
[22529.662286] hid-generic 0003:0CC2:D702.0003: hiddev0,hidraw0: USB HID v1.11 Device [Timex Corporation Timex Ironman Run Trainer GPS Watch] on usb-0000:00:1d.0-1/input0
[22674.719843] usb 6-1: Product: Timex Ironman Run Trainer GPS Watch
[22674.719847] usb 6-1: Manufacturer: Timex Corporation
[22674.731000] hid-generic 0003:0CC2:D702.0004: hiddev0,hidraw0: USB HID v1.11 Device [Timex Corporation Timex Ironman Run Trainer GPS Watch] on usb-0000:00:1d.0-1/input0

I have also checked the Timex/TrainingPeaks folder on my windows partition. In the TimexDrivers folder there are files:
DPInstx64.exe DPInstx86.exe TimeCycleTrainer.inf TimexGlobalTrainer.inf

The TimexGlobalTrainer.inf file reads:

Quote:

;
; STMicroelectronics Comunication Device Class driver instalation file
; (C)2006 Copyright STMicroelectronics
;

[Version]
Signature="$Windows NT$"
Class=Ports
ClassGuid={4D36E978-E325-11CE-BFC1-08002BE10318}
Provider=%STM%
LayoutFile=layout.inf

[Manufacturer]
%MFGNAME%=VirComDevice,NT,NTamd64

[DestinationDirs]
DefaultDestDir = 12

[VirComDevice.NT]
%DESCRIPTION%=DriverInstall,USB\VID_0483&PID_5740

[VirComDevice.NTamd64]
%DESCRIPTION%=DriverInstall,USB\VID_0483&PID_5740

[DriverInstall.NT]
Include=mdmcpq.inf
CopyFiles=FakeModemCopyFileSection
AddReg=DriverInstall.NT.AddReg

[DriverInstall.NT.AddReg]
HKR,,DevLoader,,*ntkern
HKR,,NTMPDriver,,usbser.sys
HKR,,EnumPropPages32,,"MsPorts.dll,SerialPortPropPageProvider"

[DriverInstall.NT.Services]
AddService=usbser, 0x00000002, DriverServiceInst

[DriverServiceInst]
DisplayName=%SERVICE%
ServiceType=1
StartType=3
ErrorControl=1
ServiceBinary=%12%\usbser.sys

;------------------------------------------------------------------------------
; String Definitions
;------------------------------------------------------------------------------

[Strings]
STM = "STMicroelectronics"
MFGNAME = "STMicroelectronics"
SERVICE = "USB Virtual COM port"
DESCRIPTION = "Timex Global Trainer"

In the Devices folder, the files are:
brandtx.dll qextserialport.dll timexm242.dll
pwxbrowse.dll timexm229.dll timexm878.dll

Does this info help in any way?

p.s.: Sorry for the smileys in the output, I don't know how to disable emoticons here. Obvisouly the big grin means, that the characters there are : and D

React OS via QEMU

I will try using a QEMU / Vbox VM with React OS
I am unfortunately not quite good at writing drivers (I rather suck massively, lol) so that I am going to use this approach.

but I will keep an eye on this thread, if somebody knows how to make the stuff run using the Wind DLLs it would be awesome.
My Timex is in fact the only reason that I keep a version of Win7 on my hard drive.

It seems that we Linux people aren't too much into sports :(
(I am ultra-runner, BTW).

We will have to work on that. First stop getting my Garmin running... and else... who cares, we have been keeping track of our times using chronometers for decades.

If your watch uses Timex Datalink software, wine reports that that runs well under wine.
https://appdb.winehq.org/objectManag...cation&iId=939