… it in the Wixel Configuration Utility. This is handy if you just want to program the app on to one Wixel or you want to test the parameters.
…can test different frequencies easily.
…t seems to work fine with the test_radio_signal_tx app.
…ing data and renamed the non-blocking functions so they don't have "NonBlocking" in the name. All functions in this library should be assumed to be non-blocking by default. I thought I had done this a long time ago. This is probably what was causing the problem with the test_radio_signal_rx/tx apps.
… seems to be working but not the tx one.
…ands, and 4 binary commands.
…puts docs.html in the right place.
…will get included in the docs.
…'. Replaced tabs with spaces. Conflicts: apps/example_blink_led/example_blink_led.c
…ibraries that depend on accurate timekeeping.
… easier to start the bootloader.
…he yellow LED. Changed the '?' command to be 'b' instead, and added a binary command that also gets the param_blink_period_ms.
…files. Also changed "YYYY" to "2011" in the licsense.
…wixel.h because those things have interrupts, which would cause the entire library to get linked in. Split uart.h in to two files: uart0.h, uart1.h.
…ess_serial application and it worked!
…their being multiple definitions of debug symbols, e.g. "Multiple definition of C$uart.c$148$2$2
…piled in to two different object: uart1.rel and uart0.rel. Still need to adapt all the code inside uart.c to use the new system.
…ou could see an an uncommon case.
…or example you can type: make load_wireless_serial S="serial_mode=3"
…es not currently come from the app, so it is pretty meaningless.
…il when the .lib files are absent!
…oved several TODO items.