HEXit Manual 4 FFL Page 1 e-h4x49

Transcription

1 FFL Page 1 e-h4x49

2 Manual as of Version 4.x We wish you success in your work with HEXit The Team at hse electronics You will find information about the terms of use for HEXit on page Page 2 e-h4x49

3 Table of Contents 1 HEXit Function Overview About the Manual Terminology Installation and Registration Installation Registration The HEXit Operating Concept Input Assembling the Data Files (Intel Hex, Motorola S-Record and Binary formats) Data Generator Functions Defining functions Linking files / data Link several input files/data Splitting files / data Split output Format Conversion to Intel Hex Convert to Intel Hex Format Conversion to Motorola S-Record Convert to Motorola S-Record Format Conversion to Binary Convert to Binary Format Conversion to Include Convert to Include Output Results File Settings Checksum Generation CRC settings File and CRC Results Info Projects and Commands Automating Processes Project Management Command Line Control Settings File Analyzer - Graphically Analyze Files Basic Control Elements: Analysis Filters Three Analysis Examples Visualization of Individual Data Bytes Application Examples Splitting an Intel Hex File Exchanging the Range of a Binary Code Checksum Generation (CRC) Generating a Jump Table with the Data Generator HEXit Terms of Use HSE-Electronics Products Page 3 e-h4x49

4 1 HEXit 1.1 Function Overview HEXit from hse electronics is a must-have for working professionally with Intel Hex, Motorola S-Record and Binary files With HEXit, you can modify Intel Hex, Motorola S-Record and Binary files: Intel Hex, Motorola S-Record and Binary files can be converted into any of the other formats Check sum generation (CRC 16/32) for files Write the check sum into the checked file Splits files, for example to a controller s internal and external flash drives Links multiple files Data generator that can create constant numbers, ramps, or random numbers in order to test a system s behavior Graphical analysis of Intel Hex, Motorola S-Record and Binary files for Storage allocation Address distribution Distribution of program codes / data Multiple address allocation Quick overview of large data structures via assignment of color values to individual byte values Bar chart display of data 1.2 About the Manual Terminology Terms that appear in the manual in bold italics can be found in the program interface; for example, Data area, Start address and Ramp data. The term dialog area describes an area in HEXit where settings can be adjusted or information is displayed; for example, the dialog areas Data area or Fill pattern. Buttons are called function buttons if they contain or start a function; for example, Convert to Intel-Hex. Option button Checkbox Dropdown menu Page 4 e-h4x49

5 2 Installation and Registration 2.1 Installation From the CD: Insert the CD into the CD drive and follow the instructions. From a downloaded file: Start setuphexit.exe and follow the instructions. 2.2 Registration After HEXit has been started for the first time, it must be licensed; otherwise, HEXit will only run in a limited demo mode. There are two available licensing methods: USB dongle license If a license dongle was delivered with HEXit, insert the license dongle in a USB port and HEXit will be activated. PC license HEXit registration requires two steps: Step 1: Perform this step on the computer for which HEXit is to be registered! Click Build registration data. HEXit has generated your personal System ID. - Complete the fields marked with *. - Send your data to us. You also have the following options: Via (Build mail...). As an attachment to an (Save as). Via fax; print out the data (Print ). - We will send you your activation code via . Step 2: - Enter the activation code you have received from hseelectronics in the Enter license key field. - Click Enable license. - When the message License is enabled is displayed (on a green field), FLASHit has successfully been registered. For questions about registration, send us an at info@hse-electronics.com. Note: If you need a new activation code because your hardware or other conditions have changed, send us a brief with your old license number and you will receive a new number after you pay the license transfer fee of EUR If you are using dongle licensing, this is of course not necessary Page 5 e-h4x49

6 3 The HEXit Operating Concept The HEXit interface is divided into three areas: Input Functions Output Input All of the Intel Hex, Motorola S- Record and Binary files, as well as test data generated by HEXit, are shown in this area. This is where HEXit provides a variety of information about the files and data. You can adjust settings for generating test data in the input area. Functions All of the settings for processing the files and data shown in the input area are done in this area. Output In this area, all of the settings for the generated output files are done and the outputs are displayed. Once all of the settings have been made, the Execute button initiates data processing. The File Analyzer function plays a special role in HEXit s range of functions. File Analyzer enables the option of conducting a comprehensive and quick analysis of an Intel Hex, Motorola S-Record or Binary file. The analysis is output in a graphical format so that the user can have a quick overview, even for large files Page 6 e-h4x49

7 4 Input Assembling the Data HEXit's input area is where all of the data is assembled that will later be joined, split or converted. This includes files in the Intel Hex, Motorola S-Record and Binary formats, as well as data generated by HEXit. 4.1 Files (Intel Hex, Motorola S-Record and Binary formats) Assembly of Intel Hex, Motorola S-Record and Binary files for later processing in the left part (list) of the input area. Changes the sequence of entries in the list in the input area. This is important for the >Link several input files/data< function, which will be discussed later. Deletes individual entries from the list window. By right-clicking on the highlighted file, you can select Preview for a look at the file. Information about the currently selected file is displayed in the right part of the input area. File info dialog area Size: File size in bytes Format: File format (Intel Hex, Motorola S-Record, Binary) Addr type: Address width (16-32 bit) Byte/Line: Number of data bytes per line Data rate: The percentage ratio to data size, derived from Byte/Line Source dialog area Load from start address User defined: Load the selected file, starting with a selected address File defined: Load the selected file starting with the start address specified in the file Source dialog area Load up to end address User defined: Load the selected file, up to a selected end address File defined: Load the selected file up to the end address specified in the file Destination dialog area Address Offset: File loading is offset by this value Page 7 e-h4x49

8 4.2 Data Generator The data generator produces virtual data clusters (constant data, ramp data or random data). The addresses, size and content of the files can be generated on a custom basis. Inserting a data placeholder in the list window of the input area. <Data generator0> to <Data generator13>, from which Intel Hex, Motorola S-Record or Binary files can be generated later. Changes the sequence of entries in the list window in the input area. This is important for the >Link several input files/data< function, which will be discussed later. Deletes individual entries from the list window. By right-clicking on the highlighted file, you can select Preview for a look at the file. Data area dialog area Start address: Definition of start address. Size: Length of the later data record. End address: Definition of end address. The entries under Size and End address correspond to each other. Fill pattern dialog area Constant pattern: The address range can be filled with a constant pattern. In Fill pattern preview window, the pattern can be entered in the entry field. The pattern (maximum 16 bytes) repeats continuously. Clicking? to the right of Constant pattern opens a page that shows the options that are possible with this function. In Chapter 9.4, Creating a Jump Table with the Data Generator, there is a detailed example for generating an op-code. Ramp data: The address range is repeatedly filled with the values 0x00, 0x01, to 0xFF. Random data: The address range from 0x00 to 0xFF is filled with random data Page 8 e-h4x49

9 5 Functions Defining functions In HEXit s Functions area, you can define how inputs (files/data) assembled in the Input area are processed. In the Functions area, the entries in the Input area can be: linked divided into several files; and converted into other formats (Intel Hex, Motorola S-Record, Binary or Include formats). The different functions can be combined in any way, as long as logic permits it. In the Convert dialog window, only one option at a time can be selected! Clicking the function switch shows the parameter setting options at right in the Functions dialog. This function is activated by clicking the option next to the function button (the option turns green). When the function is run at a later time, only the green (activated) functions are taken into account. A Convert function can be combined freely with the Link or Split function. The Split function can only be used if all entries in the Input window are linked with the Link function or if there is only one entry in the Input window Page 9 e-h4x49

