DebugFactory Builder 4 for AMOT Users Manual - OBJECT · DebugFactory Builder 4 for AMOT Users Manual - 7 - [2] Attached Software and Documents 2.1 CD-ROM Attached CD-ROM includes

DDeebbuuggFFaaccttoorryy BBuuiillddeerr 44 ffoorr AAMMOOTT UUsseerrss MMaannuuaall

OOBBJJEECCTT

PanaXSeries and DebugFactory Builder are trademarks of Panasonic Corporation. Microsoft Windows and MS-DOS are trademarks of Microsoft Corporation. Adobe Acrobat Reader is a trademark of Adobe Corporation. The other corporation name, logotype, and product names written in the book are trademarks or registered trademarks of their corresponding corporations.

Request for your special attention and precautions in using the technical information and semiconductors described in this book

(1) An export permit needs to be obtained from the competent authorities of the Japanese Government if any of the

products or technologies described in the book and controlled under the “Foreign Exchange and Foreign Trade Law” is to be exported or taken out of Japan.

(2) The contents of this book are subject to change without notice in matters of improved function.

(3) We are not liable for any damages arising out of the use of the contents of this book, or for any infringement of patents or other rights owned by a third party.

(4) No part of this book may be reprinted or reproduced by any means without written permission from our company.

(5) In no event will OBJECT and Panasonic Corporation Semiconductor Company be liable to you for any indirect damages caused by using this Product.

(6) In the event that you find a defect of this Product and advise OBJECT of it within one(1) year from the date of purchase, OBJECT will pay for the damage. In no event OBJECT's liability to you exceed the amount actually paid by you for this Product, and as the previous article, OBJECT and Panasonic Corporation, Semiconductor Company shall not be liable to you for defect warranty.

