Binary file
Page 1 of 1

Author:  profkelly [ Tue Nov 11, 2008 7:28 pm ]
Post subject:  Binary file

Remove Teeside header from binary file.
Add option to pad with user specified byte.

Author:  profkelly [ Tue Jan 20, 2009 4:43 pm ]
Post subject: 

I'm looking at changing the binary file and I would like opinions:

1. Does anyone use the current binary file?

2. What data should a binary file contain?

Author:  kkeeley [ Tue Jan 20, 2009 9:03 pm ]
Post subject: 


I use binary files at times, I haven't used it from EASy68k as of yet.
It would be nice if it could be compatible with burning straight to ROM for example. That would reduce the requirement to have a ROM burner software that handles S-Records, It would also allow for easy downloading to a device via serial or other methods.


Author:  profkelly [ Wed Jan 21, 2009 6:50 pm ]
Post subject: 

Here is my current thinking on the binary file format.

The current binary file is patterned after the Teesside Assembler which contains header data, address information and binary data. This format does not seem to be useful for EPROM programming.

I propose creating a binary file that contains only binary data. Options will be provided to help format the file for EPROM programmers such as:

Start - The address of the first item placed in the file.
Fill - The byte used to fill in empty areas of the file.
Length - Force the file to this length.

Author:  kkeeley [ Wed Jan 21, 2009 8:38 pm ]
Post subject: 


I think your plans should work fine.

Would it also be possible to include the option to create different bit count binnary files. ie all data in one file, data split into odd and even so it's compatible with 68K 16-bit hardware, data split into 4 files so it's compatible with 68k 32-bit hardware, etc.


Author:  profkelly [ Thu Jan 22, 2009 5:01 am ]
Post subject: 

Yes, I was considering adding the option to split the data into multiple files for 2 EPROM and 4 EPROM configurations.

Author:  kkeeley [ Fri Jan 23, 2009 2:29 am ]
Post subject: 

That would about cover the requirements for me at this time.

Will look forward to testing it when available.


Author:  profkelly [ Fri Jan 23, 2009 3:04 pm ]
Post subject: 

Once I got into doing some of the coding I decided to take a slightly different approach.

EASy68K will create a listing file (.L68) and an S-Record file (.S68)

I'm writing a separate utility that will load S-Record files and create binary files (.BIN). Options will be available for splitting the data into multiple files, specifying the fill byte, etc.

The current binary file format that EASy68K supports will be removed. It is designed for use with the Teesside simulator and I see no reason to continue creating it.

Author:  kkeeley [ Sat Jan 24, 2009 9:24 am ]
Post subject: 


That sounds fine, I will wait and see what it's like before making any further coments


Author:  RyanFaeScotland [ Mon Jan 25, 2016 10:58 pm ]
Post subject:  Re: Binary file

Hello Professor, from what I can see Easy68K is still generating a header. Is there an option to disable this or was it never actually removed?

EDIT - Nevermind, I was using an outdate version of Easy68K, now that I have the latest version I see what the above post about creating the S files and generating a BIN from them refers to. Thanks!

Page 1 of 1 All times are UTC
Powered by phpBB® Forum Software © phpBB Group