Hello,
I have 2 new
eZ430-RF2500DK kits, with the Out-of-the-box Temperature Sensor
Demo which gives me 4 targets eZ430-RF2500T v1.0: 2 Access
Points (AP) and 2 End Devices (ED), Out-of-the-box. I installed the
viewer from SLAC139c and the 3-node star network (1AP + 2EDs)
works very well with the visualizer software running on a PC, displaying
temperatures from all 3 nodes.
Before I get into any actual
development I wanted to verify that I
have the capability of bringing any target board back to an
original state, whether it is the AP or the ED.
So I
picked the 4th target (out of the box AP) and tried to
re-program it as ED, with a goal to verify the 1AP+3EDs
functionality, then program it back as AP and verify the 2EDs
with this re-programmed AP, yet again.
I downloaded the SLAC50x
(Free IAR EW-Kickstart 6, v5.10.1) from the TI site and followed the
SLAU227E (eZ430-RF2500 Development Tool User's Guide, page 13) to
download the SLAC139c Temp Sensor Demo code, Make as "AP", then Download&debug,
then pull the target (newly programmed as "AP") from the USB
port and re-inserted it into the PC and tried to verify the functionality. Later, in a similar fashion, programmed the same target as
ED and tried to verify the functionality.
Now, the PROBLEM:
If I program the target as an AP,
it does measure its own temperature and voltage and sends it to the
PC but it does NOT talk to the out-of-the-box EDs. The re-programmed
AP has red LED ON while green LED blinking in about a second interval.
If I program
the target as an ED, it does not talk to the out of the box AP
either. The re-programmed
ED LEDs are blinking in the same fashion as the out-of-the-box ED with no AP to connect to.
I didn't want to re-program yet another target yet before I
get a confirmation of (in)compatibility between the OutOfTheBox targets v1 and SLAC139c Demo code.
Is there a known incompatibility or
am I doing something wrong?
Any thoughts / suggestions are appreciated.
Thanks, Jiri
