r0ket

acronyms

2012-01-08T14:13:21+02:00

This page will explain some of the vocabulary of the r0ket project * r0ket is missing a 'c' by intention and using zero in fav0r 0f an ordinary 'o'. it names the whole project and the peace itself: a pcb in shape of a rocket as seen in * m0dul is a hardware enhancement of a r0ket. * l0dable is a software enhancement of a r0ket which can be loaded by the firmware * firmware is a preinstalled software that shows an idle screen, provides a menu and allows loading modules.

backup_firmware

2011-08-10T13:31:45+02:00

[Backup has nothing to do with firmware i think... just usb_storage]

backup_usb_storage

2011-08-10T13:25:55+02:00

This will help you to backup your own r0ket memory and restore it. For example if your r0kets data flash is corrupted. Backup old usb_storage * Connect your r0ket via USB. * Select the usb_storage mode from the r0ket menu. * Unmount the r0ket storage (e.g. Ubuntu automounts storage devices) * Run:

build

2011-08-14T23:29:26+02:00

... 0. Work in Progress After all it's r0ket science. If you actually start developing something for the r0ket now, we'd recommend to join our Mailing List and IRC channel - see contact. This article explains the setup on a Linux machine. Instructions for Mac OS X are available here.

build_mac

2011-12-27T21:35:08+02:00

You might want to disable .DS_Store files on (network) mounts ... NEVER EVER access the r0ket with the finder. 1. Compiler Using Mac OS X: Solution 1 * This explains how to build the tool chain on a Mac: Git project: jsnyder / arm-eabi-toolchain * You will probably want to add this line to /etc/bashrc, so that the tools are always accessible when you open a new Terminal: export PATH=$HOME/arm-cs-tools/bin:$PATH

building_with_a_free_toolchain

2011-08-13T22:49:41+02:00

curl -s https://github.com/matthiasr/summon-arm-toolchain/raw/master/summon-arm-toolchain | /bin/sh git clone git://github.com/matthiasr/r0ket.git r0ket cd r0ket/firmware cp SECRETS SECRETS.release PATH=$HOME/arm/bin:$PATH ./release-all I adapted a Script for building a GNU binutils/GCC/Newlib/GDB toolchain. It should be portable. gmp, mpfr and mpc need not be installed.

buildtoolchain

2011-08-10T12:39:58+02:00

In this document I will describe how to build a toolchain for ARM. setup build environment In this document we will install the toolchain in the users home directory under $HOME/arm-elf. Installation will take place in /tmp/toolchain. $ mkdir -p /tmp/toolchain/src

cccamp11_workshop

2011-08-12T18:14:42+02:00

Design your own m0dul for r0ket @cccamp11! You want to design your own PCB? Go every step from the idea to the finished, working m0dul? This workshop lets you do exactly that. In the workshop you'll learn how to use LEDs, Piezos and Buttons with the m0dul bus. You can chose those from a selection we are bringing to camp. You should already know how to solder.

colordisplay

2011-12-30T10:43:56+02:00

This is a page to collect everything on getting color display (nokia 1600 for now) to work on r0ket. 28C3 firmware Finally there's a l0dable to show a color BMP or animation instead of nickname by nihilant: (includes source and compiled binary).

concept

2011-06-21T03:39:51+02:00

r0ket r0ket is an electronic name tag and much more. * Proudly display your nick on Camp 2011 and future events * Have fun with the camp-applications or alternate firmwares * Use it as foundation for your own microelectronics project * Provide an interesting component as a m0dul for your event or workshop and rely on r0ket for the basics like display, CPU, power supply and RF * Rapidly develop for and with diverse hardware by combining extensions designed by the community

contact

2011-08-12T13:56:48+02:00

* Mail: team@r0ket.badge.events.ccc.de * Twitter @r0ketbadge * Soup: r0ket.soup.io * Mailinglist: discuss@r0ket.badge.events.ccc.de Subscribe * Our IRC Channel on Blafasel. The default server seems to limit the amount of Camp IPs joining, so here some more of the same Network: * IRC irc://space.blafasel.de/#r0ket * IRC irc://ray.blafasel.de/#r0ket * IRC irc://irc.blafasel.de/#r0ket

