[Coco] DECB BIN file format

[Juan Castro]

D'OH! I moved a variable back and forth between it being an EQU and
being a pointer in my data area, and at some point I moved it to the
EQU section without changing it from FDB to EQU. Thanks!

On Wed, Dec 26, 2012 at 3:41 AM, William Astle <lost at l-w.ca> wrote:
> On 12-12-25 10:23 PM, Juan Castro wrote:
>>
>> I'm studying the BIN file format and found this:
>>
>> http://lwtools.projects.l-w.ca/manual/x24.html
>>
>> So I looked at the binary LWTOOLS generates for CaChars. Here's the
>> start of an hex dump of it:
>>
>> 00000000  00 00 02 00 00 f6 ad 00  08 25 77 d0 57 65 6c 63
>> |.........%w.Welc|
>> 00000010  6f 6d 65 20 74 6f 20 43  61 43 68 61 72 73 20 31  |ome to
>> CaChars 1|
>> 00000020  2e 34 2e 30 0d a9 20 32  30 31 32 20 4a 75 61 6e  |.4.0.. 2012
>> Juan|
>>
>> So... there's a block of 2 bytes that's being loaded at address 0000?
>> And those bytes are F6 AD? What's that for?
>>
>> The block that comes after that is my program, that's OK. The
>> postamble is intelligible too. But what's with that 2-byte block?
>
>
> That means you have something generating those two bytes with an orign of 0.
> Since it's the first block in the file, it's probably before the first ORG
> statement since the default origin is 0. Without seeing the source code, I
> can't make any more detailed comment except that it's likely to be a data
> statement of some kind (fdb, fcb, etc.) because F6 is "LDB extended" which
> is a 3 byte instruction so there's no way that could generate a 2 byte
> block.
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco