TI E2E Community
Low Power RF & Wireless Connectivity
ZigBee®, 6LoWPAN & 802.15.4 MAC Forum
How to compile CC2530ZDK sensordemo project?
I just bought CC2530ZDK, and started playing with it. I am totally new to this product and the tool chain.
I compiled the project "SensorDemo.eww", without making any change. I see the file "SensorDemo.d51" is generated in folder "\SensorDemo\CC2530DB\SensorEB\Exe". I have 2 questions:
1. How can I generate *.hex file like "SensorEB.hex"?
2. Do I need to config the same project file to generate other *.hex files? If this is the case, how can do it?
After playing around for some time, I know the answers now. However, the hex fileI generated did not work properly. I tried only CollectorEB. If I downloaded the CollectorEB.hex coming with sample, it worked fine. I noticed the hex file generated by me is slightly larger (326K vs. 322K).
I found tried the method in the following post, but it did not work either. Any suggestions?
Which version of Z-stack are you using? The SensorDemo files are currently built for Z-stack 2.2.0.
In order to make it work with Z-stack 2.3.0 there is a small change required in the project options:
- In IAR go to Project -> Options and select General Options
- Set Number of virtual registers to 16 instead of 8
You are right. I am using Z-stack 2.3.0. I saw another post reporting similar problem (http://e2e.ti.com/support/low_power_rf/f/158/p/33534/116689.aspx#116689), and tried to verify that using Z-stack 2.2.0, but could not find it anywhere.
After I changed the number of virtual registers from 8 to 16, now I can successfully program and debug CC2530 as collector.
During the process, I encountered another problem. If I generate the hex file, and write it to the CC2530 using TI Flash programmer, I have to uncomment the following two lines in f8W2530.xcl before compilation, according to post (http://e2e.ti.com/support/low_power_rf/f/160/p/18242/70813.aspx#70813).
// Include these two lines when generating a .hex file for banked code model:-M(CODE)[(_CODEBANK_START+_FIRST_BANK_ADDR)-(_CODEBANK_END+_FIRST_BANK_ADDR)]*\_NR_OF_BANKS+_FIRST_BANK_ADDR=0x8000
Why wasn't it a problem for IAR IDE?
When you generate debug files with IAR the lines with the -M option should be commented in the linker file.
When generatig hex files with IAR for banked code (like Z-stack) the same lines should be included.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.