crypto

2011-08-03T09:15:46+02:00

OpenBeacon packets are encrypted using a private symmetric key using the XXTEA algorithm. As the key is the same for every participant of the camp it must kept secret inside the firmware. This creates the need to protect the flash memory of the main micro controller from being read by an attacker. It will therefore be read protected.

exploit

2011-08-19T13:38:32+02:00

This page describes several ways of 0wning your r0ket (i.e. retrieving the original “vendor” keys for encrypting&signing new l0dables and for encrypting&signing messages on the wireless mesh). 0wning the r0ket The r0ket uses a mesh-network to convei time, highscore and other messages. To protect these values from evil hackers, the mesh encrypts and signs messages sent to the mesh using a secret key, stored read-protected on the flash of the processor.

f0nt

2011-08-10T13:18:45+02:00

A f0nt is a binary compressed bitmap font. f0n files can be created with makefont.pl - which requires perl and the GD module. To convert a ttf font file, call it as “makefont.pl -b -f file.ttf -s 18” which should create (amongst others) a .F0N file.

features

2011-08-10T15:45:25+02:00

Basic functionality * Display your name :) TBD * Access the on-board storage via USB * You can choose to add your information to the collection of Attendee Meta Data * The red LED in the upper right starts blinking when you need a charger TBD * Transfer your contact information to other badges TBD

firststeps

2011-07-29T19:17:24+02:00

LCD * LCD on front * Apply tape * Connect * Apply LCD Battery * Battery on back * Apply tape * Connect * Apply battery * The r0ket can be charged via micro USB (use a USB 2.0 cable or adapter, micro USB 3.0 has a different connector) by any USB powered device * The estimated runtime is around 12 hours, a full charging cycle is around 1.5 hours * The battery indicator in the upper right LED blinks red if your battery is running low * The r0ket will automatically power …

flame

2011-12-28T17:42:06+02:00

See this page instead:

hardware-mods

2011-08-13T20:43:13+02:00

* from BiC crystal pens * first reprap nipple * Parametric r0ket nipple * Parametric r0ket nipple + lip * reprap casing * full knitted cover * another knitted for hardware on the m0dulbus see m0dul * *

hardware

2011-12-29T20:01:33+02:00

Hardware Intro We want to encourage you to tinker with your r0ket. Write your own software or build a pluggable hardware m0dul. Surprise with your creative ideas! Several people contacted us about producing r0kets for other occasions. All necessary information is on github and we're happy to help. But you should plan ahead at least 2 months!

help

2011-12-28T03:11:44+02:00

If your r0ket isn't working try the following steps in this order: * check here if we already know about the problem and maybe even have a solution * if nothing helps, join the r0ket irc channel irc://space.blafasel.de/#r0ket (if it is full see contact for other servers) - but our ressources there are limited.

img2lcd

2011-08-11T00:04:48+02:00

Create Your own image Use this template.png from github. The white area will be visible on your display, the 4 black rows at the bottom will not but have to be included. As soon as you have finished your drawing, use to img2lcd.pl converter located at /tools/image/ in the source repository to convert your picture.

init

2012-04-18T15:26:42+02:00

