aam1 m1 ddebug ebug pprobe robe ddwirewire quick start guide · 2011-11-24 · quick start guide /...

QQuuiicckk SSttaarrtt GGuuiiddee // RReeggiissttrraattiioonn GGuuiiddee

- Microcomputer Research & Development - OBJECT Co., Ltd. http:// www.OBJECT.jp/

- 1 -

AM1 Debug Probe DWireAM1 Debug Probe DWire

QQuuiicckk SSttaarrtt GGuuiiddee



- 2 -

[1] Set up···················································································································································· 3 1.1 Installing DebugFactory Builder ································ 3 1.2 Installing USB Drivers ········································· 6 1.3 Uninstalling ··················································· 7

[2] General ROM Version ······················································································································· 8 2.1 Precautions on Debugger【Important】······························ 8 2.2 Limitation on Debugger Function ································ 8 2.3 Monitor Program Type ··········································· 8

[3] AM1 Debug Probe DWire················································································································· 9 3.1 TARGET PROBE CONNECTOR ········································· 9 3.2 USB1.1 CONNECTOR / DCIN CONNECTOR ······························ 10 3.3 LED ···························································· 10 3.4 DIP SWITCH ····················································· 11

[4] Secure Support by Key Code ·········································································································· 12 4.1 Key Code File ·················································· 12 4.2 Key Code Type ·················································· 13 4.3 Creating a key Code File ······································· 14 4.4 Key Code File Registration ····································· 14

[5] Start-up Program ······························································································································ 15 5.1 Start-up Program Specification ································· 15 5.2 File Configuration of Start-up Program ························· 15 5.3 Start.asm ······················································ 15

[6] DebugFactory Builder······················································································································· 16 6.1 DebugFactory Builder Start-up ·································· 16 6.2 Precautions in Using WindowsXP SP2 ····························· 16 6.3 DebugFactory Builder Start-up Display ·························· 17 6.4 Compiling the Start-up Program （Flash type only）················ 17 6.5 Starting Debugging and Loading the Program ····················· 18 6.6 Executing the Start-up Program ································· 19 6.7 Typical Debug Commands ········································· 20

[7] Registration Guide····························································································································· 22 7.1 Registration ··················································· 22 7.2 Technical support ·············································· 22 7.3 Technical Report Mailing List ·································· 23 7.4 User Community Mailing List ···································· 23 7.5 Compiler Upgrade ··············································· 23



- 3 -

[1] Set up

1.1 Installing DebugFactory BuilderAM1 Debug Probe DWire includes the debug integrated environment “DebugFactory Builder”. To use this product, start up the installer included in the attached CD-ROM and install the software into your PC. [Installing Procedure]

(1)Check precautions Read the text file Readme_J.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 attached installer (DFBuilderAM1DPDWE.exe) and install the software by following the dialog message. As the type selection dialog is displayed during installation, select the type you purchased. In the default setting, each software and document is installed in the “%system%\Panasonic” folder.

[[NNOOTTEE!!]] “%system%“ shows Windows system disc. In the general IBM/PC compatible i386 system,”C:” corresponds to “%system%“. [[NNOOTTEE!!]] The installer installs sample projects of all product numbers regardless of the selected product number at installlation. Project install path : %system%\Panasonic\DebugFactory\Builder3\AM1_DPDW STEP1 The following is the DFBuilderAM1DPDWE.exe setup display. Click “Next” button.



- 4 -

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

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.



- 5 -

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

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.



- 6 -

1.2 Installing USB Drivers After installing DebugFactory Builder, the Windows system asks for driver installation when connecting AM1 Debug Probe DWire to PC with the attached USB cable. Install a driver following the steps below.

[[NNOOTTEE!!]] Install DebugFactory Builder before installing a USB driver. STEP1 When AM1 Debug Probe DWire with the PC by the USB cable, the following dialog appears. Check the “Install from a list or specific location [Advanced]” and click on the “Next” button.

