Skip to contentSkip to conversation

problems with Edgeport/416

DISCUSSION walter harms 3 participants 6 messages Aug 21, 2019 – Aug 23, 2019 6 messages not in the archive USB

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#4 lore raw

Am 21.08.2019 14:20, schrieb Greg KH:

Quoted 43 lines · walter harms
Quoted 42 lines

Am 21.08.2019 13:20, schrieb Greg KH:

Quoted 39 lines · walter harms
Quoted 27 lines

Hello List,
does some use linux with an Edgeport/416 ?

I have a strange problem. the device is resetting soon after i started using it (but not immediately). I do not see a kernel OOPS but a common pattern is:

2019-08-20T15:19:39.825812+00:00 omnfrmo10 kernel: [683270.658623] usb 7-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2019-08-20T15:19:39.825818+00:00 omnfrmo10 kernel: [683270.658626] usb 7-1.1.2: Product: Edgeport/416
2019-08-20T15:19:39.825821+00:00 omnfrmo10 kernel: [683270.658628] usb 7-1.1.2: Manufacturer: Digi International
2019-08-20T15:19:39.825823+00:00 omnfrmo10 kernel: [683270.658630] usb 7-1.1.2: SerialNumber: E63966100-1
2019-08-20T15:19:39.985571+00:00 omnfrmo10 kernel: [683270.817909] usb 7-1.1.2: Edgeport TI 2 port adapter converter now attached to ttyUSB4
2019-08-20T15:19:39.985594+00:00 omnfrmo10 kernel: [683270.818132] usb 7-1.1.2: Edgeport TI 2 port adapter converter now attached to ttyUSB5
2019-08-20T15:19:40.007943+00:00 omnfrmo10 mtp-probe: checking bus 7, device 88: "/sys/devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1.1/7-1.1.2"
2019-08-20T15:19:40.053750+00:00 omnfrmo10 kernel: [683270.885626] usb 7-1.2.2: New USB device found, idVendor=1608, idProduct=0247
2019-08-20T15:19:40.053791+00:00 omnfrmo10 kernel: [683270.885630] usb 7-1.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2019-08-20T15:19:40.053797+00:00 omnfrmo10 kernel: [683270.885633] usb 7-1.2.2: Product: Edgeport/416
2019-08-20T15:19:40.053800+00:00 omnfrmo10 kernel: [683270.885635] usb 7-1.2.2: Manufacturer: Digi International
2019-08-20T15:19:40.053803+00:00 omnfrmo10 kernel: [683270.885637] usb 7-1.2.2: SerialNumber: E63966100-5
2019-08-20T15:19:40.065569+00:00 omnfrmo10 kernel: [683270.897406] usb 7-1.1.3: new full-speed USB device number 90 using uhci_hcd
2019-08-20T15:19:40.213569+00:00 omnfrmo10 kernel: [683271.046316] usb 7-1.2.2: Edgeport TI 2 port adapter converter now attached to ttyUSB6
2019-08-20T15:19:40.213594+00:00 omnfrmo10 kernel: [683271.046782] usb 7-1.2.2: Edgeport TI 2 port adapter converter now attached to ttyUSB7
2019-08-20T15:19:40.242034+00:00 omnfrmo10 mtp-probe: checking bus 7, device 89: "/sys/devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1.2/7-1.2.2"
2019-08-20T15:19:40.301578+00:00 omnfrmo10 kernel: [683271.133380] usb 7-1.2.3: new full-speed USB device number 91 using uhci_hcd
2019-08-20T15:19:40.357559+00:00 omnfrmo10 kernel: [683271.192815] usb 7-1.1.3: New USB device found, idVendor=1608, idProduct=0247
2019-08-20T15:19:40.357584+00:00 omnfrmo10 kernel: [683271.192820] usb 7-1.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2019-08-20T15:19:40.357588+00:00 omnfrmo10 kernel: [683271.192822] usb 7-1.1.3: Product: Edgeport/416
Quoted 8 lines
2019-08-20T15:19:40.357591+00:00 omnfrmo10 kernel: [683271.192825] usb 7-1.1.3: Manufacturer: Digi International
2019-08-20T15:19:40.357593+00:00 omnfrmo10 kernel: [683271.192827] usb 7-1.1.3: SerialNumber: E63966100-2
2019-08-20T15:19:40.513702+00:00 omnfrmo10 kernel: [683271.349103] usb 7-1.1.3: Edgeport TI 2 port adapter converter now attached to ttyUSB8
2019-08-20T15:19:40.513725+00:00 omnfrmo10 kernel: [683271.349311] usb 7-1.1.3: Edgeport TI 2 port adapter converter now attached to ttyUSB9
2019-08-20T15:19:40.537138+00:00 omnfrmo10 mtp-probe: checking bus 7, device 90: "/sys/devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1.1/7-1.1.3"
2019-08-20T15:19:40.601754+00:00 omnfrmo10 kernel: [683271.433389] usb 7-1.1.4: new full-speed USB device number 92 using uhci_hcd
2019-08-20T15:19:40.601794+00:00 omnfrmo10 kernel: [683271.433631] usb 7-1.2.3: New USB device found, idVendor=1608, idProduct=0247
2019-08-20T15:19:40.601798+00:00 omnfrmo10 kernel: [683271.433634] usb 7-1.2.3: New USB device strings: Mfr=1, Produc

