I'm surprised, but I've not used the Chipkit too in-depth yet. Would =20 love to know which libraries, so I can avoid the pain when the time =20 comes. Cheers, -Neil. Quoting Mark Hanchey : > The Chipkit boards have a long way to go before they are really arduino > compatible. A lot of the arduino libraries do not work so you are left > doing mainly the basic functions like spi or i2c . I looked at porting > some of the arudino libraries but why bother when you can just code in > C32 and be done with it. I think digilent dropped the ball on this one > by trying to make the pic32 fit the arduino world, they ended up with a > neutered board with a lot of the important parts of the pic32 having to > be done via shields and add on boards. It doesn't even have a working > RTCC without adding another board or soldering on the crystal. The USB > features are the same way, requires another board which cost an > additional $50. > > Would have been much better if they ditched the arduino software side, > kept the shield ability and made use of the features the pic32 has that > are unique to it. I see a lot of postings by people wanting to use the > features the pic32 brings and getting frustrated that they have to jump > through hoops to do it with the chipkit boards . > > Mark > > -- > http://www.piclist.com PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist > --=20 http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .