On Jul 16, 2008, at 9:02 PM, Dave Hylands wrote:
> The robostix MUST be powered or you won't be able to program it.
> If the verdex doesn't boot when you power the robostix, then you
> either have a bad robostix or a bad tweener, or things aren't plugged
> in (i.e. stacked) properly.
Ah. Well, I just wrote a startup script to run, essentially, `date
>> /etc/testing; sync`, connected the verdex and robostix without a
tweener, and plugged the power into the robostix. I did this (trying
to boot it) twice, waiting a few minutes after each plug-in, but when
I reattached the tweener and checked /etc, the script hadn't been run
(except when the power was applied to the tweener), so I think that
should rule out the tweener. I cut power and rebooted once again to
make sure it wouldn't simply have not written the new /etc file to
flash, and each boot-up sequence with the tweener added a line to /
Anyway, thanks for that info. Now to figure out what to do before the
30 days run out...