10 5.1 Linking files / data Link several input files/data With Link several input files/data in the Link dialog area, the file/data entries from the Input window can be parameterized to combine them together into a data record. The subsequent Convert functions determine which format the resulting file will have, whether Intel Hex, Motorola S-Record, Binary or Include. If there is overlapping data in the inputs to be linked, the last data input from the input window overwrites the overlapping data area from the previous input, as long as this is permitted by the Allowed option. Changes the sequence of inputs in the input window, thereby changing their priority. You can enter parameters in the parameter field Parameter of Function: Link input files / data. Overwriting dialog area Allowed: This option allows overlapping address ranges. No error message will be generated! Not allowed: This option disallows overlapping of address ranges between data to be linked. In this case, HEXit would stop the linking operation with the message Overlay Error. Opens the Placement of overlapping data dialog. The dialog shows a table containing the inputs whose addresses overlap. The start and end address are displayed. If the address ranges for the data to be linked do not overlap, then it does not matter whether the Allowed and Not allowed options were selected. Note: The Link several input files/data function can process data from the address space 0x0 to 0xFFFF FFFF. A maximum of 64 MB may be contained between the lowest and highest addresses Page 10 e-h4x49

11 5.2 Splitting files / data Split output Split output in the Split dialog area can split an input from the input window into several files. If there are several entries in the input area, these must be combined beforehand with Link several input files/data in the Link dialog area. The subsequent Convert functions determine which format the resulting target files will have, whether Intel Hex, Motorola S-Record, Binary or Include. You can enter the parameters in the Parameter of Function: Split parameter field. Split dialog area Number of output files: Determines the number of parts into which the input entry should be split. The start and end address of the new files are shown in the Output window. 5.3 Format Conversion to Intel Hex Convert to Intel Hex Using Convert to Intel Hex in the Convert dialog area, you can parameterize the file/data entries from the input window in order to convert them into the Intel Hex format. All of the entries in the input window are individually transferred into the Intel Hex format. If the option Link several input files/data was selected in the Link dialog area, the inputs are combined first and then changed into a single file in the Intel Hex format. You can enter the parameters for the output format in the parameter field Parameter of Function: Convert to Intel Hex. Output format dialog area Address type: The following addressing records are supported: 32 bit or 16 bit. Data-Byte per Line: The length of the data bytes per Intel Hex line in the file to be generated can be set here between 1 and 255. This setting has a major influence on the later size of the file Page 11 e-h4x49

12 5.4 Format Conversion to Motorola S-Record Convert to Motorola S-Record Using Convert to Motorola S-Record in the Convert dialog area, you can parameterize the file/data entries from the input window in order to convert them into the Motorola S-Record format. All of the entries in the input window are individually transferred into the Motorola S-Record format. If the option Link several input files/data was selected in the Link dialog area, the inputs are combined first and then changed into a single file in the Motorola S-Record format. 5.5 Format Conversion to Binary Convert to Binary You can enter the parameters for the output format in the parameter field Parameter of Function: Convert to Motorola S-Record. Output format dialog area Address type: The following addressing records are supported: 32 bit, 24 bit or 16 bit. Data-Byte per Line: The length of the data bytes per Motorola S-Record line in the file to be generated can be set here between 1 and 250. This setting has a major influence on the later size of the file. Using Convert to Binary in the Convert dialog area, you can parameterize the file/data entries from the input window in order to convert them into the Binary format. All of the entries in the input window are individually transferred into the Binary format. If the option Link several input files/data was selected in the Link dialog area, the inputs are combined first and then changed into a single file in the Binary format.. You can enter the parameters for the output format in the parameter field Parameter of Function: Convert to Binary Page 12 e-h4x49

13 5.6 Format Conversion to Include Convert to Include Using Convert to Include in the Convert dialog area, you can parameterize the file/data entries from the input window in order to convert them into the C-Include or ASM-Include format. The data from the input window are read in, byte for byte, without interpretation, and converted into a data field than can be processed by C compilers or assemblers. You can enter the parameters for the output format in the parameter field Parameter of Function: Convert to Include. Input format dialog area Input Format: If the Ignore option is checked, the data from the input window are read in without interpretation. Otherwise, the input formats are interpreted to Intel Hex or Motorola S-Record. All other formats are not interpreted. Syntax dialog area ANSI-C ucarray: Formatting of input entry into an unsigned char C-Include corresponding to one-byte (8 bit) formatting. ANSI-C uiarray: Formatting of input entry into an unsigned integer C-Include corresponding to one-word (16 bit) formatting. ASM DB: Formatting of input entry into a Defined Byte Assembler Include (8 bit). ASM DW: Formatting of input entry into a Defined Word Assembler Include (16 bit). Output format dialog area Hexadecimal: Hexadecimal output format. Decimal: Decimal output format. Output format Byte sequence dialog area MSB, LSB: Defines the byte sequence with the Most Significant Byte. MSB, LSB: Defines the byte sequence with the Least Significant Byte. Data byte per line: Length of data rows in the file to be generated. Example dialog area In this dialog, the dependencies in the current settings are shown with an example Page 13 e-h4x49

