Microchip Application Libraries
SCREENSHOT 1. The Node 1
startup message contains
11223344556677602 as the
Peer Long Address and 02 as
the Peer Info.
Fred Eady can be reached via
email at email@example.com.
void __ISR(_EXTERNAL_1_VECTOR, ipl4)
void _ISRFAST _INT1Interrupt(void)
We are ready to attempt a compile. If the compile flies,
we’ll make an approach at loading the code via the
32MX7’s Area 51 programmer/debugger complex.
terminal emulator session.
I do read instructions every now and then. LED1 does
indeed illuminate on both nodes. However, the pushbuttons
are dead. So, the trail starts at the pushbutton definitions
for both the PIC18 Explorer and the 32MX7. The
pushbutton code for both development platforms lies
within the confines of the HardwareProfile.h file. Here are
the PIC18 Explorer assignments:
Just Because It
Doesn’t mean it will work. And in this case, it doesn’t.
We’ve got a bit more work to do. The good news is that at
least the 32MX7-to-32MX7 RF connection is working. Both
Cerebot 32MX7s are using their respective PmodUSBUARTs
to post startup messages via the terminal emulators.
Screenshot 1 is a capture of the Node 2 startup message. I
have an almost identical set of information on the Node 1
I went to the Microchip website and dialed in the PIC18
Explorer schematic. I pulled the pushbutton portion of the
PIC18 Explorer schematic into Schematic 3. Now, let’s
pull the 32MX7 pushbutton schematic snippet into
Schematic 4. Do you see what we need to fix?
The next step we need to take is to find the
pushbutton code in the Mi Wi
Simple Demo application. The
pushbutton function is not located
in the main application file but is
found in the HardwareProfile.c file:
if(PUSH_BUTTON_1 == 0)
//if the button was
//previously not pressed
52 SERVO 10.2011
SCREENSHOT 2. Once the pushbutton logic snafu was squelched, data flowed in
abundance on the PmodRF2 link.
time = TickGet();