Differences

This shows you the differences between two versions of the page.

--- help [2011/08/10 11:03] – ray
+++ help [2011/12/28 03:11] (current) – Flashing firmware if testing firmware is still installed baldo
@@ Line 1: / Line 1: @@
 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://irc.blafasel.de/#r0ket|irc://irc.blafasel.de/#r0ket]] - but our ressources there are limited. We are currently learning about the various problems people encounter and then write something here....
+  * if nothing helps, join the r0ket irc channel [[irc://space.blafasel.de/#r0ket|irc://space.blafasel.de/#r0ket]] (if it is full see contact for other servers) - but our ressources there are limited.
-Please note: our market research has told us people buy stuff with closed crypto keys and vendor approved applications like crazy, theref0re the r0ket is compatible with this audience. The original firmware contains some crypto keys to make this possible, so if you flash your own firmware you will lose those forever. We don't want to stop you from doing so (you'll loose only the stuff which needs the closed krypto keys), just wanted to tell you before you start flashing. Possibly you want to live on the Bluemchenwiese for a day or so before jailbreaking your badge...
-Please also note: Camp hasn't even started yet and we are putting more stuff together on flashing etc. Some of us aren't even at Camp yet. Probably just start with the [[simulat0r]] if you want to write your own Tetris NOW.
+Please note: we threw away the crypto keys. So if you update from the original camp firmware to the congress firmware you have to replace your l0dabels with current (unencrypted) ones!
+<del>our market research has told us people buy stuff with closed crypto keys and vendor approved applications like crazy, theref0re the r0ket is compatible with this audience. The original firmware contains some crypto keys to make this possible, so if you flash your own firmware you will lose those forever. We don't want to stop you from doing so (you'll loose only the stuff which needs the closed krypto keys), just wanted to tell you before you start flashing. Possibly you want to live on the Bluemchenwiese for a day or so before jailbreaking your badge...</del>
 ==== Collection of known Problems ====
@@ Line 11: / Line 13: @@
 Pushing joystick up while powering on erases the firstboot config. There is no risk in doing that except having to type in your nick again...
-=== Data Flash corrupted ===
+=== DataFlash corrupt ===
-It SEEMS some badges have a wrongly formated DF. The DF is the 512K Chip storing the filesystem containing fonts, l0dables, config etc.
+It SEEMS some badges have a wrongly formatted Dataflash (DF). The DF is the 512K serial flash memory chip storing the filesystem containing fonts, l0dables, config etc.
-A corrupted FS can result in the badge displaying some error on firstboot about unavailable functions. You can attach the badge to a PC (linux preferred) and start the USB Storage in the menu, a 512K FAT filesystem with >30 files should appear. If that somehow looks crazy it MIGHT be you have a corrupted fs.
+A corrupt FS can result in the badge displaying some error on firstboot about unavailable functions, unreachable executables, wrong nickname display etc. You can attach the badge to a PC (linux preferred) and start the USB Storage in the menu, a 512K FAT filesystem with >30 files should appear. If that somehow looks crazy it MIGHT be you have a corrupt fs.
-You can download an image of a clean FS from:
+To reformat the drive:
-http://y.nu/r0ket-df.dd
+<code>
+ sudo mkfs.vfat -F 12 -I -n r0ket /dev/sdX
+</code>
+with sdX being the new found device. Be sure not to overwrite your Harddrive - a small typo here could ruin all your PCs data…
-Just start your Badge in USB-Mass-Storage while having the r0ket connected to your PC (using Linux should be best). Either from the menu or hold joystick down while powering it on. A 512K Blockdevice should appear on your PC, if you had an automounter, unmount it again. Then execute
+And then copy all the files of release/files/ to the device.
+Alternatively an image of a working FS is available at
+http://y.nu/r0ket-df.dd
+Download that, boot your r0ket while pushing the joystick DOWN (not in and NOT LEFT) to start as mass storage, wait for the 512K device to appear, unmount it if your automounter mounted it an then
 <code>
 dd if=r0ket-df.dd of=/dev/sdX
 </code>
-with sdX being the correct device (check /var/log/messages. You can destroy your Notebooks bootloader when entering the wrong device here...)
+with sdX being the new found device. Be sure not to overwrite your Harddrive - a small typo here could ruin all your PCs data...
-You might want to recreate your Keys after that, for that you need a checkout of our git, in tools/crypto/ it contains a tool to generate them. Just mount the volume after executing the dd and copy the created keys over. Those are used for send/receive vcard for example. Nothing really important to use the badge to display your nick...
+For fixing your r0ket with your old or a friends backup see [[backup_usb_storage|Backup usb_storage]].
-=== Display doen't work ===
+=== C0D/NIK-files not shown in menu ===
+Two possibilities: a) your filesystem is corrupt (see above)
+b) your OS created the files with lower-case extensions (all extensions on the filesystem are always in uppercase). To fix this:
+<code>
+cd /media/…
+rm *.c0d *.nik *.int
+cd …/release/files
+rename s/c0d/C0D/ *.c0d
+rename s/nik/NIK/ *.nik
+rename s/int/INT/ *.int
+cp *.c0d *.nik *.int /media/…
+sync
+</code>
+=== Display doesn't work ===
 Careful, display connectors are fragile.
-Find someone who has a working display, try that. But: so far we haven't encountered a broken display. Your problem might be something else.
+Find someone who has a working display and give that a try instead. But: so far we haven't encountered a broken display. Your problem might be something else.
 === I have flashed a new firmware, but the old original l0dable files don't work anymore. I only see a rocket picture.  ===
-Yes, that's expected. When you flashed the new firware, you implicitly jailbroke the device and moved on from Bluemchenwiese to Hackerspace... That means you lost the original secret keys forever (unless you manage to extract them from another device, of course) and the old l0dable files are encrypted with those old keys - so you can't install them anymore. You have to install new l0dable files that are encrypted with the new keys (probably those which you downloaded from git and renamed to SECRET.release, see http://r0ket.badge.events.ccc.de/build ).
+Yes, that's expected. When you flashed the new firmware, you implicitly jailbroke the device and moved on from Bluemchenwiese to Hackerspace... That means you lost the original secret keys forever (unless you manage to extract them from another device, of course) and the old l0dable files are encrypted with those old keys - so you can't install them anymore. You have to install new l0dable files that are encrypted with the new keys (probably those which you downloaded from git and renamed to SECRET.release, see http://r0ket.badge.events.ccc.de/build ).
+=== r0ket only displays test output ===
+If you see the following output after power on and your r0ket doesn't do anything else, it still contains the testing firmware:
+  testing...
+  flash...ok
+  ADC...ok
+  RF...timeout
+  spi...ok
+  test done
+  ready for
+  takeoff
+In this case follow the instructions on [[init|init]] to flash the firmware yourself.