14 6 Output Results In HEXit s Output area, the settings for the outputs (data/crc) are made and the results are shown. The Output area is subdivided into three sectors: File settings: Defines address ranges for the output files CRC settings: Defines the CRC parameters for the files to be generated Info: Information about the files to be generated For every output generated in the Output area, the corresponding settings can be done separately in File settings or CRC settings area, and the results can be shown in the Info area. The selection of the individual outputs is done below the Output window. 6.1 File Settings After at least one input in the Input area and an output format in the Function area have been selected, the start and end addresses for each of the files to be produced can be entered separately under the File settings tab. Save from start address dialog area User defined: Saves the file from a selected start address. File defined: If the Link several input files/data function was not activated, the start address of the corresponding input entry is adopted. Otherwise, the start address from the link result is used. The calculated address can only be displayed after the Execute command has been run. Save up to end address dialog area User defined: Saves the file up to the calculated end address. File defined: If the Link several input files/data function was not activated, the end address of the corresponding input entry is adopted. Otherwise, the end address from the link result is used. The calculated address can only be displayed after the Execute command has been run Page 14 e-h4x49

15 6.2 Checksum Generation CRC settings The data for calculating the checksum can be entered separated in the CRC settings area for each of the files to be produced. Checksum generation is activated with the CRC checkbox. In the Type dropdown menu, you can choose from various checksum generation methods. By selecting User defined, the settings that were made under Settings/Program Settings in the User defined CRC Polynomial dialog area are applied. Calculate from start address dialog area User defined: Calculates the CRC from a selected start address. File defined: If the Link several input files/data function was not activated, the start address of the corresponding input entry is adopted. Otherwise, the start address from the link result is used. The calculated address can only be displayed after the Execute command has been run. Calculate up to end address dialog area User defined: Calculates the CRC from a selected end address. File defined: If the Link several input files/data function was not activated, the end address of the corresponding input entry is adopted. Otherwise, the end address from the link result is used. The calculated address can only be displayed after the Execute command has been run. Write CRC into file dialog area The resulting CRC can be written into any area of the file. Enable: Activates the function. Write CRC into file Place dialog area Address: The address after which the CRC should be written into the file. Write CRC into file Byte sequence dialog area Determines the byte sequence with MSB, LSB (Most Significant Byte) or LSB, MSB (Least Significant Byte). Note: If the resulting CRC is to be written into the file, you should make sure that the area into which the CRC should be written was excluded during CRC generation in the previous step. These are typically the last two bytes in a file Page 15 e-h4x49

16 6.3 File and CRC Results Info Information on the files and respective checksums can be called up separated in the Info area. File info dialog area Size: Size of the output file in bytes. Format: Selected output format (Intel Hex, Motorola S-Record, Binary or Include). Addr type: Selected addressing records. Data Byte/Line: The length of data bytes per Intel Hex and/or Motorola S-Record line in the file. Data rate: The percentage ratio to data size, derived from Data Byte/Line. CRC Info dialog area CRC Type: Selected type of checksum generation. CRC value: Checksum result Page 16 e-h4x49

