CLI for Badgerd SDWire Devices
Application also supports legacy SDWireC and non-Badger'd sdwires as well as new Badgerd SDwire Gen2 devices.
Please see below for usage:
❯ sdwire --help
Usage: sdwire [OPTIONS] COMMAND [ARGS]...
Options:
--help Show this message and exit.
Commands:
list
switch dut/target => connects the sdcard interface to target device
❯ sdwire switch --help
Usage: sdwire switch [OPTIONS] COMMAND [ARGS]...
dut/target => connects the sdcard interface to target device
ts/host => connects the sdcard interface to host machine
off => disconnects the sdcard interface from both host and target
Options:
-s, --serial TEXT Serial number of the sdwire device, if there is only one
sdwire connected then it will be used by default
--help Show this message and exit.
Commands:
dut dut/target => connects the sdcard interface to target device
host ts/host => connects the sdcard interface to host machine
off off => disconnects the sdcard interface from both host and target
target dut/target => connects the sdcard interface to target device
ts ts/host => connects the sdcard interface to host machine
Installing
Using pip
pip install sdwire
Using apt
sudo add-apt-repository ppa:tchavadar/badgerd
sudo apt install python3-sdwire
Listing SDWire Devices
sdwire list command will search through usb devices connected to the system
and prints out the list of gen2 and legacy devices.
❯ sdwire list
Serial Product Info
sdwire_gen2_101 [SDWire-Gen2::Badgerd Technologies]
bdgrd_sdwirec_522 [sd-wire::SRPOL]
Switching SD Card Connection
sdwire switch command switches the sd card connection to specified direction.
If there is more than one sdwire connected to then you need specify which sdwire
you want to alter with --serial or -s options.
If there is only one sdwire connected then you dont need to specify the serial, it will pick the one connected automatically. See the examples below.
❯ sdwire list
Serial Product Info
sdwire_gen2_101 [SDWire-Gen2::Badgerd Technologies]
bdgrd_sdwirec_522 [sd-wire::SRPOL]
❯ sdwire switch -s bdgrd_sdwirec_522 target
❯ sdwire switch target
Usage: sdwire switch [OPTIONS] COMMAND [ARGS]...
Try 'sdwire switch --help' for help.
Error: There is more then 1 sdwire device connected, please use --serial|-s to specify!
❯ sdwire list
Serial Product Info
bdgrd_sdwirec_522 [sd-wire::SRPOL]
❯ sdwire switch host
Metadata
Release files for sdwire 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| sdwire-0.3.1.tar.gz | 25.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sdwire-0.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 53.2 kB
Release files / sdwire-0.3.1.tar.gz
| Download URL | sdwire-0.3.1.tar.gz |
|---|---|
| Size | 25.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b669781a2a9c10accc558a4b523bbd1639f25a729a8755f324f60010526b4183
|
|
BLAKE2b-256 checksum How to use checksums |
3c4d1563b2433fe4d3724c56a245342731970e06b6a85133f024656483203afe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 26, 2025.
Transparency logRelease files / sdwire-0.3.1-py3-none-any.whl
| Download URL | sdwire-0.3.1-py3-none-any.whl |
|---|---|
| Size | 28.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
72493f5423193fe5a1efb26c2aec09e4c4e726c2753e725c25f52a9a60d390b8
|
|
BLAKE2b-256 checksum How to use checksums |
33d2a0c24efe3812b7d0bd7e9f4b1467123847ded047c0712660c28e8c108c45
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 26, 2025.
Transparency log