EASy68K  
It is currently Wed Apr 26, 2017 11:26 pm

All times are UTC




Post new topic Reply to topic  [ 10 posts ] 
Author Message
 Post subject: Binary file
PostPosted: Tue Nov 11, 2008 7:28 pm 
Offline
User avatar

Joined: Thu Dec 16, 2004 6:42 pm
Posts: 1036
Location: Monroe County Community College, Monroe Michigan, U.S.A.
Remove Teeside header from binary file.
Add option to pad with user specified byte.

_________________
Prof. Kelly


Top
 Profile  
 
 Post subject:
PostPosted: Tue Jan 20, 2009 4:43 pm 
Offline
User avatar

Joined: Thu Dec 16, 2004 6:42 pm
Posts: 1036
Location: Monroe County Community College, Monroe Michigan, U.S.A.
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?

_________________
Prof. Kelly


Top
 Profile  
 
 Post subject:
PostPosted: Tue Jan 20, 2009 9:03 pm 
Offline

Joined: Mon Apr 11, 2005 12:57 am
Posts: 27
Location: Australia
Hi,

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.

Kenneth


Top
 Profile  
 
 Post subject:
PostPosted: Wed Jan 21, 2009 6:50 pm 
Offline
User avatar

Joined: Thu Dec 16, 2004 6:42 pm
Posts: 1036
Location: Monroe County Community College, Monroe Michigan, U.S.A.
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.

_________________
Prof. Kelly


Top
 Profile  
 
 Post subject:
PostPosted: Wed Jan 21, 2009 8:38 pm 
Offline

Joined: Mon Apr 11, 2005 12:57 am
Posts: 27
Location: Australia
Hi,

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.

Kenneth


Top
 Profile  
 
 Post subject:
PostPosted: Thu Jan 22, 2009 5:01 am 
Offline
User avatar

Joined: Thu Dec 16, 2004 6:42 pm
Posts: 1036
Location: Monroe County Community College, Monroe Michigan, U.S.A.
Yes, I was considering adding the option to split the data into multiple files for 2 EPROM and 4 EPROM configurations.

_________________
Prof. Kelly


Top
 Profile  
 
 Post subject:
PostPosted: Fri Jan 23, 2009 2:29 am 
Offline

Joined: Mon Apr 11, 2005 12:57 am
Posts: 27
Location: Australia
That would about cover the requirements for me at this time.

Will look forward to testing it when available.

Kenneth


Top
 Profile  
 
 Post subject:
PostPosted: Fri Jan 23, 2009 3:04 pm 
Offline
User avatar

Joined: Thu Dec 16, 2004 6:42 pm
Posts: 1036
Location: Monroe County Community College, Monroe Michigan, U.S.A.
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.

_________________
Prof. Kelly


Top
 Profile  
 
 Post subject:
PostPosted: Sat Jan 24, 2009 9:24 am 
Offline

Joined: Mon Apr 11, 2005 12:57 am
Posts: 27
Location: Australia
Hi,

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

Kenneth


Top
 Profile  
 
 Post subject: Re: Binary file
PostPosted: Mon Jan 25, 2016 10:58 pm 
Offline
User avatar

Joined: Wed Jan 06, 2016 9:24 am
Posts: 4
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!


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 10 posts ] 

All times are UTC


Who is online

Users browsing this forum: Baidu [Spider] and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group