RZB-CC16C-ZDK User Manual
Contents
1. Hee l oo u ee 4 2 ee E ee 2 2 7 ee Oe 2 shi jee ee E 00 e I i d ee 2 5 ee eo 14 26 me ow i ga s d R23 3 J lo uy E mns zi AE 22 SH ico L JBE pog R33 m Sc Rid R28 uu 8 ee R34 R35 B ee Rss po TP1 10 H 1 GND 1 C45 E 221 Ex juo d RM 95 D3 mm e 1 e o e 0 eo e Q E Os ITERATION SCH _S2 PCB _P11 242 X IE d pq E sd qe pe db o d b pe ce Met N Figure E 1 PCB Top View RZB CC16C ZDK User s Manual Rev 1 1 37 39 December 2006 Figure 2 Bottom View RZB CC16C ZDK User s Manual Rev 1 1 38 39 December 2006 24 NESAS Applications Engineerin Appendix H Other Resources 1 For details on how to use the In Circuit Debugger and Programmer please see the RTA FoUSB MON User s Manual Start gt All Programs gt Renesas gt CC16C ZDK gt RTA FoUSB Mon Manual 2 For updates and other evaluation tools and sample programs for the RZB CC16C ZDK Kit see http america renesas com ZigBee RZB CC16C ZDK User s Manual Rev 1 1 39 39 December 20062. 33 b f ESI 12219 9433999 119939 H 3 s aene TO l g HY Ss adele d A 5 Hb BH DVDD_3 3V z M30280F o 43 24 18 o RENESAS e ae P E l us PT T 5 ES 5 32 4 gt le 23 5 E coh 52 MR 5 a lo x ant AX Thi b W a z 38 noo SORIA p B GAYE ndul 8 i gab 7 z RZB CC16C ZDK User s Manual Rev 1 1 35 39 December 2006 Applications 21 NESAS T 10 z 5002 62 SUNT Ex usp zo L 000 HOS Jaquin jueunooq azy Q8 8202 824 qwiondid VONA WONO x SNOILVOINDININOO NO TV L 92 52 vZ tz A 514 Agee A81 3022 3022 552 OZvzO el It N 938A 11531 PS 0 ino Z1S31V
3. Flash ROM 96kB 94kB user available due to kernel Connectors J1 J4 Four 2 10 measurement test points connected to the MCU pins Can also be used to connect your own expansion boards via 2x10 headers J7 In Circuit Debug connector UART1 for FoUSB ICD P1 9 Sub D RS232 connected via RS232 transceiver to UART2 Jumpers JP1 MCU Power for Measurements JP2 Power LED and RS232 Power connect Switches S1 pushbutton connected to 10 4 S2 pushbutton connected to 10 5 S3 pushbutton connected to P10_6 S4 pushbutton connected to Reset SW1 Power source select switch If set toward the ICD connector power provided by ICD If set toward the power connector power provided via power connector LEDs D1 Red User output connected to P3_4 D2 Yellow User output connected to P3_5 D3 Green User output connected to P3_ 6 D4 Red Power On if jumper JP2 shorted LCD 2 line x 8 character LCD with 50066 controller IC 8 2 Power Supply Requirements The RZB CC16C ZDK Board will draw about 35mA with no LEDs on With the ICD powered from the board the current draw will be about 85mA The board has a 3 3V low dropout voltage regulator with an input voltage range from 3 4V to 16V 8 3 Operating Environment Table 8 2 lists the environmental conditions for using and storing the RZB CC16C ZDK board Store the board in a conductive bag inside the original fact
4. LEDs Push Buttons 51 53 Analog Adjust R44 Figure 6 1 RZB CC16C ZDK Board RZB CC16C ZDK User s Manual Rev 1 1 16 39 December 2006 431 NESAS Applications Engineerin 6 2 RZB CC16C ZDK Board Block Diagram The RZB CC16C ZDK board incorporates an M30280FAHP 80 pin QFP from the M16C 28 group of microcontrollers designated U4 Figure 5 2 shows the RZB CC16C ZDK block diagram X JE Ee 10_4 Pio 5 P10 e Reset 2 fani fano 8 characters 20 06 XCin XCout x 2 lines LCD J7 ICD Header M30280FAHP Red Yellow Green MCU LED LED LED 5 4P36 RS232 ransceive Voc JP2 Jp1 Wee RS232 MCU Power Power for Measurements J1 J2 J3 J4 ZigBee Figure 6 2 RZB CC16C ZDK Block Diagram Red Power LED 6 3 M16C 28 Group of MCUs The M3028x group of 16 bit single chip flash microcontrollers MCU is part of the M16C 60 series CPU core The hardware and software manuals for the M16C 28 group of microcontrollers can be found under C Renesas RZB CC16C_ZDK Docs folder on your PC or from the Start menu Start gt Programs gt Renesas gt RZB_CC16C_ZDK gt All Manuals and Documents after ZDK software installation 6 4 RZB CC16C ZDK Board Jumper Configuration 6 4 1 JP1 MCU U4 Power JP1 is used to connect the Vcc pins of the M16C 28 MCU to the 3 3V supply of the board It can be used to measure current power consumption
5. 29 C 1 Program the RTA FoUSB Mon as an In Circuit Debugger a 29 Appendix D Reference 22004 400000 31 Appendix E Expansion 2 111 32 Appendix F Board Schematic amp 34 Appendix G RZB CC16C ZDK Printed Circuit Board n n 37 Appendix H Other Resources 39 RZB CC16C ZDK User s Manual Rev 1 1 3 39 December 2006 434 NESAS Applications Engineerin 1 0 Introduction The RZB CC16C ZDK kit is a low cost ZigBee demonstration kit for evaluating wireless ZigBee connectivity solutions based on the Renesas M16C 28 group of microcontrollers MCU A small ZigBee Personal Area Network PAN can be set up monitored and analyzed with the included hardware and software The kit contains an USB dongle that functions as an RF Sniffer Interface RFSI RF Sniffer software installed on the PC allows you to record and analyze ZigBee data packets The software can also display the network topology of a ZigBee network For more information on the RF Sniffer software and hardware see the RF Sniffer User s Manual accessible via Start gt All Programs gt Renesas gt RF SnifferV x xx A RTA FoUSB MON Flash Programmer and In Circuit Debugger ICD included in the kit allows you to r
6. Dongle Figure 4 1 ZigBee Demo Setup Optional only required if you want to update firmware and or develop code In Circuit Debugger and Programmer ICD Mini USB cable for ICD 2x5 header target cable for ICD Software Tools HEW IDE NC30 Compiler Linker FoUSB Programmer Figure 4 2 shows an ICD unit connected to a PC via USB and to a ZDK board via 2x5 pin ribbon cable RZB CC16C ZDK User s Manual Rev 1 1 7 39 December 2006 21 NESAS Applications Engineerin RZB CC16C ZDK Board PC with Windows 98SE 2000 Me or XP Mini USB Cable ATA FaUSR MON propane are Figure 4 2 ZDK Development System Connectivity 4 1 Host Computer Requirements The minimum requirement to be able to use the software that comes with the RZB CC16C ZDK is a PC with a USB port and Microsoft Windows 98 ME 2000 or XP 4 2 RZB CC16C ZDK Boards The three RZB CC16C ZDK boards are pre programmed with ZigBee demo firmware to provide a demo and evaluation environment for wireless ZigBee connectivity based on Renesas MCUs See section 6 0Hardware for more details 4 3 RF Sniffer Interface RFSI The RF Sniffer Interface RFSI is a 2 4GHz RF receiver USB dongle made by Integration See the RF Sniffer User s Manual for more information on RF Sniffer usage and features 4 4 RF Sniffer Software and USB Driver The installer program offers you the option to install the ZDK demo software tools and th
7. Rev 1 1 5 39 December 2006 434 NESAS Applications Engineerin 3 0 Limited Guarantee and Support Renesas Technology America Inc warrants the RZB CC16C ZDK to be free from component or assembly defects for a period of 180 days from the date of purchase Settlement is limited to repair or replacement of the product only Renesas Technology America Inc does not assume any liability arising out of the application or use of any product circuit or procedure described herein No other liability or warranty applies expressed or implied Software warranty is limited to replacement of the CD only While every attempt has been made to ensure accurate documentation Renesas Technology America Inc cannot be held responsible for errors or omissions and reserves the right to make changes without prior notice Flash Over USBP is a trademark of Renesas Technology America Inc All other trademarks are the properties of their respective owners RZB CC16C ZDK User s Manual Rev 1 1 6 39 December 2006 21 NESAS Applications Engineerin 4 0 System Connectivity The following lists the hardware and software products required for using the RZB CC16C ZDK ZigBee Demonstration Kit Host Computer supplied by user Three RZB CC16C ZDK Boards Three battery packs with AA batteries RF Sniffer USB Dongle RF Sniffer software and USB driver ZigBee ZigBee ZigBee Coordinator Router Router 1 INTEGRATION HE RF Sniffer USB
8. SvIgu wms 280 SEE Mi lt N3 O3HA N3 99 34 LL I 2555 ulasay 1 5 oo v js gr 0 D os AVAL TIN OSTXZT P 0 28 Pat iZ 3809 ansa Is TE T BEIN 2 L qum T savad ansa 4198 ME 290 n Od Ww an9a I de F d d Y 9 v99 09 p e Nay dodid 25 HUP HOLIMS XHXL 0313 0313729 ddu 291 191 S ENS T WoWHILI IIN OSIXZI NO H31N32 DIN Lge gg Ley TF tal ON 7 aanv _ ep 5 MS quvn q 13H oav Quyn9 A 4 5 Z ou 4 2 2 z 25 as s 55 55 55 os 58 os anyo 2 e _ 4 GGA viona zz z OSIW 29 ISON 22 419 99 82792 December 2006 36 39 RZB CC16C ZDK User s Manual Rev 1 1 434 NESAS Applications Engineerin Appendix G RZB CC16C ZDK Printed Circuit Board T M 4 0 RENESAS E s eeoooooooo NM m ee 1 2 P1 o ee s m
9. files for the compiler have been configured to create an ERROR message if you try to allocate too much RAM at compile time RZB CC16C ZDK User s Manual Rev 1 1 14 39 December 2006 434 NESAS 5 2 10 ZigBee Stack Table Sizes Table 5 4 ZigBee Stack Table Sizes Applications Engineerin ZigBee Coordinator amp Router Number of Entries ZigBee End Device Number of Entries Neighbor Table 15 4 Router Table 15 0 Router Discovery Table 15 0 Broadcast Transmission Table 20 20 5 2 11 Other Limitations The RZB CC16C ZDK provides sophisticated debugging features at a low cost but it does have some limitations when used with the HEW software debugger and ICD Those limitations are described in more detail in the RZB CC16C ZDK User manual Start gt All Programs gt Renesas gt CC16 ZDK gt Manuals and Documents RZB CC16C ZDK User s Manual Rev 1 1 15 39 December 2006 241 NESAS Applications Engineerin 6 0 Hardware 6 1 ZDK Board RZB CC16C ZDK Note The RZB CC16C ZDK board is referred to as RZB CC28 BRD on the board s silkscreen and schematic drawing Figure 5 1 shows the RZB CC16C ZDK Board with major components identified 16 MCU Photo Sensor aue Thermistor In Circuit Debug o an f Connector ICDF 2655 2895 6 103 Power Switch Power _ h ac Connector OH NES Reset Switch 8 character x 2 lines LCD
10. the Update Driver button Select Display a list and click on the Have Disk button Browse to the C Renesas FoUSB USB Drivers directory and install the usbmon sys driver awn RZB CC16C ZDK User s Manual Rev 1 1 23 39 December 2006 431 NESAS Applications Engineerin 6 If this process does not work please follow the instructions below If you encounter problems on installing the drivers you can try the following Windows 2000 a Copy the fousb inf and usbmon inf files from the C Renesas FoUSB USB Drivers folder to the WINNT INF folder b Copy the fousb sys and usbmon sys files from the C Renesas FoUSB USB Drivers folder to the WINNT SYSTEM32 drivers folder Windows 98 or XP a Copy the fousb inf and usbmon inf files from the C Renesas FoUSB USB Drivers folder to the WINDOWS INF folder b Copy the fousb sys and usbmon sys files from the C Renesas FoUSB USB Drivers folder to the WINDOWS SYSTEM32 drivers folder A 3 Debugging Problems This section discusses the cause of the problem and countermeasures to resolve it The common problems encountered with debugging are e Erratic debug behavior e Cannot connect to target e Issues that may come up during debug operations A 3 1 Erratic Debug Behavior HEW allows you to launch multiple instances of itself However if more that one instance of HEW is open during a debug session erratic behavior can result Running the FoUSB Prog
11. the commercial version except that link size will be restricted to 64 Kbytes after 60 days from when you begin using the compiler Contact your local sales representative if you wish to purchase a full license 4 6 3 HEW Debug Interface HEW communicates with a kernel i e a ROM monitor program on the target MCU through the ICD This debug interface provides a highly efficient evaluation environment Features include Source level debugging for assembly and C language Single step command unlimited breakpoints Run command with 6 breakpoints for the M16C 28 RAM monitor function e C variable watch window Note The number of breakpoints will vary depending on the M16C flash MCU used 4 6 4 FoUSB Flash over USB Programmer The Flash Over USB Programmer application provides In System Programming capability for the starter kit or any target board using an 16 family flash MCU e g R8C 16 32 Please see the RTA FoUSB MON User s Manual for more details RZB CC16C ZDK User s Manual Rev 1 1 9 39 December 2006 41 NESAS Applications Engineerin 5 0 ZigBee Evaluation Kit ZEK The ZigBee Evaluation Kit ZEK which is included with the RZB CC16C ZDK kit provides a ZigBee stack and a real time operating system RTOS for the stack in binary form Your own application code can interface to the ZigBee stack via documented Application Programming Interface API function calls Two binary file
12. 11 71 P10 ANa Klo 12 52 P4j INT INPC1 IDU 12 72 10 13 53 P1gINT IDW 13 73 10 14 54 1 14 74 P10 AN 15 55 14 15 75 AVss 16 56 P13 ANo3 16 76 100 17 57 1 11 18 58 P1 AN24 18 78 AVcc 19 59 1 20 19 79 P97 ANo7 Sing 20 60 PO7 ANoz 20 80 96 RZB CC16C ZDK User s Manual Rev 1 1 33 39 December 2006 434 NESAS Applications Engineerin Appendix F Board Schematic amp BOM Note The RZB CC16C ZDK board is referred to as RZB CC28 BRD on the board s silkscreen and schematic drawing The circuit board schematic and Bill Of Materials BOM are available as separate PDF documents They can be accessed through Start Programs Renesas RZB CC16C ZDK Board Hardware or by browsing to the folder C Renesas RZB CC16C ZDKNDocs and opening the files RZB CC28 BRD BOM pdf RZB CC28 BRD Schematic pdf RZB CC16C ZDK User s Manual Rev 1 1 34 39 December 2006 E t NI ESAS Applications Engineering b A a 5 gx s g 5 8 N j 343 IET 3 ae 3 3885 z g _ aL Bs z epe P 28 5 8 E gm ph d i 3 sce LD JE
13. 24 NE SAS Everywhere you imagine Applications Engineering ZigBee Demo Kit ZDK RZB CC16C ZDK User s Manual Rev 1 1 December 2006 44 NESAS Applications Engineerin Table of Contents 1 0 Intro dictionis seo ote ote 4 2 0 Contents of Product Packages 5 2 1 RZB CC16C ZDK ZigBee Demonstration Kit Item 5 e AC DR OM mL 5 3 0 Limited Guarantee and 6 4 9 System eee Lees Te uq Aaa tua Saa oa 7 4 1 Host Computer Requirements nn nennen nnns 8 4 2 RZB GC16C ZDIK Boards eee eret eee 8 4 3 RE Sniffer Intertace RESI iere oa te ee ER E ee ap EEA a 8 4 4 RF Sniffer Software USB 8 4 5 In Circuit Debugger and Programmer 9 4 6 Software Development Tools I nn 9 4 6 1 HEW High performance Embedded 9 4 6 2 NC30WA Evaluation Version C 002 nennen 9 4 6 3 HEW Debug Interface suu u int RR ARRA RUBRI RU 9 4 6 4 FoUSB Flash over USB V 9 5 0 ZigBee
14. C ZDI s cic ire gets i teet e EP ERR Pale re 16 6 2 RZB CC16C ZDK Board Block 17 6 3 M16C 28 Group of MCUS ts iis inn asiento EO Pere a e EE ete RED 17 6 4 RZB CC16C ZDK Board Jumper eee 17 6 4 1 9P 1 MGU WA Powers ed t ete edere Be edat cte 17 6 4 2 JP2 Power LED D4 and RS232 07 Transceiver 18 0 4 3 Default Jumper Settings 5 sc sees eed o rer f Me ep d ederet da 18 6 5 LCD Liquid Crystal Display enne nennen enn 18 6 6 ZIgBee RE eoe et adc tad Mr Mer edis td 18 7 0 System Operation amp 19 7 1 Kernel ROM Monitor 19 7 2 Pin and Peripheral Limitations 19 7 3 Memioty Map c dne et RUN re RU pde HIN eed eps eta ree I ee eed 19 7 4 Register Operation 20 7 5 Limitations on Interrupts Vectors that Reside the Hardware Vector Table 20 7 6 Stop or Wait Mode 21 RZB CC16C ZDK User s Manual Rev 1 1 December 2006 431 NESAS Applications Engineerin 7 7 User Program s Real Time Capability sese 21 7 8 Performing D
15. Evaluation R teri eter etas 10 5 1 Creating Your Own 10 5 1 1 ZigBee Demo Configurations 10 5 1 22ZEKDemoic File ore Uere ee ete kamuu Aaa s ei 11 5 1 3 Stack RAM Usagge tatit eee edie eed den Hebe eu Ree dad nte de ce ER e etie kii v etd 11 5 1 4 Global Variable RAM 11 5 1 5 Customization of 5 12 5 2 Limitations of the ZigBee Evaluation 5 13 PARET CHR 13 9 2 2 System CIoCk 1 ite tete e ted aee dde ette e Med ad taeda a 13 5 2 8 Interm pts lane 13 5 2 4 Flash and de esate d nad 13 5 2 5 MAC Address Area diete e eec eed d ed bev ied cud e d bed dn a 14 S26 ZOROM Flash SIZE HEURE Eee d t De deed rig 14 5 221 ZDROM RAM SIZE ie dro en e e TUE d POE Den et PUR ee d tete ban 14 5 2 8 User Task Stack RAM eee aede Rd ai trepida he 14 529 User Global Variable RAM u nen rent Rd Dre o nOD re de e PE 14 9 2 10 ZigBee Stack Fable SIzes 2 inp eee pde ep PE Enter 15 5 2 1 Other Eimitations ae aee ere ED Rp eh EE EE PORE cte ERE 15 6 0 HardWate tevin D tpe rede ER EE ee eer dee ete dee RUE eI Ein re dye idR 16 6 1 ZDK Board RZB CC16G
16. akes up periodically to check for new data requires stack file ZbRom CC28 RFD Vxx mot 5 1 2 ZEK Demo cFile The file ZEK Demo c in the C NRenesasNRZB CC16C ZDKNSample CodeNZEK Demo ZEK Demo directory contains the C source code for the entire ZEK demo application Reset Initialization After the MCU comes out of RESET the RTOS and ZigBee stack are initialized and then the user task function task is called This function would contain your user application code Program Flow In the ZEK Demo program the app task function first initializes the MCU peripheral and stack settings Next the ZDK board s LCD prompts the user to choose the board s ZigBee device type by pressing the corresponding pushbutton below the displayed device type options Once a button press is detected the function MainLoop is called The MainLoop function implements a loop that will never return for the life of the program Receiving New Data When new ZigBee data packet is received the function AppDataIndication is called by the ZigBee stack Because not much time should be spent in this function the payload of the data is saved in a circular receive buffer In MainLoop the function ProcessNewData is called periodically to deal with any new packets The ProcessNewData function calls the function AppGetNextRxPacket to retrieve the data payloads that were saved in the circular buffer by the AppDataIndication function It is re
17. an be programmed into the M16C 28 using the FoUSB Programmer This procedure erases the kernel and leaves only the user program 7 2 Pin and Peripheral Limitations SIO UART1 pins are used for communication between the M16C 28 kernel on the RZB CC16C ZDK board and HEW through the ICD Do not connect these pins to any other circuit as UART1 cannot be used in the user program while using the Debugger For details please see the RTA FoUSB MON ICD User s Manual on Target M16C ROM Monitor Resources or related ICD application notes 7 3 Memory Map The amount and locations of memory used by the kernel on the RZB CC16C ZDK board s M16C 28 MCU are shown in Figure 7 1 RZB CC16C ZDK User s Manual Rev 1 1 19 39 December 2006 434 NESAS Applications Engineerin 00000h SFR Area 00400h Internal RAM Area 8kB 023FFh Reserved 0 000 High EW 2kB data block OF800h High E W 2kB data block 10000h Reserved E8000h User Flash ROM Area 96kB FFFFFh 00400h 0237Fh 02380h User RAM Area 8064 Bytes Kernel RAM 128 Bytes 023FFh Note User programs must not use shaded areas User Program Area 94kB Special Page Kernel Program Fixed Vector Area Figure 7 1 M30280FAHP Memory Map with the Kernel Program Note The kernel occupies memory associated with special page vector numbers 18 19 and 192 255 The user reset vector is re mapped to address FFFD8h by the kernel 7 4 Regis
18. ble BRK Instruction FFFE4h FFFE7h User inhibited Address Match FFFE8h FFFEBh User inhibited Single step FFFECh FFFEFh User inhibited Watchdog Timer FFFFOh FFFF3h User available Note 1 DBC FFFF4h FFFF7h User inhibited NMI FFFF8h FFFFBh User available RESET FFFFCh FFFFFh Reset vector Note 2 NOTES 1 The Watchdog Timer vector is shared with the oscillation stop and voltage detection interrupts The vector is available for oscillation stop and voltage detection interrupts but you must avoid using the vector for watchdog timer interrupts 2 The kernel transparently relocates the Reset vector to FFFD8H 7 6 Stop or Wait Mode Limitations While running the kernel with an application that uses STOP or WAIT modes care must be taken not to communicate with the MCU while STOP or WAIT is active avoid RAM monitor or memory window refreshes for example Breakpoints if used should be set at points in the code where it is known that the BCLK is running at a frequency greater than 250 kHz 7 7 User Program s Real Time Capability Please be aware that while the kernel is in a STOP state the hardware peripherals will continue to run Therefore interrupts may not be serviced properly In addition the watchdog timer will not be serviced and will likely time out if active While the kernel is in a RUN state there is no overhead on the application code unless a RAM monitor window is open This window requi
19. commended that you follow the same procedure for processing new data Address Book After a node joins the network it sends a message to the coordinator with its address The coordinator then adds that address to its address book which it then broadcasts to every device in the ZigBee network You can send a ZigBee message to a specific device in the network by turning the ZDK board s potentiometer to scroll through the available list of addresses and selecting the address of the desired destination device If the selected destination address is the ZDK board s own address the address will be changed to the network broadcast address OxFFFF The address book is not part of the ZigBee specification it is implemented in the ZEK Demo program simply as an application example 5 1 3 Stack RAM Usage Try to minimize the allocation of local variables that use stack space inside of functions Remember that your user application is running as a task in an RTOS with a limited amount of stack space allocated for it For this ZEK system that value is fixed and cannot be changed You must limit the RAM space used by your local variables and function calls to less than 100 bytes 5 1 4 Global Variable RAM Usage You may create as many global variables for your user program as RAM space is available 896 bytes A virtual RAM section at the start of the debugger s RAM has been created to warn you if you try to allocate too much global RAM Below is an example o
20. d and unlock the MCU then show it is connected as in the figure below ES E FLASH OVER use mee Select Unlocked Figure B 1 FoUSB Software Connected to Target Board e f the answer is no then Is the FoUSB software s remembered MCU type identical to your target board s MCU type If the answer is Click No in the popup window that offers to update your ICD s USB monitor code FoUSB will then prompt you to select the MCU type Select the correct type that sits on your target board Now the FoUSB software s MCU type matches the one of your target board but the ICD s MMI code still does not match Consequently FoUSB will again offer to update the ICD Continue with the yes section below to update the ICD If the answer is yes Update the ICD Important the ICD has to operate at 5V to update its MMI code However if the ICD is connected to the ZDK target board its voltage is pulled down to the 3 3V operating voltage of the RZB CC16C ZDK User s Manual Rev 1 1 27 39 December 2006 41 NESAS Applications Engineerin oo target board s MCU Therefore disconnect the ZDK target from the ICD Now click OK to update the MMI code After the MMI update has completed reset the ICD by unplugging the USB cable reconnecting the ICD to the target board and then reconnecting the USB cable The FoUSB software should now automatically detect and unlock the target board s MCU and display the MCU type w
21. d usbmon sys driver files to run HEW A 2 USB Driver Problems This part discusses how to fix common problems that may occur with USB driver installation The most common problem is that Windows did not properly install the USB drivers so that the ICD is not recognized An indication of this problem is the faster blink rate of the ICD s yellow Status LED of about 2 3 times per second When the driver is installed properly the yellow Status LED only blinks every second Before trying the following steps try re starting your PC to see if this resolves the problem You can check the USB Driver status using the Windows Device Manager Start gt Control Panel gt System Properties gt Hardware gt Device Manager gt Universal Serial Bus controllers If the Renesas FoUSB ICD appears under the Universal Serial Bus controllers with no red X or yellow exclamation point the driver was installed properly NOTE If you are using Windows 2000 or XP you will need Administrator privileges to be able to install the drivers For cases where Renesas FoUSB ICD appears with a red X or yellow exclamation point in the Windows Device Manager please try the following 1 Open the Windows Device Manager Start gt Control Panel gt System Properties gt Hardware gt Device Manager Universal Serial Bus controllers Double click on Renesas FoUSB ICD A Renesas FoUSB ICD Properties dialog box appears Click on the Driver tab and click
22. e RF Sniffer software For details on installation see the QuickStart Guide or instructions in the Appendix A of this manual RZB CC16C ZDK User s Manual Rev 1 1 8 39 December 2006 4341 NESAS Applications Engineerin 4 5 In Circuit Debugger and Programmer ICD The ICD provides a plug and play debugging and programming interface to the ZDK board via the host computer s Universal Serial Bus USB The USB port also provides power to the ZDK boards and ICD thereby eliminating the need for an external power supply Use of the ICD is required only if you need to update the firmware of the kit s boards or if you intend to develop and debug your own software If not powered by the ICD the kit s ZDK boards be powered by the included battery packs 4 6 Software Development Tools The installer program offers you the option to install all the development tools For details on installation see the QuickStart Guide or instructions in Appendix A of this manual A brief description of all the included tools follows Please refer to the individual tool manuals for detailed information 4 6 1 HEW High performance Embedded Workshop HEW provides a Graphical User Interface GUI that integrates the software development tools and includes the C compiler assembler linker debugger and editor 4 6 2 NC30WA Evaluation Version C Compiler The evaluation version of the M3T NC30WA C compiler is provided with the same functionality as
23. e address you pick is unique and different from any address used by your other ZDK boards 5 2 6 ZbROM Flash Size The ZbROM area contains the ZigBee protocol stack and the RTOS used by the stack The ZbROM image occupies the two lower 32kBytes MCU Flash memory blocks for a total of 64kBytes This allocation was done to prevent the code from being erased by the debugger when downloading your user code The actual Flash memory size used by the ZigBee stack and RTOS will be less depending on ZigBee stack configuration settings when using the full development environment 5 2 7 ZbROM RAM Size The RAM allocated for use by the ZigBee stack and RTOS is the maximum amount that would be used if the device were to function as a ZigBee coordinator The actual RAM size used by the ZigBee stack and RTOS will be less for other ZigBee stack configurations when using the full development environment 5 2 8 User Task Stack RAM Your user code main program will run as an independent task of the RTOS which means that your stack is located in the same RAM area as the ZbROM RAM Therefore the user stack size available to you for function calls and local variable storage is limited to under 100 bytes 5 2 9 User Global Variable RAM The amount of RAM left over after the allocation of RAM for the ZigBee stack RTOS and the FoUSB In Circuit Debugger is 896 bytes at address 0x2000 0x237F This address range can be used to store global variables The C startup
24. e program the demo boards and to run and debug code The ICD and firmware provide a convenient Universal Serial Bus USB interface between the ZDK boards and the host PC This interface reduces resource requirements on the M16C 28 MCU and allows faster code downloads It also can be used with many other Renesas Flash MCUS starter kits and your own Renesas MCU based target boards Three ZigBee Demonstration Kit ZDK boards come pre programmed with demo software that enables you to quickly set up a small ZigBee PAN comprised of a ZigBee network Coordinator and two ZigBee network Routers The kit comes with a complete software development tool chain for Renesas MCUS including High performance Embedded Workshop HEW which includes Integrated Development Environment IDE Graphical User Interface GUI and Software Debugger NC30WA C compiler assembler and linker and Flash over USB FoUSB Programming software A real time source level debug environment is implemented using the HEW debugging interface with the RTA FoUSB MON Flash Programmer ICD The Flash over USB FoUSB Programmer software in combination with the ICD allows in system programming of the M16C 28 Flash MCUs on the ZDK and RF Sniffer target boards RZB CC16C ZDK User s Manual Rev 1 1 4 39 December 2006 21 NESAS Applications Engineerin 2 0 Contents of Product Package This section describes the contents of the RZB CC16C ZDK product package When unpacking y
25. ea The procedure to activate the boot mode to re program the Flash firmware is described in the following steps C 1 Program the RTA FoUSB Mon as an In Circuit Debugger 9 Unplug the RTA FoUSB MON unit from both its target and from the USB cable 10 Remove the black plastic case 11 Shunt JP1 with a 2 54mm 0 100 mil jumper This will configure the ICD to run in boot mode when it is powered up T Arto ere lm m d Figure C 2 Boot Jumper Location 12 Make sure that the power switch is set to the USB position so that the unit is powered via the USB bus 13 Plug the USB cable back in The RTA FoUSB MON will now be in boot mode and will communicate as a USB device to the PC In boot mode the RTA FoUSB MON uses a different USB Driver than the In Circuit Debugger Programmer application so you will need to load another USB Driver when doing this procedure for the first time The Windows New Hardware Wizard should automatically start and guide you through the installation of the required USB driver The driver is located in C Renesas FOUSB USB Drivers 14 Open the Flash Over USB program Note that the MCU device name displayed in green on the front screen will automatically change to M37641F8 the MCU inside the RTA FoUSB Mon without having to select that device 15 Click on the Load MMI button on the right This opens a chip selection window RZB CC16C ZDK User s Manual Rev 1 1 29 39 December 2006 Applicat
26. ebug Using nene nee 21 8 0 RZB CC16C ZDK Board amp 22 8 1 Hardware Specrficalloris um uu u bed ERAN sacl ke ME achete desee deas thus 22 8 2 Power Supply REQUIFEMENIS uu tice le pore her te t eder hase a a e Aedes und entice 22 8 3 Operating Erivironirrient 2 iin ior acc epo eg co ae E ED debe RI LAORE SYM eO Pd AE 22 Appendix A Troubleshooting et RR bebe er Rare ie a iei Melee edax aa 23 A1 Manual 23 AZ USB Driver Problems menses unu uu ul a t bereitet ker 23 3 u to it tret beoe ordre Be dices ebbe RR Lect 24 A 3 1 Erratic Debug Behlavigr x re edere ran eter Ra ee ee MEE ER asusta 24 3 2 Cannot Connect to Target cafe teen e eee audet 24 A 3 3 Issues that May Arise During Debug Operations 25 Appendix B Updating the ZigBee Development Kit ZDK Board Firmware 27 B 1 Programming the ZDK Board with with ZigBee Demo 27 Appendix C Updating the RTA FoUSB MON
27. em Limitations when Debugging Item Please Refer To 7 2 Pin and Peripheral Limitations 7 3 Memory Map User Limitations 7 4 Register Operation Limitations 7 5 Limitations on Interrupts Vectors that Reside in the Hardware Vector Table 7 6 Stop or Wait Mode Limitations 7 7 User Program s Real Time Capability Debugger Limitations 7 1 Kernel ROM Monitor Introduction During debug a small program called a kernel is uploaded to the M16C 28 The kernel communicates with HEW through the ICD regarding MCU status during user code debugging operations There are no special steps required in the user program to make use of the ICD The operation of the kernel is transparent to the user but there are some limitations These are discussed from section 7 2 onward After starting a HEW debug session the ICD uploads the kernel to the M16C 28 if it does not exist e g a blank device or a device that was programmed with the FoUSB Programmer After downloading the kernel the M16C 28 is ready to download user code Connecting the ICD without starting HEW will not affect the signal lines connected between the ICD and the M16C 28 the ICD keeps the signal lines in high impedance state The ICD only drives the pins after HEW or the FoUSB Programmer attempts to connect After completing program debug and verification with HEW you can create an image of your code in Intel hex or Motorola mot file formats This image c
28. f the linker warning you will receive if you exceed the available RAM space RZB CC16C ZDK User s Manual Rev 1 1 11 39 December 2006 434 NESAS Applications Engineerin Phase M16C Linker starting C NWorkSpaceNtestNtestNsect30 zek28 inc 186 Warning 1n30 C WorkSpace test test Coord Router ncrt0 zek28 r30 DATA section debugger NE is overlapped on the bss NE from 2380H to 2380H 5 1 5 Customization of Settings The following definitions can be changed at the top of the ZEK Demo c file to fit your requirements ZigBee Configuration define DEMO CHANNEL 24 define SCAN CHANNELS DWORD Ox1 lt lt DEMO CHANNEL Only scan our demo channel define SCAN CHANNELS Ox7FFF800 Scan every channel Lr Lr ASCII Input define MAX SERIAL INPUT 20 Address Book This array holds the addresses of all the nodes currently on the network It is updated only by the coordinator define MAX BOOK ENTRIES 32 RECEIVE BUFFER define RX BUFF SIZE 256 Circular buffer size for data payload all data is held in this one buffer define RX BUFF ENTRIES 16 Number of buffered packet that can be queued up RZB CC16C ZDK User s Manual Rev 1 1 12 39 December 2006 41 NESAS Applications Engineerin 5 2 Limitations of the ZigBee Evaluation System The followin
29. g is a list of limitations for the ZigBee Evaluation System ZEK platform Due to the nature of this evaluation system the MCU resources that you can use for your own application development are restricted In addition many of the configurations and customizations offered by the ZigBee protocol stack are unavailable to you with the ZEK Please do not modify or disrupt any of the MCU resources used by the ZigBee stack 5 2 1 Timers Table 5 1 MCU Timer Usage TAO available TA1 Used by ZigBee stack TA2 Used by ZigBee stack Used ZigBee stack TA4 Used by RTOS TBO Used by ZigBee stack TB1 available TB2 Used by ZigBee stack 5 2 2 System Clock After reset the main system clock denoted in the spec as f1 is set up to run at 20MHz The ZigBee stack assumes that the MCU is running at this operating frequency Please do not make any changes to the clock 5 2 3 Interrupts The interrupt vector table is located in the ZigBee stack and real time operating system RTOS program memory area ZbROM Therefore you cannot implement any interrupt sub routines other than Timer AO and UART 2 Receive To implement your own sub routines for those two interrupts you need to re direct their respective interrupt vectors to the location of your interrupt service routines by calling the pre defined functions SetTimerAOInt or SetUart2RxInt 5 2 4 Flash and RAM Usage The memory areas shaded in tu
30. ialog box that is displayed right after you start a debug session The selected MCU on the ICD board and the actual target MCU M16C 28 do not match Close the error message by clicking on the OK button then click on the Cancel button of the Init window Make sure you select M30280FA mcu If the MCU loaded on the ICD is different HEW will re program the ICD to match it e The target MCU is damaged Try a different target board and see if the HEW will connect You may have a damaged board or MCU A 3 3 Issues that May Arise During Debug Operations While debugging user code some issues may come up because the limitations discussed in section 7 0 System Operation amp Limitations were not satisfied The common issues are listed in Table A 3 including the countermeasures Table A 3 Problem Possible Cause s and Solution instructions HEW cannot stop After stepping few e Changes were made to the UART1 Special Function Registers SFRs Do not change UART1 SFRs in your code Breakpoints do not seem to work System is in FreeRun mode Change the RUN mode to Sampling from the Init window Emulator System icon HEW locks up cannot stop program or Communication error message is displayed Changes were made to the UART1 SFRs Do not change UART1 SFRs in your code Ensure that no limitations in Section 6 were violated Re initialize the system without closing debug sessi
31. ions Engineerin Load AAT Figure C 3 Load MMI Button 16 Select the MCU device of your target board to which you want to connect the RTA FoUSB Mon as an In Circuit Debugger not the MCU of the RTA FoUSB Mon unit and click the OK button to load the selected MCU Monitor Image MMI to the RTA FoUSB Mon Chip Selection Flash RAM 48K AK 4K 8 00 4K 4K 8 00 4K 8K 8 00 48K 4K 4K 8 00 a F8 AK 4K 8 00 30281 4K 8K 8 00 OK Help Cancel Figure C 4 Chip Selection Window 17 Unplug the USB Cable remove the jumper and enclose the board back into its case Now re attach the ribbon cable to your target board and re connect the RTA FoUSB Mon unit to your PC with the USB cable 18 After you connect the RTA FoUSB Mon to the PC the FoUSB Programmer should show the target MCU device name you selected earlier RZB CC16C ZDK User s Manual Rev 1 1 30 39 December 2006 434 NESAS Applications Engineerin Appendix D Reference Manuals Description Renesas ZigBee Demonstration Kit Document that will help you get started on using the 1 ZDK Quick Start Guide ZigBee Demonstration Kit 2 RZB CC16C ZDK User s Manual This document 3 RF Sniffer User s Manual Document describing the ZigBee RF Sniffer hardware and software in more detail 4 ZDK Board Schematic Schematic diagram f
32. ithout having to select the device Click Open in the left of the FoUSB program window and browse to the directory in which the demo firmware is stored C NRenesasNRZB CC16C ZDKNDemo Select the firmware file ZDK Demo Vxx mot where xx is the version number of the code A popup window displays the ID code of the firmware file you just opened Click OK Click Program in the left of the FoUSB program window In the Program Flash Window that pops up make sure Only Erase Blocks Needed is checked Click Program It is important that you only erase the blocks needed and not the entire Flash memory as each ZDK board stores a unique 8 byte MAC address that is factory programmed at Flash memory address 0 000 You do not want to erase the MAC address because the board will not be able to function without one RZB CC16C ZDK User s Manual Rev 1 1 28 39 December 2006 241 NESAS Applications Engineerin Appendix C Updating the RIA FoUSB MON Firmware This section discusses how to update the firmware of the RTA FoUSB MON hardware to function as an In Circuit Debugger ICD and Flash Over USB Programmer The ZigBee Development Kit contains an RTA FoUSB MON unit that has been pre programmed to function as an ICD Therefore you only need to read this section if for some reason the ICD firmware should get corrupted and you must update the firmware of the ICD The RTA FoUSB MON has a boot mode that can be used to program the MCU s user Flash ar
33. me more familiar with the ZigBee APIs before attempting to create a project using the Empty Project generator See the ZigBee Stack API Specification document Start gt Programs gt Renesas gt RZB_CC16C_ZDK gt All Manuals and Documents for a detailed description of the available ZigBee API functions Below are some specifics about the ZEK demo project that will help you get started 5 1 1 ZigBee Demo Configurations The demo code can be built to act as any of the following ZigBee device types by using the Build configuration pull down in HEW Please note that you have to download the correct ZigBee stack image separately as described in the section Downloading the ZigBee Binary Using the Flash over USB Programmer of the Quick Start Guide before you use HEW to load debug your own code Coord_Router Device can function as a ZigBee Coordinator or Router requires ZigBee stack file ZoRom CC28 FFD Vxx mot to be programmed into the ZDK board EndDevice Device will function as a ZigBee End Device and can receive data from its parent at any time requires stack file ZoRom CC28 RFD Vxx mot RZB CC16C ZDK User s Manual Rev 1 1 10 39 December 2006 41 NESAS Applications Engineerin EndDevice Polling Device will function as a ZigBee End Device but will only receive data from its parent when the End Device asks polls This configuration would be used for a battery powered device that sleeps most of the time and only w
34. of the MCU during various modes of operation For normal operations JP1 must be shorted JP1 is shorted by default RZB CC16C ZDK User s Manual Rev 1 1 17 39 December 2006 1 Applications Engineerin 6 4 2 JP2 Power LED D4 and RS232 U7 Transceiver Power JP2 is used to connect the Vcc pin of the RS232 transceiver chip U7 to the 3 3V supply of the board It also connects the red Power LED D4 to the board s supply It can be used to reduce the board s power consumption by disconnecting the RS232 transceiver and Power LED For normal operations JP2 must be shorted JP2 is shorted by default 6 4 3 Default Jumper Settings Table 6 1 Default Jumper Settings JP1 MCU Power Shorted JP2 Power LED and RS232 Power Shorted 6 5 LCD Liquid Crystal Display The LCD is a 2 line by 8 character display with a KS0066 controller IC 6 6 ZigBee RF The ZigBee RF circuit utilizes a Chipcon CC2420 2 4GHz IEEE 802 15 4 compliant transceiver IC RZB CC16C ZDK User s Manual Rev 1 1 18 39 December 2006 434 NESAS Applications Engineerin 7 0 System Operation amp Limitations The RZB CC16C ZDK provides sophisticated debugging features at a low cost but it does have some limitations when used with the debugger and ICD Section 6 1 introduces the kernel ROM monitor program and its purpose The limitations when this kernel is running with the user program are listed in Table 7 1 Table 7 1 Syst
35. on See note below Do a hardware reset User program runaway may be corrupting the kernel RAM interrupt vectors flags etc Close the debug session hit the reset button on the ZDK board to reset the board then restart Download problems Filenames or directory names contain spaces or special characters HEW project was not properly set up startup files missing or out of order files added to wrong member etc Try creating a new project and adding your source files to it For details please see the HEW User s Manual To re initialize the system without closing a debug session try the following RZB CC16C ZDK User s Manual Rev 1 1 25 39 December 2006 434 NESAS Applications Engineerin Click the OK button on the error dialog box to close it When an Exit dialog box appears click the Cancel button to close it Press the reset button on the ZDK board Click the HEW Reset icon After initialization debugging can resume However it is recommended that you download your program again before debugging RZB CC16C ZDK User s Manual Rev 1 1 26 39 December 2006 41 NESAS Applications Engineerin Appendix B Updating the ZigBee Development Kit ZDK Board Firmware Your ZigBee Development Kit contains three ZDK boards that come pre programmed with ZigBee demo firmware In this chapter we show you how you can update or replace this firmware You can skip this chapter if you do not in
36. or the RF Sniffer and ZDK boards 5 ZDK Board BOM Bill of materials for the ZDK board 6 M16C 20 60 Series C Language ANSI C language programming guide for the Programming Manual M16C 20 60 series MCU T M16C 20 60 Series Assembly Assembly language programming guide for the Language Programming Manual M16C 20 60 series MCUs 8 HEW User s Manual This document describes installation and operation of this Integrated Development Environment for Renesas Tools 9 AS30 User s Manual Guide for AS30 assembler 10 NC30 User s Manual Guide for NC30WA C compiler 11 RTA FoUSB MON User s Manual In Circuit Debugger and Programmer User s Manual NOTE The installer will copy all these manuals during installation They can be accessed using the Document Descriptions file by clicking on Start gt Programs gt Renesas gt RZB 16 ZDK gt Document Descriptions RZB CC16C ZDK User s Manual Rev 1 1 31 39 December 2006 434 NESAS Applications Engineerin Appendix E Expansion Headers The M30280FA MCU on the RZB CC16C ZDK target board is housed in an 80 pin QFP package Pin 1 of the package is identified by a little white circle on the board s top silkscreen Connectors J1 to J4 located around the MCU provide access to almost all of the MCU s pins You can use J1 J4 as test points to check MCU signals or by mounting your own headers connect your own expansion board The silkscreen identifying the connectors is at the bottom of
37. ory packaging box Table 8 2 Operating Environment Environmental Condition Ambient Temperature Ambient Humidity Operating 0 55 C 30 to 80 non condensing No corrosive gas allowed Storage 30 to 75 C 30 to 80 non condensing No corrosive gas allowed RZB CC16C ZDK Users Manual Rev 1 1 22 39 December 2006 434 NESAS Applications Engineerin Appendix A Troubleshooting Guide This section discusses possible problems you may encounter while installing the development tool software USB drivers or running the HEW debugger and FoUSB Programmer applications This section also discusses the countermeasures and solutions to resolve these problems For troubleshooting information on the RF Sniffer Interface and RF Sniffer board see the RF Sniffer User s Manual If for any reason you cannot resolve the problem please contact your Renesas representative for assistance A 1 Manual Installation Before connecting the In Circuit Debugger to your PC the driver files inf and sys and executables must be copied to the C NRenesasNFoUSB directory To do this run FoUSB Vx xx exe in the NToolsNFoUSB directory of the CD After the FoUSB Programmer install assuming the default directory was used a C NRenesasNFoUSB subfolder should have been created The Windows USB drivers can be found under the USB Drivers folder i e fousb inf fousb sys driver files to run FoUSB Programmer usbmon inf an
38. our RZB CC16C ZDK please check to see that all items listed below are included 2 1 RZB CC16C ZDK ZigBee Demonstration Kit Item List Table 2 1 lists the items included in the RZB CC16C ZDK Table 2 1 RZB CC16C ZDK Item List Item Name Quantity ss 222 Remarks Sees RZB CC16C ZDK Board 3 ZigBee Demo Kit ZDK Boards pre programmed with demo software Integral USB Dongle 1 Integral 2 4GHz RF Receiver USB Stick used as the RF Sniffer Interface RFSI CD ROM Auto install program RF Sniffer software HEW IDE amp debugger NC30WA C compiler assembler and linker FoUSB Programmer USB drivers Manuals Tutorials Sample programs 2 1 1 CD ROM The CD ROM contains the electronic manuals and software necessary for developing programs Your computer must have a web browser like Mozilla Firefox Netscape Browser or Microsoft Internet Explorer to view the help files and Adobe Acrobat Reader to view the manuals Insert the enclosed CD into your computer and the installer will auto start The installer program will create C Renesas and C Workspace folders on your machine NC30WA FoUSB Programmer Documentation sample code and other ZDK related files are in the C Renesas folder HEW is installed in the C Program Files folder by default If the installer program does not start browse to the CD s root folder and double click on ZDK Installer exe to start the installation RZB CC16C ZDK User s Manual
39. rammer at the same time as HEW can also result in erratic debug behavior Lastly having more than one ICD installed can also cause erratic problems or cause HEW to crash A 3 2 Cannot Connect to Target When the message Can t connect with the target is displayed when attempting to connect there are several reasons that may have caused this message to appear Each cause and its corresponding countermeasure is discussed below e The ZDK board or the ICD are not connected correctly Unplug the ICD from the USB cable First connect the ZDK target board to the ICD via the supplied 2x5 header ribbon cable then connect the ICD back to your PC s USB port via the supplied mini USB cable Please see section 4 0 System Connectivity e The ICD has no power Power LED of the ICD is off Please ensure that the Power Mode switch on the ICD is set to USB and that the power switch on the ZDK board is set toward the ICD connector if you want to power the board from the ICD unit If you want to power the ICD from the ZDK target board the ICD power mode switch must be in the RZB CC16C ZDK User s Manual Rev 1 1 24 39 December 2006 41 NESAS Applications Engineerin Target position The target board then must be provided with its own power supply and the target board s power switch must be on in the correct position toward the power connector e USB was not selected on the HEW Init dialog box Please select USB from the Init d
40. res periodic communication with the MCU This communication suspends normal application operation while servicing the request approximately 2000 BCLK cycles for each 16 bytes of data displayed in the window are used per window update The user must determine whether this behavior is acceptable 7 8 Performing Debug Using Symbols Normally when a new project is created using HEW debugging symbols are enabled If you are unable to view the source properly during debug add the debug option g in HEW before compiling the programs To enable the 9 option perform the following Open the workspace and project in HEW Select Renesas M16C Standard Toolchain from the Options pull down menu Click on the Link tab Select Output under the Category list box Click on the checkbox for g Outputs source debug information Click on the OK button For more information see the HEW user s manual RZB CC16C ZDK User s Manual Rev 1 1 21 39 December 2006 434 NESAS Applications Engineerin 8 0 RZB CC16C ZDK Board Specifications 8 1 Hardware Specifications Table 8 1 lists the specifications of the RZB CC16C ZDK Board Table 8 1 RZB CC16C ZDK Board Specifications Item Specification MCU M30280FAHP Clocks Main Clock crystal 10 MHz PLL or ring oscillator Sub Clock 32 768 kHz crystal Memory RAM 8kB 8064 Bytes user available due to kernel ICD High E W Data Block 2kB x 2 4096 Bytes
41. rquoise are available for your use Table 5 2 Flash Memory Usage Flash Address Range Usage OxFF800 OxFFFFF FoUSB Monitor Area 2KB 0xE8000 0xFF7FF 0xC0000 0xE7FFF ZbROM Area stack and RTOS 64KB OxOF7FF OxOFFFF 0x0F000 0x0F007 MAC Address Don t Erase Block RZB CC16C ZDK User s Manual Rev 1 1 13 39 December 2006 21 NESAS Applications Engineerin Table 5 3 RAM Memory Usage RAM Address Range Usage 0x2380 0x23FF FoUSB Monitor Area 0x2000 0x237F 0x0400 0x1FFF ZbROM area user task stack 100 bytes 0x0000 0x03FF MCU Register Area We strongly recommend that you use the ZEK start up files located the C NRenesasNRZB CC16C ZDKNSample Code ZEK Demo directory for your project These start up files will greatly minimize the complexity of correctly initializing the MCU and locating your user program code and data into the available memory areas 5 2 5 MAC Address Area Every 802 15 4 radio needs a globally unique 64 bit MAC address Therefore your ZDK boards have been pre programmed with such an address Please do not erase the Flash block that contains this address If you accidentally do erase the MAC address you can find mot files with replacement addresses in the C Renesas RZB CC16C_ZDK Demos Replacement MAC Addresses directory Program one of those addresses into your board using the FoUSB programming software Please make sure that th
42. s are provided in the directory C Renesas RZB CC16C_ZDK Sample Code ZEK_ ZbRom ZbRom CC28 FFD Vxx mot contains the ZigBee stack and RTOS for Full Function Devices FFD i e ZigBee Routers or Coordinators The module also contains all necessary MCU initialization routines ZbRom CC28 RFD Vxx mot contains the ZigBee stack and RTOS for Reduced Function Devices RFD i e ZigBee End Devices It has a smaller memory footprint than the FFD binary leaving more memory available for your own application code The module also contains all necessary MCU initialization routines Sample projects for the Renesas High performance Embedded Workshop HEW allow you to quickly create your own ZigBee coordinator router or end device 5 1 Creating Your Own Program This section assumes that you have worked through the Quick Start Guide Please use the HEW project wizard as outlined in the HEW IDE QuickStart Section of the Quick Start Guide to create your own ZEK application Creating a ZigBee project from scratch is quite involved and the detailed steps to do this are not discussed in this manual To create a new ZigBee application using the HEW project wizard you have two options 1 You use the ZEK Demo project that you created in the HEW IDE QuickStart section 2 You can select Empty Project in the ZigBee M16C 28 Kit Step 2 window instead We recommend that you start out by modifying the ZEK Demo project until you beco
43. tend to update the ZDK board s firmware To update the firmware of the ZDK board you need an RTA FoUSB Mon In Circuit Debugger ICD B 1 Programming the ZDK Board with with ZigBee Demo Firmware 1 Connect the ICD s 2x5 header ribbon cable to the ZDK board Make sure the ICD s Power Mode switch is set to the USB position and the ZDK board s power Switch is set toward the ICD connector 3 Connect the ICD to the USB port of your PC 4 Start the FoUSB software Start All Programs Renesas Flash Over USB V x xx FoUSB Programmer To be able to program a target board successfully both the selected MCU type of the FoUSB programming software and the MCU Monitor Image MMI loaded into the ICD must be identical to the MCU type that is on your target board The FoUSB software remembers the type of the last MCU you have programmed If it detects a mismatch between the remembered MCU type and the MCU type of the ICD s MMI code also called USB monitor code it will prompt you to update that code However before you click OK on the popup window that offers to update your ICD you must determine the correct course of action Is the ICD s MCU type identical to your target board s MCU type e f the answer is yes Click No in the popup window that offers to update your ICD s USB monitor code The FoUSB software will then prompt you to select the MCU Select the correct type that sits on your target board FoUSB will connect to the target boar
44. ter Operation Limitations Table 6 2 lists the limitations on register operation The registers are inhibited from any modification If register contents are modified in any way ker Table 7 2 Limitations on Reg ister Operation nel operation cannot be guaranteed User and Interrupt Stack Pointers RAM memory range 02380H 023FFH is used by the kernel Do not set stacks in this area UART1 Transmit Receive Mode Register UART1 Transmit Receive Control Register 0 UART1 Transmit Receive Control Register 1 Do not change UARTI Interrupt Control Register 0 Do not change UART Transmit Receive Control Register 2 Do not change bits 0 and 2 UART1 Transmit Buffer Register Do not write to this register UART1 Receive Buffer Register Do not read this register Port 6 and Port 6 DDR To prevent changes on P6 4 data and direction use read modify write only instructions BSET BCLR AND OR etc 7 5 Limitations on Interrupts Vectors that Reside in the Hardware Vector Table Table 7 3 lists the limitations on hardware interrupt i e fixed vector addresses RZB CC16C ZDK User s Manual Rev 1 1 20 39 December 2006 434 NESAS Applications Engineerin Table 7 3 Interrupt Vector Addresses _ Interrupt Cause M16C 28 Vector Address Kit Specification Undefined FFFDCh FFFDFh User available Overflow FFFEOh FFFE3h User availa
45. the ZDK board The following table shows the mapping of J1 J4 pins to MCU pins and signal names n MCU Function MCU Function Pin Pin 1 14 P9J AN CLK 1 21 P7 TAsou 2 2 2 22 P7JTA W 3 P9 TBoin 3 23 P7 TAS W d P9 TBin 4 24 P74 CTS RTS 5 V ITXD 5 5 P9 TBon 5 25 P7 CLK JTA VIRXD 6 6 26 P7 RxDJSCL TAg CLK 7 7 27 P7 TxDj SDA TA oo 8 8 28 P6 TxD 9 9 29 P6 RxD 10 10 30 P6 CLK 11 11 Vss 11 31 P6 CTS RTS CTS 12 12 32 P3 13 13 Vcc 13 33 P3 15 15 P8JINT Zphase 15 35 P34 16 16 P8 iNT 16 36 P3 17 17 P8 INT 17 37 P32 Sour3 18 18 P84 TAgin U 18 38 3 19 19 P8yTA4 U 19 39 20 20 P7 TAsn 20 40 P6JTxDo RZB CC16C ZDK User s Manual Rev 1 1 32 39 December 2006 Applications Engineerin MCU Function MCU Function 1 P62 RxDo 1 POg ANos 2 42 P61 CLKo 2 62 POs ANos 3 43 P6 CTS RTS 3 63 POg ANoa 4 44 P27 OUTC17 INPC17 4 64 PO3 ANos 5 45 P26 OUTC1 INPC1 5 65 PO2 ANoz 6 46 P24 OUTC14INPC15 6 66 PO4ANo 7 47 P2 OUTC1 4 INPC14 7 67 POo ANoo 8 48 P23 OUTC13 INPC13 8 68 P107 AN7 9 49 2 gt 1 9 69 P10gANg KL 10 50 P21 OUTC1 INPC1 SCLuw 10 70 10 Kl 11 51 P2 OUTC1o INPC1 SDAmm
Download Pdf Manuals
Related Search