(7) We can supply the support for via E-Mail (DebugFactory Builder 4 for AMOT [email protected]) and WEB SITE (http://www.OBJECT.jp) Please determine the up- to-date information and more on our WEB SITE.

(8) Please refer to Panasonic Corporation, Semiconductor company for the support of the attached C compiler.

mailto:[email protected]

http://www.object.jp/


- 3 -

- Table of Contents - [1] Introduction .................................................................. 5 1.1 Overview..................................................................... 5 1.2 Debugger Function............................................................ 5 1.3 Support PC and OS............................................................ 5 1.4 Support CPU.................................................................. 6

[2] Attached Software and Documents ............................................... 7 2.1 CD-ROM....................................................................... 7 2.2 C source code debugger(DebugFactory Builder 4)............................... 7 2.3 C compiler for MN101 series, MN103Lseries.................................... 7

[3] Product Description ........................................................... 8 3.1 Target Probe Connector....................................................... 8

[4] Set up ........................................................................ 9 4.1 Installing DebugFactory Builder 4............................................ 9 4.2 The addition of the microcomputer............................................ 11 4.3 The addition of the unit..................................................... 11 4.4 Update of the software....................................................... 11 4.5 Installing USB drivers....................................................... 12 4.6 Uninstalling................................................................. 14 4.7 Uninstall of old USB driver.................................................. 14

[5] User Program Development ...................................................... 16 5.1 Limitation on User Program Development....................................... 16 5.1.1 Debugger occupation resources ............................................ 16 5.1.2 IVBM bit of MEMCTR register(MN101C/E series) ............................. 16 5.1.3 Interrupt during break ................................................... 16 5.1.4 Undefined instruction .................................................... 16 5.1.5 Watchdog ................................................................. 16 5.1.6 Special Function Registers ............................................... 17 5.1.7 Monitor program(MN101C/E series) ......................................... 17 5.1.8 Monitor program(MN103L series) ........................................... 17 5.1.9 Interrupt vector table(MN101C/E series) .................................. 17 5.1.10 Stack(MN101C/E series) .................................................. 17 5.1.11 Stack pointer initial value ............................................. 17

5.2 The attention of the debugger................................................ 18 5.2.1 Limitation on DebugFactory Builder 4 for AM1DPDW ......................... 18 5.2.2 Target setting ........................................................... 18 5.2.3 Instruction set simulator ................................................ 18

[6] Secure Support by Keycode ..................................................... 19 6.1 Keycode Type................................................................. 19 6.1.1 Adjustable type .......................................................... 19 6.1.2 Fixed type ............................................................... 19

6.2 Keycode File................................................................. 20 6.3 Creating a Keycode File...................................................... 20 6.4 Keycode File Registration.................................................... 20

[7] Start-up Program .............................................................. 21 7.1 Start-up Program Specification............................................... 21 7.2 File Configuration of Start-up Program....................................... 21 7.3 Start.asm.................................................................... 21

[8] How to use DebugFactory Builder 4 ............................................. 22 8.1 Start of DebugFactory Builder 4.............................................. 22 8.2 Making of a project.......................................................... 22 8.3 DebugFactory Builder 4 Start-up Display...................................... 25 8.4 ROM image buffer............................................................. 25 8.5 Software breakpoints......................................................... 26 8.6 Compiling the Start-up Program............................................... 26 8.7 Starting Debugging and Loading the Program................................... 27 8.8 Setting Breakpoints and Executing the Start-up Program....................... 29 8.9 Typical Debug Commands....................................................... 30


- 4 -

8.9.1 Forced break (ESC) .......................................................30 8.9.2 Breakpoints (F9) .........................................................30 8.9.3 One Instruction Step Execution (F8) ......................................30 8.9.4 Function Step Execution (F10) ............................................30 8.9.5 Come Command (F7) ........................................................30

[9] General ROM Version............................................................31 9.1 Precautions on Debugger [Important] ..........................................31 9.2 Monitor Program Type .........................................................31 9.2.1 RAM Monitor Type .........................................................32 9.2.2 ROM Monitor Type .........................................................32

9.3 Debugger Function ............................................................33 9.4 Limitation on Debugger Function ..............................................33 9.5 Limitation on User Program Development .......................................33 9.5.1 Debugger occupation resources ............................................33 9.5.2 IVBM bit of MEMCTR register ..............................................33 9.5.3 Interrupt during break ...................................................33 9.5.4 Undefined instruction ....................................................33 9.5.5 Special Function Registers ...............................................33 9.5.6 Reset start address ......................................................33 9.5.7 Monitor program ..........................................................34 9.5.8 Interrupt vector table ...................................................34 9.5.9 Stack ....................................................................34 9.5.10 Stack pointer initial value .............................................34

[10] Target System Reference Circuits..............................................35 10.1 MN101CF73A ..................................................................35 10.2 MN101CF91D ..................................................................35 10.3 MN101CF93K ..................................................................36 10.4 MN101CF95G ..................................................................36 10.5 MN101CF97D ..................................................................37 10.6 MN103LEV03/LF06N/LF08K ......................................................37

[11] Error Message.................................................................38 [12] Index.........................................................................41


- 5 -

[1] Introduction

1.1 Overview DebugFactory Builder 4 DebugFactory Builder 4 for AM1DPDWDebugFactory Builder 4 for AM32LDPDWDebugFactory Builder 4

for AMOT consists of for MN101C/E series and for MN103L series.

for AMOT is debugging unification environment (C source code debugger, C Compier, editor, and make tool) of the MN101C/E series and MN103L series corresponding to our product AMOT. 1.2 Debugger Function

item Specification Flash ROM The writing and the reading of the flash ROM in the microcomputer Security Supports a security key cord

Practice form The practice performs a flash ROM directly Pre-exectuion break Max. 255 points

Event break 1 point (Data access:Data/Bit mask/Area) Come break The practice to the cursor position

Forced break Forced break with an ESC key Practice Free run, An arbitrary address, Step

RAM monitor Reference and change of the memory in a practice state Register Reference and change of an arbitrary register

Debug monitor Link to user's progam C language Step of source level, Inspect, Reference and change of variable

1.3 Support PC and OS - Basic configuration .................. IBM-PC and the compatible machine that implement USB1.1 and operate within

Windows environment. - CPU ........................................... Intel PentiumIII 450MHz or higher (Recommendes PentiumIII 1GHz or higher) - Memory space ......................... 256MB and over (Recommended: 512MB and over) - HDD free space ....................... 400MB and over (Recommended: 1GB and over) - OS.............................................. Microsoft WindowsXP(After SP2) Microsoft WindowsVista Microsoft Windows7


- 6 -

1.4 Support CPU AMOT is common with all the following microcomputers. But correspondence software (

or ) is necessary every microcomputer. DebugFactory Builder 4 for

AM1DPDW DebugFactory Builder 4 for AM32LDPDW

ROM Type CPU series CPU name Correspondence Debugger MN101C MN101CF73A

MN101CF91D MN101CF93K MN101CF95G MN101CF97D

MN101CFB6G/D0G MN101E MN101EF16K/16Z

MN101EF29G MN101EF30R MN101EF31G

MN101EF31D/32D MN101EF34D/35A/35D/35G

MN101EF46R MN101EF49N MN101EF50D

MN101EF51A/52A MN101EF57G MN101EF60D

MN101EF63GUB MN101EF76K

MN101EEV77/EEV82 MN101EF77G/EF82G

DebugFactory Builder 4 for AM1DPDW

Flash ROM

MN103L MN103LEV03 MN103LF06N MN103LF08K

DebugFactory Builder 4 for AM32LDPDW

MN101C MN101CROMA,MN101CRAMA MN101CROMB,MN101CRAMB

General ROM

MN101E MN101EROMA,MN101ERAMA MN101EROMB,MN101ERAMB

DebugFactory Builder 4 for AM1DPDW

*1 In the Flash version,1 CPU/1 product package. *2 in the general ROM version, 1 product package contains 8 product types. *3 The closed-door kind is not published in the above-mentioned table. Please inquire of our company in detail. *4 The name end of the general ROM is security type (xxxA : Keycode of adjustable type, xxxB : Keycode of fixed type).


- 7 -

[2] Attached Software and Documents

2.1 CD-ROM Attached CD-ROM includes both Japanese version and English version installers and “Precautions and Warranty Policy”. After reading the “Precautions and Warranty Policy”, start up any one of the installer and install the software. [CD-ROM Directory / File] DFB4_AM1DPDW.exe DFB4_AM32LDPDW.exe/ ......................DebugFactory Builder 4 installer Readme_J.txt ..............................................................................Precautions and Warranty Policy (Japanese version) Readme_E.txt .............................................................................Precautions and Warranty Policy (English version) Manual.jpn <DIR> .......................................................................Document folder (Japanese version) Manual.eng <DIR> ......................................................................Document folder (English version) USBDriver <DIR> ........................................................................USB Driver folder 2.2 C source code debugger(DebugFactory Builder 4) The source code debugger ( ) that operates on Microsoft Windows. It has high performance debugging functions of the reference and the change, etc. in loading the program, execution, the break, and the variable. It is a standard and made by Panasonic Corporation: C compiler for the MN101C/E series, MN103L series is supported, and debugging by the source level is possible.

DebugFactory Builder 4


Attached DebugFactory Builder 4 supports a simulator function. By the simulator function, a compilation and debugging of the software are made not have a target system. Please refer to online help for the usage of the simulator. [[NNOOTTEE!!]] The version of DebugFactory Builder 4 for AM1DPDW and does not synchronize with DebugFactory Builder 4 of the Panasonic Corporation site. The version up has difference in time. 2.3 C compiler for MN101 series, MN103Lseries An official version C compiler made in Panasonic Corporation is attached to DebugFactory Builder 4 of the product. Panasonic semiconductor company does the user support of this C compiler. The support needs user's registration to the Panasonic semiconductor support with registery-key for technical reports. Please refer to the following site for the registration method.

https://www.semicon.panasonic.co.jp/semi-spt/general/

https://www.semicon.panasonic.co.jp/semi-spt/general/


[3] Product Description

3.1 Target Probe Connector It is a probe connector which connects AMOT and the target system. It connects to the target system with attached 10Pin cable.

10pin

9pin

2pin

1pin

PIN/NAME RESET GND DATA VDD N.C. N.C. N.C. DMODE CLOCK GND PIN No 1 2 3 4 5 6 7 8 9 10

MN101CF73A P34 VDD - - - P35 MN101CF91D P44 VDD33 - - - P45 MN101CF93K PC1 VDD - - - PC2 MN101CF95G P00 VDD33 - - - P02 MN101CF97D P44 VDD - - - P45

MN101CFB6G/D0G

NRST VSS

P21 VDD33 - - -

DMOD

P20

VSS

MN101EF16K/16Z P03 VDD33 - - - MMOD P05 MN101EF29G - - - MN101EF30R - - - MN101EF31G - - -

MN101EF31D/32D - - - MN101EF34D

VDD5

- - - MN101EF35A/35D/35G

P01

VDD33 - - -

P02

MN101EF46R P02 VDD33 - - - P03 MN101EF49N P03 VDD33 - - - P05 MN101EF50D P00 VDD5 - - - P01

MN101EF51A/52A P30 VDD5 - - - P31 MN101EF57G P00 VDD5 - - - P01 MN101EF60D P15 VDD33 - - - P14

MN101EF63GUB P00 VDD5 - - - P01 MN101EF76K P00 VDD5 - - - P01

MN101EEV77/EEV82 P41 VDD33 - - - P40 MN101EF77G/EF82G

NRST VSS

P41 VDD33 - - -

DMOD

P40

VSS

MN103LEV03 P10 VDD33 - - - P11 MN103LF06N P10 VDD33 - - - P11 MN103LF08K

NRST VSS

P10 VDD53 - - -

NOCDMOD

P11

VSS

* It is compatible with PX-FW2 made by Panasonic Corporation. * The N.C pin must be open.

- 8 -


[4] Set up

4.1 Installing DebugFactory Builder 4 To use this product, start up the installer included in the attached CD-ROM and install the software into your PC. It is the explanation that made an example as follows. DebugFactory Builder 4 for AM1DPDW

DFB4_AM1DPDW.exe,DFB4_AM32LDPDW.exe

%system%\Program Files\Panasonic\DebugFactory Builder\AM1DPDW

DFB4_AM1DPDW.exe or DFB4_AM32LDPDW.exe

[[NNOOTTEE!!]] The installation is an account with authority of Administrator. [Installing Procedure] (1) Check precautions Read the text file Readme_E.txt on the attached CD-ROM. The latest information which is not mentioned in each manual may be described in this precaution. (2) Install software Start the installer ( ) attached on CD-ROM and install the software by following the dialog message. As the type selection dialog is displayed during installation, select the type you purchased. [[NNOOTTEE!!]] The installation is by default " ". "%system%" is a system disk of Windows. It is "C:" in a general IBM/PC i386 system STEP1 The following is the setup display. Click “Next” button.

STEP2 Read the license agreement carefully. If you accept all terms of the agreement, click on the “Yes" button.

- 9 -


STEP3 Select the folder in which the files should installed. When installing them into the default folder, click on the “Next” button. When changing the installing folder, click on the “Browse…” button and specify the folder.

STEP4 Specify the folder name which is to be added to the “program” menu in the Windows start menu. When changing the folder name, input any name to the “Program Folders” column. When selecting the default folder, click on the “Next” button.

STEP5 It is a screen where the MPU, the serial number and the installation key are input. Please input the MPU, the serial number and the install key from the written guarantee of the product attachment, click on the “Next” button.

- 10 -


STEP6 After the install file is finished coping, the set up finished dialog will appear, and click on the “Finish” button to end the set up.

4.2 The addition of the microcomputer

4.2 The addition of the microcomputer

A support microcomputer is common and can use AMOT. DebugFactory Builder 4 for AM1DPDW or is necessary every microcomputer.



When add a microcomputer kind, start an installer. Because a setup menu is displayed, I choose "Add MPU/Unit", and please click "to" next.

The screen which the said article inputs a MPU, serial number and an installation key into as well as STEP5 of "

" is displayed. Input a MPU, serial number, an installation key from a certificate attached to the product to add, and please click "to" next.

4.1 Installing DebugFactory Builder 4

The added microcomputer becomes selectable in an article number of the target setting of DebugFactory Builder 4. 4.3 The addition of the unit When use plural AMOT (units), please go like " ". But AMOT which can connect to a PC is only one of them. The use is not possible by a plural number at the same time. 4.4 Update of the software The latest installer of DebugFactory Builder 4 for AM1DPDW and shows it in homepage. The update starts the installer which downloaded, and please choose "Repair/Update" of the setup menu.

- 11 -


4.5 Installing USB drivers The Windows system asks for driver installation when connecting AMOT to PC with a USB cable after DebugFactory Builder 4 for AM1DPDW or DebugFactory Builder 4 for AM32LDPDW installation. Follow the steps below to install a driver. [[NNOOTTEE!!]] The installation is an account with authority of Administrator. When it is used an old product (AM1 Debug Probe DWire or AM32L Debug Probe DWire), please install a USB driver for AMOT after deleting an old driver. Please refer to later description about the deletion of the old driver. STEP1 The automatic search of the USB driver is performed when I connect AMOT to the PC which Windows7 is installed in for the first time. Because the message of the chart below is output after this, I click [and I refer to a computer, ... ...].

STEP2 A dialogue window appointing the reference place of the driver file next is displayed. Please set folder "USBDriver" of the CD-ROM attached to the product with the reference button of the dialogue. In addition, please check it in "Search the subfolder" displayed by a dialogue window.

Please set folder " USBDriver " of the attached CD-ROM.

- 12 -


STEP3 After the setting of the driver file, the installation of the driver is started when I click [Next (N)].

STEP4 There is the case that a dialogue window showing warning of the security is displayed. In that case, please click [I Install this driver sofrwareware].

STEP5 Finally the message window which a device driver was installed in definitely is displayed. The name confirms that it is displayed with "OBJECT WinUSB Device", and please click [Close (C)]

- 13 -


4.6 Uninstalling In order to uninstall the DebugFactory Builder 4 for AM1DPDW or DebugFactory Builder 4 for AM32LDPDW, start the attached installer again, check the “delete” box and execute the uninstallation. In order to delete the USB driver, open the “system” menu of the control panel in the Windows, select the “OBJECT USB Device” in the “device manager” of the hardware tab, and delete OBJECT WinUSB Device.

- 14 -

4.7 Uninstall of old USB driver When it is used an old product(AM1 Debug Probe DWire or AM32L Debug Probe DWire), please install a USB driver for AMOT after uninstall an old driver. [[NNOOTTEE!!]] The installation is an account with authority of Administrator. STEP1 Please open device manager of Windows. When connect old product (AM1 Debug Probe DWire or AM32L Debug Probe DWire) to a PC, "OBJECT" is displayed in device manager.


STEP2 The USB driver corresponding to a connected product is displayed when open "OBJECT" of the device manager. Please choose the Uninstall of a menu displayed this indication by a right-click.

STEP3 Because a dialogue of the confirmation is displayed, complete uninstall with a "OK" button.

- 15 -


- 16 -

[5] User Program Development

It is necessary to understand the following restrictions to debug the program that a user made in .

DebugFactory Builder 4 5.1 Limitation on User Program Development 5.1.1 Debugger occupation resources User cannot use the following CPU resources because they are occupied by AMOT.

PIN/NAME RESET OCDDATA DMODE OCDCLK MN101CF73A NRST/P27 P34/VLC3 DMOD P35/VLC2 MN101CF91D NRST/P27 P44/TXD1B/SBO1B DMOD P45/SBT1B MN101CF93K NRST/P27 PC1/TXD0B/SBO0B/LED1 DMOD PC2/SBT0B/LED2 MN101CF95G NRST/P27 P00/SDA3/SBO3 DMOD P02/SBT3/SCL3/BUZZER MN101CF97D NRST/P27 P44/TXD0B/SBO0B DMOD P45/SBT0B

MN101CFB6G/D0G NRST/P27 P21/IRQ1/SBO0/TXD0 DMOD P20/IRQ0/SBT0 MN101EF16K/16Z NRST/P27 P03/SDA2A/SBO2A MMOD P05/SCL2A/SBT2A

MN101EF29G NRST/P27 TXD1A/SBO1A/TM8IOB/LED1/P01 DMOD SBT1A/TM9IOB/LED2/P02 MN101EF30R NRST/P27 TXD1A/SBO1A/TM8IOB/LED1/P01 DMOD SBT1A/TM9IOB/LED2/P02 MN101EF31G NRST/P27 TXD1A/SBO1A/TM8IOB/LED1/P01 DMOD SBT1A/TM9IOB/LED2/P02

MN101EF31D/32D NRST/P27 TXD1A/SBO1A/TM8IOB/LED1/P01 DMOD SBT1A/TM9IOB/LED2/P02 MN101EF34D/35A/35D/35G NRST/P27 TXD1/SBO1/TM8IOB/LED1/P01 DMOD SBT1/TM4IOC/LED2/P02

MN101EF46R NRST/P27 TXD1B/SBO1B/TM0IO/P02 DMOD SBT1B/TM1IO/P03 MN101EF49N NRST/P27 P03/SDA2A/SBO2A MMOD P05/SCL2A/SBT2A MN101EF50D NRST/P27 OCD_DATA/P00 DMOD OCD_CLK/P01

MN101EF51A/52A NRST/P27 OCD_DATA/P30 DMOD OCD_CLK/P31 MN101EF57G NRST/P27 OCD_DATA/LED0/P00 DMOD OCD_CLK/TM9IOB/LED1/P01 MN101EF60D NRST/P27 P15/AN6/SBO0A/TXD0 DMOD P14/AN5/SBT0A

MN101EF63GUB NRST/P27 OCD_DATA/LED0/P00 DMOD OCD_CLK/TM9IOB/LED1/P01 MN101EF76K NRST/P27 OCD_DATA/LED0/P00 DMOD OCD_CLK/TM9IOB/LED1/P01

MN101EEV77/EEV82 NRST/P27 P41/SBO0/TXD0 DMOD P40/SBT0 MN101EF77G/EF82G NRST/P27 P41/SBO0/TXD0 DMOD P40/SBT0

MN103LEV03 NRST P10/TM0IO/OCD_SDA NOCDMOD P11/TM1IO/OCD_SCL MN103LF06N NRST P10/TM0IO/AN12/OCD_SDA NOCDMOD P11/TM1IO/AN13/OCD_SCL MN103LF08K NRST P10/OCD_SDA NOCDMOD P11/OCD_SCL

5.1.2 IVBM bit of MEMCTR register(MN101C/E series) IVBM bit of MEMCTR register cannot be changed. (vector area = fixed to 0x04000) 5.1.3 Interrupt during break All interrupts are disabled during the monitoring execution (during break). 5.1.4 Undefined instruction When the undefined instruction execution interrupt is generated in the user program, it is processed as a undefined instruction execution break and the program cannot be reexecuted. 5.1.5 Watchdog The watchdog timer is cleared in the sub-monitor program. Therefore the cycle of the watchdog timer is different in target program execution just after the sub-monitor program execution. When a reset by a watchdog timer occurred, for a keycode to become effective once again by the fixed type, a keycode of a microcontrollers can't refer to built-in flash ROM any more, and is the running out of control state. Please do the INIT command or the starting which is debugging once again in this case. See “ ”(page 19) for keycode and secure support. [6] Secure Support by Keycode* MN101EF49N cannot stop built-in watch dog timer 2(WDT2) by the break. On this account I operate an RINGCTR register at the time of the break.

When reset of WDT2 occurred, I cannot synchronize with a monitor. In this case, start the debugging again, or Reset command.


- 17 -

5.1.6 Special Function Registers Special function registers (CPUM, MEMCTR, SBNKR, DBNKR)(*1) are changed at the time of Go and Step. *1 MN101EF63GUB includes LPOWCNT and LPOWPRT. MN101EF49N includes RINGCTR. 5.1.7 Monitor program(MN101C/E series) In the Flash type and general ROM type, the monitor program should be located on user ROM.

Monitor code 96 bytes

5.1.8 Monitor program(MN103L series) The monitor program for debugging occupies a part of the RAM of the microcomputer. Access and setting of the stack pointer are prohibition in this area.

CPU Area MN103LEV03 0x1000FC00 - 0x1000FFFF MN103LF06N 0x00007E00 - 0x00007FFF, 0x10007E00 - 0x10007FFF MN103LF08K 0x00004E00 - 0x00004FFF, 0x10004E00 - 0x10004FFF

[[NNOOTTEE!!]] When an above area was changed by a target program in the case of MN103LEV03, the later debugging is not possible. 5.1.9 Interrupt vector table(MN101C/E series) The interrupt vector table is written in the monitor program (Start.asm). When an interrupt occurred, the vector table written in the monitor program (Start.asm) is used. Interrupt vector table 0x4000

5.1.10 Stack(MN101C/E series) At break, the processing inside the monitor uses over ten bytes of user’s stack depending on the type. Therefore, leave over ten bytes from the lowest address of stack pointer which is estimated by the user program.

Stack 14 bytes 5.1.11 Stack pointer initial value The stack pointer is written in the monitor program (Start.asm) at reset. The initial value varies by type. The stack pointer initialization part of the monitor program (Start.asm) can be changed.

Stack pointer 0x0100


- 18 -

5.2 The attention of the debugger 5.2.1 Limitation on DebugFactory Builder 4 for AM1DPDW - Real-time traceing facility is not included. - A breaking point can establish plural up to at most 255 points. The microcontrollers built-in function is up to 2 points, and others will be software rewriting. - If Flash ROM is programmed with A/E command, the programming of Flash ROM takes some time at the execution. 5.2.2 Target setting In DebugFactory Builder 4, each setting of Target CPU is set with the target setting. Alterable items are as follows. (1) Product type Always select the type of microcontroller included in the target system. When setting wrong types, it does not work normally. (2) Type Please choose "Debug probe". When a target system debugs only few case and software, choose an instruction set simulator. (3) Stack pointer initial value Specify the stack pointer at reset. When changing the stack pointer initialization source of the monitor program (Start.asm), change the propertiy, too. (4) Debugging Information type(MN103L series) Set the kind of the debugging information. (5) Debugging Information buffer size(MN103L series) Set the buffer size of the debugging information. It is an M byte unit. (6) OSC frequency (Hz) Correctly input the frequency input ("Hz" unit) to microcontroller on the user target system. If a wrong value is set, defects (ex. rewriting into Flash ROM is not possible) occur. The initial value of each type is as follows: (7) XO frequency (Hz) Input the correct frequency input ("Hz" unit) to microcontroller on the user target system (serious defects do not occur even if a wrong value is set). The initial values are as follows: (8) Memory mode Specify the memory mode. The default setting is single chip mode.The memory extension mode is supported. *AMOT does not support processor mode. (9) DWire clock (MHz) Set a clock of the DWire interface. The default is 3.0MHz. Other frequcencies can be selected, but normaly use the defalut value. When debugger operation is not stable, it might be helpful to lower the set clock. (10) Keycode file Specify a keycode file used for secure support by the keycode method. See “ ”(page 19) for keycode and secure support.

[6] Secure Support by Keycode

5.2.3 Instruction set simulator DebugFactory Builder 4 contains an instruction set simulator function. When there is not a target system, you can debug software. Please refer to the simulation of the online help in detail.


- 19 -

[6] Secure Support by Keycode

DebugFactory Builder 4 is supporting security of a keycode system to protect a program of a microcontroller and data of a target system from unjust reading. DebugFactory Builder 4 compares the contents of the keycode file specified by microcontroller keycode and project on the target system at the beginning of start of debugging (CTRL-T) command process. When being different in the contents, the dialogue of whether all flash ROM of a microcontroller on the target system is erased by the adjustable type or the connection is canceled by the fixed type is indicated. When there are no right keycode files, it isn't possible to read flash ROM of a microcontroller on the target system. 6.1 Keycode Type The keycode type has the "adjustable type" which can set keycode area optionally and the "fixed type" on which a keycode area is fixed. The keycode type is different depending on microcontrollers.

CPU type Keycode type Address area reference MN101CF73A 0x4000～0x4FFF MN101CF91D 0x4000～0x43FF MN101CF93K 0x4000～0x4FFF MN101CF95G 0x4000～0x43FF MN101CF97D

Adjustable

0x4000～0x4FFF MN101CFB6G/D0G Fixed Built-in flash core MN101EF16K/16Z

MN101EF29G MN101EF30R MN101EF31G

MN101EF31D/32D MN101EF34D/35A/35D/35G

MN101EF46R MN101EF49N MN101EF50D

MN101EF51A/52A MN101EF57G MN101EF60D

MN101EF63GUB MN101EF76K

MN101EEV77/EEV82 MN101EF77G/EF82G

Fixed

Built-in flash core

MN103LEV03 MN103LF06N MN103LF08K

Fixed

Built-in flash core

6.1.1 Adjustable type The part of the built-in flash ROM area of a microcontroller is used as a keycode area. The area which can be used is different in a keycode area depending on microcontrollers. When some data exists in a keycode area, a keycode file isn't designated or you can't assume that there is difference in a keycode file and data for starting of debugging. But, when Chip-erase is carried out in this case, it's possible to begin debugging. 6.1.2 Fixed type An established exclusive keycode area is used for built-in flash ROM of a microcontroller. When a keycode is set as a microcontroller, please be sure to designate a keycode file. When not understanding a keycode, debugging can't be begun. [[NNOOTTEE!!]] When a reset by external input or a watchdog timer occurred during debugging, for a keycode to become effective once again by the fixed type, a keycode of a microcontroller can't refer to built-in flash ROM any more, and is the running out of control state. Please do the INIT command or the starting which is debugging once again in this case.


6.2 Keycode File The keycode file is a text file based on certain format. Format: 1st line<Keycode storage specification address>

The adjustable type describes the start address in which keycode data is stocked. The fixed type is fixing of 0x0000.

2nd line<Keycode count> The adjustable type describes the number of the keycode data. But, this number has to be the data which is written on the address only 1 made minus from the address designated by <Keycode storage specification address>. The fixed type is fixing of 0x10.

3rd line<Keycode data> Data is described by a comma separateness.

Example of write date method:

3rd line : keycode data

0x4001 0x07 0x40,0x00,0x00,0xC2,0x40,0x00,0x00

1st line : keycode storage specification

2nd line : keycode count

Example of dedicated area method:

0x0000 0x10 0x01,0x23,0x45,0x67,0x89,0xAB,0xCD,0xEF,0xFE,0xDC,0xBA,0x98,0x76,0x54,0x32,0x10

3rd line : keycode data

In the above example of adjustable type, if the data on memory of microcontroller on the target system is the following content, the keycode matches. Address Data 0x4000 0x07 0x4001 0x40 0x4002 0x00 0x4003 0x00 0x4004 0xC2 0x4005 0x40 0x4006 0x00 0x4007 0x00

Keycode storage specification address

Keycode data

Keycode count

6.3 Creating a Keycode File The keycode file is compatible with PX-FW2 made by Panasonic Corporation. The keycode file of adjustable type can be created by the DebugFactory Builder 4 ”Tool(T)”>”Create key code file (Z)” command from Flash ROM on the current target sysetm. The keycode area does not affect user program execution. 6.4 Keycode File Registration To register the keycode file created in DebugFactory Builder 4 project, register it on property: keycode file in the target setting.

- 20 -


- 21 -

[7] Start-up Program

A startup program including the monitor program to become the model that DFB4 simplifies a start of the development is attached. The startup program is an offer in the source code. [[NNOOTTEE!!]] In user program development , a program can be written from main () function with the start-up program as a model. The vector tables included in Start.asm should be edited to use interrupts. Please note that the 31st that the debugger uses might not have the description in LSI manual. 7.1 Start-up Program Specification The start-up program consits of the monitor program (Start.asm) including start-up and C source file including sample main() function. Program itself does not have special facility. 7.2 File Configuration of Start-up Program When making a project as "Sample", the following file consists of it. Sample.df4, Sample.dft ···················Start-up project file for DebugFactory Builder 4 Test.c ··············································C source file including main() function Start.asm··········································Monitor program source file including ROM start-up Sample.mak ·····································Makefile complying with the make tool attached in DebugFactory Builder 4 7.3 Start.asm It is a monitor program file including ROM start-up. The monitor program (Start.asm) should be linked to the user program for development (debug) using AMOT. To link to the user program, parts depending on the user program, such as a vector table should be edited as needed. [[NNOOTTEE!!]] The following explanation is articles for MN101C/E series. The link of the monitor program is unnecessary in the MN103L series.. Part where Start.asm cannot be edited (1) SECTION definition _STEXT SECTION CODE,PUBLIC,0 _CONST SECTION CODE,PUBLIC,1 _GCONST SECTION CODE,PUBLIC,1 _ROMDATA SECTION CODE,PUBLIC,1 _GROMDATA SECTION CODE,PUBLIC,1 _TEXT SECTION CODE,PUBLIC,0 _CODEEND SECTION CODE,PUBLIC,1 _DATA SECTION DATA,PUBLIC,1 _GDATA SECTION DATA,PUBLIC,1 _BSS SECTION DATA,PUBLIC,1 _GBSS SECTION DATA,PUBLIC,1 _BSSEND SECTION DATA,PUBLIC,1 (2) Monitor interrupt vector (31th) da A(MonInterrupt) ; 31:0x407C:interrupt vector ( The change is impossible. ) (3) Monitor code area ; Monitor #if 1 ; When not using monitor, 0. ;;;;; Start of monitor program. Do not change. ;;;;; Do not set breakpoints here. : OCDMonitorEnd: #endif


[8] How to use DebugFactory Builder 4

8.1 Start of DebugFactory Builder 4 Start DebugFactory Builder click the Start Menu > Programs > Panasonic DebugFactory Builder 4 > AM1DPDW > DFBuilder of Windows or double-click four short cut icon DebugFactory Builder 4 for AM1DPDW or

of the desktop. DebugFactory

Builder 4 for AM32LDPDWWhen starting up DebugFactory Builder 4 for the first time, the project selection screen is displayed. Chek the “New project creation” and click on the ”OK” button for the Flash version. [[NNOOTTEE!!]] Please use DebugFactory Builder in an account with authority of Administrator.

8.2 Making of a project STEP1 The dialog to choose project classification. The project classification chooses "Standard (S)".

- 22 -


STEP2 This dialog is a setting of the project. The setting of the project sets "Project name (P)", and specifies folder "Folder (S) preservation ahead" that preserves the project file. Moreover, check box "Start-up assembler (A)" that exists in the source file added automatically and "Sample C source file (M)" are checked.

STEP3 This dialog is a setting of the language tool. has a C compiler built-in. When involving C compiler is used, attach a check of "Use the built-in language tool (T)". When use other language tools, attach a check of "Use a following language tool (S)", and please appoint a compiler / assembler / linker.

DebugFactory Builder 4

STEP4 The dialog of the setting of the target. The push button "New (C)", and please perform target setting.

- 23 -


STEP5 The dialog of the target setting. The set initial value Product type / Type / Debugging information type(MN103L series) / Debugging information buffer size(MN103L series) / Stack pointer initial value / OSC frequency[Hz] / XO frequency[Hz] / Memory mode / DWire clock[MHz] / Key code file. Please refer to " " about each item. 5.2.2 Target settingWhen the key code to microcomputer is not set, make the column of the key code file the blanks.

STEP6 The preservation folder confirmation dialog of the project made with STEP5 is displayed. Please click button "End(E)".

STEP7 When there is not a destination folder, a window confirming the making of the folder is displayed.

- 24 -


8.3 DebugFactory Builder 4 Start-up Display DebugFactory Builder 4 consists of three windows (project tree, cord window, command window). But do not recognize AMOT only by DebugFactory Builder having started in this state.

Code Window

Project tree

Command Window

8.4 ROM image buffer DebugFactory Builder 4 for AM1DPDW and has the image buffer of the flash memory for the renewal number of times restraint of the flash memory and the transaction speed improvement of the debugger.


This image buffer is managed by the sector unit of the flash memory. It is retrieved at the time of the first time access of the sector to fall under by flash memory. Reference and the change of the memory are performed for an image buffer. When the contents of the image buffer were changed, reflect it in flash memory by a command of the practice (G/P/T command).

Microcomputer DebugFactory Builder for AM1DPDW

Image buffer Flash ROM

The reflection to the flash ROM only as for program

load, execution / step

The first time of the sector accesses the reading to the

image buffer

- 25 -


8.5 Software breakpoints DebugFactory Builder 4 can set a break point to 255 points at the maximum. The breakpoint to two points uses a break function in the microcomputer. The break points more than three points become the Software renewal. The Software renewal for a practice / step of the flash memory in the microcomputer. The right or wrong of the software renewal of the General tab of Debug option do "not use software break", and can choose it. 8.6 Compiling the Start-up Program AMOT includes a start-up program as a model in order to facilitate the programming for AMOT. The startup program just after the installation isn't compiled. Compilation is necessary for execution. To compile the program, select the “Make” menu of the DebugFactory Builder 4 menu bar and execute “Make(M)”

[[NNOOTTEE!!]] The built-in compiler is installed in the following folders (normal installation). The include pass of the compiler tab / assembler tab to set in a compilation option dialogue chooses an INCLUDE folder in the following folders. The library of the linker tab chooses a library among an LIB folder. 101C series:C:\Program Files\Panasonic\DebugFactory Builder\AM1DPDW\BuiltInCC\X_XXX\CC101C 101E series:C:\Program Files\Panasonic\DebugFactory Builder\AM1DPDW\BuiltInCC\X_XXX\CC101E 103L series:C:\Program Files\Panasonic\DebugFactory Builder\AM32LDPDW\BuiltInCC\X_XXX\CC103S * X_XXX is a version and a release number [[NNOOTTEE!!]] When not connecting AMOT, or the case when you don't connect AMOT equal to an input serial number can't use a built-in compiler.

- 26 -


8.7 Starting Debugging and Loading the Program DebugFactory Builder 4 communicates in a target microcomputer and DWire interface in “start of debugging” (CTRL-T) of the debugging menu. And check the keycode.

In the keycode of adjustable type, the dialog “Key code authentication falied. Do you execute chip erase?” appears. It asks whether to erase Flash ROM on the target system and connect, or cancell the connedtion If clicking on ”Yes”, Flash ROM on the target system will be erased. If clicking on ”No”, the start of debugging will be halted. After clicking on ”Yes” and erasing ROM, the following dialog appears. In the keycode of fixed type and general ROM type, this dialog does not appear. When the keycode differs, the message “Key code does not match” appears and the start of debugging is halted.

Keycode of adjustable type Keycode of fixed type

[[NNOOTTEE!!]] When the correct keycode is specified and microcontroller on the target system is chip-erased. The above dialog does not appear.

- 27 -


"Do you want to load execution file?" is the dialog that the project program asks loading. In the Flash type, if clicking on "Yes(Y)", the start-up program will be loaded into chip on the target system. In the general ROM type, writing into the target is not executed, and debug information is read.

[[NNOOTTEE!!]] The keycode function is had built-in loads an object code, only the data different from the contents of ROM of a target microcontroller is changed. Therefore data of the address in which an object code doesn't exist won't be 0xFF by the load command. [[NNOOTTEE!!]] In AMOT, program loading is to write a program in microcontroller built-in Flash ROM on the target system. [[NNOOTTEE!!]] When connecting failes at start of debugging (CTRL-T) command execution, check the followings: - The powr of the target system is OFF. - The connection with the target system is not proper. - The clock of the target microcontroller is not supplied. - The target microcontroller reset is driven to the active side.

- 28 -


8.8 Setting Breakpoints and Executing the Start-up Program Open the start-up project and connect to the target. Then the program is loaded to microcontroller on the target system through AMOT. The lines marked with ”○” are displayed at the left frame area of the source display window. This marking indicates that the code is generated in these lines. Also, these lines are the source lines which are settable as the breakpoint. [[NNOOTTEE!!]] Besides clicking on the source line, a breakpoint can be set/relesed by putting F9 key at any carsor position on the source window.

Setting/releasing breakpoints by F9

Setting/releasing breakpoints by clicking

[[TTIIPPSS!!]] DebugFactory Builder 4 can establish even 255 breaking points. The microcontroller built-in function is up to 2 points. When using the microcontroller built-in function, it's possible to establish a new breaking point by disable or delete an effective breaking point at present. When I want to use only a storehouse function in the microcomputer, please classify a check into "Not use software break" in the tool debugger option of the menu.

- 29 -


- 30 -

8.9 Typical Debug Commands 8.9.1 Forced break (ESC) Forced break pushes the ESC key during the practice of the user's program. 8.9.2 Breakpoints (F9) After setting the breakpoint (BP) in initialize();line of main() function, the start-up program execution is started with GO command (F5 key). Shortly after the program execution, the program stops at the breakpoint. At that time, the source window indicates initialize();line in main() function where the program currently stops. As above, it is possible to set breakpoints at any source position (execution line) and debug the program operation you need. Can set the break point to 255 points at the maximum. Use the debugging function in the microcomputer to the 2 point, but become the software renewal after the 3 point. [[NNOOTTEE!!]] The software renewal is performed in the case of practice (F5) and one instruction step (F8), function step (F10) if necessary. When carry it out again from the breakpoint of the software renewal, return it and carry out one instruction step, and perform renewal again, and the practice works to write renewed contents in the debugger inside. 8.9.3 One Instruction Step Execution (F8)

8.9.3 One Instruction Step Execution (F8)

One instruction step execution is the operation that break condition is generated again after executing only one instruction of CPU. When one instruction step execution (F8 key) is executed again, it proceeds to the next instruction. [[NNOOTTEE!!]] There is it not to be able to be finished with needing time for processing or the infinite loop depending on the contents of the C source line when it is not possible for the operation of the debugger. In this case please stop it by forced break (F9) or a reset command. 8.9.4 Function Step Execution (F10) Function step execution (F10) is the step execution command similar to “ ”. With this command, step by the function can be executed in the C source code debugging. When stepping inside the function, use the instruction step execution (F8). When stepping the function call line itself, use the function step execution (F10). [[NNOOTTEE!!]] When step by a function, set a Come break in the next order of the order to call a function in the debugger inside and carry out a G command. On this account stop at the breakpoint when an effective break point was set in a function. 8.9.5 Come Command (F7) Come command (F7) is the execution command which is used at the actual debugging. This command can execute the debugging to the arbitrary source line which can be executed on the code window of C source code debugger (DebugFactory Builder 4), and break. Move the source line cursor of the source window and input come command (F7). Then debugging is executed to the position at which the cursor is placed when inputting the come command, and it breaks. [[NNOOTTEE!!]] When an effective break point was set by the line of the Come break, after program practice, stop at the breakpoint. When the line of the Come break programs it, and it is not carried out, a practice state is continued. In this case please stop it by forced break (F9) or a reset command.


- 31 -

[9] General ROM Version

DebugFactory Builder 4 for AM1DPDW has the general ROM version for ROM type microcontrollers. The product type can be selected from among 8 types after installing the general ROM version. The types differ in monitor program allocation, CPU core and security type. Every type needs debugger support (*1) for user ROM. The support is required before mask ROM order. The general ROM version of DebugFactory Builder 4 has some limitations on its debug function compared to the Flash version. [Adjustable type 101xxxxA / Fixed type 101xxxxB]

Name 101CROMx 101CRAMx 101EROMx 101ERAMx CPU core MN101C MN101E

Monitor allocation ROM RAM ROM RAM *1 Support for user ROM depends on monitor allocation. The internal ROM type needs the link of the monitor program. The internal RAM needs the

setting of the OCDINT interrupt vector and protection of the internal RAM monitor area. 9.1 Precautions on Debugger [Important] In the genral ROM version, you are responsible for debugger support to user ROM. Even if a debugger cannot get started despite debugger support (target connection), we do not investigate or adjust your system and ROM code. We do not compensate any damages caused by the user program and the monitor program when you change the ROM code for debugger support. 9.2 Monitor Program Type The monitor program of the genral ROM version has 1.ROM type and 2.RAM type. One of them should be built into the user ROM. The source code of the monitor program is included on the CD (*3). The monitor program code is compatible with the Flash version. If a program developed with the Flash version of AMOT is replaced with ROM, the general ROM version of AMOT can be used.

Monitor type RAM monitor type (101CRAMx/101ERAMx) ROM monitor type (101CROMx/101EROMx)

Specification

- Locating the monitor program (*2) in RAM. - Setting the monitor area head address in OCDINT vector (*1). - Debugger automatically loads the monitor program according to the value of OCDINT vector.

- Linking the start-up including the monitor program (*2) into the user program. - Editing other than the monitor part of the start-up program to suit the user program. Porting the monitor part of the start-up program to the user start-up program.

Merit - No need to link the monitor code to ROM. - Only OCDINT vector supports for ROM code

- No need to use RAM. - The monitor code is not destroyed by program. - The code developed by the Flash version can be used.

Demerit

- Internal RAM area (*2) where the monitor is located cannot be used in the user program. - Need for care so that internal RAM area where the monitor is located is not destroyed in the user program.

- ROM for the monitor program (*2) is consumed. - Operation and evaluation time are increased by linking the monitor.

*1 OCDINT vector = 0x407C to 0x407F addresses of ROM area. *2 Monitor program size is 128-byte. Any address can be used in RAM area that DDMA access is possible through OCD. *3 You can get a monitor source code for free before purchasing our product. Please contact us for more information.


9.2.1 RAM Monitor Type [Support by users] - Selecting any continuous 128-byte in intenal RAM area for the monitor program.(*1) - Checking that the user program does not destroy the selected monitor program area. - Setting the head address of the monitor program area selected in internal RAM area to the OCDINT vector. *1 DebugFactory Builder 4 loads the monitor program into the specified RAM area according to the contents of the OCDINT vector.

0x000000 Internal RAM

Monitor program

0x003F00 Special register Branch at OCDINT

generation. 0x004000

Internal ROM 0x00407C OCDINT vector

Set the head address of the RAM monitor program to the vector.

[Figure 1] Method 1 Memory Map in RAM Monitor Type

9.2.2 ROM Monitor Type [Support by users] - Linking the start-up program (Start.asm) which includes the monitor program to the user program. - Porting the monitor program part in the start-up program (Start.asm) to the user program.

0x000000 Internal RAM

db can not be changed within Start.asm.

0x003F00 Special register

0x004000

OCDINT vector 0x00407C Branch at OCDINT generation. Internal ROM

Monitor program

[Figure 2] Method 2 Memory Map of ROM Monitor Type

- 32 -


- 33 -

9.3 Debugger Function - Data referrence modification (RAM and registers only) - User program execution - Forced break - Step execution (instruction unit, C/assembler source level) - COME break (disassemble instrution unit, C/assembler source line) - Pre-execution break (2 points) - With data mask function, R, W, R/W access break (1 point) - Data area access break (between 2 points) - RAM monitor affecting execution time) 9.4 Limitation on Debugger Function - ROM contents cannot be changed since the ROM emulation method is not used. - Load command reads debug information but does not write to the target ROM. - In the RAM monitor type, when the monitor area is rewritten by the user program, the subsequent debugger

