Home

Multi Target Development Tool

1. cccseccsseeeeeeeeeeeeeeeseeeeeeeeeeeeeeeeneneeees 225 15 9 CTM4 CTM6 Module Windows ccsccsseeseeeseceeeeeeeseeseenssensseneseeeenees 225 CTM4 CTM6 Bus Interface and Clocks Window cccseessseeeeeeeeseeeeeseneeee 225 CTM4 CTM6 Free Running Counter Submodule Window cceeeesseeeee 226 CTM4 CTM6 Modulus Counter Submodule WiNdOW s ccssseeetsereeeeereeee 226 CTM4 Double Action Subm odule Window c ccescesseeeeeeeseeeeeeeeeeeeeeeeneeeeees 227 CTM4 Pulse Width Modulation Window css ccssceesseeeseeeeseeeeeeseeeeseeeseneeeeees 227 CTM6 Single Action Subm Odule Window cssssseessenseeseeseeseeeeeeeneereneseeeeeee 228 CTM6 Double Action Subm odule Modes Window ssssssseeesereeeeeereeee 228 CTM6 Double Action Submodule Bits WiNdOW c sesseeerseeeeeseereeneeeereeee 229 15 10 QADC Module Window cccccscceseceseceeeeeeeseeeseeeseeeceeeseeeeeeseeeseessneseee 229 QADC Main Window cccscccceeeceeeeeeeseeeeeeeeneneeeeeeeeseeeensneeeseneeneneensneeeseeeeeeeeeesneeeeees 230 QADE Ports Wit OW 5 ssi0escccscssisesenceesensensenssuceessacecuneseesseteiuessensessosseinecersntensunderntedesdee 231 QADC Channel Window ccseccceeeeeeeeeeeeeeenseeeeeeeeeeeeeensneesseeeeeeneeesneeeeeeeeseneeeeneeeeees 232 15 11 Miscellaneous Module Windows cccccsssceeeceeeceeeseeeseeeeeeeseeeseesseeneee 233 TOUCAN Main Window 2
2. cccceeeeeceeeeeeeeeeeeeeeeeeeeeeeeeseeeeeeeeseeeeeeeeeneeeees 138 Using the d define Option and Escape Characters sssssssessesseseerseees 141 Multi Target Development Tool page 5 Multi Target Development Tool 9 7 File Location Considerations cccccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeseeeeees 142 9 8 Test Termimati om 2cccccceieccccstescteenieeteesteccnencidecnenstedenecnaeeseenduedeneeuavecnenctiee 142 9 9 Cumulative Logged Regression Testing sececceeeeeeeeeeeeeeeeeeeeeeeeeeeeees 143 9 10 Regression Test Example cccsecececeeeeeeeeeeeeeeeeeeseeeeeeeseeeeeeeseeeeeeeseeeeeees 144 Part 10 Action Tags 147 10 1 Print Acton Tag eege ee ENEE 148 10 2 Timer Action Commands cccccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeseenenees 149 10 3 Write Value Action Tag ccceeeececeeeeeeeeeeeeeeeeeeeeeseeeeeeeeeseeeeeeeeseeeeeeeseneeees 150 Part 11 External Circuitry 151 11 1 Logic Simulation ic occ NENNEEAENNEKEEER ENEE ENEE EeEEER ENEE cnancude eewnoedevecctese 151 Part 12 Integrated Timers 155 Part 13 Workshops 157 Part 14 The Logic Analyzer 159 14 1 Executing to a Precise Time ccceceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeneeeeseeeeeees 160 14 2 Waveform Selection ccccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeseeeeeeneeeseeeeeeeeeeeeees 161 14 3 The Active Waveform ccccceeeeeeeeeeeeeeeeeeeeeeeeeeneeeeeeenseeeeeeeeeeseeeeeeesenenees 162 14 4 Left an
3. cs cccsseesseeeeseeeeeseeesseeeeseeeeesenenseeees 204 TPU Scheduler Window ccs ccsseeceseeeeeeeeeseeeeeseeeesnenenseeeeseeeenneeensaeeeseeeeneeeensaeens 205 TPU Micro Sequencer Registers WindOw sssssssesensseeseeseeeeeesseeeseeseeeesenees 205 TPU Execution Unit WING OW 2 cseccceecceeeeeeeseeeeeeeeeeneeenseeeeseeeenneeenseeeesneeeneeeensaeees 207 TPU Chane WING E 208 TPU Parameter RAM Window c cccsseesseeeeseeeeeneeenseeeeseeeeneeenseeeeseeeeneeeensaeees 210 15 4 CPU32 Specific WiMdOWS cccccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeneeeees 211 CPU32 Simulator Configuration WiINGOW sssscsensseeeeeeseerseeseeenseeseneeeeeseneneee 211 CPU32 Simulator BUSSES Window 2 ccceecceeeeeeeeeeeeeeeeeeeeeeeeeeeneneeeseeeeeseeeesneneeee 212 CPU32 Simulator Interrupt WiINdOW snnnnsnsnnnnsnnnnnnnnnnnnnnnnennnnnnnnnnnnnnnnnnnnnnnnnnnnnnnenn nne 212 BDM32 Configuration Window csssssseesersseeesessenerseeseeeseaeeeeeseeeseeeseeeseeeneenseees 213 CPU32 Register Window csssccsseeeseeeeseeeeeseeeeneeeeneeeseseeeeneeeesneeseseeeeneneesseeeeses 214 CPU32 Disassembly Dump Window ccetcseseeseeseeseeseeseeseneeseseeseeseneenennennenes 214 15 5 SIM Module Windows snsssasnnsnnsnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn nnmnnn nnmnnn nnmnnn 214 SIM Main Window wee 215 SIM Ports Window Seen a 216 SIM Chip Selects Window snnnnnnsnnnnnn
4. Disables listing of hexadecimal dump addressing mode and symbol data in dis assembly files NO_HEX NO_ADDR_MODE NO_SYMBOLS Adds a pragma format val to each dis assembly line This is helpful for non deterministic assembly languages to cause the assembler to generate a deterministic opcode YES_PRAGMA Adds a blank line between assembly lines Handy for finding opcode boundaries in parallel instr sets such as eTPU where a single opcode s dis assembly can span multiple lines YES_BLANK_LINES Selects the endian ordering for image and C data structure files ENDIAN MSp LSB ENDIAN_LSB MSp Selects data size in image and C data structure files DATA8 DATA16 DATA32 Selects decimal data instead of hexadecimal for C data structure files OUT_DEC Append to file if it already exists default is to overwrite any existing file C 1994 2015 ASH WARE D Target Development Tool page 105 6 Script Commands Files Available only for CStruct and Image files FILE_APPEND Specifies default options DUMP_FILE DEFAULT 6 8 4 Trace Options Enumerated Data Types 6 8 5 page 106 Multi Target Development Tho The following enumerated data type is used to specify the event options when saving a trace buffer to a file enum TRACE _EVENT_OPTIONS All targets STEP EXCEPTION MEM READ MEM WRITE DIVIDER PRINT eTPU and TPU Targets on
5. This script establishes a memory share between a docking target FromTargetName and a docked to second target ToTargetName Memory accesses for the docking target actually occur in the second target while this command has no effect on the second target s accesses Docking target accesses within the block BlockName in the address space ADDR_SPACE are projected to the docked to target at on offset address AddressOffset The address range corresponds exactly to a previously defined block within the docking target There is no such requirement for the docked to target add_mem_block Cpu_A 0x0 OxFFFF Shared ALL_SPACES add_non_mem_block Cpu_B 0x600 Ox6FF ShareRange ALL_SPACES set_block_to_dock Cpu_B ShareRange ALL SPACES Cpu_A 0x250 In this example a memory share is setup between targets Cpu_A and Cpu_B The memory that is shared resides in Cpu_A The shared block is accessed by Cpu_B between addresses 600 and 6FF hexadecimal An offset of 250 hexadecimal is applied to the address of each of Cpu_B s accesses such that from the perspective of Cpu_A the accesses occur between 850 and 94F hexadecimal Note that as required the set_block_to_dock script command has the identical address range as a previous add_non_mem_block script command Interestingly there is no such page 306 Multi Target Development T9 1994 2015 ASH WARE Inc Reference Manual 20 Building the Target Environment restriction on the
6. OR gate verify chan_output_pin 6 0 XOR gate verify chan_output_pin 7 NAND gate H Although there are several types of script commands windows only two styles can be viewed within a window primary and ISR The primary script commands file window displays the open or active primary script commands file whereas an ISR script commands file window displays a script commands file that is associated with a eTPU channel interrupt See the Script ISR section for an explanation of these two types of script commands files There are several types of script commands files The primary script commands file window displays the open or active primary script commands file An ISR script commands file window displays a script commands file that is associated with a eTPU channel interrupt which is described in the Script ISR section A list of the available script commands functional groups is given in the Script Commands Groupings section 1994 2015 ASH WARE Inc page 176 Multi Target Development Tho Reference Manual 15 Operational Status Windows The primary script commands file is loaded from the Files menu by selecting the Scripts Open submenu and following the instructions of the Open Primary Script File dialog box The primary script commands file can be reread at anytime This is done from the Files menu by selecting the Script Fast submenu MtDt re executes the file starting from the first command When the primary script co
7. write _chan_mode ChanNum ModeVal This command writes channel ChanNum to function mode ModeVal Note that this modifies the FM field of the CxSCR register This is a two bit field so valid values are 0 1 2 and 3 define PWM1 CHAN 17 write_chan_mode PWM1_CHAN 3 In this example channel 17 s function mode is set to 3 eTPU Event Vector Entry Condition Standard Alternate Commands write_chan_entry_condition ChanNum Val This command writes channel ChanNum s event vector entry condition to Val Note that this writes the CxCR register s ETCS field A value of 0 designates the standard table and 1 designates alternate Note that each function has a set value and that this value MUST match that of the eTPU function to which the channel is set define UART_STANDARD_ENTRY_VAL 0 define PWM_ALTERNATE_ENTRY_VAL 1 write_chan_entry_ condition UART1_CHAN UART_STANDARD_ENTRY_VAL write_chan_entry_condition UART2_CHAN UART_STANDARD_ENTRY_VAL write_chan_entry_condition PWM1_CHAN PWM_ALTERNATE_ENTRY_VAL write_chan_entry_ condition PWM2_CHAN PWM_ALTERNATE_ENTRY_VAL In this example the UART channels are programmed to use the standard event vector table and the PWM channels are programmed to use the alternate event vector table The ETEC compiler automatically outputs entry table type information into the auto defines file In the Byte Craft eTPU C Compiler the event vector condition alternate stan
8. 8 Test Vector Files B Engine Example eTPU File ENGINE Vector AUTHOR Andrew M Klumpp ASH WARE DATE 950404 if DESCRIPTION if This generates the test vectors associated with a four cylinder car The four spark plugs fire in the order 1 3 2 4 For convenience an engine frequency is chosen such that one degree corresponds to 10 microseconds 10 microseconds will be written as 10us A test vector frequency is chosen such that one degree corresponds to one time step The test vector frequency is the simulator debugger s internal test vector timebase Within each engine revolution two spark plugs fire ASSIGN NAMES TO PINS i Assign the descriptive names to the synch and spark plug signals node Synch ch3 node Sparki ch8 node Spark2 ch11 node Spark3 ch6 node Spark4 ch4 ASSOCIATE PINS WITH A GROUP Make a group named SYNCH with only the SYNCH TPU channel as a member group SYNCH Synch Make a group named SPARKS that consists of the four spark plug signals group SPARKS Spark4 Spark3 Spark2 Sparki DEFINE THE SYNCH STATES The synch signal can be either pulsing 1 or waiting 0 state synch_pulse 1 state synch_wait 0 Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 121 8 Test Vector Files DEFINE THE SPARK FIRE STATES There are five states fF There is one state for each of the four spark plugs firing Z There i
9. Target Development Tool page 137 9 Functional Verification 9 5 9 6 page 138 Multi Target Development Tho automation Console Mode A console mode version of the simulator debugger supports regression testing without the GUI The console mode version of the executable contains the _CL suffix on the file name Command Line Options When launching the simulator debugger the last loaded project file is automatically loaded and the project file contains most of the settings such as the name of the script file to load which messages to suppress etc However it can be useful to specify the project file to load or even to override settings contained in the project file This is by specifying settings at the command line when launching the simulator debugger This is especially useful when building regression tests Prints a list of all the Command Line Parameters pTest ETpuSimProject Loads project file Test ETpuSimProject Project File p lt ProjectFileName gt Loads the specified project file Script File s lt ScriptFileName gt sRarChunkTest Cmd Loads the specified script Loads script file file single target RarChunkTest Cmd Script File 4 sMyScript Cmd Cpu32 1994 2015 ASH WARE Inc Reference Manual 9 Functional Verification Setting Loads the specified script g lt ScriptFileName gt Loads script MyScript file into the specified target lt TargetName gt Cmd into the CPU3
10. This causes simulator debugger to stop executing This is normally used to stop simulator debugger when the expected event such as step breakpoint time slot transition etc failed to occur Reset and Go This causes simulator debugger to reset and immediately begin execution The reset actions are specified in the Reset Options submenu simulator debugger will execute until a breakpoint is encountered or until interrupted by the user selecting the Stop submenu from the Run menu Reset This causes simulator debugger to reset The reset actions are specified in the Options submenu in the Reset menu Help This accesses this help screen page 266 Multi Target Development T 1994 2015 ASH WARE Inc Reference Manual 17 Menus 17 4 Breakpoints The breakpoints menu controls the various functions associated with the breakpoint capabilities of the simulator debugger These capabilities are accessed via the following submenu s Set Toggle This toggles a breakpoint at the source code window s cursor If the instruction already has a breakpoint then the breakpoint is deleted A source code window must be active for this to work If the source code is in mixed assembly view mode and the cursor is at a dis assembly line then the breakpoint will be generated for only that address Disable All This disables all active breakpoints Disabled breakpoints remain disabled the simulator debugger remembers which breakpoints hav
11. When in fixed channel display mode the window title contains the logical name for that channel See the Test Vector Node Command section for assigning logical names eTpuX Channa Logic Fuel_3 4 13 mje x B Match TCR4 TCR2 e TCR1 TCR4 mrle SET SET 28EF88 00004 66046B 113 16 Capture 178C26 EE9CES 001A41 672 10 mrl clr clr tdl clr clr ENABLE Hatch and transition servicing lsr clr During thread ENABLE matches Input Pin Low E Output Pin Low Output Buffer ENABLED Output Not Delayed IPAC A Do not detect transitions IPAC B Do not detect transitions OPAC A Match sets output signal high OPAC B Do not change output signal Either Match Non Blocking Double Transition Flags clr 1 clr O Addr 6688 Active 66 663 Threads 16 Steps 569 Longest Thread 73 steps 1 466 66 nS Addr 69BC MI and M3 are the Match register values for action unit A and B respectively M2 and M4 are the difference between the Match register and the active counter TCR1 or TCR2 for which matches on that action unit are configured When in angle mode M2 and M4 may display the angle at which the match is scheduled to occur In order for page 198 Multi Target Development T9 1994 2015 ASH WARE Inc Reference Manual 15 Operational Status Windows Angle to be displayed certain configuration must have occurred as covered in eTPU Time Base Configuration Script Commands section Note that in the above d
12. amp address operator Array elements can be accessed with the operator where the subscript is an integer Structure members can be accessed via the or gt operators In the current release only a single operator per watch is supported Future versions will support a more full feature C syntax Note that code must be compiled with symbolic debug information for this functionality to be available See the Global eTPU Channel variableAccess section for information on accessing eTPU channel variables using the format shown below lt chan num name gt lt function var name gt Vie wing Named Timer Region Information Code can be instrumented with named timing regions Traversal time information across these regions can be viewed in the watch window using the following format AshTimer TimingRegionName The traversal time and the number of system clocks in the last traversal are listed Also the number of times traversed and the cumulative amount of time spend in the regions is also listed Depending on the target the number of instruction cycles spend in the traversal region may also be listed A list of the named regions that are available for selection is in the Insert Watch dialog box Vie wing Print Action Command Output Print action commands support instrumentation of code to output code execution information Think printf This information is normally output to the trace buffer and from the trace buffer can be
13. ccceeccseeeeeeeeeeeeeeeneeeeneeeeeneeeeneneeeseeeeseeeneneeeseeseneeeenseeees 233 TOUCAN Buffers Wind Ow c cccseceseeeeeseeeeeseeeeseeeeseeenseeeeseeeeseeeensneeeseeeeneeeenseeess 234 Masked ROM Window cccs cccseeessseeeeeeeenseeeeeneeeeeeeensneeeeeeeeseneensneeeseeeeeeeeeeseenenees 234 Standby RAM Submodule Window 68336 68376 sssseseseeseesernseseeenes 235 Static RAM Submodule Window 68338 sscescsseseeseeeseeseeenseesenesseesenenseeseeenee 235 Parallel Port UO Submodule PIOSM Window csscseessecserseeeseessneeseeneeeneeess 235 Real Time Clock RTC Window Part 16 Dialog Boxes 237 16 1 File Open Save and Save As Dialog Boxes 2 s eeeeeeeeeeeeeeeeeeeeees 238 16 2 Auto Build Batch File Options Dialog Boxes cccceeeeeeeeeeeeeeeeeeeeeees 240 page 8 Multi Target Development Tool Multi Target Development Tool 16 3 Goto Time Dialog BOX ccceeeececeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeene 241 16 4 Goto Angle Dialog BOX ccececeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeseeeeeeeseeeeeeeeeeeeenees 242 16 5 IDE Options Dialog BOX cecececeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee 243 16 6 Workshop Options Dialog BOX cccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeseeeeeeeeeeeeeeee 245 16 7 Occupy Workshop Dialog BOX cccccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeneeeees 246 16 8 MtDt Build Options Dialog BOX
14. enum ADDR_SPACE enum READ_WRITE This command results in privilege violations for accesses to the target TargetName for the memory block BlockName for the applicable address spaces ADDR_SPACE and read and or write cycles enum READ_WRITE The affected address spaces must be a subset of the address spaces to which the referenced memory block applies define ALL_DATA_SPACE CPU32_SUPV_DATA_SPACE CPU32_USER_DATA_ SPACE add_mem_block Host 0x10000 0x1FFFF Protected ALL_DATA_SPACE set_block_to_priv_viol Host Protected CPU32_USER_DATA_ SPACE RW_ALL In this example data space accesses to the simulated memory while at the supervisor privilege level will succeed whereas accesses at the user privilege level will result in a privilege violation set_block_to_addrs_fault TargetName BlockName enum ADDR_SPACE enum READ_WRITE This command results in address faults for odd accesses to the target TargetName within the block BlockName for the applicable address spaces ADDR_SPACE and read and or write cycles enum READ_WRITE The affected address spaces must be a subset of the address spaces to which the referenced memory block applies Even accesses will not result in an address fault set_block_to_addrs_fault Host EvenMem CPU32_CODE_SPACE RW_ALL In this example code space accesses to odd addresses are configured to result in an address fault set_block_timing TargetName BlockName enum AD
15. s parameter RAM word 3 bit 14 is verified to be equal to 1 If the value is indeed equal to then the simulation continues If the bit is instead a zero an error message is printed to the screen For instance if channel 10 s RAM word three is equal to 4000 hex the verification would pass while if it were instead equal to zero the test would fail and an error message would be displayed Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 91 6 Script Commands Files 6 6 33 6 6 34 page 92 Multi Target Development Tod eTPU TPU Host Service Request Register Script Commands write _chan_hsrr ChanNum Val This command writes channel ChanNum s HSRR bits to value Val write _chan_hsrr 4 0 In this example channel 4 s HSRR bits are written to zero If channel 4 had a pending host service request it would be cleared TPU Channel Interrupt Service Register Commands clear_cisr ChanNum This command clears a Channel Interrupt Service Request CISR from channel ChanNum This command accepts a single argument clear_cisr 7 In this example the CISR is cleared from channel 7 clear _this_cisr This command clears the CISR of the active channel from within an ISR script commands file Note that in the primary script commands file there is no channel context so this command cannot be used and use of this command generates a warning message No arguments are required with this command clear _th
16. sscsssseeseseeeeeseteneees 92 TPU Host Sequence Request Register COMMAMNAS csscesceeseeeesesetenseeseteneees 93 TPU Clock Control Script COMMAMNAS cteseseseeseeeeeeeseseestessevseveeeenennennennanees 93 TPU Bank and Mode Control Script Commands cccsestsseseeveeveeseeeeeeneeneenees 95 TPU Match Transition amp Link Script COMMAMNAS csceseeeeeeseeeesensetenseeneneneees 96 page 4 Multi Target Development Tool Multi Target Development Tool eTPU TPU Interrupt Association Script Commanhs ccc eteteseseneeneeneeeeees 96 External Logic Command Saia a reeeo aer taaa saaie aao aaas Ur aa aaaea nae Sa a EAE 98 6 7 Automatic and Pre Defined Define Directives SEENEN ENEE 100 6 8 Listing of Script Enumerated Data Types Script FILE_TYPE Enumerated Data Type Script VERIFY_FILES Enumerated Data Type ve SE G i Script FILE_OPTIONS Enumerated Data Type cssscssscseseerseesseerseeseeseeseneneee 105 Trace Options Enumerated Data Types cssscsessesssesesessessessesseesenseneneenenneas 106 Code Coverage Listing Options Enumerated Data Type ccceseseeeeeeeeee 106 Base Time Options Enumerated Data Type ccssssssessnsnessessesseveevenneneenenees 107 Build Script TARGET_TYPE Enumerated Data Type se 107 Build Script TARGET_SUB_TYPE Enumerated Data Type Sie nn 107 Build Script ADDR_SPACE Enumerated Data Type eessen tied 108 Build Script READ_WRITE
17. 1500 end _trace_stream The above example begins streaming all trace data except dividers and memory reads to a trace file named Stream Trace Time is recorded in micro seconds with three trailing digits following the period such that the least significant digit represents nano seconds The isResetTime field is set to true so that script execution time of 400 micro seconds is subtracted from the time and the clocks field Formatted symbolic information can be generated using as described in the String within a String section The following is an example of this format print_to_trace TEST RESULTS n a A d n B d n j C d A B C The print_to_trace command supports using HIE and or LIN as arguments that get replaced by the name and absolute path of the file in which it is found or the file line number of the text print_to_trace s d TEST COMPLETE FILE_ __ LINE outputs lt filename gt lt linenum gt TEST COMPLETE 1994 2015 ASH WARE Inc page 66 Multi Target Development Tod Reference Manual 6 Script Commands Files Save Trace Buffer Script Command DEPRECATED save_trace_buffer FileName trace enum TRACE_EVENT_OPTIONS enum TRACE FILE OPTION enum BASE_TIME U32 numTrailingDigits WARNING this save_trace_buffer script command is deprecated This command is the same as the start_trace_stream command except that the entire trace buffer is saved to a file
18. 32 MyBdm32 TPU Host I F ol x FEDcCeBA9 8 7 6 5 4 3 21 crsk E 6 6 6 68 68 68 6 8 8 8 8 8 8B BB 8666 6000 6006 GOGA CPR 66 op op op op op op op op op op op op op op og 9906 00GA HSRR op op op op op op op op op op op op op op op op 0000 0008 HSQR op 66 op op op op op op op op op op op op op op 8666 6008 CISR 6 6 6 6 6 6 6 6 6 6 8 6 GA Q G TTT CIER 6 6 6 68 6 6 6 6 6 86 68 GAGO A G B080 The TPU Host Interface window displays the Channel Function Select Register CFSR the Channel Priority Register CPR the Host Service Request Register HSRR the Host Sequence Register HSQR the Channel Interrupt Status Register CISR and the Channel Interrupt Enable Register CIER Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 221 15 Operational Status Windows 15 7 4 TPU Parameter RAM Window 32 MyBdm32 TPU Parameter RAM of x e BU 8034 oc 6166 2811 6661 gong gong 1 6610 1040 6C34 2128 opp 0021 HONO 000G 2 4011 6934 6008 9005 1120 104E 6600 gong 3 86600 8114 6606 6281 6669 0554 6600 gong 4 0319 0028 64061 6011 6216 2004 gong gong 5 2440 4034 6905 0024 3C96 1698 6600 gong 6 DOGO C266 8665 8030 8896 6460 gong 000G 7 4614 gen 4886 6112 8621 6234 90060 6008 8 8640 6660 662A 6041 8660 1004 6600 gong 9 62F2 6014 0230 110C 28668 Coon gong 000G A 6168 6761 2091 6015 6636 3660 6600 000G B 4370 gon 1240 2008 6612 6814 gong 000G C 4611 6936 9020 4012 8264 0140 6600 gong D 1212 6528 C400 6046
19. In the example shown below the name UART is assigned to the TPU s channel 5 I O pin define UART CH5 Thread Activity Nodes Thread activity can be extremely useful in both understanding and debugging simulator debugger functions The simulator debugger provides the following thread activity nodes ThreadsGroupA ThreadsGroupB ThreadsGroupC ThreadsGroupD ThreadsGroupE ThreadsGroupF ThreadsGroupG ThreadsGroupH These nodes can be renamed In the following example the ThreadsGroupB node is assigned the name A429RcvThreads Note that the primary purpose of renaming these nodes is to provide a more intuitive picture in the logic analyzer window as shown below See the Logic Analyzer Options Dialog Box section for more information on how to specify groups for monitoring of TPU and eTPU thread activity node RcvThreads ThreadsGroupB page 118 Multi Target Development T 1994 2015 ASH WARE Inc Reference Manual 8 2 8 3 8 Test Vector Files eTpu1 Logic Analyzer E ec Sal et e GAS c 1 846 820 1 nS Mouse 1 959 751 4 nS Data Start 000 000 0 nS Context 000 000 0 n Current Time 3 382 000 0 nS Left Cursor 1 848 531 2 nS Delta Cursor 109 509 2 nS Right Cursor 1 958 040 3 nS Group Command group lt GROUP_NAME gt lt NODE 1 gt NODE 2 NODE N The group command assigns multiple nodes NODE N to a group name GROUP_NAME These nodes can be referred to later by this group n
20. Local Variable Options Dialog Box License Options Dialog Box BDM Options Dialog Box Memory Tool Dialog Box Insert Watch Dialog Box Watch Options Dialog Box C 1994 2015 ASH WARE D Target Development Tool page 237 16 Dialog Boxes 16 1 File Open Save and Save As Dialog Boxes The File Open Save and Save As dialog boxes support the opening and saving of a number of files Each of these is described individually below Load Executable Dialog Box The Load Executable dialog box controls the opening of the executable image source code This enables the user to change the source code recompile the source code and reread it into MtDt It also allows a different executable image source code to be loaded into the target See the Source Code Files Windows section for information on viewing the executable image source code files Open Primary Script File Dialog Box This dialog box specifies which primary script commands file is open Only one primary script commands file may be opened for each target at one time The default search is XXXCommand where XXX denotes the type of target For instance for TPU Targets the default search is TpuCommand Save Primary Script Commands Report File Dialog Box This dialog box specifies the report file that is generated when the primary script commands file is parsed Note that selection of a file name does not actually cause the report file to be written Rather the repo
21. Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 53 6 Script Commands Files 6 6 2 page 54 Multi Target Development Tod second and a number of calculations such as TPU frequency QSM frequency etc are based on this assumption Unfortunately the simulator debugger has no way of verifying that this is in fact the correct crystal frequency so the following script command allows the user to override the default set_crystal_frequency cylesPerSecond This code sets the assumed external clock frequency to cyclesPerSecond Note that the cyclesPerSecond must be a decimal or hexadecimal number A floating point number will not work set_crystal_frequency 34000 The code in this example overrides the default external clock crystal value and sets it instead to 34 KHz Timing Script Commands at_code_tag TagString at_code_tag_ex TagString Timeout TimeoutAction These commands prevent subsequent commands from executing until the target hits the source code that contains the string lt TagString gt Note that all source code files are searched and that the string should be unique so that it is found at just one location for otherwise the command will fail at_code_tag MyTest1 verify val failFlag 0 In the example above the target executes until it gets to the point in the source code that contains the text MyTest1 and then verifies that the variable named failF
22. TDL Match Transition Service Request Inhibit SRD and Link Service Latch LSL The disable match bit from the entry point This bit controls whether a match page 208 Multi Target Development Td 1994 2015 ASH WARE Inc Reference Manual 15 Operational Status Windows is inhibited during channel servicing The active counter for capture and match TCR1 or TCR2 The pin direction input or output The current pin state high or low The PAC setting determines the pin action on a match if the pin is an output or the transition to be detected if the pin is an input The effective match condition greater than or equaLto or greater than Since this field applies to TPU2 and TPU3 only when in TPU1 mode this field is not displayed Unlike previous versions of this software the active channel is not specified directly from the menu when the window is opened Instead the active channel is specified from within the window by accessing the popup menu To do this right click the mouse and select the desired channel number from the menu This makes it easier to view the various channel settings without having to have lots of channel windows open During channel servicing the active channel can be changed by the microcode The microcode changes the active channel by writing to the CHAN register found in the TPU Execution Unit window When the active channel is changed by the microcode the effective active channel is somewh
23. The following enumeration provides the mechanism for referencing the TPU s 16 bit registers Note that this covers only those TPU registers that are newly accessible with this software version Future software versions will make greater use of this enumerated data type enum REGISTERS U16 REG_TCR1 REG_TCR2 Counter registers Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 111 6 Script Commands Files 6 8 13 CPU32 Register Enumerated Data Types The CPU32 register enumerated data types provide the mechanism for referencing the CPU32 registers These enumerated data types are used in commands that reference the CPU32 registers such as the register write commands that are defined in the Write Register Script Commands section The following enumeration provides the mechanism for referencing the CPU32 s 8 bit registers enum REGISTERS_U8 REG CCR Condition Code Register D The following enumeration provides the mechanism for referencing the CPU32 s 16 bit registers enum REGISTERS_U16 REG SR Status Register D The following enumeration provides the mechanism for referencing the CPU32 s 32 bit registers enum REGISTERS_U32 REG_PC REG_VBR Program Counter Vector Base Register REG_USP REG_SSP User and Supervisor Stack Pointers REG SFC REG_DFC Alternate Function Code Registers REG DO REG DI REG_D2 REG_D3 Data register DO to D3 REG D4 REG D5 REG D6 REG DI Da
24. and execution time also including flushes for that thread Note that this thread will normally execute many many times in the course of a simulation run and each time the thread executes it may take a different path such that the execution time may vary The worst case number shows the very worst longest amount of time that the thread takes to execute through the entire simulation run Finding a Thread s Source Code To find the line of source code for each thread move the cursor within the thread window The first source code line of that thread automatically pops into view and turns yellow as shown below Reference Manual C 1994 2015 ASH WARE Pgri Target Development Tool page 183 15 Operational Status Windows eTpu1 Source eTPU etpuc_arinc mc loj x bf RISA II ILI IE ID ISI IIIS ISN ISIS SIS ANSI SI a a Z Received an expected data bit bits 24 31 else if IsTransitionhEvent amp amp flage 2 S flagi RECEIVED_DATA_BIT_24_31 shift_reg dataf data31_24 gt gt 1 shift_reg dataB data31_31 Chan Seng datat datap 8 Cou 1 1 i 360 nS INITIALIZE 174 646 NS RE_INIT_INTERRUPT 174 566 nS RECEIVED DATA BIT 6 23 UALID_GAP_AND_DATA 168 nS UALID_GAP_NO DATA TOO Hong BITS FAULT BIT _DETECTED_IN GAP_HUNT LINE WENT IDLE FAULT INUALID_THREAD_FAULT Al Re Executing the Worst Case Thread If the thread has executed at least once such that there is a worst case thread time available
25. cccceeeeseeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeseeeeeees 246 16 9 Message Options Dialog BOX ccccceeeeseeeeeeeeeeeeeeeeeeeeeeeeeseeeeneeeseeeeeee 248 16 10 Source Code Search Dialog BOX ccccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeseeeeeensees 250 16 11 Reset Options Dialog BOX cccsececeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeseeeeeeeseeeeeeesees 251 16 12 Logic Analyzer Options Dialog BOX cccceeeeceeeeeeeeeeeeeeeeeseeeeeeeseeeeeeeeees 253 16 13 Channel Group Dialog BOX cccceeeeeeeeeeeeeeeeeeeeeeeeeseeeeeeeseeeeeeeseeeeeeesees 254 16 14 Complex Breakpoint Conditional Dialog BOX 22 c seceeeeeeeeeeeeeeeeees 254 16 15 Trace Options Dialog BOX ccceececeseeeeeeeeeeeeeeeeeeeeeeeeseeeeeeseeeeeeeseeeeeeesees 254 16 16 Local Variable Options Dialog BOX ccccseeeceeeeeeeeeeeeeeeeeseeeeeeesseeeeeeeees 256 16 17 License Options Dialog BOX ccccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeaeeeeeeeeseeeeeeeees 256 16 18 BDM Options Dialog BOX cccceeeeceeeeeeeeeeeeeeeeeeeeeeeeeeseeeeeeseeeeeeeseaeeeeesees 257 16 19 Memory Tool Dialog BOX cccceeeeceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeseeeeeeeseeeeeeesees 257 16 20 Insert Watch Dialog BOX ccccceeeeceeeeeeeeeeeeeeeeeeeeeeeeeseeeeeeesseeeeeeseeeeeeesees 258 16 21 Watch Options Dialog BOX cececeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeseeeeeeeseeeeeeesees 259 16 22 The About Dialog BOX ee EEERRRR KEREN KEREN KEE RRE KEE RRE KEREN EEE RRE en
26. clear_chan_overflow_intr ChanNum clear_data_intr ChanNum clear_data_overflow_intr ChanNum These commands clear the interrupts for channel ChanNum It is equivalent to setting the bit associated with the channel in the CICX DTRC CIOC or DTROC fields verify chan_intr ChanNum Val verify chan_overflow_intr ChanNum Val verify data_intr ChanNum Val verify data_overflow_intr ChanNum Val verify _illegal_instruction Val verify microcode_exception Val Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 89 6 Script Commands Files 6 6 31 page 90 Multi Target Development Tod These commands verify that the respective interrupts are either asserted Val 1 or de asserted Val 0 clear_global_exception This command clears the global exception along with the exception status bits It is equivalent to setting the GEC field in the ETPUMCR field disable _chan_intr ChanNum enable_chan_intr ChanNum disable _ data_intr ChanNum enable_data_intr ChanNum These commands enable disable the interrupt for channel ChanNum Note that if you associate a script ISR file with an interrupt these commands allow or prevent that file from running on assertion of the interrupt clear _this_intr This command can only be run from within a script ISR file It clears the interrupt that caused the command to execute eTPU Shared Subsystem Script Commands config_shared_sub_
27. information on each file used to create the microcode build Each section contains a number of lines that provide the following information The instruction line lists the total number of instructions Both regular and branch instructions are counted but entry table information is not The instruction hits line lists the number of instructions that have been fully covered The instruction coverage percent line lists the percent of instructions that have been covered The branches line lists the total number of branch paths This is always an even number because for each branch instruction there are two possible paths branch taken and branch not taken If the branch path has been traversed then this counts as a single branch hit Conversely if the non branch path has been traversed then this also counts as a single branch hit The branch instruction is considered fully covered when both the branch path and the non branch path have been traversed The branch coverage percent line contains the percentage of branch paths that have been traversed Flushed instructions for which a NOP has been executed are not counted as having been covered An example of such a file TPU target follows Code coverage analysis file Copyright 1996 2012 ASH WARE Inc Sun June 02 09 30 30 1996 Total Instructions 135 Instruction Hits 57 Instruction Coverage Percent 42 2 1994 2015 ASH WARE Inc page 134 Multi Target Development Tho Referen
28. type int the dereferenced pointer is displayed on the next line as an integer Default expansion is up to three levels deep with pointers arrays and structures unions bitfields supported An alternative expansion level can be specified See the Local Variable Options Dialog Box section for more information Future enhancements will give the user control over expansion and collapse of variables Note that in order for this feature to be available code must be compiled with symbolic debug information In order for this window to correctly identify and display local variables the proper options for each compiler must be chosen For instance debugging information needs to be included and certain stack frame requirements must be met In certain cases highly optimized code may cause erratic behavior in this window See the ASH WARE Web page for a detailed explanation of the correct compiler settings for each target and limitations when using certain specific compiler settings Note that as the target executes the contents of the Local Variables window will usually change quite a bit This is because each function generally has a unique set of local variables that are displayed As the target moves from function to function only the local 1994 2015 ASH WARE Inc Reference Manual 15 1 5 15 Operational Status Windows variables of the currently executed function are displayed Global variables are not displayed within this window See
29. 15 tg KTI uy 15 1 6 Thread Window This window has a number of user selectable views and options The window shown above has been configured to track all instances of the function ARINC_RX Since multiple channels can run this particular function the data shown by this window is an accumulation of all the channels that have been assigned this function page 182 Multi Target Development T9 1994 2015 ASH WARE Inc Reference Manual 15 Operational Status Windows lof x Addr Cov Cnt we Tot WC Time 6 62DC 1 1 2 18 36 366 nS INITIALIZE 1 62FC 1 4 2 2 4 646 nS RE_INIT_INTERRUPT 2 6364 1 4 216 25 4365 566 nS RECEIVED DATA_BIT_6 23 3 6368 1 4 72 23 15390 466 nS RECEIVED_DATA_BIT_24_31 4 83EG 1 4 18 27 366 546 nS UALID_GAP_AND_DATA 5 6478 1 4 1 8 8 166 nS UALID_GAP_NO_DATA 6 6498 6 2 TO0_ MANY BITS FAULT Z O4B4 6 2 8 8 BIT DETECTED IN GAP HUN 8 DEN 6 4 8 6 LINE_WENT_IDLE_FAULT 9 6566 6 3 D 8 INUALID_THREAD_FAULT mE jo TPU and eTPU code executes in response to events This event response code is known as a thread Individual threads are assigned to each event and event combination A key performance index of your code is the amount of time each thread takes to execute Therefore this thread window is an important tool for determining the performance of your code Two important columns are WC Steps and WC Time These display the worst case number of execution steps including flushes
30. 1994 2015 ASH WARE Inc Reference Manual 16 Dialog Boxes Delete This button removes a location from the search list Cut This button removes the currently selected search location from the search list and places it into the paste buffer Copy This button adds the currently selected search location to the paste buffer without removing it from the search list Copy This button creates a new search location using the paste buffer Move Up This button moves the currently selected search location higher in the search list such that this location is searched earlier Move Down This button moves the currently selected search location lower in the search list such that this location is searched later 16 11 Reset Options Dialog Box The Reset Options dialog box is accessed from the Options menu by selecting the Reset submenu It specifies the actions taken when either the Reset submenu or the Reset and Go submenu is selected Reread Primary Script Commands File Selecting this option causes the primary script commands file to be reread every time simulator debugger resets the targets Rewrite Code Image Selecting this option causes a cached version of the executable image to be re written every time simulator debugger resets the targets The executable image file is not reread Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 251 16 Dialog Boxes instead a cached version of the executable im
31. 31 UALID_GAP_AND_DATA eene ee enee eeeeeeeeeeto leieeeeeoeee E I I j ae ee ee ee enen eeeee enee wO I ak zi The group and ungroup commands allow the same threads from different event vector response combinations to be grouped together The window shown has this option set to ungroup Note that there are 32 event vector combinations To get good testing coverage all of these event combinations should be tested By setting the window to show all event response combinations it becomes clear that the simulation run on this window is not fully exercising the function and as such the event vector coverage is poor Q 1994 2015 ASH WARE Inc page 186 Multi Target Development Td Reference Manual 15 Operational Status Windows 15 1 7 Trace Window 2 Host Trace i ioi xi Ff EEIE IE IE JE IE DE JE HH JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JEJEJEJE JEFE aj GESE og EXCEPTION External Interrupt 667 472 68 80002D9B1 16 Bit Write using Supervisor Data Space at address FFCE 8x100 256 607 472 68 00002D9B1 32 Bit Write using Supervisor Data Space at address FFCA xe5e 3678 007 472 2 00002D9B4 16 Bit Write using Supervisor Data Space at address FFC8 0x2004 8196 007 472 4 66062D9BA 32 Bit Read using Supervisor Data Space at address 2566 0x590 1424 667 472 5 00002D9BD Ff RHEE IE JEJE JE JE JE IE JE JE JE JE JE JE E IE JE JE JE JE ASAI JE JE JE JE JE JE JE JE
32. 6 ADDR22 css ADDR21 PC 5 5 4 ADDR21 CS7 ADDR26 PC 4 3 2 ADDR26 C ADDR19 PC 3 1 6 ADDR19 xxxxx PORT C DATA AND CHIP SELECT PIN ASSIGNMENT REGISTER PORTC ZE CSS FC2 PC 3 D C 16 Bit CS CSPARO 3FFF CS4 FC1 PC 1 B A 16 Bit CS CS3 FCO PC 6 9 8 16 Bit CS CS2 BGACK 7 6 16 Bit CS Can BG 5 4 16 Bit CS Cp BR 3 2 16 Bit CS CSBOOT 1 6 16 Bit CS xxxxx PORT E PIN ASSIGNMENT DATA DIRECTION AN PEPAR FF SIZ1 DDRE 66 SIZ PORTE FF AS RHC 7 6 5 DS 4 3 AVEC 2 4 DSACK1 PFPAR 66 IRQ Fa DDRF 66 IRQ6 6 PORTF 61 IRQS 5 IRQ4 4 IRQ3 3 IRQ2 2 IRQ1 1 6 7 6 5 4 3 2 1 D xxxx PORT F PIN ASSIGNMENT 7 5 4 3 2 1 MODCLK D 121 1268 AS DS RNC AVEC DSACK1 DSACKO PF 7 PF PF 5 PF 4 PF 3 PF 2 PF 1 PF 8 DATA DIRECTION Input Input Input Input Input Input Input Input 15 x xxxxx PORT C DATA AND CHIP SELECT PIN ASSIGNMENT REGISTER 1 x PRIMARY ALTERNATE DISCRETE BITS D DATA REGISTERS xxx AND DATA REGISTERS xx zk 9 Ca ee ee e The SIM Ports window contains the registers that determine the port pin usage pin direction input or output and value These registers are the Port C Port E and Port F Data Registers PORTC PORTE PORTP the Chip Select Pin Assignment Registers one and zero CSPAR1I CSPARO Port E and Port F Pin Assignment Registers PEPAR PFPAR and th
33. 64K of the CPU32 s supervisor data space The default options are used for this dump An assembly file Dump dat is also created from the first 64K of supervisor code space and both address mode and symbolic information are excluded Assuming the target processor is a CPU32 the generated assembly code is for the CPU32 verify files fileNamel dat fileName2 dat enum VERIFY_FILES_ RESULT This script command verifies two file named fileName 1 dat and fileName2 dat In addition to checking for matching or mismatching this script command also can verify non existence of either file or both files Expected results are specified with the VERIFY_FILES_ RESULT enumeration verify files new dat gold dat FILE1_MISSING dump_file 0 0x28 ETPU_DATA SPACE new dat IMAGE DATA verify files new dat gold dat FILESMATCH In the above example a new file named new dat is generated and is compared against file gold dat to make sure that they match By first verifying that file new dat does not exist the fact that file new dat is actually generated by the dump command is also verified 1994 2015 ASH WARE Inc page 64 Multi Target Development Tod Reference Manual 6 Script Commands Files dump_file 0 0x28 ETPU_DATA_SPACE new dat IMAGE DATA8 verify files new dat gold dat FILES MISMATCH wait_time 100 dump_file 0 0x28 ETPU_DATA_SPACE new dat IMAGE DATA8 FILE_APPEND
34. 6668 A282 gong gong E B284 4160 4002 1020 19020 8260 np 4001 F 6260 6266 856A 85068 AG22 5509 6258 418B The TPU Parameter RAM window displays the TPU Parameter RAM Each row in the window displays the parameter RAM belonging to the row number s TPU channel 15 8 GPT Module Windows The following windows display the General Purpose Timer GPT module settings page 222 Multi Target Development Tho 1994 2015 ASH WARE Inc Reference Manual 15 8 1 GPT Main Window GPTMCR 3881 GPTICR 2368 DDGRP PORTGP 2FF2 oc1M 0C1D FSE6 TCNT 1344 PACTL PACNT 6466 TMSK1 TMSK2 82B8 TFLG1 TFLG2 16386 CFORC PWHC 2B84 PRESCL 6633 STOP FRA FR26 STOPP INCP SUPU IARB IPA IPL IUBA DDGRP PORTGP DIN IPA 14 05 TOI CPROUT CPR TOF PPR D md D rd TAND n d ECO em nm D et Dee E GO ed ECO Em nm 15 Operational Status Windows ll x GPT clocks are not shut down FR21 is not used When FREEZE on IMB halt the GPT Stop prescaler and pulse accumulator ignore input pins On STOPP increment prescaler amp input synchronizers once SzU registers access at Supu priviledge level Interrupt arbitration priority 1 Make Input Capture 2 highest priority Interrupt priority is level 3 Interrupt vector base address is 6X Pin Direction is 2F see other windows Pin Data is F2 see other windows OC1M Action Mask is 1F see Output Compare window 0C1D Action Data is 1C see Output Compare window Timer c
35. 683xx Hardware Debugger allows you to control any 683xx microcontroller across a BDM port You can load and execute code Standard debugging capabilities such as single step breakpoints goto cursor etc are supported Operational status windows support viewing of CPU32 registers memory peripherals etc 19 12 eTPU2 Simulation Engine Target The Enhanced Time Processing Unit Two or eTPU2 is a microsequencer sold by STMicroelectronics and Freescale Semiconductor on a variety of microcontrollers including the SPC563Mxx This is sold as a stand alone product and also as a system simulator in which it is co simulated along with one or more CPU targets The eTPU2 simulation engine can be used both as a stand alone device and in conjunction with other targets including multiple TPUs When used in stand alone mode of primary importance are script commands files and test vector files 19 13 eTPU Simulation Engine Target The Enhanced Time Processing Unit or eTPU is a microsequencer sold by Freescale on a variety of microcontrollers Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 279 19 Supported Targets and Available Products 19 14 TPU Simulation Engine Target The Time Processing Unit or TPU is a microsequencer sold by Freescale on a variety of microcontrollers There are currently three varieties known as TPU1 TPU2 and TPU3 simulator debugger supports all three varieties The TPU simulation
36. CPRs the Host Service Request Register HSRR the Host Sequence Registers HSQRs and the Channel Interrupt Service Request Register CISR Each register is broken down by TPU channel so that the value for each channel is easily found All register values are displayed in both binary and hexadecimal formats The user can modify the value of each of these registers in a repeatable fashion via the script commands file Alternatively these registers can be modified directly using the keyboard and mouse See the Script Commands File Window section for an explanation of this capability The TPU affects the states of the registers in the normal execution of its microcode For page 204 Multi Target Development Td 1994 2015 ASH WARE Inc Reference Manual 15 Operational Status Windows example the HSRR bits for a TPU channel are cleared when the microengine services that channel 15 3 3 TPU Scheduler Window F E D C B A 9 8 7 6 5 4 3 2 1 86 Prty D H H H H H H H Srl 6 61 6 6 6 6 6 6 6 6 A 6 6 AB SOL 6 61 6 6 6 6 6 6 6 6 6 6 6 B B HSRR 66 66 66 66 66 66 66 66 66 66 66 66 OA 66 66 66 LSR 6 6 6 6 6 6 6 6 6 Q A A B M TSR 6 6 1 6 6 6 6 A 6 E 6 6 A A A Time Slot Assignments Med Hi Hi Med Hi Lo Hi The TPU s microengine responds to the various channels based on a round robin scheduler The scheduler bases its servicing decisions on the Channel Priority Register CPR the Service Request Latch S
37. Cpu_A target set_block_dock_space TargetName BlockName enum ADDR_SPACE DockFromSpace enum READ WRITE enum ADDR_SPACE DockToSpace This command supports an address space transformation for a docked memory access Read and or write cycles enum READ_WRITE from target TargetName between within the block BlockName in the address spaces enum ADDR_SPACE DockFromSpace are transformed to occur in address space enum ADDR_SPACE DockToSpace The DockToSpace argument must specify a single space It is important to fully specify all shared memory accesses between dissimilar targets Docks with unspecified address space transformations result in indeterminate results For instance a eTPU sharing memory with a CPU32 could easily result in a opcode being fetched out of data space even though both targets have both code and data spaces Assumptions about similarity of address spaces between dissimilar targets simply should not be made add_non_mem_block Host 0x1000 0x1003 ShareRange ALL SPACES set_block_to_dock Host ShareRange ALL_SPACES eTPU_A O 0x1000 set_block_dock_space Host ShareRange ALL SPACES BN ALL TPU_PINS_SPACE In this example a target Host is docked to target eTPU_A An address space transformation is specified such that accesses to any of the CPU s address spaces occur in the TPU s PINS address space check TargetName ReportFileName This command does a check on the simulated
38. DASM66 IC Input capture x The CTM6 Double Action Modes Submodule window displays the DASM 4 5 6 7 8 9 10 26 27 28 and 29 Status Interrupt Control Registers DASM4SIC DASMSSIC DASME6SIC DASM7SIC DASM8SIC DASM9SIC DASMIOSIC DASM26SIC DASM27SIC DASM28SIC DASM29SIC See the Bits form of the CTM6 Double Action Submodule window for display of additional information page 228 Multi Target Development T9 1994 2015 ASH WARE Inc Reference Manual 15 9 8 CTM6 Double Action Submodule Bits Window 32MySim32 CTM6 Double Actions Bits DASM An input capture or output compare has occured SIC D D B DASHG4 938C 9200 988A DASHOS 6224 DASH66 8663 DASHO7 66604 DASH68 6326 DASH69 198D DASH16 Don DASH26 6222 DASH27 6641 DASH28 6666 DASH29 6666 6600 1900 8181 6666 693A 66606 B003 6761 6668 6068 6068 6068 l FLAG Yes No Ves No No No Yes No No No No Interrupt level is l IL 1 DIS DIS DIS DIS 1 3 DIS DIS DIS DIS Interrupt arbitration bit 3 If output then buffer operates mode is mode TARB3 clr clr clr clr clr SET clr clr clr clr clr l l l l l l l l WOR wired or wired or normal normal wired or normal normal wired or normal normal normal 15 Operational Status Windows la x IARB BIUMCR IARB 2 6 Connected to time base bus l l l l l l S B A A A B B A A A A A Pin function when input l BSL IN FO H
39. Development Tool page 207 15 Operational Status Windows flags PIN branch conditional is a new branch condition available in the TPU2 that is similar to the PSL latch But whereas the PSL reflects the pin state on the last time slot transition or channel register change the PIN reflects the current pin state Both the FLAG flag and the PIN branch conditional are features of the TPU2 that do not exist in the TPU1 and therefore are not displayed when in TPU1 mode 15 3 6 TPU Channel Window el Match Reg Capture Reg 4399 E Flag Match Reg 5123 Flagi Capture Reg 6666 Flag2 HSQ6 SET HSQ1 SET a Flag8 clr tdl Flagi clr sri Flag2 lsl mrle SET Hatch mri clr Captur tdl clr Hatch SEL clr Direct Lei clr Pin st Match ENABLE High c Capture TCR1 Hatch Match TCR1 Direction Output Pin State Low High on Match Match on There are two versions of the TPU Channel window The active channel version displays information on the active channel or previously active channel if none is currently active while the fixed channel version displays information on a particular channel The following information is displayed The match and capture registers The channel s bits from the Host Sequence Request HSQR register Flag2 TPU2 and TPU3 mode only Flag and Flag0 The states of the Match Request Latch Enable MRLE Match Recognition Latch MRL Transition Detection Latch
40. I Set to force output compare always reads 6 I l Capture edge match action or output pin state l l l l Operating mode FLAG IL IARB IEN BSL IN FORCE EDOUT MODE A lo sic DAT i SASH12A 6661 6666 No DIS clr dis 8 clr gt Output Port pin set high SASH12B E364 6666 Yes DIS clr dis B lo 1 clr IC gt Input Capture on falling edge SASH14A 1861 6666 No 1 SET dis A lo 8 clr OP gt Output Port pin set high SASM14B 6645 6666 No 1 SET dis A lo 6 clr OP gt Output Port pin set high SASM18A 6666 6666 No DIS clr dis A lo 8 clr IC gt Input Capture on falling edge SASM18B 6191 8D6A No DIS clr dis B HI 6 SET OP gt Output Port pin set low SASH24A 6526 6666 No DIS clr EN B lo 1 clr IC gt Input Capture on falling edge SASH24B 6686 6666 No DIS clr dis A HI 6 clr IC gt Input Capture on falling edge The CTM6 Single Action Submodule window displays the SASM 12A 12B 14A 14B 18A 18B 24A 24B Status Interrupt Control Registers SIC12A SIC12B SIC14A etc and the SASM 12A 12B 14A 14B 18A 18B 24A 24B Registers SIZDATA S12DATB S14DATA etc 15 9 7 CTM6 Double Action Submodule Modes Window 32MySim32 CTM6 Double Actions Modes DASM ioj xj DASHO4 OPWH Output pulse width modulation S A compare on channel A sets the ouptut pin to logic 1 A compare on channel B clears the ouptut pin to logic 6 DASMOS Channel A captures on a rising edge Channel B captures on a falling edge
41. JE JE JE JE JE IASI ASS 16 Bit Read using Supervisor Program Space at address 6596 Ox48e7 18663 007 472 8 00002D9C3 16 Bit Read using Supervisor Program Space at address 6592 Oxfffe 2 667 472 9 66662D9C6 6596 48E7 FFFE MOVEM L a6 a5 a4 a3 a2 a1 a0 d7 d6 d5 d4 d3 d2 d1 d6 A7 Move Multiple Registers 32 Bit Write using Supervisor Data Space at address FFC4 OxffdG 65488 007 473 0 00002D9C9 32 Bit Write using Supervisor Data Space at address FFC6 6x6 8 667 473 2 88662D9CF 32 Bit Write using Supervisor Data Space at address FFBC 6x6 6 667 473 5 00002D9D5 32 Bit Write using Supervisor Data Space at address FFB8 6x6 6 667 473 7 00002D9DB 32 Bit Write using Supervisor Data Space at address FFB4 6x6 0 667 474 60 66662D9E1 32 Bit Write using Supervisor Data Space at address FFB6 Oxfffele 16776734 607 474 2 BOGG2D9E7 y 32 Bit Write using Supervisor Data Space at address FFAC Oxfffelte 16776734 607 474 4 000O2D9ED 22 Rit Write ucinna Sunernicar Nata Snare at address FFAR AxA AY ARF 7h 7 AAAAINDFA 4 H 2 Ka l x Step 6 667 161 6 666628576 6678 aj Negate SGL s 6 667 161 1 6666 6666 000028578 16 Bit Read using Program Space at address 67E8 6x462a 16426 667 116 86 666628656 16 Bit Read using Data Space at address 6164 x c a 27658 607 116 86 00002B 5 Time Slot 6 667 116 6 6661 6661 666628656 32 Bit Read using Program Space at address 66A8 OxaciffFFF 1467188993 667 116 4 66662B666 Step 6 667 116 4 6666
42. Memory Block Access Control The purpose of the memory block access control is to make a simulated model match the behavior of real hardware For instance you might want to make a ROM read only such that reads are simply ignored or perhaps cause a bus fault An odd access may cause an address fault or an additional wait state Memory block access control allows the required level of control to achieve this This section serves as a high level guide rather than a detailed description Each memory block supports the following access types 8 bit read 8 bit write 16 bit read 16 bit write 24 bit read 24 bit write 32 bit read 32 bit write 64 bit read Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 291 20 Building the Target Environment 64 bit write 128 bit read 128 bit write For each access type the user can specify a number of parameters The following parameters are available Clocks per even access Clocks per odd access Odd access causes bus fault yes no Bus fault yes no Blank access yes no Dock offset applicable docked accesses only Dock function code applicable to docked accesses only In addition there is a block wide default blank access value This is the value that is returned on a read access to a memory block that has been marked as blank Read Write Control It is possible to disable specific types of memory accesses In this example a memory device is configured
43. QACRG 6133 MUX F F Internally multiplexed 16 possible channels PSH 8 4 PSH 13 gt Prescaler clock hi time is 661 192 1 ns PSA 3 3 QCLK high and low times are not modified PSL 2 6 PSL 3 gt Prescaler clock lo time is 666 238 4 ns QACR1 6666 CIE1 F F Queue 1 completion interrupt is disabled PIE1 E E Queue 1 pause interrupts are disabled SSE1 D D Enables a single scan after trigger event l This bit always reads as a zero Mu A 8 Disabled mode conversions do not occur QACR2 6027 CIE2 F F Queue 2 completion interrupt is disabled PIE2 E E Queue 2 pause interrupts are disabled SSE2 D D Enables a single scan after trigger event l This bit always reads as a zero Mu C 8 Single scan mode 3 0 8 Interval is micro seconds l Disabled mode conversions do not occur QASR 6666 CF1 F F Queue 1 scan is not complete PF1 E E Queue 1 has not reached a pause CF2 D D Queue 2 scan is not complete PF2 C C Queue 2 has not reached a pause TOR1 B B No queue 1 trigger events have occured TOR2 B B No queue 2 trigger events have occured Qs 9 6 Queue 1 idle Queue 2 idle CWP 5 6 Conversion Command Word 66 is currently or last executed The QADC Main window displays the QADC Module Configuration Register QADCMCR the QADC Interrupt Register QADCINT the QADC Control Registers 0 1 and 2 QACRO QACR1 QACR2 and the QADC Status Register QASR pa
44. RAM I O and capture match events saved to the trace buffer Trace data can be saved to a file The application wide font can be specified Version 3 10 Enhancements Replaced the set_cpu_frequency command with the set_clk_period script command Additional script commands New call stack window Improved local variables window Improved trace window 1994 2015 ASH WARE Inc page 26 Multi Target Development Tod Reference Manual 3 Software Upgrades Additional 683xx Hardware Debugger support for 68331 68336 68338 and 68376 New TPU Standard Mask Simulator supports 683xx and MPC5xx New local variable options dialog box Additional IDE options Additional operation status windows Version 3 0 Enhancements Source code search rules Enhanced script files Definitions using define declaration Enumerated types Simple expressions Improved assignment operators Breakpoints Complete grammar check at load time Editable register style windows Integrated timers TIMERS_HELP Watch local variable and memory dump windows Workshops Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 27 page 28 Multi Target Development Tool 4 The Project 4 The Project The Project Open and project Save As dialog boxes allow association of the simulator debugger configuration with a project file All settings are stored in this file including the active source code script file selected font spaces per
45. Set 1 Stepper Motor SM function UART ETEC Mode System Simulator Demo e System simulator demo both CPU and eTPU are simulated e Use of the superior ETEC mode style of programming e Conversion of Freescale s UART function to ETEC mode e Freescale s host side API used on a simulated CPU e The Auto generated header files similar to those used in the Freescale standard functions The ASH WARE generated lt gt _idata h file for initializing DATA memory Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 19 2 Demo Descriptions The ASH WARE generated lt gt _scm h file for initializing CODE memory 1994 2015 ASH WARE Inc page 20 Multi Target Development Tod Reference Manual 3 Software Upgrades 3 Software Upgrades World Wide Web Software Deployment All ASH WARE software is now deployed directly from the World Wide Web This is done using the following procedure Download and install a demo version of the desired software product All software products are available at a demonstration level Purchase the software product s either from ASH WARE or one of our distributors E mail to ASH WARE the license file named AshWareComputerKey ack found in the installation directory Wait until you receive an e mail notification that the information from your license file has been added to the installation utility Download and re install again The software product s you purc
46. TDLA TDLB MATCHA MATCHB CAPTUREA CAPTUREB Note that the fields FMO FM1 and PSS refer to sampled values and thus only apply to the current channel and thread time slot transition PSS is re sampled when the chan register is written Syntax for eTPU ALU Register Access eTPU C register types are now supported in symbolic processing in script commands such as print_to_trace verify_val write_val etc and also in the watch window as shown below eTpul Watches x tert U 402 8x192 register TCR1 erta Of 468 0x190 register ERTA chan_base U 768 0x300 register CHAN_BASE ASHchannel CAPTUREB Q 400 0x190 register CAPTUREB DI AC Al In order for this to work the registers must be exposed in a header file In standard the eTPU C headers etpuc h several register variables are exposed by 1994 2015 ASH WARE Inc Reference Manual 6 Script Commands Files default as follows register_chan chan register_erta erta register_ertb ertb register_tcrl tcrl register_tcr2 tcr2 register_tpr tpr register_trr trr register chan base chan_base Others can be defined per the eTPU C syntax for example register_diob diob register_mach mach register_p15_0 p15_0 lower 16 bits of p register See the standard eTPU C headers for details on the syntax of the register types Once defined such variables can be referenced in the watch window or symbolic script commands just like other variables pri
47. TPU2 supports a loading of zero using the parameter RAM sub instruction In the TPU1 one could make use of the undocumented feature that reading from the un implemented parameter RAM returned a zero In this case a zero was able to be effectively loaded This capability is supported in the TPU2 by a direct clear or write of zero using the RAM sub instruction New counter options support a higher resolution faster count for TCR1 and improved edge control clock on rising pin edge falling pin edge or both pin edges for TCR2 These include a DIV2 control bit for TCR1 and a T2CSL control bit for the TCR2 These fields are displayed in the configuration window Script commands for controlling these two bits are described in the TPU Clock Control Script Commands section A Flag2 which is quite similar to Flag and Flag0 has been added A conditional branch can now be made on the current pin state using the PIN conditional This field is displayed in the Execution Unit window Previously only the PSL conditional could be used and the PSL is updated only on a time slot transition or a write to the Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 281 19 Supported Targets and Available Products 19 15 CHAN_REG register The PIN conditional allows a branch based on the most current pin state MRL and TDL can be negated using the TBS field of instruction format three A match can be set to occur on an equal conditi
48. Target Development Tool page 45 6 Script Commands Files 6 5 8 6 5 9 page 46 Multi Target Development Tod define PARAMETER RAM 0x100 define BYTES PER CHAN 16 define SPARK CHAN ADDR PARAMETER RAM BYTES PER CHAN 5 Write a 77 hex byte to address 150 hex U8 SPARK CHAN ADDR 0x22 0x55 The normal C precedence rules can be overridden using brackets as follows write chan func 1 3 4 2 Set chan 1 to function 11 write chan func 1 3 4 2 Set chan 1 to function 14 Syntax for global access of eTPU Function Variables Although eTPU channel variables reside in statically allocated memory scope wise within eTPU C they are treated more like local variables The syntax covered in this section allows developers to access channel variables at any time for debug or verification purposes not just when within function scope The following syntax supports global reference of channel variables by symbolic name The syntax has the form lt channel name gt lt function var name gt Either a raw channel number can be used or the name assigned to the channel in the Vector file works to reference channel variables on a channel PWM3 DutyCycle 5 Period verify_val PWM72 DutyCycle 3500 ASH print_to_trace PPWA channel 3 high time Ox x n 3 HighTime This syntax can be used with the symbolic script commands such as verify_val in the Watch window as we
49. This command runs the seam RAM test at address in the address space ADDR_SPACE for the number of iterations specified by numlIterations This was developed to verify proper functionality of all read and write accesses at the boundary between two memory devices All combinations of even odd and double odd addresses and 8 16 and 32 bit wide accesses are exercised Note that the test assumes that all these access combinations are supported the test will fail if this is not a valid assumption test_byte_order address enum ADDR_SPACE numIterations This command runs the byte order RAM test at address lt address gt in the address space ADDR_SPACE for the number of iterations specified by numlIterations It verifies the byte order of the target processor This was developed to verify proper functionality of shared memory between two targets that have different byte orders A shared memory between two targets that do not have the same byte ordering can be tricky Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 73 6 Script Commands Files 6 6 15 6 6 16 6 6 17 Channel Function Select Register Commands write _chan_func ChanNunm Val This command sets channel CHANNUM to function Val define MY FUN NUM 0x10 write_chan_func 7 0x10 In this example channel 7 is set to function 10 decimal All other channel function selections remain unchanged In the Byte Craft eTPU C compiler the function
50. This file has the same name as the startup script its extension is report There are some restrictions to startup scripts These are listed below No windows are supported Flow control such as breakpoints and single step is not supported Certain script commands are not supported Restricted commands are noted as such in the reference section 6 5 File Format and Features The script commands file must be ASCII text It may be generated using any editor or word processor such as WordPerfect or Microsoft Word that supports an ASCII file storage and retrieval capability The following is a list of script command features Multiple target scripts Directives Enumerated data types Integer data types Referenced memory Assignment operators Operators and expressions Comments Numeric Notation 1994 2015 ASH WARE Inc page 40 Multi Target Development Tod Reference Manual 6 5 1 6 Script Commands Files String notation Script Commands Format The command is case sensitive though this is currently not enforced and in general has the following format command datal data2 data3 The contents within the parenthesis datal data2 and data3 are command parameters The actual number of such data parameters varies with each particular command Data parameters may be integers floating point numbers or strings Integers are specified using either hexadecimal or decimal notati
51. Verify memory script commands provide the mechanism for verifying the values of the target memory The first argument is an address space enumerated type The second argument is the address at which the value should be verified The third argument is a mask that allows certain bits within the memory location to be ignored The fourth argument is the value that the memory location must equal verify _mem_u8 enum ADDR_SPACE U32 address U8 mask U8 val verify _mem_ul6 enum ADDR_SPACE U32 address U16 mask U16 val verify _mem_u24 enum ADDR_SPACE U32 address U24 mask U24 val verify _mem_u32 enum ADDR_SPACE U32 address U32 mask U32 val page 56 Multi Target Development Tod 1994 2015 ASH WARE Inc Reference Manual 6 6 6 6 Script Commands Files This command uses the following algorithm Read the memory location in the specified address space and address Perform a logical and of the mask with the value that was read from memory Compare the result to the expected value Ifthe expected value is not equal to the masked value generate a verification error The following example verifies the value of an 8 bit byte memory location verify mem_u8 ETPU_DATA_SPACE 0x7 Oxc0 0x80 The example above verifies that the two most significant bits found at address 0x7 are equal to 10b The lower 6 bits are ignored If the bits are not equal to 10b a script failure message is generated and the target s script failure coun
52. also displayed The active channel number is displayed Since the active channel can be changed via the microcode when the CHAN register is modified the active channel numbers corresponding to the current previous and second most previous microcycles are displayed The last channel number is that of the channel that was initially being serviced after the time slot transition This allows the user to calculate which channel a particular parameter is associated with for those parameters that take multiple microcycles to adjust after the CHAN register is changed The current opcode and prefetch opcode are displayed in this window Sequencing microinstructions that affect program flow may flush the prefetch opcode causing a NOP to be executed Loading a OXFFFFFFFF as the current opcode simulates this situation The DEC register is used for various purposes such as loop indexing and subroutine termination The current DEC usage is displayed When MtDt is in TPU2 or TPU3 mode the two bank fields are displayed The code bank is the bank in which code is being executed The entry bank is the bank from which the active entry table is stored In the real TPU the entry bank is specified via the TRUMCR2 register at bit positions 5 and 6 In MtDt this entry bank register is modified by the write_entry_bank script command page 206 Multi Target Development Td 1994 2015 ASH WARE Inc Reference Manual 15 Operational Status Windows 15 3 5 TPU Executi
53. and the states of the SRL and the SGL Trace Source Code Automation The trace window and the Source Code window s can be used together Select a line in the Source Code Window associated with an instruction execution The source code file associated with this line automatically pops into view and the associated line scrolls into view and is highlighted in yellow In the TPU trace window shown above the seventh line has been selected The line is automatically displayed and highlighted yellow as shown below page 188 Multi Target Development Td 1994 2015 ASH WARE Inc Reference Manual 15 1 8 15 Operational Status Windows A Tpusim Source pta uc Se wm neg_trans6 if Match then goto accum_time_pta flush Gs Can only be Low Pulse zi au chan_reg chan_reg It s 0 K to update PSL here since si chan neg_tdl there are no more Hatch states oO U6 3 R Soja Start 263636369636 96 96 96 JEJE IE JE JE IE JE JE E JE JE E JE JE E JE JE JE EE 969696 96 96 96 36 JE JE JE JE JE JE JE JE JE JE JE IE JE JE E JE JE E JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JE JEJEJE JEJEJE HE IE Extra code to check for short pulses during flag6 6 states zi e in High and Low Pulse measurement functions JE JE HE JE HE IE JE E HE JE HE JE JE E JE JE E JE JE IE JE JE HE JE JE JE JE JE JE JE E JE JE HE JE JE FE JE JE E JE JE JE JE JE JE JE JE JE JE JE JE JE JE ME JE JEJE HEHE TENE EEE
54. be listed as 22 microseconds Note that this command has been improved starting with Version 4 8 The enabled events specified by the script command all get logged to the trace file even if not enabled in the GUI Any and all events specified in the script command get sent to the trace log file Previously when saving in VIEWABLE mode any and all events in displayed in the trace window were sent to the log file and the parameters passed in the Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 65 6 Script Commands Files script file were ignored This VIEWABLE mode behavior of previous versions was well goofy And the limitation of not being able to continuously log events to the trace file if those events were not enabled in the GUI was beyond goofy it was flat out weak end_trace_stream This command stops tracing to a stream and closes the file so that it can be opened by a text viewer that requires write permission on the file print_to_trace Message This command prints the string Message to the Trace Window assuming it is enabled in the Trace Options dialog box or to a current trace stream if so configured at_time 400 start_trace_stream Stream Trace ALL DIVIDER MEM READ PARSEABLE US 3 1 PLLNC_CO_CLACE HHH HH HHH HHH RR KIRK KIRK IR KKK RR KK RE KK KR RE K p DEE START OF TEST n T e e IO IR II II IO IK He e e IK He He e He He He e KK KK e e KEK D wait_time
55. both the field value and the actual divisor of the prescaler The TCRF displays the filtering options though these are not simulated by the eTPU Simulation engine The Angle Mode AM bit indicates if angle mode is enabled The Tooth Program Register TPR is only used in angle mode This register may be written only by the eTPU code The LAST bit indicates that angle mode should be reset on the next tooth The MISSCNT field indicates how many incoming teeth are expected to be missing such that the angle mode PLL will continue to count synthesized teeth and not wait for incoming physical tooth signals The Insert Physical tooth IPH field allows the eTPU code to tell the angle mode hardware to proceed as if an incoming physical tooth had been detected The HOLD field forces the angle mode logic to halt as if more incoming physical teeth had been detected than were expected The TICKS field specifies the number of angle ticks TCR2 increments that are in each physical tooth As such this is effectively the PLL multiplier for the difference between the frequency of the incoming teeth and the frequency of the synthesized angle ticks The Tick Rate Register TRR should be updated by the eTPU code on each incoming physical tooth It is calculated based on the time difference between the last two incoming physical teeth and specifies the time of each angle tick in TCR1 ticks In order to reduce error both an integer INT and fractional FRAC portion of
56. bypass mode is enabled for reads and if bypass mode is available for writes Enabling bypass mode significantly improves code uploads downloads and window display update rates The PLD Register bit field indicates if a bit within the ASH WARE development board s PLD is set or cleared See the Development Board documentation for a detailed explanation of this bit 1994 2015 ASH WARE Inc Reference Manual 15 Operational Status Windows 15 2 eTPU Specific Windows The following windows are available in the eTPU Simulator and eTPU System Simulator 15 2 1 eTPU Configuration Window eTPU_A Configuration General CPU Frequency 166 666 MHz CPU Clock Latest thread is E steps 6 clocks Active 56 606 Threads 6 Steps 6 Entry Table Base Addr 6666 ETB 66 TCRCLK Input Pin High Active Channel T 6 T 4 6 6 4 Address 6666 Rtn 6666 ETPU Phase Interrupts Not Supported Microcode Global Exception clr Illegal Instruction clr Verification Continuous Behavior Off Behavior Failures 66666666 Script Failures 666000666 Versions Simulator 3 76 Build A Model JPC563N66 1 engine A eTPU 2 Memory 12K CODE 2 5K DATA Code ETEC_cc 1 16 Build A ELF DWARF 2 6 Built for eTPU 2 Entry Point On Pin Direction ETPD Supported Out Of Range Opcode SCHOFFDATAR Supported Files Application Project NtDt Build Source Code Script C2 MNtdt Gui TESTFILES MtDt exe C Ntdt TestsHigh ETpu AutoRunO
57. channels with QADC controlled external multiplexing page 232 Multi Target Development T9 1994 2015 ASH WARE Inc Reference Manual 15 Operational Status Windows 15 11 Miscellaneous Module Windows The following windows display miscellaneous module settings 15 11 1 TouCAN Main Window ESTAT XXXX ses THE ESTAT STATES ARE NOT DISPLAYED ess xxx BECAUSE ESTAT READS ARE INTRUSIVE xxx Receive global mask High is FFEF Receive global mask Low is FFFE Receive buffer 14 mask High is FFEF Receive buffer 14 mask Low is FFFE Receive buffer 15 mask High is FFEF Receive buffer 15 mask Low is FFFE See buffer window See buffer window Receive error counter is 66 Transmit error counter is 66 RXGMSKHI FEEF RXGMSKLO FFFE RX14MsHI FEEF RX14MsLO FFFE RX15MsHI FEEF RX15MsLO FFFE IMASK 454E IFLAG 66600 RXECTR 66 TXECTR 66 32My68376 TouCAN Main 3 ioj xj CANMCR BIS STOP F F TouCAN clocks are ENABLED FR2 E E TouCAN is allowed to enter debug mode HALT C C On FR2 1 TouCan goes to debug mode NotRdy B B TouCAN is in low power stop or debug mode WakeMsk A A Wake up interrupt is ENABLED SoftRst 9 9 Soft reset cycle completed FrzAack 8 8 TouCAN has entered debug mode and the prescaler is Disabled SUPU 7 7 SZU registers access at Supu priviledge level SlfWake 6 6 Self wake is ENABLED APS 5 5 Auto power save ENABLED clocks stop and restart as needed StopAck 4 4 TouCAN is in low power stop
58. clr clr clr clr clr clr clr clr clr clr clr clr clr clr clr The TouCAN Buffers window displays information for each of the 16 buffers For each buffer the status identification high and low eight data bytes interrupt enable disable and interrupt set clear state is displayed 15 11 3 Masked ROM Window 32MySim32 Masked ROM MRMCR ERTS ROMBAH 6456 ROMBAL 4666 RSIGHI 1234 RSIGLO 5678 ROMBS6 1661 ROMBS1 2222 ROMBS2 3333 ROMBS3 12AC STOP BOOT LOCK ASPC WAIT AD HI AD LO RS HI RS LO BS 6 BS 1 BS 2 BS 3 eooooocormrece muon ROH ROH ROH ROH ROM ROM signature signature ROM Write lock enabled ROM array is accessible at the ROM array accesses take 2 wait bootstrap word 6 bootstrap word 1 bootstrap word 2 bootstrap word 3 Base address is 64564666 high register is 1234 low register is 5678 is 1661 is 2222 is 3333 is 12AC ROM array is is in low power stop mode ROM does not responds to bootstrap word locations during reset vector fetch Protected registers and fields cannot be written unrestricted program and data priviledge level states 5 x The Masked ROM window displays the Masked ROM Module Configuration Register MRMCR the ROM Array Base Address High Register ROMBAH the ROM Base Address Low Register ROMBAL the ROM Signature High Register RSIGHD the ROM Signature Low Register RSIGLO and the ROM Bootstrap Words 0 through 3 page 234 Multi Target Deve
59. command processor to execute an operating system command batch file or other program named by the string lt commandString gt Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 61 6 Script Commands Files The first command system ignores the return value while the second command verify_system verifies that the value returned is equal to the expected value returnVal If the returned value is not equal to the expected value than a script verification error is generated system copy c temp report txt check txt verify system fc check txt expected txt 0 In this example the operating system is invoked to generate a file named check txt from a file named report txt The file check txt is then compared to file expected txt using the fc utility A script verification error is generated if the files do not match exit This shuts down the simulator debugger and sets the error level to non zero if any verification tests failed If all tests pass the error level is set to zero The error level can be examined by a batch file that launched the simulator debugger thereby supported automated testing See the Regression Testing section for a detailed explanation of and examples showing how this command can be used as part of an automated test suite print messageString print_pass messageString does not affect exit code in auto run mode These commands are geared toward promoting camaraderie b
60. conjunction with other CPUs and peripherals including multiple CPU32s page 282 Multi Target Development T9 1994 2015 ASH WARE Inc Reference Manual 19 Supported Targets and Available Products 19 16 CPU32 Hardware across a BDM Port The 683xx line of microcontrollers can be debugged using this BDM Debugger Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 283 page 284 Multi Target Development Tool 20 Building the Target Environment 20 Building the Target Environment The simulated or hardware development environment is specified in special MtDt build script files ASH WARE provides standard build scripts for all its products In the vast majority of cases these build scripts are sufficient and therefore effectively transparent to the user But occasionally a user may desire to modify the simulation environment to unlock advanced capabilities This chapter describes how to do so A complete system may consist of multiple CPUs TPUs peripherals and non electrical devices such as automobile engines MtDt supports simulation of such advanced systems using MtDt build script files MtDt build script files are used to create the targets and specify how they interact Theory of Operation MtDt is capable of instantiating and simulating multiple targets allowing them to interact via shared memory while maintaining the correct synchronization and relative timing In addition a rich set of debugging capabil
61. data or text Dump to disassembly file Dump to Motorola SRecord SREC file Dump to Intel Hexadecimal IHEX file Dump to image file Dump to C structure file For each function the address space and memory range can be specified Earlier address ranges are stored in a buffer and can be retrieved using the recall button For the file dump options selecting the change button can specify the file name Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 257 16 Dialog Boxes 16 20 In disassembly dump files inclusion of address raw values addressing mode information and symbolic information can be selected When creating an image file or a C data structure file or when using the fill function the data word size can of 8 16 or 32 bits For the fill function verification after the fill can be selected The find capability allows a specific byte pattern to be located in memory Options include the ability to search for between one and eight sequential bytes as well as the ability to search for both a case sensitive or case insensitive string C data files can be written with the address included within a comment Output format can be either hexadecimal which is the default or decimal Selection of endian ordering is available for where the data size is exceeds one byte This option is available when dumping to an image or a C structure file or when using the find function In cases where th
62. desired line Either method causes the target execution to continue until the desired script command is executed Note that if the active line in the script file is beyond the selected goto line the target is reset and then runs to the desired line A single step capability is also provided in script commands files See the Step Menu section for a detailed explanation Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 177 15 Operational Status Windows 15 1 3 Watch Windows 32 MyBdm32 Watches Iof x global_data D 2004318071 Ox77777777 global_array 7 D 72 H packet size ul 13 Oxd i QO 13 Oxd register DZ D TT A The Watches window displays symbolic data specified by the user Both local and global variables can be displayed within this window See the Local Variable window to automatically display local variables The watches window consists of a series of lines of text used to display user specified watches Watches can be removed moved up or moved down New watches can also be inserted before any current watch or at the bottom of the list The Insert Watch function accesses the Insert Watch dialog box which allows you to select and or modify previously defined watches These functions are accessed from the Options Menu by selecting an action listed in the Watch submenu An equivalent of the Watch submenu is also accessible by right clicking the mouse from within a Watches window The Watches win
63. device for example but have only 50 gigabytes of available virtual memory on your computer the build script file will fail to execute Note that since modern computer systems employ virtual memory the amount of simulated memory can exceed the amount of RAM actually in your computer Adjusting the available amount of virtual memory on your computer can increase the total amount of memory devices that you can simulate A description of how to increase the swap file size of your computer is beyond the scope of this manual 20 1 The Build Script File MtDt supports both debugging and simulation of a variety of targets Since the single MtDt application can both simulate and debug a variety of simulation and hardware targets how does MtDt know what to do Build batch files provide the instructions that MtDt requires to create and glue together the various copies of hardware and simulation targets Although the user is encouraged to modify copies of these files when required in many cases the standard build batch files loaded during MtDt installation will suffice Typical build script files might instantiate a CPU32 and a TPU3 then instantiate RAM and ROM for the CPU32 and then cause the TPU s memory to reside in the CPU s address space MtDt Build Script Commands File Naming Conventions In order to prevent future installations of ASH WARE software from overwriting build script files that you have created or modified ASH WARE recommends th
64. engine can be used both as a stand alone device and in conjunction with other targets including multiple TPUs When used in stand alone mode of primary importance are script commands files and test vector files The TPU simulation engine is used for developing debugging and verifying operation of TPU microcode User microcode is loaded from files currently generated by Freescale s TPU Microcode Assembler These files are loaded into the TPU simulation target s microcode space The storage format is the binary equivalent of the microcode actually executed by the TPU The simulator debugger also displays user microcode source files in source code windows highlighting the line associated with the actual microinstruction being executed Additional TPU operational status information is displayed in various context windows The windows include information about channel control registers host CPU interface registers microengine control registers the scheduler script commands files source microcode files etc The Time Processor Unit TPU The TPU is a microsequencer developed by Freescale for measurement and generation of time critical waveforms It is a single silicon target that is offered on several microcontroller products such as the MC68332 and the HC16 The TPU has two operational modes It can execute microcode out of its internal ROM or it may execute custom microcode out of its internal RAM In order to execute custom microcode
65. expected case or the timeout the failing case at_time T When this command is reached no subsequent commands are executed until T microseconds from the simulation s start time At that time the script commands following the at_time statement are executed wait_time T No script commands are executed until the simulation s current time plus the T microseconds wait_time 33 5 assume current time 50 microseconds set_link 5 wait_time 100 0 set_link 2 In this example at 83 5 microseconds from the start of the simulation channel 5 s Link Service Latch LSL will be set No script commands are executed for an additional 100 microseconds At 183 5 microseconds from the start of the simulation channel 2 s LSL will be set Verify Timing Script Commands The verify timing script command verifies that timing requirements are met The format is as follows verify timer_clks TimingTag MinSysClks MaxSysClks The ActionTag parameter is a string that must match a similarly named timing region within your code The MinSysClk and MaxSysClk parameters describe the allowable minimum and maximum number of system clocks inclusive that execution of the code is allowed to take in order for the verification test to pass If the code takes less time than the minimum or more time than the maximum to execute then a verification error occurs If the code has been traversed multiple times than the verificat
66. for referencing the eTPU s registers enum REGISTERS _U32 REG _P_31_0 enum REGISTERS _U24 REG_A REG _B REG _C_ REG REG_D REG_DIOB REG_SR REG_ERTA REG_ERTB REG _TCR1 REG_TCR2 REG _TICK_RATE REG MACH REG _MACL REG P E enum REGISTERS U16 REG_TOOTH PROGRAM REG RETURN_ADDR REG _P_31_16 REG_P_15_0 1994 2015 ASH WARE Inc Reference Manual 6 Script Commands Files enum REGISTERS U8 REG LINK REG PD 31 24 REG PB 23 16 REG P_15 8 REG P_7_0 enum REGISTERS_U5 REG CHAN enum REGISTERS U1 REG_Z REG_C_FLAG REG_N REG V REG MZ REG MC REG MN REG MV The following are examples of how the enumerated register types are used write_reg32 0x12345678 REG PI verify reg32 REG P 0x12345678 write_reg24 0x123456 REGA verify reg24 REG_A 0x123456 write_reg1l6 0x1234 REG_RETURN_ADDR verify reg16 REG _RETURN_ADDR 0x1234 write_reg5 0x12 REG_CHAN verify _reg5 REG_CHAN 0x12 write_regl 0x1 REG_Z verify_reg1 REG_Z 0x1 E 6 8 12 TPU Register Enumerated Data Types The TPU register enumerated data types provide the mechanism for referencing some of the TPU registers These enumerated data types are used in commands that reference the TPU registers such as the register write commands that are defined in the Write Register Script Commands section There are no enumerated types for the TPU s 8 bit registers and the TPU has no 32 bit registers
67. format VIEWABLE or PARSEABLE the events passed to the script command are those used to determine which events actually get stored Note that similar to the start_trace_stream script command starting with version 4 8 the parameters specified in the script command are no longer ignored when in Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 67 6 Script Commands Files VIEWABLE mode Similar to how PARSEABLE mode always worked VIEWABLE mode now also uses the parameters passed int the script command to datermine which events are stored to the file how the events are formatted etc 6 6 13 Code Coverage Script Commands An important index of test suite completeness is the coverage percentage that a test suite achieves The simulator debugger provides several script commands that aid in the determination of coverage percentages In addition script commands provide the capability to verify that minimum coverage percentages have been achieved A discussion of this topic is found in the Code Coverage Analysis section The following are the script commands that provide these capabilities write_coverage_file Report Coverage verify file _ coverage MyFile uc instPct braPct verify all coverage instPct braPct eTPU Only verify file _coverage_ex MyFile c instPct braPct entPct verify _all_coverage_Ex instPct braPct entPct The write_coverage_file command generates a report file that list
68. generation frequency is set to one MHz This is a convenient test vector frequency because its period of one microsecond makes timing easy to calculate Wave Command The wave command creates and defines a new wave form generator There is no limit to the number of wave commands that may be used in a test vector file The number of wave form generators is equal to the number of wave commands found in the test vector file wave lt GROUP gt lt STATE REPEAT gt lt STATE REPEAT lt gt REPEAT gt end The wave command causes the nodes of GROUP to be stimulated by the state and repeat count pairs STATE REPEAT Multiple states and repeat counts are allowed A special infinite repeat count generates an infinite repeat count This command may span multiple lines An end statement must terminate the command wave OUTPUTS OFF 5 DRIVE_A 1 DRIVE_B 2 3 OFF end The resulting wave form from this example is shown below The wave form begins with signal A and signal B being off for five master test vector clock periods Signal A is then driven for one period Then signal B is driven for two periods These three states constitute a loop which executes three times After the loop has executed three times the OFF state is driven forever Note that the NODE GROUP STATE and FREQUENCY commands are omitted from this example for simplification purposes page 120 Multi Target Development Td amp 1994 2015 ASH WARE Inc Reference Manual 8 6
69. is supported FILTER_ETPU_ENTRIES Ignore entry table code for disassembly purposes and consider it fully covered so it is ignored in non covered only mode Example write_coverage_listing_file CoverageListing c temp CL_100percent_nc_filter 1st NON_COVERED_ONLY_LINES FILTER_ETPU_ENTRIES RAM Test Script Commands RAM test script commands provide a method for verifying internal or external RAM These tests provide both a verification capability and a diagnostic capability test_address_lines startAddress stopAddress enum ADDR SPACE numIterations This command runs the address line RAM test between stopAddress and startAddress in the address space ADDR_SPACE for the number of iterations specified by numlterations The test attempts to provide diagnostics on any errors For instance it will attempt to isolate specific address lines as stuck high or stuck low and if successful will report the suspected problem Note that this test verifies only those address lines that are dynamic within memory range being tested For instance address bit 16 which selects between 64K blocks will not be tested unless the memory block straddles a 64K block boundary test_data_lines startAddress stopAddress 1994 2015 ASH WARE Inc Reference Manual 6 Script Commands Files enum ADDR SPACE numIterations This command runs the data line RAM test between stopAddress and startAddress in the address space ADDR_SPACE for the
70. location then the following location would be searched This location is established by using the location of the main build file as the starting location for the ControlLaws relative path C MainBuild ControlLaws 5 2 Supported Compilers and Assemblers We will be adding support for compilers and assemblers based on customer demand A list of these can be found on our Web site Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 33 page 34 Multi Target Development Tool 6 Script Commands Files 6 Script Commands Files Overview Script commands files provide a number of important capabilities Script commands files provide a mechanism whereby actions available within the GUI can be automated Build script commands are used by the simulator debugger to build a full system out of various targets cores In the eTPU Simulator Script commands can be used in place of the host CPU Each script commands file is arranged as a sequential array of commands i e the simulator debugger executes the script commands in sequential order This allows the simulator debugger to know when to execute the commands Timing commands cause the simulator debugger to cease executing commands until a particular point in time At that point in time the simulator debugger begins executing subsequent script commands until it reaches the next timing script command Timing commands are not allowed in startup or MtDt build script file
71. longest thread address to display this location in the source code window and to show this time in the Logic Analyzer window eTPU Scheduler Window eTpul Scheduler RS if lol x 1F 1E 1D 1C 1B 1A 19 18 17 16 15 14 13 12 11 16 F E D C BA 8 7 65 4 amp 4 3 21 86 Prty ee eme e e HI HI HI HI HI HI HI HI HI HI HI HI HI HI HI HI HI HI HI HI Srl 6 6 6 6 6 6 ABA 6 6 6 6 6 6 6 B86 6 6 6 6 6 6 6 BA 6 6 6661 6 6 Sol 6 6 6 6 6 WC 6 6 6 6 6 6 8B 6 6 6 6 6 6 6 A 6 6 6 6 6 6 6 B HSRR 6 6 6 6 6 6 6 B 6 6 6 6 6 6 6 B 6 6 6 6 6 6 6 B 6 6 6 6 6 6 AB LSR 6 6 6 6 6 6 6 B 6 6 6 6 6 6 6 6 6 66 6 6 6 6 6 6 6 6 6 6 6 B H TSR 6 G6 6 6 6 6 6 6 6 6 6 6 6 6 BA 6 6 6 6 6 6 6 B6 6 66661 6 4 Time Slot Assignments Med Hi Lo Hi Med Hi Hi The eTPU s microengine responds to the various channels based on a round robin scheduler The scheduler bases its servicing decisions on the Channel Priority Register CPR the Service Request Latch SRL and the Service Grant Latch SGL These latches are affected by the Host Service Request Register HSRR the Link Service Requests LSRs and the Match or Transition Service Requests M TSRs which are also displayed The M TSR is generated from the Match Recognition Latch MRL Transition Detection Latch TDL and the Match Transition Service Request Inhibit SRI latch The M TSR is formed from the following logical expression MRL and TDL or SRI Each register is broken down by eTPU channel so t
72. not occured Interrupt is level 1 Interrupt arbitration bit 3 is SET Concatenated with BIUMCR IARB 2 6 Tine base bus The CTH2C clock input pin is Low The counter clock source is PCLK1 The value of the FCSH counter register is 23D2 The CTM4 CTM6 Free Running Counter Submodule window displays the FCSM Status Interrupt Control Register FCSMSIC and the FCSM Counter Register FCSMCNT 15 9 3 CTM4 CTM6 Modulus Counter Submodule Window HEHEHE HEHEHE IEEE HCSH62 SIC 2921 COF IL IARB3 DRU IN2 IN1 EDGE CLK CNT 1232 ML 1232 HHH HH HH HHH HMHCSH SIC 6666 COF 4 O x HHH HHH HHH HHH HHH HHH HHH HHHKKKKKKKRKRKRKKRHHRHHH A A overflow has not occured Interrupt level is level 2 Interrupt arbitration bit 3 is SET Concatenated with BIUMCR IARB 2 6 Time base bus A is driven The CTH2C clock input pin is Low The CTD9 modulus load input pin is Low CTD9 edge detection negative edge only The counter clock source is PCLK2 Counter register value is Modulus latch value is 1232 HEHEHE HEHEHE HEE HEE EEE EEE EE EEKEEKEEEEEKEEEEEE A overflow has not occured ha H The CTM4 CTM6 Modulus Counters Submodule window displays the MCSM 2 and 11 Status Interrupt Control Registers MCSM2SIC MCSM1ISIC the MCSM 2 and 11 Counter Registers MCSM2CNT MCSMI1CNT and the MCSM 2 and 11 Modulus Latch Registers MCSM2ML MCSM11ML page 226 Multi Target Development T9 1994 2015 ASH WARE Inc Reference Ma
73. section On the eTPU TPU each of these script commands has a unique number as follows Channel interrupts for channels 0 31 are numbered 0 31 Data interrupts for channels 0 31 are numbered 31 63 The global exception interrupt number is 64 Channel interrupts for channels 0 15 are numbered 0 15 The define is formed using the target name as follows _ASH WARE _ lt TargetName gt _ISR_ When running under a target named eTPU_A the ISR script loaded for channel 25 s channel interrupt is automatically defined as follows define _ASH WARE _eTPU_A_ISR 25 If this same script command file is also loaded for the DATA interrupt then the automatic define would be as follows define ASH WARE _ETPU_ISR 57 1994 2015 ASH WARE Inc page 102 Multi Target Development Tho Reference Manual 6 Script Commands Files An example of how this can be used is as follows define THIS ISR_NUM _ASH WARE ETPU_ISR_ define THIS CHAN NUM _ASH WARE _ETPU_ISR_ amp Ox1F clear _this_intr Write a signature to indicate that this ISR ran write_chan_data24 THIS CHAN NUM Op OxFD12A4 THIS_ISR_NUM Passing Defines from the Command Line When launching the simulator debugger it is often useful to pass define directives to the primary script commands file from the command line This is explained in detail in the Regression Testing section The following command line is found in the batch files u
74. space might actually be employed Second the multiple address space model provides the required mechanism for support of advanced simulation features These mechanisms do not necessarily exist in the actual hardware For example an engine modeling CPU might be set up to query and modify TPU channel I O pins To support this the TPU pins have been exposed in a purely theoretical PINS address space MtDt can be configured so that a read or write in the engine modeling CPU s DATA_SPACE occurs in the TPU s PINS space thus allowing the engine modeling CPU to react to and drive the TPU s pins This mechanism does not have a hardware corollary but it provides the powerful capability of simulating the full system In many cases a uniform address model is desirable This is achieved by mapping all address spaces to the same physical memory The following diagram depicts the address spaces accessed by the TPU simulation engine TPU CODE Space TPU DATA Space TPU Pins Space FFFFFFFF FFFFFFFF FFFFFFFF Unused Unused Unused The TPU simulation model fetches code between 0 and 1FFF hexadecimal from its CODE space It accesses its parameter RAM and host interface registers between 0 and 1FF hexadecimal of its DATA space And it accesses its channel pins in the first four bytes of a simulated PINS space Note that its code banks are unrolled and placed linearly in memory Reference Manual C 1994 2015 ASH WARE D Target Development Too
75. tab enabled disabled messages etc To open an existing project file either double click on the file from Microsoft Windows Explorer or from the Files menu select the project Open submenu Then select the name and existing project file Various settings from the just opened project file are loaded into the simulator debugger Note that before opening the new project file you are given the option to save the currently active settings to the currently active project file To create a new project file from the Files menu select the Save As submenu Then specify a new file name At startup global settings are retrieved from the last active project file assuming that no project file was passed on the command line Otherwise the project file passed on the command line is opened The paths to all other files are stored and retrieved relative to the project file This allows the entire set of project files to be bundled and moved together as a group Whenever the simulator debugger is exited the configuration is automatically written to the active project file Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 29 page 30 Multi Target Development Tool 5 Source Code Files 3 Source Code Files Source code files is built using code build tools For TPU Freescale s TPU Microcode Assembler must be used For CPU32 targets industry standard compilers such as Introl Diab Data or GNU can be used For the e
76. text into a single command line parameter Consider the case where a filename is to be passed into the simulator debugger A good way of doing this is to define a string then use the dump_file script command as follows define FILE_TO_DUMP n MyDataFile dat dump_file 0 0x28 ETPU_DATA_SPACE FILE_TO_DUMP IMAGE DATAS8 It is possible to pass the FILE_TO_DUMP define into the simulator debugger from the command line instead of having it in the script commands file using the following command line parameter dFILE_TO_DUMP MyDataFile dat There are four quote characters in the command line parameter shown above The first and last quote characters are used by Windows to bunch everything between them together into a single command line parameter which would for example allow spaces to Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 141 9 Functional Verification 9 7 9 8 page 142 Multi Target Development Tho appear within the single parameter But the filename MyDataFile dat is a string and strings must be surrounded by quote characters in the script commands file This is accomplished by preceding the quote character with the backslash character Windows interprets this backslash quote combination literally and the quote character is thereby passed along with the filename into simulator debugger File Location Considerations Although this discussion is equally applicable to s
77. the Open Primary Script File dialog box By selecting this submenu the actions set up in the Open Primary Script File dialog box are quickly repeated without having to actually open the dialog box The Primary Script Report Submenu This opens the Save Primary Script Commands Report File dialog box This report file is generated when the primary script commands file is parsed The Startup Script Open Submenu This opens the Open Startup Script Commands File dialog box This script commands file is executed after the simulator debugger resets its targets The Vector Open Submenu This opens the Open Test Vector File dialog box The Vector Fast Submenu This provides a fast repeat load test vector file capability By selecting this submenu the last loaded test vector file is reloaded The Project Open Submenu The Project Open submenu opens the Project Open dialog box Each dialog box provides a project session capability where the simulator debugger settings are associated with Project files This submenu allows the user to open a previously saved project session The Project Save As Submenu The Project Save As submenu opens the Project Save As Dialog Box Each dialog box provides a project session capability where the simulator debugger settings are associated with Project files This submenu provides the capability to both create a new Project file and overwrite an existing project file with the currently active configuration T
78. the ratio of TCR1 counter ticks to TCR2 ticks is supported In angle mode the TCR2 s tick rate is proportional to angle instead of time As such the TCR2 counter may be reset when it completes a cycle which is every 720 degrees in a typical car The number of such cycles since the last reset is shown as are the number of PLL synthesized teeth and the number of synthesized angle ticks Additionally the current angle is shown which is based on a default of 720 degrees per cycle The default teeth per cycle and degrees per cycle can be overridden using the set_angle_indices script command as explained in the eTPU Time Base Configuration Script Commands section The STAC bus is used share the TCR1 and TCR2 global counters between eTPU engines such that say the angle TCR2 used in both eTPU_A and eTPU_B is identical Script commands to do this are in the STAC Bus Script Commands section Some analysis is provided of the operational state of angle mode Angle mode is in normal wait or high speed depending on whether the PLL is on track ahead or behind Channel 0 can be programmed to form a sampling window and the open or closed state of this window is displayed The edge which the angle mode hardware is displayed and it should 1994 2015 ASH WARE Inc page 196 Multi Target Development Tho Reference Manual 15 Operational Status Windows be noted that this edge must be programmed to correspond the edge that is also shown which is the
79. then the time at which the thread occurs appears as a yellow vertical line in the logic analyzer window and the time at which the thread occurred is shown as the context time in the logic analyzer window as shown below To re execute this thread grab this context time by moving the cursor over the context time such that an open hand appears and depressing the left mouse button such that a closed hand appears With the left mouse button depressed move the closed hand cursor to the right Position the cursor over the field labeled current time and then release the left mouse button The simulation will reset then run until it reaches the context time which was the time at which the worst case thread executed page 184 Multi Target Development TAS 1994 2015 ASH WARE Inc Reference Manual 15 Operational Status Windows eTpu1 Logic Analyzer RevB e RevThreads e KR Avto Seroll ml b GAS 3 280 361 8 nS Mouse 3 393 293 1 nS Data Start 000 000 0 nS Context 3 332 040 0 nS Current Time 3 382 000 0 nS Left Cursor 112 931 3 nS Delta Cursor 3 167 430 5 nS Right Cursor 3 280 361 8 nS The window shown below is similar to the window set to the ARINC_FX function except that it is configured to show only the information from the channel named RcvA Note that this name has been assigned to this channel in the test vector file using the NODE command as defined in the test vector file section Be
80. transition behavior verification file name is displayed This new feature supports the verification of TPU behavior against previously saved pin transition behavior files This allows the user to make changes to a test suite and automatically determine which pin transition behaviors have changed and which behaviors have stayed the same See the Pin Transition Behavior Verification section ISR Files The currently loaded script commands ISR files associated with each TPU interrupt are listed Script commands files can be associated with TPU interrupts When the interrupt associated with a particular TPU channel becomes asserted the ISR script commands file associated with that channel gets executed Script commands ISR files are loaded using script commands See the ISR Script Commands Files section for a description TPU Host Interface Registers Window 32 MyBdm32 TPU Host I F Ps x FEDceBA9 8 7 65 43 21 86 crsk E 6 6 6 6 6 6 6 6 6 8 6 6 O O O HOOO OOOO 6500 6000 CPR 66 og op op op op OO OO op op op OO OG OO op op HBB BBB HSRR 66 66 66 OO op OO OO OO OO op OO op 66 op op op ong BABB HSQR 66 66 66 GG op OO op 66 oo op OO op OG op OG op gong BABB CISR 6 6 6 6 6 6 6 6 6 6 O O 6 nn Q Gong CIER 6 6 6 6 6 6 6 6 6 6 6 O 6 6 O Gong This window displays common TPU CPU registers whose function is primarily to control These registers include the Channel Function Select Registers CFSRs Channel Priority Registers
81. vector coverage for this case is to be clever in designing a test For example you might inject two very short pulses into two channels running the same function The channels will be serviced sequentially so if you keep the pulse width shorter than the thread length than the second thread will execute with the input pin low The second situation in which it may be difficult to achieve complete event vector coverage is when there are multiple event vectors that handle invalid cases For instance all functions must handle links even when a link is not part of the functions normal operation Such a link could occur if there was a bug in another function Since there are number of such invalid situations they are typically grouped As such it may be justified to bundle these together using the following script command This command allows coverage of a single event vector to count as coverage for other inferred event vectors infer_entry_ coverage FuncNum FromEntryIndex ToEntryIndex Consider the following thread labeled invalid_flagO This thread is never expected to Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 69 6 Script Commands Files occur because the function clears flag0 at initialization and flag0 is never set So thus state which handles a match or transition event in which the flagO condition is set should never execute eTpu1 Source MeasurePeriod c x else if IsMatchBOr
82. very end of a script commands file that is page 42 Multi Target Development Tod 1994 2015 ASH WARE Inc Reference Manual 6 5 3 6 5 4 6 Script Commands Files part of an automated test suite It allows behavior dependent on the test conditions Note that _ASH_WARE_AUTO_RUN_ is automatically defined when the simulator debugger is launched in such a way that it runs without user input In this case upon reaching the end of the script file the simulator debugger is closed when it is part of an automated test suite and otherwise a message is issued to the user Script Enumerated Data Types Many defined functions have arguments that require specific enumerated data as arguments Internally enumerated data types are defined for many script commands and the tighter checking and version independence provided by enumerated data types make them an important aspect of script files In general the enumerated data types are defined for each specific target or script file application The following is an example of an internally defined enumeration enum TARGET_TYPE TPU_SIM ETPU_SIM SIM32 BDM32 Note that in C it would be possible to pass an integer as the first argument and at worst a warning would be generated In fact in C even the warning could be avoided by casting the integer as the proper enumerated data type This is not possible in a script file because of tighter checking and because casting is not supported S
83. write_engine_data24 AddrOffset Val write_engine_datal6 AddrOffset Val write_engine_data8 AddrOffset Val verify engine_data32 AddrOffset Val verify engine_data24 AddrOffset Val verify engine_datal6 AddrOffset Val verify engine datap AddrOffset Val 1994 2015 ASH WARE Inc Reference Manual 6 Script Commands Files These commands write engine data at address AddrOffset to value Val or verify that the data at address AddrOffset matches value Val Note that 32 bit numbers must be located on a double even address boundary 0 4 8 that 24 bit numbers must be located on a single odd boundary 1 5 9 that 16 bit accesses must be located on even boundaries 0 2 4 and that 8 bit numbers can be on any address boundary The address is formed by adding the engines base address see ERBA with the address formed in the by the Addroffset field See the System Configuration Commands section for information on how the Engine Relative Base Address ECR ERBA field is writtenwrite_engine_data32 0x20 0xC6E2024A verify engine_data32 0x20 OxC6E2024A verify engine_data24 0x21 OxE2024A verify engine_datal6 0x20 OxC6E2 E verify engine_datal 6 0x22 Ox024A verify engine datap 0x20 0xC6 Js verify_engine_data8 0x21 OxE2 ks verify engine datap 0x22 0x02 verify engine datap 0x23 Ox4A In this example data at an address offset of 0x20 relative to that eTPU s engine base address wo
84. 0 2 4 and that 8 bit numbers can be on any address boundary define UART_ CHAN 12 write_chan_data32 UART_CHAN 0x20 OxC6E2024A verify chan_data32 UART_CHAN 0x20 OxC6E2024A verify chan_data24 UART_CHAN 0x21 OxE2024A verify chan_datal6 UART_CHAN 0x20 0xC6 E2 E verify chan_datal6 UART_CHAN 0x22 Ox024A verify chan dartap UART_CHAN 0x20 0xC6 E verify chan_data8 UART_CHAN 0x21 OxE2 ys verify_chan_data8 UART_CHAN 0x22 0x02 E verify chan_data8 UART_CHAN 0x23 Ox4A In this example channel 12 s data at an address offset of 0x20 relative to that channel s base address word is written with a 32 bit value OxC6E2024A hex The written value is then verified as 32 24 and 8 bit sizes In the Byte Craft eTPU C Compiler the address offset can be generated using the following pragma in the code pragma write h define MY_ADDR_OFFSET ETPUlocation Pwm MyFunc Var The ETEC eTPU C Compiler automatically generates all needed address data into the auto defines file no explicit user effort is required Bitwise access to parameter RAM is supported with a set of matching functions to those above write_chan_bits32 ChanNum AddrOffset BitOffsetFromMSB BitSize Val write_chan_bits24 ChanNum AddrOffset BitOffsetFromMSB BitSize Val Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 85 6 Script Commands Files 6 6 26 6 6 27 page 86 Multi Target Dev
85. 1 are allowed values This control bit determines whether the TPU3 s new and enhanced prescaler is used or the standard prescaler is used With the enhanced prescaler the resolution of the clock period is controllable in 3 increments of the longest clock period write_epsckv Val This command writes the TCR1 enhanced prescaler value Only values between 1 and 31 are allowed Assuming the EPSCKE bit is set the clock frequency fed to the TCR1 prescaler is the system clock divided by the TCR1 enhanced prescaler where the enhanced prescaler is equal to EPSCKV plus 1 times 2 write_epscke 1 write_epsckv 20 write_tcrl_prescaler 2 Available in all TPUs The three commands in this example set the TCR1 counter to increment at 99 87 KHz 1994 2015 ASH WARE Inc page 94 Multi Target Development Tod Reference Manual 6 6 37 6 Script Commands Files assuming the CPU clock is set to 16 778 MHz write_tcr2psck2 Val This command writes the TCR2 pre divider prescaler The only allowed values are 0 and 1 This with the next command select the system clock 8 write _t2cg 1 write_t2cs1 0 Set the TCR2 prescaler to divide by 8 write_tcr2_ prescaler 3 Set the pre divider prescaler to divide by 2 write_tcr2psck2 1 The above script command sequence sets the TCR2 counter to be clocked at the system clock frequency divided by 128 TPU Bank and Mode Control Script Commands set_tpu_type X Y Th
86. 2 multiple targets simulation model named Cpu32 Vector File v lt VectorFileName gt v MyVector vector Loads the specified vector file single target DevTool only Vector File v MyVector Loads the specified vector v lt VectorFileName gt vector oCh Core file into the specified target lt TargetName gt multiple targets DevTool only Define as true d lt DefinedText gt dCODE_BASELINE In script commands file Passes the define define DefinedText 1 CODE_BASELINE 1 to the script file Define as value d lt DefTxt gt lt Val gt dMY_VAR 55 In script commands file Passes the define define DefTxt Val MY_VAR 55 to the script file Build Define bd lt DefinedText gt bdMPC5674_2 In MtDt build script define Defines MPC5674 as true the DefinedText as true in the build define such that the MPC5674 rev 2 model is loaded Log File If5 lt FileName log gt lf5Error log Logs messages to end of Logs messages to file Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 139 9 Functional Verification page 140 Multi Target Development Tho Log File Test Suite Mode IfmTestSuite IfmTestSuite Outputs formatted Sets logging to test suite messages and extra mode only applies if verification information into logging enabled via If5 the log file when specified Useful when using the tool for verification purposes Test Name tn lt TestName gt tnPu
87. 2 script commands to write Engine Relative RAM Script commands to write the STAC bus which support sharing of the TCR1 and TCR2 global counters across eTPU engines Version 3 80 Enhancements eTPU2 script command to write the Engine Relative Base Address register Version 3 70 Enhancements CRITICAL CHANGE eTPU Engine A and B ISR Auto define eTPU2 Stand Alone Simulator Product2_SIM status ALPHA Support for the new STMicroelectronics Freescale SPC563Mxx eTPU2 microcontrollers Version 3 60 Enhancements In Dual eTPU simulation configurations one eTPU engine can drive the I O pins of the other eTPU Engine See the eTPU TPU External Logic Commands section for more information Added support for MPC5553 MPC5534 MPC5565 MPC5567 and MCF5270 1 derivatives Instrument your code with named timers TIMER_ACTION_HELP to verify that critical timing indices are met Use timing verification script commands to verify that traversal times meet application requirements View the latest traversal times in the Watch window Version 3 50 Enhancements eTPU C provides a built in type called chan_struct that allows access to such channel specific settings as IPAC OPAC PDCM TBS etc This symbolic access to channel settings has now been exposed in the eTPU Simulator For example to issue an TDL event on channel five write_val 5 ASHchannel TDLA 1 eTPU C register types are now supported in symbolic processing wa
88. 259 16 23 BDM Port Dialog Box eececeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeseeeeeeeseeeeeeeseeeeeeesees 259 Part 17 Menus 261 Dt Fles MOU aoga anara ae ir ARARSA ELAN AAAA ARAF A AAA TAAA AA NEA 261 17 2 C e ln Le WT 264 17 3 RUNNIN MEET 265 174 Ee UE 267 17 5 Workshopsessie sce ccc es Seetic ee decrec haceidecedeeree dee cntceedecseccheesiiecieceeeeneeed 268 17 6 View MQM iersinii aanaeio an EEANN EEA EAN EARRAN Aan EiS 268 LC Window Menu sicrie eraran nsr EAR E ENTES TAATA EANTA 269 17 8 Options Menu ssssssssssnnunnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn nennen nnmnnn 269 179 Help Monunuo ai an a EE EN EA EONA 271 Multi Target Development Tool page 9 Multi Target Development Tool Part 18 Hot Keys Toolbar Status Window Part 19 Supported Targets and Available Products 19 1 MC33816 Hardware Debugger 0cecscceeeeseeeeeeeseeeeneeneeeeeeees 19 2 MC33816 CPU System Simulator c ccseeeeeeeeeeeeeeeeeeeeees 19 3 eTPU CPU System Simulator 2 0cccceeeeeeeeeeeeeeeeeeeeeeeeeeeees 19 4 TPU CPU32 Full System Simulator ceeeeeeeeeeeeeeeeeees 19 5 MC33816 Stand Alone Simulator ceeeseceeeeeseeeeeeeeeeeeeeees 19 6 eTPU2 Stand Alone Simulator ccccceeeseeeeeeeeeeeeeeeeeeeeeeees 19 7 eTPU Stand Alone Simulator cccccceeeeeeeeeeeeeeeeeeeeeeeeeeeees 19 8 TPU Stand Alone Simulator cccceceeeeeseeeeeeeseeeeeeeneeeeeeees 19 9 683xx Hardware Debugg
89. 272 Multi Target Development Td amp 1994 2015 ASH WARE Inc Reference Manual 18 Hot Keys Toolbar Status Window 18 Hot Keys Toolbar Status Window Pointing and clicking with the mouse activate Toolbar buttons The toolbar is located toward the top of the main screen Toolbar buttons also allows you to quickly switch between workshops These are the text buttons located at the top right of the main screen An execution status indicator appears at the top right of the main screen This indicator appears as a moving error while the targets are executing When the targets are stopped a bitmap appears that depicts the cause of the halt An active target button appears at the top right of the main screen This button lists the active target Depressing this button causes a list of all targets to appear as a menu Selection of a target from this menu causes that target to become activated The status window is located at the bottom of simulator debugger Miscellaneous information is displayed in this window Both the toolbar and the status window can be hidden as explained in the Options Menu section At the bottom right of the main window is a menu help indicator This indicator shows the function of all menus and toolbar buttons prior to selection Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 273 18 Hot Keys Toolbar Status Window To the right of the menu help indicator is the ticks angle indic
90. 28666 66A8 32 Bit Read using Program Space at address 66AC OxahkGdFFFF 1542586369 667 116 5 66662B662 Step 6 667 116 5 666628662 BHAC 32 Bit Read using Program Space at address 66B6 Ox673bFFFF 1731985467 007 110 66662B664 apen 087 110 6 oneenn en gen TT EC ly The Trace window displays information relating to the instructions that were executed The Trace window displays all information that has been stored in the trace buffer See the Trace Options Dialog Box section for information on how to modify the information that is stored in this buffer The contents of the trace window can be saved to a trace file This is helpful for post processing of the trace data See the Trace Buffer and Files section for information on how this is done For most simulation models the data flow between processor and memory can be displayed Timing information is included but it should be noted that the most ASH WARE simulation models use an intuitive rather than a true timing model so these will vary slightly relative to the real CPU TPU or other target model type Note that in hardware targets like the 683xx Hardware Debugger this window will not function correctly because many hardware targets do not contain trace buffers Therefore MtDt does not know which instructions executed last The instructions that are displayed are those from previous single steps of the target Gaps in the trace buffer are noted and the displayed execu
91. 33816_DATA_ SPACE INVALID The same value cannot be added or subtracted to itself TPU_PINS_ SPACE TPU_PINS SPACE C 1994 2015 ASH WARE D Target Development Tool page 109 6 Script Commands Files 6 8 10 Build Script READ_WRITE Enumerated Data Type 6 8 11 page 110 Multi Target Development Tho This enumerated data type is used when specifying the applicable read and or write cycles for various build script commands enum READ WRITE RW_READ8 RW_READ16 RW_READ24 RW_READ32 RW_READ64 RW_READ128 RW_WRITE8 RW_WRITE16 RW_WRITE24 RW_WRITE32 RW_WRITE64 RW _WRITE128 RW_ALL D Some mathematical manipulations are allowed Single instances of all but the RW_ALL values can be added together and single instances of each value may be subtracted from RW_ALL define SOME_READS RW_READ8 RW_READ16 RW_READ32 define NON_ACCESS32S RW_ALL RW_WRITE32 RW_READ32 In this example ALL_READS is defined as any read access be it an 8 16 or a 32 bit read cycle NON_ACCESS32S is defined as all 8 16 24 64 and 128 bit read and write cycles eTPU Register Enumerated Data Types The eTPU register enumerated data types provide the mechanism for referencing the eTPU registers These enumerated data types are used in commands that reference the TPU registers such as the register write commands that are defined in the Write Register Script Commandssection The following enumeration provides the mechanism
92. 4 U24 enum REGISTERS_U24 write _reg32 U32 enum REGISTERS_U32 write _reg64 U64 enum REGISTERS _U64 write_reg16 0x5557 REG_DIOB In the above script command example 5557 hexadecimal is written to register DIOB Register Verify Script Commands Verify register script commands provide the mechanism for verifying the values of the target registers The first argument is aeTPU register enumerated type CPU232 register enumerated type with a definition that depends on the specific target and register width on which the script command is acting The second argument is the value against which the register will be verified verify regl enum REGISTERS OI U1 verify reg4 enum REGISTERS U4 U4 verify reg5 enum REGISTERS_U5 U5 verify reg8 enum REGISTERS_U8 U8 verify reg16 enum REGISTERS U16 U16 verify reg32 enum REGISTERS U32 U32 verify reg64 enum REGISTERS U64 U64 verify reg16 REG_DIOB 0x5557 In the script command example above register DIOB is verified to be 5557 hexadecimal If not a script failure message is generated and the script failure count is incremented Symbol Write Script Commands Write symbol value script commands provide a mechanism for writing data to simulated target memory using the symbolic names from the source code The write_val command is for writing data of a basic type to a symbolically referenced memory location write_val symbolExprString exprString The express
93. 5 SCI receive recieve data register flag RDRF f and overrun error OR interrupts are disabled ILIE 4 4 Idle line interrupts are disabled TE 3 3 SCI receiver is disabled TXD pin can be used as I 0 RE 2 2 SCI receiver is disabled status bits inhibited RWU 1 1 Normal receiver operation received data recognized SBK 6 6 Normal operation SCSR 6186 TDRE 8 8 A new character can now be written to register TDR Te 7 7 SCI transmitter is idle RDRF 6 6 Receive data register RDR is empty or contains previously read data RAF 5 5 SCI receiver is idle IDLE 4 4 SCI receiver did not detect an idle line condition OR 3 3 Receive data register RDRF is cleared before new data arrives NF 2 2 Noise was not detected on the received data FE 1 1 A framing error or break was not detected on the received data PE 6 6 A parity error did not occur on the received data SCDR 6656 RDR 8 6 Receive data register 6056 read only 8 0 Transmit data register 6655 write only read value is meaningless The QSM SCI window displays the SCI Control registers 0 and 1 SCCRO and SCCR1 the SCI Status Register SCSR and the SCI Data Register SCDR 15 7 TPU Module Windows The following windows display the Time Processing Unit TPU module settings 15 7 1 TPU Emulation RAM Window 3 MyBdm32 Standby RAM Joj x TRAMMCR ERS STOP EE RASP gg F 3 6 8 TPURAM Module is o
94. 64 796 8 666613A66 No more pending interrupts No more pending interrupts v ER un The CPU32 Simulator Interrupt window displays detailed information regarding the currently pending CPU32 interrupts Towards the top are the highest priority first to be serviced interrupts and towards the bottom are the lowest priority last to be serviced interrupts Once interrupts are serviced they are removed from this window page 212 Multi Target Development T9 1994 2015 ASH WARE Inc Reference Manual 15 Operational Status Windows 15 4 4 BDM32 Configuration Window 32 MyBdm32 Configuration Iof x Files Project MtDt Build C TESTFILES BuildScripts 1Bdm32 MtDtBuild Source Code main e68 Script No File Open Script Report No File Open Script Startup Startup Cpu32Command Build No File Open Verification Script Failures 660606666 Files The name of the project file is displayed See the Project Sessions chapter for a detailed explanation of this capability The name of the MtDt build script file is displayed See the Building the Target Environment chapter and the MtDt Build Script Commands File section for detailed explanations of the available capabilities and format of this file The names of the open source code executable image primary script primary script report and startup script files are displayed These files are listed relative to the path of the open project file The auto build file name is displaye
95. AUSE no 16 QCLK s 622 888 2 19 gt PQA 6 ANG 8308 7266 F266 4 621F PAUSE no 2 QCLK s 662 861 6 1F gt A corp BECO 3EC 5 62FF PAUSE no 16 QCLK s 022 888 2 3F gt PQA ZAN 3EF 7BCO FBCS O2FF PAUSE no 16 QCLK s 022 888 2 3F gt PQA 6 AND O3BE 6F86 EFSS 7 62D1 PAUSE no 16 QCLK s 622 888 2 11 gt PQA 6 ANG DER FACO FACE 8 mr YES 16 QCLK s 622 888 2 3F gt PQA 6 ANG 3FA Con FE8 9 O3FF PAUSE YES 16 QCLK s 022 888 2 3F gt PQA 6 AND pt FD40 phg A 3FF PAUSE YES 16 QCLK s 622 888 2 3F gt PQA 6 ANG 866F YBCO 1BCE B gong PAUSE YES 16 QCLK s 622 888 2 18 gt PQA 6 ANG pont 7786 F780 c OO7F no 4 QCLK s 005 722 0 3F gt PQA 0 ANG port BFCG 3FCA D 3BE PAUSE YES 8 QCLK S 011 444 1 3E gt PQA 6 ANG mort 7FCO FFCS E 3FE PAUSE YES 16 QCLK s 622 888 2 3E gt PQA 6 ANG mort 7FCG FFCS F O15F YES 4 QCLK S 005 722 6 1F gt PQA 0 ANG 83D9 7640 F646 16 mp YES 8 QCLK S 611 444 1 3E gt PQA 0 ANG OOFF BFCO 3FCA 11 605F no 4 QCLK s 005 722 0 1F gt PQA 6 ANG mort 7FCG FFCS 12 8108 YES 16 QCLK s 822 888 2 18 gt PQA AN rt 7FCO FFCS 13 3DD PAUSE YES 16 QCLK s 022 888 2 1D gt PQA BZAN 83D9 7640 F646 14 3EA PAUSE YES 16 QCLK s 622 888 2 2A gt PQA 6 ANG port BFCG 3FC8 15 OOFE no 16 QCLK s 622 888 2 3E gt PQA 6 ANG mort 7FCG FFCS 16 OOEF no 16 QCLK s 622 888 2 2F gt PQA 6 ANO Ort 7FCO FFCS 17 mr YES 16 QCLK s 622 888 2 3F gt PQA 6 ANG 63D9 7646 F646 18 GOFF no 16 QCLK s 622 888 2 3F gt PQA 6 ANO port BF
96. Address CSBARX and the Chip Select Options register CSORX where X denotes the selects one of the 11 chip selects Starting from the left and going to the right are the Base Address Block Size Asynchronous Synchronous E Clock Mode Upper Lower Byte Option Read Write Address Data Strobe Wait States Address Space Select Interrupt Priority Level Autovector Enable and Pin Widths fields All except the Pin Width field are bit groupings derived from the CSBARX and the CSORX registers The Pin Width field is derived from the Chip Select Pin Assignment registers one and zero CSPARI CSPARO not shown in this window 15 6 QSM Module Windows The following windows display the Queued Serial Module QSM module settings 15 6 1 QSM Main Window 32 MyBdm32 QSM Main iol x QSHHCR STOP F F The QSM Module is operating normally FR21 E EI When FREEZE on IMB ignore it FR26 D D Reserved for future use SUPU 7 7 QSM SZU registers access at Supu priviledge level IARB 3 0 QSM interrupt arbitration priority 6 QILR YR GG6GF ILQSPI D B QSPI interrupt priority is 6 ILSCI A 8 SCI interrupt priority is 6 INTU 7 6 QSM interrupt vecor number is 6F Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 217 15 Operational Status Windows The QSM Main window displays the QSM Configuration Register QSMMCR and the QSM Interrupt Level and Vector Register QILR QIVR 15 6 2 QSM Port Windo
97. BuildChar messageString This command generates a warning message if the simulator debugger version is earlier than that specified by lt verHi gt lt verLo gt and lt verBuildChar gt If an earlier than required version of the simulator debugger is actually running then a dialog appears that contains the text specified by lt messageString gt verify version 3 50 B This demo application that illustrates GLOBAL INITIALIZATION n will not work in this early version of the simulator debugger In the example above the message this demo appears if run on a simulator debugger version earlier than version 3 50 build B We recommend this script command be placed first in the script file so that it gets processed before any parse errors or unsupported command errors can occur File Script Commands These commands support loading and saving files via script commands load_executable filename executable This example loads the executable image and related source files found in file filename executable Any open source files in the previously active image are closed The file path is resolved relative to the directory in which the project file is located load_executable A Out This example loads the executable found in file A Out in the same directory where the project file is located vector filename Vector The simulator debugger test vectors found in file filename Vector are loaded by this script com
98. C 1994 2015 ASH WARE Won Target Development Tool page 59 6 Script Commands Files 6 6 9 page 60 Multi Target Development Tod the buffer has insufficient space to hold this string a bug that is difficult to identify would result See the Global eTPU Channel variableAccess section for information on accessing eTPU channel variables using the format shown below lt lt chan num name gt lt function var name gt Verify Symbol Value Script Commands These verify symbol value commands have a similar syntax to those commands described in the Write Symbol Value Script Command section verify val exprString testOpString exprString The expression strings exprString can be a numerical constant or a simple symbolic expression Constants can be supplied as decimal signed integers unsigned hexadecimal numbers prepended with Ox floating point numbers or as a character e g ALA symbolic expression can be just a local global symbol or a simple expression such as V de reference EN address of V V constant V member or V gt member where V is a symbol of the appropriate type The special channel variable eTPU only reference syntax is also supported If the types of the two sides differ C type conversion rules are followed before performing the test operation testOpString is a C test operator Supported operators are gt gt lt lt amp amp and Il If the result of the specif
99. CG 3FCA 19 3FF PAUSE YES 16 QCLK s 622 888 2 3F gt PQA 6 AND Ort rn FFCS 1A 3FF PAUSE YES 16 QCLK s 022 888 2 3F gt PQA ZAN mort 7FCO FFCS 1B 63D9 PAUSE YES 16 QCLK s 022 888 2 19 gt PQA ZAN Dong 7646 F646 1C GOFF no 16 QCLK s 622 888 2 3F gt PQA 6 ANO GOFF BFCG 3FCA 4D O3FF PAUSE YES 16 QCLK s 622 888 2 3F gt PQA 6 AND O3FF 7FCG FFCS 1E 3FF PAUSE YES 16 QCLK s 022 888 2 3F gt PQA 6 ANG mort 7FCG FFCS 1F gong PAUSE YES 16 QCLK s 022 888 2 19 gt PQA ZAN 63D9 7646 F646 28 ng PAUSE YES 16 QCLK s 622 888 2 19 gt PQA 6 AND GOFF BFCG 3FCA 29 G1FD YES 16 QCLK s 622 888 2 3D gt PQA 6 ANG mort 7FCO FFCS 2A 62DB PAUSE no 16 QCLK s 022 888 2 1B gt PQA 6 ANG mort 7FCG FFCS 2B 0391 PAUSE YES 8 QCLK S 011 444 1 11 gt PQA 0 ANG 83D9 7640 F646 2C OOFF no 16 QCLK s 622 888 2 3F gt PQA BZANG port BFCG 3FCA 2D 3FF PAUSE YES 16 QCLK s 022 888 2 3F gt PQA ZAN mort 7FCG FFCS 2E O3FF PAUSE YES 16 QCLK s 622 888 2 3F gt PQA 6 AND O3FF 7FCO FFCS 2F 63D9 PAUSE YES 16 QCLK s 622 888 2 19 gt PQA 6 ANB 83D9 7640 F646 The QADC Channels window displays the Conversion Command Word Table Registers CCWO0 to CCW2F the Right Justified Unsigned Result Registers RJURRO to RJURR2P the Left Justified Signed Result Registers LJSRRO to LJSRR63 and the Left Justified Unsigned Result Registers LJURRO to LJURR27 Note that the QADC normally has up to 16 analog input channels but can directly support up to 40 analog
100. CTM6 settings 15 9 1 CTM4 CTM6 Bus Interface and Clocks Window 32My68376 CTM4 Bus I F and Clocks 7 O x BIUMCR 1A61 STOP F F Configirable Timer Module 4 clocks are ENABLED FR21 E E When FREEZE on IMB ignore it YECT C B Interrupt vector base is SCH plus submodule offset IARB A 8 CTM4 interrupt arbitration priority 2 TBRS1 5 5 Time Base Select Bit 1 is 6 TBRSG 6 6 Time Base Select Bit 6 is 1 l Use Time Base Bus 2 TBB2 BIUTBR 6666 F 6 The value of Time Base Bus 2 is 6660 CPCR 6662 PRUN 3 3 Prescaler divider is held in reset and not running DIV23 2 2 First prescaler stage divides by two PSEL 1 0 PCLK6 post DIU23 prescaler is 28 PCLK1 PCLK2 PCLK3 PCLK4 PCLKS PCLK6 Clock Period ns 615 258 8 661 907 3 660 953 7 660 476 8 660 238 44 660 119 2 Total Prescaler 256 32 16 8 4 2 The CTM4 CTM6 Bus Interface and Clocks window displays the BIU Module Configuration Register BIUMCR the BIU Time Base Register BIUTBR and the CPSM Control Register CPCR In addition the prescaler clock period is calculated and listed in both nano seconds and division ratio Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 225 15 Operational Status Windows 15 9 2 CTM4 CTM6 Free Running Counter Submodule Window FCSMSIC 1866 CO FCSHCNT 23D2 F E B 9 Pas 2 F t DH 3 E d CN DH ai man O x A free running counter overflow has
101. DR_SPACE enum READ WRITE ClockPerEvenAccess ClocksPerOddAccess This command sets the timing for the target TargetName in the block BlockName This command applies only to memory spaces ADDR_SPACE and for the read and or write cycles enum READ_WRITE Even accesses are set to ClocksPerEvenAccess while odd accesses are set to ClocksPerOddAccess define NOT_DATA_ SPACE ALL SPACES CPU32_DATA SPACE add_mem_block Host 0 OxFFFF SlowMem ALL SPACES set_block_timing Host SlowMem CPU32_DATA_SPACE Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 305 20 Building the Target Environment RW_READ 4 8 set_block_timing Host SlowMem CPU32_DATA_SPACE RW_WRITE 2 3 set_block_timing Host SlowMem NOT_DATA SPACE RW_ALL 5 6 In this example the even data reads are set to take four clocks while odd data reads are set to take eight clock cycles Even data writes take two clock cycles while odd accesses take three All non data even reads and writes take five clocks while odd take six This example illustrates an important aspect of timing design A separate copy of the timing data is kept for each address space and for both read and write cycles So even though only a single memory block was created in this example timing data for each address space is able to be individually specified set_block_to_dock FromTargetName BlockName enum ADDR_SPACE ToTargetName AddressOffset
102. E No File Isr F No File Clocks Counters No File Open No File Open No File Open Example Vector No File Open No File Open Open Open Open Open Open Open Open Open Open Open Open Open Open Open Open Open The simulated CPU clock frequency is displayed The TCR1 prescaler TCR2 prescaler page 202 Multi Target Development Td 1994 2015 ASH WARE Inc Reference Manual 15 Operational Status Windows PSCK control bit and T2CG control bit are displayed When MtDt is in TPU2 mode the DIV2 and T2CSL control bits are displayed These control bits which are new to the TPU2 add capabilities to the TCR1 and TCR2 counters These control bits are automatically hidden when in TPU1 mode since they apply only to the TPU2 These bits are controlled using script commands described in the TPU Clock Control Script Commands section When MtDt is in TPU3 mode the enhanced prescaler enable bit ESPCKE the enhanced prescaler bit ESPCK and the TCR2 pre divider prescaler enable bit TCR2PSCK2 are displayed These control bits which are new to the TPU3 add capabilities to the TCR1 and TCR2 counters These control bits are automatically hidden when in TPU1 or TPU2 mode since they apply only to the TPU3 These bits are controlled using script commands described in the TPU Clock Control Script Commands section Verification An indication of whether behavior verification is enabled or disabled is displ
103. EEE IB WZ Complex Breakpoint Window eTpu1 Complex Breakpoints ComplexBreakpoint Output Pin UART_XMT Set Channel Flag UART_XMT Flagi Set Nyt ComplexBreakpoint W Program Counter UART_XMT UART_WRAP UART_RCY addr 0x100 Complex breakpoints are added removed and modified from within the complex breakpoint window Complex breakpoints support the ability to halt the target on the occurrence of one or more combinations of conditions Each complex breakpoint operates independently of all other complex breakpoints Each complex breakpoint can have one or more conditionals When multiple conditionals are added to the same breakpoint then all conditionals must simultaneously resolve to true in order for the complex breakpoint to halt the target s Conditionals are added and modified using the Complex Breakpoint Conditional dialog box Depending on the target conditionals can include input output and clock pins thread activity host service requests and program counter value variable values or tests etc Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 189 15 Operational Status Windows 15 1 9 Memory Dump Window 6066 7FFFFEFE 3FFFFFFE BFFFFFF8 1FFFF807 5S858F47E SCSC35FA SCSC33FA E1E461C7 A 0020 SEGBFEF8 7859FEFF 7AS9FEFF 3C7FF807 D4GEFFFF 525CB5FA 163FF00B 101DF80F OPLA QAICFFFF IAFFRA1I OZEIEEE RQNIAFFFF DOEEAEEE CHOCPEARO CHOCEANO OW GREFEE ad Host16 Memory Dat
104. ETEC_cpp exe provides enhanced preprocessing capabilities that significantly increase the power of the scripting language In most cases this capability is transparent to the user though one side affect is that the preprocessing stage is case sensitive This feature defaults to being active though it can be disabled see the IDE Options dialog box One application of the preprocessor is to support initialization of global variables in the eTPU This is done as follows The Byte Craft compiler supports a macro capability that results in a series of macros as shown below for global variable initialization __etpu_globalinit32 0x0000 0x70123456 __etpu_globalinit32 0x0004 0x71ABCDEF __etpu_globalinit32 0x0008 0x72000000 1994 2015 ASH WARE Inc Reference Manual 6 Script Commands Files The example above was output into the auto generated header files by the following Byte Craft command pragma write h ETPUglobalinit32 Using the following macro expansion it is possible change the above macros into a form supported by ASH WARE define etpu_globalinit32 location value ETPU_DATA SPACE U32 location value The eTPU Simulator then sees the following script commands which it can handle ETPU_DATA_SPACE U32 0x0000 0x70123456 ETPU_DATA_SPACE U32 0x0004 0x71ABCDEF ETPU_DATA_ SPACE U32 0x0008 0x72000000 6 2 The Primary Script Command Files The simulator debugger autom
105. Enumerated Data Type cccccssssssssesserseveeseneseennes 110 eTPU Register Enumerated Data Types sccsssesessssesessessessesseesensenseeenennees 110 TPU Register Enumerated Data Types ccsssssessssesessensessesseesenseeseeenennens 111 CPU32 Register Enumerated Data Type cccscseseesseeseestessesseseesesseeeeeesneenenes 112 Part 7 Trace Buffer and Files 113 Part8 Test Vector Files 115 8 1 Node Command 2 ceccccceeeceeeeeeeee cece eeseen secon seca essen ERKENNEN REENEN EEN 117 8 2 Group Command cccceeeeeeceeeeeeeeeeeeeeeeeeeeeeeeeeeeeseeeeeeeseseeeeseeseeeeeeeseeeeeee 119 8 3 State COMMA Nn cocci sscceccesec cists AE ES SSES 119 8 4 Frequency Command ccccceeeeeceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeseeeeseeseeeeeeeeseneeeees 120 8 5 Wave Commande ENEE EEN REENEN EEN EEE EEN 120 8 6 Engine Example CTPU cccccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeseseeeeeeeeseneneees 121 Part 9 Functional Verification 125 9 1 Data Flow Verification EEN cece nese ee ee eee EEN eeeeeeseeeeeeeeeee 126 9 2 Pin Transition Behavior Verification 2 scceeeeeeeeeeeeeeeeeeeeeeeeeeeeeees 128 9 3 Code Coverage Analysis cccccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeseeneeeeeeeeeeeees 133 9 4 Regression Testing Automation eeceeeeeeeeeeeeeeeeeeeeeeeeeeeeneeeeeeeeeneees 137 9 5 Console Mode icc t e r aaraa Eer a a aaae pra raea aa aea Jace dvedeneentut ce 138 9 6 Command Line Options
106. Files This command writes the TCR2 configuration bit Valid Val values are zero and one write _t2csl Val This is available in TPU2 mode only It writes the TCR2 counter clock source edge control bit Only 0 and 1 are allowed values This control bit along with the T2CG control bit specifies the source for the TCR2 counter With both control bits at 0 the TCR2 counter is clocked on a rising edge With both control bits at one the TCR2 counter is clocked on both the rising and falling edges thus effectively doubling the counter frequency With T2CSL at 0 and T2CG at 1 the clock source is the gated system clock With T2CSL at 1 and T2CG at 0 the TCR2 counter is clocked on the falling edge write _tcr2_prescaler Val This command writes the TCR2 prescaler Valid Val values are 0 1 2 or 3 A 0 causes a division by 1 no prescaler A 1 causes a division by 2 A 2 causes a division by 4 A 3 causes a division by 8 write_t2cg 0 write _t2csl1 0 Available in TPU2 mode only write _tcr2_prescaler 3 The commands in this example set the external pin to be the TCR2 counter clock source and set the TCR2 prescaler to divide by 8 The TCR2 counter is setup to be clocked on the rising edge These commands together set the TCR2 counter to increment on every eighth rising edge of the signal at the TCR2 input pin TPU3 Specific Script Commands write_epscke Val This command writes the TCR1 enhanced prescaler enable bit Only 0 and
107. IM clock is driven by an external source During low power stop the CLKOUT pin is held low Reset caused by an external signal No Reset caused by the power up reset circuit No Reset caused by a software watchdog timeout No Reset caused by the halt monitor No Reset caused by a loss of clock No Reset caused by a RESET instruction No Reset caused by the test submodule No The software watchdog is ENABLED First watchdog prescaler is divide by 1 Additional watchdog prescaler is 2 X9 Watchdog period is 615 625 86 micro seconds assuming 32 768 KHz C Halt monitor function Disabled Bus monitor is Disabled for external bus cycles Bus monitor timeout is 64 system clocks Interrupt priority disabled Periodic interrupt vector OF First periodic interrupt timer prescaler is divide by 1 Additional periodic interrupt timer prescaler is 66 1 Periodic interrupt timer period is 666 122 1 micro seconds assur A The SIM Main window displays the Module Configuration Register SIMCR the Clock Synthesizer Control Register SYNCR the Reset Status Register RSR the System Protection Control Register SYPCR the Periodic Interrupt Control Register PICR and the Periodic Interrupt Timer Register PITR Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 215 15 Operational Status Windows 15 5 2 SIM Ports Window 52 MyBdm32 SIM Ports PORTC a cs1e ADDR23 ECLK 9 8 16 Bit CS CSPAR1 6355 CS9 ADDR22 PC 6 7
108. In both cases every line is prepended with the original source line number When the non covered listing option is specified a line gap is placed between annotated source assembly wherever source code lines have been filtered A small annotated sample is shown below 536 else if IsMatchAEvent amp amp flag1l 1 amp amp flagO 1 536 X 0016 0x4250 Alt Entry 11 Addr 0x940 EnableMatches p_31_0 channel U32 0x0 diob channel U24 0x5 0 536 S HSR 0b000 Link X matchA TranB 1 matchB TranA InputPin ChanFlag1l ChanFlag0 2 536 001E 0x4250 Alt Entry 15 Addr 0x940 EnableMatches p_31_0 channel U32 0x0 diob channel U24 0x5 0 536 S A HSR 0b000 Link X matchA TranB matchB TranA InputPin ChanFlag1 ChanFlag0 2 537 538 All 32 bits were received amp half a gap has been detected 539 filtering if any is done now while parity check is done 540 when the full gap is validated 541 AW_A429R_ValidHalfGapFilter 542 543 ClrFlag0 543 X 0940 OxDFE87A8C ram p_23_0 channel int24 0x31 FormatD6 0 543 4 OxDFE87A8C chan clear ChannelFlag0 clear MatchRecognitionLatchaA FormatD6 4 544 ClearMatchAEvent 545 546 if RxFilter Label 546 X 0944 0x0008F019 alu nil p 0x0 SampleFlags FormatA2 4 546 T 0948 OxFOD84BC7 seq if z true then g
109. Input Pin The GPT Input Captures window displays the Timer Control Registers 1 and 2 TCTLI Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 223 15 Operational Status Windows TCTL2 the Timer Interrupt Mask Registers 1 and 2 TMSK1 TMSK2 the Port G Data Direction Register DDGRP and the Port G Data Register PORTGP 15 8 3 GPT Output Compares Window SR x On On OCI On OI Reg TCNT Force Input Pin D Match Match pin Val Interrupt Match Compare x Output Is ocs a DCH toggle op SET 1233 Disabled No clr Input HI DCH set op SET 3366 Disabled No SET Output HI oc2 clear op clr BABO Disabled Yes clr Input HI DC op clr CDEE Disabled No SET Output lo TCTL1 TCTL2 1ED8 OC1M OC1D FSE6 THSK1 THSK2 82B8 TFLAG1 TFLAG2 1636 CFPRC PWHC 2B84 DDGRP 2F PORTGP F2 Note Force Compare always reads zero The GPT Output Captures window displays the Timer Control Registers 1 and 2 TCTLI TCTL2 the OC1 Action Mask Register OC1M the OC1 Action Data Register OC1D the Timer Interrupt Mask Registers 1 and 2 TMSK1 TMSK2 the Timer Interrupt Flag Registers 1 and 2 TFLG1 TFLG2 the Compare Force Register CFORC the PWM Force Register PWMC the Port G Data Direction Register DDGRP and the Port G Data Register PORTGP 15 8 4 GPT Pulse Accumulation Window lol x 32MySim32 GPT PA Pulse Accumulate _ PACTL PACNT 6466 PAIS F F Pulse accumulator input pin s
110. K 2 DSCK DSCK DSCK PCS 3 HI HI Ilo HI HI HI HI HI HI HI HI HI HI HI lo HI PCS 2 HI HI Ilo HI HI HI HI HI lo HI l HI lo HI lo lo PCS 1 HI HI HI lo lo lo lo HI HI lo HI HI HI HI HI HI PCS 6 HI HI lo HI HI lo HI HI HI HI lo HI HI HI lo lo The QSM QSPI window displays the QSPI Control registers 0 1 2 and 3 SPCRO SPCR1 SPCR2 and SPCR3 In addition the QSPI s Receive Transmit and Command RAM RR 0 F TR O F and CR 0 F are displayed for each of the 16 locations Below the Command RAM field each of the 16 command RAM locations is broken down by bit groupings These fields are the Continue CONT the Bits per Transfer Enable BITSE the Delay After Transfer DT and the PCS to SCK Delay DSCK Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 219 15 Operational Status Windows 15 6 4 QSM and SCI UART Window 32 MyBdm32 QSM SCI siol x SCCRO DD SCBR c 68 SCI clock period 666 615 3 micro seconds assuming 32 768 KHz crystal l lI I K d SCCR1 6666 LOOP E E Normal SCI operation no looping feedback path disabled WONS D D If configured as an output TXD is a normal CMOS output ILT C C short idle line detect PT B B even parity PE A A SCI parity is disabled IN 9 9 16 bit SCI frame WAKE 8 8 SCI receiver awakened by idle line detection TIE 7 7 SCI transmit TDRE interrupts are disabled TCIE 6 6 SCI transmit complete interrupts are disabled RIE 5
111. KK IK echo SUCCESS ALL TESTS PASS echo ERIK RII K KIRK II e e e He He III e He e e I e He e e e e He He e eke ke ke ke kokk ke ke goto end errors Ch OI e he He e He He e He He e He He e He He e He He III I He e ke I IK echo YIKES WE GOT ERRORS CHO FERRI KAKI KK HK KKK KKK tee kee kk end 1994 2015 ASH WARE Inc page 144 Multi Target Development Tho Reference Manual 9 Functional Verification If the above test were named TestAIl bat then the test would be run by opening a DOS shell and typing the following command c TestDir TestAll Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 145 page 146 Multi Target Development Tool 10 Action Tags 10 Action Tags An action tag is an identifier embedded in the source code as a comment that alerts simulator debugger to perform a specified action when code execution has reached that point in the source code The action tag is ASH When target code is loaded the simulator debugger scans the source code for action tags thus if the source code can not be located the associated action tags will not get activated The full form of an action tag includes the action ASH lt action gt Code execution momentarily pauses when the associated source code is reached and the requested action is performed Simulation then re starts as if nothing happened A few of the supported action tag commands are print action timer action an
112. LSR field shows if there is a pending link into this channel MEF Match Enable Flag indicates if during a thread matches for the channel being serviced can be enabled or disabled This will only be disabled if the active channel is active and matches are disabled during the thread The input and output pin states are displayed as is the state of the output buffer Although the simulator tracks the state of this buffer there is no other affect in the simulation engine The input detection and output action fields show how the IPACs and OPACs have been configured Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 199 15 Operational Status Windows 15 2 6 The PDCM displays the Predefined Channel Mode for that channel Each channel has two flags and these are shown The CPBA Channel Parameter Base Address is shown in the Frame Address field Note that the full address is shown rather than the CPBA value This frame is where each channel stores its own private channel variable copies The channel s bandwidth is shown Bandwidth is defined as the number of clocks in which either a thread or a Time Slot Transition TST for this channel was active divided by the total number of clocks since the last reset Additionally the number of threads and the number of steps instruction or NOPs is displayed The longest thread in both steps instructions plus NOPs plus the longest thread time is displayed Click on the
113. M period is not complete IL E C PWM interrupt is level 2 IARB3 B B PWM interrupt arbitration bit 3 is l Concatenated with BIUMCR IARB 2 6 PIN 7 7 The PWH output pin is Low LOAD 5 5 SET to load pulse width always reads 6 POL EN 4 3 Always low POL EN 4 3 CLK 2 6 CLK is 6 for a period of 666 119 2 Fsys 2 PER F463 F 6 The PERIOD is F463 Pu 9D1E F 6 The PULSE WIDTH is 9D1E CNT 6661 F 6 The COUNTER is 6061 SS PWM M See SIC 66606 FLAG F F A PWM period is not complete E The CTM4 Pulse Width Modulation Submodule window displays the DASM 5 6 7 and 8 Status Interrupt Control Registers PWMS5SIC PWM6SIC PWM7SIC PWMB8SIC the DASM 5 6 7 and 8 Period Registers PWMSPER PWM6PER PWM7PER PWMS8PER the DASM 5 6 7 and 8 Pulse Width Registers PWMS5PW PWM6PW PWM 7PW PWM8P W and the DASM 5 6 7 and 8 Count Registers PWMSCNT PWMO6CNT PWM7CNT PWM8CNT Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 227 15 Operational Status Windows 15 9 6 CTM6 Single Action Submodule Window 52 MySim32 CTM6 Single Actions SASM RS m ol x Input capture or output compare has occured Interrupt level is Shared by A and B l Interrupt arbitration bit 3 lt IARB BIUMCR IARB 2 6 l l Interrupts are disabled enabled l l l Use time base bus A or time base bus B l l l l Pin state when input or flip flop state when output l l l l l
114. MAC functions Ss Use of ASH WARE s auto defines file etpuc_set4_defines h Data Types Demo e A variety of data types and data scopes commonly used in the eTPU e Run time initialization of data using the ETEC generated initialization file DataTypes_idata h Auto Defines Demo e Use of files etec_sim_autodef h and etec_sim_autodef_private h to write amp verify channel global and engine memory Note that engine memory is available in the eTPU2 only Templates Demo e A variety of templates empty code which and are excellent starting point when developing new eTPU functions Legacy and ETEC mode functions Standard and Alternate entry tables 1994 2015 ASH WARE Inc page 18 Multi Target Development Tod Reference Manual 2 Demo Descriptions System Configuration Demo e An optional system configuration file sets the system parameters such as clock frequency processor family which functions run on which channels channel priority etc e Optionally the maximum allowed worst case latency WCL for each channel can be specified Build fails if WCL requirements are not met e Analyses file shows resulting system behaviours such as WCTL and WCL for each channel Stepper Motor System Simulator Demo e System simulator demo both CPU and eTPU are simulated e Freescale s host side API on a simulated CPU e The ASH WARE lt gt defines file used in the host side API Sg Freescale s
115. Multi Target Development Tool Reference Manual by John Diener Andrew Klumpp Tony Zabinski Keith Kroker and Michael Schwager ASH WARE Inc Version 4 86 ASH 11 1 2015 C 1994 2015 ASH WARE Inc ASH WARE Inc page 2 Multi Target Development Tool Multi Target Development Tool Table of Contents Foreword 11 Part 1 Overview 13 1 1 On Line Help Content ccceeececeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeseeeeeeeeseeeeeees 16 Part 2 Demo Descriptions 17 Part 3 Software Upgrades 21 3 1 Version 3 0 to 4 3 Enhancements 22 ceceeeeeeeeeeeeeeeeeeeeeeeeeeeeeneeeeeeeeees 23 Part 4 The Project 29 Part 5 Source Code Files 31 5 1 Source Code Search Rules cccccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeseeeeeeeneeeeeeees 32 5 2 Supported Compilers and Assemblers 2 cceeeeeeeeeeeeeeeeeeeeeeeeseeeeenees 33 Part 6 Script Commands Files 35 6 1 The ETEC _cpp exe Preprocessor cccceeeeceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeneees 36 6 2 The Primary Script Command Files ceccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeees 37 6 3 ISR Script Commands Files cccccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeseeeeeeneeeeeeeees 37 6 4 The Startup Script Commands File ccs ceccceeeeeeeeeeeeeeeeeeeeeeeeeeeseeeeeeees 40 6 5 File Format and Features 2 cccceceeeeeceeeeeceeeeeeeeeeeeeseeeeeeeeeeeeeeeseeeeeeees 40 Multiple Target Scripts ccccssessseesesseesesseeseeseesnesesessess
116. RL and the Service Grant Latch SGL These latches are affected by the Host Service Request Register HSRR the Link Service Requests LSRs and the Match or Transition Service Requests M TSRs which are also displayed The M TSR is generated from the Match Recognition Latch MRL Transition Detection Latch TDL and the Match Transition Service Request Inhibit SRI latch The M TSR is formed from the following logical expression MRL and TDL or SRI Each register is broken down by TPU channel such that the value for each channel is easily found Most of these registers can be modified only by the TPU 15 3 4 TPU Micro Sequencer Registers Window Time DIUNWEGCRS us CPU Clock 666611282 TCR1 1D66 TCR2 6626 TCR2 Input Pin High Active Channel T 8 T 4 D D D D Address 66F6 Rtn 6634 Prefetch 66F4 Prefetch Opcode 9445FFFF Dec Inactive Banks Code Entry Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 205 15 Operational Status Windows The TPU Microsequencer Registers window displays miscellaneous information generally applying to the microsequencer This window is something of a catch all The current Simulator time is displayed The time is expressed in microseconds The count of CPU clocks since the last Simulator reset is also displayed The TCR1 and TCR2 counter values are displayed These 16 bit counters are displayed in hexadecimal The TCR2 input pin s value is
117. SH WARE D Target Development Tool page 235 15 Operational Status Windows 15 11 7 Real Time Clock RTC Window 52 MySim32 Real Time Clock RTC SIC 8047 PRR 8108 FRCH Cap FRCL F83A t a oon 9 8 F F F s t e ee CO 0 x A 1H2 tick has occured No Interrupt is disabled when TICKF sets Interrupt arbitration bit 3 is Concatenated with BIUMCR IARB 2 6 Writes to prescaler and counter are Disabled The RTC is not running RTC prescaler 6166 Free running counter hi 6C606 Free running counter lo F83A The Real Time Clock window displays the RTC Status Interrupt Control Register RT16SIC the RTCSM Prescaler Register RTCSM and the RTCSM Free Running Counter High and Low Registers RI6FRCH RI6FRCL page 236 Multi Target Development Tho 1994 2015 ASH WARE Inc Reference Manual 16 Dialog Boxes 16 Dialog Boxes Dialog boxes provide an interface for setting the various Simulator options Reference Manual File Open Save and Save As Dialog Boxes Auto Build Batch File Options Dialog Box Goto Time Dialog Box Goto Angle Dialog Box Occupy Workshop Dialog Box IDE Options Dialog Box MtDt Build Script Options Dialog Box Workshop Options Dialog Box Message Options Dialog Box Source Code Search Options Dialog Box Reset Options Dialog Box Logic Analyzer Options Dialog Box Thread Options Dialog Box Complex Breakpoint Dialog Box Trace Options Dialog Box
118. TPU the ASH WARE ETEC compiler or the Byte Craft compiler is used to build the code These executable files are loaded into the target core s memory space The simulator debugger also loads the associated source code files and displays them in source code windows highlighting the line associated with the instruction being executed Several hot keys allow the user to set breakpoints execute to a specific line of code or execute until a point in time The executable code is loaded by selecting the Executable Open submenu from the Files menu and following the instructions of the Load Executable dialog box The loaded source code file is then displayed in a context window The window can be scrolled re sized minimized etc Help is available for the source code file window and is accessed by depressing the lt F1 gt function key when the window is active Theory of Operation The simulator debugger associates the user s source code with the executable code generated by the compiler assembler and linker This ability provides the following important functionality Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 31 5 Source Code Files 5 1 page 32 Multi Target Development Tod Highlight the active instruction Set toggle breakpoints Execute to cursor In order for the simulator debugger to read the executable code the source code must be compiled assembled and linked The resulting executa
119. TYPE enumerated data type Script FILE_OPTIONS enumerated data type Script VERIFY_FILES RESULT enumerated data type Script BASE_TIME enumerated data type Script TRACE_OPTIONS enumerated data type Script TARGET_TYPE enumerated data type Build script Target Sub Type enumerated data type Script ADDR_SPACE enumerated data type Build Script READ_WRITE enumerated data type eTPU Register enumerated data types TPU Register enumerated data types CPU32 Register enumerated data types Script FILE_TYPE Enumerated Data Type The following enumerated data type is used to specify the file type used in various script commands This specifies a dis assembly Freescale S Record Intel Hexadecimal or C data structure file type enum FILE TYPE DIS_ASM SRECORD IHEX IMAGE C_STRUCT Script VERIFY_FILES Enumerated Data Type The following enumerated data type is used to specify the expected results of a file comparison enum VERIFY _ FILES RESULT FILES MATCH FILES MISMATCH 1994 2015 ASH WARE Inc Reference Manual 6 Script Commands Files FILE1_ MISSING FILE2_ MISSING BOTH FILES MISSING 6 8 3 Script FILE_OPTIONS Enumerated Data Type The following enumerated data type is used to specify the options when dumping data to a file The available options depend on the type of file being dumped Reference Manual enum DUMP_FILE OPTIONS Disables listing of address information in dis assembly and C data structure files NO_ADDR
120. Tool page 163 14 The Logic Analyzer 14 5 14 6 page 164 Multi Target Development Tho Displaying Behavior Verification Data Behavior Verification Data appears as a yellow line in the waveform pane as shown in the top waveform in the illustration found below eTPU_A Logic Analyzer 21 214 273 uS 21 221 243 uS Data Start 0 000 vS Context 0 000 vS Current Time 21 220 960 uS Left Cursor 21 215 297 uS Delta Cursor 4 879 vS Right Cursor 21 220 176 uS The check box to the left of each waveform is used to enable and disable display of the underlayed behavior verification data The check box in the second waveform is un selected which is why the behavior verification waveform does not appear Note that if no behavior verification data is loaded then no yellow waveform will appear even if the behavior verification checkbox is enabled The _EbvDiff and _EbvError waveforms show where differences and errors in the behavior verification data These signals are a logical or of all channels errors such that if there is an error or difference in any of the 32 channels then the signal is active high The reason that _EbvError and _EbvDiff are not identical is because of the tolerance that is allowed in each of these channels See the Pin Transition Behavior Script Commands section for a description on setting up global and pin specific behavior verfication tolerances Mouse Functionality In the waveform display panel the m
121. TransitionfEvent amp amp flag 1 oosa ox409B Std Entry 13 Addr 6x26C EnableMatches p relative U24 si 6x6 diob relative U24 6x4 6 HSR 6b606 Link 6 MatchA TranB 6 WMatchB TranA 1 InputPin 6 ChanFlagi X ChanFlag6 1 Leese ox409B Std Entry 15 Addr 6x26C EnableMatches p relative U24 si 6x6 diob relative U24 6x4 6 S HSR 6b666 Link 6 MatchA TranB 6 MatchB TranA 1 InputPin 1 ChanFlag1 X ChanFlag6 1 Bossa ox409B Std Entry 21 Addr 6x26C EnableMatches p relative U24 si 6x6 diob relative U24 6x4 6 z HSR 6b666 Link 6 MatchA TranB 1 MatchB Tranf 1 InputPin 6 ChanFlagi X ChanFlag6 1 Bosse ox409B Std Entry 23 Addr 6x26C EnableMatches p relative U24 si 6x6 diob relative U24 6x4 6 i HSR 6b666 Link 6 MatchA TranB 1 MatchB Tranf 1 InputPin 1 ChanFlagi X ChanFlag8 1 H invalid_flag6 Mark invalid flag6 state to make observable for debug purposes Clear flag Dot OxFFFSFCF9 chan clear ChannelFlag6 FormatD3 4 BadStateFault 6x334698 E 90270 8x6A633586 au P 6x334698 Formata1 4 3 8274 BxAFFFFB83 ram relative U24 ai 6xD p_23_6 FormatB2 6 OxAFFFFB83 seq end FormatB2 4 of 4 A test has been written to excersize this thread and one can see that Event vector 15 has been covered because the box on the left is white But entries 13 21 and 23 have not been executed because the boxes on the left a
122. Window Log TCRCLK eTPU and TCR2 TPU Pin Transition This controls whether the TCRCLK TCR2 input pin transitions are logged to the data storage buffer This pin can be used to clock and or gate in the eTPU and TPU Disabling this increases the effective data storage buffer size Log TCR1 TCR2 Counter Transitions The least significant bit of the TCR1 and TCR2 global counters can be logged and thereby displayed as a waveform in the logic analyzer Disabling this increases the effective data storage buffer size Log Angle Mode Transitions Various aspect of angle mode can be displayed in the logic analyzer as a waveform These include the mode high speed Normal Wait angle ticks synthesized PLL tooth ticks etc Disabling this increases the effective data storage buffer size Log Threads Threads can be grouped into thread groups and the thread group activity can be displayed in the logic analyzer window Disabling this increases the effective data storage buffer size Configure Thread Groups There are eight thread groups labeled from A to HI This opens the Thread Group Dialog Box allows configuration of which thread s are associated with each of these groups Time Display The Logic Analyzer can base the timing display on either target clock count or Simulator time Both of these are set to zero when simulator debugger is reset This field allows the user to select between the two display options Target Clocks Displa
123. _tpu_type 1 1024 write_entry_bank 1 The commands in this example set the TPU type to TPU1 the instruction space size to 1024 32 bit long words and the entry bank to 1 Setting the TPU Code Bank The following code bank discussion is applicable only to TPU2 and TPU3 There are no script commands for setting the code bank At run time the active code bank is determined during each time slot transition Bits 10 and 9 from the entry table determine the code bank The TPU assembler generally handles this field by determining the bank in which the code is located The user has control over which bank the code is located from within the source TPU microcode One method of specifying the bank in which the code will reside is the ORG statement This and other methods are described in the TPU assembler literature TPU Match Transition amp Link Script Commands set_mr1 ChanNum set_tdl1 ChanNum set_link ChanNum These commands directly sets the Match Recognition Latch MRL the Transition Detection Latch TDL or a Link Service Request LSR of channel ChanNum set_mr1 5 set_tdl1 3 set_link 8 In this example channel 5 s MRL is set channel 3 s TDL is set and a link is generated on channel 8 eTPU TPU Interrupt Association Script Commands Interrupt association script commands associate a script commands file with the firing of interrupts such that when the interrupt is both enabled and active the script commands f
124. a Space OF Xx et EEE 00 66 00 96 52 36 op op 66 B oppe oppe GO B R6 E Dt 0010 66 B 66 B6 oppe oppe oppe B oppe oppe Dt 9626 66 B 66 B oppe oppe oppe oppe oppe oppe Dt 0030 66 B 66 B oppe oppe oppe oppe oppe oppe 01 0040 66 B 66 B oppe oppe oppe oppe oppe oppe TI H 0050 oppe G8 B GG B oppe oppe OO B B B8 B e eee eee ee E 0060 op B 66 B6 oppe oppe oppe B BO B oppe H ale The Memory Dump Window displays memory A number of options are available To change a viewing option activate a memory window and from the Options menu by select the desired option from the Memory submenu Memory is viewable in 8 16 or 32 bit mode The ASCII equivalent text on the right side can be turned off or on The address space can be specified The base address of the window can be specified A common development tool deficiency is that the vertical scroll bar is unusable because it causes too much memory to be traversed MtDt addresses this problem by limiting the scroll range of the vertical scroll bar A memory dump window displays only a small amount of the total address space The portion of memory that the memory window displays is specified by the base address parameter page 190 Multi Target Development TAS 1994 2015 ASH WARE Inc Reference Manual 15 Operational Status Windo
125. a block in which the read cycles have been set to off The affected address spaces must be a subset of the address spaces to which the referenced memory block applies The first command sets an eight bit value the second sets a 32 bit value add_non_mem_block eTPU_A 0x4000 OxFFFFFFFF UnusedCode ETPU_CODE_SPACE set_block_off_data32 eTPU_A UnusedCode ETPU_CODE_SPACE OxF7F757FA In this example the address space between 0x4000 and FFFFFFFF hexadecimal is specified to contain no memory Quad read cycles to this block will return the specified off data OxF7F757FA hexadecimal at every quad address set_block_to_bus_fault TargetName BlockName enum ADDR_SPACE enum READ WRITE This command results in bus faults for accesses to the target TargetName within the block BlockName for the applicable address spaces ADDR_SPACE and read write cycles enum READ_WRITE The effected address spaces must be a subset of the spaces to which the referenced memory block applies add_mem_block Host 0x10000 0xFFFFFFFF Unused ALL_SPACES set_block_to_bus_fault Host Unused ALL SPACES RW_ALL In this example a memory block has been added to represent the unused address space page 304 Multi Target Development T 1994 2015 ASH WARE Inc Reference Manual 20 Building the Target Environment above 64K Any access to this memory block results in a bus fault set_block_to_priv_viol TargetName BlockName
126. absolute value of the time difference between a gold file pin transition time and the current simulation pin transition time exceeds the specified tolerance In general these script commands should immediately follow the run_ebehavior_file script command although tolerances can be changed on the fly during simulation set_ebehavior_global_tolerance lt time tolerance mode gt lt time offset in us gt lt time tolerance in us gt This script command sets behavior verification tolerances for all pins of interest default to all or those specified with set_ebehavior_pin_tolerance The arguments mode time offset and time tolerance are described in the set_ebehavior_pin_tolerance documentation disable ebehavior pin lt pin name gt Pins can be individually disabled from behavior verification with this script command Note that this command and set_ebehavior_pin_tolerance work sequentially when determining the final set of pins of interest stop_ebehavior_file Used to end enhanced behavior verification and close the ebv file being used as the master gold file For the pins being verified the gold file and current simulation must match at this time or a behavior verification error will occur The stop_behavior_file script command should occur at the same time as the close_ebehavior_file command did during enhanced behavior file creation Thread Script Commands The simulator debugger stores worst case latency informat
127. across the CISR register is verified using the verify_intr X Y script command described in the eTPU Interrupt Script Commands Script Commands section In the following example data flow across channel 10 s CISR and parameter RAM is verified at a simulated time of 100 microseconds and again at 250 microseconds Wait for the simulator debugger to run 100 micro seconds at_time 100 Verify that channel 10 s CISR is set verify cisr 0xa 1 Verify that channel 10 s parameter 2 bit 14 is set verify ram_bit 0xa 2 14 1 Verify that channel 10 s parameter 3 is 1000 hex verify ram_word 0xa 3 0x1000 Verify that channel 10 s parameter 5 is 1500 hex verify ram_word 0xa 5 0x1500 Clear channel 10 s CISR clear _cisr 0xa Wait for the simulator debugger to run an additional 150 microseconds wait_time 150 Verify that channel 10 s CISR is set verify_cisr 0xa 1 Verify that channel 10 s parameter 2 bit 14 is cleared verify ram_bit 0xa 2 14 0 Verify that channel 10 s parameter 3 is 3000 hex verify ram_word 0xa 3 0x3000 Verify that channel 10 s parameter 5 is 3500 hex verify ram_word 0xa 5 0x3500 Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 127 9 Functional Verification 9 2 page 128 Multi Target Development Tho Pin Transition Behavior Verification Pin transition behavior verification is one of the verification
128. ad the executable source code select the Executable Open submenu and follow the instructions of the Load Executable dialog box As the executable source code is executed the source line corresponding to the active instruction is highlighted Usually the source file is too large to be displayed in its entirety The user can use the scroll bars to view different sections of the file As the code is executed the source code line corresponding to the active instruction appears highlighted in the window The user can move the cursor within the file using the Home End up arrow down arrow Page Up and Page Down keys When adding or toggling breakpoints and using the Goto Cursor function the cursor location is an important reference MtDt searches first down then up starting from the cursor to find a source line corresponding to an instruction The executable source code can be quickly reloaded from the Files menu by selecting the Executable Fast submenu This is normally required when the user has made a change to the executable source code and has re built it Mixed Assembly View To make visible the dis assembled instructions associated with each line of source code select the Toggle Assembly Mixed submenu from the Options menu For TPU targets the 32 bit hexadecimal equivalent of the micro instruction is displayed For CPU targets the actual disassembly is displayed Coverage Indicators The little black green red and white
129. address space may be explicitly overridden U8 ADDRESS References an 8 bit memory location U16 ADDRESS References a 16 bit memory location U32 ADDRESS References a 32 bit memory location U64 ADDRESS References a 64 bit memory location U128 ADDRESS References a 128 bit memory location The following are examples of referenced memory constructs Note that these examples do not form complete script commands and therefore in this form would cause load errors U8 0x20 Refers to an 8 bit byte at addr 0x20 U24 0x17 Refers to a 24 bit word at addr 0x17 U32 0x40 Refers to a 32 bit word at addr 0x40 Assignments in Script Commands Files Assignments can be used to modify the value of referenced memory a practice commonly referred to as bit wiggling Using this it is possible to set clear and toggle specific groups of bits at referenced memory The following is a list of supported assignment operators 1994 2015 ASH WARE Inc Reference Manual 6 5 7 Reference Manual 6 Script Commands Files Assignment Arithmetic addition and subtraction Fe f Arithmetic multiply divide and remainder lt lt gt gt Bitwise shift right and shift left amp l Bitwise and or and exclusive or lt lt gt gt Bitwise shift left and shift right The following examples perform assignments on memory Writes a 44 decimal to the 8 bit by
130. age is used Since a cached version is used source code files are also not changed Note that this option should be selected with care as the executable image in the target should generally not be modified during target execution and reloading every reset could mask such a bug Reread Test Vector File eTPU and TPU Targets Only Selecting this option causes the test vector file to be reread every time simulator debugger resets the targets Initialize Global Variables eTPU and TPU Targets Only Selecting this option causes global variables to be initialized with the values found in the elf or similar executable image file Note that in the real silicon this operation must be performed by the host CPU DATA Memory eTPU and TPU Targets Only This option specifies whether the DATA memory is not changed written to all zeroes or is randomized on reset TCR1 and TCR2 Counters eTPU and TPU Targets Only This option specifies whether the TCR1 and TCR2 counters are not changed written to zero or are randomized on reset Help This accesses this help menu Cancel This discards and changes and exits the Reset Options dialog box OK This saves any changes and exits the Reset Options dialog box page 252 Multi Target Development T9 1994 2015 ASH WARE Inc Reference Manual 16 Dialog Boxes 16 12 Logic Analyzer Options Dialog Box The Logic Analyzer Options Dialog box defines the settings associated with the Logic Analyzer
131. all at once One issue is that the trace buffer can overflow so this command may not be able to save all trace data gathered since the simulation was last reset Another issue is that if an event is not enabled to be displayed in the trace window it will not exist in the buffer So events specified by this script command may not get saved because they never made it into the script command This can occur say if partway through a simulation the events enabled for display in the buffer is changed For these two reasons it is better to use the start_trace_stream script command described earlier in this section Yes use the start_trace_stream script command instead Save Lrace buffer ThisTraceFile Trace STEP MEM READ VIEWABLE US 3 In this example a file named ThisTraceFile trace is generated Only step events and memory read events are saved The selected file format is optimized for viewing rather than parsing Note that both STEP and MEM_READ events must be enabled in the GUI at the time the script is executed in order for these events to be saved Otherwise the events would not have been stored in the buffer and therefore cannot be saved Even so if a previously disabled event is enabled in the GUI during the simulation the any events that occurred before being enabled will be lost Note that the previous behavior when saving toa VIEWABLE file format ignoring events specified in the script command has changed Regardless of
132. ame enum ADDR_SPACE enum READ_WRITE This command allows accesses of a simulated memory blocks can be turned off using this script command Using this command a read only memory device such as a ROM can be created Accesses to target TargetName within the block BlockName and specified address spaces ADDR_SPACE and read and or write cycles lt enum READ_WRITE gt are turned off A turned off write access behaves exactly like a normal write access except the actual memory is not written A turned off read cycle behaves exactly like a Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 303 20 Building the Target Environment regular read cycle except that the value returned is the OFF_DATA constant defined for the entire block The affected address spaces and read write cycles must be subsets of the referenced memory block add_mem_block Host 0 OxFFFF ROM ALL SPACES define ALL WRITES RW_WRITE8 RW_WRITE16 RW_WRITE32 set_block_to_off Host ROM ALL SPACES ALL WRITES This example creates a 64K memory device and configures it to be a read only or ROM memory device set_block_off_data32 TargetName BlockName enum ADDR_SPACE OFF_DATA set_block_off_data TargetName BlockName enum ADDR_SPACE OFF_DATA These commands specify that read cycles to the target TargetName within the block BlockName return the data lt OFF_DATA gt but only if the block is either a non_mem block or
133. ame The group name may contain any ASCII printable text These group names are case sensitive though this is currently not enforced Up to 30 nodes may be grouped define ADDRESS1 ch5 define ADDRESS ch7 define DATA ch3 group PORT1 ADDRESS1 ADDRESS2 DATA In this example a group with the name PORTI is associated with TPU channel pins 5 7 and 3 State Command state lt STATE NAME gt lt BIT_VALUE gt The state command assigns a bit value BIT_VALUE to a user defined state name STATE_NAME State names may contain any ASCII printable text These state names are case sensitive though this is currently not enforced Bit values must consist of a sequence zeros and ones The total number of zeros and ones must be between one and 30 state NULL 0110 In this example a user defined state NULL is associated with the bit pattern 0110 Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 119 8 Test Vector Files 8 4 8 5 Frequency Command frequency lt FREQUENCY gt The frequency command sets the master test vector clock to FREQUENCY which is a floating point number whose terms are million cycles per second MHz All test vectors are set by this frequency Since the entire test vector file is loaded at once if a test vector file contains multiple frequency commands only the last frequency command is used and all previous frequency commands are ignored frequency 1 In this example the master test vector
134. an ORT gate place_xor_gate In1Pin In2Pin OutPin Instantiates an XOR gate place_nand_gate In1Pin In2Pin OutPin Instantiates a NAND gate place_nor_gate In1Pin In2Pin OutPin Instantiates a NOR gate place_nxor_gate In1Pin In2Pin OutPin Instantiates an INVERTING XOR gate remove_gate Out Removes the gate that drives channel Out The eTPU has up to two pins per channel which depending on the specific device may or may not actually be connected together or to from outside of the microcontroller Indexes are defined as follows for the eTPU Oto31 Channels 0 through 31 inputs respectively 32 to 63 Channels 0 through 31 outputs respectively 64 TCRCLK pin place_and_gate 5 33 64 This example places an AND gate with eTPU channels 5 s input pin and eTPU channel 2 s output pin as inputs and the TCRCLK pin as the output Two eTPU Engine Configurations In two eTPU configurations it is possible to place gates between the two eTPU s pins This is done using the following syntax 128 to 159 Other eTPU s channels 0 through 31 inputs 1994 2015 ASH WARE Inc Reference Manual 6 Script Commands Files pins 160 to 191 Other eTPU s channels 0 through 31 output pins e Other eTPU s TCRCLK pin place_xor_gate 160 161 5 This example places a XOR gate from eTPU B s channel 0 and 1 output pins to eTPU A s channel 5 input pin Note that for the TPU 16 is the index used for the TCR2 p
135. anel Data Storage Buffer As MtDt runs transition information is continuously stored in a data storage buffer Data is stored only when there is an actual transition on a node When no transitions occur no buffer space is used This is an important consideration since the user can significantly increase the effective data storage by disabling the logging of the TCR2 input pin assuming it is active This is disabled from within the Logic Analyzer Options dialog box All buffer data is retained as long as it predates the current Simulator time and there is enough room to store it Therefore if MtDt time is reset to zero all buffer data is lost When the amount of data reaches the size of the buffer Ge the buffer becomes full new data overwrites the oldest data In this fashion the buffer always contains continuous transition data starting from the current time and going backward Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 169 page 170 Multi Target Development Tool 15 Operational Status Windows 15 Operational Status Windows The target state is displayed in various operational status windows These windows correspond to the various functional blocks associated with the specific target Each of these windows can be re sized scrolled iconized minimized and maximized Multiple instances of each window may be opened Window Groups Common Windows The following windows are available on mul
136. annel to be driven unto the input channel place_and_gate 32 5 32 7 1 eTPU OUTPUT GATE INPUT Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 153 page 154 Multi Target Development Tool 12 Integrated Timers 12 Integrated Timers Integrated timers measure the amount of time that code takes to execute This capability is available for all simulated targets as well as for hardware targets outfitted with the requisite support hardware Integrated timers work with a combination of a special Timers window as well as the source code windows Specific timer stop and timer start addresses are specified from within the source code windows Completed timing measurements are viewable within the Timers window The timer number within a green circle on the far left side of the source code window identifies the start address Similarly the timer number within a red circle on the far left side of the window identifies the stop address It is possible for the same line of source code to contain multiple timer start and stop addresses In this case only a single circle timer number will be displayed though all timers still continue to function MtDt supports 16 timers Each timer has the following states armed started finished overrun and disabled The state of each timer is displayed in the Timers window Each timer can be armed in several ways Specification of a new start or stop address within a s
137. ar test run that is causing any failures to be easily identified when perusing the log file tn lt TestName gt Note that command line parameters do not handle spaces will To include spaces in the name enclose the parameter in quotes as shown below In the following example the name Angle Mode is specified tnAngle Mode 9 10 Regression Test Example The keys to successful Regression Testing is the ability to launch simulator debugger multiple times within a batch file that runs ina DOS command line shell and to verify within this batch file that the tests that were automatically run had no errors These multiple launches of simulator debugger and the tests contained therein form a test suite The following is a batch file used to launch the simulator debugger multiple times Note that there is only a single target such that no target must be specified on the command line Had this been a test running in a multiple target environment the target name would have to be specified along with each script file echo off Use the CONSOLE version of the simulator set exe C Program Files ASH WARE TPU Simulator TpuSimulator_CL exe sexe pTest1 TpuSimProject sTest1 TpuCommand AutoRun IAcceptLicense if ERRORLEVEL NEQ 0 goto errors sexe pTest2 TpuSimProject sTest2 TpuCommand AutoRun IAcceptLicense if ERRORLEVEL NEQ 0 goto errors echo RI e He e He He II RI e He He e He he e He He e He I I KI He He e ke He
138. as read only A write to this memory device will not cause the values in memory to change This read only behavior could be used to model a ROM device define ROM_STOP Oxffff define BLANK START ROM STOP 1 define MEM END Oxffffffff instantiate_target SIM32 MyCpu add_mem_block MyCpu 0 ROM_STOP Rom ALL_SPACES add_non_mem_block MyCpu BLANK START MEM END Empty ALL_SPACES Turn off READ access for the ROM device define WRITE_ALL RW_WRITE8 RW_WRITE16 RW_WRITE32 set_block_to_off MyCpu Rom ALL SPACES WRITE_ALL The command specifies that for all address spaces all write accesses will be empty Despite this being an empty access other parameters such as clocks per even cycle remain valid The last two arguments specify the address spaces and access types affected by this script command It is possible to indicate specific address spaces and a specific type of access For instance using this script command one could specify 32 bit writes to user data space Clocks per Access Control page 292 Multi Target Development Td 1994 2015 ASH WARE Inc Reference Manual 20 Building the Target Environment For each memory block and type of access the clocks per even access and the clocks per odd access can be specified This capability effectively provides the capability of setting the number of wait states set_block_timing MyCpu Rom ALL_SPACES RW_ALL 2 3 In this example even a
139. as the new ebv files Existing scripting commands apply to original bv files only where noted A more complete discussion of functional verification is given in the Functional Verification chapter while a discussion of the specifics of pin transition behavioral modeling is given in the Pin Transition Behavior Verification section With the new enhanced behavior verification the loaded master pin transition behavior data can be viewed in theLogic Analyzer Window Deprecated Behavior Verification Script Commands read_behavior_file filename bv This command loads the pin transition behavior file into the master pin transition behavior buffer This buffer forms a behavioral model of the pin transition behavior of the source code Only old style bv files can be read with this command verify all behavior This command verifies all recorded pin transition behavior against the master pin transition behavior buffer It generates a behavior verification error message and increments the behavior failure count for each deviation from the behavioral model Only old style bv files can be verified with this command enable_continuous_behavior This command enables continuous verification of pin transition behavior against the master pin transition behavior buffer During source code simulation each functional deviation generates a behavior verification error message and causes the behavior verification failure count to be incremented Thi
140. ask Product ONLY TPU_MASK 6 8 9 Build Script ADDR_SPACE Enumerated Data Type MC68376 This enumerated data type is used when specifying the applicable address spaces for various build script commands enum ADDR_SPACE page 108 Multi Target Development T46 1994 2015 ASH WARE Inc Reference Manual 6 Script Commands Files TPU DEU CODE SPACE TPU_DATA_SPACE TPU_PINS_ SPACE TPU_UNUSED_SPACE eTPU ETPU_CODE_SPACE ETPU_CTRL_SPACE ETPU_DATA_SPACE ETPU_DATA 24 SPACE ETPU_NODE_SPACE ETPU_UNUSED_SPACE CPU32 CPU32_USER_CODE_SPACE CPU32_SUPV_CODE_SPACE CPU32_USER_DATA_ SPACE CPU32_SUPV_DATA_SPACE CPU32_UNUSED_SPACE ALL_SPACES In the following very specific cases mathematical manipulation of this enumerated data type is allowed Single instances of values referencing the same target may be added to each other Single instances of values referencing the same target may be subtracted from ALL_SPACES The following are some valid mathematical manipulations of this data type The following references a CPU32 s USER and SUPERVISOR code spaces CPU32_USER_CODE_SPACE CPU32_SUPV_CODE_SPACE The following references all used CPU32 address spaces ALL_SPACES CPU32_UNUSED_SPACE The following are some invalid valid mathematical manipulations of this data type Reference Manual INVALID CPU32 and MC33816 cannot be intermixed CPU32_USER_CODE_SPACE MC
141. at murky Some channel parameters migrate after a number of instructions to the new channel while other parameters remain attached to the channel that originally caused the channel servicing How does MtDt handle this situation since the active channel version of the channel window is intended to show channel information of the active channel This is answered in the following paragraph The active channel version of the channel window shows the channel information corresponding to the active parameters For instance the effective flag changes from the old channel to the new channel two microcycles after the CHAN register is changed MtDt also switches the displayed flag two microcycles later In this way the user always views the affective channel Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 209 15 Operational Status Windows 15 3 7 TPU Parameter RAM Window Ef TpuSim Parameter RAM Iof x E 2636 7866 6666 6666 6666 662C 6631 222C 2041 4C4C 5F53 5041 SB6A 7365 745F 626C 6F63 6B5F 6F63 6B28 2248 6F73 7431 3622 5655 5F44 6174 6122 2026 114C 6661 0601B4 666C 6668 6666 166D 669F 6266 6366 3636 293B GA73 6574 5F 2 6691 4299 6166 6466 4699 6C6F 6462 660606 e bbe WT bolt bel mm ec D D wo e The parameter RAM is accessible by both the CPU and the TPU It typically is used to pass information between the CPU and TPU and is used by the TPU for scratch and storage For instance the CPU might store t
142. at you follow the following naming convention Build script files from ASH WARE begin with zzz Build script files not from ASH WARE don t begin with zzz Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 301 20 Building the Target Environment 20 2 The string zzz was chosen so that these files would appear at the end of a directory listing sorted by file name ASH WARE recommends that when you modify a build batch file you remove the letters zzz from the file name When you create a new file ASH WARE recommends that the file name not begin with the string zzz The following is a list of some of the build batch files loaded by the ASH WARE installation utility zzz_ TpuSim MtDtBuild zzz_2Sim32_1TpuSim MtDtBuild zzz_1Sim32 MtDtBuild zzz_ Bdm32 MtDtBuild How would you modify the zzz_1Sim32 MtDtBuild file to create a larger RAM ASH WARE recommends the following procedure Copy file zzz_1Sim32 MtDtBuild to file BigRamSim32 BuildScript Modify file BigRamSim32 BuildScript Build Script Commands instantiate_target_exl enum TARGET_TYPE enum TARGET _SUB_TYPE TargetName This command instantiates a target enum TARGET_TYPE and assigns it the name TargetName The enum TARGET_SUB_TYPE specifies target core specific settings Subsequent references to this target use the target name specified in this command Of particular interest to the eTPU is file zzz_eTpuVersions Dat wh
143. atically executes a primary script commands file if one is open A new or alternate script commands file must be opened before it is available to the simulator debugger for execution The desired script commands file is opened via the Files menu by selecting the Scripts Open submenu and providing the appropriate responses in the Open Primary Script File dialog box The simulator debugger displays the open or active script commands file in the target s configuration window Only one primary script commands file may be active at one time Help is available for this window when it is active and can be accessed by depressing the lt F1 gt function key 6 3 ISR Script Commands Files Currently the ability to associate a script commands file with an interrupt is limited to the eTPU and TPU simulation targets Script commands files can be associated with interrupts When the interrupt associated with a particular eTPU TPU channel becomes asserted the ISR script commands file associated with that channel gets executed In the eTPU ISR script commands files can be associated with channel and data interrupts as well as with the global exceptions Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 37 6 Script Commands Files There are some differences between the primary script commands file and ISR script commands files Some important considerations are listed below page 38 Multi Target Development Tod ISR script co
144. ation in that an access in any of the CPU s address spaces becomes an access to the TPU s PINS space For example if the CPU performs a data read within this block the value of the TPU s channel pins will be what actually gets read Shared Memory Address Offset Shared memory need not appear in the same address from the perspective of each target Indeed shared memory usually appears at different addresses for each target that is sharing that memory The following illustrates this set_block_to_dock HostCpu TpuDataDock ALL SPACES Tpu TPU_DOCK_OFFSETT In this example an offset of TRU_DOCK_OFFSETT is applied to any HostCpu access within the docking block For example if the docking block is at address FFE00 Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 295 20 Building the Target Environment hexadecimal and an offset of FFE00 hexadecimal is applied by defining TPU_DOCK_OFFSETT to this value a CPU access at address FFE20 occurs at address 20 within the TPU Shared Memory Timing Timing transformations allow the clock per access to be specified for the docking block For instance a shared memory block between a TPU and a CPU might take the CPU two clocks to access but might take the TPU only a single clock There is no special method for doing this The timing parameters specified by each of the targets own dock block apply to the docking target A Complete Shared Memory Example The example i
145. ation of angle indices required to display current angular information in various portions of the visual interface including the Global Time and Angle Counters window In a typical automotive application the angle hardware is used as a PLL on the actual engine Typically two engine revolutions are defined as a single cycle so a cycle is defined as 720 degrees Also a typical crank has 36 teeth and rotates twice per engine revolution The following script command generates this configuration This configures the visualization of the crank define DEGREES PER CYCLE 720 define TEETH PER CYCLE 72 set_angle_indices DEGREES_PER_CYCLE TEETH PER_CYCLE This command configures angle visualization for a cycle of 720 degrees and a crank with 36 teeth which rotates twice per cycle yielding 72 teeth per cycle eTPU STAC Bus Script Commands The STAC Bus for sharing time bases TCR1 TCR2 between eTPU engines on dual eTPU microcontrollers can be configured with the following script commands write _stac_tcrl _enable write_stac_tcrl_assignment Mode write _stac_tcrl_ server ServerID 1994 2015 ASH WARE Inc Reference Manual 6 Script Commands Files write _stac_tcr2 enable write_stac_tcr2_assignment Mode write_stac_tcr2_server ServerID The enable commands allow the specified time base to be exported to or imported from the STAC Bus Whether the time base acts as a server or client is determined by Mode where a Mode o
146. ator This displays either the number of ticks since the last target reset if available or the current angle if available This indication may not be valid for hardware targets that have been free run since the last reset as simulator debugger is not able to determine the number of clock ticks under this condition The users selects between ticks and angle from the IDE Options Dialog Box To the right of the ticks indicator is the steps indicator This indicates the number of opcodes that have been executed for the active target since the last reset The limitations listed above for the ticks indicator also applies to the steps indicator To the right of the steps indicator is the failures indicator The failures indicator lists the number of script commands and behavior failures respectively To the right of the failures indicator is the target type indicator This is a bitmap that depicts the type of target that is currently active To the right of the target type indicator is the current time indicator This displays the amount of time that has occurred since the last target reset The limitations listed above for the ticks indicator also applies to the current time indicator To the right of the current time indictor is a clock Use this to determine if it is time to go home page 274 Multi Target Development Td 1994 2015 ASH WARE Inc Reference Manual 19 Supported Targets and Available Products 19 Supported Targets and Availa
147. ault search is Vector Project Open and Project Save As Dialog Boxes The Project Open and Project Save As dialog boxes are opened from the Files menu by selecting the Project Open submenu or the Project Save submenu From the Project Open dialog box a Project filename is specified MtDt loads a new configuration from this file From the Project Save As dialog box a Project filename is specified The current configuration is saved to this file Run MtDt Build Script Dialog Box The Run MtDt Build Script dialog box specifies which MtDt build script is to be run Running an MtDt build script has a large impact Before the new script is run open windows are closed and all target information is deleted from within MtDt This effectively erases most of the Project information so it is usually best to create a new project before opening a new MtDt build script Save Behavior Verification Dialog Box The Behavior Verification dialog box is opened from the Files menu by selecting the Behavior Verification Save submenu This capability is only available for the eTPU and TPU simulation targets The recorded behavior is saved to this file Save Coverage Statistics Dialog Box The Save Coverage Statistics dialog box is opened from the Files menu by selecting the Coverage Statistics Save submenu This dialog box is currently only available for TPU Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 239 16 Dialog Boxe
148. ayed The count of the number of behavior verification errors that have occurred is displayed See the Pin Transition Behavior Verification section The count of the number of user defined verification tests that have failed since the last reset is displayed User defined tests are part of script commands files See the Script Commands Groupings section for a description of the various script commands that support user defined tests Versions Version information on the device being simulated TPU1 TPU2 TPU3 the Simulator and the microcode assembler is listed Files The name of the project file is displayed See the Project Sessions chapter for a detailed explanation of this capability The name of the MtDt build script file is displayed See the Building the Target Environment chapter and the MtDt Build Script Commands File chapter for detailed explanations of the available capabilities and format of this file The names of the open source microcode primary script primary script report startup script and test vector files are displayed These files are listed relative to the path of the open project file Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 203 15 Operational Status Windows 15 3 2 The auto build file name is displayed The auto build file allows direct building of the executable image from within MtDt and is covered in the Auto Build Batch File Options Dialog Box section The pin
149. ble Products Due to its layered design simulator debugger supports a variety of both simulated and hardware targets Customer requirements dictate that these capabilities to be offered as specific individual products 19 1 MC33816 Hardware Debugger The MC33816 Hardware Debugger can only be launched from the Run On Hardware button in the IDE as show below ASH WARE MC33816 DevTool IDE V1_99B DEMO C Temp DevToo lProjects DcDcConverter DcDcDemo Spd816IdeProj File Build Edit Step Run Breakpoints View Options Help Re DSDRSaEP See Z HEHEH LE Sex DeDeConverterDemo psc DcDcConverterDemoTest Spd816Command E 45 Target De ae DAC Settling 0x1 A9 A 0x00 When the debugger opens everything from the simulation session is duplicated in the debugger This includes loading of the source code running the startup script file etc The MC33816 Hardware Debugger and MC33816 Simulation IDE share this same manual However not all capabilities available to the simulator are available to the Reference Manual C 1994 2015 ASH WARE Pgri Target Development Tool page 275 19 Supported Targets and Available Products 19 2 19 3 debugger Conspicuous examples are source code breakpoints goto source code line goto state machine state and so forth These simulation capabilities are simply not supported by the hardware and therefore cannot be replicated in the debugger The timing in the wait_time and at_time script com
150. ble file can then loaded into the simulator debugger The name of the executable file varies quite a bit from one vendor and tool to another Generally TPU microcode executable files have a LST suffix while a compiler linker might produce a file named A OUT Source Code Search Rules Source code files may be contained in multiple directories In order to provide source level debugging the simulator debugger must be able to locate these files Source code search rules provide the mechanism for these files to be located The search rules are as shown below These rules are performed in the order listed If multiple files with the same name are located in different directories the first encountered instance of that file per the search rules will be used Search relative to the directory where the main build file such as A OUT is located Search relative to the directories established for the specific target associated with the source code Search relative to the global directories established for all targets In the search rules listed above the phrase search relative to the directory is used What does this mean It means that if the file is specified as Dir Dir2 FileName xyz start at the base directory and go up one then look down in directory Dir2 and search in this directory for the file FileName xyz Note that the search rules apply only to source code files in which an exact path is not available If an e
151. block ModelCpu 0xD0004 MEM END B2 ALL_SPACES Set the lowest empty block to dock with the TPU target set_block_to_dock ModelCpu TpuPinsDock ALL_SPACES Tpu O 0xC0000 Make sure that no matter which space the TPU accesses within this dock the TPU s pins space is always accessed set_block_dock_space ModelCpu TpuPinsDock ALL SPACES RW_ALL TPU_PINS_SPACE Set the middle empty block to dock with the HOST CPU set_block_to_dock ModelCpu CpuCpuShare ALL_SPACES HostCpu 0x70000 0xC0000 RRRKKKKKKKKKKKKKK END OF MODELING CPU kkk RK KKK kdk k k In this example the shared memory architecture from the above figure is generated Simulating Mirrored Memory Mirrored memory is memory that is accessible at multiple address ranges within a memory map This can occur for instance when not all address bits are decoded for a memory device The following figure depicts an 8K memory device that resides in a 64K memory system Assume it is an 8 bit wide device Since the 8K device is on a byte wide bus the device itself decodes the lower 13 address bits A12 through AO Assume that the memory controller decodes only the upper two address bits A15 and A14 and enables the device when both are zero This means that nothing decodes A13 and thus the memory device is Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 299 20 Building the Target Environment activated w
152. branch instruction where the branch path has been traversed A red box indicates an assembly branch instruction where the non branch path has been traversed O E P Hl A white box indicates a C source line or assembly instruction that has been executed Code Coverage Verification Commands The code coverage verification commands described in the Code Coverage Script Commands section provide the capability to verify both instruction and branch coverage percentages on both an individual file basis and a complete microcode build If the required Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 133 9 Functional Verification coverage has not been achieved then a verification error message is generated and the count of script failures found in the configuration window is incremented Code Coverage Report Files Code coverage report files can be generated using the write_coverage_file filename Coverage script command described in the Code Coverage Script Commands section Code coverage report files can also be generated directly from the File menu by selecting the Coverage submenu This is described in the Files Menu section The top of the code coverage report file contains a title line a copyright declaration line and a time stamp line Following this generic information is a series of sections The first section provides coverage data on the entire microcode build Succeeding sections provide coverage
153. buffer is flushed following a reset Multiple Target Considerations Individual trace settings are maintained for each target In a multiple target environment it is possible to enable trace settings in one target and disable these same settings in another target The target on which the Trace Options Dialog Box acts is listed at the top of the dialog box This corresponds with either the active target at the time that the dialog box is opened or the target associated with the active window Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 255 16 Dialog Boxes 16 16 16 17 Local Variable Options Dialog Box It is important to note that the Local Variables window automatically tracks the current function When the target transitions from running to stopped the active function s local variables are automatically displayed But in addition when you scroll through the Call Stack window the Local Variable window automatically displays the stacked local variables associated with selected line in the Call Stack window This automatic behavior is generally quite useful but in certain cases it can get in the way By locking the local variable window you are able to disable this automation Lock the local variables from lt functionName gt at stack frame lt frame Address gt When this is checked the Local Variable window displays a particular function s local variables The normally automatic tracking of the curr
154. capabilities for which an overview is given in the Functional Verification chapter Pin transition behavior verification capabilities include the ability to save recorded pin transition behavior to enhanced pin transition behavior ebv files the ability to load saved pin transition behavior files into the simulator debugger and the ability to verify that the most current pin transition behavior matches the saved behavior Old style behavior verification files bv can still be read and used for verification but can no longer be created All pin transition behavior verification must now be managed via scripting GUI menu options are no longer available From a behavioral model perspective these capabilities correlate to the ability to create behavioral models and the ability to compare source microcode against these behavioral models The emphasis in the simulator debugger is on the automation of these modeling capabilities through script commands as the capabilities are no longer available from the menus Pin Transition Buffers There are two pin transition storage buffers in the simulator debugger as shown in the following diagram Loaded As Simulator Runs Read From File Running Buffer lt a Master Buffer of Recorded Pin Compare of Pin Transition Transition Behavior Behavior Saved To File 1994 2015 ASH WARE Inc Reference Manual 9 Functional Verification The running buffer is filled as the simulator debugger runs Wheneve
155. cause it displays only the information from a single channel it may not reflect the true worst case eTpu1 ThreadStats RevA ch loj x THREAD STEPS Addr Cov Cnt We Tot WC Time 6 82DE 1 1 1 18 18 366 nS INITIALIZE 1 62FC 1 4 2 2 4 646 nS RE_INIT_INTERRUPT 2 6304 1 4 115 25 2338 566 nS RECEIVED DATA BIT 6 23 3 6368 1 4 25 23 529 466 NS RECEIVED_DATA_BIT_24_31 4 DER 174 9 16 123 326 nS VALID_GAP_AND_DATA 5 6478 6 4 8 8 8 UALID_GAP_NO_DATA 8498 6 2 8 8 TOO_MANY_BITS_ FAULT 7 G4B4 6 2 H 8 BIT_DETECTED_IN_GAP_HUNT 8 G4E4 0 4 8 8 LINE_WENT_IDLE_FAULT 9 6506 6 3 8 8 INVALID_THREAD_FAULT deg A One issue with this window is that the worst case threads during initialization are often much worse that is seen during execution of the function Since these initialization threads are not normally an issue it is helpful to be able to clear out all thread data following initialization This is done using the script commands described in the Thread Script Commandssection Note that in the above window the Cov coverage column shows for most of the threads This is because each of these threads has been configured to respond to four different event vector combinations yet the simulation run to this point has covered only one of these Which of these event vector combinations has been covered Select the ungroup option to see Reference Manual C 1994 2015 ASH WARE D Target Development To
156. ccesses are set to two clocks per access and odd accesses are set to three clocks per access In this example these settings apply to all address spaces and for all read and write accesses though it is possible to indicate the specific set of address spaces and access types for which this applies Address Fault Control For each address space and access type an address fault can be set to occur on odd accesses Note that this is generally not applicable to 8 bit accesses though it is still available define CODE_SPACE CPU32_SUPV_CODE_SPACE CPU32_USER_CODE_SPACE set_block_to_addrs_fault MyCpu Rom CODE_SPACE READ ALL In this example odd read accesses to the memory block s code space are configured to cause an address fault Bus Fault Control For each address space and access type a bus fault can be set to occur set_block_to_bus_fault MyCpu Rom CPU32_USER_CODE_SPACE RW_ALL In this example any access while at the user privilege level result in a bus fault This might be useful in a protected system in which a user process is prevented from accessing hardware Sharing Memory A fundamental aspect of multiple target simulation is the ability to share memory MtDt employs docking to implement shared memory If two targets are to share memory one target must dock memory blocks to another target There is a fundamental and important lack of symmetry in that one target must provide the dock from bloc
157. ce Manual Branches 60 Branch Hits 16 Branch Coverage Percent 26 7 MAKE ASC Instructions 2 Instruction Hits 0 Instruction Coverage Percent Branches 0 Branch Hits 0 Branch Coverage Percent 100 0 toggle UC Instructions 5 Instruction Hits 5 Instruction Coverage Percent Branches 0 Branch Hits 0 Branch Coverage Percent 100 0 pwm UC Instructions 24 Instruction Hits 14 Instruction Coverage Percent Branches 12 Branch Hits 3 Branch Coverage Percent 25 0 linkchan uc Instructions 8 Instruction Hits 0 Instruction Coverage Percent Branches 0 Branch Hits 0 Branch Coverage Percent 100 0 uart UC Instructions 58 Instruction Hits 38 Instruction Coverage Percent Branches 30 Branch Hits 13 Branch Coverage Percent 43 3 Code Coverage Annotated Listing Files 9 Functional Verification 0 0 100 0 58 3 0 0 65 5 Listing files source file lines with the associated disassembled opcodes shown below each line that generates code annotated with code coverage information can be generated with Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 135 9 Functional Verification the write_coverage_listing_file script command described in the Code Coverage Script Commands section An option parameter allows users to select between outputting a complete annotated listing file for a specified module or output just the source lines and object code not executed covered
158. cript Integer Data Types In order to maximize load time checking script command files support a large number of integer data types This allows constant overflow warnings to be identified at load time rather than at run time In addition since the scripting language supports a variety of CPUs with different fundamental data sizes the script command data types are designed to be target independent This allows use of the same script files on any target without the possibility of data type errors related to different data sizes The following is a list of the supported data types along with the minimum and maximum value Ut valid range is 0 to 1 Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 43 6 Script Commands Files 6 5 5 6 5 6 page 44 Multi Target Development Tod 1 J2 valid range is 0 to 3 i J3 valid range is 0 to 7 1 ES 4 valid range is 0 to 15 5A valid range is 0 to 16 5B valid range is 0 to 31 8 valid range is 0 to OxXFF J16 valid range is 0 to OXFFFF 32 valid range is 0 to OXFFFFFFFF J64 valid range is 0 to OXFFFFFFFFFFFFFFFF Eo EE o e a Ee ie ie A 1 E Referencing Memory in Script Files Memory can be directly accessed by referencing an address Two parameters must be available for this construct an address and a memory access size In addition there is an implied address space which for most targets is supervisor data For some targets the
159. d The auto build file allows direct building of the executable image from within MtDt and is covered in the Auto Build Batch File Options Dialog Box section Verification The count of the number of user defined verification tests that have failed since the last reset is displayed User defined tests are part of script commands files See the Script Commands Groupings section for a description of the various script commands that support user defined tests Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 213 15 Operational Status Windows 15 4 5 CPU32 Register Window PC SSP SFC AG Di A2 A3 A4 A5 A A7 SR 00009011C 66636666 666606065 22222222 11111111 666660622 666660623 66660624 66660606025 666660626 66636666 2763 UBR 666606666 USP 66666613 DFC 66666665 DO D1 D2 D3 D4 HABA 33333333 66666632 66666633 66660634 666060635 66660636 666660637 The CPU32 Registers window displays the CPU32 s registers These are the Program Counter PC the Vector Base Register VBR the Supervisor and User Stack Pointers SSP and USP the Alternate Function Code registers SFC and DFC the Address registers AO through A7 the Data registers DO through D7 and the Status Register SR 15 4 6 CPU32 Disassembly Dump Window The CPU32 Disassembly Dump window displays disassembled code starting at the target s program counter 15 5 SIM Module Windows The fo
160. d 15 High and Low Registers RX14MSKHI RXI4MSKLO RXISMSKHI RX1ISMSKLO the Interrupt Mask and Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 233 15 Operational Status Windows Flag Registers IMASK IFLAG the Receive and Transmit Error Counters RXECTR TXECTR 15 11 2 TouCAN Buffers Window 32My68376 TouCAN Buffers Buf Ctrl Sts 15 N A 14 N A 13 N A 12 N A 11 N A 16 N A 9 N A 8 N A 7 MZA 6 NZA 5 NZA 4 NZA 3 MZA 2 NZA 1 MZA 8 NZA ID HIGH DEDF 2BF7 1FEF FFD BBFB FEFF AEA DDF6 SDBF FEC 73F9 S7FE 2AF7 FD7D FF7B FFEA ID Low E645 FFFF 7C5F 75EB FFDF B7F7 E59D 7DFF EBDF FFDF EF3A F7AF EAEB F67F FFFF F79E D6 D1 FB 5F F7 FF 3E BE 7B F4 A4 5F 7F C9 FD CF FE FF FD 3F EF DE FF CF 7F D3 F7 FF 7D B5 EE F9 AF DF DATA BYTES D2 D3 FF EE FA 36 7F B7 FF FF 5B 67 FC EF 57 72 56 EF D9 27 FB F7 7F EB F2 FF DF BF D9 FB FF EB FF 7F D4 D5 4D AF F7 F7 B6 FE F EF CF CR OF 76 FF EF DE 3F CD B6 DF DC 1F B4 9D 7A F7 F7 2F FF FF AE B7 5D D6 D7 FD F3 D7 F5 AF 75 gr 9B 7D E7 9A A3 DD F7 CF D7 B7 BF FF FF 71 FA DF FF 7D F7 BS EI FD 7D FC DE Enabled Disabled ENABLED Disabled Disabled Disabled ENABLED Disabled ENABLED Disabled ENABLED Disabled Disabled ENABLED ENABLED ENABLED Disabled ll x INTERRUPTS Flag clr
161. d Right Vertical Cursors cccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeees 162 14 5 Displaying Behavior Verification Data cccccceeeeeeeeeeeeeeeeeeeeeeeeeeeeees 164 14 6 Mouse Functionality ccccceeeceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeseeeeeeeeeeeeeees 164 14 7 Vertical Yellow Context Time Cursor cccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeees 165 UE UNE 166 14 9 Display Pane Boundary Time Indicators 0 ccccceeeeeeeeeeeeeeeeeeeeeeees 167 14 10 Data Storage Buffer Start Indicator cccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeens 167 14 11 Current Time Indicator ccccceeeeeee eee ee eeeeee ee eeeeee ee eeeeeeseeeeeeeseeeeeeeeeeneeees 167 1412 Auto Scroll geed cowed E a ARA 167 14 13 Button Controls iissc 2 cccceceetisedeccen hecntae cee eet eed Mae eee ee 167 14 14 Timing Display cccccceeeeeeeceeeee ee RRE EE eeeeeeeeeeeeeeseeeeeeeseeeeeeseeeeeeeseeeeeees 168 page 6 Multi Target Development Tool Multi Target Development Tool 14 15 Data Storage Buffer 20 ccceeeeceeeee cece cece nese ee ee eee seca eeseeeeeeeeeeeeeeeseeeenes 169 Part 15 Operational Status Windows 171 15 1 Generic WiINKOWS ciiai noiera danosa taad aaa ada aaa aa essa aoea raaraa aa aa 174 Source Code Windows ccceeccsseeceeeeeeeeeeeneeeeeseeeeeeeeeneneseseeeeeeeeensaeseseeeeneeeeeeneeeeee 174 Script Com mands Window ceesessteseeeseesessesseeseese
162. d boundary 1 5 9 that 16 bit accesses must be located on even boundaries Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 83 6 Script Commands Files 0 2 4 and that 8 bit numbers can be on any address boundary The address is specified as an offset from the base of parameter RAM write_global_data32 0x20 OxC6E2024A verify global_data32 0x20 OxC6E2024A verify global_data24 0x21 OxE2024A verify global_datal6 0x20 OxC6E2 ie verify global_datal16 0x22 Ox024A verify global_data8 0x20 0xC6 J7 verify_global_data8 0x21 OxE2 E verify global_data8 0x22 0x02 Ae verify global_data8 0x23 Ox4A In this example data at an address offset of 0x20 relative to that eTPU s engine base address word is written with a 32 bit value OxC6E2024A hex The written value is then verified as 32 24 and 8 bit sizes Note the ETEC eTPU C Compiler automatically generates all needed global variable address data into the auto defines file as a series of macros no explicit user effort is required Bitwise access to engine space parameter RAM is supported with a set of matching functions to those above write_global_bits32 AddrOffset BitOffsetFromMSB BitSize Val write_global_bits24 AddrOffset BitOffsetFromMSB BitSize Val write_global_bits16 AddrOffset BitOffsetFromMSB BitSize Val write_global_bits8 AddrOffset BitOffsetFromMSB BitSize Val verify global_bits32 Add
163. d write value actions Action tags that are embedded in source code are associated with the underlying executable code as follows The search for executable code begins at the line that contains the action tag and moves downwards in the source code file If no executable code is found at or below the line where the action tag appears then the search continues upwards If there is no executable code associated with the source code file at all then the action tag fails See http www etpu org for an example application Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 147 10 Action Tags 10 1 page 148 Multi Target Development Tho Print Action Tag The Print action command is similar to the C languages prinf function and has essentially the same syntax There are two flavors available the first being print_to_trace The resulting text appears as a line in the Trace window When coupled with the ASH action tag in the source code file looks similar to the following ASH print_to_trace action tag test 1 ASH print_to_trace action tag test 2 Q ASH print_to_trace variable A d n A As with the C printf the first argument is the format string The ASH WARE Print command uses the same syntax for the format string which can then be followed by a varying number of arguments The Print command checks that the number of conversion characters in the format string matc
164. d writes channel ChanNum s 16 bit parameter ParamNum to value Val write_par_ram 3 1 0x2222 In this example channel 3 s parameter one RAM word is written to value 2222 hex verify ram_word ChanNum ParamNum Val This command verifies that channel ChanNum s RAM word number ParamNum is equal to Val If the verification fails a verification failure messages is printed to the screen This verification failure message can be disabled from the Message Options dialog box The accumulated count of verification failures is available in the Configuration Window verify ram_word 0xa 3 0x1324 In this example channel 10 s parameter RAM word three is verified to be equal to 0x1324 hex If the value is indeed equal to 0x1324 hex then the simulation continues If the value is not equal to 0x1324 hex an error message is printed to the screen verify Cam Dit ChanNum ParamNum BitNum Val This command verifies that channel ChanNum s RAM word number ParamNum bit BitNum is equal to Val Bit 15 is defined as the most significant while bit O is defined as the least significant Val must be between zero and one inclusive If the verification fails a verification failure messages is printed to the screen This verification failure message can be disabled from the Message Options dialog box The accumulated count of verification failures is available in the Configuration Window verify ram_bit 0xa 3 14 1 In this example channel 10
165. dard for the eTPU function is specified as follows pragma ETPU_function Pwm alternate void Pwm int24 Period int24 PulseWidth 1994 2015 ASH WARE Inc Reference Manual 6 6 30 6 Script Commands Files In the Byte Craft eTPU C Compiler the event vector mode can be automatically generated using the following macro pragma write h define PWM_ALTERNATE_ENTRY_VAL ETPUentrytype Pwm Note that setting of the event vector table s base address is covered in the System configuration commandsSYSTEM_CFG_CMDS section write_chan_ entry _pin_direction ChanNum Val This command writes channel ChanNum s event vector pin direction to Val Note that this writes the CxCR register s ETPD field A value of 0 uses the channel s input pin and a value of 1 uses the output pin define ETPD_PIN_DIRECTION_INPUT 0 define ETPD_PIN_DIRECTION_OUTPUT 1 write_chan_entry_pin_direction UART1_CHAN ETPD_PIN_DIRECTION_INPUT write_chan_entry_pin_direction UART2_CHAN ETPD_PIN_DIRECTION_OUTPUT In this example the UART1 chan event vector table thread selection is based on the input pin and UART2 event vector thread selection is based on the output pin See the System Configuration Commands section for information on setting the entry table s base address eTPU Interrupt Script Commands Interrupts can cause special script ISR file to execute as described in the Script ISR section clear_chan_intr ChanNum
166. dded a new String within a String format to extend the print and print_to_trace script commands such that they now support formatted symbolic information Added the GNU CPP pre processor cpp exe to script command files thereby supporting capabilities such as global variable and static local initialization among other things Added the ability to pass multiple defines from the command line and also to define strings and values previously on a single value less define was supported Added a command line switch that suppresses the Source Code Missing message when running automated tests Improved tracing data by adding such things as the ME Match Enable bit value to the trace file thereby supporting our companion latency analyses tool see our website for a description Added a verify_version script command to warn the user if there are dependencies on a particular simulator version Version 3 42 Enhancements Reference Manual Improved the Drag And Drop of time in the logic analyzer window The dump_file script can now append to any existing file The verify_files script is useful for logged regression testing using a gold file When building the simulation environment using an eTPU simulation model the eTPU sub type can be specified This supports version specific features and bug simulation Added the ability to specify the target Version such as MPC5554 eTPU Specify the full 32 b
167. de Group State Frequency Wave In addition there is an eTPU example of the waveforms generated for an automobile engine monitor system Comments Test vector files may contain the object oriented C style double slash comments A comment field is started with two sequential slash characters All text starting from the slashes and continuing to the end of the line is interpreted as comment The following is an example of a comment This is a comment Node Command node lt Name gt lt Node gt The node commands assign the user defined name Name to a node Node Note that depending on the microcontroller the input and output from each channel may or may not be brought to external pins Please refer to the Freescale literature for the specific microcontroller being used Standard eTPU Nodes ch0 in Channel 0 s input pin Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 117 8 Test Vector Files cht out Channel 0 s output pin chl in Channel 1 s input pin chl out Channel 0 s output pin ch31 in Channel 31 s input pin ch31 out Channel 31 s output pin terclk eTPU external clock input pin In the example shown below the name A429Rcv is assigned to the eTPU s channel 5 input pin node A429Rcv ch4 in Standard TPU Nodes CHO Channel 0 s I O pin CH1 Channel 1 s I O pin CH15 Channel 15 s I O pin TCR2 TPU Counter 2 gate clock input pin
168. de transitions in a graphical format similar to that of a classical logic analyzer The display can be continuously updated as MtDt runs or the user can turn off the automatic display update and scroll through previously recorded transition data eT PU_A Logic Analyzer DEAR J Axto Seroll D 8 EAS l 042 841 6 vS Movse 060 265 1 vS 073 585 3 uS Data Start 000 000 0 vS Context 066 915 5 vS Current Time 072 322 8 vS i Set Left Cursor 044 875 5 uS Delta Cursor 014 971 7 uS Right Cursor 059 847 2 vS Reference Manual C 1994 2015 ASH WARE Pgri Target Development Tool page 159 14 The Logic Analyzer 14 1 Executing to a Precise Time It is informative to consider how to execute the simulator to the precise time of the falling edge indicated by the arrow 1 shown in the picture below Use the keyboards up and down arrows to highlight the UART_RCV waveform Drag the Left Cursor near to the desired edge using the mouse Snap to the actual edge using the left and right arrow keys on your keyboard In the picture below this edge is shown to occur at 2 191 1 microseconds Place the cursor over the field showing the time of the left cursor indicated by the second arrow An open hand A will appear indicating that this time can be copied Begin dragging the time by holding the left mouse button down to forma closed hand Drag the time closed hand over the waveforms Drop the time unto the waveforms by releasi
169. dow has a user specified symbol on the far left This is the symbol whose resolved value will be displayed To the right of the user defined symbol is an options button This button accesses the Watch Options dialog box In future versions of this software this dialog box will allow individual settings for the watch to be specified To the right of the options button is a vertical separator bar You can drag the vertical separator bar left or right using the cursor To the right of the vertical separator bar is the symbol resolution field If a value from the user specified symbol can be resolved then this field is automatically displayed Otherwise a message is displayed indicating that the specified symbol could not be resolved The user can edit the user resolution field In future versions of this software this will cause the actual variable values within the targets to be modified Symbolic Data Options The Watches window supports both global and local variables Variables are resolved by looking at the innermost local scope first followed by any outer scopes in order then followed by any static variables and finally the global scope Currently a subset of C syntax is supported for the left hand side symbol input 1994 2015 ASH WARE Inc page 178 Multi Target Development Tho Reference Manual 15 Operational Status Windows Pointers can be dereferenced with the operator The address of variables can be found with the
170. e exits This is especially useful in automated testing where the test would otherwise fail if no floating license were available The amount of time to wait for a floating license to become available is specified by the NetworkRetry parameter passed on the command line See the Command Line Parameters section for specifying this parameter Dongle Licensing A dongle is a physical device that attaches to a USB port on your computer With a dongle license you can run the software in a fully functional mode as long as the dongle is connected to your computer If you unplug the dongle then the software will run only in a demo limited mode A dongle effectively replaces the license file in that you can move the software and dongle to a different computer and it will run in fully functional mode without any interaction with ASH WARE This is particularly valuable in say aerospace in which the software must be functional for many decades Since the software can be moved between computers with no interaction with ASH WARE this constitutes a stable long term development and maintenance scenario 1994 2015 ASH WARE Inc page 22 Multi Target Development Tod Reference Manual 3 1 3 Software Upgrades Hearing about Software Releases In order to be notified about ASH WARE s software releases be sure to provide your e mail address to ASH WARE This will ensure that you are automatically alerted to production and beta software releases Other
171. e Port E and Port F Data Direction Registers DDRE DDRF To the right of the bit position field are a variable number of fields Depending on the specific capability of each port the usage direction and value can be selected page 216 Multi Target Development Tho 1994 2015 ASH WARE Inc Reference Manual 15 Operational Status Windows 15 5 3 SIM Chip Selects Window 3 MyBdm3z2 SIM Chip Selects iol x Cp CSBAR CSOR ADDR SIZE MODE BYTE R W STRB WAITS SPACE IPL AVEC PIN WIDTH Boot 6667 7876 600006 1M synch Both Both AS xD S U All Off 16 Bit CS CSO 66668 AHOA 880066 2K Asynch Disable Beud AS 6 Cpu All Off 16 Bit CS CS1 66668 7876 600066 2K synch Both Both AS 6G6xD S U All Off 16 Bit CS CS2 6668 prp 600006 2K Asynch Both Both AS Dep S U All Off 16 Bit CS CS3 6868 AHOA 600006 2K Asynch Disable Rsud AS Cpu All Off 16 Bit CS CS4 6666 6666 666666 2K Asynch Disable Rsud AS Cpu All Off 16 Bit CS CSS 6666 6666 680066 2K Asynch Disable Beud AS Cpu All Off 16 Bit CS CS6 6666 6666 OOOHOO 2K Asynch Disable Rsud AS Cpu All Oort CS7 6668 6666 600066 2K Asynch Disable Rsud AS Cpu All Off ADDR26 CS8 6666 6866 660066 2K Asynch Disable Beud AS Cpu All Off ADDR21 CS9 6666 6666 660066 2K Asynch Disable Rsud AS Cpu All Off ADDR22 CS10 6668 6866 600006 2K Asynch Disable Rsud AS Cpu All Off 16 Bit CS The SIM Chip Selects window displays information for each of the SIMS chip select The second and third fields from the left are the Chip Select Base
172. e been disabled such that the Enable Breakpoints submenu can reactivate all disabled breakpoints Enable All This enables all disabled breakpoints Delete All This deletes all active and all disabled breakpoints At Address This opens a dialog box which allows placing a breakpoint any user specified address This is useful when debugging code for which there is no line number information such as GNU assembly code Delete All Address This deletes all breakpoints for which there is no associated source code Delete All Script This deletes all breakpoints that are in the script commands file All Targets Sub Menu This is only available in multiple target simulators It performs the Disable Enable and Delete Breakpoint functions for all targets The default is for just the active target Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 267 17 Menus 17 5 17 6 Help This accesses this help screen Workshops The Activate menu allows you to specify which workshop and target are active These capabilities are accessed via the following submenus Workshop This displays a list of workshops that can be activated Activation of a workshop causes all windows within that workshop to be displayed and the target associated with that workshop if any to be activated Activation of an associated target upon workshop activation is a feature that can be disabled within the Workshop Options dial
173. e from within MtDt and is covered in the Auto Build Batch File Options Dialog Box section Verification The count of the number of user defined verification tests that have failed since the last reset is displayed User defined tests are part of script commands files See the Script Commands Groupings section for a description of the various script commands that support user defined tests Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 211 15 Operational Status Windows 15 4 2 CPU32 Simulator Busses Window 32 MySim32 Busses of x Instruction Sub Instruction Instruction Size This is a 16 bit Word instruction A BUS Source 16 Bit 1234 Addr 66666266 Operand Address Register Indirect with Data16 Displacement Space Supervisor Data Space seess B BUS Source 16 Bit FOFO Destination 16 Bit 6324 Operand Data Register Space SEET CLOCKS Instruction Fetch 6 A Bus Load 3 B Bus Load 8 Instruction min 2 B Bus Store 8 The CPU32 Simulator Busses window displays detailed information regarding the just executed instruction This includes the data flow within the simulated CPU32 the data flow between the simulated CPU32 and external memory and timing information 15 4 3 CPU32 Simulator Interrupt Window 52 Host32 Interrupts oj xi Source Vec Lul IARB Time Clocks E TpuSin 6 46 3 2 664 796 8 6666013A66 TpuSin E 4E 3 2 664 796 8 6666013N66 TpuSin F AE 3 2 6
174. e script commands files to act as the host and TPU test vector files to act as the external system This is the original ASH WARE product 683xx Hardware Debugger Our TPU Standard Mask Simulator allows you to develop your CPU code used in conjunction with any standard Freescale TPU microcode Currently ASH WARE supports the following three TPU Microcode builds MASKA MASKG MASK MPC5xx This product supports all the capabilities of our system simulator products with the single exception that you cannot load microcode that you have modified Instead the only TPU microcode that can be loaded is the one of the aforementioned standard TPU microcode masks Although you can tailor your configuration to any specific microcontroller mapping the following three configurations are the defaults The default configurations are usually sufficient and intricacies of custom configuration generation need not be explored MASK A 683xx with one TPU mapped at OxFFFEOO MASK G 683xx with one TPU mapped at OxFFFE00 MASK MPC5xx MPC555 with two TPUs mapped at 0x304000 and page 278 Multi Target Development Td amp 1994 2015 ASH WARE Inc Reference Manual 19 Supported Targets and Available Products 0x304400 19 10 CPU32 Stand Alone Simulator Our CPU32 Stand Alone Simulator allows you to load code into a single simulated CPU32 You can also load the standard mask TPU microcode into a simulated TPU 19 11 683xx Hardware Debugger Our
175. e selected endian ordering does not match the natural endian ordering of the target a warning is displayed Insert Watch Dialog Box The Insert Watch dialog box is opened from within the Watch Window using the insert function keys This dialog box contains three lists The left most list of all watches that are currently in use This is helpful when a new watch is desired that is similarly spelled as an existing watch The middle list contains all recently used watches even ones that are no longer in use The right most list contains a list of the print action command and timing action commands This is special tagged text in source code used to generate formatted output to trace files think printf and for verifying that minimum and maximum timing criteria are met for traversal of named timing regions Related Information Naming timing regions in source code Verifying traversal times a script command file View named timing regions timing using the Watch Window List named timing regions in the Insert Watch Dialog Box page 258 Multi Target Development T9 1994 2015 ASH WARE Inc Reference Manual 16 Dialog Boxes 16 21 Watch Options Dialog Box The Watch Options dialog box is currently featureless This dialog box is provided to maintain forward compatibility with future versions of this software 16 22 The About Dialog Box The simulator debugger C 1994 2015 ASH WARE Inc Allrights are reserved Various national a
176. e simulator debugger automatically determines the TPU type from the source TPU microcode so this command is not normally required except for the TPU3 in which TPU2 should be specified because bug in the Freescale TPU assembler prevents selection of TPU3 so this script command is required to specify a TPU3 target In addition there are subtle differences among the TPU1 TPU2 and TPU3 that the TPU assembler hides from the user Use of this instruction can cause significant behavioral deviations between the simulator debugger and the actual TPU hardware This command sets the TPU type and the instruction space size Valid types are 1 through 3 which correspond to TPU1 through TPU3 respectively The instruction space size is expressed in 32 bit long words Supported combinations of types and instruction space sizes are as follows TPU1 256 TPU1 512 TPU2 512 TPU2 1024 TPU2 2048 TPU3 1024 TPU3 2048 write_entry_bank X This command writes the TPU entry bank Valid values depend on the instruction space Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 95 6 Script Commands Files 6 6 38 6 6 39 page 96 Multi Target Development Tod size Each bank consists of 512 32 bit long words so the number of valid banks is equal to the instruction space size divided by 512 For the common size of 1024 there are two valid banks so the maximum valid entry bank is 1 Zero is always a valid entry bank set
177. ebugger and the trace buffer has not overflowed when generating a trace file from the buffer Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 113 7 Trace Buffer and Files For large trace files it is best to use the streaming capability thereby avoiding possible trace buffer overflow issues Parsing the Trace File All post processing on the trace files should be done on files generated using the parseable option Although the file format is intended to be self explanatory it is purposely left undocumented to retain flexibility for future enhancements Instead it is recommended that those wishing to post process the trace files use the trace file parse source code available from ASH WARE The public methods in the TraceParser class are documented and will remain stable for future releases Post processing of the trace file is an excellent way to analyze important performance indices For instance eTPU and TPU latency calculations such as minimum maximum average and standard deviation would be one excellent application Trace Buffer Size Considerations The trace buffer is a set size To increase the effective size it is often desirable to disable certain types of events Disabling and enabling of trace events is accomplished by selecting the Trace submenu from the Options menu 1994 2015 ASH WARE Inc page 114 Multi Target Development Tho Reference Manual 8 Test Vector Files 8 Test Vecto
178. ecified for each individual target and for all targets globally Specifying global search options is useful in situations in which multiple targets are using the same directories for their library files When searching for a source code file the following algorithm If the path to the file is fully specified e g c SomeDir SomeFile c use that if the file exists there e If the path is partially specified e g OneUpDir SomeFile c resolve the path relative to the code image file For instance if the code image file is at c SomeDir SubDir CodeImage EIf then check for this file c SomeDir One UpDir SomeFile c e If the source file is still not found use the raw file name strip any prepended directory information and search in the directory where the executable image file is located e If the source file is still not found use the raw file name strip any prepended directory information and search for the file in the directory s listed in the Selected Targets directory search list starting from the top listed directory e If file is still not found use the raw file name strip any prepended directory information and search for the file in the directory s listed in the All Targets directory search list starting from the top listed directory Add This button inserts a new directory into the search list Modify This button modifies a previously entered search location page 250 Multi Target Development T9
179. ed and layered approach such that the bulk of the code within MtDt can be applied to any target It matters little if the target is big endian or little endian 8 16 32 or 64 bits hardware debugger or simulation engine This allows us to quickly and inexpensively provide support for additional targets Targets and Products From a tools development standpoint there is very little to differentiate one target from another CPUs execute code while peripherals have a host interface and wiggle and respond to I O pins Hardware interfaces provide different means to the same end Current MtDt targets include a MC33816 simulation engine an eTPU2 simulation engine an eTPU simulation engine a TPU simulation engine a CPU32 simulation engine and a CPU32 across a BDM port Support for additional targets continue to be added But from a customer s standpoint there are specific requirements that must be met Individual products are therefore derived from MtDt to meet these customer requirements Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 13 1 Overview As single target products we offer a MC33816 Stand Alone Simulator an eTPU2Stand Alone Simulator an eTPU Stand Alone Simulator a TPU Stand Alone Simulator a CPU32 Stand Alone Simulator and a 683xx Hardware Debugger As full system simulation products we offer a CPU32 MC33816 System Simulator a CPU32 eTPU System Simulator and a CPU32 TPU System Simulator Although
180. ed at install time contains very little page 256 Multi Target Development T9 1994 2015 ASH WARE Inc Reference Manual 16 Dialog Boxes information other than a computer identifier This dialog box allows you to add additional information such as your name purchase order number etc The license file has been a problem for ASH WARE in that users have sent in license files for purchased products but we were unable match the license files with the purchase This dialog box is intended to reduce this confusion thereby allowing us to serve you better All information is optional Generally it is best to include at least your company s purchase order number or the ASH WARE invoice number if available 16 18 BDM Options Dialog Box The following describes the Background Debug Mode BDM Options dialog box Halt Target for Periodic Update When this is selected the free running hardware is halted when simulator debugger redraws its windows The advantage of selecting this is that the windows can be updated as the target runs The disadvantages are that it effectively disables the target s ability to service interrupts and in some cases the target will execute significantly slower 16 19 Memory Tool Dialog Box This tool supports specialized memory functions listed below The dump file functions are also accessible from the dump_file script command listed in the File Script Commands section Fill memory with data or text Search for
181. edge being detected by channel 0 and which forms a detection window Spurious operation could result if these do not correspond Also channel 0 can be programmed to form a detection window and the state of this detection window closed opened is displayed 15 2 4 eTPU Host Interface Window eTpul Host Interface Wu IL xj 1F 1E 1D 1C 1B 1A 19 18 17 16 15 14 13 12 11 16 F E D C BA 8 7 6 5 43 2 1 8 CFSR og 66 66 66 66 66 66 OO 66 66 66 66 65 05 05 05 Dh 64 64 64 64 O4 66 63 63 63 63 63 63 66 62 01 ERR S HI HI HI HI HI HI HI HI HI HI HI HI HI HI HI HI HI HI HI HI HSRR 6 6 6 6 6 6 6 8 6 6 6 6 6 6 8 B 6 6 6 6 6 6 6 B 6 6 6 6 6 6 6 8 FH 66 66 66 66 66 66 OG op HG op op 66 op OG op op 66 66 66 66 66 66 op 66 HA op op OA 66 op 66 op Entry SS Se Se SoS SS SS SS SS SS SS SS SS SSS SS SS S CISR 6 6 6 6 6 6 6 8 6 6 6 6 6 6 86 8 6 6 6 6 6 6 A BA 6 6 6 6 6 6 6 1 CIER 6 6 6 6 6 6 6 8 6 6 6 6 6 6 86 8 6 6 6 6 6 6 6 B 6 6 6 6 6 6 6 86 CIOR 6 6 6 6 6 6 6 8 6 6 6 6 6 6 6 8 6 6 6 6 6 6 6 B 6 6 6 6 6 6 6 1 CDTRSR 6 6 6 6 6 6 6 8 6 6 6 6 6 6 6 8 6 6 6 6 6 6 6 BA 6 6 6 6 6 6 6 8 CDTRER 6 6 6 6 6 6 6 8 6 6 6 6 6 6 6 8 6 6 6 6 6 6 6 B 6 6 6 6 6 6 6 8 CDTROSR 6 6 0 6 6 8 A 6 6 6 6 6 6 6 8 6 6 6 6 6 6 6 8B 6 6 6 6 6 6 6 8 For each channel the following information is shown The Channel Function Select Register CFSR shows the eTPU Function the Channel Priority Register CPR shows the priority for that channel the Host Serv
182. eevseeseeseeneeseesseseseesseeseesoesnesaneas Pin Transition Behavior Script COMMANAS c se seeeeeentestesteeeeeeeeeeeeeeseeeeeeeee 76 Thread Script COM MANAS cecssseseeeteeesteseessesseeseeseeseesnesoesesoesaeveveneeneaneneennanaes Disable Messages Script COMMAMGS cscssssesseeetestestesteseeseeeeeeeeeseeseeenenanees ETPU System Configuration COM Mads secssceeceeeesesseeeeseeseeessenseenseeseneneees ETPU Timing Configuration COM MANAS scsescesceecseeeseeseeeeseeseeessensenenseesenensees eTPU STAC Bus Script Commands eTPU Global Data Write Verify Commands eTPU Channel Data Script COM MAMAS cccetcseeseeseeseeeestestessessevsevseeeneeneneeneenens eTPU Channel Address Script COMMAMNAS cscseeeeteseeetessessevseveeeeneenennennenees 86 eTPU Engine Data Script COMMANGS cctcssessseseeseeeeesestessessesseveeveneenesneneennenaes 86 eTPU Channel Function Mode Script COMMANG cccsetetsseseeseeneeeeeeeeeeeeneenees 88 eTPU Event Vector Entry Condition Standard Alternate Commands 88 eTPU Interrupt Script Commande cc eeetetseseeseeseeseeseeseesesesessevseveneeneenennennanaes 89 eTPU Shared Subsystem Script COM MAMAS uu ce seetetestessesseveeveeeeeeseeneeneenaes 90 TPU Parameter Ram Script CommandS ccccssssseeeeneeeees 91 eTPU TPU Host Service Request Register Script Commands cseseeeees 92 TPU Channel Interrupt Service Register COM MAMAS
183. eference Manual 6 Script Commands Files Cumulative Coverage To produce the highest quality software it is imperative that testing cover 100 of instructions and branches and event vectors for eTPU targets Additionally for quality control purposes this coverage should be proven using the verify_coverage scripts But most test suites consist of multiple tests such that the coverage is achieved only after all tests have run The cumulative coverage scripts provide the ability to prove that the entire test suite cumulatively has achieved 100 coverage The typical testing procedure might work as follows A series of tests is run and at the end of each test the coverage data is stored At the end of the very last test the coverage data from all previous tests are loaded such that the resulting coverage is an accumulation of the coverage of all previous tests Then the verify_coverage script command is run proving that all tests have passed The following illustrates this process Run Test A save_cumulative_file_coverage MyFunc c TestA CoverageData Run Test B save_cumulative_file_coverage MyFunc c TestB CoverageData Run Test M save_cumulative_file_coverage MyFunc c TestM CoverageData Run Test N load_cumulative_file_coverage MyFunc c TestA CoverageData load_cumulative_file_coverage MyFunc c TestB CoverageData load_cumulative_file_coverage MyFunc c TestM CoverageData ver
184. egin and end the embedded string Two example uses of this are shown below write_chan_hsrr TEST1_CHAN 5 wait_time 0 12 Send the results to the trace window print_to_trace TEST RESULTS trace n n A d n KG B d n C d A B C Same as above but to the screen print TEST RESULTS screen n y A d n i B d n i C d A B C 6 5 12 Comments in Script Commands Files Legacy C and the new C style comments are supported as follows This is a comment set_tdl1 3 This is a legacy C style comment This is also a comment This is the end of the multiple line comment set_tdl more comment 3 6 5 13 Decimal Hexadecimal and Floating Point Notation in Script Files Decimal and Hexadecimal notation are interchangeable 357 Decimal Notation 0x200 Hexadecimal Notation In certain cases floating point notation is also supported page 50 Multi Target Development Tod 1994 2015 ASH WARE Inc Reference Manual 6 Script Commands Files 3 3e5 Floating Point 6 5 14 String Notation The following is the accepted string notation STRING The characters between the first quote and the second quote are interpreted as a string File dat This denotes a string with eight characters and termination character as follows F T e Vi d a t NO Concate nation It is often desirable to concatenate stings The following example illustrates a case in wh
185. elopment Tod write_chan_bits16 ChanNum AddrOffset BitOffsetFromMSB BitSize Val write_chan_bits8 ChanNum AddrOffset BitOffsetFromMSB BitSize Val verify _chan_bits32 ChanNum AddrOffset BitOffsetFromMSB BitSize Val verify _chan_bits24 ChanNum AddrOffset BitOffsetFromMSB BitSize Val verify _chan_bits16 ChanNum AddrOffset BitOffsetFromMSB BitSize Val verify _chan_bits8 ChanNum AddrOffset BitOffsetFromMSB BitSize Val These script commands allow the writing and verification of bitfields within the specified unit The bit offset is from the MSB of the unit For example to set a _Bool bit that is in the LSB of an 8 bit unit the script command would be set _Bool at LSB of 8 bit unit to 1 write_chan_bits8 BOOL_CHAN 0x10 7 1 1 eTPU Channel Address Script Commands write chan base _addr ChanNum Addr This command writes channel ChanNum s address Addr Note that this writes the CPBA register value define PWM1_ CHAN 3 define PWM2 CHAN 4 define PWM1_CHAN ADDR 0x300 define PWM2_CHAN ADDR PWM1_CHAN ADDR PWM_RAM write_chan_base_addr PWM1_CHAN PWM1_CHAN_ ADDR write_chan_base_addr PWM2_CHAN PWM2_CHAN_ ADDR In this example channel 3 s data will start at address 0x300 Note channel variables and static local variables use this eTPU Engine Data Script Commands These engine data script commands are only available on the eTPU2 products write_engine_data32 AddrOffset Val
186. em_block Host 0 OxFFFF RAM1 ALL SPACES In this example a 64K block of simulated memory is created and the name RAMI is assigned to this memory block This memory is accessible from all of the CPU s address spaces add_non_mem_block TargetName StartAddress StopAddress enum ADDR_SPACE This command adds a blank block of simulated memory to the target TargetName It indicates that no physical memory exists in the specified memory range and specified address spaces ADDR_SPACE The name BlockName is assigned to this block and is used by other script commands when referencing this block The block name must be unique within its target but other targets can have a block with this same block name Since no memory is actually modeled by this command it effectively uses almost none of your computer s virtual memory This is important since the entire four GB address space must be represented by memory blocks regardless of whether or not the simulation target actually supports this large of an address space define DATA_SPACE CPU32_SUPV_DATA_SPACE CPU32_USER_DATA_ SPACE add_non_mem_block Host 0x1000 OxfffffffFf Empty DATA SPACE This example specifies that no physical memory exists above the first 64K for both user and supervisor data spaces Data space is defined by the define declaration as consisting of a combination of the supervisor data space and the user data space set_block_to_off TargetName BlockN
187. ent function s local variables is disabled For example if you are parsing through text a stacked function may point to the beginning of a buffer that is being traversed by called functions Use of this option would allow you to lock onto display of the calling function s local variables thereby viewing a reference to the beginning of the buffer Note that the function name and frame address are determined by the window s current display state The functionName is a symbolic name of a function e g main char argc char argv The frame address is the address such as 0x1000 Maximum Expansion Level for Structure Members Pointers etc It is common for structures to be members of other structures or to be referenced from within structures The local variable window expands these contained and referenced structures This setting specifies the number of levels to expand Maximum Number of Array Elements to Display This specifies the number of local variable array members that are displayed For example an integer array might consist of multiple members but the actual number of members is generally not available in the symbol table This setting allows you to specify how many elements to display License Options Dialog Box This dialog box allows you to enter additional information prior to sending a license file to ASH WARE Inc A license file is generated whenever you install an ASH WARE product Unfortunately the license file generat
188. er ccceeeseceeeeeseeeeeeeeeeeeneeeeeeeneees 19 10 CPU32 Stand Alone Simulator ceceeeeeeeeeeeeeeeeeeeeeeeeeeees 19 11 683xx Hardware Debugger cecccceeeeeeeeeeeeeeeeeeeeeeeeeneeeeeees 19 12 eTPU2 Simulation Engine Target cccccesseceeeeeeeeeeeeeeeeeeees 19 13 eTPU Simulation Engine Target ccccccesseeeeseeeeeeeeeeeeeeees 19 14 TPU Simulation Engine Target cccccsseeeeeeeeeeeeeeeeeeeeeeees 19 15 CPU32 Simulation Engine Target cccccssseceeeeeeeeeeeeeeeeeeees 19 16 CPU32 Hardware across a BDM Port ceceeeeeeeeeeeeeeeeeeees Part 20 Building the Target Environment 20 1 The Build Script File ccccceeeeeceeeeeeeeeeeeeeeeeeeeeeeeeeeeeneeeees 20 2 Build Script COMMAMNAS cccceeeeceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeees page 10 Multi Target Development Tool 273 Multi Target Development Tool Multi Target Development Tool page 11 page 12 Multi Target Development Tool 1 Overview 1 Overview This introductory section provides a high level overview of some of the key aspects of the simulator debugger More detail is provided in the remainder of this manual A variety of products are derived from the Multiple Target Development Tool Mtdt technology This manual covers all the current MtDt products These products include single and multiple target simulators and hardware debuggers MtDt has been developed using an object orientat
189. ervice Request LSR Match Recognition Latch and Transition Detection Latch for both action units MRLA MRLB TDLA TDLB the Function Mode Bits FM1 FMO0 the sampled and current input pin states PSS PST The upper 8 bits of the P register which are treated as conditionals by the execution unit are also displayed Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 201 15 Operational Status Windows 15 3 TPU Specific Windows The following windows are available in the TPU Simulator and TPU System Simulator 15 3 1 TPU Configuratio E TpuSim Configuration Clocks Counters CPU Frequency Prescalers TCR PSCK 1 DIU2 T2CG 6 T2CSL Verification Continuous Behav Behavior Failure Script Failures Versions Device T TPU Simulator 9 TPU Assembler 5 Files n Window 16 7786 MHz 1 6 TCR2 6 ESPCKE ESPCK TCR2PSCK2 ior Off S 66666666 66666666 PU 1 512 Instructions 9 98 Build 2 8 Le Es Project E Mtdt TargetCode HelpWindows DemoEngine MtDtProject MtDt Build E Mtdt Gui TESTFILES BuildScripts 2Sim16_1TpuSim MtDtBuild Source Code make asc Script Script Report Script Startup Test Vector Build Master Behavior ISR Files Isr 6 No File Isr 1 No File Isr 2 No File Isr 3 No File Isr 4 No File Isr 5 No File Isr 6 No File Isr 7 No File Isr 8 No File Isr 9 No File Isr A No File Isr B No File Isr C No File Isr D No File Isr
190. es can only be saved through scripting The Coverage Statistics Save Submenu This opens the Coverage Statistics dialog box This is used to store a coverage statistics report to a file Help This accesses this help screen Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 263 17 Menus 17 2 Stepping Into This runs the active target until one line of source code is executed If a function is called simulator debugger halts on the first instruction within that function If no instructions associated with source code lines occur simulator debugger continues to run until stopped by selecting the Stop submenu in the Run menu Over This single steps the target by one line of source code stepping over any function call This is the same as the above Into function except the Into function will halt on a line of source code within the function that is called If no instructions associated with source code lines occur simulator debugger continues to run until stopped by selecting the Stop submenu in the Run menu Out This runs the active target until the current function returns Execution is halted on the next line of source to be executed in the calling function If no instructions associated with source code lines associated with a calling function occur simulator debugger continues to run until stopped by selecting the Stop submenu in the Run menu Anything This causes one action to be per
191. es well under 1 of the simulator debugger s CPU time so this option is generally selected But in certain cases de selection of this option can improve performance View Toolbar This specifies whether the toolbar and its associated buttons are visible The toolbar is the gray area located at the top of the simulator debugger s application window View Status bar This specifies whether the status bar and its associated indicators are visible The status Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 243 16 Dialog Boxes bar is the gray area located at the bottom of the simulator debugger s application window Pop to Halted Target s Workshop Each target is generally assigned to a workshop Ina multiple target environment when a target halts the workshop associated with the target that caused the system to halt This should generally be left selected Auto Open Window for File of Active Target s Program Counter When Target Halts When this is selected if the target halts the source code file corresponding to the program counter of the active target is closed it will automatically be opened In addition the current line is automatically scrolled into view Display Angle Instead of Clocks if Available In the status bar there is a box that shows either the angle or time of the active target This setting specifies that angle is shown rather than time if it is available The display has the forma
192. eseeseeseeseeseesaesoesaesaeseeeenesnennenes 176 VE a Baa Tae EE 178 Local Variable WiNdOWS cs ecsseeeeseeeeeneeeseeeeeseeeeeneeeseeeeeseeeesaeeeseeeeseeeeeeeeeneeee 180 orete e e Le EEN 181 Thread WINDOW iacsesisceececccscccvetcccssccecsecedcscessnstledecccodudevsuecedvendsavevsacteddeceessacesncivnssees 182 Jrare WI COW A aA EE E TE E E E A E AE EE 187 Complex Breakpoint Wimdow s s nnsnsnnnnnusnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnenn nne 189 Memory Dump WiINdOW seeeeEeEESREESEREEREEREEREEREERREEEEEEEEREEEEEREEREEREEEEEREEEEEEEEESEESEENE 190 Timers WIN UE 191 Background Debug Mode BDM Hardware Window sssscseeseeseeeeeesenees 192 15 2 eTPU Specific Windows cccccceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeseeeeeees 193 ETPU Configuration Window zi a raene raa ma rarae e eaae Aeara aA Enan artana 193 eTPU Channel Frame Window wee 195 eTPU Global Timer and Angle Counters Window 195 eTPU Host Interface Window 197 eTPU Channel Hardware Window 198 eTPU Scheduler Window s2 ceseee 200 eTPU Execution Unit Registers Window csssscssssesesseerseesseesseeseeneeeeneneee 201 15 3 TPU Specific WiNdOWS ccceceeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeneeeeeeeeeeeees 202 TPU Configuration Window c cccseceeeeeeseeeeeeeeeeeneeenseeeeeeeeennenenseeeeseeeeneeeenseeees 202 TPU Host Interface Registers Window
193. eseesseeseesaeseesonsessensenenees 41 Script Directives Define lfdef Include scesccsesensseeseresseeseeeneeeseesseerseeeeeenenes 42 Script Enumerated Data Types cccssesssssseeseessesessesseeseeseeseesoeseesaesessevenvaneanes 43 Script Integer Data Types cc ccesssssesseseeseeesesseeseesessessessesseeseeseesaesaesaesaesaevonvaneans 43 Referencing Memory in Script Files cc ccetssessessesesseeseeeseeseeseesessessensensenenees 44 Assignments in Script Commands Files ccssssssssesesseseesnesessessessevenveneenes 44 Operators and expressions in Script Commands Files csssesseeeeeeeeeees 45 Syntax for global access of eTPU Function Variables scsseseseeseeeeneeees 46 Syntax for eTPU Channel Hardware ACCESS ssssssesesssesestesnessessesseveeveneenes 46 Multi Target Development Tool page 3 Multi Target Development Tool Syntax for eTPU ALU Register ACCESS cctcsesessseseesesnessessesseveeveneeneenenneneanans 48 String within a string supports formatted symbolic information 00 50 Comments in Script Commands Files ccssseeseeeeseeseensesseesensenseneneneesaennens 50 Decimal Hexadecimal and Floating Point Notation in Script Files 0 50 Stri g Notati EE 51 6 6 Script Commands Groupings ssssssssnnuusennnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn nnmnnn Clock Control Script CommandS s ssnsnsnnnnsnsennnnnnnnnnnnnnnnennnnnnnnn
194. et Development Tool page 247 16 Dialog Boxes 16 9 See the Building the MtDt Environment section See the Command Line Options section Message Options Dialog Box The Message Options dialog box provides the capability to disable the display of various messages These messages warn the users in a variety of situations such as a failed script verification command failure or when suspicious code is encountered When there is a check next to the described message a message is generated when the described situation occurs To disable the message remove the check The user might wish to execute through a failing or suspicious section of code without having to acknowledge each message and would therefore disable the associated message All Targets Messages Behavior Verification Failure Behavior verification failure messages are generated when the current execution does not match that from a previously recorded behavior verification file Script Verification Failure Script verification failure messages are generated when a user defined script verification test fails Bad at_time Script Command Bad at_time script commands specify when a particular script command is to be executed A message appears when this command specifies a time earlier than the current time Obsolete set_cpu_fre quency Script Command The set_cpu_frequency script command is being deprecated and users should switch to the set_period script command to ach
195. et core into the correct state for loading code when simulator debugger is launched MtDt build script files instantiate and connect targets For most users no knowledge of MtDt build script files is required because the standard build script files provided by ASH WARE provide all the required features But power users may tailor the MtDt build script files to take advantage of MtDt s advanced full system simulation capabilities Test Vector Files Test vector files provide the user with one means of exercising input and I O pins with 1994 2015 ASH WARE Inc page 14 Multi Target Development Tod Reference Manual 1 Overview complex test patterns While a script commands file functionally represents the CPU or Host MCU interface a test vector file represents the external interface And whereas a script commands file provides a broad range of functions the test vector file provides the narrow but powerful capability of driving nodes to high or low states and assigning application specific names to nodes and node groups Concurrently Developing Code for Multiple Targets Cores Code for multiple targets cores can be developed and debugged concurrently Interactions between and among multiple targets cores are modeled precisely and accurately All the normal debugging techniques such as single stepping setting breakpoints stepping into functions etc are available for each target core The IDE supports instantaneous target core swi
196. etween coworkers These commands cause a dialog box to open that contains the string lt messageString gt The truly devious practical joker will find a way to combine this script command with sound effects print Hit any key to fuse all P wells with all N substrates in your target silicon In the example above your coworker at the adjacent lab bench pauses for a certain amount of healthy introspection A well placed and timed bzilch chord can significantly enhance its effect print TEST RESULTS n A d n B d n C d A B C The print_pass print command is identical to the print script command except print_pass leaves the error level of the simulation unaffected The print script command always sets the simulation error level to 1 The print command supports using HILL as an argument that gets replaced by the name and absolute path of the file in which it is found 1994 2015 ASH WARE Inc page 62 Multi Target Development Tod Reference Manual 6 6 11 6 Script Commands Files print s TEST COMPLETE FILE outputs lt filename gt TEST COMPLETE In the case of print_sfnQ the error level of the simulation run is unaffected These script commands are available to be used via action tags as well Formatted symbolic information can be generated using as described in the String within a String section See the example shown above verify version verHi verLo ver
197. f 0 is client operation and a Mode of 1 is server operation When in client mode the ServerID determines where the time base is to be imported from The server numbers for the time bases are hardcoded in hardware as follows 0 eTPU_A TCR1 1 eTPU_B TCR1 2 eTPU_A TCR2 3 eTPU_B TCR2 A typical usage of the STAC Bus is to export the TCR2 time base angle from eTPU_A toeTPU_B This could be accomplished with the following set of script commands assumes other time base configuration already complete configure STAC Bus eTPU_A write_stac_tcr2_enable 1 eTPU_A write_stac_tcr2_assignment 1 server eTPU_B write_stac_tcr2_enable 1 eTPU_B write_stac_tcr2_assignment 0 client eTPU_B write_stac_tcr2_server 2 import eTPU_A s TCR2 enable timers write_global_time_base_enable 1 6 6 24 eTPU Global Data Write Verify Commands write_global_data32 AddrOffset Val write _global_data24 AddrOffset Val write_global_datal6 AddrOffset Val write_global_data8 AddrOffset Val verify _global_data32 AddrOffset Val verify global_data24 AddrOffset Val verify _global_datal6 AddrOffset Val verify _global_data8 AddrOffset Val These commands write global data at address AddrOffset to value Val or verify that the data at address AddrOffset matches value Val Note that 32 bit numbers must be located on a double even address boundary 0 4 8 that 24 bit numbers must be located on a single od
198. fire3 1 no_fire 1 fire3 1 Give another 175 degree delay page 122 Multi Target Development Td amp 1994 2015 ASH WARE Inc Reference Manual end 8 Test Vector Files no fire 175 The second plug fires next fire2 1 no_fire 1 fire2 1 no_fire 1 fire2 1 Give another 175 degree delay no fire 175 The fourth plug fires next fire4 1 no_fire 1 fire4 1 no_fire 1 fire4 1 Give another 175 degree delay no_fire 175 Enclose the loop and put the infinity character The following wave form is generated from the above example SPARK 4 SPARK 3 SPARK 2 M SPARK 1 SYNCH Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 123 page 124 Multi Target Development Tool 9 Functional Verification Functional Verification Functional verification supports an automated method for verifying that behavioral requirements are met by the code These capabilities can be grouped as data flow verification pin transition behavior verification and code coverage verification The following diagram shows a hardware perspective of functional verification Pin transition verification is applicable only to eTPU and TPU Simulation Data Flow Pin Transition Verification Behavior Verification a TPU eS CPU Interface Pin External Registers TPU Microcode Transitions Hardware t Code Coverage Verification Reference Manual C 1994 2015 ASH WARE D Target Devel
199. flows so that the very oldest data must be discarded and in this case the indicator shows the non zero time associated with the oldest valid data Current Time Indicator The current time indicator is the latest time associated with any target in the system Drag and drop any time into this field as explained in the Executing to a Precise Time section Auto Scroll Selecting auto scroll causes the Logic Analyzer to continuously update the view as the simulation runs De selection causes the Logic Analyzer to cease updating the view as the simulation runs Button Controls Zoomin GT Selecting the Zoom In button narrows the view to the transition data at the center of the Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 167 14 The Logic Analyzer 14 14 page 168 Multi Target Development Tho display Zoom Out bf Selecting the Zoom Out button widens the view so that more transition data is displayed Zoom Back oS Selecting the Zoom Back button restores the previous view The last five views are always saved MtDt stores the view information in a circular buffer so that if the Zoom Back button is selected five times the original view is restored Note that only the view and not the cursors are affected This allows the user to shift views while retaining the timing information associated with the vertical cursors Zoom To Cursors 4 Selecting the Zoom To Cursors button causes the view to display
200. for a delay of 666 666 5 micro seconds l for each channel with CHD RAH s DSCK bit asserted DTL 7 0 Delay from chip select negation to next operation l is equal to DTL field 64 multipied by 32 system clocks for a delay of 666 615 3 micro seconds l for each channel with CHD RAH s DT bit asserted SPCR2 6666 SPIFIE F F QSPI interrupts are disabled WREN E E Wraparound mode is disabled WRTO D D Wrap to pointer address 6 ENDQP B 7 The last QSPI channel to transfer is 6 NEQQP 3 6 The first QSPI channel to transfer is 6 SPCR3 6666 LOOPQ A A QSPI interrupts are disabled HMIE 9 9 HALTA and MODF interrupts are disabled HALT 8 8 Halt is not enabled SPIF 7 7 QSPI is not finished MODF 6 6 Another SPI node requested to become master no HALTA 5 5 QSPI is not halted CPTQP 3 0 The last channel executed is 6 QSPI RAH D 1 2 3 4 5 6 7 8 9 A B c D E F Receive 6666 81E7 7FFB 7C9F EFB3 66DB B8F2 E6FF 6747 97F3 EAAF 25AA 65FD FREI 9F7A FSB7 Transmit BBF8 7BFB 1A8E 94FF 7872 96BA FEDB DBF 15EB EXC BF6F F987 575F F77E F77B 41FD Command 7F EF 42 6D ED DC FD FF 1B FD DA 8F CB FF D2 7A CONT 7 PORT DEAS PORT PORT DEAS DEAS DEAS DEAS PORT DEAS DEAS DEAS DEAS DEAS DEAS PORT BITSE 6 BITS BITS BITS BITS BITS BITS BITS BITS 8 BITS BITS 8 BITS BITS BITS BITS DT 5 DTL DTL std DTL DTL std DTL DTL std DTL std std std DTL std DTL DSCK 4 DSCK CK 2 CK 2 CK 2 CK 2 DSCK DSCK DSCK DSCK DSCK DSCK CK 2 C
201. formed This action may be execution of a single instruction execution of a script command or simply a tick of the CPU clock This is helpful for advancing execution by as small an amount of possible allowing you to really zoom in on a problem Script This runs simulator debugger until one script command from the active target is executed If no new script commands become available simulator debugger continues to run until stopped by selecting the Stop submenu in the Run menu Thread Start Time Slot Runs until the beginning of the next eTPU TPU thread time slot transition Execution stops just prior to execution of the first opcode in the thread If no thread occurs execution continues to run until stopped by selecting the Stop submenu in the Run menu page 264 Multi Target Development T9 1994 2015 ASH WARE Inc Reference Manual 17 Menus Thread End This command is excellent for running from thread to thread in the same channel If ina thread run then stop at the end of the thread If at the end of a thread run until the beginning of a thread on the same channel Ifno thread is active run until the beginning of a thread on the last active channel Angle Tick When the eTPU is in angle mode this runs until the next angle tick occurs Angle Tooth When the eTPU is in angle mode this runs until the angle tooth occurs The angle tooth could be generated by a physical tooth a tooth induced by asserting TPR IPH
202. ge 230 Multi Target Development Tho 1994 2015 ASH WARE Inc Reference Manual 15 Operational Status Windows 15 10 2 QADC Ports Window TEE DDRQ 7166 ANS9 F F Input 6 PORTO 4166 ANSS E EI PQA 6 Output 1 ANS D D PQA 5S Output 8 ANSG ETRIG2 C C PQA 4 Output 8 ANSS ETRIG1 B B PQA 3 ANSS Input 6 ANS4 MA2 A A PQA 2 ANS4 Input 6 AN53ZMA1 9 9 PQA 2 ANS4 Input 6 ANS2 HAB 8 8 PQA 2 Output 1 AN51 7 7 PQB 7 AS51 always 8 ANSO 6 6 PQB 6 A5 always 8 ANS 5 5 PQB 5 A49 always 8 ANSS 4 4 PQB 4 A48 always 8 AN 3 ANz 3 3 PQA 3 AN3 8 AN 2 ANY 2 2 PQA 2 AN2 8 AN 1 ANx 1 1 PQA 1 AN1 8 AN 68 ANW 8 68 PQA 6 ANB 8 The QADC Ports window displays the QADC Port Data Direction Register DDRQA and the QADC Port A and B registers PORTQA PORTQB Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 231 15 Operational Status Windows 15 10 3 QADC Channel Window 32My68376 QADC Channels 10 x P PAUSE after executing current CCW l BYP Use BYPASS amplifier RESULTS l l IST Input sample time ns RHT LFT LFT l l l CHAN JST JST JST CCW X VAL 9 9 8 8 7 6 5 6 UNS SND UNS H GOFF no 16 QCLK s 622 888 2 3F gt PQA 6 ANG 62FF 3FCO BFCA 1 3FF PAUSE YES 16 QCLK s 022 888 2 3F gt PQA ZAN 6357 55C0 DCH 2 O3FF PAUSE YES 16 QCLK s 022 888 2 3F gt PQA ZAN 8913F CECR AECH 3 62D9 P
203. hased are now fully functional All other software products are still available at a demonstration level World Wide Web Software Upgrades All versions since 2 1 can be upgraded directly through the World Wide Web The Reference Manual C 1994 2015 ASH WARE Nulti Target Development Tool page 21 3 Software Upgrades following procedure is required when performing this upgrade Note that versions prior to 2 1 cannot be upgraded via the World Wide Web Upon receiving notification from ASH WARE that a new version of the simulator debugger is available download and re install After the initial software upgrade ASH WARE no longer requires a new software key Network Floating Licenses Version 4 30 and above support a floating license capability A central License Server has a pool of one or more licenses Client computers request floating licenses from the License Server The License Server issues licenses until its pool of licenses has been depleted When a client computer no longer needs a license it becomes available for the License Server to distribute to a different client When a client requests a license it normally exits if no license is available However it may choose instead to wait a certain user defined amount of time for a license to become available If a license does become available the software is able to operate If after the user specified amount of time is exceeded no license becomes available then the softwar
204. hat the value for each channel is easily found Most of these registers can be modified only by the eTPU page 200 Multi Target Development T9 1994 2015 ASH WARE Inc Reference Manual 15 Operational Status Windows 15 2 7 eTPU Execution Unit Registers Window TE ter BEBE 000000 ert 68666606 666666 p 64 C 3226C diob C22ABD Sr 4E1EC a b 04317A 3B4A62 c d 3E2301 D5676F rar 6666 link 66 chan 66 Bus 866666 666666 Result 666666 MAC FDG6F3 3E7DE9 BRANCH PLA FLAGS SET M SET SET WC SET SET MN clr clr WU clr LSR clr MWBsy clr MRLA clr MWRLB clr TDLA clr TDLB clr FM1 clr FMO clr PSS clr PST clr P6116 6168 ZC GE CO PN The Timer Counter Global Registers TCR1 TCR2 are displayed The Event Register Timers for action units A and B are displayed ERTA ERTB The standard register P DIOB SR A B C D are displayed The Return Address Register RAR link chan are displayed The execution unit s A Bus source B Bus source and result bus are shown These are the buses internal to the execution unit The Multiply Accumulate register MACH MACL are shown The Zero Carry Negative and overflow flags for both the execution unit and the MAC unit are shown Z C N V MZ MC MN M as is the Mac Busy flag MBSY Conditionals are displayed as seen by the execution unit in that these are the versions of these flags that are sampled at the beginning of the thread These include the Link S
205. he MtDt Build Script Run Submenu This opens the Run MtDt Build Script Commands File dialog box and runs the selected page 262 Multi Target Development Td 1994 2015 ASH WARE Inc Reference Manual 17 Menus MtDt build script commands file This action has a large impact on MtDt so care must be taken when selecting it The MtDt Build Script Fast Submenu This provides a fast repeat run MtDt build script commands file By selecting this submenu the last run MtDt build script file is re run This is useful when debugging a custom MtDt build script file The Auto Build Edit Submenu This opens the Auto Build Batch File Options dialog box for selection and editing of the auto build batch file The Auto Build Fast Submenu This provides a fast repeat build capability By selecting this submenu or using the lt CTRL A gt hot key the default auto build batch file is executed The Behavior Verification Open Submenu This opens the Open Behavior Verification dialog box This is used to load previously saved behavior files NOTE This option only exists prior to version 5 00 With 5 00 and newer behavior verification files can only be loaded through scripting The Behavior Verification Save Submenu This opens the Save Behavior Verification dialog box This is used to save the recorded Simulator behavior into a behavior verification file NOTE This option only exists prior to version 5 00 With 5 00 and newer behavior verification fil
206. he eTPU engine naming convention that affects the ISR auto define Freescale originally referred to the two eTPU engines as eTPU1 and eTPU2 Unfortunately this naming convention clashes with the name of the new eTPU derivative eTPU2 The original eTPU is referred to as eTPU and the new eTPU2 is referred to as eTPU2 Automatically defined defines within ISR script commands running on eTPU Engine A and Engine B are now as follows Is define ASH WARE ETPU_A ISR _ lt ChanNum gt define ASH WARE ETPU_B ISR_ lt ChanNum gt Was define ASH WARE ETPU1 ISR_ lt ChanNum gt define ASH WARE ETPU2_ISR_ lt ChanNum gt Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 39 6 Script Commands Files 6 4 The Startup Script Commands File Startup scripts provide the capability to get the target into a known state following the simulator debugger controlled reset It is particularly useful for the case in which the simulator debugger is configured to load an executable image when launched In the 683xx Hardware Debugger for instance startup scripts can be used to configure the SIM registers so that the executable image can be immediately loaded when it is launched Each target can have an associated startup script Make sure the desired target is active From the Files menu select the Scripts Startup submenu A report file is generated each time the startup script is executed
207. he number of signal edges the TPU should measure in one parameter RAM location The TPU would then keep a running count of the current number of edges measured in another parameter RAM location MtDt displays all existing RAM parameters in this window The window is arranged in rows and columns Each row displays the six or eight parameter words each word is 16 bits wide corresponding to a particular channel Across each row are the six or eight parameters belonging to that channel In the TPU1 design Freescale apparently ran out of room to provide the full eight parameters for all 16 channels In fact of the 16 channels the lower 14 contain six parameters while only the final two channels contain the full complement of eight parameters While MtDt is in TPU1 mode the un implemented parameter RAM locations are not displayed In TPU2 and TPU3 and in MtDt while in TPU2 and TPU3 mode all parameter locations are implemented While in TPU2 and TPU3 mode MtDt displays all parameter locations How do the TPU and MtDt deal with accesses to the missing locations in TPU1 mode It behooves the TPU microcoder to assume that new TPU versions will most likely have a full complement of parameter RAM For both the TPU and MtDt writes to these locations are ignored while the data returned from reads is always zero During reset it has been observed that the parameter RAM of the actual TPU remains unchanged as long as power is not lost though this behavio
208. hen A15 and A14 are zero regardless of the state of A13 All Spaces FFFFFFFF The memory here f is mirrored here This mirrored memory architecture is created by implementing a dock from the address space to itself as follows instantiate_target SIM32 MyCpu add_non_mem_block MyCpu 0x0 0x1FFF Mirror ALL_SPACES add_mem_block MyCpu 0x2000 Ox3FFF RAM ALL_SPACES add_non_mem_block MyCpu 0x4000 OxFFFFFFFF B1 ALL_SPACES Create a mirror at the lowest 8K of the next higher 8K set_block_to_dock MyCpu Mirror ALL_SPACES MyCpu 0x2000 In this example the previously described memory architecture with mirrored memory is implemented page 300 Multi Target Development Td amp 1994 2015 ASH WARE Inc Reference Manual 20 Building the Target Environment Computer Memory Considerations MtDt uses your computer s memory to model the memory devices belonging to your target There is roughly a one to one correspondence between the total amount of memory occupied by the simulated devices and the amount of your computer s memory that is required In the examples shown in the previous sections simulated memory totals a few hundred kilobytes This is a trivial amount of memory for a modern computer When many megabytes are required you are limited to the amount of virtual memory available for the MtDt application that your computer can provide If you attempt to simulate a 100 gigabyte memory
209. hes the number of parameters that follow the format string and issues an error if there is a mismatch The parameters can be constants or simple expressions variables With code compiled using tools that support more advanced debugging information simple expressions such as struct member structPtr gt member array 2 and pointer are supported The output of the Print command always goes to the Trace window and using the start_trace_stream script command it can also be directed to a file Directing it to a file can be extremely useful for verification and automated testing IMPORTANT NOTE although the print action command works via the print_to_trace script command it has a slightly different syntax The print_to_trace script command must have its input encapsulated in a single string while the print action version has its format string and any additional arguments NOT encapsulated in an enclosing string See the Global eTPU Channel variable Access section for information on accessing channel variables using the format shown below lt chan num name gt lt function var name gt The format specifier is used to denote that a parameter value is to be inserted in the resulting text The character must always be followed by a valid conversion character such as d If the character is not followed by a conversion character then a warning message is generated and any automated tests will fail The character is generated by t
210. hese scripts will execute if it is a debugger 1994 2015 ASH WARE Inc Reference Manual 6 Script Commands Files verify _spi_datal6 _AW816DA_IMM StartPins_ 0x08 verify _spi_datal6 _AW816DA_IMM StartPins45_ 0x00 else These scripts will execute if it is a simulator verify _spi_datal6 _AW816DA_IMM StartPins_ 0x00 verify _spi_datal6 _AW816DA_IMM StartPins45_ 0x01 endi E Target Specific Scripts It is often desirable to have a single script commands file run on multiple targets In this case target dependent behavior is accomplished using the target define The target define is generated using the target name as follows define _ASH WARE lt TargetName gt _ 1 TargetName is defined in the build batch file and is found in a pull down menu in the upper right hand side of the simulator debugger ifdef ASH WARE_DBG32 set_crystal_frequency 32768 endif _ASH WARE DBG32 In this example the set_crystal_frequency script command executes only if the script command is running under a target named DBG22 The build define is also injected as a macro into the script environment define lt BuildDefine gt 1 A script file shared among projects testing on different targets can then have target specific sections ifdef MPC5554_B do eTPU1 stuff elif defined MPC5674F_2 do eTPU2 stuff endif Determining the Tool Versions The compiler version and simulator version are available as the syste
211. iagram M4 displays an angle of 113 10 degrees as a TCR2 value of 0x46B see M3 above corresponds to this angle M5 and M6 show the active counters TCR1 or TCR2 which are used for the match comparison M7 and M9 show whether a match comparison has been configured for equals only or for greater than or equals gt C1 and C2 are the Capture register values for action units A and B respectively C2 and C4 are the difference between the Capture register and the active counter TCR1 or TCR2 for which the last capture into that register occurred When in angle mode C2 and C4 may display the angle at which the capture occurred In order for Angle to be displayed certain configuration must have occurred as covered in eTPU Time Base Configuration Script Commands section Note that in the above diagram M4 displays an angle of 113 10 degrees as a TCR2 value of 0x46B see M3 above corresponds to this angle C5 and C6 show which global counter will be captured on the next MRL or TDL event The states of Match Recognition Latch Enable MRLE Match Recognition Latch MRL and Transition Detection Latch TDL are displayed These are the latches in the channel hardware and may not necessarily match the value in the execution unit window since those in the execution unit window are sampled at the beginning of each thread MTD Match Transition Disable indicates whether or not matches and transitions result in a service request The
212. ialog box but this must be done manually each time the application is launched In certain cases such as tool qualification under DO178B it is desirable to disable display of the dialog box such that the test of the verification test can be automated This is done as follows disable_message PIN_TRANSITION_FAILURE disable message SCRIPT_FAILURE j THESE COMMANDS SHOULD BE USED WITH EXTREME CAUTION They remove observe ability from verification failures In all cases except automation of test of the verification tests it is preferable to disable the display of the verification messages manually from within the Messages dialog box eTPU System Configuration Commands write _entry table_base_addr Addr This command writes the Event Vector Table s address It writes a value into the ETPUECR register s ETB field that corresponds to address Addr define MY ENTRY TABLE BASE ADDR 0x800 write_entry table _base_addr MY_ENTRY_TABLE_BASE_ ADDR In the above example the event vector table is placed at address 0x800 write_engine_relative_base_addr Addr This eTPU2 ONLY command writes the Engine Relative Base Address It writes a value into the ETPUECR register s ERBA field that corresponds to address Addr define MY _ENGINE_ADDR 0xA00 write_engine_relative_base_addr MY_ENGINE_ADDR page 80 Multi Target Development Tod 1994 2015 ASH WARE Inc Reference Manual 6 Script Commands Files In the above examp
213. ialog box In addition a build is performed Cancel Button This closes the Auto Build Batch File Options dialog box Edits are not saved The default auto build file is not set to be active for future builds Instead the default auto build file reverts back to whatever the default was before the Auto Build Batch File Options dialog box was opened page 240 Multi Target Development Td 1994 2015 ASH WARE Inc Reference Manual 16 Dialog Boxes Build Button This saves edits and performs an auto build The Auto Build Batch File Options dialog box is not closed Help Button This accesses this help menu Change File Button This allows the user to select a new auto build batch file Beside this button is listed the name of the currently selected auto build file 16 3 Goto Time Dialog Box The Goto Time Dialog Box is opened via the Run menu by selecting the Goto Time submenu It provides the capability to execute the simulator debugger until a user specified time There are two types of Goto time options one of which must be selected Goto Until Time This sets the simulator debugger to execute until an absolute simulation time is reached The simulation time is initially set to zero The simulation time is reset to zero via the Run menu by selecting the Reset submenu Goto Current Time Plus This sets the simulator debugger to go to the current simulation time plus some user specified additional time User specified ti
214. ications the standard memory models work just fine so a detailed understanding of memory modeling is not required In the vast majority of other cases only a small percentage of these capabilities are required Memory Block Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 287 20 Building the Target Environment Whereas a simulated memory map can support a large variety of characteristics that might change from one memory range and address space to the next a memory block is a range of memory that has a single uniform set of characteristics A target s address space comprises a finite number of memory blocks For instance a 3 wait state RAM could reside at address 0 to FFFF hexadecimal A 0 wait state ROM could reside at address 1000 to IFFFF The rest of memory from 1000 to FFFFFFFF hexadecimal could be empty There are a number of rules associated with memory blocks A build of MtDt simulated memory will succeed only if both of the following rules are met Memory blocks must cover all memory Memory blocks may not occupy both the same address and address space A report file for each build attempt provides a detailed listing of the memory map including the information required to fix any problems The following is an example script commands sequence define MEM DEVICE STOP Oxffff define BLANK START MEM DEVICE STOP 1 define MEM END Oxffffffff instantiate_target SIM32 MySim32 add_mem_bloc
215. ice Request Register HSRR shows the state of the service request The Function Mode FM shows the state of these two bits the Entry shows if the event vector entry table for that channel is being treated as the standard or alternate event vector table The Channel Interrupt Status Register CISR shows if this interrupt has been issued by the eTPU the CIER indicates if the interrupt is enabled and the CIOR indicates if an attempt to set the interrupt when it was already set occurred and therefore there was an overflow The Channel Data Transfer Request Status Register CDTRSR shows if this interrupt has been issued by the eTPU the CDTRER indicates if the interrupt is enabled and the CDTROSR indicates if an attempt to set the interrupt when it was already set occurred and therefore there was an overflow Note that in response to these enabled and asserted interrupts special ISR script command files can execute as described in the Script ISR section Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 197 15 Operational Status Windows 15 2 5 eTPU Channel Hardware Window There are two versions of the eTPU Channel window The active channel version displays information on the active channel or previously active channel if none is currently active while the fixed channel version displays information on a particular channel Right click the mouse when inside this window to specify or change the window flavor
216. ich is found in the build directory This file supports selection of the eTPU version and associated errata and memory sizes via a define The define is selected in the the Build Script Options Dialog Box instantiate_target_ex1 SIM32 MC33816 Host instantiate_target_ex1l ETPU_SIM MPC5554 B 1 eTPU_A This example instantiates two simulation models a CPU32 simulation model and an eTPU simulation model The name Host is assigned to the CPU32 and the name eTPU_A is assigned to the eTPU Subsequent build script commands use these names when referring to these targets These names are also referenced in a variety of other places such as in workshops and the menu system add_mem_block TargetName StartAddress StopAddress BlockName enum ADDR_SPACE page 302 Multi Target Development Td amp 1994 2015 ASH WARE Inc Reference Manual 20 Building the Target Environment This command adds a memory block to a range of simulated memory The memory appears between stopAddress and startAddress in the memory space ADDR_SPACE The name BlockName is assigned to this block and is used by other script commands when referencing this block The block name must be unique within its target but other targets can have a block with this same block name The size of the memory block is equal to one plus stopAddress minus startAddress Only a single copy of this memory is created regardless of how many address spaces the block occupies add_m
217. ich this is particularly useful define TEST_DIR TestDataFiles read_behavior_ file TEST_DIR Test bv vector TEST DIR Example C Style Escape Sequences In the C language special characters are specified within a string using the backslash character For instance a new line character is specified with the backslash character followed by the letter n or n The character following the backslash character is treated as a special character The following special characters are supported References a backslash character File dat Planned Obsolescence of Single Backslash within Strings In previous versions of this software a C style escape sequence was not supported and a single backslash character was treated as a just that a single backslash character In anticipation of future software versions supporting enhanced C style escape sequences the single backslash character within a string now causes a warning ASH WARE recommends using a double backslash to ensure compatibility with future versions of this software The following string causes a warning File dat Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 51 6 Script Commands Files 6 6 Script Commands Groupings Listed below are the available script command functional groups All Target Types Script Commands Clock control script commands Timing script commands Verify traversal time commands Modify me
218. ides the capability of specifying for individual windows which workshop s the window will be visible OK This closes the dialog box and saves any changes Cancel This closes the dialog box and discards all changes Help This accesses this help window Occupy All This causes the window to be visible in all workshops Leave All This causes the window to not be visible in any workshop This should be treated as a shortcut for clearing all selections Note that this is not the same as closing the window as the window will still exist within thesimulator debugger Revert This causes any settings made since the dialog box was opened to be discarded Options This opens the Workshop Options dialog box MtDt Build Options Dialog Box This MtDt Build Options Dialog Box is opened from the Options Menu It is used to specify options for the MtDt Build Script The MtDt Build Script is run by the ASH WARE simulator or debugger when the simulator debugger is initially launched to build the simulation or debugging environment as described in the System Simulation section An example usage of this would be to select an MCF5232 revision 0 eTPU 6Kshould page 246 Multi Target Development Td amp 1994 2015 ASH WARE Inc Reference Manual 16 Dialog Boxes 1 5K RAM instead of the default MPC5554 revision B 16K code 3K RAM This is shown below See file zzz_eTpuVersions Dat in the BuildScripts directory for definitions of all suppo
219. ied operation on the expressions is 0 or false a verification error is generated at_code_tag amp amp TestlHere amp amp verify val FailFlag 0 In the example above the target is run until it gets to the address associated with the source code that contains the text amp amp TestlHere amp amp Once this address is reached the value of symbol FailFlag is read and a verification error is generated if it does not equal zero Two other forms of the verify symbol value script command are also supported that directly take the numerical value to compare against as an argument verify_val_int exprString testOpString U32 val verify val_fp exprString testOpString double val These forms allow the test value to be input as a constant expression perhaps using a 1994 2015 ASH WARE Inc Reference Manual 6 6 10 6 Script Commands Files series of macros thereby providing more flexibility Separate script commands are available to compare and verify string values verify _str exprl testOp expr2 verify str_ex exprl1 testOp expr2 len The exprl and expr2 parameters can either be a string constant or can be of type char array or char pointer If strings are resolved from both parameters then they are compared using the comparator specified in testOp If the outcome of this is true non zero the verification test passes otherwise a failure is repo
220. ieve this functionality The problem with the set_cpu_frequency command is that the simulation engine now calculates all times in periods rather than frequency This command requires an inversion which can generate extremely small error and this error over many billions of simulation cycles can become significant Consider the case of two targets where one target is running half the frequency of the other If one clock is 333 MHz and the other is 666 MHz after the inversion the resulting clock periods may not be exactly double anymore page 248 Multi Target Development Td 1994 2015 ASH WARE Inc Reference Manual 16 Dialog Boxes TPU Messages An Instruction Accessed Unimplemented Parameter RAM The message that reports an access of un implemented parameter RAM locations may be disabled Some users have taken advantage of the un documented feature that accesses to these un implemented parameter RAM locations return zero Taking advantage of this un documented feature is dangerous because Freescale might choose to implement these locations such as in the TPU2 or might change the values returned when these locations are accessed In any case these warning messages can be disabled WMER Instruction at N 1 after CHAN_REG Change The TPU behavior in this situation is undefined so the simulator debugger generates a message READ_MER Instruction at N 2 after CHAN_REG Change The TPU behavior in this situation is undefined so MtDt generates a
221. ify file_coverage MyFunc c 100 100 100 Code Coverage Annotated Listing Files It can be useful to generate reports files that provide coverage information at the source and opcode level The write_coverage_listing_fileQ has been provided to generate such reports write_coverage_listing_file ModuleName c ListingFileName enum COVERAGE_LISTING_OPTIONS For a specified module source file name a code coverage annotated listing file with the name specified by the ListingFileName argument is created Any previous file of the Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 71 6 Script Commands Files 6 6 14 page 72 Multi Target Development Tod same name is overwritten The output form is very much like a regular listing file as generated by the ETEC compiler with the additions of source file line number preprended to each line opcode disassembly lines include a coverage field that indicates to what level the opcode has been executed by tests none full execution true branch false branch inferred coverage The COVERAGE_LISTING_OPTIONS argument supports two mode options ALL_LINES Output all lines of the specified module source file with listing information NON_COVERED_ONLY_LINES Output only line associated with opcodes not fully executed Independent flags that modify the modes listed above may be added to the COVERAGE_LISTING_OPTIONS argument Currently one modifier flag
222. igh Low Low Low Low High Low Low Low Low Low Set to force chan A compare always reads 6 Set to force chan B compare always reads 6 ei eeeeee ee eeh EE ch ES E hb E DI en rn rn Edge Polarity Mode selecte string Bits of resolution l RCA FORCB EDPLO MODE Geh bi EOF OPWH DCH IC DCH unused DPWM OCAB IPH IPWH DIS unused The CTM6 Double Action Bits Submodule window displays the DASM 4 5 6 7 8 9 10 26 27 28 and 29 Status Interrupt Control Registers DASM4SIC DASMSSIC etc and the DASM Data A and B registers DASM4A DASM4B DASMSA etc See the Modes form of the CTM6 Double Action Submodule window for display of additional information 15 10 QADC Module Window The following windows display the Queued Analog to Digital Converter QADC module settings Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 229 15 Operational Status Windows 15 10 1 QADC Main Window 32My68376 QADC Main E ll x QADCHCR 4684 STOP F F The QADC clock is enabled FR2 E E QADC finishes any current conversion then freezes SUPU 7 7 All tables and registers are supervisor only IARB 3 6 QADC interrupt arbitration priority M QADCINT 313C IRLQ1 E C Queue 1 interrupt is level 3 disabled 7 highest IRLQ2 A 8 Queue 2 interrupt is level 1 disabled 7 highest IVB 7 6 Interrupt vector base is 3C l l 2 1sb s cannot be written and always read 8
223. ile Test Vector Generation Functional Model J TPU Master Wave Test Form Channel 7 Vector Generator Clock Wave Form Channel 2 Generator Wave Form T Clock Generator The test vector generation model consists of a single master test vector clock and a number of wave form generators The same master test vector clock clocks all wave form generators The wave form generators cannot produce waveforms whose frequencies exceed that of the master test vector clock A wave form might consist of a loop in which a node is driven high for 10 master test vector clock periods then low for 15 The loop could be set up to run forever Test vector files provide the following functionality The master test vector clock frequency is specified The wave form generators are created and defined Wave form outputs drive device input pins nodes Descriptive names are assigned to TPU nodes Oe TPU channel 7 s pin is page 116 Multi Target Development T9 1994 2015 ASH WARE Inc Reference Manual 8 1 8 Test Vector Files named UART_RCV Multiple nodes are grouped i e group COMM consists of UART_RCV1 and UART_RCV 2 Complex Boolean states are defined Before being parsed test vector files are run through a C Preprocessor Thus the files can use the include mechanism as well as macros and other preprocessor directives and capabilities Command Reference The following test vector commands are available No
224. ile executes See the Script Commands Files chapter for a description of the use of ISR 1994 2015 ASH WARE Inc Reference Manual 6 Script Commands Files script commands files load_chan_isr filename eTpuCommand ChanNum eTPU Only load_data_isr filename eTpuCommand ChanNum eTPU Only load_exception_isr filename eTpuCommand eTPU Only load_isr filename TpuCommand ChanNum TPU Only In order for the ISR script to actually execute the ISR must be enabled The following script commands enable and disable ISRs for both the eTPU and TPU enable chan _intr chanNum eTPU Only disable chan _intr chanNum eTPU Only enable data_intr chanNum eTPU Only disable _data_intr chanNum eTPU Only write_chan_cier chanNum isEnable TPU Only This commands loads ISR script commands file filename TpuCommand or filename eTpuCommand and associates them with the various types of interrupts from channel ChanNum close_chan_isr ChanNum eTPU only close_data_isr ChanNum eTPU only close_exception_isr eTPU only close_isr ChanNum TPU only These commands close the ISR script command that is associated with the channel ChanNum load_isr ISR_5 TpuCommand 5 write_chan_cier 5 1 Enable the TPU interrupt wait_time 2000 close_isr 5 write _chan_cier 5 0 Disable the TPU interrupt This eTPU example loads the file ISR_5 TpuCommand and associates it with the
225. imulator debugger as a whole it is important to point out how files are located within the context of Regression Testing A project file relative approach is used for searching and finding almost all files This means that the user should generally locate the project files near the source code and script files within the directory structure Consider the following directory structure C BaseDir SubDirA Test Sim32Project C BaseDir SubDirB Test Cpu32Command To load the script command file Test Cpu32Command the following option could be used s SubDirB Test Cpu32Command By employing this project file relative approach the testing environment can be moved around without having to modify the tests and therefore the files names can be smaller and easier to use Note that this does NOT apply to the log file The log file is written to the current working directory which is to say in the directory from which the tests are launched This exception to the normal directory locations is used so that multiple project files can exist in different sub directories and the test results can all be logged to the same log file Test Termination Termination of simulator debugger and the passing of the test results to the command line batch file is a key element of Regression Testing At the conclusion of a script file simulator debugger can be shut down using the exit script command as described in the System Commands section This command causes
226. in place_buffer 5 16 This example instantiates a buffer follower with TPU channel 5 as the input and the TCR2 pin as the output Each of the place_xyz script command has an extended version that supports cross target core gates as shown below place_buffer_ex InTarget InPin OutTarget OutPin Instantiates a buffer follower place_inverter_ex InTarget InPin OutTarget OutPin Instantiates an inverter place_and_gate_ex In1Target In1Pin In2Target In2Pin OutTarget OutPin Instantiates an AND gate place_or_gate_ex In1Target In1Pin In2Target In2Pin OutTarget OutPin Instantiates an ORT gate place_xor_gate_ex In1Target In Pm In2Target In2Pin OutTarget OutPin Instantiates an XOR gate place_nand_gate_ex In1Target In1Pin In2Target In2Pin OutTarget OutPin Instantiates a NAND gate place_nor_gate_ex In1Target In Pm In2Target In2Pin OutTarget OutPin Instantiates a NOR gate place_nxor_gate_ex In1Target In1Pin In2Target In2Pin OutTarget OutPin Instantiates an INVERTING XOR gate The InTarget InlTarget In2Target and OutTarget are the names of the target and are expressed as strings such as eTPU_A or Ch1_Core0 place_or_gate_ex eTPU_A 32 16 Ch1l_Core0O 10 eTPU_A 11 Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 99 6 Script Commands Files 6 7 page 100 Multi Target Development Tho In the above example an ORT gate is
227. indicators on the left side of the source code window are graphical indications of code coverage as explained in the Code Coverage Analyses section Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 175 15 Operational Status Windows 15 1 2 Script Commands Window eTpu1 Script ScriptTest ET puCommand Re loj xj The clock period terms are fento seconds 1e 15 seconds A Simple conversion is to divide a billion 1e9 by the desired MHZ E G for 100 MHZ Z4 1e9 108 10000000 Fento seconds set_clk_period 10000000 Place gates on the various pins place_buffer 32 0 32 2 place_inverter 32 0 32 3 place_and_gate 32 0 32 1 324 lace_or_gate 32 8 3241 32 5 place_nand_ gate 32 0 32 1 32 7 place_nor_gate 32 0 321 32 8 place_nxor_gate 32 0 321 32 9 Set to function 15 Execute an HSR thread that writes the channels 6 amp 1 output pins write _chan_func CHAN_NUM ScriptTest_FUNC_ write chan _base_addr CHAN NUM 0x200 write chan_data32 CHAN_NUM 6 ScriptTest_g_ myThreadStateTable WriteChan_ and_1_Pins_ write chan data32 CHAN NUM 4 060x0000 Set pins to 6 6 wait_time 168 verify chan_output_pin 6 6 Output 1 verify chan_output_pin 1 0 Output 2 verify chan_output_pin 2 0 Buffer verify_chan_output_pin 3 1 Inverter verify chan output pinih 6 AND gate verify chan_output_pin S 6
228. interrupt from channel 5 Any asserted and enabled interrupt on channel 5 during that 2ms window will cause the script commands in the file to be run load_data_isr ISR_22 eTpuCommand 22 enable data_intr 22 wait_time 5000 close _data_isr 22 disable _data_intr 22 This eTPU DATA isr example loads the file ISR_22 eTpuCommand and associates it with the data interrupt from channel 22 If the interrupt for channel 22 is both asserted and enabled within the first 5ms then the script commands in the file will run load_exception_isr GlobalExc eTpuCommand eTPU Only Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 97 6 Script Commands Files 6 6 40 page 98 Multi Target Development Tod This eTPU example loads the file GlobalExc eTpuCommand and associates it with the global interrupt External Logic Commands Boolean logic that is external to the eTPU is instantiated through the use of place_xyzQ script commands Several types of external logic are available The script command used to instantiate each type of logic is listed below See the External Logic Simulation chapter for a detailed description of the use of external Boolean logic gates place_buffer InPin OutPin Instantiates a buffer follower place_inverter InPin OutPin Instantiates an inverter place_and_gate In1Pin In2Pin OutPin Instantiates an AND gate place_or_gate In1Pin In2Pin OutPin Instantiates
229. ion command verifies the last full traversal The following is an example of a region of code marked for timing See the Timer Action Commands section for more information on naming timing regions Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 55 6 Script Commands Files int MyFunc int x int y ASHQ timer_ start Test A y x 25 return y ASH timer_stop Test A In the following example the last full traversal of the above code is verified to have taken between 10 and 20 system clocks A verification error occurs if the code has never been fully traversed if the last traversal took 9 or fewer system clocks or if the last traversal took 21 or more system clocks verify timer_clks Test A 10 20 Note that on the eTPU there are two system clocks per instruction cycle so the following define can improve the test s readability define CYCLES 2 A cycle is two clocks on the eTPU verify timer_clks Test A 5 CYCLES 10 CYCLES Related Information Naming timing regions in source code Verifying traversal times a script command file View named timing regions timing using the Watch Window List named timing regions in the Insert Watch Dialog Box 6 6 4 Memory Modify Script Commands Memory is modified within script commands using the assignment operator See the Assignments in Script Commands Files section for a description 6 6 5 Memory Verify Script Commands
230. ion for each channel This is very useful for optimizing system performance But in some applications the initialization code which generally does not contribute to worst case latency experiences the worst case thread length In this case it is best to ignore the initialization threads when considering the worst case thread length for a function This command provides for ignoring the initialization threads Initialize the channels write_chan_hsrr RCV_15_A ETPU_ARINC_RX_INIT write_chan_hsrr RCV_15_B ETPU_ARINC_RX_INIT Wait for initialization to complete then reset the worst case thread indices wait_time 100 clear _worst_case_ threads Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 79 6 Script Commands Files 6 6 20 6 6 21 In this example the channels are issued a host service request then after 100 microseconds presumably sufficient time to initialize the threads indices are reset Disable Messages Script Commands Note that this command has been DEPRECATED Please use the Quiet and the ILF5 command line options to suppress generation of these messages in an automated regression testing environment Pin transition verification failures and script command verification failures result in a non zero return code when the simulator debugger exits as well as display of a dialog box to inform the user of the failure This dialog box can be disabled in the Messages d
231. ion string exprString can be a numerical constant or a simple symbolic expression Constants can be supplied as decimal signed integers unsigned hexadecimal numbers prepended with Ox floating point numbers or as a character e g ALA 1994 2015 ASH WARE Inc Reference Manual 6 Script Commands Files symbolic expression can be just a local global symbol or a simple expression such as V de reference amp V address of V V constant V member or V gt member where V is a symbol of the appropriate type The special channel variable eTPU only reference syntax is also supported symbolExprString must be a symbolic expression as described above an value in compiler parlance The type of the symbolic expression must be a basic type char int float etc If the types of the two sides differ then C type conversion tules are followed before writing the data to memory Two other forms of the write symbol value script command are also supported that directly take the numerical value to write as an argument write_val_int symbolExprString U32 val write_val_fp symbolExprString double val These forms allow the value to be input as a constant expression perhaps using a series of macros thereby providing more flexibility The write_str command is provided as a shorthand way to write a string into the memory pointed to by a symbolic expression of pointer type write_str pointerExprString st
232. ior_file command The simulation should run and at the end at the same time as when the ebv file was saved and closed the verification should be stopped with the stop_ebehavior_file script command stop_ebehavior_file stop EBV verification Tolerances can be adjusted and the pins being verified can be specified using the enhanced behavior verification pin tolerance script commands With the set_ebehavior_global_tolerance script command all pins under test can have their allowed error tolerance set run_ebehavior_file Engine_gold EBV verify all pins in the ebv file to a 2us tolerance set_ebehavior_global_tolerance EBV_ABSOLUTE 0 0 2 0 Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 131 9 Functional Verification The set_ebehavior_pin_tolerance script command serves a dual purpose Once one of these commands is specified only pins specified with set_ebehavior_pin_tolerance script commands will be verified run_ebehavior_file PWM_gold EBV test only PWM_A and PWM_C pins w appropriate tolerance set_ebehavior_pin_tolerance PWM_A EBV_ABSOLUTE 0 0 11y set_ebehavior_pin_tolerance PWM_C EBV_ABSOLUTE 0 0 1 17 Although the tolerances can be adjusted at any time during simulation if using set_ebehavior_pin_tolerance to configure a subset of pins to test these commands should directly follow the run_ebehavior_file command Tolerances can then be adjusted late
233. ipt command at the end of a simulation run Time tolerances for pin transitions default to 2 system clocks but can be adjusted using the new enhanced behavior verification set_ebehavior_pin_tolerance and set_ebehavior_global_tolerance script commands A count of failures is displayed in the Configuration window This count is incremented whenever a behavior verification failure occurs By default each failure will generate an error dialog but this can be disabled by de selecting Options gt Messages gt Behavior verification failure A consideration regarding these behavioral models is the buffer size The maximum behavioral buffer size is currently set at 100 000 records though this may increase in future releases If the number of recorded pin transitions equals or exceeds this buffer size then the buffer rolls over and verification against this buffer is not possible A second consideration is TCR2 pin recording Normally TCR2 pin transitions are not written in these buffers This is because the recording of TCR2 pin transitions very quickly fills up the buffer and causes the buffer to quickly roll over When the buffer rolls over verification is not possible with legacy bv files Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 129 9 Functional Verification Enhanced Pin Transition Behavior Verification The new enhanced pin transition behavior verification makes use of a user friendly data file fo
234. is lists a variety of settings available for a Memory Dump Window Note that this type of window must be selected for these options to be available Toggle Mixed Assembly This toggles the visibility of assembly within Source Code File windows Note that this type of window must be selected for these options to be available Verify Recorded Behavior This verifies the recorded behavior against the currently active master behavior verification file See the Pin Transition Behavior Verification section for a description of this capability NOTE This option only exists prior to version 5 00 With 5 00 and newer behavior verification can only be controlled via scripting Enable Continuous Verification This enables continuous verification of behavior against the currently active master behavior verification file This provides immediate feedback if the microcode behavior has changed See the Pin Transition Behavior Verification section for a description of this capability NOTE This option only exists prior to version 5 00 With 5 00 and newer behavior verification can only be controlled via scripting page 270 Multi Target Development Td 1994 2015 ASH WARE Inc Reference Manual 17 Menus Disables Continuous Verification This disables continuous verification of behavior against the currently active master behavior verification file This prevents a large number of verification errors from being displayed if microcode behavior has changed
235. is_cisr Assume in this example that an ISR script commands file that is associated with TPU channel 3 executes this command This file gets executed upon assertion of channel 3 s interrupt When this command is executed channel 3 s interrupt request bit is cleared verify cisr ChanNum Val This command verifies that the CISR bit from channel ChanNum is equal to Val This command accepts a pair of arguments Argument Val must be between zero and one inclusive If the verification fails then a verification failure message is printed to the screen This verification failure message can be disabled from the Message Options dialog box The count of verification failures is available in the Configuration Window verify cisr 5 1 In this example channel 5 s CISR bit is verified to be a 1 If the bit is indeed a 1 then the simulation continues If the bit is instead a 0 a verification failure message is printed to the screen The accumulated count of verification failures is available in the Configuration Window 1994 2015 ASH WARE Inc Reference Manual 6 Script Commands Files 6 6 35 TPU Host Sequence Request Register Commands write_chan_hsqr ChanNum Val This command writes channel ChanNum s HSQR bits to value Val The HSQR bits of all other registers remain unchanged write_chan_hsqr 8 0x2 In this example two is written to channel 8 s HSQR bits 6 6 36 TPU Clock Control Script Commands These commands contr
236. it read result on unused memory Added a new auto define that helps conditional parsing of script command files Run the simulator until a channel s thread boundary C 1994 2015 ASH WARE Won Target Development Tool page 25 3 Software Upgrades Version 3 41 Enhancements Display current angle on status bar Execute to a user specified angle Extended eTPU code coverage to include event vectors Inferred event vector coverage Accumulate coverage over multiple tests View channel nodes Write and verify chan_data16 commands View critical thread execution indices Clear Worst Case Thread Indices Commands Resizing the Pin Transition Buffer Testing Cumulative Logged Regression Testing Version 3 40 and 3 30 Enhancements Added a new Complex Breakpoint Window eTPU Stand Alone Simulator Product Multiple target scripting Added ability to view thread group activity in the logic analyzer window Improved Regression Testingsection Added the include directive to script commands files Added ifdef ifndef else endif preprocessing to script command files Added automatic defines to script command files Version 3 20 Enhancements Testing automation via command line capabilities Verification and modification of symbolic data Superior Logic Analyzer Window including precise event timing measurement Improved simulation speed by between 2x and 2 6x depending on loading conditions Superior tracing including pin transitions parameter
237. ities normally associated with single target systems has been extended to this multiple target environment Each target loads and runs its own executable code image Each target can have primary and startup script commands files TPU targets can also have ISR files that are associated with and activated by specific interrupts and test vector file that can be used to wiggle the TPU s I O pins Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 285 20 Building the Target Environment The relative timing of targets is maintained with one femto second precision Each target has its own atomic execution step size that must be a multiple of the femto second precision Negative numbers and zero are valid steps sizes Since the currently supported targets are all execution cycle simulators the step size is equal to the amount of simulated time it takes to execute a single opcode As each target executes it is advanced by the amount of time the last opcode took to execute It is then scheduled to execute again when the simulation time is equal to the target s next scheduled time The current simulation time is defined as the time that the next scheduled target will execute Although all the currently supported targets are execution cycle simulation engines this is not a fundamental restriction of MtDt In fact MtDt can support targets that have much finer execution granularities This would allow for instance a VHDL targe
238. k MySim32 0 MEM _DEVICE_STOP RAM ALL SPACES add_non_mem_block MySim32 BLANK_START MEM END OFF ALL_SPACES In this example a single CPU32 CPU is instantiated A 64K simulated memory device is added between addresses 0 and FFFF hexadecimal and is assigned the name RAM The device resides in all address spaces A second memory block also residing in all address spaces fills the rest of memory between 1000 hexadecimal and FFFFFFFF hexadecimal and is assigned the name OFF This block is blank and as such takes up no physical memory on your computer Address Spaces All MtDt simulated memory supports eight address spaces The function of each address space depends entirely on the particular target and how it is specified in the build script file For instance a simulated TPU target makes use of three address spaces Code Data and Pins By treating its I O pins as shared memory the simulated TPU exposes its pins to other targets This allows for instance a simulated engine model to read and modify the TPU s pins page 288 Multi Target Development Td 1994 2015 ASH WARE Inc Reference Manual 20 Building the Target Environment With the nearly universal acceptance of the superiority of a single unified large address space why does MtDt still support non unified memory space architecture The answer is twofold First the MtDt supports older but still popular architectures such as CPU32 in which a split code data and
239. k and the other target must be the dock to The dock to target is relatively unaffected by being the recipient of a dock other than that its physical memory Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 293 20 Building the Target Environment might be modified on occasion On the other hand there are numerous effects to the dock from target First and foremost it must be able to support extrinsic or externally mapped memory In other words it must be able to project its memory access outside of itself and to a different target Note that this command must match exactly the memory bounds of an existing memory block for the docking device but not for the dock to target In fact the dock to target could be any target such as a MC68332 across a BDM port In fact the dock to target could be itself and this is the recommended way of modeling multiple image memory Although memory accesses are fully re entrant legal and often necessary it is possible to create an infinitely cyclic access that would without guards cause a stack overflow on your computer To guard against this MtDt has limited memory accesses re entrance to a depth of 100 The following build script command is presented in a later example iP wis set_block_to_dock HostCpu TpuDataDock ALL_SPACES Tpu O 0x80000 IT e In the above command a previously added blank block is docked to memory contained in a target na
240. l 15 Operational Status Windows 15 2 2 eTPU Channel Frame Window JeTpu1 Channel Frame CrankTooth_ o 0 ETPU function UNKNOWN pel channel context 8x a thisToothTinme 338000 0x52850 toothPeriod 19800 0x4d58 tickRateTimes8x208 5064 68x13c8 nissingToothTine 371150 OxSa9ce toothCount 7 0x7 lt The Channel Frame window shows the channel function and static local variables belonging to a particular channel Right click the mouse in the window to change the channel 15 2 3 eTPU Global Timer and Angle Counters Window eTpu1 Global Time and Angle Counters Module Configuration Register MCR HCR GTBE 6 6 Time bases in both engines are ENABLED wore nnn n Time Base Configuration TBCR TBCR 42618666 TCR2CTL 31 29 TCR2 Clock source is falling external TCRCLK Signal Physical tooth detection on falling TCRCLK pin edge TCRF 28 27 on 25 25 ETPU ANGLE mode EAC is ENABLED TCR2P 21 16 TCR2 prescaler divides by 2 TCR2P 61 TCRICTL 15 14 TCR1 prescaler clock source is system clock 2 TCR1P 7 6 TCR1 prescaler divides by 1 TCR1P 66 l TCR1 Period 2 660 6 nS Tonnsdneranass Tooth Program Register TPR TPR 6617 LAST 15 15 Not the last tooth MISSCNT 14 13 6 missing teeth IPH 12 12 No operation HOLD 11 11 Normal operation TICKS 9 6 617 1 24 dec angle ticks in each tooth tick Tick Ra
241. l as the number of pin transition behavior and script command failures are displayed Versions The eTPU simulator version displays the major and minor release letters along with the build letter The model displays the microcontroller version and engine some microcontrollers contain dual execution units designated A and B and the size of the code and data memories The code line contains compiler specific information such as compiler name file format such as COD or ELF DWARE 2 0 as well as the intended eTPU target the original eTPU 1 has fewer capabilities than the eTPU 2 Certain eTPU minor revisions added support for entry table pin direction control ETPD and the opcode that is returned when an opcode is fetched from an invalid address SCMOFFDATAR Files The simulator executable with full path project file and MtDt build file eTPU source code file are displayed The name of the primary script file is and the corresponding parse report file are displayed The startup script file is a special file that runs to completion immediately following reset It is generally not used The test vector file and build batch file and any master behavior verification file names gold file are displayed Semaphores The state locked or free of each of the four semaphores along with an indicator of which eTPU is locking the semaphore is displayed 1994 2015 ASH WARE Inc page 194 Multi Target Development Tho Reference Manua
242. l page 289 20 Building the Target Environment In order for accesses to these spaces to behave properly simulated memory devices must be placed into these address spaces The following build script commands create the required memory for a stand alone TPU Simulation engine Create a target TPU instantiate_target PPU SIN TpuSim Create a simulated memory block for the TPU s code microcode add_mem_block TpuSim 0 Ox1fff Code TPU_CODE_SPACE add_non_mem_block TpuSim 0x2000 OxFFFFFFFF UnusedCode TPU_CODE_SPACE Create a simulated memory block for the TPU s data host interface add_mem_block TpuSim 0 Oxlff Data TPU_DATA SPACE add_non_mem_block TpuSim 0x200 OxFFFFFFFF UnusedData PPU DATA SPACE Create a simulated memory block for the TPU s pins channel pins and TCR2 counter pin add_mem_block TpuSim 0x0 0x3 Pins TPU_PINS_ SPACE add_non_mem_block TpuSim 0x4 OxFFFFFFFF UnusedPins TPU_PINS_SPACE Be sure to provide a non_mem block for the unused address spaces add_non_mem_block TpuSim 0x0 Oxffffffff B4 TPU_UNUSED_SPACE In this example the TPU s code data and pins address spaces are filled with the memory devices required for proper operation Unused space above and below the simulated devices is filled in with blank blocks This is required as all space must be filled in even unused space must be provided with memory bl
243. lag is equal to zero It is important to note that the variable could be local to the function that contains the tag string such that it may be only briefly in scope The only scoping requirement is that the variable is valid right when the target is paused to examine this variable The extended version of the command at_code_tag_ex also supports a timeout in microseconds such that if the tagged source code is not traversed in the amount time specified by Timeout then the action specified by TimeoutAction will occur Supported actions are FAIL_ON_TIMEOUT FAIL_ON_TAG and ALWAYS PASS FAIL_ON_TIMEOUT causes a verification failure and subsequent test suite failure if the tagged code is not traversed in the specified time FAIL_ON_TAG is just the opposite and is used when the tagged code is NOT expected to be traversed ALWAYS_PASS allows the script command execution to proceed on the first of either the tagged code being traversed or on the timeout and no verification error is generated in either case at_code_tag_ex S S MyTest2 4 5 FAIL_ON_TIMEOUT 1994 2015 ASH WARE Inc Reference Manual 6 6 3 6 Script Commands Files In example above the target executes until the point in the source code is traversed that contains the text MyTest2 If in 4 5 microseconds the tagged code has NOT yet been traversed than a verification failure results Script command execution continues on the first of the tagged text being traversed the
244. le the engine relative space is placed allocated at address OxA00 write_scheduler_priority_passing_disable Val This eTPU2 ONLY command writes the Scheduler Priority Passing Disable bit It writes the specified 0 or 1 value into the SPPDIS bit of the ETPUECR register The default value is 0 write_scheduler_priority_ passing_disable 1 In the above example priority passing in the scheduler is disabled write_global_time_base_enable Enable The command enables the time bases for all the eTPUs write_entry table _base_addr Addr In the Byte Craft eTPU C Compiler the event vector table base address can be automatically generated using the following macro pragma write h define MY_ENTRY_TABLE_BASE_ADDR ETPUentrybase 0 In the Byte Craft eTPU C Compiler the event vector table base address is specified as follows pragma entryaddr 0x800 This command writes the SCMOFFDATAR register This register is the opcode that gets executed when the eTPU executes from an SCM address that is not populated with actual memory write_scm_off_data Val 6 6 22 eTPU Timing Configuration Commands write_angle_mode Val write_tcrl_control Val write _tcr2_ control Val write_tcrl_source Val NOTE planned but not implemented yet These commands write their respective field values in the ETPUTBCR register write_tcrl_prescaler Prescaler write_tcr2 prescaler Prescaler IMPORTANT NOTE These
245. llas in the ASH print_to_trace action command Syntax for eTPU Channel Hardware Access eTPU C provides a built in type called chan_struct that allows access to such channel specific settings as IPAC OPAC PDCM TBS etc This symbolic access to channel settings has now been exposed in the eTPU Simulator Typically a chan_struct variable is defined in a standard header file etpuc h e g chan_struct channel This variable channel can then be used to access channel settings in the watch window or script command such as print_to_trace and verify_val with the syntax channel OPACA 1994 2015 ASH WARE Inc Reference Manual 6 Script Commands Files channel PDCM In addition to any chan_struct variables explicitly defined in the code the Simulator always predefines a variable called ASHchannel of type chan_struct Thus this special access is available even when the predefined headers are not used This is shown in the watch window below eTpul Watches x ASHchannel TDLA 0 6x6 register TDLA ASHchannel MRLA Up 6x6 register MRLA ASHchannel TDLB O 6x6 register TDLB ASHchannel MATCHA O 466 6x198 register MATCHA ASHchannel CAPTUREB Q 266 Gxc8 register CAPTUREB ter1 QJ 210 geg register TCR1 Hl When a chan_struct variable is accessed as described above e g print_to_trace Current channel PDCM is d ASHchannel PDCM the value accessed is always from the curre
246. llowing windows display the System Integration Module SIM settings page 214 Multi Target Development Tho 1994 2015 ASH WARE Inc Reference Manual 15 5 1 SIM Main Window 32 MyBdm32 SIM Main SIMCR HS SYNCR 5SF68 SYPCR 86 PICR 666F PITR 6666 l l l l l l l l l l l l l l l l l l RSR 88 l l l l l l l l l l l l l l l l l l Al EXOFF FRZSW FRZBH SLUEN SHEN SUPU MM IARB Y X Y EDIU SLIMP SLOCK RSTEN STSIM STEXT EXT Pow SW HLT Loc SYS TST SWE SWP SWT HHE BHE BHT PIRQL PIU PTP PTH E ef E E D P B B 9 8 Foot 6 6 3 8 F F E E D 8 Fant 4 4 3 3 Zand 1 1 D 8 Taal 6 6 5 5 4 4 yer 4 1 1 D 8 Tant 6 6 5 4 3 3 Zand 1 6 A 8 7 0 8 8 7 60 15 Operational Status Windows ol xi CLKOUT Pin On On FREEZE the watchdog amp periodic interrupt timer are Off On FREEZE the bus monitor is Off The IMB is Not Available to external bus master Show Cycles Enable is 66 SIM SZU registers access at Supu priviledge level Internal modules at FFFO66 FFFFFF SIM interrupt arbitration priority F W freq ctrl VCO multiplied by 1 X freq ctrl VCO divided by 2 Y freq ctrl UCO divided by 1F 1 Clock frequency is 8 388668 MHz assuming 32 768 KHz crystal ECLK pin addr 23 divide rate is system clock divided by 8 Crystal reference is ok UCO is locked or external Loss of reference causes limp mode During low power stop S
247. lopment Tho 1994 2015 ASH WARE Inc Reference Manual 15 Operational Status Windows Registers ROMBS0 ROMBS1 ROMBS2 and ROMBS3 15 11 4 Standby RAM Submodule Window 68336 68376 CT EE ox RAMMCR 6866 STOP F F Standby RAM SRAM is RLCK B B SRAM base address registers are locked RASP 9 8 SRAM is accessible at the unrestricted program and data priviledge level RAMBAH 6656 AD HI 7 6 F C RAMBAL 2666 AD LO Base address is 66562066 The Standby RAM Submodule window 68336 68376 displays the RAM Module Configuration Register RAMMCR the RAM Array Base Address High Register RAMBAH and the RAM Array Base Address Low Register RAMBAL 15 11 5 Static RAM Submodule Window 68338 Z2Mysim32 Static RAM submodule Tal FFF500 6666 6666 6666 6666 6666 6666 6666 6666 FFF516 1111 BEET 99099 see 6666 6666 6666 6666 FFF526 6666 6666 6666 6666 6666 6666 6666 6666 FFF5360 6666 6666 6666 6666 6666 6666 6666 6606 The Static RAM Submodule Window 68338 consists of 16 contiguous 16 bit words of RAM 15 11 6 Parallel Port UO Submodule PIOSM Window BER HI DATA Bit7 Input DDR 66 Bit Input lo Bits Input lo Bits Input lo Bit3 Input HI Bit2 Input HI l Bit1 Input lo Bit6 Input lo The Parallel Port I O Submodule window displays the PIOSM Control Register PIO17A which controls data direction and either reads or writes the port data Reference Manual C 1994 2015 A
248. lse Width Test Used in conjunction with Appends Pulse Width Test the log file to append a test Passes or fails to the result to the end of the log end of the log file file Suppress Warning 1 wsl wsl Suppress the Source Code Missing warning No Popup Dialogs Quiet Quiet Disables display of dialog boxes Accept License I AcceptLicense I AcceptLicense Skips the startup license agreement dialog box Automatically Run AutoRun AutoRun Sets the target system to running when the simulator debugger is launched Network Retry Time NetworkRetry lt Sec gt NetworkRetry 30 1994 2015 ASH WARE Inc Reference Manual 9 Functional Verification Setting Time to wait in seconds Retries for 30 seconds if for a network license if unable to make a network none is available connection Network License Checkout NetworkCheckout lt y networkcheckout 2035 5 6 16 m d h m gt 00 Perform a network license checkout providing success fail status and then Attempts to check out a exiting license until 4pm of May 6 2035 Network License Checkin NetworkCheckin NetworkCheckin Check back in a checked out license which frees the license for other users after the linger time has completed 9 6 1 Using the d define Option and Escape Characters There are issues with passing a quote character into simulator debugger in Windows because Windows uses the quote character to bunch multiple pieces of
249. ly TPU_TIME_SLOT TPU_NOP TPU_PIN_TOGGLE TPU_STATE_END TPU_MATCH CAPTURE TPU_TCR1_COUNTER TPU_TCR2_COUNTER NOTE Same as TPU_TCR1_COUNTER TPU_TCR2_COUNTER TPU_TCR_COUNTER Hardware debugger only options FREE_RUN All options ALL The following enumerated data type is used to specify the file format options when saving a trace buffer to a file enum TRACE FILE_OPTIONS VIEWABLE This format is optimized for viewing PARSEABLE This format is optimized for parsing Code Coverage Listing Options Enumerated Data Type The following enumerated data type is used to specify the listing file options when writing a code coverage annotated listing file write_coverage_listing_file script command enum COVERAGE_LISTING_OPTIONS 1994 2015 ASH WARE Inc Reference Manual 6 8 6 6 8 7 6 8 8 Reference Manual 6 Script Commands Files listing file modes ALL_LINES output all source module lines and disassembly NON_COVERED_ONLY_LINES output only non fully covered source module lines flag items below can be added to alter main modes above FILTER_ETPU_ENTRIES do not show disassembly and do not show entry table source disassembly at all in non covered mode Base Time Options Enumerated Data Type The following enumerated data type is used to specify the base time for various script commands enum BASE TIME US NS PS Build Script TARGET_TYPE Enumera
250. m macros __COMPILER_VERSION__ and ___MTDT_VERSION__ These resolve as strings and are available in script commands such as print_to_trace and verify_trace See below print_to_trace Using compiler version Se and simulator version Se ___COMPILER_VERSION__ __MTDT_VERSION__ verify _str __MTDT_VERSION__ TPU Simulator Version 3 50 Build D Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 101 6 Script Commands Files These can also be used in ASH print action commands that are embedded in the source code files as follows QASH print_to_trace Compiler version is s n COMPILER_VERSION_ Determining the Auto Run Mode The simulator debugger is often launched as part of an automated test suite Under these conditions the test starts running and executes to completion assuming no failures with no user intervention The following is automatically defined when the simulator debugger is launched in auto run mode ASH _ WARE_AUTO_RUN The following is typically found at the end of a script file used as part of an automated test suite ifdef _ASH WARE AUTO BON exit else print All tests are done endif _ASH WARE AUTO_RUN Determining the Interrupt Number Channel interrupts for channels 0 15 are numbered 0 15 ISR script commands execute in response to an enabled and asserted interrupt as described in the ISR Script Commands Files
251. mand Test vector files normally have a vector suffix Note that the vector suffix is preferable Test vector files can also be loaded via the Open Test Vector File dialog box which is opened from the Files menu by selecting the Vector Open submenu Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 63 6 Script Commands Files vector UART Vector This example loads the test vectors found in file UART Vector in the directory where the project file is located The file path is resolved relative to the directory in which the project file is located dump_file startAddress stopAddress enum ADDR_SPACE filename dump enum FILE_TYPE enum DUMP_FILE OPTIONS This command creates the file filename dump of type FILE_TYPE using the options specified by DUMP_FILE_OPTIONS The file is created from the image located between startAddress and stopAddress out of the address space ADDR_SPACE dump_file 0 Oxffff CPU32_SUPV_DATA SPACE Dump S19 SRECORD DUMP_FILE DEFAULT define MY OPTIONS NO_ADDR NO SYMBOLS dump_file 0 Oxffff CPU32_SUPV_CODE_SPACE Dump dat DIS_ASM MY_OPTIONS The downside of the dump_file command is that it does a one time dump of the entire file overwriting any previous file An alternative to this is to continuously write the trace data to a file as it is generated See the Trace Script Commands section This example creates a Motorola SRECORD file Dump S19 from the first
252. mand verifies that channel chanNumbers s pin is equal to pinState logical one or zero If the verification fails a verification failure messages is printed to the screen This verification failure message can be disabled from the Message Options dialog box verify pin 3 1 In this example channel 3 s pin is inspected and if it not a one a verification failure message is printed to the screen and the verification failure count is incremented eTPU input pins are normally controlled using test vector files eTPU output pins and TPU I O pins configured as outputs are normally controlled by the eTPU TPU and are verified using master behavior verification test files described in the Functional Verification section Therefore these commands are not the primary method for controlling and verifying pin states Instead these commands serve as a secondary capability for pin state control and verification write_chan_input_pin ChanNum Val write_chan_output_pin ChanNum Val write_tcrclk_pin Val verify chan_output_pin ChanNum Val verify ouput_buffer_disabled ChanNum verify ouput_buffer_enabled ChanNum These commands write either ChanNum s or the TCRCLK pin to value Val verify that ChanNum s pin is equal to Val or verify that an output buffer is enabled or disabled write _chan_input_pin 25 0 write_tcrclk_pin 1 In this example channel 25 s input pin is cleared to a low and the TCRCLK pin is set high verif
253. mands will not be at all accurate due to the relatively slow SPI interface to the target hardware Important debugger features that are supported are the watch window items that are available across the SPI bus such as data variables and all SPI accessible registers The circuit windows have a high level of functionality The script commands file is largely functional though not every script command is supported To return to the simulation environment simply close the debugger MC33816 CPU System Simulator Our MC33816 CPU System Simulator supports instantiation and simulation of an arbitrary number and combination of MC33816s and CPUs A dedicated external system modeling CPU could be used for instance to model the behavior of an automobile engine Executable code can be individually loaded into each of these targets Synchronization between targets is fully retained as the full system simulation progresses All CPU engine targets can be used with this system simulation include the CPU32 and soon to be released PPC simulation engines eTPU CPU System Simulator Our eTPU CPU System Simulator supports instantiation and simulation of an arbitrary number and combination of eTPUs and CPUs A dedicated external system modeling CPU could be used for instance to model the behavior of an automobile engine Executable code can be individually loaded into each of these targets Synchronization between targets is fully retained as the full system si
254. mation which is time units for the first column followed by pin names of all saved pin data After that each line contains a simulation time value in microseconds followed by the value of each pin Below is an example of the first few lines of an ebv file which contains data on just two pins TIME US PWM_A PWM_B 000000000000 000000 0 000000000019 980000 1 0 000000000039 980000 L 1 tf r 1 r r 1 000000000049 980000 0 0 The comma separated value allows the file to be easily parsed by other existing tools such as spreadsheet applications Once a master ebv file has been created it can be used to verify pin behavior stays within an expected tolerance range on subsequent simulation runs Typically this is done after a software change has been made that is not supposed to affect pin transition behavior With enhanced behavior verification only a continuous verification model is supported As with ebv file creation all control is via script commands First which ebv file to be used for the verification run must be specified this is done with run_ebehavior_file filename ebv By default all pins found in the ebv file are verified with a default transition error tolerance equivalent to two system clocks test all pins run_ebehavior_file PWM_gold EBV The above command should be issued at simulation time zero at the same place in the script file as the ebv file was generated with the create_ebehav
255. me is entered as thousands of seconds ksec seconds secs milliseconds ms microseconds us and nanoseconds ns Note that the simulator debugger resolution is one instruction cycle Help This accesses this help window Goto Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 241 16 Dialog Boxes 16 4 This closes the Goto Time dialog box and runs the simulator debugger until the specified time OK Save This closes the Goto Time dialog box and saves any changes The simulator debugger remains idle Cancel This closes the Goto Time dialog box without saving any changes Goto Angle Dialog Box The Goto Angle Dialog Box is opened via the Run menu by selecting the Goto Angle submenu It provides the capability to execute the active target until it gets at or beyond the specified angle The eTPU must be in angle mode AM 1 in order for this to function properly This dialog box uses the TCR2 counter and user defined angle indices to calculate the angle See the eTPU Time Base Configuration Script Commands section for setting the angle indices The Cycles field refers to the number of times the angle has rolled over For example in an automobile engine two rotations constitutes one cycle The angle therefore goes from 0 degrees to 720 degrees then rolls over back to zero degrees Cycles is the count of these rollovers The current angle can be seen in the status bar at the b
256. med TPU The last argument ALL_SPACES is potentially problematic as will be discussed later Shared Memory Address Space Transformation No assumptions should be made about address spaces between or among dissimilar targets In other words the code space of a CPU32 may not map to the code space of memory shared witha TPU For memory docks between dissimilar target types it is critical to fully specify all address spaces from the docking memory block Due to the lack of symmetry this is not true for the dockee The following script command should be used to fully define all docked address spaces between dissimilar targets When docking a CPU to a TPU the following address space transformation such as that shown in the following figure is often required page 294 Multi Target Development Td 1994 2015 ASH WARE Inc Reference Manual 20 Building the Target Environment TPU PINS Space All Modeling CPU Spaces Other TPU Spaces FFFFFFFF FFFFFFFF ER The following build script commands generate the address space transformations shown in the above figure If the modeling CPU does a read from its address C0000 hexadecimal the read will actually access the shared memory with the TPU in its PINS space set_block_dock_space ModelingCpu TpuPinsDock ALL SPACES RW_ALL TPU_PINS_SPACE In this example all address spaces from a docked block of a modeling CPU are set to the TPU s PINS address space This is an eight to one transform
257. memory for a target TargetName and creates a report file ReportFileName The check invoked by this command occurs whether or not this script command is included in the script file Use of this command allows you to specify the name of the report file and limit the scope of the check to a single target check Host C Temp CpuBuildReport txt check eTPU_A TpuBuildReport txt In this example report files named C Temp CpuBuildReport txt and TpuBuildReport txt are generated for the Host and eTPU_A targets respectively Note that C style double backslashes are required when separating directory names Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 307
258. message Subroutine Return from Outside a Subroutine When the TPU performs a subroutine call the calling address is pushed unto the stack It would be legal but highly suspicious to do multiple subroutine returns following a single subroutine call Sequential TCRx Write than Read This is actually legal but it is unlikely that it does what you want it to You see the read finds the pre written value having to do with some usual TPU craziness Entry Bank Register Accessed Multiple Times In the real TPU the register holding the entry bank number can be written only once The TPU Simulator allows this register to be written multiple times but gives a warning if you choose to do so Address Rollover Within a Bank TPU2 and TPU3 support multiple banks TPU behavior is not defined if a non end and non return last bank instruction is executed Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 249 16 Dialog Boxes 16 10 Source Code Search Dialog Box The Source Code Search Options dialog box is opened from the Options menu by selecting the Source Search submenu When the executable image is loaded there are normally a number of source code files associated with the executable image that get loaded The simulator debugger needs to be able to find these files This dialog box allows specification of source code directories to be searched when searching for these source code files The search locations can be sp
259. mmand line parameters allow specific tests to be run From the command line the project file that is run and the primary script file s that are loaded into each target are specified Command line parameters also are used to specify that the target system automatically start running with no user intervention and to accept the license agreement thereby bypassing the dialog box that would otherwise open up and require user intervention A script command is used to terminate the simulator debugger once all the tests have been run Upon termination the simulator debugger sets the error level to zero if no verification tests failed and otherwise error level is set to be non zero This error level is the simulator debugger s termination code and can be queried within a batch file running under the operating system s DOS shell By launching the simulator debugger multiple times each time with a different set of tests specified and by checking the error level each time the simulator debugger terminates multiple tests can be run automatically and a single pass meaning all tests passed or fail meaning one or more tests failed result can be determined Note that this only works in operating systems that support access to exit codes from a batch file Windows 98 does not support this True operating systems such as Windows 7 Windows XP Professional Windows 2000 Professional and Windows NT 4 0 do support Reference Manual C 1994 2015 ASH WARE D
260. mmands file is reread MtDt state is not modified When MtDt is reset the user has the option of re initializing the primary script commands file opening a new or modified primary script commands file or taking no action If no action is taken primary script commands file execution will continue from where it left off before the reset The user selects the desired option via the Reset submenu in the Options menu This submenu activates the Reset Options dialog box When the primary script commands file is reread its execution starts back at the first line This allows the user to modify and then rerun a series of script commands without exiting MtDt Only one primary script commands file may be active at a time Multiple ISR script commands files may be open at once but only a single ISR script commands can be associated with each TPU channel Note that each ISR script commands file can be associated with multiple TPU channels Debugging Capabilities in Script Command Windows These capabilities are available starting in version 3 20 Script commands file windows support breakpoints Similar to source code windows breakpoints can be set cleared enabled and disabled See the Breakpoints Menu section for a complete explanation A goto line capability is supported within the script commands file windows Although this can be activated from the Run menu as described in the Run Menu section a more convenient method is to right click on the
261. mmands files are associated with channels using the load_isr and similar script commands The primary script commands file begins execution after a simulator debugger reset whereas ISR script commands files execute when the associated interrupt becomes both asserted and enabled The primary script commands file is preempted by the ISR script commands files ISR script commands files are not preempted even by other ISR script commands files and even if the discouraged use of timing commands with these ISR script commands files is adapted Only a single primary script commands file can be active at any given time Each interrupt source can have only a single ISR script commands file associated with it Within the TPU s interrupt service routine the ISR script commands file should clear the interrupt This is accomplished using the clear_cisr X the clear_this_cisr or similar script command Failure to clear the interrupt request causes an infinite loop Within the eTPU s interrupt service routine the ISR script commands file should clear the interrupt This is accomplished using the clear_chan_intr X the clear_this_intr or similar script command Failure to clear the interrupt request causes an infinite loop A single ISR script commands file can be associated with multiple interrupt sources such as eTPU TPU channels To make the ISR script commands file portable across multiple channels be sure to use the clear_this_intr or
262. mode IARB 3 6 Interrupt arbitration priority 6 CANICR Dout ILCAN A 8 Interrupt request is disabled IUBA 7 5 Interrupt vector base upper 3 bits are 2 CANCTRL6 4486 Bofflisk F F BUS OFF interrupt is Disabled Errlsk E EI ERROR interrupt is ENABLED Rx1Mode B B On the CANRX1 pin a logic 6 is dominant 1 is recessive Rx Mode A A On the CANRX6 pin a logic 1 is dominant 6 is recessive TxMode 9 8 Full CMOS positive polarity CANTX6 6 CANTX1 1 is dominant SAMP 7 7 Sample each receive bit three times Loop 6 6 Internal loopback is Disabled TSYNC 5 5 Timer synchrnization Disabled LBUF 4 4 Message buffer with lowest ID is transmitted first PROPSEG 2 6 PROPSEG 6 gt Propogation Segment Time 666 659 6 ns PRESDIU CTRL PRESDIV 7 6 PRESDIUV 66 gt Clock 666 059 6 ns 6066 RJV 7 6 RJW 6 gt Resynchronization Jump Width 666 659 6 ns PSEG1 5 3 PSEG1 6 gt Phase Buffer Segment 1 666 6059 6 ns PSEG2 2 6 PSEG2 6 gt Phase Buffer Segment 1 666 659 6 ns l l l l l l l l l l l l l l l l l l l l l l l l The TouCAN Main window displays the TouCAN Module Configuration Register CANMCR the TouCAN Interrupt Configuration Register CANICR the TouCAN Control Registers 0 1 and 2 CANCTRLO CANCTRL1 and CANCTRL2 the touCAN Prescaler Divide Register PRESDIV the Receive Global Mask High and Low Registers RXGMSKHI RXGMSKLO the Receive Buffer 14 an
263. mory Write Selecting this option causes each memory write to be logged to the trace buffer Exception Selecting this option causes each exception to be logged to the trace buffer This is only page 254 Multi Target Development Td amp 1994 2015 ASH WARE Inc Reference Manual 16 Dialog Boxes meaningful in the context of CPU targets Time Slot Transition Selecting this option causes each time slot transition to be logged to the trace buffer This is only meaningful in the context of TPU targets State End Selecting this option causes state end to be logged to the trace buffer This is only meaningful in the context of TPU targets Pin Transition Selecting this option causes each pin transition to be logged to the trace buffer This is only meaningful in the context of TPU targets SGL Negation NOP Selecting this option causes SGL negation NOP to be logged to the trace buffer This is only meaningful in the context of TPU targets Trace Window and Trace Buffer Considerations The Trace Options Dialog Box specifies what is stored in the trace buffer The Trace Window displays all trace information stored in the trace buffer regardless of whether or not this information is enabled for storage If information has already been stored in the buffer and you disable tracing of this information the information will not disappear from the Trace Window until the buffer has been completely overwritten with new information or until the
264. mory script commands Verify memory script commands Register write script commands Register verification script commands Symbol value write script commands Symbol value verification script commands System script commands File script commands Trace script commands Code coverage script commands RAM test script commands eTPU TPU Script Commands Channel function select register script commands Channel priority register script commands Host service request register script commands Interrupt association script commands External boolean logic script commands Pin control and verification script commands Pin transition behavior script commands Disable messages script commands Clear Worst Case Thread Indices Commands eTPU Script Commands System configuration commands Timing configuration commands STAC Bus commands Global Data Commands Channel data commands Channel base address commands Engine data commands Channel function mode FM commands Channel event vector entry commands page 52 Multi Target Development Tod 1994 2015 ASH WARE Inc Reference Manual 6 6 1 6 Script Commands Files Interrupt script commands Shared Subsystem Script Commands TPU Script Commands TPU parameter RAM script commands TPU channel interrupt service register script commands TPU host sequence request register script commands TPU clock control script commands TPU bank and mode control script commands TPU match transition and li
265. mulation progresses All CPU engine targets can be used with this system simulation include the CPU32 and soon to be released PPC simulation engines page 276 Multi Target Development Td 1994 2015 ASH WARE Inc Reference Manual 19 Supported Targets and Available Products 19 4 TPU CPU32 Full System Simulator Our TPU CPU32 System Simulator supports instantiation and simulation of an arbitrary number and combination of TPUs and CPU32s A dedicated external system modeling CPU32 could be used for instance to model the behavior of an automobile engine Executable code can be individually loaded into each of these targets Synchronization between and among targets is fully retained as the full system simulation progresses Standard single target debugging capabilities such as single stepping breakpoints goto cursors etc are fully supported within this full system simulation environment For instance breakpoints can be inserted and activated within several targets simultaneously The full system simulation is halted as soon as a breakpoint is encountered in any target 19 5 MC33816 Stand Alone Simulator This product is a single target version that uses only the MC33816 simulation engine Because it is a stand alone product the user must use script commands files to act as the host and test vector files to act as the external system The MC33816 Stand Alone Simulator is a superset of the MC33816 CPU System Simulator in that purchase
266. n this section creates a TPU simulation engine a host CPU simulation engine and a modeling CPU simulation engine The shared memory architecture from the following figure is generated page 296 Multi Target Development Td 1994 2015 ASH WARE Inc Reference Manual 20 Building the Target Environment TPU DATA Space Host CPU All Spaces FFFFFFFF FFFFFFFF FFFFF FFE00 Modeling CPU All Spaces FFFFFFFF TPU PINS Space FFFFFFFF The following build script commands instantiate the shared memory architecture found in the above figure define MEM END Oxffffffff Create a target TPU instantiate_target TPU_SIM Tpu Create a simulated memory block for the TPU s code microcode add_mem_block Tpu 0 Ox1lfff Code TPU_CODE_SPACE add_non_mem_block Tpu 0x2000 MEN END B1 Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 297 20 Building the Target Environment TPU_CODE_SPACE Create a simulated memory block for the TPU s data host interface add_mem_block Tpu 0 Ox1lff Data TPU_DATA_SPACE add_non_mem_block Tpu 0x200 MEM END B2 TPU_DATA SPACE Create a simulated memory block for the TPU s pins channel pins and TCR2 counter pin add_mem_block Tpu 0x0 0x3 Pins TPU_PINS_SPACE add_non_mem_block Tpu 0x4 MEM END B3 TPU_PINS_SPACE Be sure to provide a non_mem block for the unused address spaces add_non_mem_bl
267. nd international laws and treaties protect these rights Any misuse or other violation of the copyright will be prosecuted to the full extent of the law The simulator debugger media may not be copied or transmitted except for the purpose of creating a backup copy for archival purposes 16 23 BDM Port Dialog Box The BDM Port dialog box is used only in the rare event that simulator debugger finds BDM target hardware on multiple parallel ports In this case you are asked to select target hardware from a list found during BDM auto detection Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 259 page 260 Multi Target Development Tool 17 Menus 17 Menus The main menu consists of the following menu items Files Menu Step Menu Run Menu Breakpoints Menu Activate Menu View Menu Window Menu Options Menu Help Menu 17 1 Files Menu The Executable Open submenu This opens the Load Executable dialog box The Executable Fast Submenu This provides a fast repeat capability for the Load Executable dialog box By selecting this submenu the actions set up in the Load Executable dialog box are quickly repeated without having to actually open the dialog box Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 261 17 Menus The Primary Script Open Submenu This opens the Open Primary Script File dialog box The Primary Script Fast Submenu This provides a fast repeat capability for
268. ng the left mouse button The simulator will reset and execute to precisely 2 191 1 microseconds Verify this observing the time in the current time field shown by arrow 3 Tv TpuSim Logic Analyzer lo sl uaRT_RcV x EN D A Mouse 005 427 4 uS 008 000 Context 004 479 1 vS Current Time 007 651 6 vS Delta Cursor 000 936 0 vS Right Cursor 003 127 1 uS A similar method can be used to execute to a context time The context time is shown at arrow 4 above The context time is the time at which some context event occurs For instance in the trace window click on any stored event By clicking on the event the time at which that event occurred becomes the context time Similarly in the thread window click on a worst case thread and the time at which the first instruction of the worst case page 160 Multi Target Development Td 1994 2015 ASH WARE Inc Reference Manual 14 The Logic Analyzer thread occurred becomes the context time This context time can then be dragged into the current time field causing the simulator to execute to that precise time 14 2 Waveform Selection The Logic Analyzer displays nodes from the pin transition trace buffer as a waveform Nodes are added to the display when they are selected from within the drop down list box located to the left of the waveform display panel The nodes that may be displayed include the TPU channel I O pins and the TCR2 pin as well as any
269. nk script commands Build Script Commands Build script commands Clock Control Script Commands The script commands described in this section provide control over the clock and frequency settings The set_cpu_frequency script command has been deprecated Instead use the set_clk_period script command described in this section A warning message is generated when this command is used This message can be disabled from the Message Options dialog box set_clk_period femtoSecondPerClkTick The script command listed above sets the target s clock period in femto seconds per clock tick Note that one femto second is le 15 of a second or one billionth of a micro second A simple conversion is to invert the desired MHz and multiply by a billion 1e9 16 778 59601860 femto seconds set_clk_period 59601860 In this example the CPU clock frequency is set to 59 601 860 femto seconds which is 16 778 MHz Many Freescale MC683xx microcontrollers use an external low frequency crystal to generate the CPU s clock source This crystal generally has a frequency of 32 768 KHz or 2 to the 15th cycles per second A crystal of this frequency is known as a watch crystal because a simple 15 bit ripple counter can be used to generate a one second clock tick A phase lock loop within the 683xx microcontroller uses this to synthesize the main CPU clock The simulator debugger assumes that this external crystal oscillates at 32768 cycles per
270. nnnnnnnnnnnnnnnnnnnnnnn nnen ne 53 Timing Script Commande sseesEREEREENEENEESEEEEEEEEEEEEEEREEREEREEREEREEREEEEERREEREEEEEREESEEEEESEEEn 54 Verify Timing Script COM MAMAS ou eeetsetssteeseeseesesseeseesneseesesessevonvenesnesneeneneanaes 55 Memory Modify Script COM MAMAS cctstsssesseeeeeseeeeeesesessessessevseeseeeneseesoennens 56 Memory Verify Script COMMANAS ccstsstesesseeeeeseeeeeeseeseessessessevsenseeeneenenaennens 56 Register Write Script COMMAMNAS cccctessssseeeeseeeseeseeseeneseeseeseeeeeseeesnesneneenaneas 57 Register Verify Script Commands 58 Symbol Write Script CommandS eeeesetsteeseeseeseeseeseeseeseesaessessevsevseeenesneseennanens 58 Verify Symbol Value Script Commande sseeeSEREEREEREEREEREERREERERREENEEREENEESEENEESEEen 60 System Script Command S serie iaee aeae aaa aaia 61 File Script COM MAMAS eeeeEEREEREESEESEEREENEEREEEEEEREEREEREEREEREEREEREEREEEEEEEEEEEEEEESEESEESEESEENEN 63 Trace Script COM MAMAS ce ceseseeeeeeeeestessessesseeseeseeseesoesoesaesaesaevanvaneoneanenneneanaes 65 Code Coverage Script COM MAMAS cssssceenseeeseeeseerseeseeeseeeseneseeeseneneeeseneneeeenees 68 RAM Test Script COM MAMAS cccestseeeteeseeseeseeseveevsneseeseeneesnesaesaeseesseeseesneseeeaneas 72 Channel Function Select Register COM MAMAS ssssecsetseeseeeseeseeeeeneneereeeees 74 Channel Priority Register Commands Pin Control Script COMM ANS cesteteseseesesseesev
271. nnnunnnnnnnnnnnnnnnennnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn ennnen nnen 217 Multi Target Development Tool page 7 Multi Target Development Tool 15 6 QSM Module Windows c ccccccsscscncceccececnsceceseecuseseesaeaususeeneuaeeeseeeenaeaes 217 QSM Main Window QSM Port Window QSM and QSPI Wind Te UE 219 QSM and SCI UART Wind OW cssccessesseeseeeseeseeseenseeeeeenseenseeneeenaeenaeesaneneeeeaes 220 15 7 TPU Module Windows cccccesecseeseeeeeesseesneesneeenecensenesenesensseneseneanens 220 TPU Emulation RAM Window 2 ccs cccseenesseeeeseeeeseeeeneeeeeseeeeseeeenseeeeseeeeneeeenseeees 220 RS ER WINDOW wccseecvseciccnscccccecestecsenceeseocsesneivaducssnonessceesenseecentsesbecessenessoncentersancestss 221 TPU Host Interface Window ccsecccsecceeeeeeeseeeeseeeeseeeenseeeeseeeeseensnseeeeseeeeneenenseeess 221 TPU Parameter RAM Window 2 cccseecesseeeeseeeeeeeeenseeeeseeeeneeeenseeeeseeeeneenenseeees 222 15 8 GPT Module Windows c cccesccseeeseeceeeseeeneeeneeeneeensenesenssenssenesenesnens 222 GPT Main Wind Le UE 223 GPT Input Captures Window cc cesesessssesestesessesseesessenseeseeseesneneeneesaesansaneaes 223 GPT Output Compares Wind OW c css esseesesteseessesseesesseeeeeseeseeseesnensesnesesaneans 224 GPT Pulse Accum ulation WiNGOW 2 cs cceseceeeeeceeeeeeeeeeeeeeeensneeeeseeeeeeeeeenenenees 224 GPT Pulse Width Modulation Window
272. not offered as a specific product MtDt supports mixing hardware and simulated targets This would allow for instance a software model of a new CPU to be linked to a real peripheral across a BDM Port Driver code could be developed for a CPU that exists only as a software model but controls real hardware Source Code Files Source code files are built using a compiler or an assembler and the resulting executable image is loaded into the target core code space When executing code it is actually the executable image that gets executed Source level debugging information cross references the source code files line numbers and variables with the underlying executable image thereby supporting key debugging capabilities such as breakpoints single stepping viewing modifying variables in watch windows etc Source code must be built external to Mtdt and once built loaded into the executable memory using the lt Ctrl E gt hotkey Script Commands Files Script commands files have several purposes The primary script file used to automate things like loading code initialization and functional verification ISR script files can be associated with specific interrupts and execute only when that interrupt is activated Startup script commands files available to the MC33816 and CPU are executed following a reset or when the simulator debugger is initially launched The purposes of the startup script commands file is initialization and getting the targ
273. nsidered to be just outside the display edge for the drag and drop operation 14 7 Vertical Yellow Context Time Cursor The Vertical Yellow Context Time Cursor The vertical yellow context cursor is the time of some referenced event occurring elsewhere in the IDE For instance open a trace window and scroll backward through the trace data The vertical yellow context cursor will show the time at which the trace window event occurred This context capability is a powerful debugging tool The source code associated with the trace data also pops into view This allows you to line up previously executed source code the trace data and in some cases the call stack data If you want to re execute to that context time use the mouse to drag the time from the context time indicator into the current time indicator as explained in the Executing to a Precise Time section Context Time Indicator The context time indicator displays the time with the IDE wide context time For example Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 165 14 The Logic Analyzer select a past event in a trace window The time associated with this event becomes the context time This context time appears as the vertical yellow context cursor in the waveform display Drag and drop this time into the current time as explained in the Executing to a Precise Time section 14 8 Scroll Bars The horizontal scroll bar provides the functionality sh
274. nt channel as indicated by the chan register There are times where it is useful to access channel fields for other than the active channel The following script commands could be used to help test thread handling when both TDLA and a link service request LSR are set write_val ASHchannel TDLA 1 write_val ASHchannel LSR 1 As written above they only apply to the current channel or whatever the chan register is currently set to if no thread is active Similar to channel variables the channel relative syntax can be applied to chan_struct type variables lt channel number channel vector name gt Setting TDLA and LSR on channel 5 which for example we assume is named P_IN in the vector file the script should be something like as follows write_val 5 ASHchannel TDLA 1 write_val P_IN ASHchannel LSR 1 Note that when writing channel settings great care must be taken For example setting TDLB without setting TDLA may result in undefined behavior Not all channel fields described in the chan_struct type definition are supported and several additional ones have been added the supported list is as follows IPACA IPACB LSR Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 47 6 Script Commands Files 6 5 10 page 48 Multi Target Development Tod MRLA MRLB MTD OPACA OPACB PDCM TBSA TBSB FLAGO FLAG1 FMO FM1 PSS PSTI PSTO
275. nt_to_trace Current channel is d chan Note that write only registers like link do not provide meaningful data In addition the ALU and MDU condition codes are exposed to the symbolic script commands via the CC symbol struct unsigned int V 1 ALU overflow condition code unsigned int N 1 ALU negative condition code unsigned int C 1 ALU carry condition code unsigned int Z 1 ALU zero condition code unsigned int MV 1 MDU overflow condition code unsigned int MN 1 MDU negative condition code unsigned int MC 1 MDU carry condition code unsigned int MZ 1 MDU zero condition code unsigned int MB 1 MDU busy flag unsigned int SMLCK 1 semaphore locked flag CC This allows for script access such as the examples below print_to_trace CC N d CC N verify val CC N 1 verify val CC Z 0 verify val CC SMLCK 0O print_to_trace CC MZ d CC MZ Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 49 6 Script Commands Files verify val CC MN 0 verify val CC MZ 1 6 5 11 String within a string supports formatted symbolic information The string within a string formatted supports generation of formatted symbolic information by certain script commands The format is a C string with a second embedded C string The embedded sting must use the backslash escape character to b
276. nter associated with stacked functions as shown above Call Stack Local Variables and Source Window Automation It is often not sufficient to simply view the functions on the call stack The Call Stack window works in conjunction with the source code and the local variable window to show both the source code line and the stacked local variables associated with any stacked function For instance the second line of the above Call Stack has been selected This line is Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 181 15 Operational Status Windows associated with the PTA_DemolInit function When you move the cursor to this line the source code file shown below automatically pops into view and the source code line scrolls into view and is highlighted with yellow 2 5 x void PTA_DemoInit U32 tpuBaseAddr U16 vecBase J2 Host Source platformDemo c const int PTAFuncNum Oxf write chan ee write_chan_func tpuBaseAddr 1 PTAFuncNum write chan herrftouRaseAddr 1 21 Upon selection of the Call Stack window s second line the Local Variables window is also affected as shown below The highlighted function PTA_DemoInit had several local variables that were stored on the stack The values of these local variables are automatically displayed in the Local Variables window D Host Local variable Window Automatic Tracking tpuBase ddr 776704 pE E 16 vecBase 64 6x4 PTAFuncNun
277. nual 15 Operational Status Windows 15 9 4 CTM4 Double Action Submodule Window 32My68376 CTM4 Double Actions DASM RE ll SIC 2B88 FLAG F F An input capture or output compare has R IL E C Interrupt is level 2 IARB3 B B Int arbitration bit 3 is SET BIUMCR IARB 2 6 WOR 9 9 IF output then buffer operates in wired or mode BSL 8 8 Connected to time base bus B IN 7 7 If input then the pin is High FORCA 6 6 Set to force channel A compare always reads 6 FORCB 5 5 Set to force channel B compare always reads 8 EDPOL 4 4 O is A compare on channel A sets the ouptut pin to logic 1 l A compare on channel B clears the ouptut pin to logic 8 MODE 3 0 OPWH Output pulse width modulation 16 bit resolution DATA A GBBS F 6 The DATA A register value is 6BB5 DATA B E97B F 6 The DATA B register value is E97B EE DASH 4 i eal aan aa an ale amie EE SIC 6606 FLAG F F I An input capture or output compare has not occured E The CTM4 Double Action Submodule window displays the DASM 3 4 9 and 10 Status Interrupt Control Registers DASM3SIC DASM4SIC DASM9SIC DASM10SIC and the DASM 3 4 9 and 10 Data Register A and B registers DASM3A DASM4A DASM9A DASM10A DASM3B DASM4B DASM9B and DASM10B 15 9 5 CTM4 Pulse Width Modulation Window 32My68376 CTM4 Pulse Width N loj xj PWM 5 al SIC 28606 FLAG F F A PW
278. number can be automatically generated using the following macro pragma write h define MY_FUNC_NUM ETPUfunctionnumber Pwm Channel Priority Register Commands write_chan_cpr ChanNum Val This command writes the priority assignment Val to the CPR for channel ChanNum write _chan_cpr 6 2 In this example a middle priority level 2 middle priority is assigned to channel 6 by writing a two to the CPR bits for channel 6 All other TPU channel priority assignments remain unchanged Pin Control Script Commands TPU I O pins configured as inputs are normally controlled using test vector files TPU I O pins configured as outputs are normally controlled by the TPU and are verified using master behavior verification test files described in the Functional Verification section Therefore these commands are not the primary method for controlling and verifying pin states Instead these commands serve as a secondary capability for pin state control and verification pin_hi chanNum pin_lo chanNum ter2_hi ter2_lo These commands sets either channel chanNums s or the TCR2 s pin hi logical 1 or lo logical 0 pin_hi 0xC page 74 Multi Target Development Tod 1994 2015 ASH WARE Inc Reference Manual 6 Script Commands Files pin_lo 5 ter2 lo o In this example channel 12 s pin is set to high channel 5 s pin is set low and the TCR2 pin is set low verify pin chanNumber pinState This com
279. number of iterations specified by numlterations The test attempts to provide diagnostics on any errors For instance it will attempt to isolate specific data lines as stuck high or stuck low and if successful will report the suspected problem test_random startAddress stopAddress enum ADDR_SPACE numIterations This command runs the data line RAM test between stopAddress and startAddress in the address space ADDR_SPACE for the number of iterations specified by numlterations This is the most robust test but it provides no diagnostic capabilities It writes a pseudo random number sequence to the entire memory device and then verifies that it reads back correctly The most difficult to detect errors will generally be detected by this test test_increment startAddress stopAddress startVal enum ADDR_SPACE numIterations This command runs the block increment RAM test between stopAddress and startAddress in the address space ADDR_SPACE for the number of iterations specified by numiterations using the start value startVal as the initial value from which to increment This is the least robust test but it is excellent for human factors purposes Folks like you and I are generally quite good at picking out breaks in patterns For a typical memory error this test sets the memory to a convenient pattern so that we can easily spot errors by scrolling down through a memory dump window test_seam address enum ADDR_SPACE numIterations
280. nvalidated and any verification scripts that thereafter test the timers will result in verification failures The test tag is case sensitive such that the following tag ASH timer_start TestTag is a different test from the following tag QASH timer_start TESTTAG On both target reset and on code reload all timing measurements are reset Related Information Naming timing regions in source code Verifying traversal times a script command file View named timing regions timing using the Watch Window List named timing regions in the Insert Watch Dialog Box Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 149 10 Action Tags 10 3 Write Value Action Tag When the source code containing a write value action tag is traversed the specified symbolic write value script command write_val write_val_int or write_val_fp is exercised ASH write_val s24 0x123456 ASH write_val_int varui32 0x10101010 Q ASH write_val_fp ratio 0 232323 See the Print Action Tag section for more information on referencing channel frame variables 1994 2015 ASH WARE Inc page 150 Multi Target Development Tho Reference Manual 11 External Circuitry 11 External Circuitry This section covers external circuitry 11 1 Logic Simulation External logic is used to drive one I O or input pin with other I O or output pin s External logic can include buffers inverters and gate
281. ock Tpu 0x0 MEM END B4 TPU_UNUSED_SPACE BRK k d ke k k de ke k k k k k k k END OF TPU k kk k k k k k k k k k k k k k k k k k k k Create a target host CPU instantiate_target SIM32 HostCpu Add a half meg RAM add_mem_block HostCpu 0 Ox7FFFF RAM ALL SPACES Add three empty spaces add_non_mem_block HostCpu 0x80000 OxFFDFF B1 ALL_SPACES add_non_mem_block HostCpu OxFFEOO OxFFFFF TpuDataDock ALL_SPACES add_non_mem_block HostCpu 0x100000 MEM END B2 ALL_SPACES Set the middle empty block to dock with the TPU target set_block_to_dock HostCpu TpuDataDock ALL SPACES Tpu O 0x80000 Make sure that no matter which space the TPU accesses within this dock the TPU s data space is always accessed set_block_dock_space HostCpu TpuDataDock ALL SPACES RW_ALL TPU_DATA_ SPACE xkkkkkkkkkkkkkkk END OF HOST CPU k k dedede kedede k ded kkk k k k page 298 Multi Target Development Td amp 1994 2015 ASH WARE Inc Reference Manual 20 Building the Target Environment Create a CPU for modeling the external system instantiate_target SIM32 ModelCpu Add a half meg RAM add_mem_block ModelCpu 0 OxBFFFF RAM ALL SPACES Add three empty spaces add_non_mem_block ModelCpu 0xC0000 0xC0003 TpuPinsDock ALL SPACES add_non_mem_block ModelCpu 0xC0004 0xD0003 CpuCpuShare ALL SPACES add_non_mem_
282. ock s Memory Block Size Each memory block has a specific size The size is equal to the stop address minus the start address plus one A common error is to overlap by one byte the end of one device with the start of the next device MtDt cannot support multiple devices occupying the same address in the same address space so this causes an error One method for avoiding page 290 Multi Target Development Td amp 1994 2015 ASH WARE Inc Reference Manual 20 Building the Target Environment this error is to cascade define directives and thereby ensure that contiguous devices form the proper zero byte seam define FLASH SIZE 0x10000 64K FLASH device define RAM SIZE 0x8000 32K RAM device define FLASH START 0 define FLASH END FLASH START FLASH SIZE 1 define RAM START FLASH END 1 define RAM END RAM START RAM SIZE 1 define BLANK START RAM END 1 define BLANK END FFFFFFFF instantiate_target SIM32 MyCpu add_mem_block MyCpu FLASH_START FLASH_END Flash ALL SPACES add_mem_block MyCpu RAM START RAM END RAM ALL_SPACES add_non_mem_block MyCpu BLANK_START BLANK_END Empty ALL_SPACES In this example two devices are created in such a way that a zero byte seams between them is guaranteed All memory for every address spaces is covered Notice that the FLASH and RAM sizes can be changed at a single location and that the devices will remain contiguous in memory
283. of the Stand Alone Simulator license allows installation of a fully functional Stand Alone Simulator product as well as the full System Simulator configuration 19 6 eTPU2 Stand Alone Simulator This product is a single target version that uses only a single instance of our eTPU2 simulation engine Because it is a stand alone product the user must use script commands files to act as the host and test vector files to act as the external system The eTPU2 Stand Alone Simulator is a superset of the eTPU Stand Alone Simulator in that purchase of the eTPU2 Stand Alone Simulator license allows installation of a fully functional eTPU Stand Alone Simulator product as well as an eTPU2 Stand Alone Simulator product Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 277 19 Supported Targets and Available Products 19 7 19 8 19 9 eTPU Stand Alone Simulator This product is a single target version that uses only a single instance of our eTPU simulation engine Because it is a stand alone product the user must use script commands files to act as the host and test vector files to act as the external system This product simulates the originaleTPU1 from Freescale For simulation of the new eTPU2 see the eTPU2 Stand Alone Simulator product TPU Stand Alone Simulator This product is a single target version that uses only a single instance of our TPU Simulation engine Because it is a stand alone product the user must us
284. og box Target This displays a list of targets that can be activated The active target is the one used when target specific functions such as single stepping are selected This feature is useful only in a multiple target environment Help This accesses this help screen View Menu This menu opens the various Simulator windows for viewing The simulator debugger allows multiple instances of each window to be open simultaneously When there are multiple targets a submenu for each target appears Otherwise all available windows are available directly within the view menu See the Operational Status Windows chapter for a listing of the available windows for each target Help This accesses this help screen page 268 Multi Target Development Td 1994 2015 ASH WARE Inc Reference Manual 17 Menus 17 7 Window Menu The Window menu accesses the four standard windows functions Cascade Tile Arrange Icons and Close All The standard Windows size toggle function switches the window between maximized and normal size In addition there is a list of all open windows Selecting an open window from this list causes that window to pop to the front Occupy Workshop This opens the Occupy Workshop dialog box This allows display of the currently active window within the various workshops to be enabled and disabled Redraw All This causes all windows to be redrawn In addition all windows caches are invalidated thereby forcing sim
285. ol page 185 15 Operational Status Windows eTpul1 ThreadStats RevA loj x Table THREAD STEPS Addr Addr Cnt WC Tot WC Time 6 6646 G2FC 2 2 646 nS RE_INIT_INTERRUPT 1 6042 62FC RE_INIT_INTERRUPT 2 8044 org RE_INIT_INTERRUPT 3 68646 62FC RE_INIT_INTERRUPT 4 8648 6200 1 48 1 368 nS INITIALIZE 5 884A 6568 INUALID_THREAD_FAULT 6 BOC 6568 INVALID THREAD FAULT 7 OOE 68568 6 INVALID THREAD FAULT 8 0050 G4E4 LINE WERT IDLE FAULT 9 0052 0478 VALID_GAP_NO_DATA 10 6654 OLEH LINE _ WENT IDLE FAULT 11 46656 63E6 16 12 326 nS UVALID_GAP_AND_DATA 12 6658 DEM LIRE _WENT_IDLE_ FAULT 13 BOSA 6478 ses VALID _ GAP_NO_ DATA 14 BOSC DEM LIRE WENT_ IDLE FAULT 15 BOSE 83E 0 VALID GAP_AND_ DATA 16 6668 6364 RECEIVED DATA BIT_8_23 17 6662 04B 4 wg BIT_DETECTED_IN_GAP_HUNT 18 6664 6368 RECEIVED _DATA_BIT_24 31 19 6666 6498 TOO_MANY_BITS_FAULT 20 6668 6364 11 25 233 566 nS RECEIVED _DATA_BIT_6 23 21 666A G4B4 BIT_DETECTED_IN_GAP_HUNT 22 666C 6368 2 23 52 466 nS RECEIVED DATA_BIT_24 31 23 BE 6498 24 6676 6364 25 6672 6478 26 66074 6368 27 6676 3E6 28 6678 6364 29 667A 6478 36 667C 6368 31 807E 83E 8 00 Hong BITS FAULT RECEIVED DATA_BIT_6 23 UALID_GAP_NO_DATA RECEIVED DATA_BIT_24 31 UALID_GAP_AND_DATA RECEIVED DATA_BIT_6 23 UALID_GAP_NO_DATA RECEIVED DATA_BIT_24
286. ol the TCR1 counter the TCR2 input pin frequency and the TCR2 counter See the Clock Control Script Command section for information on how to set the clock period The set_cpu_frequency script command has been deprecated Instead use the set_clk_period script command described in the Clock Control Script Command section A message is generated when this command is used This message can be disabled from the Message Options Dialog Box write_psck Val This command writes the prescaler clock source bit Only 0 and 1 are allowed values A 1 selects the system clock divided by 4 A zero selects the system clock divided by 32 write_div2 Val This is available in TPU2 mode only Writes the divide by 2 control bit Only 0 and 1 are allowed values A 1 selects the system clock divided by 2 and bypasses the prescaler A 0 selects the clock source specified in the PSCK bit write_tcrl_prescaler Val This command writes the TCR1 prescaler Valid Val values are 0 1 2 or 3 A 0 causes a division by 1 no prescaler A 1 causes a division by 2 A two causes a division by 4 A 3 causes a division by 8 write_psck 1 write _div2 0 Available in TPU2 mode only write_tcrl_prescaler 2 The two commands in this example set the TCR1 counter to increment at 1 0486 MHz assuming the CPU clock is set to 16 778 MHz write _t2cg Val Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 93 6 Script Commands
287. on Floating point parameters are specified using floating point notation and strings are specified using string notation Hexadecimal and decimal are fully interchangeable Multiple Target Scripts In a multiple target environment it is generally best to have just a single script file in the first target core found in the project Script commands executed in this target core affect specifically that core For example the following script command will affect just this first target core write_reg32 0x400 REG PC write_chan_hsrr TEST_CHAN 7 So how can scripts control other targets cores besides the default one with which the script file is associated For a script to operate on a specific target core the target name is prepended to the script as follows lt TargetName gt lt ScriptCommand gt The specific target for which a script command will run is specified as shown above eTPU_B write_chan_hsrr LAST CHAN 1 wait_time 10 verify_mem u32 ETPU_DATA_SPACE SLAVE_SIGNATURE_ADDR OxfffffF DATA TRANSFER_INTR_SIGNATURE eTPU_B verify_data_intr LAST_CHAN 1 eTPU_A verify_data_intr LAST_CHAN 0 In this example a host service request is applied to target eTPU_B Ten microseconds later script commands verify that the host service request generated a data interrupt on eTPU_A but not eTPU_B Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 41 6 Script Commands Files 6 5 2 Script Di
288. on Previously matches always occurred based on a greater than or equal logic This match on equal allows the user to schedule a match further out in the future because using this feature the concept of past events is dropped All events are effectively considered to occur in the future This field is displayed in the Channel window Setting the TPU Mode The simulator debugger automatically sets the TPU mode when the source microcode files are parsed The type command is located and the appropriate TPU mode TPU1 TPU2 or TPU3 is set based on the values of this field The simulator debugger also supports a script command described in the TPU Bank and Mode Control Script Commands section for setting the TPU mode Use of this command is highly discouraged since there are subtle differences among the TPU1 TPU2 and TPU3 that the TPU assembler hides from the user Support for TPU3 Version 2 1 of simulator debugger supports the TPU3 The following is a list of new and supported features of the TPU3 Enhanced TCRI prescaler TCR2 pre divider prescaler TCR2 controllable clock edge rising falling or both The prescaler options listed above are accessible using script commands described in the TPU Clock Control Script Commands section CPU32 Simulation Engine Target The CPU32 is sold on a number of Freescale microcontrollers including the very popular 68332 The CPU32 Simulation Engine can be used both in stand alone mode and in
289. on Unit Window ter1 ME tcr2 6626 a 6166 diob 0901B4 sr 1A99 ert 1EAF p 66 68 6668 dec F link 8 chan D A Bus 6669 B Bus 6666 Result 6668 BRANCH PLA FLAGS clr Flag2 clr Flagi SET clr Flag6 SET clr HSQ1 clr MRL SET HSQ6 clr TDL clr PSL clr LSL clr PIN CS GE CO PN This window displays the information associated with the microengine registers and the branch PLA flags The A bus source B bus source and result before any shifting are also displayed The ERT register is that of the active channel An important consideration is that the branch PLA flags are for the most part latched on a time slot transition Therefore they do not necessarily match the values displayed in the channel windows The following list shows those branch PLA flags that may change during a channel service routine The four execution unit flags Z C N and V are latched whenever the CCL is specified on an AU subcommand The Pin State Latch PSL gets latched two microinstructions after the CHAN_REG is written FLAG2 FLAGI and FLAGO are always input directly to the branch PLA They are not latched at all Two micromstructions after the CHAN_REG is changed these flags reflect the new channel When MtDt is in TPU2 or TPU3 mode the FLAG2 flag and PIN branch conditional are displayed FLAG2 is an additional TPU2 flag similar to the existing FLAG and FLAGO Reference Manual C 1994 2015 ASH WARE D Target
290. opment Tool page 125 9 Functional Verification 9 1 Data flows between the eTPU and the CPU via interface registers Data flow verification provides the capability of verifying this data flow Pin transitions are generated by the eTPU or by external hardware Pin transition verification capabilities allow the user to verify this pin transition behavior Code coverage provides the capability to determine the thoroughness of a test suite Code coverage verification allows the user to verify that a test suite thoroughly exercises the code A Full Life Cycle Verification Perspective The following describes a typical software life cycle Initially a set of requirements is established Then the code is designed to meet these requirements Following design the code is written and debugged A set of formal tests is then developed to verify that the software meets the requirements The software is then released Now the software enters a maintenance stage In the maintenance stage changes must be made to support new features and perhaps to fix bugs Along with this the formal tests must be modified and rerun Then the software must be re released This life cycle can be described as having three stages development verification and maintenance All of these three stages are supported The IDE and GUI are primarily of interest in the initial development phase Verification involves developing a set of repeatable and automated tests that tha
291. or by the EAC decrementing TPR MSCNT Assembly This runs the active target until a single assembly instruction occurs If instructions occur DevTool continues to run until stopped by selecting the Stop submenu in the Run menu Assembly N This runs the active target until a user specified number of assembly instructions occur A dialog box opens allowing specification of the desired number of assembly instructions If no assembly instructions occur simulator debugger continues to run until stopped by selecting the Stop submenu in the Run menu Help This accesses this help screen 17 3 Running Goto Cursor This runs simulator debugger until an instruction associated with the current cursor location is about to be executed or a breakpoint is encountered A source code window must be Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 265 17 Menus active for this command to work Goto Time This opens the Goto Time dialog box Runs simulator debugger until the specified time or until a breakpoint is encountered Goto Time Fast This behaves exactly like the Goto Time submenu except the goto time dialog box is not opened Instead the previously specified Goto Time options are used Go This causes simulator debugger to execute indefinitely simulator debugger executes until a breakpoint is encountered or until the user terminates execution by selecting the Stop submenu in the Run menu Stop
292. oto addr_0x978 flush FormatEl1 4 547 548 unsigned int24 bitIndex 549 unsigned int24 filterWord 550 ifdef _ETEC__ 551 bitIndex _ bit_n_update 0 Data B Bits23_0 amp 15 1 0 551 094C OxBFEFFB80 ram p_23_0 channel int24 0x1 FormatB2 4 551 0950 O0x0C380BFA alu a p amp OxF FormatA3 4 1994 2015 ASH WARE Inc page 136 Multi Target Development Tho Reference Manual 9 4 9 Functional Verification 551 0954 Ox3F3F1FFD alu sr u24 0 1 lt lt a FormatB6 4 After the prepended source code line number each opcode line has coverage status shown inside brackets followed by code address opcode or entry point and disassembly The coverage status can be one of the following not executed at all X fully executed both paths taken if branch T only branch true path executed F only branch false path executed I inferred entry point coverage Note if the non covered listing option is specified and the module has been fully executed the result is an empty output file For eTPU targets an additional flag option can be applied that causes entry table items to be ignored no disassembly for all mode all entry source and disassembly filtered for non covered mode Regression Testing Automation Regression Testing supports the ability to launch the simulator debugger from a DOS command line shell Co
293. ottom of the IDE See the IDE Options Dialog Box section for information on enabling this feature Goto Until Angle This sets the active target to go to an absolute simulation angle The simulation angle is initially set to zero The simulation angle is reset to zero via the Run menu by selecting the Reset submenu Note that if the desired stop cycle and angle has already been traversed then the Cycles field is ignored and the simulation is halted the next time the specified angle is traversed in either the current or next cycle Goto Current angle Plus page 242 Multi Target Development T9 1994 2015 ASH WARE Inc Reference Manual 16 Dialog Boxes This sets the additional angle to which the active target will be run The angle to which the active target will run is the current angle plus the specified delta angle Help This accesses this help window OK This closes the Goto Angle dialog box and runs the simulator until the simulator is at or beyond the specified angle in the active target Cancel This closes the dialog box without saving any changes 16 5 IDE Options Dialog Box The following describes the IDE Options dialog box All Targets Settings The following settings are for all targets Change the simulator de bugger Wide Font Changes the fonts used by all the windows Update Windows While Target is Running This specifies whether the windows are continually updated as target runs The window update generally tak
294. ould be extrinsically mapped to a CPU32 across a BDM port The access would be transferred Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 15 1 Overview 1 1 page 16 Multi Target Development Tod across the BDM port and would actually occur in the CPU32 s address space Intrinsic exposure is less powerful but is supported by all targets A target that cannot redirect a memory access to another target is said to be intrinsic For example a CPU32 hardware such as a 68332 exposed across a BDM port is intrinsic All memory accesses initiated by the CPU32 must occur within the address space of that CPU32 and cannot for example be redirected to memory owned by a simulated TPU Miscellaneous Capabilities The simulator debugger has a number of additional features not yet mentioned These include project sessions source code files functional verification external logic simulation integrated timers multiple workshops a rich set of dialog boxes a menu system and an IDE with hot keys a toolbar and target status indicators On Line Help Contents The following help topics are available Overview Software Deployment Upgrades and Technical Support Version 4 30 4 00 and 3 70 through 3 00 Enhancements Supported Targets and Available Products Project Sessions Source Code Files Script Commands Files Script Commands Groups Test Vector Files Functional Verification External Logic Simulation In
295. ounter register is 1344 Output compare 5 Disable Input capture 4 ENABLE See Pulse Accumulator window for most settings See other windows for most settings Interrupt requested when TOF flag is set TCNT clock driven out OCI pin CPR 6 TCNT Capture Compare clock period is 666 256 1 ns or Fsys 4 Timer Overflow flag is clr See Output Compare and PWH windows for most settings PPR 6 PWM CNT input is 666 125 14 ns or Fsys 2 9 Bit prescaler is 0633 Bits F 9 always zero The GPT Main window displays the GPT Module Configuration Register GPTMCR the GPT Interrupt Configuration Register GPTICR the Port G Data Direction Register DDGRP the Port G Data Register PORTGP the OC1 Action Mask Register OCIM the OCT Action Data Register OC1D the Timer Counter Register TCNT the Pulse Accumulator Control Register PACTL the Pulse Accumulate Counter PACNT the Timer Interrupt Mask Registers 1 and 2 TMSK1 TMSK2 the Timer Interrupt Flag Registers 1 and 2 TFLG1 TFLG2 the Compare Force Register CFORC the PWM Control Register C PWMC and the GPT Prescaler PRESCL 15 8 2 GPT Input Captures Window 32MySim3z2 GPT IC Input Captures Capture D Edge ICH both Ic3 rising Ic2 falling IC disabled DDGRP 2F Reg Val 6666 6666 6666 6666 Interrupt Output Is ENABLED Input fl Disabled Output ilo ENABLED Output HI Disabled Output lo TCTL1 TCTL2 1ED8 TMSK1 TMSK2 82B8 PORTGP F2
296. ource code window automatically arms the timer The timer can also be armed from within the timer window by clicking on the state field or placing the cursor in the state field and typing the letter AT When the target hits the start address of an armed timer the timer state changes to started When the target hits the stop address the timer state changes to finished Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 155 12 Integrated Timers MtDt then computes the amount of time it took to get from the timer start address to the timer stop address and this information is displayed in both clock ticks and micro seconds in the timer s window An overrun occurs when a timer exceeds the capacity of the timing device For the simulated timers the limitation is E96 femto seconds of simulated time This corresponds to 1E72 years of simulated time This is significantly less ominous than Y2K Virtual Timers in Hardware Targets For targets that do not support the full number of timers that MtDt supports the concept of virtual timers is introduced MtDt remembers the start and stop addresses of all 16 virtual timers The arming of any virtual timer causes a hardware timer to be assigned to that virtual timer If more virtual timers are armed than are actually supported by the target hardware s timing device then the last armed virtual timer is automatically disabled 1994 2015 ASH WARE Inc page 156 Mul
297. ouse has two purposes It is used to provide a goto time function and also is used to move the left and right cursors To get MtDt to execute to a particular point in time move the mouse to a location corresponding to that time and click the right mouse button If the selected time is earlier than the current Simulator time MtDt automatically resets before executing The simulation 1994 2015 ASH WARE Inc Reference Manual 14 The Logic Analyzer runs until the selected time is reached The second mouse function is to move the left and right cursors These cursors are displayed as blue and green vertical lines The user may move either cursor using the mouse The times or CPU clocks associated with both cursors as well as the delta between cursors are displayed in the cursor time indicators Note that the left and right cursors can also be moved using the left and right arrow keys on your keyboard This causes the cursors to snap to edges on the active waveform Cursor display and movement follow these rules Cursors may be located beyond the edge of the wave form display panel If the left cursor gets beyond the right display edge it is automatically moved back into the display If the right cursor gets beyond the left display edge it is automatically moved back into the display Cursors outside the display retain their timing association To allow the user to pick up a cursor that is not in the display the cursor is co
298. own in the picture below Note that this is a standard Windows scroll bar except that it has the additional functionality of the Home and End keys These keys move the view to the start or end of the simulation Home PageLeft PageRight End ShiftLeft Drag ShiftRight The vertical scroll bar provides the functionality shown in the picture below This provides the user with the ability to scroll through the 30 available nodes that the Logic Analyzer supports ShiftUp PageUp Drag PageDown ShiftDown 1994 2015 ASH WARE Inc page 166 Multi Target Development Tho Reference Manual 14 9 14 10 14 11 14 12 14 13 14 The Logic Analyzer Display Pane Boundary Time Indicators The left and right time indicators show the time associated with the left most and right most visible portions of the display pane The display pane can be changed so that a different section of the waveform is in view For example use the mouse to drag the current time by depressing the left mouse button over the current time indicator Holding the left mouse button down move the mouse over the right time indicator the release the left mouse button Data Storage Buffer Start Indicator The data start indicator shows the time associated with the very first data in the buffer This time indicator generally shows zero because the buffer can usually hold all the previously saved pin transition data But occasionally the buffer over
299. perating normally TPURAM array is accessible at the Supu priviledge level TPURAM array base address is 666666606 TPURAM array is Disabled TRAMBAR 6661 ADDR RAMDS The TPU Emulation RAM window displays the TRURAM Module Configuration Register TRAMMCR and the TRURAM Base Address Register TRAMBAR page 220 Multi Target Development T9 1994 2015 ASH WARE Inc Reference Manual 15 Operational Status Windows 15 7 2 TPU Main Window 32 MyBdm32 TPU Main op x TPUNCR STOP F F TPU Module is operating normally TCRIP E D TCR1 prescaler divides by 1 TCR2P C B TCR2 prescaler divides by 1 EW A A TPU executes out of standard mask ROM T2CG 9 9 TCR2 pin used as clock source for TCR2 STF 8 8 TPU is operating normally SUPU 7 7 TPU SZU registers access at Supu priviledge level PSCK 6 6 Clock input to the TCR1 input is the system clock 32 IARB 3 6 TPU interrupt arbitration priority 6 l TCR1 counter clock period is 666 603 8 micro seconds l TCR2 counter clock period is micro seconds l The TCR2 counter clock source is the TCR2 input pin divided by 1 TICR 66066 CIRL 8 Channel interrupt request level is 6 CIBU 7 4 Channel interrupt base vector is 6 interrupt vector is 6x66 plus channel number The TPU Main window displays the TPU Module Configuration Register TPUMCR and the TPU Interrupt Configuration Register TICR 15 7 3 TPU Host Interface Window
300. pin The default is to verify all the pins in the ebv file or bv file if an old style behavior data file is loaded but once one of these script commands is specified then each pin to be verified must be specified with a set_ebehavior_pin_tolerance script command The lt pin name gt argument is the name provided in the vector file through the node command or is the default name of the pin The only available time tolerance mode currently available is EBV_ABSOLUTE this means that pin transition times in the gold file will be compared directly to the pin transition times that occur in the current simulation run taking into account the offset and tolerance The time offset in microseconds is an adjustment made to pin transition data in the gold file before comparing to the simulation pin transition time For example if additional code in the initialization of an eTPU function has caused it to start outputting a signal 2us later than previously then a time offset of 2us can be specified and a smaller time tolerance used in the comparison The time offset can be positive or negative The time tolerance controls the maximum amount of difference between the master gold file pin transition time and the simulation pin transition time before a behavior verification error is thrown Behavior verification throws an error if the 1994 2015 ASH WARE Inc page 78 Multi Target Development Tod Reference Manual 6 6 19 6 Script Commands Files
301. piped to trace files for post processing But it is also possible to view this information in the watch window using the following command AshTimer FormatString Where the format string matches exactly a Print Action Command s format string from within the source code See the Print Action Command section for more information on how to instrument your code A list of the available print action command strings is available for selection is in the Insert Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 179 15 Operational Status Windows Watch dialog box 15 1 4 Local Variable Windows page 180 Multi Target Development Tho 52 MyBdm32 Local Variables OF x Function watchExample in watchExample c a data 2064318671 Ox7 7777777 cnt e 3 THREE packet Bx2ff54 packet size 13 G T packet butter 6x26632 ABCDEFGHI JKLH xpacket butter 65 Aa c 78 Hr register D3 i 13 G T register D2 The Local Variables window automatically displays all local variables in the current context along with their current values Variable names are listed in a column on the left hand side of the window Values are displayed in a matching column on the right hand side The displayed format is relevant to the variable type Additionally if the variable is assigned a register the register is output Based upon type variables are automatically expanded For example if a variable is of
302. placed with its two inputs coming from the eTPU A s channel 16 output pin and the MC33816 s OA_1 pin The output of the OR gate drives eTPU A s channel 11 s input pin Automatic and Pre Defined Define Directives ASH WARE Specific Script It is often desirable to conditionally parse or not parse portions of a script command file depending on whether or not it is in the ASH WARE development environment The following define is automatically prepended when parsing any script file and therefore can be used to control the aforementioned conditional parsing define _ASH WARE SCRIPT 1 This define is prepended prior to parsing every script file ifndef _ASH WARE SCRIPT_ void RunEngineDemo endif The code above causes the function declaration to be ignored by the ASH WARE parser Tool Specific Scripts With the introduction of the new Development Tool in some cases it may be helpful to have tool specific behavior This is achieved using the Development Tool define as follows define _ASH WARE DEV_TOOL_ 1 This define is prepended prior to parsing every script file in the Development Tool but NOT in the legacy Mtdt tool When running as a hardware debugger rather than a simulator the following define allows differentiation between the simulator and debugger define _ASH WARE DEV_TOOL_ 1 The following is an example usage of simulator debugger specific scripting ifdef ASH WARE HARDWARE DEBUGGER _ T
303. put is the eTPU s channel 5 output pin output pin s start at index 32 so channel 5 s is at 37 The channel drives the TCR2 pin which is at index 64 place_buffer 32 5 64 epp XMIT RECV Example 2 Driving a Pin with the Logical Combination of Two Pins In the following multi drop communications example TPU channel 5 is a communications channel output TPU channel 7 is used as a gate to enable and disable the output Channel 1 is the communications input An idle line is low An AND gate is instantiated using the place_and_gate X Y Z script command The gate pin causes an idle LOW state on the input by going low By going high the gate pin causes the state on the output channel to be driven unto the input channel place_and_gate 5 7 1 TPU 1994 2015 ASH WARE Inc page 152 Multi Target Development Tho Reference Manual 11 External Circuitry In the following multi drop communications example eTPU channel 5 s output pin is a communications channel output eTPU channel 7 s output pin is used as a gate to enable and disable the output eTPU Channel Us input pin is the communications input Since the eTPU s output pins start at 32 a 32 is added to both arguments to designate these as the output pins An idle line is low An AND gate is instantiated using the place_and_gate X Y Z script command The gate pin causes an idle LOW state on the input by going low By going high the gate pin causes the state on the output ch
304. r either by individual pin or globally Currently there is one tolerance type EBV_ABSOLUTE This means the absolute time of each transition in the master file is compared to the absolute time of the matching transition in the current simulation run In the comparison process first the offset is is applied to the master file transition time and then the difference between the two times is calculated If the absolute value of this result is less than the configured tolerance the behavior is considered valid and simulation continues If it is greater than the tolerance a behavior error is thrown this may or may not trigger a pop up error dialog depending upon the IDE messages configuration Last individual pins can be disabled from behavior verification with the disable_ebehavior_pin script command disable_ebehavior_pin PWM_C With enhanced behavior verification an ebv file can be created while simultaneously using another one for verification This could be handy in the sense that after running a simulation session the user has a new current pin transition file it could be used as an input into other tools or if verification is successful it could be copied as the new gold or master file create and verify simultaneously create_ebehavior_file Powertrain_current EBV run_ebehavior_file Powertrain_gold EBV simulation finish behavior verification close_ebehavior_file close EBV being saved
305. r Files Overview Test vector provides a complex test vector generation capability Simulated signals similar to those found in a typical environment can be generated Test vector files are used for forcing of high or low states at the device s input or I O pins Note that this capability is NOT available for the CPU simulation engine It is helpful to compare test vector files to script commands files Roughly test vector files represent the external interface to the device while script commands files represent the CPU interface Test vector files are treated quite differently from script commands files While script commands file lines are executed sequentially and at specific simulated times test vector files are loaded all at once Test vector files are used solely to generate complex test vectors on particular simulator debugger nodes As the simulator debugger executes these test vectors are driven unto the specified nodes Loading and Editing the Test Vector File The test vector file is loaded into the simulator debugger from the Files menu by selecting the Vector Open sub menu The test vector file is an ASCII file that the user can edit with any text editor The configuration window shows the currently loaded test vector file It is preferable to keep the test vector file in the same directory as the Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 115 8 Test Vector Files project f
306. r Unit Windows 1994 2015 ASH WARE Inc page 172 Multi Target Development Tho Reference Manual 15 Operational Status Windows TPU Main Window TPU Host Interface Window TPU Parameter RAM Window General Purpose Timer Windows GPT Main Window GPT Input Captures Window GPT Output Compares Window GPT Pulse Accumulation Window GPT Pulse Width Modulation Window Counter Timer Module 4 and 6 Windows CTM4 CTM6 Bus Interface and Clocks Window CTM4 CTM6 Free Running Counter Submodule Window CTM4 CTM6 Modulus Counter Submodule Window CTM4 Double Action Submodule Window CTM4 Pulse Width Modulation Submodule Window CTM6 Single Action Submodule Window CTM6 Double Action Submodule Modes Window CTM6 Double Action Submodule Bits Window Miscellaneous Windows Real Time Clock Window Parallel Port I O Submodule Window TouCAN Windows TouCAN Main Window TouCAN Buffers Window Queued Analog to Digital Converter Windows QADC Main Window QADC Ports Window QADC Channels Window CPU32 Simulator Specific Windows The following window is available for CPU32 Simulator targets CPU32 Simulator Configuration Window CPU32 Simulator Busses Window CPU32 Simulator Interrupt Window Universal CPU32 Windows Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 173 15 Operational Status Windows The following windows are available for both the CPU32 hardware and the CPU32 Simulator targets CPU32 Regis
307. r a pin transition occurs information regarding this transition is stored in this buffer which is also used to draw the signals in the logic analyzer window This pin transition information can be selectively recorded to file using the create_ebehavior_file filename ebv add_ebehavior_pin lt pin name gt and close_ebehavior_file script commands also see Enhanced Pin Transition Behavior Verification below Deprecated Pin Transition Behavior Verification Legacy bv pin transition data files can still be used by the new enhanced behavior verification bv files can no longer be generated The master buffer can be loaded only with pin transition behavior data from a previously saved file This file forms a behavioral model of the source microcode Changes can be made in the source microcode and the changed microcode can be verified against these behavioral models This file is loaded using the read_behavior_file filename bv script command There are two options for verifying pin transition behavior against the previously generated behavioral model The first option is to continuously check the running pin transition behavior buffer against the master pin transition behavior buffer This is selected by the enable_continuous_behavior script command that follow a behavior file load The second option is to perform a complete check of the running buffer against the master buffer all at once This is selected using the verify_all_behavior scr
308. r into the next state The timer can also be forced into a specific state by typing the first letter of the desired state The Start Address and Stop Address fields are to the right of the State field These fields contain the addresses that when accessed by the target cause the state to change For instance a timer in the armed state changes to the started state when the start address is executed Then when the stopped state is executed the timer progresses to the finished state The This Ticks and the Last Ticks fields are to the right of the Stop Address field These fields indicate how many clock ticks of the target have occurred for any timer calculation Why are these split into two fields This allows the last calculated timing to be retained while a new timer calculation is underway When a timer is re armed the This Ticks field goes blank while the Last Ticks field retains the previous value To the right of the Last Ticks field is the Last Time field The Last Time field is identical to the Last Ticks field except that the timer result is displayed in micro seconds instead of Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 191 15 Operational Status Windows 15 1 11 page 192 Multi Target Development Tho clock ticks Note that the Last Ticks and This Ticks fields use the target s current clock period in the calculation Only the start time and stop time are retained by the timers This means tha
309. r is apparently not documented MtDt allows the user to specify whether the parameter RAM is cleared to all zeros or remains unchanged after a reset This is specified in the Reset Options dialog box page 210 Multi Target Development TAS 1994 2015 ASH WARE Inc Reference Manual 15 Operational Status Windows 15 4 CPU32 Specific Windows The following windows are available in the simulator debugger 15 4 1 CPU32 Simulator Configuration Window MySim32 Configuration _ O x Files Project E hMtdt TargetCode Cpu32_ Test1 1Sim32 MtDtProject MtDt Build E Mtdt Gui TESTFILES BuildScripts 1Sim32 MtDtBuild Source Code main e68 Script No File Open Script Report No File Open Script Startup No File Open Auto Build No File Open Verification Script Failures 66600666 Files The name of the project file is displayed See the Project Sessions chapter for a detailed explanation of this capability The name of the MtDt build script file is displayed See the Building the Target Environment chapter and the MtDt Build Commands File section for detailed explanations of the available capabilities and format of this file The names of the open source code executable image primary script primary script report and startup script files are displayed These files are listed relative to the path of the open project file The auto build file name is displayed The auto build file allows direct building of the executable imag
310. rOffset BitOffsetFromMSB BitSize Val verify global_bits24 AddrOffset BitOffsetFromMSB BitSize Val verify global_bits16 AddrOffset BitOffsetFromMSB BitSize Val verify _global_bits8 AddrOffset BitOffsetFromMSB BitSize Val These script commands allow the writing and verification of bitfields within the specified unit The bit offset is from the MSB of the unit For example to set a _Bool bit that is in the LSB of an 8 bit unit the script command would be set _Bool at LSB of 8 bit unit to 1 write _global_bits8 0x10 7 1 1 page 84 Multi Target Development Tod 1994 2015 ASH WARE Inc Reference Manual 6 Script Commands Files 6 6 25 eTPU Channel Data Script Commands write_chan_data32 ChanNum AddrOffset Val write_chan_data24 ChanNum AddrOffset Val write_chan_datal6 ChanNum AddrOffset Val write_chan_data8 ChanNum AddrOffset Val verify chan_data32 ChanNum AddrOffset Val verify chan_data24 ChanNum AddrOffset Val verify chan_datal6 ChanNum AddrOffset Val verify chan_data8 ChanNum AddrOffset Val These commands write channel ChanNum s data at address AddrOffset to value Val or verify that the data at the specified parameter RAM memory location is value Val Note that 32 bit numbers must be located on a double even address boundary 0 4 8 that 24 bit numbers must be located on a single odd boundary 1 5 9 that 16 bit accesses must be located on even boundaries
311. rd is written with a 32 bit value OxC6E2024A hex The written value is then verified as 32 24 and 8 bit sizes Note the ETEC eTPU C Compiler automatically generates all needed engine variable address data into the auto defines file as a series of macros no explicit user effort is required Bitwise access to engine space parameter RAM is supported with a set of matching functions to those above write_engine_bits32 AddrOffset BitOffsetFromMSB BitSize Val write_engine_bits24 AddrOffset BitOffsetFromMSB BitSize Val write_engine_bits16 AddrOffset BitOffsetFromMSB BitSize Val write_engine_bits8 AddrOffset BitOffsetFromMSB BitSize Val verify _engine_bits32 AddrOffset BitOffsetFromMSB BitSize Val verify _engine_bits24 AddrOffset BitOffsetFromMSB BitSize Val verify _engine_bits16 AddrOffset BitOffsetFromMSB BitSize Val verify _engine_bits8 AddrOffset BitOffsetFromMSB BitSize Val These script commands allow the writing and verification of bitfields within the specified unit The bit offset is from the MSB of the unit For example to set a _Bool bit that is in the LSB of an 8 bit unit the script command would be Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 87 6 Script Commands Files 6 6 28 6 6 29 page 88 Multi Target Development Tod set _Bool at LSB of 8 bit unit to 1 write_engine_bits8 0x10 7 1 1 eTPU Channel Function Mode Script Command
312. re still black Since this is an invalid case that actually should never execute it is considered sufficient to infer coverage of entries 13 21 and 23 as long as event vector 15 is covered This is done using the following script command infer_entry_ coverage MEASURE_PERIOD_FUNC 15 13 infer_entry_coverage MEASURE_PERIOD_FUNC 15 21 infer_entry_coverage MEASURE_PERIOD_FUNC 15 23 Although there are a number of restrictions listed below that are enforced by the simulator debugger the most important restriction is not enforced Namely that this coverage by inference should only used for invalid cases where the thread exists purely as Built In Test BIT and would not in normal operation be expected to execute In fact when testing to the very highest software testing standards 100 percent event vector coverage should be achieved without the use of this script command Execution of an event vector that is covered by inference results in a verification failure The FromEntryIndex s thread and the ToEntryIndexthread thread must be the same Note when developing eTPU code using the ETEC eTPU class programming paradigm unused unexpected entries are often directed to the built in global error handler These entries thus do not show up in the user source module but rather are associated with the global error handler source code _global_error_handler sta 1994 2015 ASH WARE Inc page 70 Multi Target Development Tod R
313. rectives Define Ifdef Include The define directive Script commands files may contain the C style define directive The define directive starts with the pound character followed by the word define followed by an identifier and optional replacement text When the identifier is encountered subsequently in the script file the identifier text is replaced by the replacement text The following example shows the define directive in use define THIS CHANNEL 8 define THIS FUNC 4 set_chan_func THIS_ CHANNEL THIS_FUNC Since the define directive uses a straight text replacement more complicated replacements are also possible as follows define THIS_SETUP 8 4 set_chan_func THIS_SETUP There are a number of automatic and predefined define directive as described in the like named section The include lt FileName h gt directive Allows inclusion of multiple files within a single script file Note that included files do not support things like script breakpoints script stepping etc include AngleMode h In this example file AngleMode h is included into the script commands file that included it The ifdef ifndef else endif directives These directives support conditional parsing of the text between the directives That is all she wrote ifdef _ASH_WARE_AUTO_RUN exit print else All tests are done endif _ASH WARE AUTO RUN The above directive is commonly found at the
314. regon1ETpu ETpuSimProject C Mtdt Gui TESTFILES BuildScripts zzz_1ETpuSim MtDtBuild DemosSpc563hxx eTPU2 etpu2_code elf DemoLimitsETpu2 ETpuCommand Script Report DemoLimitsETpu2 Report Script Startup No File Open Test Vector Build No File Open No File Open Master Behavior No File Open Semaphores Semaphore Semaphore Semaphore Semaphore Free Free Free Free General The CPU frequency is displayed The eTPU executes at half of this CPU frequency in that a single eTPU instruction takes two CPU clocks to execute The CPU Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 193 15 Operational Status Windows clocks field displays the number of CPU clock ticks that have occurred since the last reset The latest thread in both steps opcode execution and NOPs and CPU clocks is displayed The execution unit activity level since reset is shown This is the total number of CPU clocks divided by the number in which the eTPU was either in a Time Slot Transition or in a thread The current execution unit address and the address to which the unit will begin executing should a return statement be encountered are displayed Interrupts The state of the Microcode Global Exception MGE1 MGE2 and the Illegal Instruction Flag ILF1I ILF2 are displayed which are both part of the ETPUMCR register Verification The state of continuous verification enabled or disabled is displayed as wel
315. ringExprString The pointer expression string pointerExprString is symbolic expression as described above but of type pointer rather than a basic type It can be a pointer to any type and is implicitly type cast to the char type stringExprString can either be a string constant or it can be of type char array or char pointer In either case write_str function like the C library function strcpy Use write_str with caution no effort is made to check that the destination buffer has sufficient space available and the resulting bug induced by such a buffer overflow can be extremely difficult to debug A key concept is that of symbol scope A variable defined within a particular function goes out of scope if that function is not being executed To get around this a script command can be set to execute when the function becomes active using the at_code_tag script command See the Timing Script Commands section for a description at_code_tag amp amp TestlHere amp amp write_val FailFlag 0 In the above example the target is run until it gets to the address associated with the source code that contains the text amp amp TestlHere amp amp Once this address is reached symbol FailFlag is set equal to zero at_code_tag amp amp Test23Here amp amp write_str PlayerBuffer Michael Jordan In this case the string Michael Jordan is written to the buffer named PlayerBuffer If Reference Manual
316. rmat and provides more options on how master file pin transitions are compared to transitions in the current simulation With the original behavior verification capability anything other than an exact match clock cycle for clock cycle was considered a failure The reality is that often times even very small code changes can result in a signal being shifted by a clock cycle or two which previously would result in failure Enhanced behavior verification provides options for controlling the tolerance used in comparisons so that small changes that are functionally correct can pass verification Additionally master file pin transition data can now be viewed in the Logic Analyzer Window making it easier to track down problems when a failure does occur The first step in making use of pin transition behavior verification is to create a master file also called a ebv file for its default extension These enhanced behavior verification files are text and in comma separated value CSV or csv format All behavior verification is controlled from the scripting environment to create a master file use the create_ebehavior_file filename ebv script command It must execute at simulation time zero but after any vector file load or pin buffer placements save off all pins create_ebehavior_file Engine EBV By default all pins are saved to the ebv file On the TPU this is all 16 channel pins and the TCR2 pin On the eTPU this is all 32 channel inpu
317. rt file is written only when the primary script commands file is parsed Open Startup Script Commands File Dialog Box This dialog box specifies which startup script commands file is open Only one startup script commands file may be opened for each target at one time This file is very similar to the primary script file Almost all script commands that are supported in the primary script file are also supported in the startup script file The primary difference between primary and startup script command files is when they are executed Startup script command files are executed only when MtDt resets a target Primary script files execute as the target executes Startup script files do not support specification of a report file name The report file name generated for the startup script is always the same as the startup script file name except page 238 Multi Target Development Td 1994 2015 ASH WARE Inc Reference Manual 16 Dialog Boxes the file suffix is changed to report Open Test Vector File Dialog Box This dialog box is accessed via the Files menu by selecting the Vector Open submenu It is only available when a TPU simulation target is active This dialog box specifies a test vector file to be loaded The entire file is loaded at once Loading additional files causes existing test vectors to be removed This dialog box allows full specification of drive directory and filename The default filename is VECTORS Vector and the def
318. rted Supported comparator operators are gt and lt gt and lt Greater than and less than operations follow the same rules as the stremp standard library function The extended version of this command verify_str_ex also support a length specifier len Think strncmp where the comparison acts only on the first len characters and the remainder are ignored at_code_tag StringTest1 verify _str somePtr Hello World In the example above the target is run until it gets to the address associated with the source code that contains the text StringTest1 Once this address is reached the ASCII values are read until the terminating character a byte of value zero is reached The resulting string is compared case sensitively with the string Hello World If the two strings are not equal a verification error is generated at_code_tag StringTest2 verify_str_ex somePtr lt Hello World 5 In the example above the first five letters of two strings are compared and verification error results unless somePtr is less than or equal to Hello See the Global eTPU Channel variableAccess section for information on accessing eTPU channel variables using the format shown below lt lt chan num name gt lt function var name gt System Script Commands system commandString verify system commandString returnVal These commands invoke the operating system
319. rted microcontroller versions that contain an eTPU Note that Freescale constantly develops new microcontroller derivatives that contain eTPU s The following is a list of all supported version at the time of this writing JPC SPC eTPU 2 s JPC563M60_1 SPC563M54_0 SPC563M60_0 SPC563M64_0 MPC56xx Family eTPU 2 s MPC5632M_0 MPC5633M_0 MPC5634M_0 MPC5674_0 MPC5674 2 MPC55xx Family MPC5534_0 MPC5553_A MPC5554_B MPC5534_A MPC5565_0 MPC5566_0 MPC5567_0 MCF52xx Family MCF5232_0 MCF5233_0 MCF5234_0 MCF5235_0 MCF5271_0 Enter MtDt Build Script define The define that is defined here is passed nto the MtDt Build script which is useful say for specifying an eTPU s sub version MPC5554_B MPC5553_4 MPC5534_0 MPCS534_A MCF5232_0 MCF5233_0 MCF5234_0 MCF5235_0 etc See file zzz_eT puVersions Dat for a Est of the latest supported micros This Sdefine is saved in the peogect file but is overnden if an MtDt Bud Script Bdefine is passed on the command line MPC5567_d CE zl mm In order for any changes to take affect the simulator debugger must be closed and re opened de fine Used to specify a define that is passed to the MtDt Build Script Note that this setting is overridden if this same define is passed on the command line when the simulator debugger is launched See the Command Line Parameters section Related Topics Reference Manual C 1994 2015 ASH WARE D Targ
320. s 16 2 Simulation targets From the Save Coverage Statistics Dialog Box a coverage filename is specified An overview of the coverage statistics since the last reset on both a project and a file by file basis is written to this file Auto Build Batch File Options Dialog Boxes The Auto Build Batch File Options dialog box provides the capability of building the executable image file source code from within MtDt This dialog box is opened from the Files menu by selecting the Auto Build Open submenu The auto build batch file is a console window batch file In this batch file the user puts the shell commands that build the executable image from the source code MtDt executes this auto build batch file The following describes the various capabilities accessed from within the Auto Build Batch File Options dialog box Edit Window From within this window the user can edit the currently selected auto build batch file Edits to this file are saved only if the user hits the OK button the OK Build button or the Build button If the Cancel button is hit or if a new file is selected before one of these buttons is hit then all edits are lost OK Button This saves edits makes the currently selected auto build batch file the default and closes the Auto Build Batch File Options dialog box OK Build Button This saves edits makes the currently selected auto build batch file the default and closes the Auto Build Batch File Options d
321. s The following script help topics are found later in this section Script Commands File Format Script Command Groups Multiple Target Scripts Automatic and Predefined define Directives Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 35 6 Script Commands Files 6 1 page 36 Multi Target Development Tod Predefined Enumerated Data Types Enhanced Scripting capabilities variables loops etc Types of Script Commands Files The different types of script commands files are as follows The Primary Script Commands Files ISR Script Commands Files The Startup Script Commands File The MtDt Build Commands File It is best to just have a single primary script command associated with just one target core Alternatively in a multi target core simulation each target core can have it s own primary script commands file ISR script commands files are associated with interrupts Although each interrupt may have only a single associated ISR script commands file it is important to note that each script commands file may be associated with multiple interrupts The simulator debugger can have only a single active MtDt build batch file Similarities to the C Programming Language The script commands files are intended to be a subset of the C programming language In fact with very little modification these files will compile under C The ETEC cpp exe Preprocessor The ETEC C PrePprocessor
322. s cores are treated as slave devices and are stepped however much is required in order to cause the active target core s simulation to progress by one step simulator debugger makes use of the active target core when a new executable code image is loaded Clearly the user needs to have the ability to select a new executable image into a single specific target But which target should this be The simulator debugger automatically selects the Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 157 13 Workshops active target core as the one into which the executable code image is to be loaded To associate workshops with targets see the Workshops Options Dialog Box section In that section there are descriptions of putting workshop buttons on the toolbar renaming workshops or automatically giving a workshop the same name of its associated target and associating workshops with targets When a target is assigned to a workshop the windows associated with that target are automatically made visible within the assigned workshop It is often desirable to override this either to make individual windows visible in multiple workshops or to remove window from specific targets See the Occupy Workshop Dialog Box section for a detailed description of how this is done page 158 Multi Target Development T9 1994 2015 ASH WARE Inc Reference Manual 14 The Logic Analyzer 14 The Logic Analyzer The Logic Analyzer displays no
323. s or gates xor gates etc These external logic gates are placed using external logic commands within script commands files These external logic gates are evaluated on a one pass per per instruction cycle basis and there is no attempt to elegantly handle a stable situations For instance an inverter that has both it s input and output connected to the same pin would simply toggle once every instruction cycle There are a number of limitations to the Boolean logic There are only two logic states one and zero The logic is simulated with a single pass per instruction cycle Alloutput states are calculated before they are written and therefore all calculations are based on the pre calculated states Thus it takes multiple passes for state changes to ripple through sequentially connected logic All Boolean logic inputs and outputs must be input output or I O pins Behavior of pins connected to Boolean logic outputs and also driven by test Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 151 11 External Circuitry vectors is undefined Example 1 Driving a Pin with another Pin In the following script command the output pin which drives the buffers input is the TPU s channel 5 I O pin The input pin driven by the buffer s output is the TCR2 pin Note that the TCR2 s pin is at index 16 place_buffer 5 16 TPU In the following script command the output pin which drives the buffers in
324. s is useful for identifying the specific areas in which the microcode behavior has changed This command only applies to verification with old 1994 2015 ASH WARE Inc page 76 Multi Target Development Tod Reference Manual 6 Script Commands Files style bv files Enhanced behavior verification automatically runs in continuous mode disable _continuous_behavior This command disables continuous verification of pin transition behavior against the master pin transition behavior buffer Note that pin transition behavior is still recorded in the pin transition behavior buffer This command only applies to verification with old style bv files Enhanced behavior verification automatically runs in continuous mode resize _pin_buffer lt NumPinTransitions gt This command resizes the pin transition buffer The default size is 100K transitions resize _pin_buffer 500000 In this example the pin transition buffer size is changed such that it can hold 500K pin transitions This script command should only be executed at time zero Note that resizing the pin transition buffer can have serious affects on performance For instance it can cause a long delay when the simulator debugger is reset It can also significantly slow down the logic analyzer redraw rate such that the simulation speed is bound by the redraw rate Simulation speed reductions can be obviated by hiding or minimizing the logic analyzer while the simulator debugger runs such
325. s one state for none of the spark plugs firing state FIRE4 1000 state FIRE3 0100 state FIRE2 0010 state FIRE1 0001 state NO_FIRE 0000 SET THE TEST VECTOR BASE FREQUENCY 1 In order to have a convenient relationship between time and degrees an engine revolution is made to be 3600us such that one degree corresponds to 10us Thus a convenient test vector time step period of 10us is chosen frequency 1 period 1 10us 0 1MhzZ Frequency is expressed in MHz this is a modification of a previous version of the User Manual frequency 0 1 CREATE DEFINE THE SYNCH WAVE FORM This generates a one degree 10us pulse every 360 degrees 3600us wave SYNCH synch_pulse 1 synch_wait 364 end CREATE DEFINE THE SPARK WAVE FORM Each spark is equally spaced every 1 2 revolution which is 180 degrees 1800us Bach spark plug triple fires and each fire lasts one degree 10us In addition there is a 17 degree 170us lag of this wave form relative to the synch wave form wave SPARKS no_fire 17 This creates a 17 degree lag Enclose the following in a bracket to generate a loop The first plug fire cycle lasts five degrees 50us The spark plug fires three times firel 1 no fire 1 firel 1 no_fire 1 firel 1 The delay between fire cycles is 180 degrees less the five degree fire cycle 180 5 175 degrees no_fire 175 The third plug fires next fire3 1 no fire 1
326. s the coverage Statistics Statistics for individual files are listed as well as a cumulative file for the entire loaded code The verify_file_coverage and verify_file_coverage_ex commands are used as part of automation testing of a specific source file The instPct and braPct parameters are the minimum required branch and coverage percentages in order for the test to pass The entPct parameter is the minimum require entry percentage and is available only in the eTPU simulator These parameters are both expressed in floating point notation The valid range of coverage percentage is zero to 100 Note that for each branch instruction there are two possible branch paths the branch can either be taken or not taken Therefore in order to achieve full branch coverage each branch instruction must be encountered at least twice and the branch must both be taken and not taken The verify_all_coverage and verify_all_coverage_ex are similar to the verify_file_coverage commands except these commands focus on the entire build rather than specific source code modules As such they are less useful as a successful testing strategy will focus on specific modules rather than on the entire build 1994 2015 ASH WARE Inc page 68 Multi Target Development Tod Reference Manual 6 Script Commands Files Note that this capability is also available directly from the file menu wait_time 100 verify file coverage toggle uc 92 5 66 5
327. sed as part of the automated testing of the eTPU simulator echo Running ALUOP B6 Tests eTpuSimulator exe pAutoRun ETpuSysSimProject d_TEST_ALUOP_B6 if ERRORLEVEL NEQ 0 goto errors In the primary script file that is part of this project the following command is used to load the executable file that is specific to this test ifdef TEST ALUOP_B6 load_executable AluopB6 gxs endif _TEST_ALUOP_B6 TPU Target Pre Defined Define Directives The following define directives are automatically loaded and available for the simulator debugger define CFSRO U16 zi 0x0C define CFSR1 U16 Ox0E define CFSR2 U16 0x10 define CFSR3 U16 0x12 define HSQ U32 0x014 define HSQO U16 0x014 define HSQ1 U16 0x016 define HSRR U32 0x018 define HSRRO U16 0x018 define HSRR1 U16 0Ox01A define CPR U32 0x01C define CPRO U16 0x01C define CPR1 U16 0x01le Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 103 6 8 6 8 1 6 8 2 page 104 Multi Target Development Tho Script Commands Files eTPU Target Pre Defined Define Directives The following define directives are automatically loaded and available for the eTPU Simulation target define ETPU1 MPC5554 B 1 define ETPU2 MPC5554 B 2 Listing of Script Enumerated Data Types Some script commands have the following pre defined enumerated types Script FILE_
328. significantly See the Pin Transition Behavior Verification section for a description of this capability NOTE This option only exists prior to version 5 00 With 5 00 and newer behavior verification can only be controlled via scripting Timer This lists a variety of options available for timers These options are only available if a Source Code File window is selected Options include setting the timer s start or stop address to be equal to that associated with the cursor location within the Source Code File window A timer can also be enabled or disabled Watch This lists a variety of options available for a watch These options are available only if a Watches window is selected Options include inserting and removing a watch moving a watch up or down and setting the options for a specific watch Help This accesses this help screen 17 9 Help Menu The Help menu provides the following options Contents Accesses the contents screen of simulator debugger s on line help program Using Help Accesses the standard Microsoft Windows help on help program Latest Enhancements This accesses information on the enhancements added in the various versions of this software Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 271 17 Menus Technical Support This accesses information on obtaining technical support for this product About This gives general information about simulator debugger page
329. similar script command Do not use the clear_this_intr script command in the primary script commands file because the primary script commands file does not have an eTPU TPU channel context Use of timing commands within an ISR script commands file is discouraged This would be analogous to putting delays ina CPU s ISR routine Sucha delay would have a detrimental effect on CPU latency and in the case of the eTPU TPU Simulator would be considered somewhat poor form eTPU TPU channels need not have an association with an ISR script commands file 1994 2015 ASH WARE Inc Reference Manual 6 Script Commands Files There is an automatic define that can be used to determine which channel the script command is associated with This script command appears as follows define _ASH_WARE_ lt TargetName gt _ISR_ X Where TargetName is the name of the target generally TpuSim eTPU_A or eTPU_B and X is the number of the channel associated with the executing script The following shows a couple examples of its use ifdef _ASH_ WARE _TPUSIM_ISR_ print this is an ISR script running on a target TPUSIM else print this is not an ISR running on TPUSIM endi E write_par_ram _ASH WARE_TPUSIM_ISR_ 2 0x41 write_par_ram _ASH WARE_TPUSIM_ISR_ 3 8 clear _this_cisr Critical Change in Version 3 70 and Later Beginning with MtDt Version 3 70 support for the Freescale and ST Microelectronics eTPU2 forced a change in t
330. sociate targets with workshops specify workshop names and place workshop buttons in the toolbar When adding a new target association to a workshop you will be prompted to indicate whether you would like all windows belonging to that target to be made visible within that workshop It is generally desirable to select the yes or yes to all option The very first workshop is special in that all windows initially visible within this workshop This prevents windows from becoming lost To avoid confusion this workshop name is always AIL This dialog box allows you to remove a target association from a workshop In this case you will also be prompted to indicate whether you would like to remove visibility of all windows belonging to the removed target from the affected workshops On Toolbar Checking this option causes a button to appear on the toolbar that automatically switches to that workshop when depressed Workshop Name This is the name of the workshop You can either type in a new name using the keyboard alternatively a button to the left of this edit control allows you to assign the associated target s name to the workshop Primary Association This is the target that is associated with the workshop A dropdown list allows selection of any target Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 245 16 Dialog Boxes 16 7 16 8 Occupy Workshop Dialog Box The Occupy Workshop dialog box prov
331. stop_ebehavior_file stop EBV verification 1994 2015 ASH WARE Inc page 132 Multi Target Development Tho Reference Manual 9 Functional Verification When enhanced behavior verification is used with a dual eTPU simulation model an ebv file and the associated commands apply to a single eTPU engine In other words if pin transition behavior verification is to be done on each eTPU there must be a separate ebv file for each 9 3 Code Coverage Analysis Code coverage analysis is one of the verification capabilities for which an overview is given in the Functional Verification chapter There are two aspects to code coverage The first aspect is the code coverage visual interface while the second aspect is the coverage verification commands Code Coverage Visual Interface The visual interface is enabled and disabled within the IDE Options dialog box When this is enabled black boxes appear as the first character of each source code line that is associated with a microinstruction As the code executes and the instruction coverage changes these black boxes change to reflect the change in the coverage This is summarized below I A black box indicates a C source line or assembly instruction that has not been executed An orange box indicates C source line that has been partially executed A blue box indicates an assembly branch instruction in which neither branch path has been traversed A green box indicates an assembly
332. system subSystemId engineId chanNum This command configures the subsystem subSystemld to generated a link on engine engineId channel ChanNum SubSystemld is the ID for the sub system The parameter engineld programs the ETPUSSSnIR register s LENQ field and is set to DISABLED ENGINE_1 or ENGINE_2 The parameter chanNum programs the ETPUSSSnIR register s LCHAN field issue_sub_system_link subSystemId This command issues a link that originates from the sub system specified by the subSystemld field config_shared_sub_system 0 ENGINE_1 17 issue_sub_system_link 0 The above command sequence configures the shared memory subsystem to interrupt channel 17 of engine 1 and then issues a link write_chan_shared_subsystem_access_enable chanNum enableVal eTPU2 only This command enables or disables shared subsystem accesses This is done on a per channel bases in that some channels can have this enabled while others have it disabled The chanNum specifies the channel to be enabled or disabled The enableVal can either 1994 2015 ASH WARE Inc Reference Manual 6 Script Commands Files be 1 enabled or 0 disabled Note that this command is only available for eTPU2 write_chan_shared_subsystem_access_enable 4 1 In this example channel 4 is enabled for memory accesses to the shared subsystem 6 6 32 TPU Parameter Ram Script Commands write_par_ram ChanNum ParamNum Val This comman
333. t if the clock period changes during the course of a calculation these clock tick calculations will not be correct Note also that the time calculation on simulated targets does not use the clock period so this field will be correct even if the clock period is changed Background Debug Mode BDM Hardware Window 52 MyBdm32 Hardware iof x Using BDH Port Errors 66666666 Go Hode is Lock Step Is ASH WARE Hardware Yes Hardware Revison 32 65 Build A Bypass Mode is Available Bypass Mode Read is Disabled Bypass Mode Write is Disabled Jumper6 is Installed Jumper1 is Installed PLD Register Bit SET Data Bus Size Word Data Bus Wait States Clock Cycles Per Second Hex 66866666 The first field indicates to which parallel port the BDM cable is attached The BDM Port errors field gives the total number of low level communications errors encountered This field should never be greater than zero when the port communications are working properly The Lock Step field indicates if the hardware is free running or is in lock step Lock step is when the hardware is only single stepped This greatly reduces the target execution speed and generally should not be selected The Hardware Revision field gives the release number of the ASH WARE hardware Bypass mode is a special accelerated communications mode in which the normal BDM path is bypassed to speed up code download and upload The three fields indicate if the mode is available if
334. t is incremented verify_mem_u16 ETPU_DATA SPACE 0x10 Oxffff 0Ox55aa In the example above a 16 bit two byte memory at address 10h is verified to equal Ox55aa By using a mask of FFFFh the entire word is verified verify_mem_u24 ETPU_DATA_ SPACE 0x101 Oxffffff 0x555aaa In the example above a 24 bit three byte memory at address 101h is verified to equal Ox555aaa By using a mask of OxFFFFFF the entire word is verified verify_mem_u32 ETPU_DATA_ SPACE 0x20 1 lt lt 27 1 lt lt 27 In the example above bit 27 of a 32 bit four byte memory location at address 20h is verified to be set All other bits except bit 27 are ignored Related Topics See the eTPU Channel Data Script Commands section which covers both writing and verifying eTPU memory Register Write Script Commands Write register script commands provide the mechanism for changing the values of the target registers The first argument is the value to which the register will be set The second argument is a eTPU register enumerated type CPU32 register enumerated type with a definition that depends on the specific target and register width on which the script command is acting write_reg4 U4 enum REGISTERS_U4 write_reg8 U8 enum REGISTERS_U8 Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 57 6 6 7 6 6 8 page 58 Multi Target Development Tod Script Commands Files write_reg16 U16 enum REGISTERS _U16 write _reg2
335. t of XC Y Z where X is the number of cycles and Y Z is the current angle in degrees Note that determination of the engine angle relies on certain timing settings specified using the set_angle_indices script command which is described in the eTPU Time Base Configuration Script Commands section Use the ETEC CPP Preprocessor for Script Commands Files Indicates if the ETEC_CPP exe preprocessor should be used to preprocess script command files See the ETEC CPP Preprocessor section for more details eTPU and TPU Simulator Target Only The following settings are only available for eTPU and TPU Simulator targets View Coverage TPU Targets Only This specifies whether the code coverage indicators are visible within source code windows These are the color coded boxes at the far left of each line of text that is associated with an instruction These boxes indicate if the associated instruction has been executed and if it is a branch instruction if the true and false cases have been traversed Active Target Settings The following settings act only on the target that was active at the time that the dialog box page 244 Multi Target Development T 1994 2015 ASH WARE Inc Reference Manual 16 Dialog Boxes was opened Each target can be individually set Source Code Spaces per Tab Specifies the number of spaces that correspond to each tab character 16 6 Workshop Options Dialog Box The Workshops Options dialog box is used to as
336. t pins all 32 output pins and the TCRCLK pin In many cases only a small subset of pins are of interest The add_ebehavior_pin lt pin name gt script command allows the user to save data only on those pins of interest The pin name comes from any node naming in the vector file or is the underlying default pin name e g ch3 is the channel 3 pin on the TPU or _ch5 out is the channel 5 output pin on the eTPU save off only the fuel injection output signals create_ebehavior_file Engine_Injection EBV add_ebehavior_pin commands must immediately follow the create command add_ebehavior_pin Injector1 add_ebehavior_pin Injector2 add_ebehavior_pin Injector3 add_ebehavior_pin Injector4 After the creation setup commands are complete and the script file exercises the software the ebv file needs to be closed and any unsaved data flushed out Note that data may be saved in several steps as the simulation runs enhanced behavior verification 1994 2015 ASH WARE Inc page 130 Multi Target Development Tho Reference Manual 9 Functional Verification is not subject to buffer size limitations due to its continuous file management This is done with the close_ebehavior_file script command wait_time 20000000 Let the tests run to completion close_ebehavior_file close EBV being saved As mentioned the ebv file is in comma separated value format The first line contains the column header infor
337. t show that the requirements are being met In the maintenance stage these previously developed automated tests are rerun to prove that requirements are still being met when bug fixes and enhancements cause the code base to change There is a significant emphasis on automation such that a complete test suite can be run sometimes spanning hours and a series of tests results in a single pass or fail result Data Flow Verification Data flow verification is one of the verification capabilities for which an overview is given in the Functional Verification chapter Data flows between the TPU and the CPU primarily across the Channel Interrupt Service Request CISR register and the parameter RAM The data flow verification capabilities address data flow across these registers page 126 Multi Target Development Td 1994 2015 ASH WARE Inc Reference Manual 9 Functional Verification The TPU parameter RAM data flow is verified using the verify_ram_word X Y Z and verify_ram_bit X Y Z V script commands described in the TPU Parameter RAM Script Commands section The data flow across the CISR register is verified using the verify_cisr X Y script command described in the TPU Channel Interrupt Service Register Script Commands section The eTPU parameter RAM data flow is verified using the verify_chan_data24 X Y Z and verify_chan_bits24 X Y Z V script commands described in the eTPU Parameter RAM Script Commands section The data flow
338. t that properly models inter target interaction down to the transistor level Debugging Capabilities All standard single target debugging capabilities such as single stepping breakpoints goto cursor etc are available in the multiple target debugging environments For instance if breakpoints are injected and activated within multiple targets the simulation halts on whichever breakpoint is encountered first A concept of an active target is employed to support specifically single target capabilities such as single stepping When the active target is single stepped the entire system simulation proceeds until the active target completes the commanded single step With an essentially limitless number of targets and with the large number of possible windows per target the vast number of windows can become unwieldy to say the least Actually without some mechanism to bring order to the chaos of having way too many windows MtDt becomes unusable Workshops bring order to this chaos and are therefore a key enabling feature that makes MtDt usable Each target can be associated with a specific workshop Those target s windows are displayed only when the workshop associated with that target is activated Individual windows can be overridden to appear in more than one target A target other than the active target can halt a simulation In this situation the workshop is changed to one associated with the halting target This can be caused for ins
339. ta register D4 to D7 REG_AO REG Al REG_A2 REG A3 Addr register AO to A3 REG AA REG Ap REG AG REG ATI Addr register A4 to A7 page 112 Multi Target Development Td amp 1994 2015 ASH WARE Inc Reference Manual 7 Trace Buffer and Files H Trace Buffer and Files Overview Trace files have two primary purposes they are useful for generation of a file that appears identical to the trace window but can be loaded into a file viewer to access advanced search capabilities and they are used to load into a post processing facility for advanced trace analyses The various capabilities and settings are focused on these two purposes Generating Viewable Files Viewable trace files can be generated by selecting the Trace buffer Save As submenu from the Files menu Note that the trace buffer is about five times larger than what appears in the trace window A viewable trace file can also be generated using script commands See the Trace Script Commands section Because viewable files are appropriate only for things like advanced search capabilities no error or warning is generated if the underlying trace buffer has overflowed Generating Parseable Files Parseable files can be generated only by using the trace commands described in the Trace Script Commands section To ensure generation of deterministic parseable trace files these files can be generated only if the selected trace events are enabled within the simulator d
340. tance if a breakpoint is encountered in a non active target In this case the simulation is halted the halting target becomes the active target and the workshop is switched to the one page 286 Multi Target Development T9 1994 2015 ASH WARE Inc Reference Manual 20 Building the Target Environment associated with the newly active target Building the MtDt Environment With MtDt an entire hardware or simulation environment can be built This is done using a dedicated build script file that gets loaded when the project file is loaded A detailed description of each command that can be used within MtDt build script files is found in the MtDt Build Script Commands File section That section explains how a complete system is defined using these build script commands MtDt Simulated Memory Simulated targets require memory for executing code for holding data and for providing capabilities supported in a simulated environment The following is a list of simulated memory characteristics supported by MtDt memory Multiple address spaces Memory sizing Read only or read write accesses Shared memory Byte word and long word access widths Access speed based on even or odd access addresses Privilege violations Bus faults Address faults Banking Mirroring The ASH WARE MtDt simulated memory model supports all of these characteristics though at the cost of increased complexity The good news is that for many appl
341. tate is lo PAEN E E Pulse accumulator is Disabled PAMOD D D External event counting PEDGE C C PAI falling edge increments counter PCLKS B B PCKLK pin state is lo 14 05 A A Output compare 5 Disable Input capture 4 ENABLE PACLK 9 8 Clock source System clock divided by 512 Clock period is 666 632 06 ns PACNT 7 6 Pulse accumulator count is 66 TMSK1 TMSK2 82B8 PAOUI 5 5 Counter overflow Interrupt ENABLED PAII 4 4 Input pulse Interrupt ENABLED TFLG1 TFLG2 1636 PAOUF 5 5 Counter overflow flag PAIF 4 4 Input pulse flag is SET The GPT Pulse Accumulate window displays the Pulse Accumulate Control Register PACTL the Pulse Accumulate Counter Register PACNT the Timer Interrupt Mask Registers 1 and 2 TMSK1 TMSK2 and the Timer Interrupt Flag Registers 1 and 2 page 224 Multi Target Development TAS 1994 2015 ASH WARE Inc Reference Manual 15 Operational Status Windows TFLG1 TFLG2 15 8 5 GPT Pulse Width Modulation Window y ulse 5 i o x Force Force Pin Fast Period Period Width Width Output State Use Slow CNTs us Val Percent PWH A Yes lo TCNT FAST 256 606 632 6 66 8 PWH B Yes lo slow 32768 604 698 4 66 D CFPRC PWHC 2B84 The GPT Pulse Accumulate Width Modulation window displays the Compare Force Register CFORC and the PWM Control Register C Register PWMC 15 9 CTM4 CTM6 Module Windows The following windows display the Counter Timer Module CTM4
342. tch windows print_to_trace verify_val write_val etc For example ertA tcr1 p15_0 etc A verify_str_ex script command has been added It is very much like the verify_str script command with the addition of a fourth argument a length Think strncmp The verify_str script command now supports the gt and lt operators Added system macros for determining the Byte Craft compiler version __COMPILER_VERSION and the ASH WARE simulator version __MTDT_VERSION__ which are useful in script command used to verify or report this information 1994 2015 ASH WARE Inc page 24 Multi Target Development Tod Reference Manual 3 Software Upgrades print_to_trace Using compiler version s n __COMPILER_VERSION_ print_to_trace Using simulator version s n MTDT_VERSION__ Added an at_code_tag_ex script command to add a timeout thereby handling more cleanly the situation in which the tag is never hit Added the eTPU CPU System Simulator product Added a ASH print_to_trace capability whereby formatted symbolic information think printf can be exported to the trace window every time an area of your code is traversed GREAT FOR AUTOMATED TESTING Extended the existing print_to_trace script command to support formatted symbolic information using a new string within a string format Added global eTPU ChannelVariable access support to the Watches window and various script commands A
343. tching such that it is possible in the system simulator for example to run to a CPU breakpoint and then switch to a eTPU or MC33816 core and single step it All the while all targets cores are kept fully synchronized The Freescale eTPU and TPU Of special interest are the Enhanced Time Processor Unit eTPU and TPU from Freescale For those wishing more information on the eTPU refer to the Freescale user manuals For this wishing to develop their own eTPU Code it is highly recommended that you obtain the book eTPU Programming Made Easy from AMT Publishing For those wishing to develop their own TPU microcode it is highly recommended that you obtain the book TPU Microcoding for Beginners from AMT Publishing Do not be misled by the title This book is essential for beginners and experts alike The eTPU and TPU training seminars are also highly recommended Sharing Memory between Multiple Targets The key ingredient to the full system simulation capability is shared memory Targets expose their address spaces to other targets Two levels of address space exposure are possible extrinsic and intrinsic Extrinsic exposure is the most powerful but is not supported by all targets Extrinsically mapped address spaces allow memory accesses to that section of the memory map to occur in a target different from the one in which the access originated For example a simulated TPU might perform a write to data memory The section of data memory c
344. te Register TRR TRR 000400 INT 17 9 89002 Integer part of TCR1 clocks in one angle tick FRAC 8 6 666 Fractional part of TCR1 clocks in one angle tick The next angle increment is in 2 dec TCR1 ticks l l l l i l Each PLL tooth takes 96 0 uS 3 456 0 uS revolution l which correspnds to 17361 11 RPH Sereegetegegtetetegeteg Timer Counter 2 TCR2 660628 Rotations I l l l l Tooth Ticks l l TCR2 6 Current Rotations Tooth Count Resets 13 Z 72 Current tooth tick counts Angle Ticks 23 Z 24 Current angle tick counts Angle 139 58 720 Current Angle EE Analyses Mode Halted PLL predicted a tooth but the tooth has not yet been detected PLL is halted in anticipation of the next physical tooth TCRCLK Physical Tooth Detection Window Open a physical pin transition can be detected TCRCLK Last Tooth No tooth yet detected all External TCRCLK signal is filtered by system clock 2 2 sample mode Each angle increment takes 2 66 TCR1 increments or 4 660 6 nS The Module Configuration Registers MCR Global Time Base Enable GTBE field Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 195 15 Operational Status Windows indicates if the time bases in the eTPU s are enabled The Time Base Configuration Register s TBCR TCRICTL and TCR2CTL fields display the configuration of the TCR1 and TCR2 counters The TCR1P and TCR2P fields show
345. te at address 17 U8 0x17 44 Writes a OxAABBCC to the 24 bit word at address 0x31 U24 0x31 OxAABBCC Sets bits 31 and 15 of the 32 bit word at addr 0x200 U32 0x200 0x10001000 Increments by one the 16 bit word at address 0x3300 UL6 0x3300 1 Using an optional memory space qualifier memory from a specific address space can be modified See the Build Script ADDR_SPACE Enumerated Data Type section for a listing of the various available address spaces Sets the TPU I O pins for channel 15 and channel 3 TPU_PINS_ SPACE U16 zi 0x0 1 lt lt 15 1 lt lt 3 Sets the TPU s HSQR bits such that channel 7 s is a 11b TPU_DATA_SPACE U32 0x14 3 lt lt 7 2 Injects a new opcode into the TPU s code space TPU_CODE_SPACE U32 0x20 0x12345678 Operators and expressions in Script Commands Files Operators can be used to create simple expressions in script commands files Note that these simple expressions must be fully resolved at load time The precedence and ordering is the same as in the C language The following is a list of the supported operators Arithmetic addition and subtraction Arithmetic multiply divide and remainder amp 1 Bitwise AND OR and EXCLUSIVE OR lt lt gt gt Bitwise shift left and shift right The following example makes use of simple expressions to specify the channel base C 1994 2015 ASH WARE Won
346. ted Data Type The following enumerated data type is used to specify the target type No mathematical manipulation of this data type is valid enum TARGET_TYPE TPU_SIM ETPU_SIM SIM32 BDM32 Build Script TARGET_SUB_TYPE Enumerated Data Type The following enumerated data type is used to specify the target s sub type No mathematical manipulation of this data type is valid enum TARGET_SUB_TYPE eTPU2 SIM Single Engine MPC5632M Oo A MPC5633M_0_A MPC5634M 0A SPC563M54_ 0A C 1994 2015 ASH WARE D Target Development Tool page 107 6 Script Commands Files SPC563M60_0_A SPC563M64_0_A eTPU2 SIM MPC5674 2 A MPC5674_ 2 B MPC5674_0_A MPC5674_0_B JPC563M60_1 A Rev 0O Engine JPC563M60_1 B Rev 0O Engine Dual Engine Rev 2 Engine eTPU SIM Dual Engine MPC5566_0_1 MPC5566_0_2 MPC5554_B 1 MPC5554_ B 2 eTPU SIM MPC5567_0_1 MPC5565_0_1 MPC5553_A 1 MPC5534_0_1 eTPU SIM MPC5571_0_1 MCF5232_0_1 MCF5233_0_1 MCF5234_0_1 MCF5235_0_1 Rev 0 Engine Rev 0 Engine Rev B Engine A Rev 2 Engine B Rev 0 Engine A Rev 0 Engine B A B A B A B Rev B Engine Single Rev Rev Rev Rev Single Rev Rev Rev Rev Rev 683xx Debuggers MC68331 MC68332 MC68336 MC68338 Engine 55xx opr pT PR Engine Coldfire 0 MPC5570 and MPC5571 0 ooo TPU Standard M
347. tegrated Timers Workshops Operational Status Windows Dialog Boxes Menus Hot Keys Toolbar Status Window Building the Target Environment 1994 2015 ASH WARE Inc Reference Manual 2 Demo Descriptions 2 Demo Descriptions Note that Youtube videos covering several of these demos as well as feature tutorial demos are available on our website at www ashware com product_videos htm The following eTPU demos install by default with simulator debugger This demos also work in in the ETEC compiler run from the command line Demo videos and tutorials can be found at A demo is available at the following link www ashware com product_videos htm Freescale Set 1 UART Demo e Use of the Freescale s Set12 UART function e Use of header file etec_to_etpuc_uart_conv h to convert between the automatically generated etpuc_set1_defines h and the standard Freescale API interface file Freescale Set 2 Engine Demo e Use of the Freescale s Set2 Cam Crank Fuel Spark Knock functions e Use of the identical auto generated headers that Freescale uses for it s host side API Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 17 2 Demo Descriptions Freescale Set 3 ASDC Demo e Use of the Freescale s Se ASDC PWMF and PWMMDC functions e Use of the identical auto generated headers that Freescale uses for it s host side API Freescale Set 4 ASAC Demo e Use of the Freescale s Self ASAC PWMF and PWM
348. ters Window CPU32 Disassembly Dump Window 15 1 Generic Windows The following windows display generic information 15 1 1 Source Code Windows eat cond hsr1 1 hsr6 6 TpuSim Source uart UC Init TOGGLE ram diob lt TOGGLE_HI au ert tcri diob chan neg_tdl neg_mrl neg_1sl pac high_low pin high write_mer end 969636 JE 96 96 JE JE 96 96 96 36 IE JEJEJE EIE HE Host16 Source HostMain c Bisi x c fa O3DE JSR 3deh EXT26 4 a STATE low write chan cpr 14 3 G6ca 37b5 6663 LDD 3h IHH16 4 PRELOAD PARAMETER gece 34 61 PSHM d IMM8 2 66d6 37b5 00E LDD 6eh IMM16 4 5 ENTER WHEN lol oan fa 825A JSR 25ah EXT20 4 i ACTION D Setup channel 13 to function 12 UART d 7 wm ven fme g pag Ve B dc 34 61 PSHM d sentry start_address g e2 fa 9312 JSR 312h name TOGGLE _low_hit write_chan_hsrr 13 3 cond hsr1 6 hsr6 6 m gece 37b5 6663 LDD 3h G6ea 34 61 PSHM d _ G6ec 37b5 AD LDD 6dh Te ra aana Ien sanh E IMM8 2 IMM16 4 EXT26 4 IMM16 4 IMM8 2 IMM16 4 ryran ret These windows display the executable source code that is currently loaded in the target Each window displays one source file page 174 Multi Target Development TAS 1994 2015 ASH WARE Inc Reference Manual 15 Operational Status Windows The executable source code is loaded into the target s memory via the Files menu To lo
349. that redraws are not required thereby improving simulation speed The effective pin transition buffer size can also be increased in other ways This is discussed in the Logic Analyzer Options Dialog Box section Enhanced Behavior Verification Script Commands The test tolerance commands apply whether an old style bv file or new ebv file is being used as the master however the file manipulation script commands only apply to ebv files create_ebehavior_file filename ebv This command creates an enhanced behavior data file with the specified name ebv file creation in a script command file has the following limitations only one can be created cannot have the same file name as a running under verification ebv file must occur at simulation time 0 before any wait_time or at_time script commands must occur after any external gate instantiation or after any vector file commands add_ebehavior_pin lt pin name gt By default when an enhanced behavior data file is created all pins will be saved out on Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 77 6 Script Commands Files the TPU that is channel 0 15 and _tcr2 while on the eTPU that is all 32 channel input 32 channel output pins and _tcrclk With this script command the user can select just the pins desired to be saved to the ebv file as this is generally just a small subset The lt pin name gt argument is the name pro
350. the description of the Watches window for information on how to display global variables Local Variable Window Automation In conjunction with the Call Stack window the Local Variables window can display the local variables of functions that have been pushed unto the call stack In a Call Stack window move the cursor to a line associated with a function that has been pushed onto the callstack This causes the local variables from that function s context to be displayed in the Local Variables window Occasionally it is desirable to lock the local variable to display the local variables of a particular function To do this you must disable the automation This is done within a Local Variables window by opening the Local Variable Options Dialog Box and selecting the lock the local variables option Locking and unlocking of the current function s context can also be done more quickly by selecting either the lock or the unlock options from the popup menu that appears when you right click the mouse within a Local Variable window Call Stack Window KEE Call Stack f E J E ll x PTA DemoInit in platformDemo c at line 296 address 6xb94 frame OxffcB R platformDemoInit in platformDemo c at line 122 address Oxa4a frame 6xffd6 ash_main in main c at line 56 address Ox4d2 frame Oxfff6 ll d The Call Stack window displays the function source code file name and line number address and stack frame poi
351. the microcontroller s operational software must first copy the microcode into its internal RAM and then configure the TPU to execute out of RAM Support for TPU1 The simulator debugger supports the TPU1 This is the original TPU Support for TPU2 The simulator debugger supports the TPU2 The following is a list of new and supported features of the TPU2 not available n TPU1 page 280 Multi Target Development TAS 1994 2015 ASH WARE Inc Reference Manual 19 Supported Targets and Available Products Entry table bank ETBANK Code bank Full parameter RAM Load zero using a RAM sub instruction Additional TCR2 and TCR1 clock options Flag2 set clear and conditional execution Branch on current pin state Negation of MRL and TDL using TBS sub instruction Match on equal The entry bank is controlled in the TPU simulation engine using a write_entry_bank script command as described in the TPU Bank and Mode Control Script Commands section The current state of this field is displayed in the microsequencer window The code bank is set during a time slot transition using bits 10 and 9 of the entry table The user modifies this directly within the source microcode The current state of this field is displayed in the microsequencer window The TPU1 does not implement parameters six and seven of the parameter RAM for channels zero through 13 The TPU2 supports a full complement of parameter RAM for all channels The
352. the simulator debugger s termination error level to be set to be non zero if any verification tests failed or zero if all the tests passed 1994 2015 ASH WARE Inc Reference Manual 9 Functional Verification The overall strategy in ensuring that a zero error level truly represents that all tests have run error free and to completion is to treat any unusual situation as a failure Specifically a failing non zero termination code will result unless the following set of conditions has been met No verification tests are allowed to fail in any target Alltargets must have executed all their script commands simulator debugger must terminate through the exit script command Abnormal termination such as detection of a fatal internal diagnostic error results in a non zero error level 9 9 Cumulative Logged Regression Testing Cumulative logged regression testing supports the ability to run an entire test suite without user intervention even if one or more of the tests fail This capability overcomes the problem in which a failure halts the entire test suite until acknowledged by the user Using this capability the alert is logged to a file rather than being displayed in a dialog box Test completion occurs when the exit script command is encountered At this time a PASS or FAIL indicator is appended to the end of the log file Because it is appended to the end of the log file the normal usage would be to delete the log file prior
353. the transition data between the left and right cursors Setup t Selecting the Setup button causes the Logic Analyzer Options dialog box to be opened This dialog box accesses various setup options as described in the Logic Analyzer Options Dialog Box section Hep Hl Selecting the Help button accesses the Logic Analyzer section of the on line help Timing Display Below the Logic Analyzer s horizontal scroll bar are two fields that display the time or CPU clock counts corresponding to the left hand and right hand sides of the wave form display panel The display region can be modified using the horizontal scroller located below the wave form view panel It can also be modified using the buttons described in the Button Controls section found earlier in the description of the Logic Analyzer Below the left side of the wave form display panel are the three fields that display the time or CPU clock counts associated with the left cursor right cursor and delta cursor 1994 2015 ASH WARE Inc Reference Manual 14 15 14 The Logic Analyzer Delta refers to the time or CPU clock counts difference between the left and right cursors Below the right side of the wave form display are three fields that display the time or CPU clock counts associated with the current Simulator time the oldest available transition data and the mouse The mouse field is visible only when the window s cursor is within the wave form display p
354. ti Target Development Tho Reference Manual 13 Workshops 13 Workshops Workshops bring order to a chaotic situation The problem is that with multiple targets each of which have many windows the number of windows may become overwhelming In fact it may become so overwhelming that without workshops the Multiple Target Simulator would be nearly unusable Workshops allow you to group windows together and view only those windows belonging to that group Generally it is best to group by target so that each workshop is associated with a specific target though this is completely configurable by the user Some windows such as watch windows and the logic analyzer windows are often made visible in multiple workshops Menus and toolbar buttons allow instantaneous switching between workshops and selection of the active target The name of the active target is also prominently displayed in the top right toolbar button Closely coupled with workshops is the concept of the active target core It is generally best to associate targets cores with workshops Thusly when the workshop is switched the active target core is also automatically switched to the one associated with the newly activated workshop The active target core is important in that simulator debugger acts on the active target core in a variety of situations For instance when a single step command is issued the active target core is the one that gets single stepped and all other target
355. tion times are an approximation based on the real time clock Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 187 15 Operational Status Windows of the PC Saving Trace Data to a File The trace data can be saved to a file either directly through the GUI or from within a script commands file This is explained in the TRACE BUFFER AND FILES section TPU Simulation Considerations The TPU simulation model provides several additional events that can be viewed in the Trace window These are in addition to the normal data flow between TPU and memory and opcode execution etc that are available for most targets These events include execution steps time state transitions active channel transitions and four CPU clock NOPs This window serves two purposes It shows the thread of execution and it can be used to analyze channel service timing When the TPU services a particular channel a 10 clock time slot transition occurs The states of the Service Request Latch SRL and Service Grant Latch SGL as well as a timestamp and a channel number are displayed for each time slot transition The SRL is the fourth field from the left while the SGL field is displayed to the right of the SRL field When all pending service requests from a particular priority level have been serviced the TPU negates the service grant bits associated with those channels This requires four CPU clocks For this event MtDt displays the timestamp
356. tiple targets Source Code File Windows Script Commands File Windows Watch Window Local Variables Window Call Stack Window Threads Window Trace Window Complex Breakpoint Timers Window Memory Dump Window Logic Analyzer Window e TPU Specific Windows Reference Manual C 1994 2015 ASH WARE Pgri Target Development Tool page 171 15 Operational Status Windows The following windows are available on eTPU Simulator targets eTPU Channel Frame eTPU Configuration Window eTPU Global Timer and Angle Counters Window eTPU Host Interface Window eTPU Channel Window eTPU Scheduler Window eTPU Execution Unit Registers Window TPU Simulator Spe cific Windows The following windows are available on TPU Simulator targets TPU Configuration Window TPU Host Interface Window TPU Scheduler Window TPU Microsequencer Registers Window TPU Execution Unit Registers Window TPU Channel Window TPU Parameter RAM Window 683xx Hardware Debugger Windows 683xx Hardware Debugger Configuration Window 683xx ASH WARE Hardware Window System Integration Module Windows SIM Main Window SIM Ports Window SIM Chip Selects Window Queued Serial Module Windows QSM Main Window QSM Port Window QSM QSPI Window QSM SCI UART Window RAM and ROM Windows Masked ROM Submodule Window 68336 68376 Standby RAM Submodule Window 68336 68376 Static RAM Submodule Window 68338 TPU Emulation RAM Window 68332 68336 68376 Timer Processo
357. to beginning the test suite Then upon completion of a test run the log file grows At the end of the test suite the log file can be perused and any failing tests are quickly identified Note that only certain types of failures bypass the normal message dialog box For instance if the failure log file itself cannot be written then this generates a failure message in a dialog box which must be manually acknowledged This capability is invoked using a combination of two Command Line Parameters shown below LF5MyLogFile log Quiet The first command LF5MyLogFile log specifies that message are appended to the end of a log file named MyLogFile log The second command Quiet specifies that the dialog boxes that normally carry test errors or warnings are not displayed Note that this command only works in conjunction with AutoRun IAcceptLicense and LF5 lt LogFileName log gt If any of these options is not selected then this Quite command is ignored Note also that if the user halts the simulation then this option is disabled such that messages shown in dialog boxes will Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 143 9 Functional Verification require manual acknowledgement It is convenient to name each test run That is when simulator debugger is launched the command line parameter shown below applies a name the test run This name shows up in the log file This allows the particul
358. two script commands write actual value of the system clock divider NOT THE VALUE OF THE TCRIP or the TCR2P registers So for example the script write_tcr1_prescaler 6 gives a divide by of 6 but the TCRIP register gets written to a 5 Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 81 6 Script Commands Files 6 6 23 page 82 Multi Target Development Tod These commands write the prescaler Prescaler to the ETPUTBCR register Valid values for TCR1 are 1 256 and for TCR2 are 1 64 write_angle_mode 0 Disable write _tcrl_control 1 System clock 2 write _tcr2_control 2 TCR2 s clk is falling TCRCLK Pin write_tcrl_prescaler 1 Fastest divide by 1 write_tcr2_prescaler 64 Slowest divide by 64 In this example angle mode is disabled the TCR1 counter is programmed to be equal to the system clock divide by two system clock divided by two prescaler is divides by one and TCR2 is programmed to be the system clock divided by 512 system clock divided by 8 with a 64 prescaler write _tcrl_control 2 System clock 1 eTPU2 Only write_tcrl_source 1 System Clock 1 eTPU2 Only write_tcrl_prescaler 1 Fastest divide by 1 In the above example system clock 1 is the input to the TCR1 prescaler This is ONLY available in the eTPU2 set_angle_indices lt DegreesPerCycle gt lt TeethPerCycle gt This command supports specific
359. ulator debugger to go out to the hardware for hardware targets to refresh window data This is helpful on hardware targets for updating the display of hardware registers that may be changing even while execution is halted Help This accesses this help screen 17 8 Options Menu The Options menu provides the user with the capability of setting various Simulator options These are listed below IDE This opens the IDE Options dialog box Workshop This opens the Workshops Options dialog box Messages This opens the Message Options dialog box Reset This opens the Reset Options dialog box It specifies the actions taken when simulator Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 269 17 Menus debugger is reset from the Reset menu by selection of the Reset submenu Waveform Logic Analyzer This opens the Logic Analyzer dialog box Note that a Logic Analyzer window must be active for this submenu item to be available BDM This opens the BDM Options dialog box Note that a 683xx Hardware Debugger target must be active for this submenu item to be available Memory Tool This opens the Memory Tool dialog box Note that if a Memory Dump Window is selected when this dialog box is opened settings from the window are automatically loaded into the dialog box This supports a variety of capabilities including dumping memory to files searching for patterns in memory and filling memory Memory Th
360. ursor is at 1 microsecond Therefore the left cursor is to the left of the visible area To bring the left cursor back into view click the left mouse button at the location indicated by arrow 2 page 162 Multi Target Development Td 1994 2015 ASH WARE Inc Reference Manual 14 The Logic Analyzer n TpuSim Logic Analyzer EE Oo x uaRT_Rcv fuaRT_Rcv Ta z 006 027 4 uS Mouse 006 251 8 uS Data Start 000 000 0 vS Context 000 000 0 vS Current Time 006 229 3 vS Sc D Set Left Cursor 001 047 1 vS The simulation can execute to precisely the left or right cursor s time by dragging and dropping the time into the current time as explained in the Executing to a Precise Time section Delta Cursor 005 132 1u5 Right Cursor 006 179 2 vS The cursor can also be moved by dragging and dropping a time into a vertical cursor s time indicator Left Right and Delta Cursor Time Indicators The left and right time cursor time indicators show the time associated with the respective vertical cursors The Delta Cursor indicator shows the difference in time between the left cursor and the right cursor These time indicators are capable of extremely precise time measurement with accuracies approaching one femto second This is because the cursors can be snapped to the precise pin transition time using your keyboard s left and right arrow keys Reference Manual C 1994 2015 ASH WARE D Target Development
361. user defined nodes User defined nodes are those defined within Test Vector Files The waveform display panel may not be large enough to display all the desired nodes The display can be scrolled vertically using the vertical scroll bar Viewing Thread Activity Nodes Thread activity can be viewed in the logic analyzer window as shown below There are eight user configured thread nodes Each of these thread nodes can display the thread activity for one or more channels See the Logic Analyzer Options dialog box section for more information on configuring thread nodes rc TpuSim Logic Analyzer x lol x z T Auto Seroll E mi IS GA c 001 765 0 uS Mouse 005 522 8 vS Data Start 000 000 0 uS Context 000 000 0 uS Current Time 005 437 2 uS T Set Left Cursor 001 821 9 uS Delta Cursor 003 643 9 uS Right Cursor 005 465 8 uS Viewing Channel Nodes Several eTPU and TPU channel nodes can be viewed in the logic analyzer as shown below These include the Host Service Request HSR Link Service Request LSR Match Recognition Latch output and enable MRL and MRLE and Transition Detection Latch TDL Only the nodes from a single channel can be stored and viewed at a time The channel for which the nodes will be stored is defined in the Logic Analyzer Options Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 161 14 The Logic Analyzer dialog box m TpuSim Logic Analyzer sl UaRT_RCV
362. verify all coverage 33 3 47 5 write_coverage_file record Coverage The code in this example waits 100 microseconds and then verifies that at least 92 5 percent of the instructions associated with file toggle uc have been executed and 66 5 percent of the possible branch paths associated with file toggle uc have been traversed In addition the example verifies that at least 33 3 percent of all instructions have been executed and that 47 5 percent of all branch paths have been traversed A complete report of instruction and branch coverage is written to file record Inferred Event Vector Coverage In eTPU applications it is often difficult to get complete 100 event vector coverage There are two situations in difficulties may be encountered The first situation would be a valid and expected thread that is difficult to reproduce in a simulation environment For example when measuring the time at which a rising edge occurs it may be difficult to generate a test case for when the input pin is a zero because a thread handler will normally execute immediately such that the pin is still high But an event vector handling the case of a rising edge and a low pin is valid For instance a rising edge followed by a falling edge could occur before a thread executing in another channel completes Now the thread handling this rising edge executes with a low pin state It is therefore important to test this case but how The solution to achieving event
363. verify files new dat gold dat FILES MATCH The above example illustrates use of the FILE_APPEND options to store multiple data snapshots into a single file By first verifying that the files mismatch then that the files match it proves that it is this verification process that actually generated the passing results Related Topics Trace Script Commands 6 6 12 Trace Script Commands start_trace_stream FileName Trace enum TRACE_EVENT_OPTIONS enum TRACE FILE OPTIONS enum BASE TIME U32 numTrailingDigits int isZeroTraceTime This command saves the target s trace buffer to file FileName trace with the options set by TRACE_EVENT_OPTIONS TRACE_FILE_OPTION BASE_TIME_OPTIONS and numTrailingDigits The numTrailingDigits field defines the number of digits to display after the decimal point For example if you specify numTrailingDigits to be 2 and the time options to use micro seconds then the representation of 1 333 microseconds is 1 33 The isZeroTraceTime parameter specifies if the time reference used by the tracing capability gets referenced to the time when the start_trace_stream script command is executed For instance if the start_trace_stream were to be issued at time 100 microseconds and 22 microseconds an Pin Transition occurred then the time of the Pin Transition event time would be listed at 122 microseconds if isZeroTraceTime is a 0 Conversely if isZeroTraceTime is a 1 the time would
364. vided in the vector file through the node command or is the default name of the pin e g _ch3 out is the channel 3 output pin on the eTPU or _ch10 is the channel 10 pin on the TPU These script commands must immediately proceed the create_ebehavior_file script command Once one add_ebehavior_pin script command is used all pins of interest must be added with this script command as the default of all is disabled close_ebehavior file Closes an enhanced behavior file that was created saving off any remaining buffered data to file When using the created ebv file verification should be stopped at the same time as when the ebv file data stopped being recorded see stop_ebehavior_file run_ebehavior_file filename ebv This script command opens the specified enhanced behavior verification file The loaded file is often referred to as the master file or gold file By default all pins found in the ebv file are enabled for verification The script command has the same limitations as create_ebehavior_file script command in that it must be called out at a simulation time of 0 etc The default tolerance for all pin transition data being verified is two system clocks and zero offset set_ebehavior_pin_tolerance lt pin name gt time tolerance mode gt lt time offset in us gt lt time tolerance in us gt Sets the time tolerance allowed between the loaded master file and the current simulation run for the specified
365. w 52 MyBdm32 QSM Port oj x PQSPAR BE ron 7 7 PQS 7 Input 8 DDRQS 80 PCS3 6 6 PQS 6 Input 8 PORTQS 89 PCS2 5 5 PQS 5 Input 8 Pcs4 4 4 PQS 4 Input 6 PCSO SS 3 3 PQS 3 Input 6 SCK 2 2 PQS 2 Input 8 MOSI 1 1 PQS 1 Input 8 MISO 8 0 PQS 6 Input 8 The QSM Port window displays the Port QS Pin Assignment Register PQSPAR the Port QS Data Direction Register DDRQS and the Port QS Data Register PORTQS Using the bit port bit fields located to the right of the bit position fields the use of each port pin can be specified Each pin can be specified as a generic I O or assigned to the QSM In addition both the data direction and register value can be specified 1994 2015 ASH WARE Inc page 218 Multi Target Development Tho Reference Manual 15 Operational Status Windows 15 6 3 QSM and QSPI Window 3 MyBdm32 QSM QSPI Oo x SPCRO PED MSTR F F QSPI is a slave device Wong E E Outputs have normal HOS drivers BITS D A Bits field is 8 resulting in 16 bits per transfer CPOL 9 9 The inactive state value of the SCH pin is lo CPHA 8 8 Data CHANGED on SCK s leading edge and captured on the trailing edge SPBR 7 6 SPBR is 64 for a clock period of 666 661 06 microseconds SPCR1 6464 SPE F F QSPI is a slave device DSCKL E 8 Delay from chip select assertion to leading edge of SCK is equal to DSCKL field 64 system clocks l
366. wise you will have to periodically check the ASH WARE Web site to find out about new software releases Note that your e mail address and other contact information will never be released outside of ASH WARE Further ASH WARE will only add you to our e mail list if you specifically request us to do so The simulator debugger automatically displays an informational message when your software subscription is close to expiration Note that the software license has no expiration so it is legal to use the simulator debugger beyond the software subscription expiration date The software subscription entitles you to free technical support and Web based software upgrades Technical Support Contact Information With the purchase of this product comes a one year software subscription and free technical support This technical support is available through Email the World Wide Web and telephone Contact information is listed below 503 533 0271 phone Wwww ashware com support ashware com Version 3 0 to 4 3 Enhancements Version 4 30 Enhancements Support for Network Floating Licensing Support for Dongle Licensing Version 4 00 Enhancements eTPU2 script commands to write verify Global Data eTPU2 Stand Alone Simulator Product status PRODUCTION Support for the new STMicroelectronics Freescale SPC563Mxx eTPU2 microcontrollers Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 23 3 Software Upgrades eTPU
367. wo consecutive characters The other flavor of the Print action commands have the same capabilities but sends their output to either a message dialog thereby pausing simulation or to a log file if autorun logging is enabled See the print and print_pass script command documentation for more details 1994 2015 ASH WARE Inc Reference Manual 10 Action Tags QASH print action tag print to dialog or log file Q ASH print_pass output a message without affecting the simulator exit code 10 2 Timer Action Commands The timer action commands provide a method for instrumenting source code to verify that time critical paths are being met QASHQ timer_start Test 1 ASH timer_stop Test 1 The passed parameter is the test name and can contain any text with the restriction that each test must have both a timer_start and a timer_stop action command In other words timer action commands must come in pairs such that each named test has both a start and a stop Additionally only one start and one stop is permitted for each test In order for a timing measurement to be considered valid the following must occur The code containing the start tag must be first and the code containing the stop_tag must be traversed next In other words the traversal must occur in pairs of start stop start stop etc If this order is broken a stop before a start two starts in a row or two stops in a row then the action timer is i
368. ws 15 1 10 Timers Window Start Stop This Last Last Time ID State Address Address Ticks Ticks micro seconds D ID 00000190 66666194 66666828 66666628 666 616 6 1 Disabled 66661666 66662668 FFFFFFFF 666 666 6 2 Finished 66666146 6666616A 00002A73 66662A73 662 931 6 3 Disabled 66661666 666626686 FFFFFFFF 666 666 6 4 Disabled 66661666 6669626686 FFFFFFFF 000 000 08 5 Disabled 66661666 66662666 FFFFFFFF 666 666 6 6 Disabled 66661666 66662668 FFFFFFFF 666 666 6 7 Disabled 66661666 66662668 FFFFFFFF 666 666 6 8 Finished 666666098 66666164 66662AE3 668662AE3 662 957 A 9 Started 6666613A 666666A8 FFFFFFFF 666 666 6 A Disabled 66661666 666626686 FFFFFFFF 666 666 6 B Disabled 66661666 666962668 FFFFFFFF 666 666 6 H Disabled 66661666 66662668 FFFFFFFF 000 0006 08 D Disabled 66661666 66662666 FFFFFFFF 666 666 6 E Finished 66666692 G66666AE 668606667 66666007 666 661 4 F Disabled 66661666 66662666 FFFFFFFF 666 666 6 The Timers window displays the state of the 16 ASH WARE timers See the Integrated Timers chapter for a detailed explanation Each row of the window contains information regarding a single timer The ID field on the far left indicates which of the 16 timers the row represents The State field is to the right of the ID field This field indicates the current state of the timer The possible states are generally disabled armed started finished and overrun Double clicking with the left mouse button forces the time
369. x UART_RCV Tal uaRT_RC V Mrle e EART Rev Ne IV Auto Seroll E III UI gt i KS c 001 861 5 uS Mouse 005 451 2 uS Data Start 000 000 0 uS Context 000 000 0 uS Current Time 007 718 4 uS Set Left Cursor 001 915 9 uS Delta Cursor 003 480 9 vS Right Cursor 005 396 8 uS 14 3 The Active Waveform The active waveform is red whereas all others are black Use the lt up gt and lt down gt arrows on the keyboard to switch the active waveform 14 4 Left and Right Vertical Cursors The logic analyzer has two cursors a left cursor and a right cursor The left cursor is blue whereas the right cursor is green One of the two cursors is always selected and this selected cursor is displayed as a solid line Conversely the unselected cursor is displayed as a dashed line The concept of an active cursor is important because the active cursor is snapped to edges on the active waveform using the keyboard s left and right arrow keys To switch between the selected and unselected cursor hold the lt CTRL gt key while pressing either the left or right arrow keys on the keyboard Grabbing an Out of View Cursor Occasionally the left or right cursor may be out of view as the left cursor is in the picture seen below The right cursor is at arrow 1 But the left cursor is out of view because the waveform is only displaying a quarter microsecond of waveform at around six microseconds but the left c
370. xact path is available the source code file will be searched only at that exact path If an exact path is provided and the file is not located at that exact path the search will fail The Source Code Search Options dialog box allows the user to specify the global directories search list as well as the search lists associated with each individual target Absolute and Relative Paths 1994 2015 ASH WARE Inc Reference Manual 5 Source Code Files The simulator debugger accepts both absolute and relative paths An absolute path is one in which the file can be precisely located based solely that path The following is an absolute path C Compiler Libary A relative path is one in which the resolution of the full path requires a starting point The following is an example of a relative path ControlLaws Relative paths are internally converted to absolute paths using the main build file as the starting point As an example suppose the main build file named A OUT is located at the following location C MainBuild TopLevel A out Now assume that in the search rules the following relative path has been established ControlLaws Now assume that file Spark C is referenced from the build file A OUT Where would the simulator debugger search for this file The following location would be searched first because this is where the main build file A OUT is located C MainBuild TopLevel If file Spark C were not located at the above
371. y See the above description from the time display Reference Manual C 1994 2015 ASH WARE D Target Development Tool page 253 16 Dialog Boxes 16 13 16 14 16 15 Channel Group Dialog Box The Channel Group Options Dialog box is used to select groups of one or more channels It is accessed in different locations for different purposes This dialog box is accessed from the Logic Analyzer Options Dialog Box to specify groups for monitoring of eTPU thread activity Note that thread group activity is displayed as a waveform in the Logic Analyzer This dialog box also is used by the Complex Breakpoint Conditional Dialog to select which channels a complex breakpoint conditional acts upon Complex Breakpoint Conditional Dialog Box The complex breakpoint conditional dialog box allows the user to add conditionals to complex breakpoints Each complex breakpoint must contain one or more conditionals This dialog box is accessed from the complex breakpoints window Trace Options Dialog Box Instruction Execution Selecting this option causes each instruction execution to be logged to the trace buffer Instruction Boundary Selecting this option causes each instruction boundary to be logged in the trace buffer While an instruction boundary contains no useful information the resulting dividing line makes the trace window easier to read Memory Read Selecting this option causes each memory read to be logged to the trace buffer Me
372. y chan_output_pin 5 1 verify ouput butter disabled 5 wait_time 5 verify chan_output_pin 5 0 verify _ouput_buffer_enabled 5 In this example channel 5 s output pin is verified to have a falling transition within a 5 micro second window It is also verifying that the pin is acting like an open drain active low passive high Reference Manual C 1994 2015 ASH WARE Won Target Development Tool page 75 6 Script Commands Files 6 6 18 Pin Transition Behavior Script Commands The pin transition behavior capabilities allow the user to generate behavioral models of the source code and to verify the source code against these saved behavioral models The script commands allow the user to both create pin transition behavioral model and automate the verification process Script command capabilities include the ability to save and load pin transition behavior files the ability to enable continuous verification against these models and control tolerance of tests and the ability to perform a complete verification of all recorded behavior at once NEW Enhanced behavior verification starting with release 5 00 provides much more flexible and useable pin transition verification capabilities With enhanced behavior verification pin transition data is saved in a new format that is csv comma separated value format for compatibility with many other tools However the enhanced behavior verification can read original style bv files as well

Multi Target Development Tool

Contents

Download Pdf Manuals

Related Search

Related Contents