mirror of
https://github.com/fadden/6502bench.git
synced 2024-11-06 12:04:39 +00:00
4b46b78e34
Copied the extension script tutorial files out of the Scripts directory and into the Tutorial directory. This makes more sense, and makes it possible to expand the script sample without altering the tutorial. Reverted the Scripts sample to be an actual sample, rather than a tutorial. Renumbered the last two tutorials and added them to the ToC. This gives them actual numbers rather than treating them as add-ons to the advanced tutorial. Moved the source files for the tutorial binaries into a subdirectory to reduce clutter. This does mean we have two separate copies of the inline string sample plugins, but that's an artifact of our attempts at security. |
||
|---|---|---|
| .. | ||
| A2-Amper-fdraw | ||
| A2-HP-CDA | ||
| A2-lz4fh | ||
| A2-Zippy | ||
| Scripts | ||
| Tutorial | ||
| README.md | ||
SourceGen Examples
These are some sample projects you can play with. The binaries are accompanied by the original source code, so you can compare the SourceGen project to the original.
- Tutorial: simple projects, intended for use with the tutorial in the manual.
- Scripts: extension script samples.
- A2-lz4fh: two functions for unpacking a simplified form of LZ4 compression. One is 6502, the other is 65816. This is pretty straightforward. (Full project)
- A2-Amper-fdraw: 6502 code that provides an Applesoft BASIC interface to a machine-language graphics library. The public interface of the graphics library is defined in a .sym65 file. This example has multiple entry points in a jump table, and is used to demonstrate address table formatting in the advanced tutorial. (Full project)
- A2-Zippy: a program for controlling an Apple IIgs CPU accelerator card. 65816 sources, with a little bit of ProDOS 8 and IIgs toolbox usage. Demonstrates how extension scripts are used during analysis. (Full project)
- A2-HP-CDA: HardPressed Classic Desk Accessory. This is 65816 code in OMF loader format, which SourceGen doesn't support, so it's a little rough. (This is chiefly here to answer the question, "what does it look like when you disassemble OMF binaries?") (Full project)
(You may be wondering why some of the example files have filenames with things like "#061d60" in them. It's a method of preserving the file type for Apple II files used by some utilities. The potential advantage for disassembly is that the file type often determines the load address, possibly removing some initial guesswork.)