operation is indefinite. 9.5 Limitation on User Program Development 9.5.1 Debugger occupation resources User cannot use the following CPU resources because they are occupied by AMOT.

Occupation resources NRST OCDDATA DMODE OCDCLK *1 The reset pin can drive form the target system. Drive the reset (NRST) pin of the target system with open-drain. 9.5.2 IVBM bit of MEMCTR register IVBM bit of MEMCTR register cannot be changed. (vector area = fixed to 0x04000) 9.5.3 Interrupt during break All interrupts are disabled during the monitoring execution (during break). 9.5.4 Undefined instruction When the undefined instruction execution interrupt is generated in the user program, it is processed as a undefined instruction execution break and the program cannot be reexecuted. 9.5.5 Special Function Registers Special function registers (CPUM, MEMCTR, SBNKR, DBNKR)(*1) are changed at the time of Go and Step. *1 MN101EF63GUB includes LPOWCNT and LPOWPRT. MN101EF49N includes RINGCTR. 9.5.6 Reset start address The reset start address is written in a monitor- programmed (Start.asm). When a reset is startted, it branches in the reset start address. Please describe a user program in the main function. The main routines of the start-up program is written in Test.c.

Reset start address 0x04000


- 34 -

9.5.7 Monitor program In 101CROMx/101EROMx of the general ROM type, the monitor program should be located on user ROM. The located address should be written in the OCDINT vector. In 101CRAMx/101ERAMx of general ROM type, the monitor code is located on RAM and user ROM is not consumed.

