No problem, really.
No problem, really.
Readers certainly know my ASM80 – online assembler / IDE for eight-bit processors. I made several derived versions, like single page compiler, embedded version of the translator (I used it in tutorial Stroják.cz), or a stand-alone IDE. The good old command line assembler is here now too.
The prerequisite you have to meet is a functional Node.js environment. It is not complicated, it exists for all major platforms, and you can download it here: nodejs.org. During installation, package manager called NPM is installed too.
NPM is used for install the packages and libraries. To install ASM80 itself just run a command prompt and type:
NPM i -g asm80
-g causes the asm80 will not be installed as a library, but as a system tool. Then toy can invoke it as a standard command line utility:
launches translation for file test.a80 and the result will be two files: test.hex with output and test.lst with the translation protocol. Extension .a80 tells the compiler to use the processor’s instruction set for Intel 8080 CPU.
Behaviour can be influenced by parameters. You can set the output file name, you can suppress the generation .lst, or explicitly determine the processor type and format of the output file (besides HEX and S record it can output .COM files for CP/M, .PRG for C64 emulators, or SNA and TAP for ZX Spectrum).
-o, --output <file>Output file name
-t, --type <type>Output type [default: hex]. Available types are: hex, srec, com (for CP/M), sna, tap (for ZX Spectrum), prg (for C64)
-n, --nolistSuppress listing (.lst file)
-m, --machine <type>Processor type, one of the following: Z80, I8080, C6502, C65816, CDP1802, M6800, M6809
-h, --helpSee HELP
Machine type can be omitted. Right CPU is determined by file name extension (-m option overrides this decision).
These parameters are described on page NPM package ASM80.
Overview of the syntax and directives can be found on GitHub Pages.
I still have a few suggestions for improvements, I would like to know your opinion …
Thanks for the tips and suggestions. You can send them straight to the GitHub Issues.