pees cara VBF Tool 2.2.0 With VBF Tool you can create and edit files conforming to the Versatile Binary Format (VBP), version 2.1, 2.2 or version 2.2 VBF Tool 2.2.0 Use VBF Tool Create, open or save a VBF document Edit a VBF document View a VBF document Browse a VBF document Glossary Motorola Intel Hex. Versatile Binary Format 2,1 Versatile Binary Format 2,2 Versatile Binary Format 2,3 VBF 2.1 File Example VBE 2.2 File Example VBE 2.3 File Example Change history -record, Use VBF Tool “reate, open or save a VBF document Edita VBF docu View a VBF document Browse a VBF document Create, open or save a VBF document New file Open file Close file ‘Save file Save as file Export to file Import from file Dump to file Import header from file New file On the File menu, click New. A sub menu with four alternatives will be visible: * VBF 2.1 STANDARD * VBF 2.1 EXTENDED VBF 2.2 STANDARD VBF 2.2 EXTENDED + VBF 2.3 STANDARD * VBF 2.3 EXTENDED Select requested version and frame format to create a new VBF document with a default header.‘Top Create open or savea VBE document Open file On the File menu click Open, and a file dialog is opened. The file extension is set to (VBF files), which means it fill only show vbf files. The extension filter can be changed in the popup-field Files of type. Browse the file of interest, select it, and click Open button. te LS 6 Lock in: [Give fles a S| eG ce [27 test_vBF20.vbF [EA Test_veF20_2.vbF [Eo tect_yer20_3.vbF Fiewre | Flesottes (Fverrvay ———S—S~SYS— ach T pene: readonly A Close file On the File menu, click Close. This closes the active VBF document. If there are unsaved changes, you are asked if you want to save first. ‘Top Clete open or eave a VF document Save file On the File menu, click Save. This saves the active VBF document with its current filename. Ifit is a new document, you are prompted for a filename. “ap Clue apn or ave a VBE document Save as file On the File menu, click Save As, choose a filename in the file dialog and click Save. Export to file This function exports the binary data of the VBF document to a file. To export file formats are supported; Motorola or Intel. On the File menu, click Export To File and click on either Intel or Motorola format. Choose a filename in the file dialog and press the Save button. ‘Top Crste open or save a VDF decuen! Import from file This function imports a binary into the active VBF document. The binary file can be of either Motorola or Intel binary format. VBF Tool automatically detects the format of the imported file when reading the first bytes. On the File menu, click Import From File. Choose a file in the file dialog and press the Open button. The file extension filter is by default set show Motorola and Intel binary files. The extension filter can be changed in the popup field Files of type.‘Top Create open or save a VBF document Dump to file This function dumps the contents of the VBF document to a readable text file. There are two options regarding the contents of the text file. + Header, block start address, block length and block checksum + Header, block start address, block length, block checksum and block data, On the File menu, click Dump To File, Choose a filename in the file dialog and press the Save button. ‘op hile open or ave a VBP document Import header from file This function reads the contents of a text file into the header of the active VBF document, The text in the file must conform to the VBF header format. On the File menu, click Import Header From File. Choose a filename in the file dialog and press the Open button. ‘Top Create,openor sive a VBE document Edit a VBF document Edit header Sort blocks Group blocks Align blocks Add area Delete inside area Delete outside area Atadd Edit header This function opens a text dialog box where you can edit the header of a VBF document. On the Edit menu, click Header. Edit the header and press the Ok button to store the changes in the VBF document. Top Edita VBE document Sort blocks This function sorts the blocks in a VBF document. The blocks are sorted after their start address in an ascending order. On the Edit menu, elick Sort Blocks. op Edita VBF cova Group blocks This function groups blocks that have adjacent data areas. On the Edit menu, click Group Blocks. ‘op Baile VBF document Align blocks This function takes to arguments; an align length and a fill value. It sets the size and the start address of the blocks to be a multiple of the align size. If two blocks have adjacent data areas, they are grouped into one block. To fill the new blocks with data up to their new size , they are padded with data bytes using the fill value. On the Edit menu, click Align Blocks, Enter an alignment size and a fill value, both in hexadecimal formats,Top Edita VBE document Add area This function adds a block with start address and length. On the Edit menu, click Add Area, Enter a start address, block size, fill data and press the OK, button. A block is created and filled bytes using the fill value. Tap lita VBE dosunens Delete inside area This function deletes a data area in the VBF document. This area can span over several blocks, On the Edit menu, click Delete Inside Area, Enter a start address and length of the data area to delete. ‘Top Edita VBE document Delete outside area This function deletes everything but a specified data area, This area can span over several blocks. On the Edit menu, click Delete Outside Area, Enter a start address and length of the data area not to delete, Top ills VBE cosas At address This function sets a byte value at a specific address. On the Edit menu, click At Address. Enter an address, a byte value, and press the OK button. Top Edit VBE dour, View a VBF document View header variables View header variables This function opens a text dialog that displays all the variables in the header. On the View menu, click Variables. op Views VBE document Browse a VBF document The content of the VBF document is displayed using a tree view and an information text box. Different parts of the VBF are represented as nodes in the treeview, with a node for the header and one node for each block. The block nodes also have a set of child nodes: start addres length, data and checksum. When a node is selected, information about that node is presented in the information text box. Error! Objects cannot be created from editing field codes. Glossary Motorola S-record Intel Hex Volvo Binary Format VBF File ExampleMotorola S-record Motorola 16-bit and 24-bit Format (S-record) Motorola 32-bit Format (S-record) Motorola 16-bit and 24-bit Format (S-record) Motorola data files may begin with an optional sign-on record, which is initiated by the start characters "S0”, Data records starts with an 8-character prefix and end with a 2-character suflix. Each data record begins with the start characters "S1” or "S2”, "S1” if the following address field has 4 characters, ”$2” if it has 6 characters. The third and fourth characters represent the byte count, which expresses the number of data, address and checksum bytes in the record, The address of the first data byte in the record is expressed by the last 4 characters of the prefix (6 characters for addresses above hexadecimal FFFF). Data bytes follows, each represented by 2 hexadecimal characters. The number of data bytes occurring must be 3 or 4 less than the byte count. The suffix is a 2-character checksum, which equals the one’s, complement (in binary) of the preceding bytes in the record, including the byte count, address and data bytes. The terminator record consist of the start characters "S9” (16-bit address) or "S8” (24-bit address), the byte count, the address (in hex) and a checksum. The maximum record length is 250 data bytes. A sample file is shown below. $00300004441544120492F4FF. $1130000FFFFFPFFFFFEFFFFFFFFEEEPEFEEFFEFFC s OFFFFFFFF EFSF FFFEFFFF! s EFFEFF FES? FEES? FEF! $1130030FF FFF PF FFFFFFFFFFFFFE PF FEPPFFFFFCC $1130040FFFFFPFFFFESFFFEFFFFEEEEEEEEEEEFBC 90300005 Some compiler/linker also produce a record-count-record. The record-count-record verifies the number of data records preceding it, See example. $503010DEE The example above shows a record-count-record indicating a total of 269 records, hexadecimal 010D and a checksum of hexadecimal EE. ‘Tap Motowla Second Motorola 32-bit Format (S-record) Motorola data files may begin with an optional sign-on record, which is initiated by the start characters “SO”. Data records starts with an 8-character prefix and end with a 2-character suffix. The Motorola 32-bit format closely remembers the Motorola 16- and 24-bit format, the main difference being the addition of the "S3” and "S7” start characters. The "S3” characters is used to begin a record containing a 4-byte address. The "S7” character is a termination record for block of "S3” records. A sample file is shown below. 00500004441544120492F4FF3 $31500000000AAS5AA55AAS5AAS SAAS SAASSAASSAASSF2 30D0000001 0AASSAASSAASSAASSE6 70500000000FC Some compiler/linker also produce a record-count-record, The record-count-record verifies the number of data records preceding it. See example.$503010DEE The example above shows a record-count-record indicating a total of 269 records, hexadecimal 010D and a checksum of hexadecimal EE. Top Motorola Second Intel Hex Intel Intellec 8 Format (Intel Hex) Intel Hex-32 Format Intel Intellec 8 Format (Intel Hex) Intel data records begin with a 9-character prefix and end with a 2-character suffix. The byte count must be equal the number of data bytes in the record. Each record begins with a colon, which is followed by a 2-character byte count. The 4 digits following the byte count give the address of the first data byte. Each data byte is represented by 2 hexadecimal digits, the number of data bytes in each record must be equal the byte count. Following the data bytes of each record is the checksum, the two's complement (in binary) of the preceding bytes (including the byte count, address record type and data bytes), expressed in hexadecimal. The end-of-file record consists of the “colon” start character, the byte count (equal to "00”), the address, the record type (equal to ”01”) and the checksum of the record, A sample file is shown below. aooo 00010 FRFEPEFEPPFF 0002 FFFEFFFEFFFE 0003 0004 0000 Intel Hex Intel Hex-32 Format The Intel 32-bit Hexadecimal Object file record format has a 9-character (4-field) prefix that defines the start of record, byte count, load address, record type and a 2-character checksum suflix. Example below illustrates the sample records of this format. 20000020000FC (Extended Segment Address Record) 20000040010EA (Extended Linear Address Record) 0000000FFFFEFFFFFFFFFFFFFFFFFFEFFFFFFFFF00 (Data Record) 0001000FFFFFFFFFFFFFFFF FFF FFF FFF FFFFFFEFO 0002000FFFFFFFFFF! FFFFEFFEEFEFFEFFEO 0003000FFFFEPFFEFFFFFFFFFFFFFFE 0004000 :00000001FF (End-of-File Record) The six record types are described below. 00 - Data Record This record begins with the colon start character, which is followed by the byte count (in hex notation), the address of the first data byte, and the record type (equal to 00), Following thes are the data bytes . The checksum follows the data bytes and is the two's complement (in binary) of the preceding bytes in the record, including the byte count, address, record type and data bytes. Top Titel Hex 01 - End RecordThis end-of-file record begins with the colon start character and is followed by the byte count (equal to 00), the address (equal to 0000), the record type (equal to 01) and the checksum, FF. ‘Top ele 02 - Extended Segment Address Record This is added to the offset to determine the absolute destination address. The address field for this record must contain ASCII zeros (hex 30). This record type defines bits 4 to 19 of the segment base address, it can appear randomly anywhere within the object file and affects the absolute memory address of subsequent data records in the file. The following example illustrates how the extended segment address is used to determine a byte address, Problem: Find the address for the first data byte for the following file. 102 0000 04 0010 EA 2 0000 02 1230 BA 0 0045 00 SSAA FF . BC Solution: Step 1 Find the extended linear address offset for the data record, (0010 in the example). Step 2. Find the extended segment address offset for the data record, (1230 in the example). Step 3. Find the address offset for the data from the data record, (0045 in the example), Step 4. Calculate the absolute address for the first byte of the data record as follows: 00100000 Linear offset, shifted left 16 bits 12300 Segment address offset, shifted left 4 bits 0045 Address offset from data record 0011234 32-bit address for first data byte The address for the first data byte is 112345. Top IntelHex 03 - Start Segment Address Record VBF Tool does not support this record, which specifies bits 4-19 of the execution start address for the object file ip lntLiss 04 - Extended Linear Address Record This record specifies bits 16-31 of the destination address for the data record that follows. It is added to the offset to determine the absolute destination address and can appear randomly anywhere within the object file. The address field of this record must contain ASCII zeros (hex 30). ‘Top Intelbiex 05 - Start Linear Address Record VBF Tool does not support this record, which specifies bits 16-31 of the execution start address for the object file. Top nel Hcx Versatile Binary Format 2.1The VBF-file consists of a header in ASCII followed by a binary part. The header in the file has variable length and use normal ”C-notation”. The reserved words in the header are: Reserved word vbf_version Header Description sw_part_number ‘sw_part_type network Ecu_address can_frame_format Description Version number of the Versatile Binary Format. Should always be: vbf_version = 2.1; Indicate start of the header section Optional description entry consisting of an array of strings. Max. 16 strings of 80 characters each. Example: description = ( “SOP software for S60 AND”, “Created: 2002-03-14" Software part number. A string of max 24 characters. Example: sw_part_number = “31808832 A”; Software part type. CARCKG = Car configuration CUSTOM = Custom parameters DATA = Data or parameters EXE = Executable GBL = Gateway bootloader SBL = Secondary bootloader SIGCFG = Signal configuration Example: sw_part_type = SIGCFG; ‘Network for software download operation CAN_HS = main network @ 500 kbit/s CAN_MS = main network @125 kbit/s SUB_MOST = MOST sub network connected to a gateway SUB_CANI = CAN sub network connected to a gateway SUB_CAN2 = CAN sub network connected to a gateway SUB_LINI = LIN sub network connected to a gateway SUB_LIN2 = LIN sub network connected to a gateway Examples: network = CAN_HS; network = { CAN MS, SUB_MOST }; Indicates the physical ECU address to a node on a main network or a node on a main network and a sub network. Valid values for addresses are 00-FF Examples: // main node with address 0x51 ecu_address = 0x51; // main node (gateway node) address 0x54, // sub node address 0x65 ecu_address = { 0x54, 0x65 } ‘The can_frame_format entry indicates if standard frame format (I -bit CAN identifers) or extended frame format (29-bit CAN identifiers) shall used for requests and respones to an ECU on a main network. The following identifiers are valid. STANDARD = standard frame format, Li-bit CAN identifiers EXTENDED = extended frame format, 29-bit CAN identifierserase Flash memory to erase before a software download can take plac Example: // Two blocks: 0x4200-O7EBF, 0x8010, 0xB003 erase = { { 0x4200, Ox3CBF }, { 0x8010, Ox2FF3 } ve call Start address of a pre-defined executable function in the ECU memory. Example: call = 0x0100 checksum_table Checksum table with start address, stop address and checksum, Used for Software Security Example: checksum_table 0x8000, OxBFFF, Ox1c 0x8002, OxBFFD, OxAF 0x8010, OxBFFO, 0x43 0x8020, OxBFEO, 0x85 File_checksum A four byte CRC32 file checksum. Example: #ile checksum = 0x29058C73; The header starts with the reserved word header followed by a”{”" character. The header ends with a”} "character. Immediate after the ””}”” character binary data follows. The binary data are stored in the following way: Start address in 4 bytes, binary Block I memory Length of data 4 bytes, binary block Data n bytes, binary Checksum 2 byte, binary Start address in 4 bytes, binary Block 2 memory Length of data 4 bytes, binary block Data n bytes, binary Checksum 2 byte, binary Start address 4 bytes, binary Block 3 In many cases data will not be placed in continuous address space. To handle this data can be split into blocks, as shown above. Start address and Length are stored with most significant byte first. Checksum is calculated with CRC16-CITT checksum, Only the n bytes data are included in the checksum calculation not the start address and length. ‘Top Versatile Binary Format 2 Versatile Binary Format 2.2 The VBF-file consists of a header in ASCII followed by a binary part. The header in the file has variable length and use normal ”C-notation”. The reserved words in the header are: Reserved word Description vbf_version Version number of the Versatile Binary Format, ShouldHeader Description sw_part_number ‘sw_part_type Network Ecu_address frame_format Erase always be: vbf_version = 2.2; Indicate start of the header section Optional description entry consisting of an array of strings. Max. 16 strings of 80 characters each. Example: description = { “SOP software for S60 AWD”, “Created: 2002-03-14" Mi Software part number. A string of max 24 characters. Example: ew_part_nunber Software part type. 31808832 a”; CARCFG = Car configuration CUSTOM = Custom parameters DATA = Data or parameters EXE = Executable GBL = Gateway bootloader SBL = Secondary bootloader SIGCFG = Signal configuration TEST=Test program Example: sw_part_type = SIGCFG; Network for software download operation CAN_HS = main network @ 500 kbit/s CAN_MS = main network @125 kbit/s SUB_MOST = MOST sub network connected to a gateway SUB_CANI = CAN sub network connected to a gateway SUB_CAN2 = CAN sub network connected to a gateway SUB_LIN1 = LIN sub network connected to a gateway SUB_LIN2 = LIN sub network connected to a gateway SUB_OTHER = Other sub network connected to a gateway. Examples: network = CAN HS; network = { CAN MS, SUB_MOST }; Indicates the physical ECU address to a node on a main network or a node on a main network and a sub network. Valid values for addresses are 00-FF Examples: // main node with address 0x51 ecu_address = 0x51; // main node (gateway node) address 0x00, // sub network addr. 0x06 sub node addr 0x65 ecu_address = { 0x00, 0x06, 0x65 } The frame_format entry indicates if standard frame format (11-bit CAN identifers) or extended frame format (29-bit CAN identifiers) shall used for requests and respones to an ECU on a main network. The following identifiers are valid. CAN_STANDARD = standard frame format, Li-bit CAN identifiers CAN_EXTENDED = extended frame format, 29-bit CAN identifiers Flash memory to erase before a software download can take place. Example:/1 ‘Two blocks: 0x4200-O7EBF, 0x8010, 0xB003 erase = { { 0x4200, Ox3CBF }, { 0x8010, Ox2FF3 } de Call Start address of a pre-defined executable function in the ECU memory. Example: call = 0x0100 checksum_table Checksum table with start address, stop address and checksum. Used for Software Security Example: checksum_table 0x8000, OxBFFF, Ox1c }, 0x8002, OxBFED, OxAF }, 0x8010, OxBFFO, 0x43 }, 0x8020, OxBFEO, 0x85 } y File_checksum A four byte CRC32 file checksum. Example: file_checksum = 0x29058C73; The header starts with the reserved word header followed by a”{”" character. The header ends with a"} "character. Immediate after the *""}"” character binary data follows. The binary data are stored in the following way: Start address in 4 bytes, binary Block | memory Length of data 4 bytes, binary block Data nbytes, binary Checksum 2 byte, binary Start address in 4 bytes, binary Block 2 memory Length ofdata 4 bytes, binary block Data n bytes, binary ‘Checksum 2 byte, binary Startaddress 4 bytes, binary Block 3 In many cases data will not be placed in continuous address space. To handle this data can be split into blocks, as shown above. Start address and Length are stored with most significant byte first. Checksum is calculated with CRC16-CITT checksum, Only the n bytes data are included in the checksum calculation not the start address and length. ‘Top Merstile Binary Formal 22 Versatile Binary Format 2.3 The VBF-file consists of a header in ASCII followed by a binary part. The header in the file has variable length and use normal *C-notation”” The reserved words in the header are: Reserved word Description vbf_version Version number of the Versatile Binary Format. Should always be: vbf_version = 2.3;Header Description sw_part_number ‘sw_part_type Network Ecu_address frame_format Indicate start of the header section Optional description entry consisting of an array of strings. Max. 16 strings of 80 characters each. Example: description = { “SOP software for S60 AWD”, “Created: 2002-03-14" ds Software part number. The sw_part_number identifier can have either one or two identifier values assigned. If there is only one identifier value assigned, it shall be either WERS or KDP part number. If there are two identifier values assigned, the first value shall always be WERS part number, and the second value shall always be KDP part number. A string of max 24 characters. Example (Both WERS & KDP numbers): sw_part_number = ("YW47-13B525-AB", 31808832aB"}; Software part type. CARCFG = Car configuration CUSTOM = Custom parameters DATA = Data ot parameters EXE = Executable GBL = Gateway bootloader SBL = Secondary bootloader SIGCFG = Signal configuration TEST=Test program Example: sw_part_type = SIGCFG; Network for software download operation CAN_HS = main network @ 500 kbit/s CAN_MS = main network @125 kbit/s SUB_MOST = MOST sub network connected to a gateway SUB_CANI = CAN sub network connected to a gateway SUB_CAN2 = CAN sub network connected to a gateway SUB_LINI = LIN sub network connected to a gateway SUB_LIN2 = LIN sub network connected to a gateway SUB_OTHER = Other sub network connected to a gateway. Examples network = CAN_HS; network = { CAN MS, SUB_MOST }; Indicates the physical ECU address to a node on a main network or a node on a main network and a sub network. Valid values for addresses are 00-1 Examples: // main node with address 0x51 ecu_address = 0x51; // main node (gateway node) address 0x00, // sub network addr. 0x06 sub node addr 0x65 ecu_address = ( 0x00, 0x06, 0x65 } The frame_format entry indicates if standard frame format (11-bit CAN identifers) or extended frame format (29-bit CAN identifiers) shall used for requests and respones to an ECU on a main network. The following identifiers are valid. CAN_STANDARD = standard frame format, Li-bit CAN identifiersCAN_EXTENDED = extended frame format, 29-bit CAN identifiers Erase Flash memory to erase before a software download can take place, Example: // two blocks: 0x4200-O7EBF, 0x8010, 0xB003, erase = { ( 0x4200, 0x3CBF }, (028010, Ox2FF3 } Mi Omit Range(s) of memory that should be manually deleted by the VBF parser from both the erase entry identifier (if present) in the header section as well as the data section. Example: omit = ( { 0x00008000, 0x00001000 } }; Call Start address of a pre-defined executable function in the ECU memory. Example: call = 0x0100 checksum_table Checksum table with start address, stop address and checksum, Used for Software Security Example: checksum_table = ( { 0x6000, OxBFFF, Ox1C }, { 0x8002, OxBFED, OxAF ), { 0x8010, OxBFFO, 0x43 ), { 0x6020, OxBFEO, 0x85 } ye File_checksum —_A four byte CRC32 file checksum Example: file checksum = 0x29058C73; ‘The header starts with the reserved word header followed by a”{”" character. The header ends with a} "character. Immediate after the """}"” character binary data follows. The binary data are stored in the following way: Start address in 4 bytes, binary Block 1 memory Length of data 4 bytes, binary block Data nbytes, binary Checksum 2 byte, binary Start address in 4 bytes, binary Block 2 memory Length ofdata 4 bytes, binary block Data n bytes, binary Checksum, 2 byte, binary Start address 4 bytes, binary Block 3 In many cases data will not be placed in continuous address space. To handle this data can be split into blocks, as shown above. Start address and Length are stored with most significant byte first. Checksum is calculated with CRC16-CITT checksum, Only the n bytes data are included in the checksum calculation not the start address and length. ‘Top Versatile Binary Formal 23 VBF 2.1 File Examplevolve car Corpor VBP Tool ver. 2.1 example file ue omnes ue 17 application program for the DIM. “ Jeanwnnees 17 softuare part aumber ow part somber = "96765432" 11 Software part type: Exeovtable Su_part_tipe © 11 S00 address used for: DIM Driver Information Module ees address = Ox517 1) 25-pa CAM dont sion 11 stazt address for flash sect erase = { { 0x2000, 01200 ty 4 ox400a, Ox200 4, 1 Ox6000, 0x200 1" bs 11 coackaum tabie Start stop chesksun checkaun tabie'~ ( ( 048000, OxBFEE, Oxie 08002, ORBEED, OxaE 3 Ox8910, OxBFEO, Ox43 1, 08020, ORBFED, 0x85 , M7 Blocks: 24 1 Bytes: 2108 #lle-checksun ~ 0x29058C73: ) binary deem Top VBF2.1 File Example VBF 2.2 File Example header { ue ae volve Car Corporation a i) vee convert ver, 2.1 example file ue Oe po wor EDrS ue ue Connents uw 17 application progzan. for the DIM ue 1 software part number 5y_part_comber 1 Software pas aw_part. typ // B00 address used for: DIM Driver Information Module: ecu address = 0x51;(0 29-bit CaN sdentisier Erane format = CAN EXTENDED: 1 Start address for flash se: erase { { 012009, 01200 |, 1 dxe000, 0x20 1, { ox6000, 03200 1) 11 Checksum tabie: Start stop Checksum checksum table ~ ( ( 0x8000, OxBPFF, OxIC hy (038002, OXBFED, OXAF 3, ( 0x8010, OxBFFO, Ox43 3) (038020, OXSFED, 0385 {1 Blocks: 24 1 aytes: 2108 file checksum = 0429058073; ) binary aata> Top VBE22 File Example VBF 2.3 File Example vbf_version=2.31 header { ie faknwnnnen we vie we Wit WBE Convers we vie bo Nor EDIT | we we Comments “ 77 Application program for the OTM “ 11 software part number Sw pare _noner = "987 3283 (1 Software pact type: Exeoutable Su_part_lype > J BCU address used for: DIM Driver Information Module ecu address ~ 0x51; 1 28-bit CaM sdentifier 1 Start address for flash sector te) erase { { 0x2000, 01200 }, 1 5e4000, e200 1, 1 9x6000, 0x200 1} 1 omit information ” start, length omit = { { 0x00008000, 0x00001000 } 1; 11 Checksum tabe: Start stop Checksum checksum tabi 0x8000, OXSFFF, OnIC 3, 048002, OXSFED, OXAF 5 Ox8910, OXBFFO, Oxt3 048020, OXSFEO, OxES (Blocks: 24 20s _ehecksun = 0x29058C73; ) binary data> Top VBE23 FileExample Change history Version 2.2.0 12 Mar 2007‘* Updated to conform to Versatile Binary Format 2.3 specification, Version 2.1.3 1 Oct.. 2005 © Add Area / Delete Inside Area corrections Version 2.1.2 1 May.. 2005 Updated to conform to Volvo Binary Format 2.2 specification. New sub menu options (File\New\VBF2.x) available to select what version to create. © Menu option File\Select can_frame_format removed ‘© Toolbar button New creates VBF 2.2 STANDARD files as default. Version 2.1.1 18 Aug.. 2004 * Correction for “Delete inside area” of I-byte large blocks. © Correction regarding addresses close to 0xFFFFFFFF (Motorola $19 files) Version 2.1 30 Jan. 2004 © Updated to conform to Volvo Binary Format 2.1 specification. « New menu option (File \ Select can_frame_format) which sets the default can_frame_format (STANDARD or EXTENDED) ‘© Support for viewing of both 2.0 and 2.1 VBF files. «Fixed error regarding Extended Linear Address in combination with Extended Segment Address (IntelHex). Version 2.0 30 Apr. 2002 ‘© Updated to conform to Volvo Binary Format 2.0 specification. A help file has been added. All number inputs in dialogs are hexadecimal. ‘No need to specify file format when importing binary files. The format is detected automatically when reading the file ‘New function Import From Header. New function Align blocks. File checksum is 32 bit CRC. Block checksum is CRC16-CITT. More strict type checking in VBF header. Extended default generation of header. More parameters included by default Data browsing can now be done for large blocks, provided that the internal memory of the system is large enough. ‘© Now supports large blocks, 32 bit lengths, Fixed minor bug, Group Block with no blocks, previously generated one empty block. Automatically updates file_checksum in header when saving VBF. © Converted to Visual Basic 6.0. ‘Top Changs history