Created Thu, 17 Nov 2011 22:30:36 +0000 by meistro
Thu, 17 Nov 2011 22:30:36 +0000
Hey guys!! Thanks for allowing me to use the Arduino environment to play with my Cerebot :) I have the boot loader burned and my led is blinking. I loaded the basic blink the leds sketch.
Where can I find the list of arduino pin map to Cerebot32MX4 pins? I'd like to become familiar with it :D.
Tue, 13 Dec 2011 07:35:31 +0000
One of the main things that I have been working on for the last month and a half is rearchitecting the core system to remove all board dependencies from the core files. I have put in place (with Rick Anderson's help in the IDE) a mechanism that allows easy definition and incorporation of boards into the system. It is now possible to plug a new board into the system without having to make any modification to the code for it to be supported.
The 20111212-test release that was put up on github today contains this support in its final form. The Cerebot 32MX4 is one of the boards for which I have creataed board definition files. (naturally I would support this board, since I designed it)
Look in the hardware/pic32/variants/Cerebot_32MX4 folder in the MPIDE installation tree. The file Board_Data.c contains all of the data tables that map from digital pin number to port and bit. The simple answer for most pins, though, is that connector JA has pins 0-7, JB has 8-15, JC has 16-23, etc.
The Board_Defs.h file contains symbols that map the physical peripheral devices (e.g. UART1, SPI1) to their logical use. On most boards UART1 maps to Serial, UART2 maps to Serial1, etc. However this is not the case on all boards. This file also contains symbols like: PIN_LED1, PIN_LED2, PIN_BTN1, PIN_BTN2, etc. that can be used in sketches to make the code more portable between boards. These symbols are defined on a board-by-board basis to map the device (e.g. LED1) to the correct pin on each board.
The latest test release if fully functional, we're just doing some final testing before making an official release.
Gene Apperson Digilent