Monitor code 96 bytes

9.5.8 Interrupt vector table The interrupt vector table is written in the monitor program (Start.asm). When an interrupt occurred, the vector table written in the monitor program (Start.asm) is used. Interrupt vector table 0x4000

9.5.9 Stack At break, the processing inside the monitor uses over ten bytes of user’s stack depending on the type. Therefore, leave over ten bytes from the lowest address of stack pointer which is estimated by the user program.

Stack 14 bytes

9.5.10 Stack pointer initial value The stack pointer is written in the monitor program (Start.asm) at reset. The initial value varies by type. The stack pointer initialization part of the monitor program (Start.asm) can be changed.

Stack pointer 0x0100


[10] Target System Reference Circuits

The following reference circuits show the minmum pin processing which can be operated. Please refer to LSI manual etc. for CPU without the description. 10.1 MN101CF73A

DATA

CLOCK

nRESET

P27/NRST

DMODE

RESET

AM1 Debug Probe

(KDK)

(KDK)

MN101CF73A

(Panasonic)MN101CF73A64P TQFP

P27/NRST11

VDD4

VSS12

P34/VLC31

P35/VLC22

DMODE5MMOD 8

OSC1 7

OSC2 6

XO 9

XI 10

SMTE3

RB501

MCH18FN104ZK0.1uF

