This is a retired product, but fear not as there is a newer, better version available: DEV-09713
images are CC BY-NC-SA 3.0
Replacement: DEV-09713. The new version of the UBW32 now uses the PIC32MX795 IC.This page is for reference only.
Description: Based on the work of Brian Schmalz, the UBW32 is a small development board for the new PIC32MX460F512L 32-bit CPU from Microchip. The UBW32 is breadboard friendly and includes all the external circuitry to get the PIC32 up and running. Power can be provided over USB or from an external source. It has 3 push buttons (Reset, and 2 user-defined buttons) and 5 LEDs (Power, USB, and 3 user defined LEDs). All of the 78(!) of the PIC32's I/O pins are broken out. The board comes pre-loaded with a USB bootloader and special UBW firmware that accepts simple serial commands to control the various I/O functions.
If you have used a UBW or Arduino before and are frustrated by the lack of CPU power, lack of memory, lack of I/O pins, or lack of sophisticated software, the UBW32 is just what you are looking for! While only slightly more expensive than the 8-bit UBW, the UBW32 has significantly more I/O and CPU horsepower.
The UBW32 is also a very good stand-alone development platform for the USB PIC32 chip. It contains a simple to use USB bootloader so that you can write your own code and download it to the board without any additional programmer, tools, or software. If you need low-level debugging, you can also attach an ICD2/ICD3 or other PIC debugger.
The PIC32 chip is capable of doing USB OTG, USB Mass Store, USB Virtual Com Port and USB Host roles. There is a footprint on the bottom of the board for a USB connector that will allow you to plug any USB device into the UBW32. There is a jumper that allows you to power the VBUS 5V USB wire if you program your UBW32 to be a USB Host.
Note: Any UBW32s bought before 11/3/2009 has the first version of the bootloader on it. This version of the bootloader causes the "BL" (bootload) command to break with the latest version of the firmware (v1.3). In order to update to the most recent version of the firmware, which fixes the problem, you'll need a hardware programmer.
Note: This product is a collaboration with Brian Schmalz. A portion of each sales goes back to them for product support and continued development.