I don't see any errors there. What is the problem with the device?

Quoted 9 lines
Quoted 3 lines

You use it, it resets (ports gone etc) and appears again. I suspected that the device is broken but i test today with windows (and a different computer) showed it works fine.

Different computer? Did you try windows on the same exact machine with same exact cable? This sounds like a hardware program, if the device disconnects,there's nothing the software can do about that, it's a hardware / electrical thing.

Different computer but same cables i guess the device is ok.

NTL I found that little gem:
https://www.fclose.com/linux-kernels/594677/usb-io_ti-add-heartbeat-to-keep-idle-ep-416-ports-from-disconnecting-linux-4-3/

The behavior would fit (any way to check that the heartbeat is active ?).

Casten Schmidt ask me to look into /sys/kernel/debug/dynamic_debug/control before i start to
debug the whole usb part, is that below expected behavior ? (i tried to find what version of edgeport the driver suspects).

drivers/usb/serial/io_ti.c:1507 [io_ti]do_boot_mode =_ "%s - STAYING IN BOOT MODE\012" drivers/usb/serial/io_ti.c:1500 [io_ti]do_boot_mode =_ "%s - Download successful -- Device rebooting...\012" drivers/usb/serial/io_ti.c:1493 [io_ti]do_boot_mode =_ "%s - Error downloading operational code image\012" drivers/usb/serial/io_ti.c:1487 [io_ti]do_boot_mode =_ "%s - Downloading operational code image version %d.%d (TI UMP)\012" drivers/usb/serial/io_ti.c:1440 [io_ti]do_boot_mode =_ "%s - Wrong CPU Rev %d (Must be 2)\012" drivers/usb/serial/io_ti.c:1403 [io_ti]do_boot_mode =_ "%s - VID = 0x%x\012" drivers/usb/serial/io_ti.c:1393 [io_ti]do_boot_mode =_ "%s - RUNNING IN BOOT MODE\012" drivers/usb/serial/io_ti.c:1367 [io_ti]do_download_mode =_ "%s - Update complete 0x%x\012" drivers/usb/serial/io_ti.c:1358 [io_ti]do_download_mode =_ "%s - Start firmware update\012" drivers/usb/serial/io_ti.c:1347 [io_ti]do_download_mode =_ "%s - write download record failed\012" drivers/usb/serial/io_ti.c:1338 [io_ti]do_download_mode =_ "%s - can't read header back\012" drivers/usb/serial/io_ti.c:1291 [io_ti]do_download_mode =_ "%s - Found Type BLANK FIRMWARE (Type F2) record\012" drivers/usb/serial/io_ti.c:1252 [io_ti]do_download_mode =_ "%s - HARDWARE RESET return %d\012" drivers/usb/serial/io_ti.c:1243 [io_ti]do_download_mode =_ "%s - HARDWARE RESET\012" drivers/usb/serial/io_ti.c:1178 [io_ti]do_download_mode =_ "%s - Update I2C dld from %d.%d to %d.%d\012" drivers/usb/serial/io_ti.c:1166 [io_ti]do_download_mode =_ "%s - >> FW Versions Device %d.%d Driver %d.%d\012" drivers/usb/serial/io_ti.c:1129 [io_ti]do_download_mode =_ "%s - Found Type FIRMWARE (Type 2) record\012" drivers/usb/serial/io_ti.c:1110 [io_ti]do_download_mode =_ "%s - Wrong CPU Rev %d (Must be 2)\012" drivers/usb/serial/io_ti.c:1089 [io_ti]do_download_mode =_ "%s - DOWNLOAD MODE -- BAD I2C\012" drivers/usb/serial/io_ti.c:1085 [io_ti]do_download_mode =_ "%s - RUNNING IN DOWNLOAD MODE\012" drivers/usb/serial/io_ti.c:906 [io_ti]i2c_type_bootmode =_ "%s - Unknown\012" drivers/usb/serial/io_ti.c:901 [io_ti]i2c_type_bootmode =_ "%s - ROM_TYPE_III\012" drivers/usb/serial/io_ti.c:899 [io_ti]i2c_type_bootmode =_ "%s - read 2 data = 0x%x\012" drivers/usb/serial/io_ti.c:897 [io_ti]i2c_type_bootmode =_ "%s - read 3 status error = %d\012" drivers/usb/serial/io_ti.c:888 [io_ti]i2c_type_bootmode =_ "%s - ROM_TYPE_II\012" drivers/usb/serial/io_ti.c:886 [io_ti]i2c_type_bootmode =_ "%s - read 2 data = 0x%x\012" drivers/usb/serial/io_ti.c:884 [io_ti]i2c_type_bootmode =_ "%s - read 2 status error = %d\012"

