Executable binary file - Revision history

Stef at 22:19, 3 March 2022

2022-03-03T22:19:48Z

Stef at 22:18, 3 March 2022

2022-03-03T22:18:14Z

Grenouye: /* PGZ */

2021-08-18T02:06:50Z

‎PGZ

Grenouye: /* PGX */

2021-08-18T02:06:33Z

‎PGX

PJW: /* PGZ */

2021-08-09T15:52:06Z

‎PGZ

PJW: /* PGX */

2021-08-09T15:43:39Z

‎PGX

PJW: /* PGX */

2021-08-09T15:43:14Z

‎PGX

PJW: Created page with "The '''F_RUN''' and '''F_LOAD''' kernel calls supports multiple binary formats. If you try to load a file in one of these formats without specifying a starting address, it wil..."

2021-08-09T15:40:02Z

Created page with "The '''F_RUN''' and '''F_LOAD''' kernel calls supports multiple binary formats. If you try to load a file in one of these formats without specifying a starting address, it wil..."

New page

The '''F_RUN''' and '''F_LOAD''' kernel calls supports multiple binary formats. If you try to load a file in one of these formats without specifying a starting address, it will be loaded into the locations specified in the file. If you try to run a file in one of these formats, the file will be loaded into memory and executed.

== PGX ==

PGX is a simple, single segment format akin to Commodore's PRG format. The file starts with an eight byte header, followed by the contents to be loaded into memory. The header consists of three parts:

* The first three bytes are the ASCII codes for "PGX", serving as a file type signature.
* The fourth byte is the CPU code, indicating the target CPU. Currently, only the value $01 is supported and designates that the 65816 is the target CPU.
* The final four bytes of the header are the starting destination address in little-endian format. This address will be the location to store the first byte of the data (which is the ninth byte of the file).

== PGZ ==

PGZ is a multi-segment file format that can load data into multiple areas in memory. The format is derived from binary format used by Western Design Center's C compiler.

* The first byte of the PGZ format is the ASCII code for "Z". This serves as the file type signature.
* Next comes any number of segments, each following right after the previous segment with no separator. Each segment has the following format:
** Three bytes of address, in little endian format. This is the starting address for writing the data of the segment.
** Three bytes indicating the size of the segment, in little endian format.
** The bytes of data in the segment (same number of bytes as specified in the size).
* If final segment has a size of $000000 and no data bytes, then address specifies the starting address of the executable.

@@ Line 49: / Line 49: @@
 | 22 || ... || ... || Data of Segment #2
 |-
-|rowspan="2"| START || 30 || 3 || $010000 || Starting address
+|rowspan="2"| 3 || 30 || 3 || $010000 || Starting address
 |-
 | 33 || 3 || $000000 || 0 to indicate start address
 |}

@@ Line 12: / Line 12: @@
 ! Offset !! Count !! Example !! Purpose
 |-
-| 0 || 3 || "PGZ" || Signature
+| 0 || 3 || "PGX" || Signature
 |-
 | 3 || 1 || $01 || CPU

← Older revision		Revision as of 15:52, 9 August 2021
Line 31:		Line 31:
	** The bytes of data in the segment (same number of bytes as specified in the size).		** The bytes of data in the segment (same number of bytes as specified in the size).
	* If final segment has a size of $000000 and no data bytes, then address specifies the starting address of the executable.		* If final segment has a size of $000000 and no data bytes, then address specifies the starting address of the executable.
		+
		+	{\| class="wikitable"
		+	! Segment !! Offset !! Count !! Example !! Purpose
		+	\|-
		+	\| N/A \|\| 0 \|\| 1 \|\| "Z" \|\| Signature
		+	\|-
		+	\|rowspan="3"\| 1 \|\| 1 \|\| 3 \|\| $010000 \|\| Address of segment #1
		+	\|-
		+	\| 4 \|\| 3 \|\| $000009 \|\| Size of segment #1
		+	\|-
		+	\| 7 \|\| ... \|\| ... \|\| Data of Segment #1
		+	\|-
		+	\|rowspan="3"\| 2 \|\| 16 \|\| 3 \|\| $020000 \|\| Address of segment #2
		+	\|-
		+	\| 19 \|\| 3 \|\| $000008 \|\| Size of segment #2
		+	\|-
		+	\| 22 \|\| ... \|\| ... \|\| Data of Segment #2
		+	\|-
		+	\|rowspan="2"\| START \|\| 30 \|\| 3 \|\| $010000 \|\| Starting address
		+	\|-
		+	\| 33 \|\| 3 \|\| $000000 \|\| 0 to indicate start address
		+	\|}

@@ Line 14: / Line 14: @@
 | 0 || 3 || "PGZ" || Signature
 |-
-| 4 || 1 || $01 || CPU
+| 3 || 1 || $01 || CPU
 |-
-| 5 || 3 || $010000 || Destination Address
+| 4 || 4 || $010000 || Destination Address
 |-
 | 8 || - || $00 $01 $02 ... || The data to load

@@ Line 26: / Line 26: @@
 * The first byte of the PGZ format is the ASCII code for "Z". This serves as the file type signature.
-* Big "Z" = 24bits Addresse Pointers and Sizes. Small "z" = 32bits Addresse Pointers and Sizes.
+<span style="color:red">* Big "Z" = 24bits Addresse Pointers and Sizes. Small "z" = 32bits Addresse Pointers and Sizes.</span>
 * Next comes any number of segments, each following right after the previous segment with no separator. Each segment has the following format:
 ** Three bytes of address, in little endian format. This is the starting address for writing the data of the segment.

@@ Line 9: / Line 9: @@
 * The final four bytes of the header are the starting destination address in little-endian format. This address will be the location to store the first byte of the data (which is the ninth byte of the file).
+{| class="wikitable"
 == PGZ ==