224466881010 9 9

7 7

5 5

3 3

1 1

C

MCH1

8FN1

04ZK

0.1u

F

103

+3.3V

103 +3.3

V

+3.3V

R6 105

X1

HC-4

9/S3

9.88

4MHz

C19

MCH18FN200ZK20p

C18

MCH18FN200ZK20p

R10

105

X2 NC38

32.7

68KH

z

C17

MCH18FN101ZK100p

C16

MCH18FN101ZK100p

103

MCH1

8FN1

04ZK

0.1u

F

+3.3V

10.2 MN101CF91D

DATA

CLOCK

nRESET

P27/NRST

DMODE

RESET

AM1 Debug Probe

(KD

K)(K

DK)

(Panasonic)MN101CF91D 48P TQFP

MN101CF91D

MMOD 6

OSC2 2

OSC1 3

XO 5

XI 4

DMODE36

P27/NRST7

VSS1

VDD188

P45/SBT1B42

P44/TXD1B/SBO1B41

VDD339

SMTE3

RB501

MCH18FN104ZK0.1uF

224466881010 9 9

7 7

5 5

3 3

1 1

103

+3.3V

103 +3.

3V

R6

105

X1

HC-

49/S

39.

884M

Hz

C19

MCH18FN200ZK20p

C18

MCH18FN200ZK20p