17 7 Projects and Commands Automating Processes 7.1 Project Management All of the parameters for HEXit s functions can be managed via project files. The settings can be made in the Project navigation menu. New project: Create a new project. Open project: Loads the parameters of a previously created project. Save project: Saves the current parameters under the active project name. Save project as: The current settings can be saved under a project name. Close project: Closes the current project. Switch to the quick project overview. The last 6 projects are shown here and can be run from there with Execute. Switch back to the parameter environment. 7.2 Command Line Control When starting up, a project file can be "transferred" to HEXit and automatically executed. HEXit 4 supports the following command line parameters: PROJECT= Load project data when starting the program. AUTOSTART Run Execute after starting the program EXIT Quit the program after error-free execution. RETURN Always end the program after execution (even with errors). The Return code sends error numbers to the operating system. Error = 0 means that the execution was error-free. Example for a fully automated execution: <Path>/Hexit.exe PROJECT=j:\hexit4\MyProject1.hix AUTOSTART RETURN Page 17 e-h4x49

18 7.3 Settings Specific settings can be made via the navigation menu item Settings / Program Settings. Values: Value of undefined memory: Fills in a non-defined memory area with any value. A non-defined memory area arises whenever e.g. an Intel Hex file is converted into a Binary file and the jump instructions in the Intel Hex file create gaps in the Binary file. Default file extension of output file: Sets file extensions. User defined CRC Polynomial Sets CRC polynomials. Default name of include array Selection of an array s variable name. Messages: Sets various program parameters. Infos: Displays the working directory Page 18 e-h4x49

19 8 File Analyzer - Graphically Analyze Files Call File Analyzer: The File Analyzer enables you to conduct a comprehensive and quick analysis of an Intel Hex, Motorola S-Record or Binary file. The analysis is output in a graphical format so that the user can have a quick overview, even for large files. The Analyzer interprets the file s contents on the basis of the format specification (Intel Hex or Motorola S-Record) and displays them in a graphical representation. Every analyzed byte (word) is represented as a pixel in the graph. Depending on the analysis results, a color is assigned to the pixel. The Intel Hex, Motorola S-Record or Binary file is tested for: non-defined address ranges defined addresses defined addresses that were deleted (memory content 0x00 or 0xff) defined address ranges whose content is in the ASCII area addresses with data content of 0x00 and multiply defined addresses Page 19 e-h4x49

20 8.1 Basic Control Elements: Opens the file to be analyzed. The file can also be dragged into the analysis window by using drag & drop. Save the graphic in a bitmap. Print the graphic. Sets the visible range of the analyzed file. If the zoom function is set to Auto, the correct zoom factor is automatically set to display the entire file. Appears whenever the loaded file is larger than the area displayed in the graphic (the user has zoomed into the address range). You can navigate the graphic by clicking the arrow. Bar chart representation Page 20 e-h4x49

21 Status Bar Lowest Addr: Lowest address of the file shown Highest Addr: Highest address of the file shown Mouse Addr: Address and contents of the file on which the mouse pointer is currently located By clicking on any point in the graphic, the data are displayed numerically (in Hex and ASCII mode). Selecting a FLASH memory from a database can check whether an application will fit on a given FLASH memory. A window opens in which you can choose from approx. 500 different FLASH memories. The FLASH types can be sorted by manufacturer or size. The size and position of sectors are graphically displayed. If you click on a sector, you will find additional information about this sector in the status bar. Before the flash memory is selected, its arrangement in the bus system must be set so that the size of the sectors can be calculated for the graphical display. Bus modes: an 8-bit flash memory on an 8-bit data bus. a 16-bit flash memory on a 16-bit data bus. two 8-bit flash memories that are operated in tandem on a 16-bit data bus. Turns the selected FLASH component on and off. The black lines in the graphic show the position and size of the individual sectors graphically over the analyzed data. Note: It is not necessary to select a flash type if you do not want to display the sectors Page 21 e-h4x49

22 8.2 Analysis Filters Activation and deactivation of individual analysis steps (described below). In the graphic at left, all of the button elements are activated. Most of the time, however, only certain factors are of interest, and these can be displayed individually or in combination. The filters can be combined as desired. (None) Non-defined address ranges. (Used) Defined addresses. (Free) Defined addresses that were deleted (memory content 0x00 or 0xff). (Text) Defined address ranges whose content is in the ASCII range. (Variable) Addresses with a data value of 0x00. (Error) Multiply defined addresses Page 22 e-h4x49

