The supervisor for my autopilot is working. This is a fairly critical piece that runs on the AVR I/O board and handles the handover between the manual remote, the autopilot, and any safeties.
I’d like to learn Go, so I’m considering using for the command side of my never complete self driving RC truck project. Here’s some quick notes after a night of hacking:
We’ve got some Christmas stars in the window that needed some illumination. I hacked together a Olimex OLIMEXINO-85, a 8 mm RGB led, and the support components to make this:
I’m pretty happy with this. It’s a USB to 3.3 V 1 A supply using a AMS1117 linear regulator. I used the SMT version as the pin spacing is fine for veroboard and I can hide it away on the bottom of the board.
Looks like I’ve run into my first problem: FTDI based USB to serial adapters don’t work as they seem to be automatically disconnected shortly after plug in. I suspect that it’s udev running the brltty rules, not finding a assistive device, and aborting.
Looks like I’ve run into my first problem: FTDI based USB to serial adapters don’t work on Chrome OS as they seem to be automatically disconnected shortly after plug in. I suspect that it’s udev running the brltty rules, not finding a assistive device, and aborting.
I’m going to see if my Samsung ARM Chromebook can be my primary machine. I’ve put a crouton Ubuntu chroot on a SD card (so it survives the kids dropping out of developer mode) and will mainly SSH into it.
‘clobber’ ensures that the register is free before entering and after exiting an instruction. Therefore you can’t use it to say a register is used then destoryed by an instruction such as LOADACC, (X+) on X.
GCC is crazy. It recognises a printf(‘foo\n’) and turns it into the equivalent puts(‘foo’) instead. builtins.c has all types of similar transformations including printf(‘%c’, v) to a putch(v) and printf(‘%s’, v) to fputs().
The Cii seems interesting. It needs more publicity – this is the first time I’ve heard of it in my fifteen years in Christchurch.