
Originally Posted by
hjalfi
Oh, yeah, I forgot that (it's not actually in the 'documentation', and that bit is marked as reserved). However the motor doesn't actually come on when the program runs and it's cached.
sfx: looks at code
Aha, there's a sort of bug where every clock tick the interrupt handler turns the motor off again. Maybe that's worth fixing. The core problem is that port's not readable so I can't change it without reading the shadow copy, which (a) that standalone program can't access and (b) I don't actually keep a shadow copy yet anyway...
Bookmarks