Over the course of three months and two PCB revisions, Codethink developed a USB 3 switch (See Image) in order to address issues regarding software deployment and continuous integration faced by one of our major customers.
The aim was to deliver a computer-controlled, automated deployment pipeline for testing software on actual target hardware, without reliance on human interaction for flashing or power-cycling of target hardware.
The board, designed by Codethink, features two SuperSpeed USB 3 host ports and a single USB 3 device port, alongside another USB 2 host control port for programmatically controlling which of the two USB 3 host is connected to the device. The control port is also capable of selecting which host powers the device, and configuring numerous banks of GPIO for other automation.
Design for USB 3 requires more attention to detail than USB 2, due to the higher speed digital signals involved with USB 3.
The main challenge faced in development of the USB 3 switch is making sure that care is given for all USB 3 transmission lines to avoid as much noise as possible. In order to meet these challenges, Codethink used FOSS KiCAD software. This was used for schematic capture and PCB layout. The tools available for differential routing and track length matching were used in order to make sure that transmission lines were treated carefully and detail was maintained. Research was also conducted into transmission line theory to further understand techniques that are involved in mitigating complications arising from such high speed digital systems.
Other Content
- Codethink/Arm White Paper: Arm STLs at Runtime on Linux
- Speed Up Embedded Software Testing with QEMU
- Open Source Summit Europe (OSSEU) 2024
- Watch: Real-time Scheduling Fault Simulation
- Improving systemd’s integration testing infrastructure (part 2)
- Meet the Team: Laurence Urhegyi
- A new way to develop on Linux - Part II
- Shaping the future of GNOME: GUADEC 2024
- Developing a cryptographically secure bootloader for RISC-V in Rust
- Meet the Team: Philip Martin
- Improving systemd’s integration testing infrastructure (part 1)
- A new way to develop on Linux
- RISC-V Summit Europe 2024
- Safety Frontier: A Retrospective on ELISA
- Codethink sponsors Outreachy
- The Linux kernel is a CNA - so what?
- GNOME OS + systemd-sysupdate
- Codethink has achieved ISO 9001:2015 accreditation
- Outreachy internship: Improving end-to-end testing for GNOME
- Lessons learnt from building a distributed system in Rust
- FOSDEM 2024
- QAnvas and QAD: Streamlining UI Testing for Embedded Systems
- Outreachy: Supporting the open source community through mentorship programmes
- Using Git LFS and fast-import together
- Testing in a Box: Streamlining Embedded Systems Testing
- SDV Europe: What Codethink has planned
- How do Hardware Security Modules impact the automotive sector? The final blog in a three part discussion
- How do Hardware Security Modules impact the automotive sector? Part two of a three part discussion
- How do Hardware Security Modules impact the automotive sector? Part one of a three part discussion
- Automated Kernel Testing on RISC-V Hardware
- Automated end-to-end testing for Android Automotive on Hardware
- GUADEC 2023
- Embedded Open Source Summit 2023
- RISC-V: Exploring a Bug in Stack Unwinding
- Adding RISC-V Vector Cryptography Extension support to QEMU
- Introducing Our New Open-Source Tool: Quality Assurance Daemon
- Achieving Long-Term Maintainability with Open Source
- FOSDEM 2023
- Think before you Pip
- BuildStream 2.0 is here, just in time for the holidays!
- A Valuable & Comprehensive Firmware Code Review by Codethink
- GNOME OS & Atomic Upgrades on the PinePhone
- Flathub-Codethink Collaboration
- Codethink proudly sponsors GUADEC 2022
- Tracking Down an Obscure Reproducibility Bug in glibc
- Web app test automation with `cdt`
- FOSDEM Testing and Automation talk
- Protecting your project from dependency access problems
- Full archive