23 8.3 Three Analysis Examples Analysis for single and double occupied address ranges: The following functions are required: Non-defined address ranges Defined addresses Error: Multiply defined addresses The large non-used range (light blue) is easy to see. The green areas represent the payload data, which is not interpreted further here. In the red area (at lower right and left in the graphic), the address range was multiply defined. This error can occur if for example additional data were in the Hex file that was actually meant to be stored later in RAM. IRQ Vectors: This shows which data in the start range (blue) were not defined. It is clear that several interrupt vectors were not defined. Unused Address Ranges: The blue ranges were not used by the linker. The frequency of gaps shows the degree of optimization in the compiler that was used Page 23 e-h4x49

24 8.4 Visualization of Individual Data Bytes The Analyzer can also be used to assess Intel Hex, Motorola S-Record, and Binary files down to the individual byte level. Switches the detail analysis. The user can choose between 8- or 16-bit command format (here 8- bit). All data bytes are shown in different colors. In the legend at the right of the window, the user can see the assignment of colors to data. In this example, you can very clearly see from the regular structures that either tables or graphics were saved here. exclusively. Individual files can be defined and shown In this example, only 0xCC00 (yellow) is shown. With this function, the user could search through the HEX file for specific Op codes (i.e.: 0xCC00 for NOP). In the example at left, the button for Non-defined address ranges was also activated Page 24 e-h4x49

25 9 Application Examples 9.1 Splitting an Intel Hex File An Intel Hex file (ca. 270k bytes) should be split in such a way that the first part fits into an internal flash memory on the MCU used (64k bytes). The second part of the file should be loaded into an external flash memory. Loading the source file (here over-test-ft01.hex). Address range 0x x0002 A001. Set Split output to Name the target file (here area01.hex). Splitting the first part for the internal address range: 0x x0000FFFF. 2. Name the target file (here area02.hex). Splitting the second part for the external address range: 0x x0002A001 Result: Source file over-test-ft01.hex Part 1 area01.hex Part 2 area02.hex for the internal FLASH memory for the external FLASH memory Page 25 e-h4x49

26 9.2 Exchanging the Range of a Binary Code A data range within a Binary file is to be exchanged with a data excerpt of the same size. In this example, a graphic in an executable file is exchanged with a graphic of the same size. In the first step, the old graphic is extracted from the Binary file. In the second step, the graphically altered file is re-integrated into the file. Step 1 Extract the data range from the Binary file: To swap the data ranges, the start and end addresses must be known. In this case, the exchange range was determined with the File Analyzer by searching for the start identification for the bitmap ( BM for bitmap). In this example, the start address is 0x05B84. The end address is 0x15BF9. Extracting the exchange range: Input: Load the Binary file (here Extract-1.exe). Function: Select the Convert to Binary function. Output: In the Save from start address dialog area, the start address of the data range to be exchanged is entered under User defined. In the Save up to end address dialog area, the end address of the data range to be exchanged is entered under User defined. The selected data range is written into a new file with Execute. Because Convert to Binary was selected, the data range is written into a Binary file Page 26 e-h4x49

27 In this example, the bitmap at left was extracted. Step 2 Integrate the new data range into the Binary file: In this example, the graphic that was abstracted in step 1 is changed before being re-integrated into the Binary file. In this example, we made sure that the file size was identical with the old file's size. Integrating the exchange range: Input Load the old Binary file (here Extract-1.exe). Load the exchange file (new_bitmap.bmp). The sequence of the input files in the list window is important because the last entry overwrites the previous one. Function Select the Link several input files/data function. Overwriting must be permitted by pressing the Allowed button. Select the Convert to Binary function. Output No additional settings need to be done in the Save from start address dialog area. The selected files are written into a new file with Execute. Because Convert to Binary was selected under Function, a Binary file is produced. The result, displayed in the File Analyzer Page 27 e-h4x49

28 9.3 Checksum Generation (CRC) A checksum is to be generated for a file. The checksum should be written together with the file s data into a new file. In this example, the file <source1.bin> occupies the address range 0x0000 0xFFFD. The CRC should be produced for this range and then written into the addresses 0xFFFE and 0xFFFF. Approach: Input area: The Add Data function in the input area generates a data cluster with a size of 64k bytes (address range 0x0000 0xFFFF) with a data content of 0xFF. The data cluster serves as the placeholder for the file and the CRC. Functions area: Link several input files/data in the Function area creates the link between the data cluster and the example file <source1.bin>. In the parameter field of several input files/data, data overwriting is permitted with Allowed. Important: The generated data cluster must come before the file <source1.bin> in the Input area s list window. The data cluster is then overwritten by the file. Output area File settings: The target file is saved over the entire address range 0x0000 0xFFFF. The process is started with Execute. Output area CRC settings: CRC calculation is activated. The CRC range to be calculated (0x0000 0xFFFD) is entered in the Calculate from start address and Calculate up to end address dialog areas. The position at which the CRC is to be saved (0xFFFE) is entered in the Write CRC to file dialog area Page 28 e-h4x49

29 9.4 Generating a Jump Table with the Data Generator This example shows that the Add Data function and the Fill pattern parameter can be used to generate executable machine code. The code generated in this example produces a jump table that enables the use of interrupt vectors in RAM to run applications in RAM, for example. To do this, the interrupt vectors must be forwarded from the flash memory into RAM. A jump table enables the use of interrupt vectors in address ranges that are different from those specified by the manufacturer, the MCU. The jump table described here applies to the XC167 processor family. The command for the interrupt vectors is: JMPS <Segment> <Address>. For the complete jump table, a series of 128 successive commands are required. Each command is 4 bytes long. The OP code for JMPS is 0xFA. The segment is 0xE0, because in this processor the segment 0xE0 is located in the internal program RAM. The address increases by 4 bytes after every jump command. The complete object code for the first command is: 0xFA, 0xE0, 0x00, 0x00. Byte 3 is the low byte of the jump target and byte 4 is the high byte of the jump target. The start address is 0x0000; the length is 128*4 bytes = 512 bytes; this results in an end address of 0x1FF. Byte 0 and byte 1 (FA and E0) are constants. The low byte is generated in that the address counter is linked with the FC logic AND. The pattern is: FA E0 &FC >8. To get the address s high byte, the address counter is moved 8 bits to the right. The data generator produces the following data record: Page 29 e-h4x49

30 10 HEXit Terms of Use LIMITED WARRANTY! By using HEXit and its auxiliary products, you agree to the following conditions of use. If you do not agree with these conditions, please notify us within two weeks of purchasing HEXit. LIMITED Warranty: hse-electronics GmbH guarantees for a period of 6 months after the date of receipt that HEXit will function in a manner that basically corresponds to our advertising, and that it will be free of errors under normal conditions of use. Customer CLAIMS: The entire liability of hse-electronics GmbH and their sole remedy consists of the following options, to be selected at the discretion of hse-electronics GmbH: a) refund of the price paid; or b) upgrade or replacement of the product. This limited warranty does not apply if the product failure is due to an accident, abuse, or erroneous use. NO additional guarantees: hse-electronics GmbH excludes all other warranties related to the delivered product and the manual and written documentation that belongs to it. NO liability for consequential damages: Neither hse-electronics GmbH nor the suppliers for hse-electronics GmbH are liable to compensate for any damages (including without limitation damages from lost profits, business interruption, loss of business information or data, or any other financial loss) arising from the use of this hse-electronics GmbH product, even if hse-electronics GmbH is notified of the possibility of such damages. LIMITED liability: The liability of hse-electronics GmbH is in every case limited to the amount that the customer has actually paid for the product. This exclusion does not apply to damages caused by premeditated action or gross negligence by hse-electronics GmbH. COURT OF JURISDICTION: The District Court of Kiel, Germany is the exclusive venue for all disputes arising from this licensing agreement If you have questions about this agreement, please contact your retailer or write an to info@hse-electronics.com. Kiel, Germany, January 9, Page 30 e-h4x49

31 11 HSE-Electronics Products Page 31 e-h4x49