Version 28
    MCU/MPU/DSP > Development Platforms & Kits > General Accessories >
    Beaglebone mikroBUS Cape
    Technical Docs
    Product Brief/Fact sheet


    The BeagleBone mikroBUS Cape allows users to connect up to four MikroElektronika Click boards to the BeagleBone and BeagleBone Black host platforms. There are over 70 Click Boards to choose from and the list is expanding.


    The BeagleBone mikroBUS Cape works only with Click boards that require 3.3V power


    • Space for connecting up to 4 mikroE Click Boards
    • DIP Switch to select up to four addresses and allow simultaneous use of other Capes

    Ships With

    • BeagleBone mikroBUS Cape


    How do I enable the adaptor board under the Angstrom O/S?
    Getting Started - Angstrom
    1. Download a fresh image: (Angstrom Linux)
    2. Flash an SD Card with that image.
    3. Keep the SD Card in your PC and open the uEnv.txt found in the first partition of the SD Card.
    4. Change the Argument from:
    optargs=quiet drm.debug=7 capemgr.disable_partno=BB-BONELT-HDMI
    5. Save the uEnv.txt
    6. Safely remove the SD Card from your PC
    7. Insert the SD Card into your Beaglebone
    8. Mount the MikroBus Cape
    9. Bootup the board
    10. Log in via SSH or Debug
    How do I enable the adaptor board under the Debian O/S?
    Getting Started - DEBIAN
    NOTE: At this time due to the changes being made in the kernel, the Device Tree Overlay is not functional. The Linux comminity is currently working on the Device Tree handling.
    $ git clone git://
    $ cd BBB-mikroBUS-Cape
    $ mkdir bbclickdtbo
    $ tar -C /root/BBB-mikroBUS-Cape/bbclickdtbo/ -xvf BB_board_dtbo.tar
    $ cd bbclickdtbo/
    $ cp BB-MIKROBUS-01-00A1.dts /lib/firmware/
    $ cp BB-MIKROBUS-01-00A1.dtbo /lib/firmware/
    $ reboot
    BeagleBone (Black)
    From the adoption of Linux kernel 3.x a new method to configure pin headers was introduced. At the boot time, an in-kernel utility named “capemgr” can dynamically load Device Tree definitions to configure the appropriate pin headers and bus initialization.
    BeagleBone (White)
    To allow the BB to identify an appropriate pin header configuration, The Click Cape has a programmed onboard EEPROM to make use of the Cape's “plug and play” functionality, just insert the Cape and reboot the BB.

    As in the case of the White, which reads the information stored in the onboard EEPROM, the Click Cape has a “plug and play” functionality, but requires the user ( initially) to include the *.dtbo file (which is downloadable from here) into the directory - /lib/firmware and then to reboot the system.

    $ wget
    $ mkdir bbclickdtbo
    $ tar -C /home/root/bbclickdtbo/ -xvf BB_board_dtbo.tar
    $ cd bbclickdtbo/
    $ cp BB-MIKROBUS-01-00A1.dts /lib/firmware/
    $ cp BB-MIKROBUS-01-00A1.dtbo /lib/firmware/
    $ reboot
    The cape is not functioning with the BBB as it should be, what can I do with it?
    HDMI Disable
    For the BeagleBone Black to function properly with the cape, the HDMI has to be disabled. To do this you have to replace the contents of the uEnv.txt file in the FAT partition of the BeagleBone Black:

    $ mkdir /mnt/boot
    $ mount /dev/mmcbk0p1 /mnt/boot
    $ nano /mnt/boot/uEnv.txt

    Replace the contents of uEnv.txt to this

    optargs=quiet capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN

    Then save and exit (Control X, then Y then Enter), and reboot. On Debian this can be done by uncommenting the same line in the uEnv.txt

    Blog Posts