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

MCU Programmer

The MCU Programmer flashes a .hex, .bin or .elf file onto a microcontroller through the Binho Atira, over SWD at 1 MHz. It needs no project or source code. It is in the desktop app only.

Plug in the Atira, choose it in the bar at the top (Binho Atira · S/N …), then click Connect.

To power the target from the Atira, set Atira supply to the voltage the target needs, from 1.2 V to 5.0 V, and turn the supply on. The Atira then drives that voltage onto pin 1 of the Programming Port: use it only for targets that are not powered through that pin.

The Transaction Log at the bottom has one entry per run, with the part, the file and the result. It can be searched, filtered, copied and exported.

Target lists the parts of the device family pack opened in Mission Control 3; there are no built-in parts. To flash an MCU, click Open pack… and open the vendor’s device family pack for it (.pack or .atpack). Its parts are listed under From your packs, with flash size, address and core. Type in Search targets to filter the list. The pack stays open after a restart; Close pack closes it and empties the list. With no pack open, the list shows a note that links to Install a Device Pack, which says where to get the pack. Device Packs explains what a pack is.

Some parts in a pack are listed as Not supported yet, with the reason, for example a part with several separate flash regions. A part marked Not supported yet: needs vendor connect steps can still be flashed: Mission Control asks before every Flash or Erase, and runs only after Flash at my own risk or Erase at my own risk is clicked.

  • Binary: click Choose… and pick a .hex, .bin or .elf file. A .bin is written at the start of the target’s flash; .hex and .elf files carry their own addresses.
  • Flash writes the file. Verify after flash (on by default, remembered) reads it back afterwards. Reset after flash (on by default) resets the target so the new firmware runs; with it off, the core stays halted at the reset vector.
  • Verify compares the flash with the file and reports a mismatch with its address.
  • Erase erases the whole flash.
  • Reset resets the target and runs it.
  • Flash and Erase arm on the first click (Click again to flash) and run on the second.
  • Wrong MCU: Flash and Erase first check that the MCU connected to the Atira is the part picked. If it is not, or it cannot be identified exactly, nothing is written. Pick the right part or open the right pack. If the pick is certain, type the part name to enable Flash anyway or Erase anyway.
  • Large erase: flash is erased in whole sectors. If that erases much more than the image, or the area before it (where a bootloader may live), Flash shows the range first; Erase and flash goes ahead. Don’t show this again stops the question for that MCU, and Ask before a large erase brings it back.
  • MCU Debugger attached: the Programmer shows Detach debugger. Click it twice to end the debug session, then flash.