eZ430-RF2500 Demo Software compile error (IAR)

This error is generated when the declaration for __low_level_init is different between the one in bsp_board.c and the one in intrinsics.h found in your IAR installation (under \430\inc). Open these 2 files and compare the declarations, most likely the return types will be different. Try changing the return type in bsp_board.c to match that in intrinsics.h. There may be a couple of places where you may need to do this.

Also refer to this post: http://e2e.ti.com/support/low_power_rf/f/156/p/16496/107818.aspx#107818

ok, I will check it the both files out. It seems odd that the example code that is zipped(downloaded) from the TI website would have this error without me even starting to do anything.

I looked at the link you posted at the top. Looks like IAR is where the change happened. I am trying to change the .h file, but it does not allow me. Is there a trick to this? Or do I have ti create a new .h file.

Thanks

I did some editing on the .c files to match. It compiled fine but somehow the ED never links to the AP. I can see the AP data on the Sensor Monitor, but no ED. The ED light just blinks real slow.

I have the same problem.

Could not get CCS to work with building the endpoint, so  used IAR.  Changed the bsp_board.c to correct the error;
Download/program/ breakpoints OK on the endpoint.

Problem:  Now the EP doesn't connect to the access point.

There seems to be an incompatibility between the as-shipped firmware and the source code provided.

Any help on this would be great: I'd rather work on the sensor application than try to debug RF.

Thanks!!

Obviously:  Just needed to build/program the access point.  Without a non-usb COM port to feed the terminal app, the AP splash screen
can't be viewed, so I'm not sure what the as-shipped version was; now, both AP and ED are 1.03, communicating OK.

So:  If you update the End Device code, you will likely need to build/program the AP to sync version.

HTH-- JLC

Just to run this into the ground:
I got the CCS build / prog process to work, but an ED built/prog with CCS  appears to not be compatible
with an AP built/prog using IAR..... using the same source tree (slac139c).

Updating the AP (yet again)  with the CCS build restored communication.
Seems obvious to not mix tools within a solution: I have verified that this is a bad idea. ( insert emoticon here)

-- JLC

I thought I did recompiled and uploaded the ED code. i will try again and see what happens. How many place did you need to edit to get the code to work. I think I edits in 2 places. I will post the lines I edited later on today.

I shelved the project since the last time I wrote on this thread.

I just downloaded the IAR KickStart and also the new eZ430-RF2500 codes from the Ti website.

Open it on Kickstart and compiled the AP and ED. Both compiled fine. But when I click on "Make" I get this error.

Building configuration: Sensor_Demo_AP_as_Data_Hub - CC2500 Sensor Demo-Access Point
Updating build tree...
Linking
Fatal Error[e89]: Too much object code produced (more than 0x1000 bytes) for this package
Error while running Linker
 
Total number of errors: 1
Total number of warnings: 0

Anyone know what this mean?

Thanks

Hi I have the same proble.

Joe Curren said:

Problem:  Now the EP doesn't connect to the access point.

I am using IAR v5.10 30 days trial. Both ( ED and AP) compiles and dowloads  OK but the ED never connect to AP. Is ther problem with IAR or something? How solve the problem?