re,
wh

#5 lore raw
Quoted 3 lines

Different computer but same cables i guess the device is ok.

But maybe the USB port of the computer is broken.

Quoted 6 lines

NTL I found that little gem:
https://www.fclose.com/linux-kernels/594677/usb-io_ti-add-heartbeat-to-
keep-idle-ep-416-ports-from-disconnecting-linux-4-3/

The behavior would fit (any way to check that the heartbeat is active ?).

Which kernel are you running on?
use "uname -a" to get it.
This patch was introduced in 4.3 kernel, not really hot ... And, yes, looks like what you experience.

Quoted 6 lines

Casten Schmidt ask me to look into /sys/kernel/debug/dynamic_debug/control before i start to
debug the whole usb part, is that below expected behavior ? (i tried to find what version of edgeport the driver suspects).

drivers/usb/serial/io_ti.c:1507 [io_ti]do_boot_mode =_ "%s - STAYING IN BOOT MODE\012"

...

Quoted 2 lines

drivers/usb/serial/io_ti.c:884 [io_ti]i2c_type_bootmode =_ "%s - read 2 status error = %d\012"

That says that we have dynamic debug messages available for the driver. If you enable those by doing
echo -n 'module io_ti =p' > /sys/kernel/debug/dynamic_debug/control

Then you should see at least some of those messages appear in dmesg (kernel log).

Best regards
Carsten

#6 lore raw

Am 21.08.2019 15:20, schrieb Schmid, Carsten:

Quoted 9 lines
Quoted 3 lines

Different computer but same cables i guess the device is ok.

But maybe the USB port of the computer is broken.

Quoted 4 lines

NTL I found that little gem:
https://www.fclose.com/linux-kernels/594677/usb-io_ti-add-heartbeat-to-
keep-idle-ep-416-ports-from-disconnecting-linux-4-3/

Quoted 7 lines
Quoted 2 lines

The behavior would fit (any way to check that the heartbeat is active ?).

Which kernel are you running on?
use "uname -a" to get it.
This patch was introduced in 4.3 kernel, not really hot ... And, yes, looks like what you experience.

mea culpa, i had a typo in the first msg to greg so you did not see my first post:

I tested with: Opensuse 15.1 on a DELL latitude E5400

uname -a
Linux omnfrmo10 4.12.14-lp151.28.10-vanilla #1 SMP Sat Jul 13 17:59:31 UTC 2019 (0ab03b7) x86_64 x86_64 x86_64 GNU/Linux

I did some experiments (changing cables etc) but always the same. But when tested with a windows system it worked all fine. later i used a single port USB->Serial and all worked as expected.

