Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Power-cycling a USB port should be simple, right? (2017)

laforge.gnumonks.org

Post reply on HN
Print view View original

11–16 of 16 posts

Re: Power-cycling a USB port should be simple, right? (2017)

#11

Post by d-sc »

ursaspark wrote: post #7
dxld wrote: post #4

Earlier quoted context omitted.

Took me a while to find this again, but here you go: https://www.yepkit.com/product/300110/YKUSH3 , a 3-port USB 3.1 Hub with switchable Vbus that doesn't cost an arm and a leg.

we use these in our CI/CD pipelines as we deal with embedded hardware. they work absolutely awesome for power cycling stuck USB peripherals or powering USB-powered boards for tests.

I’me working on an embedded project and would like to setup a CI/CD pipeline. Do you have any recommended resources?

Re: Power-cycling a USB port should be simple, right? (2017)

#13

Post by dingaling »

banana_giraffe wrote: post #3

I had a need to test the insert/remove a whole bunch for a while. Because the timing worked out, I ended up getting a programmable USB hub [1]. It worked well for my needs, but I'm not sure I'd trust it enough for a really inaccessible location. I do wish I could find a not stupid priced version of this concept that does USB 3.1 [1] https://capablerobot.com/products/programmable-usb-hub/

Pegasus Astro make a switchable six-port USB3.1 hub which is suitable for very wide temperature range. Costs about 200 Euro:

https://pegasusastro.com/products/usb-control-hub/

Re: Power-cycling a USB port should be simple, right? (2017)

#14

Post by londons_explore »

If the system is well designed, this power cycle should be a rare event (ie. maybe once per year).

For that rare event, it doesn't seem worth writing code to power cycle a single USB peripheral (and then write and test all the code to clear the error states at each level of the stack and bring that peripheral back up again).

Instead, power cycle the entire system. Have a small hardware watchdog which, when not being tickled, will power off the whole system for 5 seconds and power everything back on.

Write code to periodically tickle the hardware watchdog when everything is 100% healthy, or when 3 reboots have happened in short succession (you'd prefer the system up with 90% of the hardware working than bootlooping).

Re: Power-cycling a USB port should be simple, right? (2017)

#15

Post by pakesson »

d-sc wrote: post #11
ursaspark wrote: post #7

Earlier quoted context omitted.

we use these in our CI/CD pipelines as we deal with embedded hardware. they work absolutely awesome for power cycling stuck USB peripherals or powering USB-powered boards for tests.

I’me working on an embedded project and would like to setup a CI/CD pipeline. Do you have any recommended resources?

There was a presentation about CI/CD for embedded systems at HITB+CyberWeek a couple of days ago: https://cyberweek.ae/2020/ci-cd-with-sast-and-dast-for-embed...

A recording can be found here: https://www.youtube.com/watch?v=nFytbVFMLfA

Re: Power-cycling a USB port should be simple, right? (2017)

#16

Post by d-sc »

pakesson wrote: post #15
d-sc wrote: post #11

Earlier quoted context omitted.

I’me working on an embedded project and would like to setup a CI/CD pipeline. Do you have any recommended resources?

There was a presentation about CI/CD for embedded systems at HITB+CyberWeek a couple of days ago: https://cyberweek.ae/2020/ci-cd-with-sast-and-dast-for-embed... A recording can be found here: https://www.youtube.com/watch?v=nFytbVFMLfA

Thanks!
Post reply on HN