R10 105

X2

NC3

832

.768

KHz

C17

MCH18FN101ZK100p

C16

MCH18FN101ZK100p

103

MCH

18F

N104

ZK0.

1uF

+3.3V C

MC

H18

FN1

04ZK

0.1u

F

+3.3V

C

MCH

18F

N104

ZK0.

1uF

+1.8V

- 35 -


10.3 MN101CF93K

DATA

CLOCK

nRESET

P27/NRST

DMODE

RESET

AM1 Debug Probe

(KDK)

(KDK)

(Panasonic)

MN101C93K

100pin LQFPMN101C93K

VSS35

VSS16

VDD19VDD32

DMODE24MMOD 22

OSC1 17

OSC2 18

XI 20

XO 21

P27/NRST23

SBT0B/LED2/PC211

TXD0B/SBO0B/LED1/PC110

SMTE3

RB501

MCH18FN104ZK0.1uF

224466881010 9 9

7 7

5 5

3 3

1 1

103

+3.3V

103 +3.3

V

103

MCH1

8FN1

04ZK

0.1u

F

+3.3V C

MCH1

8FN1

04ZK

0.1u

F

+3.3V

105

105 MCH18FN101ZK

100p

MCH18FN101ZK100p

NC38

32.7

68KH

zHC

-49/S3

