Home

bdiNDI_UserManual_CPU32_32+

1. m BDI2000 Firmware Logic Current 1 03 111 1 00 Loader Firmware Logic Newest Current 111 1 00 nl gt TCP IP Configuration IP Address Subnet Mask Default Gateway Cancel Ok 151 120 25 102 255 255 255 255 255 255 255 255 Transmit Connecting to BDI2000 Loader passed dialog box BD 2000 Update Setup The following options allow you to check or update the BDI firmware and logic and to set the network parameters Channel Select the communication port where the BDI2000 is connected during this setup session Baudrate Select the baudrate used to communicate with the BDI2000 loader during this setup session Copyright 1992 2005 by ABATRON AG V 1 00 d La BDM interface for Nucleus Debugger BD 2000 CPU3Z 32 User Manual 14 Connect Current Update IP Address Subnet Mask Default Gateway Transmit Click on this button to establish a connection with the BDI2000 loader Once connected the BDI2000 remains in loader mode until it is restarted or this dialog box is closed Press this button to read back the current loaded BDI2000 software and logic versions The current loader firmware and logic version will be dis played This button is only active if there is a newer firmware or logic version present in the execution directory of the BDI setup software Press this button to write the new firmware and or logic into the BDI2000 flash
2. is able to deliver a current up to 1A 5V For pin description and layout see chapter 2 1 Connecting the BDI2000 to Target Insert the enclosed Jumper as shown in figure below Please ensure that the jumper is inserted correctly A For error free operation the power supply to the BDI2000 must be between 4 75V and 5 25V DC The maximal tolerable supply voltage is 5 25 VDC Any higher voltage or a wrong polarity might destroy the electronics CEE BDI OPTION Connector BDI TRGT BDI MAIN BDI OPTION 13 14 2 ef Jumper The green LEDs BDI and TRGT marked light up when target is powered up and the jumper is inserted correctly 13 Vcc Target 5V 14 Vcc BDI2000 5V POWER 3 i Connector 1 Vcc BDI2000 5V S 2 Vcc Target 5V 4 Jumper POWER BDI TRGT The green LEDs BDI and TRGT marked light up when target is powered up and the jumper is inserted correctly Copyright 1992 2005 by ABATRON AG V 1 00 d La BDM interface for Nucleus Debugger BD 2000 CPU3Z 32 User Manual 9 2 3 Status LED MODE The built in LED indicates the following BDI states Rev B C MODE LED BDI STATES The BDI is ready for use the firmware is already loaded The power supply for the BDI2000 is lt 4 75VDC The BDI loader mode is active an invalid firmware is loaded or loading firmware is ac
3. For example enter 16 if you are using two AM29F010 to build a 16bit flash memory bank workspace If a workspace is defined the BDI uses a faster programming algorithm that run out of RAM on the target system Otherwise the algorithm is processed within the BDI The workspace is used for a 1kByte data buffer and to store the algorithm code There must be at least 2kBytes of RAM available for this purpose Copyright 1992 2005 by ABATRON AG V 1 00 d La BDM interface for Nucleus Debugger BD 2000 CPU3Z 32 User Manual 23 5 1 2 Flash Erase This command allows to erase one flash sector Syntax flash erase addr 0x02800000 addr The start address of the flash sector to erase 5 1 3 Flash Load This command enables loading to flash memory If the address of a data block is within the given flash range the BDI automatically uses the appropriate programming algorithm This command must be executed before downloading is started Syntax flash load addr 0x02800000 size 0x200000 addr The start address of the flash memory size The size of the flash memory 5 1 4 Flash Idle This command disables loading to flash memory Syntax flash idle Copyright 1992 2005 by ABATRON AG V 1 00 d La BDM interface for Nucleus Debugger BDIZ000 CPU32 32 User Manual 24 5 2 Download to Flash Memory The BDI supports programming flash memory To automate the process of downloading to flash memory a codelet can be used
4. e Copy the entire contents of the enclosed diskette into a directory on the hard disk e You may create a new shortcut to the b20c32 exe configuration program Copyright 1992 2005 by ABATRON AG V 1 00 User Manual 13 ldi 2 6 Configuration BDM interface for Nucleus Debugger BDIZ000 CPU32 32 Before you can use the BDI together with the debugger the BDI must be configured Use the SETUP menu and follow the steps listed below e Load or update the firmware logic store IP address gt Firmware e Set the communication parameters between Host and BDI gt Communication gt nitiist gt Mode gt Mode Transmit e Setup an initialization list for the target processor e Select the working mode e Transmit the configuration to the BDI For information about the dialogs and menus use the help system F1 2 6 1 BDI2000 Setup Update First make sure that the BDI is properly connected see Chapter 2 1 to 2 4 The BDI must be con nected via RS232 to the Windows host To avoid data line conflicts the BDI2000 must be disconnected from the target system while programming the logic for an other target CPU see Chapter 2 1 1 The following dialogbox is used to check or update the BDI firmware and logic and to set the network parameters BD12000 Update Setup Connect BDI2000 Loader Channel Baudrate 9600 Cam C 38400 57600 SN 91084317 C COMI COM2 C COM3 C COM4
5. e g 28F800C3 28F160C3 28F320C3 power up with all blocks in locked state In order to erase program those flash chips use the init list to unlock the appropriate blocks WM16 OxFFF00000 0x0060 unlock block 0 WM16 OxFFF00000 0x00D0 WM1 6 OxFFF10000 0x0060 unlock block 1 WM1 6 OxFFF10000 0x00D0 WM1 6 OXxFFF00000 OxFFFF select read mod Not all flash chips support a chip erase command Also if a chip erase takes too long the BDI com munication layer may time out In this case use multiple sector erase commands Copyright 1992 2005 by ABATRON AG V 1 00 d La BDM interface for Nucleus Debugger BD 2000 CPU3Z 32 User Manual 26 6 Specifications Operating Voltage Limiting Power Supply Current RS232 Interface Baud Rates Data Bits Parity Bits Stop Bits Network Interface Serial Transfer Rate between BDI and Target Supported target voltage Operating Temperature Storage Temperature Relative Humidity noncondensing Size Weight without cables Host Cable length RS232 5 VDC 0 25 V typ 500 mA max 1000 mA 9 600 19 200 38 400 57 600 115 200 8 none 1 10 BASE T up to 16 Mbit s 1 8 5 0 V 3 0 5 0 V with Rev A B 5 60 C 20 C 65 C lt 90 rF 190 x 110 x 35 mm 420 g 2 5 m Specifications subject to change without notice Copyright 1992 2005 by ABATRON AG V 1 00 d La BDM interface for Nucleus Debugger BD 2000 CPU3Z 32 User M
6. via the BDI OPTION connector Rev A or via POWER connector Rev B C The available power supply from Abatron option or the enclosed power cable can be directly connected In order to ensure reliable operation of the BDI2000 keep the power supply cable as short as possible A For error free operation the power supply to the BDI2000 must be between 4 75V and 5 25V DC The maximal tolerable supply voltage is 5 25 VDC Any higher voltage or a wrong polarity might destroy the electronics Re A BDI OPTION Connector 2 GROUND BDI OPTION 1 4 GROUND eee 6 GROUND 2 Vec GND 8 GROUND 10 GROUND The green LED BDI marked light up when 5V power is connected to the BDI2000 12 Vcc 5V 14 Vcc 5V Rev B C POWER Connector 1 Vcc 1 Vcc 5V 3 GROUND The green LED BDI marked light up when 5V power is connected to the BDI2000 Please switch on the system in the following sequence e 1 gt external power supply e 2 gt target system Copyright 1992 2005 by ABATRON AG V 1 00 d La BDM interface for Nucleus Debugger BDIZ000 CPU32 32 User Manual 8 2 2 2 Power Supply from Target System The BDI2000 needs to be supplied with 5 Volts max 1A via BDI MAIN target connector Rev A or via TARGET A connector Rev B C This mode can only be used when the target system runs with 5V and the pin Vcc Target
7. MODE blinks fast q o E INIT MODE We al o N e Turn the power supply OFF again Le DEFAULT e Return the jumper to the DEFAULT position e Reassemble the unit as described in Appendix Maintenance Copyright 1992 2005 by ABATRON AG V 1 00 ldi BDM interface for Nucleus Debugger BDIZ000 CPU32 32 User Manual 15 3 Init List Startup Init List Address 0003FF00 07000133 00000005 OOOO00FF 00000004 OO004CFF DOE 2F3 O00003E 8 00008000 0000008F 00000080 np annt AN 07001009 07001022 07001000 07001010 07001014 0700100 07001016 DZ 040 New Value Comment Set CPU space to access MBAR smn MBAR dual port RAM internal registers at 0 07 000000 Set supervisor data space RSR Clear reset status register SYPCR disable watchdog enable bus monitor 1k clocks MCR FR2Z1 BCLR 3 SUPY BCLRl 7 IARB 15 PLLCR enable PLL lock access div128 multiplication 761 Delay after changing PLL frequency CDVCR lock access CLKOCR disable CLKO2 disable CLKO1 lock access PEPAR WE3 WEO DE CASO CAS3 CS7 AVEC CAD rafrmols Dhawan Tha me COL ansan MLO ARAM SE En Paste Delete Cancel dialog box Startup Init List In order to prepare the target for debugging you can define an Initialization List This list is stored in the Flash memory of the BDI2000 and worked
8. application code with the BGND instruction All the time the application is halted i e caused by a breakpoint the target processor remains freezed Single step is implemented by starting the target processor and immediately activating the BKPT line So the target processor will be frozen after executing exactly one instruction All interrupts are dis abled during the execution of this single instruction The status register SR is restored to the correct value after single stepping an instruction The BDI takes care of instructions that changes the SR e g RTE MOVE to SR ANDI to SR or writes the SR value to memory register e g MOVE from SR TRAP Note when using SIM60 breakpoint logic If the SIM60 breakpoint hardware is enabled and also use no target resources is checked only hardware breakpoints will be used There is no code replacement and therefore the code may be stored in read only memory Only one breakpoint can be active at the same time 4 2 2 Breakpoint Mode LOOP In this mode breakpoints are implemented by replacing application code with a TRAP 15 instruction A stopped application loops within an exception procedure The target processor is freezed only for short time periods max 70us The priority level used when looping in the exception procedure can be defined using the option Loop Level If you want to stop the hole application use Loop Level 7 If only the current task should be stopped use Loo
9. mem ory programmable logic Enter the IP address for the BDI2000 Use the following format xxx xxx xxx xxxe g 151 120 25 101 Ask your network administrator for assigning an IP address to this BDI2000 Every BDI2000 in your network needs a different IP address Enter the subnet mask of the network where the BDI is connected to Use the following format xxx xxx xxx xxxe g 255 255 255 0 A subnet mask of 255 255 255 255 disables the gateway feature Ask your network administrator for the correct subnet mask Enter the IP address of the default gateway Ask your network administra tor for the correct gateway IP address If the gateway feature is disabled you may enter 255 255 255 255 or any other value Click on this button to store the network configuration in the BDI2000 flash memory In rare instances you may not be able to load the firmware in spite of a correctly connected BDI error of the previous firmware in the flash memory Before carrying out the following procedure check the possibilities in Appendix Troubleshooting In case you do not have any success with the tips there do the following e Switch OFF the power supply for the BDI and open the unit as described in Appendix Maintenance e Place the jumper in the INIT MODE position e Connect the power cable or target cable if the BDI is powered from target system Vv e Switch ON the power supply for the BDI again and wait until the LED
10. through every time the target comes out of reset Use it to get the target operational after a reset The memory system is usually initialized through this list After processing the init list the RAM used to download the application must be accessible Use on line help F1 and the supplied configuration examples on the distribution disk to get more information about the init list Copyright 1992 2005 by ABATRON AG V 1 00 d La BDM interface for Nucleus Debugger BD 2000 CPU32 32 User Manual 16 4 BDI working modes BDI working mode Identification CPU360 2MB SRAM freezed Startup p Breakpoint Workspace 00000400 Hex Reset GG Freezec e E Vector base 00000000 Hex Stop Lies C Run R Terminal data 00000000 Hex use no target resources D Loop Level Current Clock Rate 25000000 Hz Run Time F DO ms Watch Points CRU Type E SIM6O Breakpoint Logie cpu __Transmit_ RegBase 07001000 CPU32 dialog box BDI Working Mode With this dialog box you can define how the BDI interacts with the target system Identification Startup Breakpoint CPU Type CPU Clock Rate Workspace Vector base Terminal Data Enter a text to identify this setup This text can be read by the debugger with the appropriate Command Startup mode defines how the BDI interacts with the target processor after reset or power up The options RESET STOP or RUN can be selected Breakpoint m
11. 00 The BDI2000 is a processor system in a small box It implements the interface between the JTAG pins of the target CPU and a 10Base T Ethernet RS232 connector The firmware and the program mable logic of the BDI2000 can be updated by the user with a simple Windows based configuration program The BDI2000 supports 1 8 5 0 Volts target systems 3 0 5 0 Volts target systems with Rev B Copyright 1992 2005 by ABATRON AG V 1 00 d La BDM interface for Nucleus Debugger BDIZ000 CPU32 32 User Manual 4 2 Installation 2 1 Connecting the BDI2000 to Target The cable to the target system is a ten pin flat ribbon cable In case where the target system has an appropriate connector the cable can be directly connected The pin assignment is in accordance with the Motorola specification In order to ensure reliable operation of the BDI EMC runtimes etc the target cable length must not exceed 20 cm 8 Target System f Target Connector BERR GROUND BKPT DSCLK GROUND FREEZE RESET DSDI Vcc Target IPIPE DSO BDI2000 JO O1 B ND The green LED TRGT marked light up when target is powered up Target System 1 CPU 32 A gt HEEE ue 2 f Target Connector BERR GROUND BKPT DSCLK GROUND FREEZE RESET DSDI Vcc Target IPIPE DSO es sp x
12. BDM interface for Nucleus Debugger CPU32 32 User Manual Manual Version 1 00 for BDI2000 AAR N 1992 2005 ABATRON AG d La BDM interface for Nucleus Debugger BD 2000 CPU3Z 32 User Manual 2 UI Tu E 3 Hod Pe ADO a a de ne 3 AT EEN E 4 2 1 Connecting the BDI2000 to Target ard ase Sn 4 2 1 1 Changing Target Processor Type s vnicisccivecismctzvancobncneeinctence Wi eeetesenedsdernentavrecttinedunnets 6 2 2 Connecting the BDI2000 to Power Supply ss 7 2 2 1 External Power Supply EE 7 2 2 2 Power Supply from Target System issues 8 2 3 Status LED MODE tea a ee cam 9 2 4 Connecting the BD12000 to Most seziandiasdenaeiuctinadaxtonrteeas ended EAR ENEE E 10 2 4 1 Serial line GIERENS 10 2 4 2 Ethernet communication ee eege Ee EE EE 11 25 Installation of the Configuration Software iiss cccecsssscntevedensetansdcbieusesioceetisvesiceustleaeserctecieia 12 2 6 Configuration 252 nee D dt ni ee 13 2 6 1 BDI2000 S tip Ubaldi 13 ge INC IST nn dace ck otic nie Reese nie een 15 4 BDI WotkKIng MOURS 5 080 SEENEN dee 16 4 1 E re ET 17 4 1 1 Startup mode RE 17 4 1 2 Startup Mode S TOP nissan seed tale RA EN NE 18 4 1 3 Startup mode PONS ae ed tee 18 4 2 Breakpoint e ET 19 421 Breakp int M d FREEZED israse es ie enced 19 4 2 2 Breakpoint Mode LEE de seseesgbaguebegervergesdgege b ie e ug cactdeninteediasedeweceasieteeseuinndans 19 EE 21 GW ET 22 5 1 Dir et Commands ss ananas nie ani ans te
13. Following an example of such a codelet void flash_load int coreld char output 256 printf Specifying the flash type command bdi flash setup type AM29F size 0x00800000 bus 8 output 256 printf s n output printf Erasing the first sector command bdi flash erase addr 0xfff00000 mode sector output 256 printf s n output printf Erasing the second sector command bdi flash erase addr 0xfff10000 mode sector output 256 printf s n output printf Erasing the third sector command bdi flash erase addr 0xfff20000 mode sector output 256 printf s n output printf Setting load address command bdi flash load addr 0xfff00000 size 0x00020000 output 256 printf s n output printf Loading the image command load C MGC embedded Nucleus demo out plus_demo out output 256 printf s n output printf Taking the BDI out of Flashing mode command bdi flash idle output 256 printf amp s n output A user who needs to reflash often can just call such a codelet from the Nucleus Debugger command view by typing flash_load 1 at the command prompt For this to work two steps are required 1 The codelet file must first be loaded into EGDE e From the Run Menu select Codelet Composer e On the Codelet Composer dialog click the Load button e Browse to and select your cdl file e T
14. Rev A B This input to the BDI2000 is used to detect if the target is powered up If there is a current limiting resistor between this pin and the target Vdd it should be 100 Ohm or less INSTRUCTION PIPE For normal modes output signal from the MCU Indicates instruction pipeline activity DATA SERIAL OUT For background debug mode serial data output from the MCU All the pins except pin 1need to be connected to the target system for the debug operation Copyright 1992 2005 by ABATRON AG V 1 00 d La BDM interface for Nucleus Debugger BD 2000 CPU3Z 32 User Manual 6 2 1 1 Changing Target Processor Type Before you can use the BDI2000 with an other target processor type e g CPU32 lt gt PPC a new setup has to be done see Appendix A During this process the target cable must be disconnected from the target system The BDI2000 needs to be supplied with 5 Volts via the BDI OPTION connec tor Rev A or via the POWER connector Rev B C For more information see chapter 2 2 1 External Power Supply To avoid data line conflicts the BDI2000 must be disconnected from the target system while programming the logic for an other target CPU Copyright 1992 2005 by ABATRON AG V 1 00 d La BDM interface for Nucleus Debugger BDIZ000 CPU32 32 User Manual 7 2 2 Connecting the BDI2000 to Power Supply 2 2 1 External Power Supply The BDI2000 needs to be supplied with 5 Volts max 1A
15. System e RD Rev B C PC Host Do The following explains the meanings of the built in LED lights TX RX 10 BASE T U TX RX 10 BASE T BDI2000 Ethernet 10 BASE T L LED Name Description LI Link When this LED light is ON data link is successful between the UTP port of the BDI2000 and the hub to which it is connected TX Transmit When this LED light BLINKS data is being transmitted through the UTP port of the BDI2000 RX Receive When this LED light BLINKS data is being received through the UTP port of the BDI2000 Copyright 1992 2005 by ABATRON AG V 1 00 ldi BDM interface for Nucleus Debugger BD 2000 CPU3Z 32 User Manual 12 2 5 Installation of the Configuration Software On the enclosed diskette you will find the BDI configuration software and the firmware required for the BDI Copy all these files to a directory on your hard disk The following files are on the diskette b20c32 exe b20c32 hlp b20c32 cnt b20c32fw xxx c32jed20 xxx c32jed21 xxx bdiifc32 dil bdi Configuration program Helpfile for the configuration program Help contents file Firmware for BDI2000 for CPU32 targets JEDEC file for the BDI2000 Rev A B logic device programming JEDEC file for the BDI2000 Rev A B logic device programming BDI Interface DLL for configuration program Configuration Examples Example of an installation process
16. TARGET A 1 JO O1 B ND i The green LED TRGT marked light up when target is powered up For BDI MAIN TARGET A connector signals see table on next page Copyright 1992 2005 by ABATRON AG V 1 00 d La BDM interface for Nucleus Debugger BD 2000 CPU3Z 32 User Manual 5 BDI MAIN TARGET A Connector Signals Describtion Not used BUS ERROR Active low input to the MCU Signals an invalid bus operation attempt GROUND SYSTEM GROUND BKPT DSCLK BREAKPOINT For normal modes active low input to the MCU Signals a hardware breakpoint DEVELOPMENT SERIAL CLOCK For background debug mode serial input clock signal to the MCU FREEZE Active high output from the MCU Indicates that the MCU has acknowledged a breakpoint and that it has entered background debug mode RESET Active low open drain signal to start a system reset INSTRUCTION FETCH For normal modes output signal from the MCU Indicates instruction pipeline activity DATA SERIAL IN For background debug mode serial data input signal to the MCU Vcc Target 1 8 5 0V This is the target reference voltage It indicates that the target has power and it is also used to create the logic level reference for the input comparators It also controls the output logic levels to the target It is normally fed from Vdd I O on the target board 3 0 5 0V with
17. and the result is displayed in the Nucleus Debugger Command Line Window Direct Commands are ASCII Strings with the following structure lt Object gt lt Action gt lt ParName gt lt ParValue gt Example flash erase addr 0x02800000 All names are case insensitive Parameter values are numbers or strings Numeric parameters can be entered as decimal e g 700 or as hexadecimal 0x80000 values If the commands are directly entered in the Nucleus Debugger Command Line Window use the fol lowing syntax bdi direct command Example bdi flash erase addr 0x02800000 5 1 1 Flash Setup In order to support loading into flash memory the BDI needs some information about the used flash devices Before any other flash related command can be used this direct command must be execut ed Syntax flash setup type am29f size 0x80000 bus 32 workspace 0x1000 type This parameter defines the type of flash used It is used to select the correct program ming algorithm The following flash types are supported see also appendix C AM29F AM29BX8 AM29BX16 128BX8 I28BX16 size The size of one flash chip in bytes e g AM29F010 0x20000 This value is used to calculate the starting address of the current flash memory bank bus The width of the memory bus that leads to the flash chips Do not enter the width of the flash chip itself The parameter TYPE carries the information about the number of data lines connected to one flash chip
18. anual 27 7 Environmental notice A J Ce Disposal of the equipment must be carried out at a designated disposal site 8 Declaration of Conformity CE CE DECLARATION OF CONFORMITY This declaration is valid for following product Type of device BDM JTAG Interface Product name BDI2000 The signing authorities state that the above mentioned equipment meets the requirements for emission and immunity according to EMC Directive 89 336 EEC The evaluation procedure of conformity was assured according to the following standards EN 50081 2 EN 50082 2 This declaration of conformity is based on the test report no QNL E853 05 8 a of QUINEL Zug accredited according to EN 45001 Manufacturer ABATRON AG St ckenstrasse 4 CH 6221 Rickenbach Authority 4 ay MMC CE Max Vock Ruedi Dummermuth Marketing Director Technical Director Rickenbach May 30 1998 Copyright 1992 2005 by ABATRON AG V 1 00 d La BDM interface for Nucleus Debugger BDIZ000 CPU32 32 User Manual 28 9 Warranty ABATRON Switzerland warrants the physical diskette cable BDI2000 and physical documentation to be free of defects in materials and workmanship for a period of 24 months following the date of purchase when used under normal conditions In the event of notification within the warranty period of defects in material or workmanship ABATRON will replace defective diskette cable BDI2000 or documentation T
19. ation program enters an endless loop until it is interrupted by the BDI This mode is intended for special requirements on the reset sequence or if for example separate hardware needs to be initialized immediately In this mode the following steps are executed by the BDI after system reset or power up e RESET and BKPT are activated on the target system e RESET is deactivated and the target system changes to background debug mode If the target system does not change to background debug mode the BDI waits for a short time and then activates the BERR line e Register DFC and SFC are set to supervisor data space e The target CPU is started the target starts at the address fetched when reading the start vec tor at address 0 e The target system is working through the application code e After the programmed run time BKPT is activated and the target system changes to back ground debug mode If the target system does not change to background debug mode the BDI waits for a short time and then activates the BERR line e The BDI works through the initialization list and writes the corresponding addresses e Depending on the break mode the necessary vectors are set and support code is written into the RAM on the target system 4 1 3 Startup mode RUN This mode is used to debug applications which are already stored in ROM The application is started normally and is stopped by the BDI as soon as the debugger connects to the BDI In
20. he remedy for breach of this warranty shall be limited to replacement and shall not encompass any other damages includ ing but not limited loss of profit special incidental consequential or other similar claims ABATRON Switzerland specifically disclaims all other warranties expressed or implied including but not limited to implied warranties of merchantability and fitness for particular purposes with respect to defects in the diskette cable BDI2000 and documentation and the program license granted here in including without limitation the operation of the program with respect to any particular application use or purposes In no event shall ABATRON be liable for any loss of profit or any other commercial damage including but not limited to special incidental consequential or other damages Failure in handling which leads to defects are not covered under this warranty The warranty is void under any self made repair operation except exchanging the fuse Copyright 1992 2005 by ABATRON AG V 1 00 d La BDM interface for Nucleus Debugger BD 2000 CPU3Z 32 User Manual 29 Appendices A Troubleshooting Problem The firmware can not be loaded Possible reasons e The BDI is not correctly connected with the target system see chapter 2 e The power supply of the target system is switched off or not in operating range 4 75 VDC 5 25 VDC gt MODE LED is OFF or RED e The built in fuse is damaged gt MODE LED
21. ing is as shown in the figure below casing NS elastic sealing back panel nr front panel 5 3 Mount the screws do not overtighten it 5 4 Mount the two plastic caps that cover the screws 5 5 Plug the cables A ks Observe precautions for handling Electrostatic sensitive device Unplug the cables before opening the cover Use exact fuse replacement Microfuse MSF 1 6 AF Copyright 1992 2005 by ABATRON AG V 1 00 d La BDM interface for Nucleus Debugger BD 2000 CPU3Z 32 User Manual 32 C Trademarks All trademarks are property of their respective holders Copyright 1992 2005 by ABATRON AG V 1 00
22. is OFF e The BDI is not correctly connected with the Host see chapter 2 e A wrong communication port Com 1 Com 4 is selected Problem No working with the target system loading firmware is ok Possible reasons e Wrong pin assignment BDM JTAG connector of the target system see chapter 2 e Target system initialization is not correctly gt enter an appropriate target initialization list e An incorrect IP address was entered BDI2000 configuration BDM JTAG signals from the target system are not correctly short circuit break e The target system is damaged Problem Network processes do not function loading the firmware was successful Possible reasons e The BDI2000 is not connected or not correctly connected to the network LAN cable or media converter e An incorrect IP address was entered BDI2000 configuration Copyright 1992 2005 by ABATRON AG V 1 00 d La BDM interface for Nucleus Debugger BDIZ000 CPU32 32 User Manual 30 B Maintenance The BDI needs no special maintenance Clean the housing with a mild detergent only Solvents such as gasoline may damage it If the BDI is connected correctly and it is still not responding then the built in fuse might be damaged in cases where the device was used with wrong supply voltage or wrong polarity To exchange the fuse or to perform special initialization please proceed according to the following steps A ks Observe precautions for ha
23. ndling Electrostatic sensitive device Unplug the cables before opening the cover Use exact fuse replacement Microfuse MSF 1 6 AF 1 1 Unplug the cables Swiss Made BDI2000 AG 2 1 Remove the two plastic caps that cover the screws on target front side e g with a small knife 2 2 Remove the two screws that hold the front panel BDI OPTION BDI MAIN BDI TRGT MODE 3 1 While holding the casing remove the front panel and the red elastig sealing casing NS elastic sealing front panel Copyright 1992 2005 by ABATRON AG V 1 00 d La BDM interface for Nucleus Debugger BD 2000 CPU32 32 User Manual 4 1 While holding the casing slide carefully the print in position as shown in figure below m Jumper settings o We e E S DEFAULT INIT MODE Fuse Position Fuse Position Rev B C Rev A E X Pull out carefully the fuse and replace it Type Microfuse MSF 1 6AF Manufacturer Schurter Reinstallation 5 1 Slide back carefully the print Check that the LEDs align with the holes in the back panel 5 2 Push carefully the front panel and the red elastig sealing on the casing Check that the LEDs align with the holes in the front panel and that the position of the seal
24. nu 22 5 11 PASS SUR E 22 En BE 23 23 Flash Lodd E 23 WE Ea o e E E de rte ec 23 5 2 Download to Flash Memory ESS Lt 24 EC E a T A eee ere 26 1 Envir nmental NOCE TT 27 8 Declaration of Conformity GE setietegegseesgreseegeueekagEeeesdc eege genee de 27 CRT E 28 Appendices A Troubleshooting sess sicssss sine esencecet iasa eena scence te EEGENEN in een naiai auian 29 G il ire AAKE aa aiaa iaaa 30 ER E E 32 Copyright 1992 2005 by ABATRON AG V 1 00 d La BDM interface for Nucleus Debugger BD 2000 CPU3Z 32 User Manual 3 1 Introduction Target System Target System CPU32 BDM Interface PC Host RS232 Ethernet 10 BASE T L The BDI2000 adds Background Debug Mode features to the Nucleus debugger environment from Mentor Graphic s With the BDI2000 you control and monitor the microcontroller solely through the stable on chip debugging services You won t waste time and target resources with a software ROM monitor and you eliminate the cabling problems typical of ICE s This combination runs even when the target system crashes and allows developers to continue investigating the cause of the crash A RS232 interface with a maximum of 115 kBaud and a 10Base T Ethernet interface is available for the host interface The configuration software is used to update the firmware and to configure the BDI2000 so it works with the Nucleus debugger 1 1 BDI20
25. o complete the operation click the Open button Alternatively any cdl file that is simply imported into one of the user s projects will be identified by Nucleus Debugger 2 Since the flashing commands are issued over the debug connection this of course requires that a connection to already been established to the target In addition the contents of the codelet can be placed in the user s initialization codelet and thus be called automatically after connect Copyright 1992 2005 by ABATRON AG V 1 00 d La BDM interface for Nucleus Debugger BD 2000 CPU3Z 32 User Manual 25 Supported Flash Memories There are currently 2 standard flash algorithm supported The AMD and Intel algorithm Almost all currently available flash memories can be programmed with one of this algorithm The flash type se lects the appropriate algorithm and gives additional information about the used flash For 8bit only flash select AM29F 128BX8 For 8 16 bit flash in 8bit mode select AM29BX8 I28BX8 For 8 16 bit flash in 16bit mode select AM29BX16 I28BX16 For 16bit only flash select AM29BX16 I28BX16 The following table shows some examples Chipsize Am29F010 AM29F 0x020000 Am29F800B AM29BX8 AM29BX16 0x100000 Am29DL323C AM29BX8 AM29BX16 0x400000 Intel 28F032B3 128BX8 0x400000 Intel 28F640J3A 128BX8 128BX16 0x800000 Intel 28F320C3 128BX16 0x400000 Note Some Intel flash chips
26. ode defines how breakpoints are processed The target pro cessor may be frozen FREEZED option or may be set to loop in an ex ception procedure LOOP option while the application software is halted Select the appropriate CPU type For CPU32 select CPU32 For Nucleus only CPU32 32 is supported Enter the clock rate which the target CPU runs after BDI has worked through the init list BDI selects the BDM communication speed based on this parameter If this parameter selects a CPU clock rate that is higher than the real clock BDM communication may fail When selecting a clock rate slower than possible BDM communication still works but not as fast as possible In all configurations except when use no target resources is activated BDI needs some target memory space Enter here the start address of this memory area A maximum of 512 bytes is needed The BDI needs to know where the vector table is located Enter here the start address of the vector table This address is automatically loaded into the VBR register at startup time The application should not change the VBR unless use no target resources is selected Together with Nucleus the terminal function is not supported Enter a val ue of 00000000 in any case This disables the terminal function Copyright 1992 2005 by ABATRON AG V 1 00 d La BDM interface for Nucleus Debugger BD 2000 CPU3Z 32 User Manual 17 Loop Level Selects the priority level interr
27. p Level CURRENT Single step is implemented by setting the Trace bit in the processor status register So a single step steps always over the current instruction If interrupts are pending they are served first without stop ping the target processor In order to halt the application TRAP 1 is used Copyright 1992 2005 by ABATRON AG V 1 00 d La BDM interface for Nucleus Debugger BD 2000 CPU3Z 32 User Manual 20 The following diagram shows the used universal exception procedure for CPU32 targets May be this helps you to understand how BDI works in LOOP mode Vectortable gt save all register Target BDI2000 set SFC DFC to supervisor data space SE write loop level to status register cleared Test and clear semaphore set set semaphore set acknowledge flag clear restart flag r enter BDM mode BDM interrupt BGND instruction read stackframe pointer no Acknowledge BDI2000 firmware flag cleared lt 4 clear ackhowledge flag The application loops here when stopped Also if interrupts are enabled Loop Level lt 7 tasks with lower priority will get no CPU time because the stopped task consumes it all ae set restart flag restart flag set yes restore all registers RTE Copyright 1992 2005 b
28. r 101000 if MBAR points to 100000 all numbers in hexadecimal 4 1 Startup Mode Startup mode defines how the BDI interacts with the target system after a reset or power up sequence 4 1 1 Startup mode RESET In this mode no ROM is required on the target system The necessary initialization is done by the BDI with the programmed init list The following steps are executed by the BDI after system reset or system power up e RESET and BKPT are activated on the target system e RESET is deactivated and the target system changes to background debug mode If the target system does not change to background debug mode the BDI waits for a short time and then activates the BERR line e Register DFC and SFC are set to supervisor data space e The BDI works through the initialization list and writes to the corresponding addresses e Depending on the break mode the necessary vectors are set and help code is written into the RAM on the target system The RESET mode is the standard working mode Other modes are used in special cases i e applications in ROM special requirements on the reset sequence Copyright 1992 2005 by ABATRON AG V 1 00 d La BDM interface for Nucleus Debugger BD 2000 CPU3Z 32 User Manual 18 4 1 2 Startup Mode STOP In this mode the initialization code is in a ROM on the target system The code in this ROM handles base initialization and sets the stackpointer At the end of the code the initializ
29. this mode the following steps are executed by the BDI after system reset or power up e RESET and BKPT are activated on the target system e RESET is deactivated and the target system changes to background debug mode If the target system does not change to background debug mode the BDI waits for a short time and then activates the BERR line e Register DFC and SFC are set to supervisor data space e The target CPU is started the target starts at the address fetched when reading the start vec tor at address 0 e The target system is executing the application code e The application runs until the debugger stops the execution e BKPT is activated on the target system and the target system changes to background debug mode If the target system does not change to background debug mode the BDI waits for a short time and then activates the BERR line e Depending on the break mode the necessary vectors are set and help code is written into the RAM on the target system Copyright 1992 2005 by ABATRON AG V 1 00 d La BDM interface for Nucleus Debugger BD 2000 CPU3Z 32 User Manual 19 4 2 Breakpoint Mode The use of breakpoints is only possible if the application code is stored in RAM not in ROM on the target system Depending on the selected breakpoint mode breakpoint and single step functions are implemented total differently 4 2 1 Breakpoint Mode FREEZED In this mode breakpoints are implemented by replacing
30. tive Copyright 1992 2005 by ABATRON AG V 1 00 d La BDM interface for Nucleus Debugger BDIZ000 CPU32 32 User Manual 10 2 4 Connecting the BDI2000 to Host 2 4 1 Serial line communication The host is connected to the BDI through the serial interface COM1 COM4 The communication cable between BDI and Host is a serial cable RXD TXD are crossed There is the same connector pinout for the BDI and for the Host side Refer to Figure below RS232 Connector for PC host Target System 2 RXD data from host 3 TXD data to host 5 GROUND PC Host UI RS232 Rev B C RS232 Connector for PC host Target System 2 RXD data from host 3 TXD data to host 5 GROUND BDl2000 PC Host est RS232 Copyright 1992 2005 by ABATRON AG V 1 00 d La BDM interface for Nucleus Debugger BDIZ000 CPU32 32 User Manual 11 2 4 2 Ethernet communication The BDI2000 has a built in 10 BASE T Ethernet interface see figure below Connect an UTP Un shilded Twisted Pair cable to the BD2000 For thin Ethernet coaxial networks you can connect a commercially available media converter BNC gt 10 BASE T between your network and the BDI2000 Contact your network administrator if you have questions about the network 10 BASE T Connector 1 TD 2 TD 3 RD Target
31. upt priority mask the application uses when halted in LOOP mode A level of 7 disables all interrupts when the application is halted The value CURRENT default means the application loops with the level currently active at the point where it is stopped use no target res Check this switch if the BDI should not use any RAM or vectors in the tar get system This option is only enabled when FREEZED is selected as breakpoint mode This mode is suitable for testing new hardware or de bugging custom exception routines Run Time When startup mode STOP is selected this option allows to set the run time after reset in milliseconds until the target CPU is stopped Values from 100 0 1 sec till 32000 32 sec are accepted SIM60 Breakpoint The internal breakpoint logic in a CPU with a SIM60 module e g MC68360 is supported and can be used to set Breakpoints on variable accesses or to set code breakpoints even when the code runs out of a read only memory e g Flash Device Check this switch if the SIM60 breakpoint logic is present and should be used to support hardware break points Only one hardware breakpoint can be set at the same time In the special case when also use no target resources is checked every code breakpoint uses the SIM60 hardware In this mode it is easy to work through the code even when stored in ROM by simple mouse clicks to the source code RegBase Enter the base address of the SIM60 registers For example ente
32. y ABATRON AG V 1 00 d La BDM interface for Nucleus Debugger BD 2000 CPU3Z 32 User Manual 21 4 3 Workspace Depending on the working mode the BDI needs some RAM in the target system The following table shows how much RAM is used in the different modes Mode Remark RESET FREEZED 4 needed to trap the exceptions STOP FREEZED 4 needed to trap the exceptions RUN FREEZED 4 needed to trap the exceptions RESET LOOP 512 used for standard exception procedure and the initial Supervisor stack STOP LOOP 256 used for standard exception procedure RUN LOOP 256 used for standard exception procedure Vectors in RUN mode When RUN mode is selected only specific vectors are initialized when the application is halted for the first time CPU32 0 9 12 24 and 33 47 in LOOP mode Copyright 1992 2005 by ABATRON AG V 1 00 d La BDM interface for Nucleus Debugger BD 2000 CPU3Z 32 User Manual 22 5 Working with Nucleus For information about using the Nucleus debugger look at the appropriate Nucleus user s manual 5 1 Direct Commands For special functions mainly for flash programming the BDI supports so called Direct Commands This commands can be entered in a codelet file e g PRELOAD CDL or directly executed in the Nu cleus Debugger Command Line Window This Direct Commands are not interpreted by the Nucleus Debugger but directly sent to the BDI After processing the comm

Download Pdf Manuals

Related Search

bdiNDI_UserManual_CPU32_32

bdiNDI_UserManual_CPU32_32+

Contents

Download Pdf Manuals

Related Search

Related Contents