Intel® Compute Stick
Discussions Regarding Intel® Compute Sticks and Cards
Announcements
All support for Intel® NUC 7 - 13 systems is transitioning to ASUS. Read more.
548 Discussions

STK1AW32SC EMI/ESD crashes USB subsystem

NS4
Beginner
1,804 Views

Hello

I have several Intel Compute Sticks STK1AW32SC (H93326-103 and H93326-104). Running the latest BIOS and x86 Ubuntu server Xenial 16.04.4. I'm using the compute sticks to build a network device that has multiple wifi cards (always in monitor mode) connected through a 4 port hub to the USB 3.0 port. I use the onboard wifi to connect to a local network and the system just does its job, works for months on end, no issues whatsoever.

However, when I disconnect the onboard wifi and add a 3G USB modem to the mix (connected to the USB 2.0 port) I start experiencing USB issues. Every now and then I see messages like "[15775.183824] usb 1-2-port1: disabled by hub (EMI?), re-enabling..." in the kernel log. This can result in one of two scenarios:

  1. The disconnected USB device recovers with no issues and its business as usual
  2. The USB subsystem crashes, the disconnected USB device(s) "fail to enumerate" making USB ports completely unusable

When scenario two occurs, even a system restart does not seem to resolve the issue and human intervention is required to physically unplug and replug (so that the internal circuits discharge?). After which the system boots and starts working normally again until it experiences one of the above two scenarios again.

Troubleshooting done so far:

  • Have tried using different USB cables, hubs, wifi cards, compute sticks and 3 different brands of 3G cards. This means that all hardware is most probably working as designed.
  • Plugged all wifi cards and the 3G modem on a powered USB hub. This setup seems stable, but requires more testing to confirm if this actually works. However, this makes the setup bulky and requires more power sockets and components and so is not ideal at all. (This test may suggest that the powered USB HUB provides Vcc isolation? And could suggest that the ESD transient is simply travelling up the Vcc line???)
  • Have shuffled around the various components in the box to ensure that the devices were not just interfering with each other.
  • I know that USB 3.0 devices can create certain amount of EMR, but none of my USB devices are USB 3.0.
  • All the USB extension cables are shielded and are no longer than 6cm (~2.5 inches long)
  • The EMI issue happens randomly and I have no way of reproducing it on demand, which also makes troubleshooting very hard.

Questions:

Sorry about the long post, I wanted to be very thorough. Thank you for reading and your help in solving this issue!

0 Kudos
3 Replies
AlHill
Super User
418 Views

I know it is not the answer you want to hear, but your OS is not supported on the STK1AW32SC:

https://www.intel.com/content/www/us/en/support/articles/000005899/mini-pcs/intel-compute-sticks.html Supported Operating Systems for Intel® Compute Sticks

Only Windows 10 is supported.

Doc

0 Kudos
NS4
Beginner
418 Views

Oh interesting, thank you for pointing that out. I'm wondering how accurate that page is though? The latest BIOS (0038) on these compute sticks lets you select Android as an operating system to install on the device and Android is not even mentioned on that page.

I'm also curious if an official response from Intel would be similar? Because if so, then this is important information for any business looking to invest in most of Intel compute stick range (and possibly other Intel products) for open source projects.

Anyways, I was simply hoping to draw upon the experience and expertise of this community to troubleshoot a problem that seems like a hardware issue. Appreciate your time

0 Kudos
n_scott_pearson
Super User Retired Employee
418 Views

Let me say it a different way: While it is true that the boot of other O/Ss is supported, Intel Customer Support will only provide support for issues related to Windows.

If you want to see an issue addressed, you essentially have to demonstrate that the issue also occurs with Windows or you debug it to the point where it can be shown that the BIOS is responsible.

...S

0 Kudos
Reply