How it Works
Renesas
Loading...
RZB-ZMD16C-ZDK
User Manual
33 pgs1.31 Mb0

Renesas RZB-ZMD16C-ZDK User Manual

Download
Applications Engineering
ZigBee Demo Kit (ZDK)
RZB-ZMD16C-ZDK
User’s Manual
Version 1.2 August 2006
www.renesas.com
Table of Contents
1.0 Introduction............................................................................................................................................. 4
2.0 Contents of Product Package................................................................................................................. 5
2.1. RZB-ZMD16C-ZDK ZigBee Demonstration Kit Item List................................................................... 5
2.2. CD-ROM ............................................................................................................................................ 5
3.0 Limited Guarantee and Support ............................................................................................................. 6
4.0 System Connectivity ............................................................................................................................... 7
4.1. Host Computer Requirements ........................................................................................................... 8
4.2. RZB-ZMD16C-ZDK Boards ............................................................................................................... 8
4.3. RF Sniffer Board................................................................................................................................ 8
4.4. RF Sniffer Interface (RFSI)................................................................................................................ 9
4.5. RF Sniffer Software and USB Driver ................................................................................................. 9
4.6. In-Circuit Debugger and Programmer (ICD)...................................................................................... 9
4.7. Software Development Tools ............................................................................................................ 9
4.7.1. HEW (High-performance Embedded Workshop)........................................................................ 9
4.7.2. NC30WA Evaluation Version C Compiler ................................................................................... 9
4.7.3. HEW Debug Interface ................................................................................................................. 9
4.7.4. FoUSB (Flash-over-USB™) Programmer................................................................................. 10
5.0 Hardware .............................................................................................................................................. 11
5.1. ZDK Board (RZB-ZMD16C-ZDK) .................................................................................................... 11
5.2. RZB-ZMD16C-ZDK Board Block Diagram ...................................................................................... 12
5.3. M16C/28 Group of MCUs ................................................................................................................ 12
5.4. RZB-ZMD16C-ZDK Board Jumper Configuration ........................................................................... 12
5.4.1. JP1: MCU (U4) Power............................................................................................................... 12
5.4.2. JP2: Power LED (D4) and RS232 (U7) Transceiver Power...................................................... 13
5.4.3. Default Jumper Settings............................................................................................................ 13
5.5. LCD (Liquid Crystal Display) ........................................................................................................... 13
5.6. ZigBee RF........................................................................................................................................ 13
6.0 Limitations of the ZbRom System......................................................................................................... 13
6.1. Timers.............................................................................................................................................. 13
6.2. System Clock................................................................................................................................... 14
6.3. Interrupts.......................................................................................................................................... 14
6.4. Flash and RAM Usage .................................................................................................................... 14
6.5. Stack RAM Usage ........................................................................................................................... 14
6.6. Global Variable RAM Usage............................................................................................................ 15
6.7. MAC Address Area .......................................................................................................................... 15
6.8. ZbROM Flash Size .......................................................................................................................... 15
6.9. ZbROM RAM Size ........................................................................................................................... 15
6.10. ZigBee Stack Table Sizes ............................................................................................................. 15
6.11. Customization of Demo Program Settings ....................................................................................16
6.12. Other Limitations............................................................................................................................ 16
7.0 System Operation & Limitations ........................................................................................................... 17
7.1. Kernel (ROM Monitor) Introduction.................................................................................................. 17
7.2. Pin and Peripheral Limitations......................................................................................................... 17
7.3. Memory Map.................................................................................................................................... 17
7.4. Register Operation Limitations ........................................................................................................ 18
7.5. Limitations on Interrupts - Vectors that Reside in the Hardware Vector Table ............................... 18
7.6. Stop or Wait Mode Limitations......................................................................................................... 19
7.7. User Program’s Real-Time Capability ............................................................................................. 19
7.8. Performing Debug Using Symbols .................................................................................................. 19
8.0 RZB-ZMD16C-ZDK Board Specifications ............................................................................................ 20
8.1. Hardware Specifications.................................................................................................................. 20
8.2. Power Supply Requirements ........................................................................................................... 20
RZB-ZMD16C-ZDK User’s Manual Rev 1.2 August 2006
8.3. Operating Environment.................................................................................................................... 20
Appendix A. Troubleshooting Guide........................................................................................................... 21
A.1 Manual Installation ........................................................................................................................... 21
A.2 USB Driver Problems ....................................................................................................................... 21
A.3 Debugging Problems........................................................................................................................ 22
A.3.1 Erratic Debug Behavior.............................................................................................................. 22
A.3.2 Cannot Connect to Target.......................................................................................................... 22
A.3.3 Issues that May Arise During Debug Operations ...................................................................... 23
Appendix B. Reference Manuals ................................................................................................................ 25
Appendix C. Expansion Headers................................................................................................................ 26
Appendix D. Board Schematic & BOM....................................................................................................... 28
Appendix E. RZB-ZMD16C-ZDK Printed Circuit Board.............................................................................. 31
Appendix F. Other Resources .................................................................................................................... 33
RZB-ZMD16C-ZDK User’s Manual Rev 1.2 3/ 33 August 2006
1.0 Introduction
The RZB-ZMD16C-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 one RF Sniffer board that connects to a PC’s USB port via an RTA-FoUSB-MON unit, which comes pre-programmed to function as the 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 > (All) Programs > Renesas > RF SnifferV.x.xx
A second RTA-FoUSB-MON unit included in the kit comes pre-programmed to function as a Flash Programmer and In-Circuit-Debugger (ICD). Three ZigBee Demonstration Kit (ZDK) boards come pre­programmed with demo software that allows 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 combination with the ICD, allows in-system programming of the M16C/28 Flash MCUs on the ZDK and RF Sniffer target boards.
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.
This ZDK 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 files are provided in the directory
C:\Renesas\RZB_ZMD16C_ZDK\ZbRom:
ZbRom_ZMD28_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_ZMD28_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.
TM
(FoUSB) Programmer software, in
RZB-ZMD16C-ZDK User’s Manual Rev 1.2 4/ 33 August 2006
2.0 Contents of Product Package
This section describes the contents of the RZB-ZMD16C-ZDK product package. When unpacking your RZB-ZMD16C-ZDK, please check to see that all items listed below are included.
2.1. RZB-ZMD16C-ZDK ZigBee Demonstration Kit Item List
Table 2-1
Table 2-1 RZB-ZMD16C-ZDK Item List
RZB-ZMD16C-ZDK Board 3 ZigBee Demo Kit (ZDK) Boards, pre-programmed with
RF Sniffer Board 1 RF Sniffer Board, pre-programmed with Sniffer
RTA-FoUSB-MON (ICD) 1 In-Circuit Debugger and Flash Programmer Interface RTA-FoUSB-MON (RFSI) 1 RF Sniffer Interface 6” 10-Pin Target Cable 2 Connects ICD and RFSI units to ZDK and RF Sniffer
6’ Mini USB Cable 2 Connects ICD and RFSI units to Host PC Battery Pack with 3 AA batteries 3 Powers the three ZDK boards CD-ROM Auto-install program
lists the items included in the RZB-ZMD16C-ZDK.
Item Name Quantity Remarks
demo software
firmware
boards
RF Sniffer software HEW (IDE & debugger) NC30WA (C-compiler, assembler, and linker) FoUSB Programmer USB drivers Manuals Tutorials Sample programs
2.2. 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-ZMD16C-ZDK User’s Manual Rev 1.2 5/ 33 August 2006
3.0 Limited Guarantee and Support
Renesas Technology America, Inc., warrants the RZB-ZMD16C-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-USB” is a trademark of Renesas Technology America, Inc. All other trademarks are the properties of their respective owners.
RZB-ZMD16C-ZDK User’s Manual Rev 1.2 6/ 33 August 2006
4.0 System Connectivity
The following lists the hardware and software products required for using the RZB-ZMD16C-ZDK ZigBee Demonstration Kit.
• Host Computer (supplied by user)
• Three RZB-ZMD16C-ZDK Boards
• Three battery packs with AA batteries
• RF Sniffer Board
• RF Sniffer Interface (RFSI)
• Mini USB cable for RFSI
• 2×5 header target cable for RFSI
• RF Sniffer software and USB driver
RF Sniffer
ZigBee Coordinator ZigBee Router ZigBee Router
Figure 4.1: ZigBee Demo Kit Setup
RZB-ZMD16C-ZDK User’s Manual Rev 1.2 7/ 33 August 2006
Optional (only required if you want to update firmware and/or develop code).
• In-Circuit Debugger and Programmer (ICD)
• Mini USB cable for ICD
• 2×5 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 2×5-pin ribbon cable.
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-ZMD16C-ZDK is a PC with a USB port and Microsoft Windows 98, ME, 2000, or XP.
4.2. RZB-ZMD16C-ZDK Boards
The three RZB-ZMD16C-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 “5.0
” for more details. Hardware
4.3. RF Sniffer Board
The RF Sniffer board is based on the same hardware as the ZDK demo boards, but is pre-programmed with a different firmware to function as a ZigBee RF Sniffer. See section “5.0 ” for more details
RZB-ZMD16C-ZDK User’s Manual Rev 1.2 8/ 33 August 2006
Hardware
on the board hardware, and the RF Sniffer User’s Manual for more information on RF Sniffer usage and features.
4.4. RF Sniffer Interface (RFSI)
The RF Sniffer interface is an RTA-FoUSB-MON unit that comes pre-programmed with firmware to allow the RF Sniffer software running on the Host PC to take control of the RF Sniffer board. The RFSI connects to the PC’s USB port via the included mini USB cable, and to the RF Sniffer board via the included 2×5-header ribbon cable. The USB port also provides power to the RF Sniffer board and RFSI, thereby eliminating the need for an external power supply.
4.5. RF Sniffer Software and USB Driver
The installer program offers you the option to install the ZDK demo software tools and the RF Sniffer software. For details on installation, see the QuickStart Guide or instructions in the Appendix A of this manual.
4.6. 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 can be powered by the included battery packs.
4.7. 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.7.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.7.2. NC30WA Evaluation Version C Compiler
The evaluation version of the M3T-NC30WA C-compiler is provided with the same functionality as 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.7.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
• C variable “watch” window
RZB-ZMD16C-ZDK User’s Manual Rev 1.2 9/ 33 August 2006
*Note: The number of breakpoints will vary depending on the M16C flash MCU used.
4.7.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 M16C family flash MCU (e.g. R8C, M16C, M32C). Please see the RTA-FoUSB-MON User’s Manual for more details.
RZB-ZMD16C-ZDK User’s Manual Rev 1.2 10/ 33 August 2006
5.0 Hardware
5.1. ZDK Board (RZB-ZMD16C-ZDK)
Note:The RZB-ZMD16C-ZDK board is referred to as RZB-ZMD28-BRD on the board's silkscreen and schematic drawing. Figure 5-1 shows the RZB-ZMD16C-ZDK Board with major components identified.
Figure 5.1: RZB-ZMD16C-ZDK Board
RZB-ZMD16C-ZDK User’s Manual Rev 1.2 11/ 33 August 2006
5.2. RZB-ZMD16C-ZDK Board Block Diagram
The RZB-ZMD16C-ZDK board incorporates an M30280FAHP (80-pin QFP) from the M16C/28 group of microcontrollers designated as U4. Figure 5-2 shows the RZB-ZMD16C-ZDK block diagram.
RS232
Transceiver
D4
Red
Power LED
8 characters x 2 lines LCD
J7
ICD Header
Vcc
JP2
RS232
Power
P0_0...6
Vcc
JP1
MCU Power
for Icc
Measurements
Figure 5-2: RZB-ZMD16C-ZDK Block Diagram
Y1
10MHz
Xin Xout XCin XCout
UART 1
U4
M30280FAHP
MCU
UART 2
Ports
J1, J2, J3, J4
Headers
Y2
32kHz
ZigBee
RF
S1 S2 S3 S4 R3 RT1 R44
P10_4 P10_5 P10_6 Reset AN2 AN1 AN0
Red LED
Yellow
LED
Green
LED
D1 D2 D3
P3_4 P3_5 P3_6
5.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_ZMD16C_ZDK\Docs folder on your PC or from the Start menu (Start > Programs > Renesas > RZB_ZMD16C_ZDK > All Manuals and Documents) after ZDK software installation.
5.4. RZB-ZMD16C-ZDK Board Jumper Configuration
5.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 of the MCU during various modes of operation. For normal operations, JP1 must be shorted.
JP1 is shorted by default.
RZB-ZMD16C-ZDK User’s Manual Rev 1.2 12/ 33 August 2006
5.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.
5.4.3. Default Jumper Settings
Table 5-1: Default Jumper Settings
Jumper Default
Setting
JP1: MCU Power Shorted JP2: Power LED and RS232 Power Shorted
5.5. LCD (Liquid Crystal Display)
The LCD is a 2-line by 8-character display with a KS0066 controller IC.
5.6. ZigBee RF
The ZigBee RF circuit utilizes a ZMD 44102, 900MHz, IEEE 802.15.4 compliant transceiver IC.
6.0 Limitations of the ZbRom System
The following is a list of limitations for the ZbRom system. 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 ZbRom.
Please do not modify or disrupt any of the MCU resources used by the ZigBee stack:
6.1. Timers
Table 6-1: MCU Timer Usage
TA0 available TA1 Used by ZigBee stack TA2 Used by ZigBee stack TA3 Used by ZigBee stack TA4 Used by RTOS TB0 Used by ZigBee stack TB1 available TB2 Used by ZigBee stack
RZB-ZMD16C-ZDK User’s Manual Rev 1.2 13/ 33 August 2006
6.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.
6.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 the ones listed below. To implement your own sub-routines for those interrupts, you need to re-direct their respective interrupt vectors to the location of your interrupt service routines by calling the pre-defined functions SetxxxInt().
Available User Interrupts Interrupt Routine Vector Set Function
Timer A0 void SetTimerA0Int(long funct_addr); Timer B1 void SetTB1Int(long funct_addr); UART 2 Rx void SetUart2RxInt(long funct_addr); INT2 void SetInt2Int(long funct_addr); INT3 void SetInt3Int(long funct_addr); DMA 0 void SetDma0Int(long funct_addr); DMA 1 void SetDma1Int(long funct_addr);
6.4. Flash and RAM Usage
The memory areas shaded in turquoise are available for your use.
Table 6-2: Flash Memory Usage
Flash Address Range Usage
0xFF800-0xFFFFF 0xE8000-0xFF7FF 0xC0000-0xE7FFF 0x0F7FF-0x0FFFF 0x0F000-0x0F007
Table 6-3: RAM Memory Usage
RAM Address Range Usage
0x2380-0x23FF 0x2000-0x237F 0x0400-0x1FFF 0x0000-0x03FF
FoUSB Monitor Area (2KB) User code/const space (30KB) ZbROM Area (stack and RTOS) (64KB) User Data Flash Area (2KB) MAC Address (Don’t Erase Block)
FoUSB Monitor Area User global variable space (896 bytes) ZbROM area, user task stack <100 bytes MCU Register Area
6.5. 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 ZbRom 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.
RZB-ZMD16C-ZDK User’s Manual Rev 1.2 14/ 33 August 2006
6.6. 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 of the linker warning you will receive if you exceed the available RAM space:
Phase M16C Linker starting
C:\WorkSpace\test\test\sect30_zdk28.inc(186) : Warning (ln30): C:\WorkSpace\test\test\Coord_Router\_ncrt0_zdk28.r30 : 'DATA' section 'debugger_NE' is overlapped on the 'bss_NE' from 2380H to 2380H
6.7. 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_ZMD16C_ZDK\Demos\Replacement MAC Addresses directory. Program one of those addresses into your board using the FoUSB programming software. Please make sure that the address you pick is unique and different from any address used by your other ZDK boards.
6.8. 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.
6.9. 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.
6.10. ZigBee Stack Table Sizes
Table 6-4: ZigBee Stack Table Sizes
ZigBee Coordinator & Router
Number of Entries Neighbor Table 15 4 Router Table 15 0 Router Discovery Table 15 0 Broadcast Transmission Table 20 20
ZigBee End Device Number of Entries
RZB-ZMD16C-ZDK User’s Manual Rev 1.2 15/ 33 August 2006
6.11. Customization of Demo Program Settings
The following definitions can be changed at the top of the ZDK_Demo.c file to fit your requirements.
/* ZigBee Configuration */
#define DEMO_CHANNEL 1 #define SCAN_CHANNELS ((DWORD)0x1 << DEMO_CHANNEL) /* Only scan our demo
channel */
//#define SCAN_CHANNELS 0x7FFF800 /* Scan every channel */
ZbPANId s_LocalPanId = 0x1ACE; /* MUST BE A VALUE LOWER THAN 0x3FFF */
/* 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 */
6.12. Other Limitations
The RZB-ZMD16C-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-ZMD16C-ZDK User manual (Start > (All) Programs > Renesas > RZB_ZMD16C_ZDK > All Manuals and Documents).
RZB-ZMD16C-ZDK User’s Manual Rev 1.2 16/ 33 August 2006
7.0 System Operation & Limitations
The RZB-ZMD16C-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: System Limitations when Debugging
Item Please Refer To
7.2

