I\'ve added power functions message sending to Bibo, plus fixed a few bugs. I\'m uploading this as a whole tarball with otherwise fairly minimal changes compared with the latest release.
Unfortunately there appears to be no way to get reliable PF message timing without completely disabling interrupts for the duration of a message, 10-12 milliseconds. I\'ve considered using the serial interface but it\'s not suited for bits of varying length (the start bits get in the way). A demo program shows how you can use the RCX to access the \'extra\' address space described in the PF RC protocol, in effect doubling the number of available PF channels.
When I compile it in cygwin, I got error as below, what can I do?
which: no esterel in (/brickos/util;/usr/local/bin:/usr/bin:/usr/bin:/cygdrive/c/Program Files/Windows Resource Kits/Tools:/cygdrive/c/Program Files/ThinkPad/Utilities:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/System32/Wbem:/cygdrive/c/Program Files/Diskeeper Corporation/Diskeeper:/cygdrive/c/Program Files/ThinkPad/ConnectUtilities:/cygdrive/c/Program Files/Common Files/Lenovo:/cygdrive/c/Program Files/Lenovo/Client Security Solution:/cygdrive/c/Program Files/Intel/WiFi/bin:/cygdrive/c/Program Files/Common Files/Intel/WirelessCommon:/cygdrive/c/cygwin/brickos/util:/cygdrive/c/cygwin/bin:/cygdrive/c/Program Files/Intel/WiFi/bin:/cygdrive/c/Program Files/Common Files/Intel/WirelessCommon:/cygdrive/c/cygwin/brickos/util)
/usr/local/bin/h8300-hitachi-hms-gcc -MD -DB2400 -g -Os -mquickcall -fno-builtin -fomit-frame-pointer -Wall -Iinclude -c util/host/fastdl.S -o util/host/fastdl_2400.o
util/host/fastdl.S:103: unterminated character constant
util/host/Makefile.sub:91: recipe for target 'util/host/fastdl_2400.o' failed
make: *** [util/host/fastdl_2400.o] Error 1
That's odd. The error comes from a line that only contains a comment:
; Hack the update function state so we don't hear two beeps
Can you verify that that's the line that's causing trouble?
It would be easier to try to reproduce the bug if we knew what version of gcc
you're using. Could it have something to do with the ' in the comment? Does
it work if you replace "don't" with "do not", or just remove the whole line?
//Carl
On 11/03/2013 09:56 AM, Zhengrong Zang wrote:
Related
Patches: #27