Quoted 6 lines
Quoted 6 lines

Casten Schmidt ask me to look into /sys/kernel/debug/dynamic_debug/control before i start to
debug the whole usb part, is that below expected behavior ? (i tried to find what version of edgeport the driver suspects).

drivers/usb/serial/io_ti.c:1507 [io_ti]do_boot_mode =_ "%s - STAYING IN BOOT MODE\012"

Quoted 9 lines

...

Quoted 2 lines

drivers/usb/serial/io_ti.c:884 [io_ti]i2c_type_bootmode =_ "%s - read 2 status error = %d\012"

That says that we have dynamic debug messages available for the driver. If you enable those by doing
echo -n 'module io_ti =p' > /sys/kernel/debug/dynamic_debug/control

Then you should see at least some of those messages appear in dmesg (kernel log).

i see a lot, see attached file

#7 lore raw
Quoted 5 lines

uname -a
Linux omnfrmo10 4.12.14-lp151.28.10-vanilla #1 SMP Sat Jul 13 17:59:31 UTC
2019 (0ab03b7) x86_64 x86_64 x86_64 GNU/Linux

4.12.14 - it should have the heartbeat patch introduced in 4.3

Quoted 1 line

i see a lot, see attached file

The dyndbg for the driver is active :-)

The log you sent does not show something irregular.
Can you collect the log "around a device reset" in the same way please?

Best regards
Carsten

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#10 lore raw

Am 21.08.2019 16:24, schrieb Schmid, Carsten:

Quoted 9 lines
Quoted 3 lines

this should it be,

Suspicious: line 141 of the log:

[765647.193393] usb 7-1.1.2: reset full-speed USB device number 15 using uhci_hcd

Can you please collect another log around reset, additionally enabling uhci dyndbg using echo -n 'module uhci_hcd =p' > /sys/kernel/debug/dynamic_debug/control

Just to close the problem:
I have installed the Edgeport/416 on a different pc

Linux 4.12.14-lp150.12.25-default #1 SMP Thu Nov 1 06:14:23 UTC 2018 (3fcf457) x86_64 x86_64 x86_64 GNU/Linux With opensuse 15.0

the one with the problem was:
Linux 4.12.14-lp151.28.10-vanilla #1 SMP Sat Jul 13 17:59:31 UTC 2019 (0ab03b7) x86_64 x86_64 x86_64 GNU/Linux

the far the device works as expected (to my surprise). So it seems to be a broken USB, why it fails with the edgeport but not with the pl2303 (usb->rs232 someone) i used for comparison; no idea.

sorry for the noise,

re,
wh

maintainer
#11 lore raw
In reply to walter harms
Quoted 50 lines · walter harms

Am 21.08.2019 14:20, schrieb Greg KH:

Quoted 47 lines · walter harms
Quoted 45 lines

Am 21.08.2019 13:20, schrieb Greg KH:

Quoted 37 lines · walter harms
Quoted 27 lines

Hello List,
does some use linux with an Edgeport/416 ?

I have a strange problem. the device is resetting soon after i started using it (but not immediately). I do not see a kernel OOPS but a common pattern is:

