chipKIT® Development Platform

Inspired by Arduino™

Difference between Uno32 and uC32?

Created Thu, 13 Aug 2015 19:33:30 +0000 by w5uxh


w5uxh

Thu, 13 Aug 2015 19:33:30 +0000

I started with the Uno32 last year after becoming aware of ChipKit. I noticed today that it is being discontinued. At first glance it appears the uc32 could be identical except for having more memory. I zeroed in on the Uno32 because it was the board being used by Ten Tec for an "open source" transceiver (amateur radio hobby). I could immediately see the advantages over the Arduino boards. I can see now that I would have been better off if I had noticed the uC32 at the time, since it has the larger memory!

My current project targets any of the Uno32, Max32, or PICadillo-35T. I have a PCB layout that the Uno32 plugs into. I would hope that the uC32 is 100% pin compatible so that hardware wise I can just swap out the Uno32 with the uC32. Can I expect this?

I currently use board definitions to target differences between the three boards. Is it likely that all chip resources (e.g. SPI, interrupts etc.) will be compatible so I can just "blindly" include the BOARD_UC32 in a logical OR at every place I use BOARD_UNO and easily substitute the uC32 for the Uno32?

Of course the most important thing would be the pin assignments for compatibility with my PCB layout.

I can dig into this myself, but perhaps there is a simple answer out there that can save me the trouble of comparing the two boards in detail.

Thanks.


djgardn2

Thu, 13 Aug 2015 21:23:26 +0000

I have a PCB layout that the Uno32 plugs into. I would hope that the uC32 is 100% pin compatible so that hardware wise I can just swap out the Uno32 with the uC32. Can I expect this?

If I remember correctly from someone else mentioning it before the answer is Yes, they are 100% pin compatible.

Edit: You can even keep using the Uno32 board selection in MPIDE and the sketches will still work correctly without the need to modify your code at all, you simply are uploading the code to uC32 instead. The catch with not modifying your code to work with the uC32 is it wouldn't use the extra memory available and other features etc that the Uno32 doesn't have.


w5uxh

Thu, 13 Aug 2015 21:52:24 +0000

Thanks for the reply. I had already ordered one from Amazon / NKC after posting my query, figured I might as well bite the bullet. Hopefully it will be the Rev B! I also added the uC32 as a target, just in case it might matter, and for clarity.

Perhaps it will plug and play with no surprises! (I would guess this is likely.)

Thanks again.