Difference between revisions of "MSXhex"

From MSX Game Library

(Command line options)
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
'''MSXhex''' is part of the [[Build tool]] process and convert .IHX files generated by SDCC into final binary file (.ROM, .COM or .BIN).
+
'''MSXhex''' is part of the [[Build tool]] process and convert .IHX files generated by the linker (SDCC) into final binary file (.ROM, .COM or .BIN).
  
 
The tool handle [[Create a mapped ROM|ROM mapper]] segment merging to take advantage of SDCC segment definition syntax.
 
The tool handle [[Create a mapped ROM|ROM mapper]] segment merging to take advantage of SDCC segment definition syntax.
  
 
== Command line options ==
 
== Command line options ==
<pre>
+
<syntaxhighlight lang="txt">
MSXhex 0.1.5 - Convert Intel HEX file to binary
+
MSXhex 0.1.13 - Convert Intel HEX file to binary
 
--------------------------------------------------------------------------------
 
--------------------------------------------------------------------------------
 
Usage: msxhex <inputfile> [options]
 
Usage: msxhex <inputfile> [options]
  
 
Options:
 
Options:
  -o filename   Output filename (default: use input filename with '.bin')
+
  -o filename         Output filename (default: use input filename with '.bin')
  -e ext         Output filename extension (can't be use with -o)
+
  -e ext             Output filename extension (can't be use with -o)
  -s addr       Starting address (default: 0)
+
  -s addr             Starting address (default: 0)
  -l length     Total data length (default: 0, means autodetect)
+
  -l length           Total data length (default: 0, means autodetect)
  -b length     Bank size (default: 0, means don't use)
+
  -b length           Bank size (default: 0, means don't use)
  -p value       Pading value (default: 0xFF)
+
  -p value           Pading value (default: 0xFF)
  -check         Validate records
+
  -r offset file      Raw data 'file' to add at a given 'offset'
  -log           Log records
+
--check             Validate each record using checksum
 +
  --log               Log each record
 +
--segcheck          Check if segment size does not exceed the bank size
 +
--segexcept num    Don't report oversize for this segment (can be use more than once)
 +
--segaddr seg addr  Base address of the given segment (can be use more than once)
 +
                    If no base address is supplied, autodetection is used.
 +
-help              Display this help
  
 
  All integers can be decimal or hexadecimal starting with '0x'.
 
  All integers can be decimal or hexadecimal starting with '0x'.
 
  One of the following named values can also be used:
 
  One of the following named values can also be used:
 
   1K, 2K, 4K, 8K, 16K, 24K, 32K, 48K, 64K, 128K, 256K, 512K, 1M, 2M, 4M, 8M, 16M, 32M, 64M
 
   1K, 2K, 4K, 8K, 16K, 24K, 32K, 48K, 64K, 128K, 256K, 512K, 1M, 2M, 4M, 8M, 16M, 32M, 64M
</pre>
+
</syntaxhighlight>
 +
[[Category:Tool]][[Category:MSXtk]]

Latest revision as of 16:20, 6 February 2025

MSXhex is part of the Build tool process and convert .IHX files generated by the linker (SDCC) into final binary file (.ROM, .COM or .BIN).

The tool handle ROM mapper segment merging to take advantage of SDCC segment definition syntax.

Command line options

MSXhex 0.1.13 - Convert Intel HEX file to binary
--------------------------------------------------------------------------------
Usage: msxhex <inputfile> [options]

Options:
 -o filename         Output filename (default: use input filename with '.bin')
 -e ext              Output filename extension (can't be use with -o)
 -s addr             Starting address (default: 0)
 -l length           Total data length (default: 0, means autodetect)
 -b length           Bank size (default: 0, means don't use)
 -p value            Pading value (default: 0xFF)
 -r offset file      Raw data 'file' to add at a given 'offset'
 --check             Validate each record using checksum
 --log               Log each record
 --segcheck          Check if segment size does not exceed the bank size
 --segexcept num     Don't report oversize for this segment (can be use more than once)
 --segaddr seg addr  Base address of the given segment (can be use more than once)
                     If no base address is supplied, autodetection is used.
 -help               Display this help

 All integers can be decimal or hexadecimal starting with '0x'.
 One of the following named values can also be used:
  1K, 2K, 4K, 8K, 16K, 24K, 32K, 48K, 64K, 128K, 256K, 512K, 1M, 2M, 4M, 8M, 16M, 32M, 64M