2019-08-20T15:19:39.825812+00:00 omnfrmo10 kernel: [683270.658623] usb 7-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2019-08-20T15:19:39.825818+00:00 omnfrmo10 kernel: [683270.658626] usb 7-1.1.2: Product: Edgeport/416
2019-08-20T15:19:39.825821+00:00 omnfrmo10 kernel: [683270.658628] usb 7-1.1.2: Manufacturer: Digi International
2019-08-20T15:19:39.825823+00:00 omnfrmo10 kernel: [683270.658630] usb 7-1.1.2: SerialNumber: E63966100-1
2019-08-20T15:19:39.985571+00:00 omnfrmo10 kernel: [683270.817909] usb 7-1.1.2: Edgeport TI 2 port adapter converter now attached to ttyUSB4
2019-08-20T15:19:39.985594+00:00 omnfrmo10 kernel: [683270.818132] usb 7-1.1.2: Edgeport TI 2 port adapter converter now attached to ttyUSB5
2019-08-20T15:19:40.007943+00:00 omnfrmo10 mtp-probe: checking bus 7, device 88: "/sys/devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1.1/7-1.1.2"
2019-08-20T15:19:40.053750+00:00 omnfrmo10 kernel: [683270.885626] usb 7-1.2.2: New USB device found, idVendor=1608, idProduct=0247
2019-08-20T15:19:40.053791+00:00 omnfrmo10 kernel: [683270.885630] usb 7-1.2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2019-08-20T15:19:40.053797+00:00 omnfrmo10 kernel: [683270.885633] usb 7-1.2.2: Product: Edgeport/416
2019-08-20T15:19:40.053800+00:00 omnfrmo10 kernel: [683270.885635] usb 7-1.2.2: Manufacturer: Digi International
2019-08-20T15:19:40.053803+00:00 omnfrmo10 kernel: [683270.885637] usb 7-1.2.2: SerialNumber: E63966100-5
2019-08-20T15:19:40.065569+00:00 omnfrmo10 kernel: [683270.897406] usb 7-1.1.3: new full-speed USB device number 90 using uhci_hcd
2019-08-20T15:19:40.213569+00:00 omnfrmo10 kernel: [683271.046316] usb 7-1.2.2: Edgeport TI 2 port adapter converter now attached to ttyUSB6
2019-08-20T15:19:40.213594+00:00 omnfrmo10 kernel: [683271.046782] usb 7-1.2.2: Edgeport TI 2 port adapter converter now attached to ttyUSB7
2019-08-20T15:19:40.242034+00:00 omnfrmo10 mtp-probe: checking bus 7, device 89: "/sys/devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1.2/7-1.2.2"
2019-08-20T15:19:40.301578+00:00 omnfrmo10 kernel: [683271.133380] usb 7-1.2.3: new full-speed USB device number 91 using uhci_hcd
2019-08-20T15:19:40.357559+00:00 omnfrmo10 kernel: [683271.192815] usb 7-1.1.3: New USB device found, idVendor=1608, idProduct=0247
2019-08-20T15:19:40.357584+00:00 omnfrmo10 kernel: [683271.192820] usb 7-1.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2019-08-20T15:19:40.357588+00:00 omnfrmo10 kernel: [683271.192822] usb 7-1.1.3: Product: Edgeport/416
Quoted 8 lines
2019-08-20T15:19:40.357591+00:00 omnfrmo10 kernel: [683271.192825] usb 7-1.1.3: Manufacturer: Digi International
2019-08-20T15:19:40.357593+00:00 omnfrmo10 kernel: [683271.192827] usb 7-1.1.3: SerialNumber: E63966100-2
2019-08-20T15:19:40.513702+00:00 omnfrmo10 kernel: [683271.349103] usb 7-1.1.3: Edgeport TI 2 port adapter converter now attached to ttyUSB8
2019-08-20T15:19:40.513725+00:00 omnfrmo10 kernel: [683271.349311] usb 7-1.1.3: Edgeport TI 2 port adapter converter now attached to ttyUSB9
2019-08-20T15:19:40.537138+00:00 omnfrmo10 mtp-probe: checking bus 7, device 90: "/sys/devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1.1/7-1.1.3"
2019-08-20T15:19:40.601754+00:00 omnfrmo10 kernel: [683271.433389] usb 7-1.1.4: new full-speed USB device number 92 using uhci_hcd
2019-08-20T15:19:40.601794+00:00 omnfrmo10 kernel: [683271.433631] usb 7-1.2.3: New USB device found, idVendor=1608, idProduct=0247
2019-08-20T15:19:40.601798+00:00 omnfrmo10 kernel: [683271.433634] usb 7-1.2.3: New USB device strings: Mfr=1, Produc
Quoted 2 lines

I don't see any errors there. What is the problem with the device?

You use it, it resets (ports gone etc) and appears again. I suspected that the device is broken but i test today with windows (and a different computer) showed it works fine.

Quoted 7 lines
Quoted 5 lines

Different computer? Did you try windows on the same exact machine with same exact cable? This sounds like a hardware program, if the device disconnects,there's nothing the software can do about that, it's a hardware / electrical thing.

Different computer but same cables i guess the device is ok.

So the device works, but the connection to your other computer probably does not. I'm betting this is an electrical issue :)

thanks,

greg k-h