9.88

4MHz MCH18FN200ZK

20p

MCH18FN200ZK20p

10.4 MN101CF95G

DATA

CLOCK

nRESET

P27/NRST

DMODE

RESET

AM1 Debug Probe

(KD

K)(K

DK)

(Panasonic)

MN101CF95G

MN101CF95G 80P TQFP

VSS14

MMOD 17DMODE7

VDD3310

VPP9

SDA3/SBO3/P0019

P27/NRST18

OSC1 13

OSC2 12

XO 16

XI 15

P02/SBT3/SCL3/BUZZER21

VDD1811

SMTE3

RB501

MCH18FN104ZK0.1uF

224466881010 9 9

7 7

5 5

3 3

1 1

103

+3.3V

103 +3.

3V

103

MCH

18F

N104

ZK0.

1uF

+3.3V

C

MCH

18F

N104

ZK0.

1uF

+1.8V

C

MC

H18

FN1

04ZK

0.1u

F

+3.3V

MCH18FN200ZK20p

MCH18FN200ZK20p

HC-

49/S

39.

884M

Hz

105

105

NC3

832

.768

KHz MCH18FN101ZK

100p

MCH18FN101ZK100p

- 36 -


10.5 MN101CF97D

DATA

CLOCK

nRESET

P27/NRST

DMODE

RESET

AM1 Debug Probe

(KDK)

(KDK)

MN101CF97D

(Panasonic)TQFP048-P-0707B

DMODE1

P45/SBT0B48

P44//TXD0B/SBO0B47

OSC1 7

OSC2 8

MMOD 6

P27/NRST3

VSS9

VDD332 XI 5

XO 4

SMTE3

RB501

MCH18FN104ZK0.1uF

224466881010 9 9

7 7

5 5

3 3

1 1

103

+3.3V

103 +3.3

V

R6 105

X1

HC-4

9/S3

9.88

4MHz

R10

105

X2 NC38

32.7

68KH

z

103

MCH1

8FN1

04ZK

0.1u

F

+3.3V C

MCH1

8FN1

04ZK

0.1u

F

+3.3V

MCH18FN101ZK100p

MCH18FN101ZK100p

MCH18FN200ZK20p

MCH18FN200ZK20p

10.6 MN103LEV03/LF06N/LF08K

NRST

OCD_SCL

OCD_SDA

NOCDMOD

VDD33/VDD53

VSS

RESET

CLOCK

DATA

DMODE

VDD

GND

1K

VDD33/VDD53 DWire32 Connector

RESET

CLOCK

DATA

DMODE

VDD

GND

Target Board Debug Probe

1K

1K

- 37 -


- 38 -

[11] Error Message