Pin and Peripheral Limitations

7.3

Memory Map

User Limitations
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 can be programmed into the M16C/28 using the FoUSB Programmer. This procedure erases the kernel and leaves only the user program.
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
7.2. Pin and Peripheral Limitations
SIO/UART1 pins are used for communication between the M16C/28 kernel on the RZB-ZMD16C-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-ZMD16C-ZDK board’s M16C/28 MCU are shown in . Figure 7-1
RZB-ZMD16C-ZDK User’s Manual Rev 1.2 17/ 33 August 2006
00000h
00400h
023FFh
0F000h
0F800h
10000h
E8000h
FFFFFh
SFR Area
Internal RAM
Area - 8kB
Reserved
High E/W
2kB data block
High E/W
2kB data block
Reserved
User Flash ROM Area - 96kB
User RAM Area
FF900h
FFE80h
= 8064 Bytes
Kernel RAM
(128 Bytes)
User Program
Area - 94kB
Kernel
Program
00400h
0237Fh 02380h
023FFh
Note: User programs must not use shaded areas.
Special Page
Area
FFFDCh
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. Register 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, kernel operation cannot be guaranteed.
Table 7-2: Limitations on Register Operation
Register Name Restriction
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
Do not change. UART1 Transmit/Receive Control Register 0 UART1 Transmit/Receive Control Register 1 UART1 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-ZMD16C-ZDK User’s Manual Rev 1.2 18/ 33 August 2006
Table 7-3: Interrupt Vector Addresses
Interrupt Cause M16C/28 Vector Address Kit Specification
Undefined FFFDCh ~ FFFDFh User available Overflow FFFE0h ~ FFFE3h User available BRK Instruction FFFE4h ~ FFFE7h User inhibited Address Match FFFE8h ~ FFFEBh User inhibited Single-step FFFECh ~ FFFEFh User inhibited Watchdog Timer FFFF0h ~ 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 requires 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 [-g] 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-ZMD16C-ZDK User’s Manual Rev 1.2 19/ 33 August 2006
8.0 RZB-ZMD16C-ZDK Board Specifications
8.1. Hardware Specifications
Table 8-1
Table 8-1: RZB-ZMD16C-ZDK Board Specifications
MCU M30280FAHP Clocks Main Clock: crystal 10 MHz, PLL, or ring oscillator
Memory (ICD)
Connectors [J1-J4]: Four 2×10-pin measurement test points connected to the MCU
Jumpers [JP1]: MCU Power for Icc Measurements
Switches [S1]: pushbutton (connected to P10_4)
LEDs [D1] (Red): User output (connected to P3_4)
LCD 2-line × 8-character LCD with KS0066 controller IC
lists the specifications of the RZB-ZMD16C-ZDK Board.
Item Specification
Sub Clock: 32.768 kHz crystal RAM: 8kB (8064 Bytes user available due to kernel) High E/W Data Block: 2kB × 2 (4096 Bytes) Flash ROM: 96kB (94kB user available due to kernel)
pins. Can also be used to connect your own expansion boards via 2×10 headers. [J7]: In-Circuit Debug connector (UART1 for FoUSB-ICD) [P1]: 9-Sub-D RS232 connected via RS232 transceiver to UART2
[JP2]: Power LED and RS232 Power connect
[S2]: pushbutton (connected to P10_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.
[D2] (Yellow): User output (connected to P3_5) [D3] (Green): User output (connected to P3_6) [D4] (Red): Power On (if jumper JP2 shorted)
8.2. Power Supply Requirements
The RZB-ZMD16C-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 board in a conductive bag inside the original factory packaging box.
Table 8-2: Operating Environment
Environmental Condition Ambient Temperature Ambient Humidity
Operating 0 - 55°C
Storage -30 to 75°C
RZB-ZMD16C-ZDK User’s Manual Rev 1.2 20/ 33 August 2006
lists the environmental conditions for using and storing the RZB-ZMD16C-ZDK board. Store the
30 to 80% (non-condensing)
(No corrosive gas allowed)
30 to 80% (non-condensing)
(No corrosive gas allowed)
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:\Renesas\FoUSB directory.
To do this, run FoUSB_Vx.xx.exe in the \Tools\FoUSB directory of the CD. After the FoUSB Programmer install, assuming the default directory was used, a C:\Renesas\FoUSB 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, and 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 > Control Panel > System Properties > Hardware > Device Manager > 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 > Control Panel > System Properties > Hardware > Device Manager > Universal Serial Bus controllers).
2. Double-click on ‘Renesas FoUSB ICD’. A Renesas FoUSB ICD Properties dialog box appears.
3. Click on the ‘Driver’ tab and click the ‘Update Driver’ button.
4. Select ‘Display a list…’ and click on the ‘Have Disk’ button.
5. Browse to the C:\Renesas\FoUSB\USB Drivers directory and install the usbmon.sys driver.
6. If this process does not work, please follow the instructions below.
RZB-ZMD16C-ZDK User’s Manual Rev 1.2 21/ 33 August 2006
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:

