No, unfortunately I don't have answers to your other problems. I'm not that far yet in "experimenting" with FoxBoard. Just started a while ago and my first "concerns" are a decent I2C driver (one which can handle multiple bytes per message, not one that is only capable of sending one byte at a time between a start and a stop...) and how to catch interrupts from the FoxBoard pins.
Next to this, a decent IDE to code and debug is on my wish list. Sorry I can't be of more help on your other subjects. Best rgds, --Geert --- In [email protected], "Alex" <[EMAIL PROTECTED]> wrote: > > --- In [email protected], "Geert Vancompernolle" > <geert.vancompernolle@> wrote: > > > > Hi, > > > > Don't know for the other points you mentioned, but: > > > > > The SDK won't compile unless you make the following links: > > > > > > cd devboard-R2_01/apps/crypto/openssl/openssl/include/openssl/ > > > > > > ln -s ../../crypto/idea/idea.h > > > > > > ln -s ../../crypto/engine/engine.h > > > > > > > I didn't have this problem when I compiled the Phrozen Patch. > > > > Next to this, this is not a typical Phrozen Patch problem. This has > > been reported by me already a while ago and Sergio has adapted the > > Troubleshooting web page: > > > > http://www.acmesystems.it/?id=34 > > > > Weird enough: I sometimes have to do this, I sometimes don't have to > > do this. > > Couldn't figure out when I had and when I didn't have to do this yet. > > I know this was already reported and the solution is on the > Troubleshooting web page, but I wanted to report it together with the > other bugs I found. > > Anyway I always have had to link those files, so I though it was > really a bug. > > > Thanks anyway for answering my post. Any idea about the other bugs? >
