That's what stacks are good at. They just take care of the allocation problems automatically with no waste of memory. Somewhat related, I'm interested in the software buffer idea that Arlet presented the challenge for. I have imagined it for years, but never needed it badly enough to figure it out. Whether anyone shows any real interest in the challenge itself or not, I'm still hoping there will me more helpful ideas and uses posted. Again, I'm always straining for an expanded tool box.

_________________
http://WilsonMinesCo.com/ lots of 6502 resources
The "second front page" is http://wilsonminesco.com/links.html .
What's an additional VIA among friends, anyhow?

It's true, a stack is ideal, I was just thinking within the framework of 6502, where stack access for locals isn't much fun. And even if can get the locals, if they are pointers you'll need to copy them to zero page to use them.

As shown in the 6502 stacks treatise, I think the access works pretty nicely, but the pointers issue remains if we're talking about the page-1 hardware stack rather than a ZP virtual stack. In ZP, the (ZP,X) addressing mode is hugely useful for that. The '02 has no such thing outside of ZP though (except for JMP), so copying a byte pair to a ZP "register" would be necessary. Fortunately, it wouldn't be needed for more than a few cycles, and then something else can use the same "register" if necessary.

_________________
http://WilsonMinesCo.com/ lots of 6502 resources
The "second front page" is http://wilsonminesco.com/links.html .
What's an additional VIA among friends, anyhow?

That is the key to working with the 6502...careful planning. It's amazing how much functionality can be gotten by working out memory usage on paper before starting to write code.

_________________
x86?  We ain't got no x86.  We don't NEED no stinking x86!

An observation as I code my monitor.

Assembly code is way more compact than I thought it would be coming from higher level languages like C/C++.

I guess I always imagined it would take many lines of code in assembly to do even the most simple thing. So far, that has not been my (admittedly small) experience.

I am currently writing the code to parse arguments to commands, specifically, getting a HEX number from a character string. I am amazed at how few lines of code it is taking, considering I want to allow both upper and lowercase A-F characters, and that the letters and numbers aren't consecutive in ASCII.

I think the key is that there are so many branching opcodes, and that they seem to cover pretty much everything. I think that has been the biggest revelation. When I first started reading on 6502 assembly, I kinda glossed over the status register, but its the key to everything!

Another pleasant observation. In C, and especially in C++, I found myself spending as much time wrestling with the particulars of the language itself, as I did solving the actual problem. Not so here. Even at this early stage of my learning, I feel like 95% of my time is spent designing the algorithm.

Anyone else have a similar experience? Also, I have no other assembly language experience, so I'm curious if I'd find other common CPU's as pleasant to code for. I'm specifically curious about x86 assembly.

Additionally, new assembly-language programmers usually miss a lot of possible optimizations, making their programs unnecessarily long. You'll just keep getting better.

Next, usually not affecting the length of the assembler's output, but making the source code a lot shorter and clearer, are macros. I wouldn't introduce them to someone who's brand new to assembly-language programming, but I wouldn't wait long either.

_________________
http://WilsonMinesCo.com/ lots of 6502 resources
The "second front page" is http://wilsonminesco.com/links.html .
What's an additional VIA among friends, anyhow?

An interesting first-hand report! You only get once chance to come across something for the first time, so it's good to have some insight into how it comes together. I hadn't previously heard anyone say that about the status register, but it makes sense. It can be surprising how a skilled 6502 programmer can perform a calculation or comparison and then quite some time later, perhaps some distant part of code, perform a test which uses one of the flags that were set. The carry bit is sometimes used explicitly as a one-bit register.

I think many people - especially on this forum - would say the 6502 is especially straightforward to pick up. There are not many registers, not too many addressing modes, not much machine state to track.

There's a neat diagram by Bob Sander-Cederlof which I like a lot:

The Propeller (prop 1) assembly language is possibly the easiest 'modern' assembly language to write in. It was designed that way, to be a pleasure to use. You wouldn't think so when you learn that self-modifying code is an inherent (and necessary) concept for the P1, but it is.

Update:

Had a harddrive crash on the computer with my monitor's source code on it

Dumb drive isn't even recognized by the BIOS of any machine I hook it to. I even swapped PCBs with an equivalent drive.

I think it's the dreaded fluid bearing seize-up that that drive is susceptible to. Cheapest physical recovery place around here starts at $300 or so. Not bad, but there really isn't much of value on the drive. My monitor is probably one of the least bothersome losses because, not only was it still relatively small, I do have the code on the ROM if I want to reconstruct it. Also, there was a good portion that I posted here. I'm toying with the idea of a DIY platter transplant if it turns out I'm truly out of options. Of course I'd have to conjure some sort of clean air box, and get a few specialized tools. The scotch tape method I see often for maintaining platter alignment frankly terrifies me. Yeah, DIY swap probably not a likely plan...

Probably the most annoying loss is a bunch of C code for a MCU project I also have going. A scratch written driver for a character LCD with an I2C expander for I/O is gone now.

Cloud based backups will probably be something I use now guess

