That should have read: .... we smoothed the transition to PIC32, .. and also: .... but I give the ChipKit a huge thumbs up ... On 5 February 2012 00:40, Chris Roper wrote: > I use the ChipKIT Uno 32 as PIC32 Development board for quickly testing > Ideas. > > It is true that there are a few holes in the libraries, but all of the > simple Arduino Sketches work, just not all of the 3rd Parties Libraries. > It is actually a well priced and powerful dev board and you can use it > directly with PICKit3 or ICD3 if you don't want to mess with the > Arduino Environment and the Bootloader. > > The one major advantage is that it has a C++ compiler, something that > MPLab is currently lacking, and so is great for knocking out a proof of > concept. > > The only shield I have used with it was the Arduino Ethernet Shield and > it worked well enough. It proved that an Existing App, that was > developed on Arduino, could be ported to the PIC32 platform, with a rewri= te > of the libraries. The cross compiling to PIC32 then proceeded > in parallel with the PIC32 based target board production. > > Without that confidance boost from the CHIPKit board, we would have gone > to production with several thousend ATMEL based boards. This way we smoth= er > the transition to PIC32, boosted perfoprmance and reduced cost. > > I am not an Arduino or ATMEL fan but I give the PICKit a huge thumbs up= .. > > Cheers > Chris > > > On 4 February 2012 07:30, Mark Hanchey wrote: > >> On 2/3/2012 1:37 PM, PICdude wrote: >> > How about just using their firmware on a Chipkit (PIC32-based Arduino >> > clone)? It should run the firmware directly. The Chipkit IDE is the >> > Arduino IDE with a specific board configuration for the PIC32. >> > >> > Cheers, >> > -Neil. >> >> 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 .