• Erratic debug behavior

• Cannot connect to target

• 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 Programmer 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.
• 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 2×5-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
• 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 ‘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).
RZB-ZMD16C-ZDK User’s Manual Rev 1.2 22/ 33 August 2006
• USB was not selected on the HEW Init dialog box.
Please select ‘USB’ from the Init dialog 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.
• 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 & Limitations the countermeasures.
” were not satisfied. The common issues are listed in Table A.3, including
Table A.3
Problem Possible Cause/s and Solution
After stepping a few instructions, HEW cannot “stop”
Breakpoints do not seem to work
HEW locks up (cannot stop program) or Communication error message is displayed.
Download problems
To re-initialize the system without closing a debug session, try the following:
• 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.
• Changes were made to the UART1 Special Function
Registers (SFRs). Do not change UART1 SFRs in your code.
• System is in “FreeRun” mode. Change the RUN mode to “Sampling” from the “Init” window (Emulator System icon).
• 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 session. 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.
• 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.
RZB-ZMD16C-ZDK User’s Manual Rev 1.2 23/ 33 August 2006
• 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-ZMD16C-ZDK User’s Manual Rev 1.2 24/ 33 August 2006
Appendix B. Reference Manuals
Item Title Description
Renesas ZigBee Demonstration Kit
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
(ZDK)Quick Start Guide
RZB-ZMD16C-ZDK User’s Manual RF Sniffer User's Manual
ZDK Board Schematic
ZDK Board BOM M16C/20/60 Series C-Language Programming Manual M16C/20/60 Series Assembler Language Programming Manual HEW User's Manual
AS30 User's Manual NC30 User's Manual RTA-FoUSB-MON 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 > Programs > Renesas > RZB_ZMD16C_ZDK > Document Descriptions.
Document that will help you get started on using the ZigBee Demonstration Kit.
This document. Document describing the ZigBee RF Sniffer hardware and software in more detail. Schematic diagram for the RF Sniffer and ZDK boards. Bill of materials for the ZDK board. ANSI C-language programming guide for the M16C/20/60 series MCU. Assembly language programming guide for the M16C/20/60 series MCUs. This document describes installation and operation of this Integrated Development Environment for Renesas' Tools. Guide for AS30 assembler. Guide for NC30WA C-compiler. In-Circuit Debugger and Programmer User’s Manual.
RZB-ZMD16C-ZDK User’s Manual Rev 1.2 25/ 33 August 2006
Appendix C. Expansion Headers
The M30280FA MCU on the RZB-ZMD16C-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 the ZDK board. The following table shows the mapping of J1-J4 pins to MCU pins and signal names.
J1
Pin
MCU
Pin
MCU Function
1 1 P95/AN25/CLK4 1 21 P76/TA 2 2 P93/AN24 2 22
3 3 P92/TB 4 4 P91/TB
5 5 P90/TB
3 23 P74/TA
2in
4 24
1in
5 25 P72/CLK2/TA
0in
6 6 26 P71/RxD2/SCL/TA 7 7 27 P70/TxD2/SDA/TA 8 8 28 P67/TxD1 9 9 29 P66/RxD1 10 10 30 P65/CLK1 11 11 Vss 11 31
12 12 32 P37 13 13 Vcc 13 33 P36 14 14
15 15
16 16
17 17
18 18
19 19 P80/TA 20 20 P77/TA
/NMI / SD
P8
5
/
INT /Zphase
P8
4
P8
/
INT
3
P8
/
INT
2
P8
/TA
1
4in
4out
3in
2
1
0
/ U
/U 19 39 P30/CLK3
J2
Pin
MCU
Pin
P7
P7
/TXD
P6 /CLKS
14 34 P3
15 35 P3
16 36 P3
17 37 P3
18 38 P3
20 40 P63/TxD0
MCU Function
3out
/TA
/ W
5
2in
/W
2out
/
CTS /
3
1
/
CTS /1RTS /0CTS
4
1
5
4
3
2/SOUT3
1/SIN3
2
1
RTS /TA
2
/V/RXD1
1out
/CLK1
0in
0out
1in
/ V
RZB-ZMD16C-ZDK User’s Manual Rev 1.2 26/ 33 August 2006
J3
Pin
MCU
Pin
MCU Function
J4
Pin
MCU
Pin
MCU Function
1 41 P62/RxD0 1 61 P06/AN06 2 42 P61/CLK0 2 62 P05/AN05 3 43
P6
/
0
CTS
RTS
/
0
0
3 63 P0
/AN04
4
4 44 P27/OUTC17/INPC17 4 64 P03/AN03 5 45 P26/OUTC16/INPC16 5 65 P02/AN02 6 46 P25/OUTC15/INPC15 6 66 P01/AN01 7 47 P24/OUTC14/INPC14 7 67 P00/AN00 8 48 P23/OUTC13/INPC13 8 68
9 49 P22/OUTC12/INPC12 9 69
10 50 P21/OUTC11/INPC11/SCLMM 10 70
11 51 P20/OUTC10/INPC10/SDAMM 11 71
12 52
13 53
14 54
/
INT /INPC1
P1
7
/
INT /IDW
P1
6
INT
P1
/
5
/IDU
AD
TRG
7
/IDV
5
4
/
3
12 72 P10
13 73 P10
14 74 P10
P10
P10
P10
P10
/AN7/
7
/AN6/
6
/AN5/
5
/AN4/
4
/AN3
3
/AN2
2
/AN1
1
KI
3
KI
2
KI
1
KI
0
15 55 P14 15 75 AVss 16 56 P13/AN23 16 76 P100/AN0 17 57 P12/AN22 17 18 58 P11/AN21 18 78 AVcc 19 59 P10/AN20 19 79 P97/AN27/S 20 60 P07/AN07
20 80 P96/AN26/S
IN4
OUT4
RZB-ZMD16C-ZDK User’s Manual Rev 1.2 August 2006
Appendix D. Board Schematic & BOM
Note:The RZB-ZMD16C-ZDK board is referred to as RZB-ZMD28-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_ZMD16C_ZDK > Board Hardware, or by browsing to the folder
C:\Renesas\RZB_ZMD16C_ZDK\Docs\ ZDK_Manuals and opening the files: RZB_ZMD28_BRD_BOM.pdf RZB_ZMD28_BRD_Schematic.pdf
RZB-ZMD16C-ZDK User’s Manual Rev 1.2 28/ 33 August 2006
R140
DVDD_3.3V
R43 680
R42 680
R41 680
1
D1RED
D2YEL
D3GRN
LED_GRN
LED_RED
LED_YEL
C44
3
VoutEnable
3825 4
2
Vin
JP1
154
FoUSB_PWR
C19
PGND GND
1 2
+
C43
C42
+
MCU_POWER
2.2uF
REG711-5.0
R25
10k
C18
10uF
FoUSB_PWR
D D
C41
0.1uF
0.1uF
0.1uF
2.2 uF
6
2
DVDD_3.3V
3
DVDD_5.0V
4
C20
0.22uF
C+ C-
U6
7 6
DVDD_3.3V
5
SW1
Power Source Select
LDO_OUT EN_5V
DVDD_5.0V
ZMD_DA3
ZMD_DA2
ZMD_DA1
ZMD_DA0
ZMD_DA5
ZMD_DA7
ZMD_DA6
ZMD_DA4
J2-15
J2-14
J2-13
J2-12
J2-16
LED_RED
LED_YEL
LED_GRN
J2-18
J2-17
J2-19
393837
36
323334
35
P33
P37
P36
P35
P34
P31/SIN3
P30/CLK3
P32/SOUT3
J4-18
AVcc
78
Vcc
13
J1-13
P60/C•R T S0
P61/CLK0
P62/RxD0
P63/TxD0
P64/C•RTS1/CTS0/CLKS1
P65/CLK1
P66/RxD1
J3-2
J3-1
GND
BYPASS
LP2992AIM5-3.3
C15
O
ICD_BUSY
J2-11
J2-20
0.01uF
ICD_CLK
J2-10
ICD_IN
J2-9
P67/TxD1
ICD_OUT
J2-8
U4
434241403130292827262524232221201918171615
ZMD_MOSI
ZMD_MISO
ZMD_CLK
ZMD_CS
J3-3
LDO_OUT
Vin Vout
ON/OFF
U5
1 523
4
C16
10uF
INPUT_PWR
123
O
Tip
J6
POWER JACK
Vol t age
16.0V
3.4V to
Inpu t
D6
0
ZMD_PD
J3-5
J3-10
J3-4
J3-9
J3-8
J3-7
J3-11
J3-6
51504948474645
44
P22/OUTC12/INPC12
P23/OUTC13/INPC13
P24/OUTC14/INPC14
P25/OUTC15/INPC15
P26/OUTC16/INPC16
P27/OUTC17/INPC17
P21/OUTC11/INPC11/SCLMM
P20/OUTC10/INPC10/SDAMM
P70/TxD2/SDA/TA0out
P71/RxD2/SCL/TA0in/CLK1
P72/CLK2/TA1out/V/RXD1
P73/C•RTS2/TA1in/V/TXD1
P74/TA2out/W
P75/TA2in/W
P76/TA3out
P77/TA3in
J2-1
J2-5
J2-3
J2-2
J1-20
RS232_RTS
RS232_OUT
RS232_IN
J2-7
J2-6
J2-4
C21
0.1uF
DVDD_3.3V
R14 680
D5
D4RED
134
C1+
JP2
1 2
RS232 POWER
VCCGND
1615
JP2-1
V+
U7
2
C22
0.1uF
C C
CD Modu le L
ZMD_RESETn
J3-18
J3-17
J3-19
P12/AN22
P11/AN21
P10/AN20
P80/TA4out/U
P81/TA4in/U
P82/INT0
J1-19
J1-18
J1-17
ZMD_IRQ
C23
0.1uF
5
C1-
C2-
C2+
V-
6
C24
0.1uF
594837261
P1
LCD1
J3-16
P13/AN23
P83/INT1
J1-16
J3-15
J1-15
RS232_OUT
2
3
Vcc
DB4
111213
R321.8K
R341.8K
LCD1
LCD0
J3-14
J3-13
POT_EN
CDS_EN
545352
5556575859
P14
P15/INT3/ADtrg/IDW
P84/INT2/Zphase
P85/NMI/SD
14
J1-14
ZMD_WR
ZMD_RD
RS232_RTS
R37 0
R39 0
111012
T1IN
T2IN
T1OUT
T2OUT
14713
Vo
DB5
DB6
R281.8K
LCD2
J3-12
TEMP_EN
P16/INT4/IDV
P17/INT5/INPC17/IDU
ZMD_ALE
RS232_IN
R1OUT
R1IN
789
14
R261.8K
LCD3
R33 0
9
8
C45
R40
DB0
DB1
DB7
J4-7
LCD0
676665
P00/AN00
P90/TB0in
543
J1-5
R2OUT
R2IN
456
LCD_RS
J4-6
LCD1
J1-4
1K
0.1uF
10
DB2
RS
LCD_EN
J4-5
LCD2
P01/AN01
P91/TB1in
J1-3
MAX202
DB3
EN
P02/AN02
P92/TB2in
LCD_R/W
J4-4
LCD3
J1-2
R/W
J4-3
LCD_RS
64
63
P03/AN03
P93/AN24
2
1
J1-1
DB9 Female
ACM0802B
Vss
1
10K
R38
10K
R36
R27 3 .3 K R29 3 .3 K R35 3 .3 K R19 3 .3 K
J3-20
J4-2
J4-1
LCD_R/W
EN_5V
LCD_EN
606162
P07/AN07
P06/AN06
P05/AN05
P04/AN04
M30280F
P95/AN25/CLK4
P96/AN26/SOUT4
P97/AN27/SIN4
80
79
J4-19
J4-20
DVDD_3.3V
DVDD_3.3V
Xcout
Xcin
8
7
P86/Xcout
Vref
P100/AN0
76
7467372717069
77
AN1
AN0
J4-16
J4-14
B B
R12 0
Xcout
Y1
R13 0
12109
Xin
Xout
P87/Xcin
P105/AN5/KI1
P101/AN1
P102/AN2
P103/AN3
P104/AN4/KI0
J4-12
AN2
J4-11
J4-13
J4-10
R17
10K
R7
7.32K 1%
R44
10K
13
C25
0.1uF
Xcin
J4-9
AN0
C39
18pF
Y2
32kHz
C40
18pF
C38
33pF
10 MHZ
C37
33pF
D5
BAT54C
75
11
R9
U8-1
R23
J4-15
J1-11
10K
S3
S2
S1
R3
CdS Cell
2 1
NDS9956A
POT_EN
2
100K
2
1
C17
0.1uF
S4
RESET
EVQ-PAC04M
12
12
VOLT_SEL
MCU_RESET
ICD_BUSY
ICD_IN
246810
+++++
J7
+++++
13579
In Circuit Debug por t
2
FoUSB_PWR
ICD_CLK
R15
1
Xcout
CDS_EN
4
R30
10K
U8-2
NDS9956A
6
3
5
TEMP_EN
2
R10
U3-1
NDS9956A
8 7
1
R31
10K
TP1
GND Point
A A
3
DVDD_3.3V
MCU_RESET
RESET
M30280Fx
AVss
Vss
P106/AN6/KI2
P107/AN7/KI3
CNVss
68
J4-8
CNVss
AN2
AN1
RT1
10K
t
2
7 8
ICD_OUT
0
10K
1
RZB-ZMD28-BRD Zigbee Development Kit
Title
R16
R11
103308-1
1
Size Document Number Rev
47K
0
CNVss
of
12Friday, July 14, 2006
1
SCH-9063-04 E
B
Date: Sheet
2
3
4
5
RZB-ZMD16C-ZDK User’s Manual Rev 1.2 29/ 33 August 2006
of
22Friday, July 14, 2006
1
C4
100pF
C31
1uF
C30
1uF
100pF
2
100pF
C1
VDD_2.5VVDD_2.5V VDD_2.5V VDD_2.5V VDD_2.5V
VDD_2.5V
1uF
C12
10uF
L1
470nH
C9
10uF
123
4
A1
5
C49
L2
8.2nH
C48
50 OHM TRACE
C2 22pF
RFO
RP-SMA
1.8pF
1.8pF
C14
100uF
C11
10uF
DVDD_3.3V
C8
0.01uF
1523
4
U1
VinVout
ON/OFF
BYPASS
LP2992AIM5-2.5
GND
VDD_2.5V
C7
270pF
C5
200pF
R2
1.6K
12
R1
2.2K
12
C6
3900pF
C28
43pF
1
SCH-9063-04 E
RZB-ZMD28-BRD Zigbee Development Kit
B
Title
Size Document Number Rev
Date: Sheet
2
C10
3
VDD_2.5VDVDD_3.3V
4
5
100pF
C35
1uF
X-1
X-2
C34
100pF
412018154335
10
7914
131911
RFO
RFIO
LPF2
AVDD
LPF1
U2
IRQ
DA2
DA3
DA4
DA5
DA7
DA6
34
23
ZMD_IRQ
ZMD_DA2
ZMD_DA3
ZMD_DA6
ZMD_DA4
ZMD_DA5
ZMD_DA7
ZMD_RD
AVDD
AVDD
AVDD
C36
1uF C3
C29
DNI C27
DVDD
DVDD
DVDD
DVDD3.3
DVDD3.3
39
21
C47
C13
12
12
12
12
12
AVDD
N/C
N/C
N/C
ALERDWR
1
47
423837
48
0.1uF
10uF
R4
100K
R6
100K
R5
100K
R22
100K
R24
100K
ZMD_WR
ZMD_ALE
21617
36
22
CLKO
GPD
N/C
N/C
MOSI
SCK
27
4046844
N/C
AVSS
DVSS
MISO
RSN
SS
262545
24
AVSS
AVSS
RTC1
46
AVSS
RTC2
12
XTAL1
XTAL2
DA0
DA1
28293031323335
Y4
680
1 2
1 2
1 2
1 2
R18 0
R20 0
R21 0
R47
ZMD_PD
ZMD_MISO
ZMD_MOSI
ZMD_CLK
ZMD_DA0
ZMD_CS
ZMD_RESETn
ZMD_DA1
ZMD44102
12
12
Y3
24 MHz
SX5159
C26
43pF
NOTE:
SEPARATE XTAL CIRCUIT FROM LOOP
FILTER AS FAR AS POSSIBLE. BEST
WITH ONE ON BOTTOM, ONE ON TOP.
C32
15pF
32.768KHz
C33
15pF
R8
100K
C46
R45
DNI
DNI
F5
F4
F2
F1
3
4
FIDUCIAL
FIDUCIAL
5
FIDUCIAL
FIDUCIAL
D D
C C
B B
A A
RZB-ZMD16C-ZDK User’s Manual Rev 1.2 30/ 33 August 2006
Appendix E. RZB-ZMD16C-ZDK Printed Circuit Board
Figure E-1: PCB Top View
RZB-ZMD16C-ZDK User’s Manual Rev 1.2 31/ 33 August 2006
Figure E-2: PCB Bottom View
RZB-ZMD16C-ZDK User’s Manual Rev 1.2 32/ 33 August 2006
Applications Engineering
Appendix F. 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 > (All) Programs > Renesas > RZB_ZMD16C_ZDK > RTA-FoUSB-Mon Manual).
2. For updates and other evaluation tools and sample programs for the RZB-ZMD16C-ZDK Kit, see:
http://america.renesas.com/zigbee
.
RZB-ZMD16C-ZDK User’s Manual Rev 1.2 33/ 33 August 2006
Loading...
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use