In this chapter, main error messages are described. Refer to the online help of DebugFactory Builder 4 regarding the other messages output from DebugFactory Builder 4. 11.1 “No Information” [80080301] This message is displayed when DebugFactory Builder 4 is not installed definitely, [Countermeasures] - Try to install . DebugFactory Builder 4 11.2 “The microcomputer product number is incorrect” [80080302] If any error occurs through checking chip ID of microcontroller on the target system while DebugFactory Builder 4 is processing "start of debugging" command (CTRL-T), this error message is displayed. [Countermeasures] - Set the correct product number in target setting. - Is the power of the target system ON? - Is the connection with target system correct? - Does microcontroller on the target system operate properly (clock, reset, etc.)? 11.3 “USB adapter cannot open” [80080303] This message is displayed when USB cable is accidently unpluged even though OS recognizes “OBJECT WinUSB Device”. [Countermeasures] - Is USB cable connected correctly? - Is power supply of USB sufficient? (approx. 500mA is need at the maximum, depending on the operating condition) - Does "OBJECT WinUSB Device" that should be installed on USB (Universal Serial Bus) of Windows device manager operate correctly? 11.4 “USB adaptor does not respond” [80080304] This message is displayed when USB cable is accidently unpluged even though OS recognizes “OBJECT WinUSB Device”. [Countermeasures] - Is USB cable connected correctly? - Is power supply of USB sufficient? (approx. 500mA is need at the maximum, depending on the operating condition) - Does "OBJECT WinUSB Device" that should be installed on USB (Universal Serial Bus) of Windows device manager operate correctly?

11.5 “Please check the power supply of a target.” [80080305] This message is displayed in the case of off whether the power supply of the target system is out of a range. [Countermeasures] - Is the power of the target system ON? 11.6 “OCD interface comunication error.” [80080306] This message is displayed in the microcontroller and the OCD communication of the target system were not possible. [Countermeasures] - Is the power of the target system ON? - Is the connection with target system correct? - Does microcontroller on the target system operate properly (clock, reset, etc.)?


- 39 -

11.7 “The load of the sub-monitor program failed” [80080307] This message is displayed in the load of the sub-monitor program failed in a target system. [Countermeasures] - Is the power of the target system ON? - Is the connection with target system correct? - Does microcontroller on the target system operate properly (clock, reset, etc.)? 11.8 “Synhronization between the monitor and USB adaptor failed” [80080308] When connecting to the target or executing RESET command or INIT command, C source code debugger (DebugFactory Builder 4) indicates the transmission negotiation between AMOT and microcontroller on the target system. If any error occurred during this process, this error message is displayed. This message also appears when the power of the target system is OFF. [Countermeasures] - Is the power of the target system ON ? - Is the connection with target system correct? - Does microcontroller on the target system operate properly (clock, reset, etc.)? 11.9 “Updating USB adaptor failed” [8008030A] If the firmware version of the supporting USB adapter is not adapted at activation, DebugFactory Builder 4 tries to update the firmware of AMOT by using current firmware update file (DPusb.frm). This error message is displayed if any error occurs during the processing. [Countermeasures] - AMOT may be broken down. Contact our support center ([email protected]) via E-Mail. 11.10 “Writing of Flash memory failed” [8008030B] AMOT writes programs into Flash ROM inside microcontroller. If any error occurs in writing into the Flash ROM during this process (load command execution), this message is displayed. This message is also displayed if microcontroller's chip ID is not adapted. [Countermeasures] - There is a possibility that the monitor program has not been correctly linked with the loaded program. Please confirm

the user program. - Flash ROM of microcontroller has limitations in writening number. Normally, several hundreds times writings are

possible. There is a possibility that the Flash ROM reaches the limit. In this case, the purchase of new microcontroller chip is required.

- If this error message is displayed despite writings are executed apparently less than several hundreds times (writing also occurs at program mode), it may break down. In this case, return AMOT to us for repair. 11.11 “The load of the monitoring failed” [8008030C] This message is displayed in the load of the monitor program failed in a target system. [Countermeasures] - Is the power of the target system ON? - Is the connection with target system correct? - Does microcontroller on the target system operate properly (clock, reset, etc.)? 11.12 “The flash memory is protected.” [8008030D] This message is displayed in the flash memory is protected, at the time of the renewal of the target system. [Countermeasures] - Please use the microcontroller which is not protected.


- 40 -

11.13“The contents of ROM and the file have a difference.” [8008030E] This message is displayed in the debugging contents are different from the ROM of the target system. (Only General-ROM Version) [Countermeasures] - Please set contents of the ROM and an equal file. 11.14 “Chip erase of Flash memory failed” [80080310] This message is displayed in flash memory couldn't be chip-erase by a target system of the keycode ajustable type. [Countermeasures] - Flash ROM of microcontroller has limitations in erasing number. Normally, several hundreds times writings are

possible. There is a possibility that the Flash ROM reaches the limit. In this case, the purchase of new microcontroller chip is required.

11.15 “The format of the key code file is an error” [80080311] This message is displayed in keycode file isn't an expected form [Countermeasures] - Please set a right key cord file. 11.16 “Key codes are different” [80080312,80080313] This message is displayed in did not match a keycode to microcontroller of the target system. [Countermeasures] - Please set a right key cord file.


- 41 -

[12] Index

A

Adjustable type ..................................................................19

B

BP......................................................................................30 Breakpoints..................................................................29, 30

C

C compiler............................................................................7 Code Window ....................................................................30 Come Command................................................................30 Compiling...........................................................................26

D

Debugger .............................................................................5 Debugger occupation resources ..................................16, 33 Debugging Information buffer size .....................................18 Debugging Information type...............................................18 Documents...........................................................................7 DWire clock........................................................................18

E

Error Message ...................................................................38 ESC ...................................................................................30

F

F10 ....................................................................................30 F7 ......................................................................................30 F8 ......................................................................................30 F9 ......................................................................................29 Fixed type ..........................................................................19 Forced break......................................................................30 Function step .....................................................................30 Function Step Execution ....................................................30

G

General ROM.....................................................................31

I

Illegal break .................................................................16, 33 Installing......................................................................... 9, 11 Interrupt ...........................................................16, 17, 33, 34 IVBM bit .......................................................................16, 33

K

Key code file ......................................................................18 Keycode.............................................................................19 Keycode File ......................................................................20 Keycode Type ....................................................................19

L

Limitation................................................................16, 18, 33 Loading the Program .........................................................27

M

Making of a project.............................................................22 MEMCTR .....................................................................16, 33 Memory mode ....................................................................18 Model .................................................................................26 Monitor program.................................................................17 Monitor program.................................................................17 Monitor program.................................................................34

N

NOTE!................................................................................17

O

OCDINT vector.............................................................31, 32 Open-drain .........................................................................33 OSC frequency ..................................................................18 Overview............................................................................. 5

P

Processor mode.................................................................18 Product type.......................................................................18

R

RAM monitor ......................................................................32 Reference Circuits..............................................................35 Reset pin............................................................................33 Reset start address ............................................................33 ROM image buffer..............................................................25 ROM monitor......................................................................32

S

Set up.................................................................................. 9 Software breakpoints .........................................................26 Special Function Registers...........................................17, 33 Stack ............................................................................17, 34 Stack pointer ..........................................................17, 18, 34 Stack pointer initialization...................................................18 Starting Debugging ............................................................27 Start-up ..............................................................................22 Start-up Display..................................................................25 Start-up Program................................................................21 Step Execution ...................................................................30 Support CPU....................................................................... 6 Support PC and OS ............................................................ 5


- 42 -

T

Target Connector .................................................................8 Target setting .....................................................................18 The addition of the microcomputer .................................... 11 The addition of the unit ...................................................... 11 Type...................................................................................18

U

Undefined instruction...................................................16, 33 Uninstall.............................................................................14 Update of the software....................................................... 11 USB drivers .......................................................................12

User program.....................................................................16

V

vector table ..................................................................17, 34

W

Watchdog...........................................................................16

X

XO frequency.....................................................................18

DDeebbuuggFFaaccttoorryy BBuuiillddeerr 44 ffoorr AAMMOOTT UUsseerrss MMaannuuaall RReevv 11..00 AApprriill 11,, 22001111

OBJECT Co., Ltd. 3rd Floor, Mori New Bldg. 1-3-1 Hotarugaike Higashimachi, Toyonaka,Osaka, 560-0032, Japan

TEL : +81 6-6844-1747 E-Mail : [email protected] URL : http://www.OBJECT.jp/