STEP2 As specifing the directory path of the driver file, check the “Search for the best driver in these locations (S)” and “Include this location in the serarch” box, and click on the “Browse” button to specify the following file. After completing input, click on the “Next ” button and then searching the driver will start.

%system%\Panasonic\DebugFactory\Builder3\MN101DPDW\Driver\omusbi.inf

[[NNOOTTEE!!]] %system% shows Windows systems disc. In the general IBM/PC compatible i386 system, “C:” corresponds to “%system%”



- 7 -

STEP3 Next, when the warning dialog appears, click on the “Continue Anyway” button to continue installing.

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

1.3 Uninstalling In order to uninstall the DebugFactory Builder, 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 “USB (UniversalSerialBus) controller” in the “device manager” of the hardware tab, and delete AM1 DebugProbe DPDW USB I/F.



- 8 -

[2] General ROM Version

AM1 Debug Probe DWire 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 has some limitations on its debug function compared to the Flash version. [Area security type 101xxxxA / Flash core built-in security type 101xxxxB]

Name 101CROMx 101CRAMx 101EROMx 101ERAMx

CPU core MN101C MN101C MN101E 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.

2.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. 2.2 Limitation on Debugger Function - ROM contents cannot be changed since the ROM emulation method is not used. - Load command reads debug information and 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. 2.3 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 Flashversion of AM1 Debug Probe DWire is replaced with ROM, the general ROM version of AM1 Debug Probe DWire 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 t

he 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 -

[3] AM1 Debug Probe DWire

3.1 TARGET PROBE CONNECTOR It is a 10P probe connector which connects with the target system. The following is the connection table for each type.

TARGET CONNECTOR

9 7 5 3 1

10 8 6 4 2

[Importance] The order of turning on connection and power supply (1) AM1 Debug Probe DWire is connected with PC with the USB cable. (Power ON) (2) It connects it with the target system of power supply OFF. (3) The power supply of the target system is turned on. (Power LED is changed into green -> red.) [1]TARGET PROBE CONNECTOR by CPU type

PIN/NAME RESET GND DATA VDD NC NC NC DMODE CLOCK GND

PIN No 1 2 3 4 5 6 7 8 9 10

MN101CROMx/R

AMx NRST GND OCDDATA VDD - - - DMODE OCDCLK GND

MN101CF74G NRST/P27 GND TXD0B/SBO0B/LED1

/PC1 VDD - - - DMODE SBT0B/LED2/PC2 GND

MN101CF73A NRST/P27 GND P34/VLC3 VDD - - - DMODE P35/VLC2 GND

MN101CF91D NRST/P27 GND P44/TXD1B/SBO1B VDD - - - DMODE P45/SBT1B GND

MN101CF97D NRST/P27 GND P44/TXD0B/SBO0B VDD - - - DMODE P45/SBT0B GND

MN101CF93K NRST/P27 GND TXD0B/SBO0B/LED1

/PC1

VDD - - - DMODE SBT0B/LED2/PC2 GND

MN101CF95G NRST/P27 GND SDA3/SBO3/P00 VDD - - - DMODE P02/SBT3/SCL3/

BUZZER GND

MN101CFA2D NRST/P27 GND VLC2 VDD - - - P00/KEY0 VLC1 GND

MN101CFA7D NRST/P27 GND P44/TXD1B/SBO1B VDD - - - DMODE P45/SBT1B GND

MN101EROMx/R

AMx NRST GND OCDDATA VDD - - - DMODE OCDCLK GND

MN101EF29G NRST/P27 GND TXD1A/SBO1A/TM8I

OB/LED1/P01 VDD - - - DMODE

SBT1A/TM9IOB/L

ED2/P02 GND

MN101EF30R NRST/P27 GND TXD1A/SBO1A/TM8I


SBT1A/TM9IOB/L

ED2/P02 GND

MN101EF31G NRST/P27 GND TXD1A/SBO1A/TM8I


SBT1A/TM9IOB/L

ED2/P02 GND

MN101EF34D

MN101EF35D NRST/P27 GND