This procedure also brings your r0ket back into shape in case you “bricked” it or experience other strange software glitches including a damaged file system for l0dables. RevisionChange 1 Initial 2 Improved Mesh 3 Improved r_player l0dable 4 Improved fahrplan, mesh, fonts 5 Fixed mesh 6 Actually pushed the mesh changes, improved game l0dable 15 numerous small bugfixes Linux * Download the firmware pack here: * Unpack the archive with your favourite tool. * Turn r0ket off (…

l0dable

2011-12-30T13:18:32+02:00

l0dable documentation This page documents to how to write a l0dable. depending on the font you are seeing this looks like “I/O dables” but meant is “loadable”. these are small software components (in opposite to m0duls which are hardare components) that can easily copied to the r0ket. Once you are done with you l0dable please mention it in l0dables.

l0dables

2012-01-03T16:22:53+02:00

l0dables Intro this page is intended to list l0dables that are already implemented, their features and source. How to write your own l0dables is documented in l0dable L0dables are small (<2.5k) loadable modules for the r0ket firmware. In the default released firmware these need to be encrypted signed to be run (only true for original camp firmware)

lcd_art

2012-01-02T14:43:32+02:00

Here you can publish any LCD art you made.You can display *.lcd files using the “showlcd” l0dable Here's a small script to convert gifs to lcds: Display images as nick * Download the *.lcd * Rename it to “NICK.LCD”. * Replace it with the NICK.LCD on your r0ket. * Choose in the r0ket menu: nick --> chooseAnim --> IMAGE.

m0dul-ethernet

2012-04-24T10:55:19+02:00

Ethernet m0dul. Makes the r0ket speak IP. Currently in planning. Main reason to do this is to get the received Openbeacon data from the r0ket to a central location in a nice and easy way. Alternate Options There are of course other options to do this:

m0dul-example

2011-06-20T20:28:18+02:00

Description: The example m0dul is an example! Author: example@example.com Links: author, project site, whatever Usage instructions The example m0dul has a “1” mark on the PCB. Plug onto either m0dul A or m0dul B connector. Used addresses I2C 0000000 Chip select #DEFINE SS0 or SS3 EXAMPLE_SPI_CS in main.c Step by step assembly instructions, schematic, board, eagle, bom, etc

m0dul-flame

2012-01-03T19:24:47+02:00

Description: Ignite your r0ket! Kits Sorry, SOLD OUT! Assembly See Author: kiu Links: https://github.com/kiu/flame Kits Sorry, SOLD OUT! Aww, that's sad. But hey, what about creating new ones? See thoughts on flames production of new RGB flames (internal)

m0dul-flame_rgb-mod

2011-08-18T16:56:04+02:00

* original flame m0dul * 1x RGB LED * 2x 100K SMD Resistors * a few centimeters hookup wire (german: Fädeldraht) * soldering equipment Source LRTB G6TG RGB MultiLED LED Datasheet * unscrew the acrylic flame * unsolder the original one-color LED

m0dul-j0y

2011-07-21T03:58:16+02:00

j0y+ m0dul is a game controller for your r0ket . Just connect the j0y+ m0dule to your r0ket. Eventually you will have to flash a new firmware onto the r0ket, we are not sure about this at the moment. This is a gamepad, so feel free to program games that use a analog stick, 4 buttons, some LEDs and perhaps a vibro motor (yes, we live in fear of Immersion). And good god, make them multiplayer!

m0dul-r0ketc0m

2011-08-15T13:15:31+02:00

This m0dul will use a VS1053b audio dsp to connet a microphone and headphone jack to your rocket. With a populated SD-slot you get an mp3/vorbis player, but main purpose is intendet to be a streaming player for talks / PTT coms device. Expect to see hardware in a few days. Planed on a 200pcs production run. Coders needed...

m0dul-torch

2011-08-10T16:43:24+02:00

Torch is a simple parasitic m0dule for r0ket. It uses the regulated 3.3v power supply and r0kets plentiful battery to drive a couple of white leds triggerd by an attached pushbutton. Grip your r0cket so you can reach the pushbutton. Then press it. If your r0ket is turned on then it should light up.

m0dul

2011-12-30T00:10:40+02:00

The r0ket can easily be extended by pluggable m0duls. See m0duls for existing m0duls. Please keep in mind that power is a very limited resource on the r0ket. The more a m0dul consumes the less fun you have! Interface A m0dul can be connected to the r0ket via the m0dulbus. The connectors are in 2.54mm/100mil spacing, prepopulated with female sockets. If available, a stackthrough connector should be used to interface with the m0dulbus. The hackerbus is intended for tinkering, a m0dul should us…

m0duls

2012-04-24T10:47:10+02:00

m0duls This page is intended to list avaiable hardware components for the r0ket. As m0duls use I2C and/or SPI to communicate with the r0ket, its possible that multiple m0duls use the same addresses. Here is a list of used addresses to verify compatibility.

manual

2011-12-29T22:27:33+02:00

R0ket User Manual Intro The r0ket was developed as the badge for the Chaos Communication Camp 2011. Besides being a shiny electronic name tag, the r0ket is an easy to use full featured microcontroller development board. We want to encourage you to tinker with your r0ket.

nick_animation

2011-08-10T21:48:11+02:00

Animated Nick Specification * Each frame is a .lcd file. * All frames are concatenated and saved as “nick.lcd”. * Each frame is shown with a fixed frame rate of 0.5s. Notes on lcd files * Pixels are not quadratic, but rectangular with a 1.209 ratio (each pixel is 1.209 times higher than its width). * This means a square should be 77 pixel wide and 64 pixel high (for example).

r0ket

2011-12-30T00:17:05+02:00

a r0ket is a r0ket is a r0ket

r0ketlauncher

2012-01-03T00:31:32+02:00

getDigital left lots of USB missile launchers in our hands. So we'll give you the opportunity to play with them at 28c3! We have quite some of those, so take them apart, solder pins to the hackerbus, launch r0kets, whatever... how will that work? * receive a missile launcher after a security deposit of 20 Euros. You get those 20 EUR back, they are just a deposit! * Missiles are avaible at an additional security deposit of 2 Euros each. * you will get that back when returning the launcher…

r0ketlauncher_ammunition

2011-12-29T15:47:49+02:00

Improvised ammunition for the r0ketlauncher, if you don't have enough foam missiles. Roll your own It does not get much more simple than this. A small piece of paper, ~3x~5 cm, rolled together and bent. No tape is needed, but that might reduce air resistance and increase range a bit.

rem0te

2012-01-07T19:59:18+02:00

With the rem0te package of r0ket software you can build a game or other installation that can be interacted with, using a r0ket. The system consists of three elements: The game server, the bridge and the l0dable r_player. The game server uses the bridge to announce the game, receive button presses and (in the future) send text to the display of a player.

simulat0r

2011-12-25T02:15:53+02:00

... 1. What is it? The simulat0r basically is a set of headerfiles and some C code which enables you to compile r0ket applications on x86 machines and run them using a qt GUI frontend. Currently only the LEDs, display and input button are supported, but that should be enough to develop simple games, a cool nickname-scroller firmware or similar stuff.

software

2011-12-29T23:56:19+02:00

You can find the whole software in our git repository on github: The code is released under BSD license. Structure The base firmware provides you with a set of functions to control the r0ket * How to build your own software * Use the simulat0r to test your software without having a r0ket * Write your own l0dable but... * Document the l0dables you built

start

2012-04-24T12:53:34+02:00

r0ketlauncherdocumented For the consumers: * The user manual for the r0ket * A list of often used acronyms * List of l0dables init help For the producers: * The hardware powering the r0ket * The software on the r0ket * How to write your own l0dable * List of m0duls that have been done/planned * Information about r0ket tracking

tracking

2012-04-24T11:57:52+02:00

We are tracking r0kets. General Idea is the Openbeacon project. We are using the “new JSON API”, see . Json changes We added some new fields to the JSON * added tag->nick: nickname as sent by r0ket * added reader->name: string that describes reader location

tvr0tator.c

2011-12-30T13:15:21+02:00

/* Licensed under CC0 1.0 Universal (CC0 1.0) * by andy (andy_@jabber.ccc.de) * see http://r0ket.badge.events.ccc.de/r0ketlauncher */ #include #include #include #include #include #include usb_dev_handle* launcher; pid_t pID; int send_message(char* msg, int index) { int i = 0, j; j = usb_control_msg(launcher, 0x21, 0x9, 0x200, index, msg, 8, 1000); memset(msg, 0, 8); return j; } void movement_handler(char control) { /* grab…