SK-FR80-120PMC-USB Fujitsu, SK-FR80-120PMC-USB Datasheet - Page 145

• Manufacturer Part Number: SK-FR80-120PMC-USB
• Description: BOARD, EVAL, FOR MB91660 SERIES
• Manufacturer: Fujitsu
• Type: Evaluation Boardr

Specifications of SK-FR80-120PMC-USB

• Kit Features: External FRAM Memory MB85RS256, USB A & USB A Connectors, USB To Serial Converter
• Mcu Supported Families: MB91660
• Silicon Manufacturer: Fujitsu
• Core Architecture: FR80
• Kit Contents: Board, USB A To Mini-B Cable
• Features: USB Connector, 7-segment LED, Humidity Sensor
• Rohs Compliant: No
• Lead Free Status / RoHS Status: Contains lead / RoHS non-compliant

4.4
listed below.
The monitor debugger provided on this starter kit is functionally limited compared to an ICE as
- "Program stop", "Reset" must be done by pressing the switch on the board.
- The operating clock for the CPU must not be changed as the monitor debugger program
- The resources used by the monitor debugger cannot be used by the user.
- Monitor debugger uses the following memory area. User programs cannot use this area.
- Default interrupt vector area (TBR: 0xFFC00) is used by the monitor debugger. This area
- Only 16 break points (code breaks) are allowed.
- Monitor debugger uses user interrupts for the break function, communication functions, etc.
- Do not press the Reset button on the board when launching the debugger.
- Do not press the Reset button on the board during continuous execution.
cannot be overwritten when loading the monitor debugger. Therefore, the TBR is set to
0x80000 when monitor debugger launches.
(This cannot be controlled from SOFTUNE on the PC.)
performs data communications internally with the PC using asynchronous communications.
(This does not apply when checking the operation of a completed program.)
(Refer to Appendix 4.2 for resources used by the monitor debugger.)
RAM: 0x3E000 to 0x3FFFF, ROM: 0xFE000 to 0xFFFFF
To use these interrupts in the user program, the interrupt vector addresses must be defined
outside of the monitor debugger.
Changing interrupt levels and enabling/disabling settings for interrupts in the user program
may disable certain monitor debugger functions.
(Refer to Appendix 4.3 for the memory map when the monitor debugger is installed.)
Monitor debugger limitations
144