TXD1/SBO1/TM8IOB

/LED1/P01 VDD - - - DMODE

SBT1/TM4IOC/LE

D2/P02 GND

* It is compatible with PanaX FW2. * The N.C pin must be open. * Please refer to LSI manual for CPU that there is no description in the table above.



- 10 -

3.2 USB1.1 CONNECTOR / DCIN CONNECTOR Do not connect to the power supply connector（DC jack）since only USB Bus power supply can be operated. The maximum power consumption is 350ｍA.

USB 1.1 TARGET CONNECTOR

+5V POWER IN

+5V GND

3.3 LED

AM1 Debug Probe

STATUS POWER

OBJECT

LED NAME COLOR SPECIFIC OFF Debugger is not connected. RED User program is running.

STATUS

GREEN User program is suspending.

OFF Power supply is OFF. RED Target power supply is on. GREEN Target power supply is off.

POWER

ORANGE Target is communicating.



- 11 -

3.4 DIP SWITCH

1 2 3 4

OFF

BIT DEFAULT Name ON(↓) OFF(↑) 4 OFF RSVSW3 Disabled Fixed to OFF 3 OFF RSVSW2 Disabled Fixed to OFF 2 OFF RSVSW1 Disabled Fixed to OFF 1 OFF RSVSW0 Disabled Fixed to OFF



- 12 -

[4] Secure Support by Key Code

AM1 Debug Probe DWire supports for security of the key code method to protect MN101C/E program of the target system from illegal read. DebugFactory Builder compares the contents of the key code file specified by MN101C/E key code and project on the target system at the beginning of start of debugging (CTRL-T) command process. When the contents differ, a dialog appears. It asks whether to erase MN101C/E Flash ROM on the target system and connect, or cancel the connection. MN101C/E Flash ROM on the target system cannot be read without a correct key code file. 4.1 Key Code File The key code file is a tect file based on ceratin format. Format: 1st line<key code count storage specification address> 2nd line<key code count> 3rd line<key code data>

Example: In the ablove example, if the data on memory of MN101C/E on the target system is the following content, the key code matches. [Key code on MN101C/E memory] Address Data 0x4000 0x07 0x4001 0x40 0x4002 0x00 0x4003 0x00 0x4004 0xC2 0x4005 0x40 0x4006 0x00 0x4007 0x00

Key code storage specification address

Key code count

Key code data

3rd line: key code data

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

2nd line：key code count

1st line：key code storage specification address



- 13 -

4.2 Key Code Type The key code file has two formats. One of them is the “adjustable key code area type” which can set any key code area and the other one is the ”fixed keycode area type” which is fixed at key code area. The type depends on MN101C/E chip type.

CPU Type Key code type Specification enable address area reference

General ROM type(*1) Adjustable 0x4000～0x4FFF MN101CF74G Adjustable 0x4000～0x4FFF MN101CF73A Adjustable 0x4000～0x4FFF MN101CF91D Adjustable 0x4000～0x43FF MN101CF97D Adjustable 0x4000～0x4FFF MN101CF93K Adjustable 0x4000～0x4FFF MN101CF95G Adjustable 0x4000～0x4FFF MN101CFA2D Adjustable 0x4000～0x43FF MN101CFA7D Adjustable 0x4000～0x43FF

MN101EF29G fixed - With built-in Flash core

MN101EF30R fixed - With built-in Flash core

MN101EF31G fixed - With built-in Flash core

*1 General ROM type：101CROMx/101CRAMx/101EROMx/101ERAMx



- 14 -

