![]() The compiler reported: Sketch uses 39314 bytes (15%) of program storage space. I moved the cave array into a text file called cave.txt and altered the code to use the text file as well as changing some variables from 16-bit integers to 8-bit integers. The text strings in advcave.h were first. So I moved away from the “all-in-one” option and looked into off loading game data onto the SD card. I had issues with that code as I discovered (after much searching) that storing data above the 64K barrier using PROGMEM was not advised as the C string handling routines didn't work on data above 64K. ![]() That resulted in 70-80K of downloadable code. The code used a pre-processor directive called BUILTIN to allow for a configuration where all the data was contained within the executable code. Global variables use 16256 bytes (198%) of dynamic memory, leaving -8064 bytes for local variables. Maximum is 253952 bytes.ĭata section exceeds available space in board I made some basic changes to read the game files from an SD card and disabled save and restore.Ī few tweaks and I got my first compilation without errors: Sketch uses 46488 bytes (18%) of program storage space. ![]() ![]() After some time I settled on the port that I found on Joachim Wiberg’s github page at GitHub - troglobit/advent4: Classic Colossal Cave Adventure I spent a bit of time searching for a port to C that would act as a suitable starting point for my attempt at an Arduino port. The original source code was written in ForTran of which I had a basic understanding of from my early days as a student. That got me thinking as to whether I could get Colossal Cave running on an Arduino. With the recent release of Colossal Cave 3D, it brought back memories of my early days in home computing and my first taste of interactive text adventures. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |