-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Needs to add raw binary output feature. #60
Comments
I second this request. I was trying to learn 8085 code to use on my Tandy Model 200, but it appears to be impossible to get the binary output I need from GNUSim8085. |
I've found another assembler written in python written by ept221 and I've
made a fork of it that makes it add buffer bytes when using ORG 0xXXXX.
I've also made a fork of GNUASM85 written by chandywerks so that it can
parse the output from pyasm as well as GNUsim and turn it into raw binary.
I also fixed a bug in GNUASM85.
My Forks:
https://github.com/RingingResonance/8085-Assembler
https://github.com/RingingResonance/GNUasm8085
Then it's just a matter of running a few commands:
python3 assembler.py sourceFile.asm -H -o code.list
./gnuasm85 code.list -o output.bin
It's messy, but it works pretty well.
…On Fri, Mar 25, 2022 at 1:45 AM hackerb9 ***@***.***> wrote:
I second this request. I was trying to learn 8085 code to use on my Tandy
Model 200, but it appears to be impossible to get the binary output I need
from GNUSim8085.
—
Reply to this email directly, view it on GitHub
<#60 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AET3MM5U72MI5JBUJJYQOBTVBVOH5ANCNFSM5GTAAY4Q>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Thanks for getting that working. It sounds like GNUSim8085 just needs to integrate the gnuasm85.c code to generate binary output. Right? Is there any licensing reason that GNUSim8085 couldn't include gnuasm85 with it? |
Honestly, I don't know why it was never added. I did look at the code for
gnusim and I'm not well versed enough in C to do the task of adding it into
that program, or at least I wasn't back when I last looked at that code
years ago. I might be able to do it now, but that IDE, if you can call it
that, is very limited compared to pyasm mentioned earlier so that's what I
use now. I think the original author just lost interest in the project
anyways. Shame as there aren't many free tools out there for Z80s, 8080s,
and 8085s. Nobody uses these anymore except the TI series calcs, a few
micro controllers, and enthusiasts looking to build or restore old
computers and equipment. They are fun and simple little CPUs though.
The author of pyasm is still pretty active, so that's what I recommend to
use now along with a way to parse it into raw binary code in some way. It
could all be done in python, but I'm even less well versed in python than I
am in C so I opted to edit GNUasm85 to do that for me as I had already
fixed one bug in it and therefore I kinda already knew how it worked. If
you haven't gotten it to work already, python is worth the trouble of
getting it to work as I'm sure you will need it in the future for other
stuff.
…On Sun, Mar 27, 2022 at 12:22 AM hackerb9 ***@***.***> wrote:
Thanks for getting that working. It sounds like GNUSim8085 just needs to
integrate the gnuasm85.c
<https://github.com/RingingResonance/GNUasm8085/blob/master/gnuasm85.c>
code to generate binary output. Right?
Is there any licensing reason that GNUSim8085 couldn't include gnuasm85
with it?
—
Reply to this email directly, view it on GitHub
<#60 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AET3MM5ZWKTLBO7IBDLK2J3VB7WA5ANCNFSM5GTAAY4Q>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Neat little program, but you need an option for raw binary output or at least raw hex code in txt format. I would prefer raw 8085 binary so I can just copy it over to a rom and be done with it. Thanks!
The text was updated successfully, but these errors were encountered: