Skip to content
binho.io (opens in a new tab)Contact Us

Binho Atira: Setup

This page goes from the box to a halted Cortex-M target. For the full pinout, specifications and more examples, see the Binho Atira overview and its hardware reference.

Connect the Atira’s USB Port to the computer with a USB-C cable. Leave the target unconnected for now.

Open Mission Control 3. The Atira appears under Connected Devices on the home screen, and its MCU Programmer and MCU Debugger tools are in the desktop app. The steps below use PyCosmicSDK to check the connection and the first SWD halt from a script.

PyCosmicSDK drives the Atira from Python. It needs Python 3.10 or newer.

pip install --upgrade pycosmicsdk

On Linux, a udev rule gives the current user access to the Atira (USB ID 1fc9:8347). Without it, DebugProbe.open() fails with DeviceNotFoundError and names the permission problem. Windows and macOS need nothing.

Create /etc/udev/rules.d/65-binho-atira.rules:

sudo nano /etc/udev/rules.d/65-binho-atira.rules

with these lines:

# Binho Atira (HID control)
SUBSYSTEM=="hidraw", ATTRS{idVendor}=="1fc9", ATTRS{idProduct}=="8347", MODE="0660", GROUP="plugdev", TAG+="uaccess"
# Binho Atira (USB: CMSIS-DAP and SPI bulk)
SUBSYSTEM=="usb", ATTRS{idVendor}=="1fc9", ATTRS{idProduct}=="8347", MODE="0660", GROUP="plugdev", TAG+="uaccess"
# Binho Atira bootloader
SUBSYSTEM=="hidraw", ATTRS{idVendor}=="1fc9", ATTRS{idProduct}=="82fe", MODE="0660", GROUP="plugdev", TAG+="uaccess"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1fc9", ATTRS{idProduct}=="82fe", MODE="0660", GROUP="plugdev", TAG+="uaccess"
# Binho Atira UART bridge
SUBSYSTEM=="tty", ATTRS{idVendor}=="1fc9", ATTRS{idProduct}=="8347", TAG+="uaccess"

Reload the rules, then unplug and replug the Atira:

sudo udevadm control --reload-rules && sudo udevadm trigger
from pycosmicsdk import DebugProbe, list_debug_probes
print(list_debug_probes())
with DebugProbe.open() as probe:
info = probe.info
print(f"Serial: {probe.serial_number}")
print(f"Firmware: {info.fw_major}.{info.fw_minor}.{info.fw_patch}")
print(f"UART bridge: {probe.uart().bridge_port or '(not found)'}")
ObservedMeaning
An empty listThe Atira is not on USB. Try another cable or port.
DeviceNotFoundErrorAnother program holds the Atira, or (Linux) the udev rule is missing.

Connect the target’s 10-pin Cortex debug header to the Atira’s Programming Port with a straight (not mirrored) 1.27 mm ribbon: the red stripe goes to pin 1 at both ends.

Programming Port pinSignal
1VDD (target rail, 1.2 to 5.0 V)
2SWDIO
3, 5GND
4SWCLK
10nRESET

Choose how the target is powered:

Powered by the Atira

Leave the target’s own supply (USB, bench supply) disconnected. The Atira powers it through pin 1 of the Programming Port.

Self-powered target

A self-powered target works with pin 1 of the Programming Port left unwired. Power the target before turning the Atira supply on, and turn the Atira supply off before unplugging or swapping the target. The rail must still be switched on in step 6: the Atira’s level shifters need it.

The rail is off when the Atira powers up. Switch it on and check the reading:

import time
from pycosmicsdk import DebugProbe
with DebugProbe.open() as probe:
power = probe.power()
power.set_output(True)
time.sleep(0.5) # the reading lags the switch by ~0.5 s
r = power.reading()
print(f"{r.voltage_mv} mV, {r.current_ua / 1000:.2f} mA")

With the default rail setting, expect about 3300 mV. The current is what the target draws; a NUCLEO-H503RB powered this way draws about 20 mA. If the current is far above what the board should draw, switch the rail off (power.set_output(False)) and check the wiring.

import time
from pycosmicsdk import DebugProbe
with DebugProbe.open() as probe:
probe.power().set_output(True)
time.sleep(0.5)
debug = probe.debug()
debug.attach()
state = debug.halt()
print(f"halted at PC 0x{state.pc:08X}")
print(f"SP = 0x{debug.read_register(13):08X}")
debug.run()
debug.detach()

A PC address inside the target’s flash (for example 0x08xxxxxx on STM32) means SWD works.

If attach() fails:

  • Check that the rail is on and reads the voltage it is set to. With the rail off, SWD cannot connect.
  • Check the cable is straight, not mirrored.
  • If the target board has its own on-board debugger (ST-LINK, MCU-Link), hold it in reset or unpower it so it does not drive SWDIO/SWCLK. On a NUCLEO-H503RB, fit JP1.