Wireless Hello World Code

Is the sensor demo you mention part of SLAC139 from the eZ430-RF2500 Product Folder, or the Wireless Sensor Monitor using the eZ430-RF2500 (SLAA378)?

Either way, I think the principle is the same.  In these examples, there is a project configuration for the End Device (ie. ED) and Access Point (ie. AP).

Currently, the ED is setup to use a timer to wake the MSP430F2274 and perform a measurement of the termperature and voltage on ADC10 channel 11.  When it collects this information, it sends both of these values to the AP via message with the SMPL_Send().
This message is received by the AP which in turns sends the message it received over the UART interface of the MSP430F2274.  This UART interface is connected to the eZ430 USB emulator pod which enables a Virtual COM port of the USB, allowing the message to be displayed via a terminal program such as HyperTerminal or TeraTerm.

If you don't care for the timer event, this could be removed and you can add either a polling of a GPIO connected to a push button (P1.2) on the RF2500T target board, or make this an interrupt.  At this point, it probably doesn't matter what the actual message contents are, but send a message via SMPL_Send().
The AP would need to be modified to not transmit this message over the UART interface, but perhaps toggle the GPIO connected to the LED (either P1.1 or P1.0) on the RF2500T target board.

The AP side demo_AP.c has a registered callback function call sCB() which is passed to the SimpliciTI stack via the SMPL_Init() function.  This callback function is called in the frame-receive ISR thread so it runs in the interrupt context.  Information about this can be obtained by downloading the SimplicTI stack from its Product Folder.
It is suggested the callback be very thin as it is run in the interrupt context.  The callback should set a flag or otherwise store the information about the waiting frame.  The user thread can then check this flag to call the SMPL_Receive() to retrieve the message in the frame.

Thanks Brandon,

               I'm working off the SLAC139 files. The SLAA378 gives good information. How come there is no reference at all to it in the eZ430-RF2500 user guide SLAU227?

 I'm able to toggle the LED on the target board with an interrupt from the pushbutton. Doing SMPL_Send instead of an LED operation should be straightforward. However, on the A-P target board, I'd like to only toggle the LED with a request from an authorized E-D. So I do need to look at the message.

When I get into an interrupt routine from the pushbutton, should I use SMPL_Link, or go directly into SMPL_Send to hit the AP?

Thanks!

Here's the code I'm running on the End Device. So far, I'm not having success. When I push the button on the ED target board, the LEDs light up, stay lit about 3 seconds and then go off. If all goes correctly, the LED2 on the Access Point board should light up each time I use the pushbutton on the ED to send a packet.

AP is running the Demo Sensor Monitor code unchanged, so LED1 keeps toggling at a 1 Hz rate.

Any help I can get on what to change will be super.

Reviewing the code you sent, I guess I would not have implemented the SMPL_Init() in the Port 1 interrupt service routine.  I would suggest using a structure similar to the SLAC139 demo_ED.c file to Initialize the SimpliciTI stack in the main() loop.  Once this is established, you can tell the MSP430F2274 to go to LPM3.  Then a push button event would wake up the device and get the message ready for sending.  I would put a little inside the ISR as possible.

Thanks Brandon,

        I need more help though. If I take the timer out, then is it sufficient to do the init only once? Should I do Ioctl calls within my ISR like the demo app does?

Thanks

I probably led you astray with removing the Timer interrupt as this is what wakes the MSP430F2274 up to run the SMPL_Init() calls until they succeed.  Therefore, you should probably keep the timer in there.

However, you may want to potentially disable the timer, if you don't need it.  Or change the behavior in linkTo() to not process the ADC stuff based on a Timer interrupt, but rather due to a button press.  What this would entail is adding a flag in the Port ISR to set once the interrupt service routine is executed.  The linkTo() would condition execution of the ADC stuff based on the setting of this flag.  Once you are finished with the ADC conversions and sending the data via SMPL_Send(), the flag would be cleared.

During this time, the timer may wake up the device, but since the Timer ISR would not set this flag, the ADC conversions would be skipped and the device would loop on the while(1) {} within linkTo().

Appreciate that Brandon. I'm still a novice at this. If possible, could you give me just some pseudocode detailing how you would do it? What would you put in the main() and what in the interrupt routine? Again, not detailed code, but just pseudocode so I can see easily what you're suggesting.

Thanks!

I don't know if this helps but I tried to do a similar thing with the one you do: I got the old demo_ED app and modified so it uses a timer to try and join the network but then it uses the push button to send the message.Since I am really a beginner, I am not sure if all the new lines of code are needed but the code seems to work fine. If it helps, here is what I did was:

a) after the while loop in which the end point tries to join the network   while (SMPL_NO_JOIN == SMPL_Init((uint8_t (*)(linkID_t))0)) {.....} I stopped the timer (btw, I am using TimerB instead of the original TimerA):

  TBCCR0 = 0;   // we used the timer to join the network, now stop it