4.3 Creating a key Code File The key code file is compatible with PanaX FW2. It can be created by the DebugFactory Builder ”Tool (T)”＞”Key code file creation (K)” command from MN101C/E Flash ROM on the current target sysetm. The key code area does not affect user program execution. Key code file (text style） 1st line [Key code storage specification address] MN101C/E physical address. It specifies arbitrary address on the Flash ROM. The data value of the address-1 must be between 7 to 255 and the specification enable address range is defined by product type (see ”4.2”). The format is hexadecimal form headed with 0x. (*1) *1 The key code count uses the value of the key code storage specification address-1. The key code storage specification address can not specify the head address of the speficiation enable address range. 2nd line [Key code count] The data value of the key code storage specification address-1 is used as key code count. The value must be between 7 to 255. The format is hexadecimal form headed with 0x. 3rd line [Key code data] The data values of the key code storage specification address to the key code storage specification address + the key code count are written with ”,”. The format is a hexadecimal form headed with 0x.

3rd line: key code data

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

2nd line: key code count

1st line: key code storage specification address

[[NNOOTTEE!!]] When key code storage specification address = 0x4001, the key code count is the data value of address：0x4000. 4.4 Key Code File Registration To register the key code file created in DebugFactory Builder project, register it on property: key code file in the target (debug probe) of DebugFactory Builder.



- 15 -

[5] Start-up Program

AM1 Debug Probe DWire includes a start-up program with a monitor program as a model in order to facilitate the programming for AM1 Debug Probe DWire. The start-up program is provided as source code. You should do the make-up by trial version C compiler of the product attachment. 5.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. 5.2 File Configuration of Start-up Program Project1.dfp Start-up project file for DebugFactory Builder Main.c C source file including main() function Start.asm Monitor program source file including ROM start-up MakeProject1.mak Makefile complying with the make tool attached in DebugFactory Builder 5.3 Start.asmIt 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 AM1 Debug Probe DWire. To link to the user program, parts depending on the user program, such as a vector table should be edited as needed. 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 da A(MonInterrupt); interrupt vector（define interrupt function (MonInterrupt) Don't Change!）

(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



- 16 -

[6] DebugFactory Builder

AM1 Debug Probe DWire includes the integrated environment DebugFactory BuilderDebugFactory Builder for AM1DPDW as standard equipment. The main functions are the C source code debugger, trial version C compiler, source file editor and make tool. This integrated environment is the same as the AM1 series full ICE and simulator. 6.1 DebugFactory Builder Start-up When starting up DebugFactory Builder for the first time, the project selection screen is displayed. Chek the “New project creation” and click on the” Run” button for the Flash version. Check the ”Execution file debugging” and click on

the “Run” button for the general ROM version.

[[NNOOTTEE!!]] In “New project creation”, a project will be created based on the attached stat-up program. In ”Execution file debugging”, the dialog that asks the execution file path appears. Specify PATH where the program source written in ROM and the EX file are located to start up. 6.2 Precautions in Using WindowsXP SP2 After installing AM1 Debug Probe DWire in a PC suitable for WindowsXP ServicePack2, Windows Security Arart may appear if it is the first start up of DebugFactory BuilderDebugFactory Builder for AM1DPDW. In this case, make sure that “Name” is “AM1DPDW”, and click the “Unlock” button.



- 17 -

6.3 DebugFactory Builder Start-up Display The project of the start-up program opens at start-up. Select the target (debug probe) of the project explore window . Then, select the product type which you have purachsed from the following property window.

Select the product type which you have purchased.

6.4 Compiling the Start-up Program （Flash type only） AM1 Debug Probe DWire includes a start-up program as a model in order to facilitate the programming for AM1 Debug Probe DWire. C compiler is not attached in the AM1 Debug Probe DWire. The finished version should be separately obtained. The following is based on the assumption that C compiler is installed. STEP1 To execute the start-up program, compiling is needed because the start-up program just after installing is not compiled. To compile the program, select the “Make” menu of the DebugFactory Builder menu bar and execute “Make(M)”



- 18 -

6.5 Starting Debugging and Loading the Program After starting DebugFactory Builder and finishing make, connect AM1 Debug Probe DWire with the attached USB cable. Then, connect the target system with the probe and turn on the power supply of the target system. Next, when executing the “start of debugging” (CTRL-T) in the debug menu of DebugFactory Builder, AM1 Debug Probe DWire is recognized. It communicates with MN101C/E on the target system through interface and checks the key code. When the key code is different, the following dialog appears. STEP1 After starting DebugFactory Builder and finishing make, connect AM1 Debug Probe DWire with the attached USB cable. Then, connect the target system with the probe and turn on the power supply of the target system. Next, when executing the “start of debugging” (CTRL-T) in the debug menu of DebugFactory Builder, AM1 Debug Probe DWire is recognized. It communicates with MN101C/E on the target system through interface and checks the key code. When the key code is different, the following dialog appears.

STEP2 In the Flash type, the dialog “Key code authentication falied. Execute chip erase?” appears. It asks whether to erase MN101C/E Flash ROM on the target system and connect, or cancell the connedtion. If clicking on ”Yes(Y)”, MN101C/E Flash ROM on the target system will be erased. If clicking on ”No（N）”, the start of debugging will be halted. After clicking on ”Yes(Y)” and erasing ROM, the following dialog appears. In the general ROM type, this dialog does not appear. When the key code differs, the message “Key code does not match” appears and the start of debugging is halted.

“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 MN101C/E chip on the target system. In the general ROM type, writing into the target is not executed, and debug information is read.

[[NNOOTTEE!!]] When the correct key code is specified and MN101C/E on the target system is chip-erased., the above dialog does not appear.

[[NNOOTTEE!!]] In AM1 Debug Probe DWire, program loading is to write a program in MN101C/E chip built-in Flash ROM on the target system.



- 19 -

6.6 Executing the Start-up Program The start-up program attatched to AM1 Debug Probe DWire is executed by Debug menu>Execution(G). The forced break by the ESC key allows to halt the execution.

[[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.



- 20 -

6.7 Typical Debug Commands 6.7.1 Forced Break (ESC) If pressing the ESC key during user program execution, the user program is halted (break). 6.7.2 Breakpoints (F9) Up to 2 pre-execution breakpoints can be set. There are several methods to set breakpoints in DebugFactory Builder. The most heavily-used one is to left-click the line marked with ”-” at the left frame area of the source display window. Breakpoints can be set/released by pressing the F9 key at any carsor position on the source window.

Setting/releasing breakpoints by F9

Setting/releasing breakpoints by clicking

6.7.3 One instruction step execution （F8） One instruction step execution (F8) is the operation that break condition is generated again after executig only one instruction of CPU. When one instruction step execution (F8 key) is executed again, it proceeds to the next instruction. 6.7.4 Function step execution (F10） Function step execution (F10) is the step execution command. 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). 6.7.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), 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.



- 21 -

AM1 Debug Probe DWireAM1 Debug Probe DWire

UUsseerr RReeggiissttrraattiioonn GGuuiiddee



- 22 -

[7] Registration Guide

Thank you for purchasing AM1 Debug Probe DWire (this “Product”). OBJECT offers a variety of support to upgrade and maintain the performance of this “Product”. To receive support, you are required to complete your user registration. In this user registration guide, you can learn how to register and what type of support is available.

7.1 Registration - Visit the following our website and choose “English”, and click "Registration" on the right corner of the page.

http://www.OBJECT.jp/ - Complete the required fields (product name, serial number, user information) and enter the optional fields

(questionnaire about product). If the required fields are not completed, you cannot finish the user registration.

- Product serial number is mentioned on the backside of the body case (11-digit number). - User information means general information such as your name, company name, etc.

- Choose whether to join the mailing list of our technical report community. “I Join” is selected in the default setting. If you would not like to join the mailing list, select “I do NOT Join”.

- Registration process takes few minutes. When the registration has been completed, you will be notified via e-mail.

- After the user registration is completed, you can request technical supports. If you select to join the technical report community, the technical report information is distributed (Past reports are not distributed. If you would like to get the past information, please see “Support” page of our website.

7.2 Technical support - Please request technical support by e-mail.

- To request technical support, visit “Support” page of our website and click [email protected] inquiry sheet starts up. The URL is as follows:

http://www.object.jp/support/tec-sup.html

- Complete the inquiry sheet and send. If your user registration has not completed, the message “please complete user registration and send your inquiry again” is sent to you.

- After your user authentication is confirmed, you will be notified within 24 hours via e-mail that your inquiry has been received.

- We will respond to your inquiry as quickly as possible. Please note that it takes time depending on the type of inquiry.

- The contents of your inquiry will be opened on the FAQ of our website and in some cases are posted on the technical support mailing list. If you do not want your inquiry listed as a FAQ please mention this in your e-mail inquiry.

http://www.object.jp/

mailto:[email protected]

http://www.object.jp/support/tec-sup.html



- 23 -

7.3 Technical Report Mailing List - We offer timely e-mail messages that keep you up-to-date with technical information for products (product news,

technical report updates, application notes, bug information, etc.).

- To join this mailing list, you need to complete your user registration.

- Distribution of information starts immediately after your user registration is completed.

- Whether to join the mailing list is determined at user registration. When modifying your choice, list the registered product name, product serial number, and changes, and then send e-mail to the following address:

Mail address : [email protected]

Subject : Change of Technical Report Community Registration

7.4 User Community Mailing List - We offer our User community mailing list, which is different type from the technical report community mailing list.

- Anyone may participate in this group. Please join us and exchange information.

- For more information, please see the “Support” page of our website.

7.5 Compiler Upgrade - After the user registration is completed, you are authorized to request one-time upgrade option of the attach

ed C compiler, which supports MN101C/MN101D/MN101E manufactured by Panasonic, to the latest version. You can request this option indefinitely.

- You can upgrade C compiler by downloading from the below URL after user authentication. This page is accessed from “Support” page of our website.

http://www.object.jp/support/dp_user_regist.html - To get an upgrade needs software license agreement. Only those who accepted the software license agree

ment can advance the step for the upgrade after getting user authentication.

- Software serial and registry key needed for the user authentication are mentioned on the backside of the product warranty.

- After the user authentication is completed, download page is opened to you.

mailto:[email protected]?subject=%E3%83%86%E3%82%AF%E3%83%8B%E3%82%AB%E3%83%AB%E3%83%AC%E3%83%9D%E3%83%BC%E3%83%88%E3%82%B3%E3%83%9F%E3%83%A5%E3%83%8B%E3%83%86%E3%82%A3%E7%99%BB%E9%8C%B2%E5%A4%89%E6%9B%B4

http://www.object.jp/support/%EF%BD%84%EF%BD%90_user_regist.html



- 24 -

PanaXSeries and DebugFactory Builder are trademarks of Matsushita Electric Industrial Co., Ltd.

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 Matsushita Electric Industrial Co., Ltd. Semiconductor Company be liable to you for any indirect damages caused by using this Product.

(6) Compiler is for the programming evaluation with hardware. If compiler is used for product development, we can not guarantee the performance, and also can not give you technical support. But an after-purchase upgrade is available for only once from our Web SITE. Refer to “7.5 Compiler Upgrade” of Quick Start Guide for the way to upgrade.

(7) In the event that you find a defect of this Product and advise OBJECT of it within one(1) year fromthe 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 Matsushita Electric Industrial Co., Ltd. Semiconductor Company shall not be liable to you for defect warranty.

(8) We can supply the support for AM1 Debug Probe DWire for DWire via E-Mail ([email protected]) and WEB SITE (www.OBJECT.jp)) Please determine the up- to-date information and more on our WEB SITE.

AAMM11 DDeebbuugg PPrroobbee DDWWiirree QQuuiicckk--SSttaarrtt GGuuiiddee RReevv 33..66 RReevviissiioonn oonn NNoovv 2266,, 22000066

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] : http://www.OBJECT.jp/

mailto:[email protected]?subject=%5bAM1DPDW%20SUPPORT%5d


mailto:[email protected]


aam1 m1 ddebug ebug pprobe robe ddwirewire quick start guide · 2011-11-24 · quick start guide /...

Documents