Home

ST7MDT2-EMU2B HDS2 Series Emulator User Manual

1. External clock input SUB Click connector The SUB click external clock connector on the probe can be used with the two SMB to BNC connectors provided in the emulator package Voltage at these connectors must range between 0 V and 5 V The levels are TTL However if additional connectors are needed you can purchase them at the dealers or manufacturers listed in the section entitled Hardware spare parts on page 80 This list is not exhaustive The oscillator on the probe does not take into account the application circuitry but only the Probe circuitry So you must insert its quartz into the XT1 reserved location between the C1 and C2 capacitors If you want to use a custom clock oscillator located on your board you must connect the same oscillator on the probe After this you must choose the PROBE clock as clock source Refer to Emulation Functional Limitations and Discrepancies on page 59 for information on the application clock available on your emulator WATCHDOG This option allows you to choose whether the watchdog timer is enabled by software or by hardware When the Software option is chosen the watchdog has to be enabled by software When the Hardware option is chosen the watchdog is always enabled ST7MDT2 EMU2B User Manual 4 Emulator Features 4 7 3 4 8 4 8 1 4 8 2 Refer to the
2. 63 U user application board definition 78 workspaces creating NEW aihair eiai 32 Saving rennen 39 Information furnished is believed to be accurate and reliable However STMicroelectronics assumes no responsibility for the consequences of use of such information nor for any infringement of patents or other rights of third parties which may result from its use No license is granted by implication or otherwise under any patent or patent rights of STMicroelectronics Specifications mentioned in this publication are subject to change without notice This publication supersedes and replaces all information previously supplied STMicroelectronics products are not authorized for use as critical components in life support devices or systems without the express written approval of STMicroelectronics The ST logo is a registered trademark of STMicroelectronics Intel is a U S registered trademark of Intel Corporation Microsoft Windows and Windows NT are U S registered trademarks of Microsoft Corporation 2000 STMicroelectronics All Rights Reserved Purchase of C Components by STMicroelectronics conveys a license under the Philips Patent Rights to use these components in an system is granted provided that the system conforms to the Standard Specification as defined by Philips STMicroelectronics Group of Companies Australia Brazil China Finland France Germany Hong Kong Ind
3. Figure 15 QFP64 Pin Socket Adapter ref DB389 Components Layout 70 85 ST7MDT2 EMU2B User Manual Appendix B Hardware Schematics Female Connectors 2 X 12 Female Connector 2 X 8 Adapter for Yamaichi Support Figure 16 QFP64 Probe Adapter ref DB200 Components Layout 71 85 Appendix B Hardware Schematics ST7MDT2 EMU2B User Manual zx w 1 cl m T cO 959105 4111 15 vay gadids ZLUN C EH EH e000000000000000000000000008 EH un SERRE BE EEEEEE gt 4 Figure 17 SDIP56 Pin Socket Device Adapter ref DB408 Components Layout 72 85 ST7MDT2 EMU2B User Manual Appendix B Hardware Schematics TU OOO0O0O0O0000000000 p u 000000 fu 190195050 c3 E
4. The parallel cable is connected between the emulator and one of the PC s parallel ports LPT1 or LPT2 Note that the use of switch boxes between the parallel port connector of your PC and the emulator are not recommended The development board is powered on The parallel cable used is the one supplied with the kit by STMicroelectronics If none of the above items has been overlooked this may mean that your parallel port connection needs to be reconfigured Please refer to Changing the Parallel Port Setup on Your PC on page 64 Error Messages when starting the Ensure that SUE CED gt Emulator The flat cables linking the ST7MDT2 Active Probe and Communication error with EMULA the emulator box are properly connected TOR board The selected configuration file matches the connected or ST7MDT2 Active Probe configuration SYSTEM ERROR DETECTED by If it doesn t from within ST7 Visual Debug open the EMULATOR BOARD RESET CPU Configuration dialog box selecting Tools gt MCU Configuration from the main menu Choose the correct MCU target device in the drop down list then click OK to save your changes to the wsp file for your debugging session Exit STVD7 and power off the emulator Power on the emulator and restart STVD7 to ensure correct installation You are using the TQFP44 MCU pack TQFP44 probes are not provided with this emulator kit If age you are using the TQFP MCU package you can or
5. Source File asm Types Required asm li macrost7 asm debug Options Resulting File obj 1st Types Linker Step Required lyn macrost7 0bj macrost7 Options asm macrost7 asm sym fi macrost7 map Resulting File map 1st Types Converter obsend macrost7 f macrost7 s19 srec not cvdwarf Step applicable or obsend macrost7 f macrost7 hex intel Resulting Application File Necessary Intermediate Files The application file s source files and any necessary intermediate files these are listed above and contain debug information necessary to the STVD should be located in the same project directory You do this when you define your workspace Note It is always preferable to have access to all of the files generated by the development toolchain However you can load s19 or hex binary files directly and have limited debugging capabilities refer to Section 3 8 on page 36 31 85 3 STVD7 ST7MDT2 EMU2B User Manual 3 6 Creating a workspace 1 Select File New Workspace This command opens a new window where you define the name of your workspace and the directory in which you want to work New Workspace C Program Files 5 T M st toolchain 32 85 ST7MDT2 EMU2B User Manual 3 STVD7 2 Then click Next The New Workspace Project Settings dialog box appears New Workspace Project Settings 2 x Workspace filename
6. 7 software and documentation for 8 F ferrites attaching to 15 1577 H hardware INStAN LION eee 12 hardware test 65 HDS2 emulators main 49 c e eee 55 installation hardwarean 12 anne 25 L erp oun 56 load binary Nest ke een 36 EVD STATUS t tiet rete tette 59 EVDAMALUE itio lerne 59 M MB31798 5 ir e sen 11 MCU emi lated 2 ne ee 5 on chip peripherals 57 MCU 42 MCU memory configuringi nennen 44 ERE 44 N Nested Concurrent Interrupts Buttons 60 Non Maskable Interrupt Management 60 on chip peripherals 57 watchdog eiei potaa n aida 58 watchdog in Halt mode 59 output triggers 53 83 85 Index parallel port troubleshooting connection problems 64 passive probe definition of 78 PC System 11 peripherals configuring 43 project settings modifying n a eid 37 Q 4 o e A 67 64 67 R RAM IMU ee ceu eee 11
7. Figure 18 SDIP56 to SDIP42 Device Adapter ref DB326 Components Layout 73 85 Appendix B Hardware Schematics ST7MDT2 EMU2B User Manual B 2 Device adapter pin matching diagrams On the top face of the ST7MDT2 Active Probe ref DB407 there are 64 pins to which you can connect to a multimeter or oscilloscope to monitor signal values However if your target device package has less than 64 pins as is the case for the TQFP44 SDIP56 and SDIP42 packages you need to how the device adapter pins are mapped onto the 64 pins of the ST7MDT2 Active Probe For this reason we have included pin matching diagrams for each of the three aforementioned package types To use them follow these instructions Photocopy the corresponding diagram onto a stiff sheet of paper or cardboard Cut along the dashed edges Don t forget to cut along the inner rectangles e Punch out the rectangular boxes Place the diagram over the 64 pins on the ST7MDT2 Active Probe ref DB407 board The two W1 pins must correspond For TQFP44 Figure 19 Pin matching diagram for TQFP44 package 74 85 ST7MDT2 EMU2B User Manual Appendix B Hardware Schematics For SDIP56 For SDIP42 Figure 20 Pin matching diagrams for SDIP56 and SDIP42 packages 75 85 Appendix B Hardware Schematics 76 85 ST7MDT2 EMU2B User Manual ST7MDT2 EMU2B User Manual Appendix C Glossary APPENDIX C GLOSSARY Application Board Thi
8. 44 S SDIP22 2 uam 18 EE 18 software Updates um een 80 ST7MDT2 M 15 15 ST7MDT2 EMU2B architecture esses 49 specific features 49 ST7MDT2 Active Probe main features 49 STVD7 84 85 ea ofa 27 build context 41 2 22 ann 41 creating a 32 debug 41 installing eee 25 main 5 27 MCU configuration 42 opening binary 36 opening 34 supported application files 29 supported toolchains 29 switching between contexts 42 toolchain paths 26 28 support contact numbers 79 for development 79 information 79 tetti 9 T target device definition of sess 78 s pported ee 5 TOEP OM E 20 64 troubleshooting 63 connection
9. Hardware Test function and if any are detected contact your STMicroelectronics sales representative Product Support on page 79 You may open the Hardware Test dialog box by selecting from the Main Menu Emulator gt Hardware Test or Clicking on the Hardware Test icon in the Emulator toolbar Be cautious in performing a Hardware Test on the emulator while an application is open The opened application WILL BE corrupted by the hardware testing process If you find that your application has been corrupted simply close the application and reopen it 65 85 Appendix A Troubleshooting ST7MDT2 EMU2B User Manual The Hardware T b Hardware Test x dialog box shows a list of different tests Development Board test Iv that can be HALT and RESET emulator test Iv perfo rmed on the Write protect request test Iv emulator Next request test Iv Check the box of SA breakpoint request test each test that you Logical analyser request check wish to perform they are all checked by default and click Apply to start the hardware test Apply Select All Unselect The Hardware tests UR Test will be performed one by one and the Development Board test V Test OK Im results summarized HALT and RESET emulator test in the dialog box as Write protect request test Test OK shown on the right Next request test v TestOK SA breakpoint request test Te
10. The second ref DB379 allow you to connect an actual MCU device to the Yamaichi socket i e without soldering the MCU directly to the footprint see Using the TQFP64 Device Adapter Ref DB379 on page 20 A If you are using the TQFP64 package proceed as follows f you have already designed your application board using a true TQFP64 footprint see the troubleshooting table entry entitled QFP64 TQFP64 Incompatibility on page 64 f you haven t yet designed your application board and want to know how best to do so see the section entitled QFP64 TQFP64 amp QFP44 TQFP44 Footprint Issues on page 67 f you have designed your application board using a hybrid QFP64 TQFP64 compatible footprint how to do this is described in QFP64 TQFP64 amp QFP44 TQFP44 Footprint Issues on page 67 continue with the following instructions A Yamaichi QFP64 socket and its cover are provided in the package Before going through the procedure make sure that the emulator kit you were delivered includes the socket its cover and its screws and washers To connect the ST7MDT2 Active Probe to its TQFP64 device adapter and then to your application follow these steps see Figure 6 ST7MDT2 EMU2B User Manual 2 Getting Started 1 Solder the Yamaichi QFP64 socket base onto your application board Do not use the socket cover set it aside for future use with an actual MCU ST7MDT2 Active Probe ref DB407 Ese Er ius Devi
11. at the left hand side of the graphical viewer you will see a small triangle and rectangular box giving the boundary addresses of the memory zone You can change a boundary address by dragging and dropping the triangle with the mouse to its new location The triangle can be moved either up or down left or right in the graphical viewer 46 85 1574 ST7MDT2 EMU2B User Manual 3 STVD7 3 13 The MCU configuration that you specify will by default be saved in a workspace file wsp for the project The next time the application is opened the STVD will automatically set the MCU configuration as well as the layout of opened windows and other debug information to the same conditions you had when you left the last debugging session If you do not wish your MCU configuration information to be saved in the workspace file you must alter the default Configuration Setup options by clicking on the Conf button Start debugging Once in debug context you are now ready to start debugging your application using the emulator Full documentation on how to e control your STVD7 work environment e use its integrated editor use the many debugging windows and features is available from the online help and the online STVD7 user manual located under Help in the main menu 47 85 3 STVD7 48 85 ST7MDT2 EMU2B User Manual ST7MDT2 EMU2B User Manual 4 Emulator Features 4 1 4 2 4 3 EMULATOR FEATURES Main Fe
12. weorksmywork wsp Software T oolchain ST Hiware Toolchain X Executable Filename sample c hiware sample abs Es Build Maker Hiwaemaker e Maker filename DAHIWARE PROG maker p Makefile or batch file sample c hiware buildmak af Build command line makerbuildmak SS Rebuild All command line makerrebuildmak Start Build Rebuild All in sample c hiware Here you enter your software toolchain your executable filename and your build parameters either by typing or using the drop boxes Select the toolchain and enter the name of your application s executable file For example if you wish to use the Hiware toolchain for ST7 your executable file will be of type abs refer to Table 2 on page 31 click on the browse button E to browse to the folder where your executable file is saved and select it Next choose the type of maker your application uses from the drop down list In the example above we have chosen the default Hiware maker maker exe STVD7 will automatically look for this maker file in the folder you defined as the Hiware toolchain path Finally you must define a make file or a batch file There are several sample files provided with STVD7 see Table 1 on page 30 Here we have chosen 33 85 3 STVD7 3 7 Note 34 85 ST7MDT2 EMU2B User Manual build mak as the default make file used when
13. 460060 U K 44 1628 890800 Asia Pacific Region Japan 81 3 3280 4120 Hong Kong 852 2861 5700 Sydney 61 2 9580 3811 Taipei 886 2 2378 8088 Software updates You can get software updates from the ST Internet web site http mcu st com For information on firmware and hardware revisions call your distributor or ST using the contact list given above Hardware spare parts 80 85 Most of the hardware you will require is included in the emulator kit However some special applications may require additional parts such as connecting an external clock Below is a list of manufacturers and dealers of SMB and BNC connectors that can be used with our product European manufacturers Manufacturer Radiall Dealer Radialex Phone 33 4 72 35 31 72 The EXTERNAL clock male connector on the emulation probe has the following commercial reference In SMB range Number 114665 Adaptable Female connectors to this connector are ST7MDT2 EMU2B User Manual Product Support SMB upright range Number1 14005 for cable 2 6 Number114003 for cable 4 2 Number1 14009 for cable 3 8 SMB kneed range Number114165 for cable 2 6 Number1 14163 for cable 4 2 SMB to BNC range Number191214 Adapter SMB female BNC male Number191215 Adapter SMB female BNC female USA manufacturers Manufacturer R Tek 411 Quentin Road Palatine IL 60067 Phone 847 934 7900 Fax 847 934 7946 Adaptable femal
14. bus 16 bit of the ST7 emulation chip used for RAM addressing and trace DATA bus 8 bit of the ST7 emulation chip Control bus to manage ST7MDT2 Active Probe hardware like breakpoint features ST7 HDS2 Emulation RAM i ST7 Data Parallel link Mies Control nteriace RAM Control HDS2 Control ST9050 ST7 Address Address Address lt ST7MDT2 Active Probe 4 3 2 ST7MDT2 Active Probe Hardware The hardware functions provided by the ST7MDT2 Active Probe are Probe Emulation MCU This is an ST7 microcontroller similar to those of the emulated target device s which runs in emulation mode It acts as the ST7 51 85 4 Emulator Features core and gives access to all on chip peripherals ST7MDT2 EMU2B User Manual Control logic Control logic is provided to manage the software execution by the user i e program running and halting Application Vcc follower The probe emulation MCU is supplied with the same voltage as the application i e must be in the range 3 5 V to 5 5 V e ST7 HDS2 interface All of the communication buses connecting the active pro
15. can be modified ROM Read Only Memory of the microcontroller Write protected This memory type can be modified Stack Stack of the microcontroller This memory type cannot be modified System The emulator uses this space for emulation management This memory type cannot be modified EEPROM This memory is internal to the microcontroller and is located inside the emulation device The programming of this zone is done according to an automaton found in the user manual This memory type cannot be modified Reserved This memory zone is reserved as on the microcontroller It is not allocated to any use and is write protected This memory type cannot be modified Vectors This memory zone contains the user interrupt vectors zone It is write protected This memory type can be modified Application This memory type is microcontroller specific The user can add memory or peripheral resources on its hardware It is not available on every emulator Properties are linked to the user hardware This memory type can be modified For most target MCUs you may modify the following types of memory zone RAM ROM Reserved and Application This feature would enable you for instance to temporarily decrease the RAM zone increase the size of the ROM to exceed what is available on the real microcontroller during the first stages of development Once your program is functional you can start to optimize its size by reducing your code and returning
16. datasheet for your ST7 MCU for more information on the watchdog timer WGD HALT Allows you to determine if a reset is generated when entering HALT mode while the watchdog is active There are two options Reset where a reset is generated when entering Halt mode if the watchdog is active and No Reset where no reset is generated when entering Halt mode Emulation Functional Limitations and Discrepancies The following is a list of functional limitations and discrepancies between certain features of the ST7MDT2 EMU2B emulator and its actual target devices Power Supply The application supply follower allows this emulator to run with an application Vpp ranging between 3 V to 5 5 V If the application isn t powered or the Vpp lt 3 V the power supply is maintained at 3 V If your application is powered by a voltage greater than 5 5 V the emulator will limit this value internally to 5 5 V Low Voltage Detector Management The Low Voltage Detector LVD of the emulator is slightly different than the one embedded in the emulated devices Since the emulation device is always supplied by a voltage ranging between 3 V to 5 5 V the LVD cell detects a fall in the application voltage and resets the emulation microcontroller and the application To enable this functionality you have to select the LVD STATUS field in the Micro Configuration window and toggle the value from OFF to ON You can notice that the field LVD VALUE is able to be set fo
17. device such as memory and the link 49 85 4 Emulator Features 4 3 1 50 85 ST7MDT2 EMU2B User Manual interfaces with the PC This board is connected to the PC via a parallel link and to the second part by two 50 pin connectors The ST7MDT2 Active Probe contains the specific resources for the emulated ST7MDT2 devices and is used as a link between the ST7 HDS2 and your application ST7XXX EMU2B Parallel Link ST7 HDS2 Emulation Memory Control RAM Trace Memory ST9 MCU Flat Cables Address bus ST7 Active Probe ST7 MCU Automaton Control Data bus Control bus Device Adapter Application Board ST7 HDS2 Hardware The hardware functions provided by this component are listed below HDS2 CPU Used to control the ST7XXX HDS board and manage common HDS2 features such as the parallel link with the PC RAM memory 64K bytes for ROM and RAM emulation 64K bytes as break points control and Mapping 1K x 32 bit as trace memory Hardware breakpoint control logic to manage breakpoints from the 16 bit address bus ky ST7MDT2 EMU2B User Manual 4 Emulator Features Logical analyser control logic to manage sophisticated recording and break events in the trace PClink parallel interface for communication with PC e ST7MDT2 Active Probe interface 3 buses connect the ST7 HDS2 to the ST7MDT2 Active Probe Address
18. of two Trigger Outlets on the front panel of the emulator OUT1 or OUT2 This feature enables you to count events using an external equipment when optimizing software for example or to synchronize an oscilloscope when debugging hardware Hardware Events can be used to control the sending of signals to the trigger outputs You can choose the output that you wish the signal to be sent to i e either OUT1 or OUT2 A Hardware Test function that allows you to perform a number of hardware tests on the Development Board at your choosing Refer to Running the Hardware Test for more information A powerful online help facility can be invoked at any time to give additional information about the commands the processor or the emulator kit 27 85 3 STVD7 3 4 28 85 ST7MDT2 EMU2B User Manual Workspaces STVD7 organizes project development and debugging into workspaces Workspaces allow you to store application and project settings and save them as wsp file so that each time you wish to work on the project you will find all of the settings exactly as you left them Creating a workspace is the first thing that you need to do when using STVD7 for the first time or when starting any new project You must have an open workspace to work with STVD7 How to create a new workspace is described in detail in Section 3 6 on page 32 Sample workspaces for each supported toolchain are provided so that you can familiarize yourself with STV
19. plug the ST7MDT2 Active Probe and its connected adapter s onto your application board ST7MDT2 Active Probe Y D Adapter SDIP56 ref DB408 SDIP 56 to SDIP42 Adapter DB326 D SDIP 56 or SDIP42 socket to solder A Application board Figure 7 SDIP42 or SDIP56 MCU Package Connections Step 4 Connecting the power supply Warning Make sure that both the ST7MDT2 EMU2B the application board are powered OFF before making any connections 1 Connectthe external power supply provided with the emulator to the rear panel of the mainframe using a 5 pin DIN connector 2 Plug the power supply into the mains using the supply cable provided Mains Voltage Specifications AC Voltage 100 V to 240 V 19 85 2 Getting Started ST7MDT2 EMU2B User Manual Mains Voltage Specifications Step 5 Powering up Note 2 4 2 5 20 85 1 Check the ST7 HDS2 operating voltage 110 V 220 V indicated on the label on the power supply Contact your dealer if this voltage does not correspond to your mains supply 2 Power up the ST7 HDS2 emulator from the ON OFF switch located on the rear panel The LED labelled Power on the front panel should then light up 3 Power up your application Remember that while your application Vpp supply must be in the 3 5 V to 5 5 V range to comply with the actual target MCU the emulator only supports Vpp in t
20. project or toolchain settings in the event you wish to change them Project 53 Build Rebuild All Stop Bond Project Settings Alt F Toolchains Path 37 85 3 STVD7 ST7MDT2 EMU2B User Manual From the main menu select Project gt Project Settings Project Settings ST Hiware Toolchain v sample abs Other maker 4 C HIWARESPROG Maker exe Maker exe sample mak Maker exe sample mak C View vob guiistvd src stydebug De You can change your settings here and continue running your application When you exit STVD7 the system will ask you if you want to save these settings in the workspace you have been working in If you choose yes these will become your new workspace settings if you choose no these settings will be lost 38 85 ST7MDT2 EMU2B User Manual 3 STVD7 The Toolchain Path item invokes the following window Toolchain Path Cosmic builder path C COSMIC ST Hiware builder path m ST Assembler path C Program Files STM st toolchain s OK Cancel In this window you can define your builder and or Assembler paths Clicking B opens a browser window 3 10 Saving workspaces Whenever the current workspace is closed it is automatically saved This can happen either when exiting STVD or opening or creating a new workspace In addition to this a workspace can be explicitly saved with the F
21. the Build command is issued and rebuild mak as the make file to use when the Rebuild command is issued 6 After you have finished defining your project settings click Finish Once the workspace is opened the Workspace window displays its contents When you create a new workspace the first time you switch to Debug context see Section 3 11 for an explanation of STVD7 contexts the MCU Configuration window will automatically open to prompt you to choose you target MCU and confirm or modify its option and memory configuration see Section 3 12 on page 42 Opening an existing workspace If you have already created a workspace you simply need to open it in order to load all of your project settings into the STVD7 There are a number of sample workspaces provided with STVD7 that you can open to get familiar with STVD7 These samples are listed in Table 1 on page 30 1 From the main menu select File gt Open Workspace This command opens a window where you can browse to any folder you wish and select an existing workspace Filename Files of type 577 Project Workspace wsp Cancel ST7MDT2 EMU2B User Manual 3 STVD7 2 The Workspace window opens er When a workspace is opened all mywork wsp of the predefined project settings B sample chhiware build mak are loaded into the STVD7 The sample c hiware sample abs Workspace window will show a structured representation of the project
22. the emulated MCU t controls the internal data bus of the emulated microcontroller providing arbitration and tracing capabilities on all accesses to either of the following resources ST7 HDS2 resource ST7MDT2 Active Probe resources Application resources Therefore you can have the emulator running your software in the application as the emulated microcontroller unit MCU would do associated with extensive tracing capabilities keeping a trace of what the MCU did and control capabilities ability to react specifically upon defined conditions In this way it is possible to obtain a full emulation of the microcontroller resources ST7MDT2 EMU2B User Manual 1 Introduction 1 1 1 2 Emulator Configuration Figure 1 shows a general configuration for the ST7MDT2 EMU2B emulator kit The main ST7 HDS2 box is connected to your PC via the parallel port Two flat cables connect the ST7 HDS2 box to the ST7MDT2 Active Probe to which a device adapter can be fixed so that you can connect the emulator to your application board PC Parallel Port y Parallel Cable Figure 1 ST7MDT2 EMU2B General Configuration Emulator Operation A symbolic debugger ST7 Visual Debug also referred to as STVD7 is provided to control the emulator ST7 Visual Debug can be run on a PC under the Windows environment and is common to all ST7 devices ST7 Visual Debug uses a wi
23. the next step you must perform before starting your STVD7 debugging session is to define and configure the target device MCU that you wish to emulate The target device is defined and configured from the MCU Configuration window 1 First ensure that you are in Debug context by clicking on STVD7 has two contexts Debug context and Build context these are described in Section 3 11 The first time you enter into the Debug context after having created a new workspace the MCU Configuration window will be opened automatically 2 Select Tools gt MCU Configuration from the main menu The MCU Configuration window will open ST7MDT2 EMU2B User Manual 3 STVD7 An example of a typical MCU Configuration window is shown in Figure 11 MCU Name field MCU Configuration STZXXNXXX MCU name 5 7 256 16416 1221 Selection auto zoom IV 050000 1050002 PERIPH 00003 00003 RESERVED LVD 5 V OFF _0x0007 050007 RESERVED EXT IT ITO PAZIT 0x000b 0x001f RESERVED 1 00020 00026 PERIPH WATCHD SOFT 00027 040027 RESERVED HALT 040028 0x002e PERIPH Note 0002 040030 RESERVED 00031 0 004f PERIPH 00050 04005 RESERVED 040070 040071 v PERIPH 00072 00077 RESERVED 00080 09013 080140 040171 00180 On Nuk
24. these zones to their original size There are two different actions you may perform on the memory configuration change the type of an entire existing zone define a new zone of any type wherever possible 45 85 3 STVD7 ST7MDT2 EMU2B User Manual To change an existing memory zone 1 Select the memory zone to be modified 2 Click on the Modify button at the bottom of the window A New MCU Memory Range dialog box will open allowing you to change either the address range and or the memory type of the memory zone New MCU memory range From 00080 001 3f Type RAM m PERIPHERALS Cancel To create a new zone of any type 1 Click on the Insert button The New MCU Memory Range dialog box will appear 2 Enter the address range of the new memory zone in the From and To fields 3 Select the type of the new memory zone in the Type field 4 Click OK to validate your choice The new memory zone will then appear in the MCU Configuration window unless you tried to create a new zone in a non modifiable memory space such as Stack or EEPROM To use the Graphic Memory Configuration viewer 1 Inthe memory configuration window click on the zone whose boundaries you wish to move 2 Check the Selection auto zoom box in the upper right hand corner The graphical view of the memory configuration will be scaled so that the zone you have selected is easily visible 3 At the upper and lower boundary of the zone
25. 7 Sample Workspace with Sample Make and or Batch Description of default path files with default path Make Batch File Toolchain realtim realtim wsp realtim tim rtc bat Batch file that forces a recompile ST Macro of application file assembler spimll spimll wsp spiml1 spimll bat Batch file that forces a recompile of application file c cosmic sample wsp c cosmic sample mak Recompiles only if the application file has been resaved Cosmic c cosmic sample bat Forces a recom pile of application file c hiware build mak Recompiles only if the application file has been resaved c hiware sample wsp c hiware rebuild mak Forces recom pile of application file 1 The full default path is C Program Files Stm st7toolchain stvd7 hds sam ple 3 5 1 About application files The user should verify that the options to include debug information were active during creation of the project files Table 2 on page 31 summarizes the way each toolchain functions and lists the different file types source files intermediate files and application files used and produced by the toolchain The application file types and intermediate file types necessary to exploit fully the STVD7 capabilities are listed 30 85 ST7MDT2 EMU2B User Manual 3 STVD7 Table 2 Toolchain steps and their output files Toolchain ST Macroassembler Hiware Cosmic Compile or Assemble Step
26. B HDS2 Emulator both hardware software components has been designed to work with PCs meeting the following requirements One of the following operating systems Microsoft Windows 95 98 or Intel Pentium or compatible processor with minimum speed of 100 MHz Minimum RAM of 32 MB 21 MB of free hard disk space to install all of the ST7 tools Delivery Checklist The emulator unit ref ST7MDT2 EMU2B is delivered with the following refer to Figure 2 1 Oneemulator box containing the ST7 HDS2 main board ref MB176 2 One parallel cable 3 Two 50 wire flat cables to connect the ST7 HDS2 main board to the emulation probe 4 One emulation probe the ST7MDT2 Active Probe ref DB407 A TQFP64 device adapter ref DB389 for connecting the ST7 Active Probe to your application board Used with f below See QFP64 TQFP64 amp QFP44 TQFP44 Footprint Issues on page 67 for additional information on QFP64 TQFP64 issue 6 A QFP64 socket adapter ref DB200 This fits between the TQFP64 device adapter ref DB389 and the QFP64 Yamaichi socket A Yamaichi TQFP64 socket ref 16149 8 A SDIP56 ref DB408 device adapter for connecting the ST7 Active Probe to your application board 9 A SDIP56 to SDIP42 ref DB326 device adapter 10 A TQFP64 device adapter for use in Device Mode ref DB379 plus its User Manual Not shown 11 One User Manual for the ST7 Family Software Developm
27. D7 s debugging features Section 3 4 what a workspace is Section 3 5 what toolchains and application files are supported by STVD7 Section 3 6 how to create a STVD7 workspace Section 3 7 how to open existing workspaces Section 3 8 how to open binary files Section 3 9 how to change your project settings Section 3 10 how to save workspaces Section 3 11 how to switch from the build context to the debug context Section 3 12 how to configure the target MCU in order to debug more accurately and efficiently Installing STVD7 Your emulator comes with the MCU on CD CD ROM which contains a number of ST7 software tools These tools run under the Windows 95 98 and Windows NT operating systems To install and setup the ST7 software tools follow these steps 1 2 Close all other open applications on your Windows desktop Insert the MCU on CD into your CD ROM drive The CD ROM s autorun feature will open up a welcome screen on your PC If the autorun feature does not work use Windows Explorer to browse to the CD ROM s root folder and double click on Welcome exe Select Install Your Development Tools from the list of options A new screen will appear listing the different families of STMicroelectronics MCUs Use your mouse to place the cursor over the ST7 Tools option Choose ST Tools then ST7 Toolchain from the lists that appear The install wizard will be launched Follow the instructions that a
28. D7 for a listing of sample workspaces see Table 1 on page 30 Each workspace is comprised of three information sets the project settings the visual environment and the debugging context The project settings consists of the information necessary for a successful build of an application commands to run makefile file etc Your workspace s project settings include the definition of your application toolchain see Section 3 5 on page 29 The visual environment consists of the open windows elements along with their current layout bookmarks and other features The visual environment is composed of two environments one in the Build context and one in the Debug context see Section 3 11 on page 41 The debugging information includes information on breakpoints memory mapping advanced breakpoints programs trace etc ST7MDT2 EMU2B User Manual 3 STVD7 3 5 Toolchains and application files A quick summary of development toolchains and application file types supported by STVD7 will help you in setting up your workspace Three different development toolchains are currently supported by the STVD7 Each type of toolchain has its own application file types project environment and building tools i e linkers and convertors The ST7 macroassembler toolchain from STMicroelectronics which generates either s19 or hex application files with various intermediate files such as map 1st files The Hiware C o
29. Ds on the front panel of the HDS2 box indicate the state of the development tool during emulation Power Green indicates that the 5 V power supply is ON Yellow indicates that the 517 is running not in RESET and HALT mode System Red not used with this emulator ST7MDT2 EMU2B User Manual 4 Emulator Features 4 7 4 7 1 Reset Red not used with this emulator On Chip Peripherals You can configure certain on chip peripherals in ST7 Visual Debug s MCU Configuration dialog box refer to Creating a workspace on page 32 so that the emulator accurately emulates your target device The on chip peripheral options supported by the emulator are CLOCK The emulator can work with six clock sources Max Frequency 16 MHz Min Frequency 2 MHz 16 MHz internal oscillator 8 MHz internal oscillator 4 MHz internal oscillator 2 MHz internal oscillator Application clock or Probe provided by your oscillator on emulation probe A user provided External Clock input SUB Click located on the ST7MDT2 57 85 4 Emulator Features ST7MDT2 EMU2B User Manual Note 4 7 2 58 85 Active Probe as shown below DB407 board 725 5 208 7 HE10 MALE 50 Pts
30. EMU2B package is a development tool designed for emulation of the following microcontrollers of the MDT2 family ST 72334 ST7MDT2 EMU2B package will assist you in debugging your application hardware as well as your software The ST7MDT2 EMU2B kit comes with a new debugger software package ST7 Visual Debug which contains all of the necessary resources to help you design develop and debug ST7 application software running in a real environment If you come across any terms or abbreviations you do not understand you can check their meaning in the Glossary on page 77 First off check that the ST7 MCU that you have picked for your application is in the list of devices see table above supported by this version of the ST7MDT2 EMU2B emulator The Emulator Package is made up of two main parts The Hardware Development System ST7 HDS2 which is the common mainframe to all ST7 emulators The ST7MDT2 Active Probe dedicated to the family which constitutes the physical link between the emulator and your application 5 85 1 Introduction ST7MDT2 EMU2B User Manual Note 6 85 When receiving the ST7MDT2 EMU2B development tool please refer to the Delivery Checklist on page 11 to confirm that all of the contents of the package are present The emulator performs two main functions It replaces the microcontroller in the application by means of an emulation probe that is plugged into the application in place of
31. For example mywork wsp shows that it uses build mak as the make file and sample abs as the application file Note Although the name of the application file is shown in the Workspace window it has not yet been loaded into the emulation memory see page 36 If you click on the Source Workspace Source Directo Directory tab the window will show every source and intermediate file type c s asm h or o in the selected directory iz xd C Program Files STM st toolchain s samplel c sample2 asm sample3 c start0 h ouble click here rug fr m ru c w Workspace N Source Direct 3 If there are no source files shown in the Source Directory tab of the Workspace window or you wish to list additional files stored in another folder you may browse to them by clicking the Double Click here folder The Add Source 35 85 3 STVD7 ST7MDT2 EMU2B User Manual Directory window pops up allowing you to enter or browse for a new directory and filter out the file types of interest ix xd C Program Files samplel c sample2 asm sample3 c statt07 c start07 h Double click here Add Source Directory Ea Path Ic Program Files STM st7toolchainstvd thds Files filter asm 7 5 inc spp OK Cancel 1 Wor N Sou 4 To lo
32. MCU selected However you can configure the memory settings as you wish if your application requires non default settings This feature would enable you for instance to temporarily increase the ROM size during the development phase of your application OxffeO Oxfff VECTORS Cont Insert Delete Graphic memory configuration fields configuration viewer There are two methods for configuring the memory settings on the MCU by typing in the start and stop addresses of each memory zone into the memory configuration window and by graphically moving the memory zone boundaries in the graphic memory configuration viewer see page 46 for more instruction Memory zone types The left column of the memory configuration window indicates the address range of each memory zone The right column indicates the memory type of each zone Depending on your target MCU the available memory types may be Peripherals RAM ROM Stack System EEPROM Reserved Vectors 44 85 57 ST7MDT2 EMU2B User Manual 3 STVD7 Application Some of these zones can have their type and size modified others cannot be modified Their definitions and properties are explained as follows Peripherals Microcontroller internal or rebuilt peripherals registers Their properties are defined as in the microcontroller user manual This memory cannot be modified RAM Random Access Memory of the microcontroller This memory type
33. S2 SX Emulator Ferrites Probe Side View Application Board Flat Cables Figure 5 Making your Probes EMC Compliant Step 3 Connecting the Probe to your Application Board using Device Adapters Important Notes Concerning ST7MDT2 devices and their packages Emulated devices of the ST7MDT2 family are available in several packages as the following table shows Each package has its own connection procedure found on the page cited in the table below QFP64 ST 72311 R ST 72512 ST 72532 R ST 72314 TQFP64 16 ST 72334 N SDIP56 18 15 85 2 Getting Started ST7MDT2 EMU2B User Manual Note 16 85 ST72314J DIP4 ST 72334 J TQFP44 Probe not provided ST 72124 J See page 63 Note the following constraints The TQFP44 package is not supported by the probe provided in this emulator kit refer to page 63 for more information Special precautions are required if you are using the TQFP64 package Because there is no Yamaichi socket available specifically for the TQFP64 footprint a QFP64 Yamaichi socket is furnished instead there are special footprint precautions to be taken when designing your application board see QFP64 TQFP64 amp QFP44 TQFP44 Footprint Issues on page 67 In addition two TQFP64 device adapters are provided in this emulator kit The first ref DB389 allows you to connect the emulator i e the ST7MDT2 Active Probe to your application board
34. ST7MDT2 EMU2B HDS2 Series Emulator User Manual release 1 2 June 2000 Ay amp Ref DOC ST7MDT2 EMU2B USE IN LIFE SUPPORT DEVICES OR SYSTEMS MUST BE EXPRESSLY AUTHORIZED STMicroelectronics PRODUCTS ARE NOT AUTHORIZED FOR USE AS CRITICAL COMPONENTS IN LIFE SUPPORT DEVICES OR SYSTEMS WITHOUT THE EXPRESS WRITTEN APPROVAL OF STMicroelectronics As used herein 1 Life support devices or systems are those which a are intended for surgical implant into the body or b support or sustain life and whose failure to perform when properly used in accordance with instructions for use provided with the product can be reasonably expected to result in significant injury to the user 2 A critical component is any component of a life support device or system whose failure to perform can reasonably be expected to cause the failure of the life support device or system or to affect its safety or effectiveness Chapter 1 Chapter 2 Chapter 3 Chapter 4 1 1 1 2 1 3 1 4 1 5 1 6 2 1 2 2 2 3 2 4 2 5 2 6 3 1 3 2 3 3 3 4 3 5 3 6 3 7 3 8 3 9 3 10 3 11 3 12 3 13 4 1 4 2 4 3 4 4 4 5 Table of Contents INTKOGUCHION i cer ete oe an 5 Emulator Configuration nee 7 Emulator seele 7 Software and Documentation for the Emulator Kit 8 About this Manual u pH EDI rix ee 8 Related Documentation eed capto gu e uter te qaae
35. ad the application file as well as any intermediate files click the Debug icon or the Reset Chip icon The application and symbols will be loaded Before you can start debugging you must set the target hardware device by configuring the MCU 3 8 Opening binary files If you do not have access to the source or intermediate files generated by a toolchain you may also load s19 and hex files on their own using the Open Workspace command Note The range of debugging features available when you open a binary file only will be very restricted You will only have access to the Disassembly Window 1 Launch STVD7 and select File gt Open Workspace from the main menu 36 85 ST7MDT2 EMU2B User Manual 3 STVD7 2 Browse to the folder where your binary file is stored and select All files in the Files of type field Look in a my work c File name my_project 19 Files of type al files Cancel 3 Select your binary file hex or s19 and click Open The binary code in the 519 or hex file will be loaded into STVD7 and you will be able to access the Disassembly Window A workspace file of the same name as the binary file but with an extension wsp will be created automatically 3 9 Changing your project settings The Project menu contains the Build and Rebuild All commands you need to recompile your application after having made changes to it in the course of debugging You may also access your
36. atures of the ST7 HDS2 Emulator series The features described below are common to all ST7 emulators Real time emulation capability internal frequency from internal 0 5 MHz up to 8 MHz Full memory emulation up to 64 KB Real time trace with 3 event conditions allowing selective recording Hardware breakpoint capability on instruction Fetch Hardware breakpoint capability on address Breakpoint capability on invalid address access Breakpoint capability if trace is full 1K x 32 bit real time trace address data ctrl 6 different modes to configure trace access by combining 3 event conditions Selective trace recording capability 2 Trigger output capability Can use as an external clock source either the on probe oscillator or an external source via the front panel input 4 probe inputs to display application signals in the trace Specific Features The features described below are specific to the ST7MDT2 Active Probe Clock source selection The application power supply follower allows this emulator to run with application Vcc from 3 V to 5 5 V When the probe is not connected to an application board or if the application board isn t powered application Vcc 3 V the default value is 3 V An external LVD management cell is included Emulator Architecture The ST7MDT2 EMU2B emulator is composed of 2 parts The ST7 HDS2 Hardware Development System contains all of the common resources necessary to emulate any ST7
37. be to the ST7 HDS2 board are buffered ST7 Address bus 16 bit of the ST72C171 in emulation mode Data bus 8 bit of the ST72C171 in emulation mode ST7 emulation chip control bus for trace recording breakpoints and memory mapping ST7 ACTIVE PROBE Control Status Clock Source Control PLD Automaton Control Decoder ST7 Emulation Emulation Signals MCU Addresses ST7 Addre Addresses Power Supply Application Follower Device Adapter O Peripherals ST7MDT2 Control ST7MDT2 MCU Adapter Application Board 52 85 ST7MDT2 EMU2B User Manual 4 Emulator Features 4 4 Output Triggers Your ST7 HDS2 emulator has two output triggers OUT1 and OUT2 The OUT1 and OUT2 outlets are available via SUB click connectors located on the front panel of the ST7 HDS2 emulator box OUT1 Trigger output OUT Trigger output 0000 C Analyser ST7 HDS2 Emulator Triggers Probe You can program the output signals to these triggers using ST7 Visual Debug 53 85 4 Emulator Features ST7MDT2 EMU2B User Manual 1 From the main menu in ST7 Visual Debug sel
38. ce Adapter ref DB389 Screw Holes O QFP64 Socket Adapter ref 200 88 2 Y Yamaichi Socket to Solder Application Board Figure 6 TQFP64 MCU Package Connections 2 Place the QFP64 socket adapter ref DB200 upon the socket base aligning pin 1 of the socket adapter with pin 1 on the socket base Pin 1 is indicated by a chamfer on the QFP64 socket adapter and by a little arrow or chamfer on the socket base 3 Now plug the male bars of the TQFP64 device adapter ref DB389 onto the socket adapter i e into the 2 x 8 pin connector located between the two 2 x 12 pin connectors There is only one connection scheme Handle the device adapter and its bars carefully 4 Using four screws fasten the TQFP64 device and socket adapter assembly onto the Yamaichi socket through the holes located on the upper surface of the TQFP64 device adapter 17 85 2 Getting Started ST7MDT2 EMU2B User Manual 5 Once screwed in you can connect the ST7MDT2 Active Probe ref DB407 to the TQFP64 device adapter using the four female connectors on the TQFP64 device adapter and the corresponding male pins on the ST7MDT2 Active Probe The pins numbered 1 on these two boards must correspond W1 connectors on both boards must vertically correspond If you require supplementary sockets their commercial reference numbers are giv
39. ce materials Datasheets for the ST7 MCU family About this Manual Detailed instructions on how to install your emulator configuration is described in Chapter 2 Getting Started on page 11 How to start debugging your application using your emulator and ST7 Visual Debug is described in Chapter 3 STVD7 on page 25 The emulator kits hardware features are described in Chapter 4 Emulator Features on page 49 ST7MDT2 EMU2B User Manual 1 Introduction 1 5 1 6 Related Documentation To get all the essential information about your ST7 MCU and the software that comes on the CD ROM with the emulator kit you will need to refer to these documents also contained on the CD ROM e ST7 Family Data Sheets e ST7 Family 8 bit MCUs Product Overview Ref BKST7 2 e Software Tools for the 517 Family Ref Doc ST7ASMLK SW ST7 Family Programming Manual Getting Assistance For more information application notes FAQs and software updates on all the ST microcontroller families check out the CD ROM or our website http Umcu st com For assistance on all ST microcontroller subjects or if you need help with using your emulator use the contact list provided in Product Support page 79 We ll be glad to help you 9 85 1 Introduction 10 85 ST7MDT2 EMU2B User Manual ST7MDT2 EMU2B User Manual 2 Getting Started 2 1 2 2 GETTING STARTED Your System Requirements The ST7MDT2 EMU2
40. click OK The default paths for each toolchain are shown below OK Cancel If you choose Cancel you will be prompted again to enter the toolchain paths the next time you launch STVD7 You may modify the toolchain path at any time from within STVD7 simply select Project gt Toolchain Paths from the main menu to access the dialog box above ST7MDT2 EMU2B User Manual 3 STVD7 3 3 About STVD7 debugging features A number of advanced features are included in the STVD7 software Data Breakpoints on the occurrence of a memory access via a read operation or a write operation or both Instruction Breakpoints on the occurrence of an opcode fetch A Logical Analyser that allows you to control either the recording of the trace buffer or a break in the execution of the application using a series of specific conditions events A Trace window to view the contents of the trace buffer which permanently records in real time on 32 bits Address and data bus information Flag status and 4 external signal values You can record up to 1024 executed cycles Using trace filtering you can filter out only those cycles you wish to record in the trace buffer You can equally control which of the recorded cycles are displayed in the Trace window using line filtering Addresses data control status bits and 4 user signals are displayed using mnemonic and user symbols Internal synchronization signals can be output to either
41. der a compatible probe from the STMicroelectronics Microcon troller Tools Sales Support see Product Support on page 79 The order number is ST7MDT2 PB TQ44 63 85 Appendix A Troubleshooting ST7MDT2 EMU2B User Manual IF THE FOLLOWING OCCURS QFP64 TQFP64 Incompatibility Recovery solution in case of problems with TQFP64 foot You have already designed your prints application board and it uses true In the event you have TQFP64 footprint so cannot solder already designed your Yamaichi QFP64 socket into place application board before and connect emulator probe receiving this emulator kit and your footprint is a real TQFP64 you will not be able to solder the Yamaichi Socket You can however debug your application by using an Emulation Technology TQFP64 adapter ref EPP 064 QF29D SM We can provide an adapter board ref DB387 see figure above for this component which connects to the ST7MDT2 Active Probe Ask your dealer or ST sales representative for information about availability see Product Support on page 79 You have not yet designed your Resolve QFP TQFP incompatibilities by designing application board but wish to use your application board using a hybrid footprint TQFP64 or TQFP44 compatible seo 4 4 amp QFP44 TQFP44 Footprint Issues footprint on page 67 for more details A 2 Changing the Parallel Port Setup on Your PC Under certain circumstances you may receive th
42. e Cancel Conf Insert Delete Option configuration Memory configuration Graphic memory fields fields configuration viewer Figure 11 MCU Configuration window The options shown in the above example may not be available for your particular target MCU 3 Set the Target MCU In the MCU name field select the target device for which the application is intended from the dropdown box Once a target MCU has been chosen the Option configuration and the Memory configuration fields will show the default values for this device Configure the MCU Options and On Chip Peripherals All of the configurable options on your target hardware device are listed in the Option configuration fields Beside each option a default value is given You may change this value by clicking on it and choosing a new value from the drop down list This allows you to configure your target device s options and on chip peripherals Depending on the MCU selected the default settings in the Option configuration fields will change It is up to you to configure those options that will impact your application so that the emulator accurately emulates your target device 43 85 3 STVD7 ST7MDT2 EMU2B User Manual Note For more information about the configurable options available on your target hardware device please consult your target MCU s datasheet 5 Configuring the MCU Memory The default memory settings depend on the
43. e connectors parts numbers CCAX00168 2 cable length 2 ft with SMB plug to BNC plug CCAX00168 3 cable length 3 ft with SMB to BNC plug 81 85 Product Support 82 85 ST7MDT2 EMU2B User Manual Index A Active Probe architect re iin ich edis 51 hardware er 51 analyser probe signals 55 C clock selecting 57 selecting 57 Glock Probe 61 configuration analyer probe input signals 55 output 53 connections emulator power supply 19 emulator to 13 probe to 14 SDIP42 18 SDIP56 18 enel 20 Device PINS 22 documentation 9 definition 0 er 77 compliance eee 15 emulator kit configuration 7 delivery checklist sess 11 functional limitations discrepancies 59 installing software for 25 main functions of 6 operation of
44. e following error message Connection Error LPT1 LPT2 Interconnection failure Verify your input output cable This may mean that the setup of the LPT1 or LPT2 port on your PC is not compatible with the ST7MDT2 EMU2B emulator To set up the port correctly 1 Shutdown and restart your PC in order to enter the BIOS setup 2 Follow the messages displayed on the screen and when prompted press the key required to enter the BIOS setup usually a function key or the ESC key 3 Select the parallel ports menu This may be listed under ports 64 85 ST7MDT2 EMU2B User Manual Appendix A Troubleshooting A 3 Caution 4 Change the Mode of the LPT port that you have connected the development board to i e either LPT1 or LPT2 to one of the following compatible modes according to the following table Operating System Compatible Parallel Port Modes Windows 95 ECP EPP Bidirectional or Centronics Windows 98 EPP Bidirectional or Centronics Windows NT4 ECP EPP Bidirectional or Centronics 5 Save your changes and exit the BIOS setup Running the Hardware Test The Hardware Test in the STVD7 for HDS2 lets you check that your emulator is correctly connected configured and working You can test components of the development board individually or all at the same time If problems occur during debugging such as bad debugger responses and unexpected behavior you should check for hardware problems using the
45. e upper face of the ST7MDT2 Active Probe 22 85 ST7MDT2 EMU2B User Manual 2 Getting Started These pins are numbered as they appear on the TQFP64 devices user datasheets The physical location of these connectors is shown in Figure 9 rer m DB407 BOARD HE10 MALE 50 Pts HE10 MALE 50 Pts EMI 256SRLZOB 7 cos Eis 64 Figure 9 Pin Connector Location The pin number diagrams on page 74 shows the correspondence between the 64 pin connectors and their corresponding real pin number in SDIP56 SDIP42 and TQFP44 You can photocopy these diagrams on a cardboard sheet cut along the dashed edges and place them on the top of the ST7MDT2 Active Probe You will then find the correct pin numbering for the package 23 85 2 Getting Started 24 85 ST7MDT2 EMU2B User Manual ST7MDT2 EMU2B User Manual 3 STVD7 3 1 STVD7 STVD7 is an integrated development environment that allows you to edit debug and rebuild your application all from within STVD7 The following sections tell you Section 3 1 how to install the STVD7 software Section 3 2 how to launch STVD7 Section 3 3 a little about STV
46. ect View gt Hardware Events The Hardware Events window will open in your workspace Enabled Hardware Disabled Hardware Event Event Er mig omm 700677 090002 e pem New Hardware E vent Enable Disable Selected Hardware E vent Enable Disable All Hardware E vents Remove Selected Hardware E vent Remove All Hardware E vents v Allow Docking Hide Float In Main Window 2 Right click the mouse while the mouse pointer is anywhere in the Hardware Events window 3 Choose New Hardware Event the contextual menu The Hardware event settings dialog box will open as below Hardware events setting our v Enabled From 0 0000 C Whole variable Cancel 54 85 ST7MDT2 EMU2B User Manual 4 Emulator Features 4 5 4 Choose the trigger output that you wish the signal to be sent to i e OUT1 or OUT2 and check the Enabled box 5 You may trigger output signals by setting an event on any of the following whole variable creating an event for synchronization which enables you to preset the pulse synchronization for external equipment connected to the output trigger asingle address also creates an event for synchronization see above arange of addresses creating an event to measure time which enables you to measure the time elapsed during a subroutine execution A positive impulse is emitted on OUT1 and OUT2 when a specific condition is met This impulse la
47. efer to Contact List on page 79 using the following order number ST7MDT2 PB TQ44 mm inches 8565526 8 foss ozs ns ponen Pe rer em 55 Es rss o vos sro os Le urs uso e je NumberoPims 44 4x11 SK Plastic socket overall dimensions Figure 13 TQFP44 Device and Emulation Probe Compatible Footprint 68 85 ST7MDT2 EMU2B User Manual Appendix B Hardware Schematics APPENDIX B HARDWARE SCHEMATICS B 1 Component layouts rar 26 C14 S9B IH4Z 517251 1 9 R 2 Ub pan n n to 25 9S BH 99 29 nN o JSEGSS 78 19 N o lt N w N L N 00500000005 19195 C i3 58 13619819 g 144 13454 19491 15457 a a ESH n 199722 413394 Figure 14 ST7MDT2 Active Probe ref DB407 Components Layout 69 85 Appendix B Hardware Schematics ST7MDT2 EMU2B User Manual 470000 4810000 OO SERIAL NUMBER U1 ADQFP64 Ul GJ OOOOOOOON OOOOOOOOu B5loooooooooooo 35 000000000000 373 00000000129 9 00000000 24 31000000000000 000000000000
48. en below Yamaichi socket WITH positioning pins QFP TQFP 64 1 149 064 108 5 Yamaichi socket WITHOUT positioning pins QFP TQFP 64 1 149 064 008 5 Note Once your code is debugged you may want to program some devices and test them in your application without the emulator Another TQFP64 Device Adapter ref DB379 is included in the emulator kit to allow you to connect an actual MCU to your application without removing the Yamaichi socket Refer to Using the TQFP64 Device Adapter Ref DB379 on page 20 B If you are using the SDIP56 or SDIP42 MCU package use this procedure Note A SDIP56 device adapter and a SDIP56 to SDIP42 adapter are provided in the emulator package Before going through the procedure make sure that the package you were delivered includes these items To connect the ST7MDT2 Active Probe to its SDIP56 or SDIP42 adapter and then to your application follow these steps see Figure 7 1 Solder a SDIP56 or a SDIP42 pin socket onto your PCB 2 Plug the SDIP56 adapter ref DB408 into the ST7MDT2 Active Probe ref DB407 Find the W1 connector on both boards They must correspond vertically 3 This step is for the SDIP42 adapter ONLY Plug the SDIP56 to SDIP42 adapter ref DB326 onto the SDIP56 pin socket of the SDIP56 adapter Pins 1 of both must correspond Refer to Hardware Schematics on page 69 to find the layout of the adapter 18 85 ST7MDT2 EMU2B User Manual 2 Getting Started 4 Now
49. ent Tools assembler linker and formatter Not shown 12 This manual Not shown 11 85 2 Getting Started ST7MDT2 EMU2B User Manual 2 3 12 85 13 A CD ROM containing ST7 information and software including ST7 Visual Debug and a Windows Epromer Not shown nee Figure 2 Main Components of ST7MDT2 EMU2B Emulator Kit Installing the Hardware The ST7 HDS2 emulator is connected through the parallel port to a PC computer which runs the control software ST7 Visual Debug as explained later To connect your ST7 HDS2 emulator you will have to follow these general steps 1 Connect the ST7 HDS2 to your PC using the parallel cable provided 2 Connect the two flat cables of your ST7 HDS2 emulator to the emulation probe connectors 3 Connect the emulation probe on your application to the appropriate socket adapter 4 Connect the power supply cable between the power supply block and the power connector located on the rear panel of your ST7 HDS2 emulator 5 Power up the emulator and then connect your application power supply ST7MDT2 EMU2B User Manual 2 Getting Started A connection flow diagram is shown hereafter Step details are discussed in the following sections PC Parallel Port 1 Parallel Cable E Power Supply Application Board Power Supply Application Board Step 1 Connecting the Emulator to y
50. er Probe Input Signals uuurssssssnsssnnnnnnnnnnunnnonnnnnnnnnnnn nenn 55 3 85 Table of Contents 4 6 Front Panel LEDS nn do ee eap ete 56 4 7 On Chip Peripherals u 57 4 8 Emulation Functional Limitations and Discrepancies 59 Appendix A Troubleshooting 63 A 1 Identifying the Problem u el ee 63 A 2 Changing the Parallel Port Setup on Your 64 A 3 Running the Hardware Test iis eie rts ee foco a 65 A 4 QFP64 TQFP64 amp QFP44 TQFP44 Footprint Issues 67 Appendix B Hardware Schematics 69 B 1 COM PONS Mu fol ic 69 B 2 Device adapter pin matching diagrams 74 Appendix C Glossary bee RAREMENT E E EE 77 PIOGUCLSUDDOR a esos 79 Getting prepared before you 79 Go tact 79 Software updates e 3 o RE br REM in hepa M e ftp a t 80 Hatdware Spare PANS See en RER 80 Index sos epos PRA Meee YE QUERI EX SOME E RIP RUE Ro VETUS E R BIN N 83 4 85 ST7MDT2 EMU2B User Manual 1 Introduction Note INTRODUCTION Thanks for choosing ST7 This manual will help you get started with the ST7MDT2 EMU2B ST7MDT2
51. eset euren 9 Getting ASSISTANG MERE Haare ee 9 Getting Started 2229 zn re ea 11 Your System Requirements aaa 11 Delivery Checklist scooter a 11 Installing the Hardware nn ae need 12 Debuggers Supporting the ST7 HDS2 emulator 20 Using the TQFP64 Device Adapter Ref DB379 20 Accessing Device PINS ertt E RU 22 25 cios 25 launching STVD7 Seen 26 About STVD7 debugging features 27 ANOIKSDHOOS oca MIEL E 28 Toolchains and application files 29 Creating workspace eere trier erre a ex ee 32 Opening an existing workspace 34 Opening binary files u see e d ek eae eO TREE ences 36 Changing your project settings 37 Saving workspaces a een 39 Debug context and Build context a ee 41 Config ring the MGU terrane anie oeni aia E ata Su R 42 91 uo dei See mee 47 Emulator Features i sad a 49 Main Features of the ST7 HDS2 Emulator series 49 Specific Features zei ee bred c m ee 49 Em lat r Archileel re sr een AE 49 Quiput IrIgdels En 53 Analys
52. flag are available Non Maskable Interrupt Management A non maskable interrupt pin is present on this MDT2 family ST72511 and derivative devices To be considered by the emulator your application has to be supplied The emulator will consider that the application is supplied only if its voltage is superior to about 2 5 V Nested Concurrent Interrupts Buttons Two modes of interrupt management are possible on this MDT2 family devices Nested or Concurrent Nested is dedicated to ST72511R ST72311R ST72512R ST72532R devices Concurrent mode is dedicated to ST72334J N ST72314J N and ST72124J devices See the user datasheets for a detailed explanation of these two modes As a result the CCR register does not have the same bits meaning In the STVD7 debugger you can choose the aspect of the CCR register by selecting View gt ST7 Registers from the main menu A window is ky ST7MDT2 EMU2B User Manual 4 Emulator Features displayed where you can toggle between the two displaying modes Nested IT or Concurrent IT 4 8 6 Clock Probe This clock source is not available on the ST7MDT2 EMU2B emulator 61 85 4 Emulator Features 62 85 ST7MDT2 EMU2B User Manual ST7MDT2 EMU2B User Manual Appendix A Troubleshooting APPENDIX A TROUBLESHOOTING A 1 Identifying the Problem IF THE FOLLOWING OCCURS Error Message when starting the Ensure that STVD7 for HDS Emulator No message received from emula tor
53. he range of 3 V to 5 5 V For more information refer to Emulation Functional Limitations and Discrepancies on page 59 Debuggers Supporting the ST7 HDS2 emulator The debuggers currently supporting the ST7 HDS2 emulator are ST7 Visual Debug also known as STVD7 by STMicroelectronics e Hilight for ST7 HIWARE e HI WAVE for ST7 HIWARE Zap for ST7 COSMIC ST7 Visual Debug is free software It is available on the STMicroelectronics website See Product Support on page 79 for more information Using the TQFP64 Device Adapter Ref DB379 Once your code is debugged you may want to program some devices and test them in your application without the emulator This mode is called Device Mode However because the Yamaichi socket furnished is a QFP64 type you will not be able to insert a TQFP64 device and ensure perfect contact For this reason this emulator kit includes a TQFP64 device adapter ref DB379 which can be connected onto the QFP64 socket adapter ref DB200 upper face connectors as follows 1 Remove the ST7MDT2 Active Probe ref DB407 and its device adapter ref DB389 and replace them by the TQFP64 device adapter ref DB379 ST7MDT2 EMU2B User Manual 2 Getting Started Note 2 On the upper face of this adapter you will find low insertion socket for your programmable device On the upper face of this adapter you will also find 64 numbered pins to access the device pins vo
54. ia Italy Japan Malaysia Malta Morocco Singapore Spain Sweden Switzerland United Kingdom U S A Mouser Electronics Authorized Distributor Click to View Pricing Inventory Delivery amp Lifecycle Information STMicroelectronics ST7MDT2 PB TQ44
55. iews to that which was current when STVD7 was closed The toolbar layout plus customized toolbar content is also saved and restored with the workspace options set via the tabs entitled Toolbars and Commands By default i e when saved automatically the workspace is saved as file lt application gt wsp The name of the file corresponds to the name used for the executable file for example lt application gt abs for a Hiware application file 40 85 ST7MDT2 EMU2B User Manual 3 STVD7 Note 3 11 3 11 1 3 11 2 Using the Configuration Setup dialog box available from the MCU Configuration dialog box you can also control what type of MCU configuration information is restored from a workspace file wsp Debug context and Build context There are two STVD7 contexts the build context and the debug context Until now in creating a workspace and defining your project settings you have been in the build context To proceed step configuring your MCU you need to change to the debug context Briefly the two contexts are different in that In the build context you can open and close workspaces and build or re build the application executable file n the debug context you set the emulated MCU configuration this step is described in Section 3 12 on page 42 and debug the executable file created while in the build context Build Context The build context is the context set when starting STVD7 In thi
56. ile gt Save Workspace or File gt Save Workspace as commands The user is given the choice of which of the workspace elements to include in the saved file Either the visual environment or the debugging information may be saved alone or both may be saved together This is configured as follows 1 From the main menu select Tools gt Options 2 In the Options window that opens see Figure 10 on page 40 select the Workspace tab 3 Choose whether you wish your saved workspace to include either the visual environment or the debugging information or both 39 85 3 STVD7 ST7MDT2 EMU2B User Manual 4 Select which windows will appear docked when a project is opened by checking the appropriate check boxes in the Floating windows in the main frame area Only windows currently docked in the main window can be included Options Toolbars Commands Edit Debug Workspace Floating windows in the main frame Workspace includes V Output Visual environment Disassembly Memory Instruction Breakpoints Watch Call Stack Local Variables ST Data Breakpoints ST Registers ST Peripheral Registers Debugging context Cancel Figure 10 Options window 1 Click Apply to confirm your settings 2 Click OK close the dialog box In addition open file contexts and current window positions are saved when the workspace is closed This feature restores the workspace window window layout and file v
57. ltage These pins are numbered as they appear on the devices user datasheets If your have already designed your application board with a real i e non hybrid TQFP64 footprint see QFP64 TQFP64 Incompatibility on page 64 Figure 8 provides a summary of the different hardware configurations depending on your application board QFP64 TQFP64 footprint On the left are the configurations used when you designed your application board with the compatible footprint On the right are the configurations when you used the TQFP64 device footprint incompatible with our emulation socket 21 85 2 Getting Started ST7MDT2 EMU2B User Manual Note If you plan to use epoxy devices such as EQFP64 please contact STMicroelectronics Microcontroller Development Tools Sales Support COMPATIBLE FOOTPRINT REAL TQFP64 FOOTPRINT EMULATION MODE E T Adapter n ae 64 Yamaichi socket C149 Application Board 4 QFP64 device amp E T socket DB379 Mid Base Board Device DEVICE MODE Probo Y tur nt 64 Yamaichi socket IC149 Application Board Application Board _ __ lt Parts provided by ST Microelectronics in the emulator package Figure 8 Hardware Configurations for QFP64 TQFP64 Footprints 2 6 Accessing Device Pins In the event you wish to access the device pins to for example monitor pin voltage once your debugging bench is set you will find a 64 pin connector made up of 4 connectors on th
58. ndow menu driven interface and enables you to configure the emulator 7 85 1 Introduction ST7MDT2 EMU2B User Manual 1 3 1 4 8 85 Chapter 3 STVD7 on page 25 explains how to install ST7 Visual Debug on your PC and set up the emulator configuration so that you can begin your debugging session Once assembled and linked the application software is ready to be downloaded into the ST7 emulator The development station performs a real time emulation of the target device thus allowing high performance testing and debugging of both application hardware and software When the program is fully debugged the ST7 EPROM programming board ref ST7MDT2 EPB2 not provided with this emulator kit can be used to program the emulation device with the Motorola S Record format file produced by the OBSEND formatter Software and Documentation for the Emulator Kit The MCU on CD CD ROM contains _ST7 Tools comprising the following software The source level graphic debugger ST7 Visual Debug that operates with ST7 HDS2 Emulators and ST7 Development Kits or as a standalone ST7 simulator The ST7 Assembly chain composed of an assembler linker librarian and formatter The ST7 Windows Epromer to program your MCU target devices Third party C compiler and toolchain demos Hiware and Cosmic ST7 application notes with sources training slides and exercises this manual in PDF version and other useful referen
59. our PC 1 Shutdown and power off the PC that is to be connected to the emulator 13 85 2 Getting Started ST7MDT2 EMU2B User Manual 2 Connect one end of the parallel cable to the emulator s rear panel 25 pin SUB D connector and the other end to one of the PC s parallel ports LPT1 to LPT2 refer to Figure 3 to LPT1 or LPT2 fi rear panel y A O SUBD25 connector Figure 3 Connecting the Emulator to the PC Step 2 Connecting the HDS2 and the probe 1 Ensure that the application and the emulator are powered off 2 Plug the two 50 wire flat cables into J1 and J2 as described below ST7 HDS2 Emulator ST7MDT2 Active Probe ref MB176 ref DB407 Upper cable Lower cable Upper Cable J2 Connector Lower Cable ST7 HDS2 Emulator Side View J1 Connector Figure 4 Connecting the Emulator to the ST7 Active Probe 14 85 ST7MDT2 EMU2B User Manual 2 Getting Started 3 EMC Compliant Probes In order to work under an EMC compliant environment you will have to clip one or two EMC ferrite on each 50 wire flat cable linking the probe to the emulator box Place these ferrites as close to the emulator window as possible Four ferrites are provided in the package See Figure 5 for an illustration of where to attach the ferrites ST7 HD
60. ppear on the screen 25 85 3 STVD7 Note 3 2 Note 26 85 ST7MDT2 EMU2B User Manual You can choose to install the complete toolchain i e the appropriate version of STVD7 the Windows Epromer and the Assembler Linker for each type of development tool Development Kit HDS2 or EMU3 emulators or simulator or perform a customized installation If you choose a customized installation you can choose to install any or all of the STVD7 versions and or the Windows Epromer and or the Assembler Linker As a minimum in order to use your emulator you must install STVD7 for HDS2 If you also install the ST7 Assembly Toolchain you will be able to use the ST7 Assembly Toolchain as part of STVD7 s integrated development environment The installation is now complete You will be prompted to reboot your computer You should do so before launching STVD7 Launching STVD7 1 From your Windows desktop select Start gt Programs gt ST7 Tool Chain gt Development Tools gt STVD7 HDS2 emulator The first time you open a version of STVD7 you will be prompted to enter the toolchain paths to be used Cosmic builder path by STVD 7 s integrated C COSMIC ST zl development environment Toolchain Path Hiware builder path E h hs f h nter the paths for the C HIWARESPROG e toolchains that you use i e any or all of the Hiware ST7 Assembler path Cosmic or ST7 ASM C Program Files STM st7toolchain s toolchains and
61. r Assembler toolchain which generates abs application files with various intermediate files such as o or dbg files The Cosmic C or Assembler toolchain which generates e1f application files with various intermediate files such as o or st files When you set up a workspace you will need to define the following project settings The toolchain to be used Hiware Cosmic or ST7 macroassembler The executable application file abs elf s19 or hex depending on toolchain refer to Table 2 on page 31 The maker program for the toolchain The maker program can be a part of the toolchain software such as Hiware s maker exe or you can choose to use a generic maker such as Nmake exe or Gmake exe which is provided with the STVD7 The maker batch file mak or bat This is a file which you create for each application which spawns the compilation and or link step each time you wish to build or rebuild In it you define the conditions for recompiling re linking or both Default mak or bat files are often included with the toolchains for example maker mak is included with the Hiware toolchain and simply recompiles your application if it detects that the file has been saved since the start of your debugging session The STVD7 software includes sample mak and or bat files for each toolchain these are listed in Table 1 29 85 3 STVD7 ST7MDT2 EMU2B User Manual Table 1 Sample files included with STVD
62. r ST72334 devices and derivatives 3 LVD values and fixed to 4 05 V for ST72511 and ST72311 derivative A LVD reset will be generated each time the following three conditions are met The LVD STATUS is ON The program is running The application voltage has fallen under the LVD VALUE and the application is considered as supplied The emulator will consider that the application is supplied only if its voltage is superior to about 2 5V A non supplied application or a non connected application will not trigger a permanent reset 59 85 4 Emulator Features ST7MDT2 EMU2B User Manual 4 8 3 4 8 4 4 8 5 60 85 To indicate that your application voltage is under the LVD VALUE when LVD is ON a LED located on the board as indicated on the figure will light up DB407 board EPM 2555RC208 7 CROSS Module discrepancy The Clock Reset Option and Supply Smart module is not exactly the same as in the emulated devices For ST72334 the clock security system is not emulated This means in particular that On Clock Reset and supply register CSSIE and CSSD bits are set to 0 and are not able to be set Only LVD reset flag and Watchdog reset
63. s context it is not necessary to be connected to an emulator and the debug commands are not available You can also edit the source files of an application and perform the use the Build command to perform compile and link actions in an interactive and iterative way to re build the application executable file Debug Context In this context the following debug actions can be carried out Loading running and stopping the application Defining the MCU configuration MCU options and memory mapping e Viewing source and disassembled code Setting instruction breakpoints with a counter and or condition Setting data breakpoints Viewing local variables memory and ST7 registers Viewing history of execution from the trace buffer or with the Call Stack feature analyzing the performance of a piece of code 41 85 3 STVD7 3 11 3 3 12 Note 42 85 ST7MDT2 EMU2B User Manual Switching between contexts The switch between contexts usually occurs when the Start Debugging and Stop Debugging commands are used 9 From the main menu choose Debug Start Debugging or Stop Debugging or click on the Start Debugging or Stop Debugging icons shown at right While debugging the editor allows source files to be T modified To switch to the Build context perform either a Build or Rebuild action or use the Stop Debugging command Stop Debugging Configuring the MCU After you create or open a workspace
64. s is the printed circuit board onto which you wish to connect the target ST7 MCU It should include a socket or footprint so that you can connect the application board to your emulator or development kit using the probe and the appropriate device adapter This allows you to emulate the behavior of the ST7 MCU in a real application in order to debug your application program Device Adapter Device adapters are included in your emulator kit to allow you to connect the emulator to your application board The type of device adapter depends on the target device s packaging Many MCUs come in more than one different package and you should therefore use the device adapter that corresponds to the type of package you have chosen for your application DIL Dual In Line Designates a type of device package with two rows of pins for thru hole mounting Sometimes also called DIP Dual In line Package ECP Extended capabilities port communication standard EPP Enhanced parallel port communication standard Footprint Designates the dimensions of the location of a component on a printed circuit board or in a socket It depends on the number of pins their size type and positioning The footprint of each ST7 device is specified in the datasheet in the section titled Package Mechanical Data MCU Microcontroller Unit Otherwise referred to as the target device throughout this manual This is the core product or family of products for which
65. st OK Logical analyser request check On Going 66 85 ST7MDT2 EMU2B User Manual Appendix A Troubleshooting A 4 QFP64 TQFP64 amp QFP44 TQFP44 Footprint Issues Some of the emulated devices have a TQFP footprint and require you to solder a Yamaichi socket onto your application board However be aware that you may encounter problems owing to the fact that the Yamaichi sockets used to connect the TQFP64 device adapter require footprints that are not compatible with TQFP copper traces For this reason when designing your board plan to have a double trace compatible with both Yamaichi sockets and TQFP copper traces Specifications for compatible footprints are provided below If you use compatible footprints a single printed circuit board design will serve for both the development stage and the final product When you are finished the development stage you can simply replace the development Yamaichi socket by the programmable target device in an actual TQFP64 or TQFP44 package 64 4x16 0000 SK Plastic socket overall dimensions Figure 12 TQFP64 Device and Emulation Probe Compatible Footprint 67 85 Appendix A Troubleshooting ST7MDT2 EMU2B User Manual Note Remember that TQFP44 probes are not provided in this emulator kit If you want to use one you must order it from STMicroelectronics Microcontroller Development Tools Sales Support r
66. sts for one Clock cycle Analyser Probe Input Signals The ST7 HDS2 allows you to use 4 external input signals TTL level These signals are on pins 6 7 8 9 of the Analyser Probe connector located on the front panel of the emulator as shown below L3 12 11 ALO You can view these probe inputs using ST7 Visual Debug From the main menu select View gt Trace The input signal values are listed under the Sig column AL3 0 ST7 Visual Debug s Logical Analyser allows you to use these input signals to define trace filtering or output trigger events From the main menu select Tools gt Logical Analyser to open the dialog box A full description of how to use 55 85 4 Emulator Features ST7MDT2 EMU2B User Manual 4 6 56 85 this facility to control trace recording or trigger output signals is given in the ST7 Visual Debug online help A rainbow colored cable will also be delivered to connect your application to these inlets Each red connector is to be connected to your signal Each black connector is to be connected to the reference ground for the signal Colors are attributed as follows ALO is to be taken between the RED signal and BROWN ground wires e 1 is to be taken between the YELLOW signal and ORANGE ground wires e AL2isto be taken between the BLUE signal and GREEN ground wires AL3is to be taken between the GREY signal and PURPLE ground wires Front Panel LEDs Four LE
67. the Development Kit is designed to act as an emulator and programming tool In general terms an MCU is a complete computer system including a CPU memory a clock oscillator and I O on a single integrated circuit 77 85 Appendix C Glossary ST7MDT2 EMU2B User Manual ST7MDT2 Active Probe A printed card having connector pins that allow you to connect the Emulator to the MCU socket of the user application board Using the active probe allows the HDS2 emulator to function as if it were the target device embedded in your application The probe is connected to the emulator by two flat cables PC Program Counter The program counter is the CPU register that holds the address of the next instruction or operand that the CPU will use RC network Resistor capacitor network SDIP Serial Dual In line Package SO Small outline Designates a type of device package with two rows of pins for SMD or socket mounting ST7 Visual Debug STVD7 A graphic debugger software package that allows you to debug applications destined for the ST7 family of MCUs either using a built in simulator function a Development Kit or an HDS2 Emulator Target Device This is the ST7 device that you wish to use in your application and which the development kit will emulate for you User Application Board Designates your application board 78 85 ST7MDT2 EMU2B User Manual Product Support PRODUCT SUPPORT If you experience any problems
68. with this product or if you need spare parts or repair contact the distributor or ST sales office where you purchased the product Getting prepared before you call Collect the following information about the product before contacting ST or your distributor 1 Name of the company where you purchased the emulator kit 2 Date of purchase 3 Order Code Refer to the side of your emulator kit box The order code will depend on the region for which it was ordered i e the UK Continental Europe or the USA 4 Serial Number The serial number is located on the rear panel of the emulator box 5 Target Device The sales type of the ST7 microcontroller you are using in your development Contact List Note For American and Canadian customers seeking technical support the US Canada is split in 3 territories According to your area contact the following sales office and ask to be transferred to an 8 bit microcontroller Field Applications Engineer FAE Canada and East Coast STMicroelectronics Lexington Corporate Center 10 Maguire Road Building 1 3rd floor Lexington MA 02421 Phone 781 402 2650 Mid West STMicroelectronics 1300 East Woodfield Road Suite 410 Schaumburg IL 60173 Phone 847 517 1890 79 85 Product Support ST7MDT2 EMU2B User Manual West coast STMicroelectronics Inc 30101 Agoura Court Suite 118 Agoura Hills CA 91301 Phone 818 865 6850 Europe France 33 1 47407575 Germany 49 89

ST7MDT2-EMU2B HDS2 Series Emulator User Manual

Contents

Download Pdf Manuals

Related Search

Related Contents