OSX

DO NOT plug in the Digispark to your computer's USB port until prompted.

Install the artoo-digispark gem:

$ gem install artoo-digispark

After installing the artoo-digispark gem run the following command to upload littlewire to the digispark, plug it to a USB port when prompted:

$ artoo littlewire upload

Once plugged in, use the artoo connect scan command with the -t usb option to verify your connection info:

$ artoo connect scan -t usb

Now use the ID info returned to find the product and vendor ID's required to establish a connection with the Digispark in your Artoo code.

That is it, you are set to start running Artoo digispark examples.

Ubuntu

The main steps are:

Install the artoo-digispark gem

Add a udev rule to allow access to the Digispark device (Do not worry
about this, the artoo littlewire upload command does it for you if none is detected)

Plug in the Digispark to the USB port

Connect to the device via Artoo

DO NOT plug in the Digispark to your computer's USB port until prompted.

Install the artoo-digispark gem:

$ gem install artoo-digispark

After installing the artoo-digispark gem run the following command to upload littlewire to the digispark, plug it to a USB port when prompted, you might be asked to enter your sudo password, since uploading littlewire to the digispark requires some new udev rules, you can check and review them in /etc/udev/rules.d/49-micronucleus.rules after running the artoo littlewire upload command):

$ artoo littlewire upload

Once plugged in, use the artoo connect scan command with the -t usb option to verify your connection info:

$ artoo connect scan -t usb

Now use the ID info returned to find the product and vendor ID's required to establish a connection with the Digispark in your Artoo code.

Windows

We are currently working with the Celluloid team to add Windows support. Please check back soon!

Documentation

Check out our documentation for lots of information about how to use Artoo.

IRC

Need more help? Just want to say "Hello"? Come visit us on IRC freenode #artoo

Contributing

All active development is in the dev branch. New or updated features must be added to the dev branch. Hotfixes will be considered on the master branch in situations where it does not alter behaviour or features, only fixes a bug.

All patches must be provided under the Apache 2.0 License

Please use the -s option in git to "sign off" that the commit is your work and you are providing it under the Apache 2.0 License

Submit a Github Pull Request to the appropriate branch and ideally discuss the changes with us in IRC.

We will look at the patch, test it out, and give you feedback.

Avoid doing minor whitespace changes, renamings, etc. along with merged content. These will be done by the maintainers from time to time but they can complicate merges and should be done seperately.

Take care to maintain the existing coding style.

Add unit tests for any new or changed functionality.

All pull requests should be "fast forward"

If there are commits after yours use “git rebase -i <new_head_branch>”