Anyway, just wanted to let you guys know I'm still at it since Its been a bit.

_________________
http://WilsonMinesCo.com/ lots of 6502 resources
The "second front page" is http://wilsonminesco.com/links.html .
What's an additional VIA among friends, anyhow?

Turns out the best thing I did was put that resistor in the clock line

See, that caused some wacky behavior that caused me to post a fairly recent version of my code here for help debugging what turned out to be a hardware problem.

The bulk of the more recent parts are my white board. Turns out all I really lost on this project was a routine that clears the terminal screen by sending the appropriate number of newline characters. Nothing at all really.

I plan on using the drive that I bought for a donor PCB as a backup drive. And some sort of cloud based solution. My wife is an aspiring fiction writer, and even she was smart enough to have cloud copies of everything she does.

Sorry to hear it. At best, it's annoying.

That said, all disks will eventually fail—you can take it to the bank. I have replaced hundreds and hundreds of them over the years, and have seen grown men weep because the disk went south and they had no viable backups.

"Backing up" to the "cloud" is not backing up. If the machine that has been backed up goes completely DOA due to a failed disk, you cannot restore it from an off-site backup because you won't have any Internet access, because you won't have an operating system loaded. In other words, you can't do a bare-metal restoration, something which is only possible with local backup media that you have in your possession, along with a bootable medium that can start an operating system to give you access to the backup media.

Everything around here gets backed up to tape every night. Both of my Linux boxes have LTO SCSI tapes and I can do a bare metal recovery using a custom boot CD. None of that cloud-based snake oil for me. If the root disk in either box blows, I can put a new disk in and boot the machine on the CD, which gives me a working Linux kernel and set of utilities. From that, I can restore the tape back to the disk, including the boot block, and on the next reboot, everything will be up and running as though nothing had happened.

Each night a 4 AM, the Window$ PCs' disks are imaged to one of the Linux boxes. The previous night's images will have been backed up to tape. So if a PC disk goes south I can restore the server-based image and in less than an hour have normal operation. None of it would be possible if the files were being copied to an off-site "backup facility."

_________________
x86?  We ain't got no x86.  We don't NEED no stinking x86!

I think you only mean that restoring might be difficult. It's a perfectly valid backup tactic, and has the advantage of being off-site.

A common tactic is to have a couple of removable drives or USB drives, so there is always a copy off-site.

A common mistake is never to check that the backed up data is really there and can be restored.

Another common mistake is to copy the present data on top of the (only) previous copy. If your data is corrupted, you will have overwritten the good copy.

I use a 1TB external USB drive for backup. I only copy my personal working directories, not the OS, or other stuff that can be downloaded again. I use the linux 'rsync' program to create a 1:1 copy of the entire directory structure, one for each day of the week, uncompressed. In my experience, files are most often corrupted by simple user error, so I can go to the backup disk, and just copy a single file back.

In case of something like a house fire, I can quickly yank off the external drive and stick it in my pocket.

No, I mean it isn't backing up. You don't have the medium containing the backed up data in your immediate possession. Also, what happens if the place where your "backup" has been stored goes out of business (had that happen to a client about two years ago), burns down, gets blown away by terrorist, etc? Also, how do you know your data is secure and not being nefariously used?


That is a good tactic that I would recommend to anyone with a standalone PC. I stress to my clients that at least one recent backup medium should be in a physically different location or in a UL-listed media safe (what we use around here) so they will have something to work with if a major calamity destroys their facility and new hardware has to be purchased. I've assisted two clients with this sort of thing in the last 10 years, one whose office building was flattened by a tornado. In both cases, they had followed my advice about physical protection of the backup media and all turned out well.

USB drives are pretty trustworthy these days and inexpensive enough to make purchasing several of them practical. A rotating grandfather strategy gives good assurance that a viable backup will be available if needed.


Unfortunately, you are quite right. The backup process can fail for any number of reasons, not the least of which is failure of the backup medium itself. All of my clients running on Linux use a product called Microlite Backup Edge, which does a meticulous job of verifying that the backup is 100 percent viable. Most of them back up to LTO tape as I do, but I have one who backs up up to RDX data cartridges. LTO tape is actually more reliable than RDX, but the latter is substantially faster during restorations because it is capable of random access.


Another good point. That is where the rotating grandfather strategy gets into the picture. My business clients all used two sets of cartridges labeled Even and Odd, which refer to the week of the year. There are either five or six cartridges in both sets, for Monday through Friday or through Saturday. Right now, we're on an Even week, so the Odd set is taken off-site and the Even set is in the media safe. Next week, the process will be reversed. This procedure virtually guarantees that a viable backup exists at all times. It also means that files can be recovered up to two weeks in the past, just in case a number of days go by before it is discovered that a file has been corrupted or deleted.

For home use, one doesn't have to be as elaborate. However, I recommend a minimum of three backup media in the rotation, both to improve redundancy and to reduce wear and tear on the media.

_________________
x86?  We ain't got no x86.  We don't NEED no stinking x86!