User Manual - Abatron AG
Contents
1. 3Vcc Target 450mA 5 0Vcc Target For pin description and layout see chapter 2 1 Connecting the BDI1000 to Target Insert the en closed Jumper as shown in figure below Please ensure that the jumper is inserted correctly A For error free operation the power supply to the BDI1000 must be between 2 5V and 5V DC The maximal tolerable supply voltage is 5 25 VDC Any higher voltage or a wrong polarity might destroy the electronics Jumper POWER Connector 1 Vcc BDI1000 2 5 5V 2 Vcc Target 42 5 5V Target A Connector TARGET A 53 3 GROUND 5 GROUND The green LEDs BDI and TRGT marked light up when target is powered up 9 Vcc Target and the jumper is inserted correctly O Copyright 1992 2001 by ABATRON AG V 1 01 e A BDM interface for CodeWarrior Debugger BDI1000 MPC5xx 8xx User Manual 9 2 3 Status LED MODE The built in LED indicates the following BDI states MODE LED BDI STATES The BDI is ready for use the firmware is already loaded The power supply for the BDI1000 is 2 5VDC The BDI loader mode is active an invalid firmware is loaded or loading firmware is active O Copyright 1992 2001 by ABATRON AG V 1 01 rj A BDM interface for CodeWarrior Debugger BDI1000 MPC5xx 8xx User Manual 10 2 4 Connecting the BDI1000 to Host 2 4 1 Serial line communi2. BDM interface for CodeWarrior Debugger BDI1000 MPC5xx 8xx User Manual 4 2 Installation 2 1 Connecting the BDI1000 to the 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 VFLSO SRESET GROUND DSCK GROUND VFLS1 HRESET DSDI Vcc Target DSDO 1 9 i an f Target Connector j BEN j 2 10 oooNnNoOoANAUON The green LED TRGT marked light up when target is powered up For TARGET A connector signals see table on next page O Copyright 1992 2001 by ABATRON AG V 1 01 e A BDM interface for CodeWarrior Debugger BDI1000 MPC5xx 8xx User Manual 5 BDI MAIN TARGET A Connector Signals Description VFLSO These pin and pin 6 VFLS1 indicate to the debug port controller whether or not the MPC is in debug mode When both VFLSO and VFLS1 are at 1 the MPC is in debug mode SRESET This is the Soft Reset bidirectional signal of the MPC8xx On the MPC5xx it is an output The debug port configuration is sampled and determined on the rising edge of SRESET for both processor families On the MPC8
3. Interface PC Host mm RS232 Ethernet 10 BASE T UJ The BDI1000 adds Background Debug Mode features to the CodeWarrior debugger environment from Metrowerks With the BDI1000 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 BDI1000 so it works with the CodeWarrior debugger 1 1 BDI1000 The BDI1000 is a processor system in a small box It implements the interface between the BDM pins of the target CPU and a 10Base T Ethernet RS232 connector BDI1000 is powered by a MC68331 256Kbyte RAM and a flash memory of 512Kbyte As a result of consistent implementation of lasted technology the BDI1000 is optimally prepared for further enhancements The firmware and the pro grammable logic of the BDI1000 can be updated by the user with a simple Windows based configu ration program The BDI1000 supports target system voltages from 2 7 up to 5 Volts O Copyright 1992 2001 by ABATRON AG V 1 01 rj A
4. 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 Switch OFF the power supply for the BDI and open the unit as described in Appendix Maintenance Place the jumper in the INIT MODE position Jumper Connect the power cable or target cable if the BDI is powered from target system pm ED z om Switch ON the power supply for the BDI again and wait until the T INIT MORE LED MODE blinks fast Ee Turn the power supply OFF again DEFAULT Return the jumper to the DEFAULT position T Reassemble the unit as described in Appendix Maintenance O Copyright 1992 2001 by ABATRON AG V 1 01 e A BDM interface for CodeWarrior Debugger BDI1000 MPC5xx 8xx User Manual 15 3 Init List Type Address Value Comment NOP eaaa E TOt LL Lond WSPR 638 0x02200000 IMMR internal memory at 0x02200000 WSPR 158 Ox00000007 ICTAL not serialized no show cycles NOP Init SIU register WM32 0x02200000 001632440 SIUMCR WM32 002200004 OxFFFFFF88 SYPCR enable bus monitor disable software watchd WM16 0x02200200 00002 TBSCR stop timebase and decrementer while freeze
5. 0 BASE T 5 5 Mbit s BDM 12 Mbit s JTAG 2 7 5 VDC 5 T 4 60 C 20 C 65 C 90 rF 160 x 85 x 35 mm 280 g EN 50081 2 EN 50082 2 Specifications subject to change without notice O Copyright 1992 2001 by ABATRON AG V 1 01 e A BDM interface for CodeWarrior Debugger BDI1000 MPC5xx 8xx User Manual 20 7 Environmental notice Dj e Disposal of the equipment must be carried out at a designated disposal site 8 Declaration of Conformity CE Declaration of Conformity This declaration is valid for the following product Type of device BDM JTAG Interface Product name BDI1000 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 EN50081 2 EN50082 2 This declaration of conformity is based on the test report no QNL E079 05 9 a of Quinel Zug accredited according to EN 45001 Manufacturer Abatron AG St ckenstrasse 4 CH 6221 Rickenbach Authority poy WI Py TN did er at Pu m od Max Vock Ruedi Dummermuth Marketing Director Technical Director Rickenbach November 2 1999 O Copyright 1992 2001 by ABATRON AG V 1 01 e A BDM interface for CodeWarrior Debugger BDI1000 MPC5xx 8xx User Manual 21 9 Warranty ABATRON Switzerland warrants th
6. 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 b10mpc exe Configuration program b10mpc hlp Helpfile for the configuration program b10mpc cnt Help contents file b10ppcfw xxx Firmware for BDI1000 for MPC8xx MPC5xx targets ppcjed10 xxx JEDEC file for the BDI logic device programming bdiifc32 dll BDI Interface DLL bdi Configuration Examples Example of an installation process Copy the entire contents of the enclosed diskette into a directory on the hard disk You may create a new shortcut to the b10mpc exe configuration program e Copy the BDI interface DLL to CodeWarrior Bin Plugins Support Abatron bdiifc32 dll O Copyright 1992 2001 by ABATRON AG V 1 01 A User Manual 13 2 6 Configuration 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 BDM interface for CodeWarrior Debugger BDI1000 MPC5xx 8xx Load or update the firmware logic store IP address gt Firmware Set the communication parameters between Host and BDI gt Communication gt Initlist gt Mode gt Mode Transmit Setup an initialization list for the target processor Select the working mode Transmit the configuration to the BDI For in
7. BDM interface for CodeWarrior V Debugger DewerPC MPOgxss MPQSee User Manual Manual Version 1 01 for BDI1000 AAR N 1992 2001 ABATRON AG e A BDM interface for CodeWarrior Debugger BDI1000 MPC5xx 8xx User Manual 2 1 IntroduellOD ssccnucin Dadti etus die cadcm iiec Ind Pru PI PUDE GET ei asd teen avais cr rcd Pa dS 3 m HBT OOO Pcr 3 2 CC ETT Ero eS 4 2 1 Connecting the BDTTOO0 to the Target pee eoe Tete leone ee Ree 4 2 1 1 Changing Target Processor Type uii e tote teen edhe Se Ele eco ti use Lin ue OUE 6 2 2 Connecting the BDI1000 to Power Supply sssseeeeeeeenneeeen nenne 7 2 2 1 External Power SUpply accipe treten nre ether oe opere tonis eke 7 2 2 2 Power Supply from Target System sesssssssseeeeeeenereeennnee nenne 8 2 3 Status LED MODE to ted sspe tul m cup D Resa n M deems carted M DuC dU AE 9 2 4 Connecting the BDI1000 to Host iir cae Ip E XR ERR HER D Rr ern 10 2 4 1 Serial line COMMUMICAUO Med sar toes ds acte o ERE E Se ber eden ver el esses la uu AUN 10 2 4 2 Ethernet communication scu desse ib hr OR t s de beiede o bab Qr Pd peg rr dee 11 2 5 Installation of the Configuration Software sseeeceeeeeeeenneene 12 2 5 OMMOUNAU ON canc e tet oe E siste Lem Mons sessi tue tte Eie fees en mum D oue 13 25 1 BDITODO Setup Updale in aede be bets aon tau p nono aunts 13 3 Inlt Bist ig cee es i ee ce ee ee ee uiu ine
8. DI being clocked in The DSDO serves also as READY signal for the debug port con troller to indicate that the debug port is ready to receive controller s command or data Mention of sources used MPC860ADS User s Manual Revision A Enhanced Debug Mode Detection For MPC8xx and MPC555 targets debug mode Freeze detection also works when the BDM con nector pins VFLSO and VFLS1 are not connected to the target If not connected to VFLSx this BDM connector pins should be left open or tied to Vcc The BDI uses the following algorithm to check if the target is in debug mode freezed BOOL PPC TargetFreezed void if VFLSO 1 VFLSO 1 return FALSE read debug port status if status freezed return TRUE else return FALSE O Copyright 1992 2001 by ABATRON AG V 1 01 e A BDM interface for CodeWarrior Debugger BDI1000 MPC5xx 8xx User Manual 6 2 1 1 Changing Target Processor Type Before you can use the BDI1000 with an other target processor type e g CPU32 lt gt PPC a new setup has to be done see chapter 2 6 Configuration During this process the target cable must be disconnected from the target system The BDI1000 needs to be supplied between 2 5V and 5V via the POWER connector For more information see chapter 2 2 1 External Power Supply A To avoid data line conflicts the BDI1000 must be disconnected from the target system while programming the logic for an othe
9. WM32 002200320 Ox55CC4433 RTCSCK unlock real time clock status and control re WM16 0x02200220 00002 RTCSC stop real time clock while freeze is asserted WM16 0x02200240 00002 PTSCR stop periodic interrupt while freeze is assertec NOP Init UPM x CIIDkA nun nn1 co nun onnn1 7C Cat addrana far hACD and kInD New 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 BDI1000 and worked 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 Note You may also use the debuggers feature to setup the hardware But keep in mind that the BDI will speed up BDM communication clock after processing its own initialization list based on the Clock Rate field in the BDI Working Mode dialog box see next chapter The Clock Rate value you have to enter is therefore the value the target runs immediately after reset To use a BDM speed as fast as possible you should at least speed up the target with an entry in the BDI initialization list and set the Clock Rate field to the appropriate value The re
10. carefully the print Control that the LEDs align with the holes in the back panel 5 2 Push carefully the front panel and the blue elastig sealing on the casing Check that the LEDs align with the holes in the front panel and that the position of the sealing is as shown in the figure below casing NS elastic sealing back panel Er 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 a 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 2001 by ABATRON AG V 1 01 e A BDM interface for CodeWarrior Debugger BDI1000 MPC5xx 8xx User Manual 25 C Trademarks All trademarks are property of their respective holders O Copyright 1992 2001 by ABATRON AG V 1 01
11. cation 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 Target System for PC host CPU PC Host mm RS232 i 2 RXD data from host 3 TXD data to host 5 GROUND BDhooo O Copyright 1992 2001 by ABATRON AG V 1 01 rj A BDM interface for CodeWarrior Debugger BDI1000 MPC5xx 8xx User Manual 11 2 4 2 Ethernet communication The BDI1000 has a built in 10 BASE T Ethernet interface see figure below Connect an UTP Unshilded Twisted Pair cable to the BD1000 For thin Ethernet coaxial networks you can connect a commercially available media converter BNC gt 10 BASE T between your network and the BDI1000 Contact your network administrator if you have questions about the network UTP port of the BDI1000 and the hub to which it is connected 10 BASE T Connector Target System 2 2 TD 5xx8xx PN Uu 10 BASE T 6 RD When the LI LED light is ON data link is successful between the PC Host NN BDhiooo Ethernet 10BASE T Copyright 1992 2001 by ABATRON AG V 1 01 e A BDM interface for CodeWarrior Debugger BDI1000 MPC5xx 8xx User Manual 12 2
12. e physical diskette cable BDI1000 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 BDI1000 or documentation The 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 BDI1000 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 2001 by ABATRON AG V 1 01 e A BDM interface for CodeWarrior Debugger BDI1000 MPC5xx 8
13. formation about the dialogs and menus use the help system F1 2 6 1 BDI1000 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 BDI1000 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 Connect BDI1000 Loader r Channel r Baudrate C COMI C 9600 COM2 C 19200 C COM3 C 38400 C COM4 57600 SN 91000140 BDI2000 Firmware Logic Current Loader 1 00 Firmware 1 00 Logic 1 00 Newest Current io uwe r TCP IP Configuration IP Address Subnet Mask Default Gateway Cancel k 151 120 25 102 255 255 255 255 255 255 255 255 Writing setup data passed dialog box BDI1000 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 BDI1000 is connected during this setup session Baudrate Select the baudrate used to communicate with the BDI1000 loader during this setup session O Copyright 1992 2001 by ABATRON AG V 1 01 e A BDM interface for CodeWarrior Debugger BDI1000 MPC5xx 8xx User Manual 14 Connect Current U
14. ication code The application runs until it is stopped by the debugger Copyright 1992 2001 by ABATRON AG V 1 01 e A BDM interface for CodeWarrior Debugger BDI1000 MPC5xx 8xx User Manual 18 5 Working with CodeWarrior 5 1 Setup Use the CodeWarrior IDE Preferences dialog box section Debugger gt Remote Connections and setup the appropriate communication parameters for the Abatron TCP IP and Abatron Serial con nection Use the CodeWarrior your project Settings dialog box section Debugger gt Remote Debugging and select either Abatron TCP IP or Abatron Serial 5 2 Exceptions From the CodeWarrior menu Edit open your project Settings Select Debugger EPPC Exceptions This opens the EPPC Exceptions dialog box Here it is possible to define which EPPC exceptions causes an entry into debug mode Do not check exceptions which should be handled by application code typically External Interrupt and Decrement er Interrupt Never disable Development Port and External Breakpoint For normal debugging you should also not disable Program Trace Software Emulation Load Store Breakpoint and Instruction Breakpoint aC and ASM Settings B Target Settings Panels E Language Settings B EPPC Exceptions C C Language Exception handling currently only supported for EPPC BDM Targets Sii edd Exception Handling check the exceptions to always catch E Code Generation Ox40000000 System Rese
15. ly 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 Observe precautions for handling 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 I BDI1000 Alahon AG F 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 3 1 While holding the casing remove the front panel and the blue elastig sealing casing NS elastic sealing front panel Copyright 1992 2001 by ABATRON AG V 1 01 ldi BDM interface for CodeWarrior Debugger BDI1000 MPC5xx 8xx User Manual 24 figure below Mie Jumper settings E o om 4 DEFAULT INIT MODE 4 1 While holding the casing slide carefully the print in position as shown in Fuse Position o Pull out carefully the fuse and replace it K Type Microfuse MSF 1 6AF Manufacturer Schurter Reinstallation 5 1 Slide back
16. ommunication speed based on this param eter If this parameter selects a CPU clock rate that is higher than the real clock rate BDM communication may fail When selecting a clock rate slower than possible BDM communication still works but not as fast as possible In order to access the floating point registers of a MPC5xx microproces sor the BDI needs a workspace of 8 bytes in target RAM Enter the base address of this RAM area This memory is used when a floating point reg ister is accessed If there is no RAM space available for the BDI you may enter OXFFFFFFFF as the workspace address but then accessing float ing point registers is not possible Click on this button to send the initialization list and the working mode to the BDI This is normally the last step done before the BDI can be used with the debugging system O Copyright 1992 2001 by ABATRON AG V 1 01 e A BDM interface for CodeWarrior Debugger BDI1000 MPC5xx 8xx User Manual 17 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 HRESET is activated on the target system HRESET is deactivated and the target is forced into debug mode The BDI
17. pdate IP Address Subnet Mask Default Gateway Transmit Click on this button to establish a connection with the BDI1000 loader Once connected the BDI1000 remains in loader mode until it is restarted or this dialog box is closed Press this button to read back the current loaded BDI1000 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 BDI1000 flash mem ory programmable logic Enter the IP address for the BDI1000 Use the following format xxx xxx xxx xxxe g 151 120 25 101 Ask your network administrator for assigning an IP address to this BDI1000 Every BDI1000 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 BDI1000 flash memory In rare instances you may not be able to load
18. r target CPU O Copyright 1992 2001 by ABATRON AG V 1 01 e A BDM interface for CodeWarrior Debugger BDI1000 MPC5xx 8xx User Manual 7 2 2 Connecting the BDI1000 to Power Supply 2 2 1 External Power Supply The BDI1000 needs to be supplied between 2 5V and 5V via the POWER connector The available power supply from Abatron option or the enclosed power cable can be directly connected In order to ensure reliable operation of the BDI1000 keep the power supply cable as short as possible A For error free operation the power supply to the BDI1000 must be between 2 5V and 5V DC The maximal tolerable supply voltage is 5 25 VDC Any higher voltage or a wrong polarity might destroy the electronics POWER Connector 1 Voc 42 5 5V GND 3 1 Vcc 3 GROUND The green LED BDI marked light up when power 2 5 5V is connected to the BDI1000 Please switch on the system in the following sequence 1 gt external power supply 2 gt target system O Copyright 1992 2001 by ABATRON AG V 1 01 e A BDM interface for CodeWarrior Debugger BDI1000 MPC5xx 8xx User Manual 8 2 2 2 Power Supply from Target System The BDI1000 needs to be supplied between 2 5V and 5V via TARGET A connector This mode can only be used when the target system runs between 2 5V and 5V and the pin Vcc Target is able to deliver a current up to 900mA Q22 5Vcc Target e 700mA Q23
19. s 15 4 BDI Workitig mod65 ouri terme gus tori i eeu d ewe s eie ew nne bnin eda ern Vom sa D ea da kids 16 AA Startup Mode re mtt tube ee Rt ler pe n tale edd ERa aE aaa 17 4T T Startup mode RESET t Eat peer RM Ret cedars s b Dita et due ters 17 4 12 Startup Mode STOP cole te Ree co Me p ERR EXER E HE nd Stc a m RR RH e Ress 17 41 3 Starup mode RUN edi fet ote pte ttti pax oet ESA pn Bekk diene eaan 17 5 Working with CodeWAatrtloL nates ken et iet hatc elie nate ae eens ate 18 x SS GTP m 18 5 2 EXC OPI OMS MR C tach cad ica clic ec asia pated AEE Ae AEE a EA eaten dee eae 18 6 Specificallons cuoi ele eM Io lube eraa cope cou icit eM Let ster oe a tt 19 4 Environmental nollGOsudsiicee cete nues ko sd zen aE asc e na Do daas trE a pM EU IUE ERU LUKE DAS EC US auessa T MNE 20 8 Declaration of Conformity CE eeeeeeeeeeeeeeeeeeseeseeeeeeee nennen nnnn nani nennt nnns nnn nnns 20 9 Warranty iainta cider co tien raaa ada aada naaa araa Vnde cu Foren E E Ku Cw Vaca su E Ed DL ds 21 Appendices A TroubieshoOlllig icta oed en tree naaras opaan enire OR oA uS E Ene E PURSE EN S HERUM EE 22 zm cnr ET 23 C Trademarks 4 Lecteurs Aue A LA LL ELLE ELE 25 O Copyright 1992 2001 by ABATRON AG V 1 01 rj A BDM interface for CodeWarrior Debugger BDI1000 MPC5xx 8xx User Manual 3 1 Introduction Target System Target System BDM
20. st of the initialization e g memory controller can be done with the debugger O Copyright 1992 2001 by ABATRON AG V 1 01 e A BDM interface for CodeWarrior Debugger BDI1000 MPC5xx 8xx User Manual 16 4 BDI working modes BDI Working Mode Identification j40S860 r Startup Breakpoint A CPU Type MPCBxx Reset C Stop Clock Rate 20000000 Hz C C Hardware Run Workspace JFFFFFFFF Hex 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 Clock Rate Workspace Transmit 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 mode defines how instruction breakpoints are implemented When Software is selected default instruction breakpoints are set as re quested by the debugger Software or Hardware breakpoints When Hardware is selected the BDI uses always hardware breakpoints This is useful when the attached debugger does not support hardware break points on instruction access For CodeWarrior select always Software Select the CPU type of the target system Enter the clock rate the target CPU runs after BDI has worked through the init list BDI selects the BDM c
21. t M 0x00004000 Software Emulation Global Optimizations 0x20000000 Check Stop 0x00002000 Instruction TLB Miss EPPC Processor 0x10000000 Machine Check T 000001000 Instruction TLB Error EPPC Disassembler 002000000 External 000000800 Data TLB Miss E Linker M 0 01000000 Alignment 0x00000400 Data TLB Error EPPC Linker M 0 00800000 Program v 0 00000008 Load Store Breakpoint E Editor M 0 00400000 Floating Point Unavailable 0x00000004 Instruction Breakpoint Custom Keywords 000200000 Decrementer 000000002 Extemal Breakpoint E Debugger M 0 00040000 System Call M 0 00000001 Development Port Debugger Settings M 0 00020000 Trace EPPC Target Settin Remote Debugging Connection Settings Factory Settings Jf unselected these may affect the debugger s ability to control target Copyright 1992 2001 by ABATRON AG V 1 01 e A BDM interface for CodeWarrior Debugger BDI1000 MPC5xx 8xx User Manual 19 6 Specifications Operating Voltage Limiting Power Supply Current max 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 Electromagnetic Compatibility EMC 2 5 5 25VDC 900mA 22 5V 700mA 23 3V 450mMA 5 0V 9 600 19 200 38 400 57 600 115 200 8 none 1 1
22. works through the initialization list and writes to the corresponding addresses 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 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 At the end of the code the initialization program enters an endless loop until it is interrupted by the BDI This mode is intended for special requirements on the reset sequence e g loading a RAM based programmable logic device In this mode the following steps are executed by the BDI after system reset or power up HRESET is activated on the target system HRESET is deactivated and the target is forced into debug mode The target is started and begins executing application code After a delay of 2 seconds the target is forced into debug mode The BDI works through the initialization list and writes the corresponding addresses 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 when the debugger is started In this mode the following steps are executed by the BDI after system reset or power up HRESET is activated on the target system HRESET is deactivated and the target is forced into debug mode The target is startet and begins executing appl
23. xx User Manual 22 Appendices A Troubleshooting Problem The firmware can not be loaded Possible reasons The BDI is not correctly connected with the target system see chapter 2 The power supply of the target system is switched off or not in operating range 2 5 VDC 5 VDC gt MODE LED is OFF or RED The built in fuse is damaged gt MODE LED is OFF The BDI is not correctly connected with the Host see chapter 2 A wrong communication port Com 1 Com 4 is selected Problem No working with the target system loading firmware is ok Possible reasons Wrong pin assignment BDM JTAG connector of the target system see chapter 2 Target system initialization is not correctly gt enter an appropriate target initialization list An incorrect IP address was entered BDI1000 configuration BDM JTAG signals from the target system are not correctly short circuit break The target system is damaged Problem Network processes do not function loading the firmware was successful Possible reasons The BDI1000 is not connected or not correctly connected to the network LAN cable or media converter An incorrect IP address was entered BDI1000 configuration O Copyright 1992 2001 by ABATRON AG V 1 01 rj A BDM interface for CodeWarrior Debugger BDI1000 MPC5xx 8xx User Manual 23 B Maintenance The BDI needs no special maintenance Clean the housing with a mild detergent on
24. xx it is a bidirectional signal which may be driven externally to generate soft reset sequence This signal is in fact redundant regarding the MPC8xx debug port controller since there is a soft reset signal integrated within the debug port protocol However the local debug port controller uses this signal for compatibility with MPC5xx existing boards and s w System Ground Debug port Serial Clock During asynchronous clock mode the serial data is clocked into the MPC according to the DSCK clock The DSCK serves also a role during soft reset configuration VFLS1 These pin and pin 1 VFLSO indicate to the debug port controller whether or not the MPC is in debug mode When both VFLSO and VFLS1 are at 1 the MPC is in debug mode HRESET This is the Hard Reset bidirectional signal of the MPC When this signal is asserted low the MPC enters hard reset sequence which include hard reset configuration This signal is made redundant with the MPC8xx debug port controller since there is a hard reset com mand integrated within the debug port protocol Debug port Serial Data In Via the DSDI signal the debug port controller sends its data to the MPC The DSDI serves also a role during soft reset configuration Vcc Target TARGET POWER This input to the BDI1000 is used to detect if the target is powered up DSDO Debug port Serial Data Out DSDO is clocked out by the MPC according to the debug port clock in parallel with the DS
Download Pdf Manuals
Related Search