(extracting a couple of issues from recent PR discussion)
Does it make sense to add a platform file for c65, rather than using the py65mon target? I don't want to get rid of the py65mon target, as there are some users that may be using it. The c65 target would add support for the block file and make csim (or make cdebug) would add the command line for that as well, so that you drop into an environment with block support.
Once that exists, I think a reasonable next step would be to move the block-ramdrive-init code out of Tali and provide it as forth code in the examples folder instead (with instructions in the source file). It's still useful for those who want to play with a ramdrive block device (on real hardware, perhaps), but we can use c65 for the tutorial and simply mention the ramdrive version as an alternative. I'm hoping to have more time this summer to work on the documentation, and we can add that to the list.
(extracting a couple of issues from recent PR discussion)
Does it make sense to add a platform file for c65, rather than using the py65mon target? I don't want to get rid of the py65mon target, as there are some users that may be using it. The c65 target would add support for the block file and make csim (or make cdebug) would add the command line for that as well, so that you drop into an environment with block support.
Once that exists, I think a reasonable next step would be to move the block-ramdrive-init code out of Tali and provide it as forth code in the examples folder instead (with instructions in the source file). It's still useful for those who want to play with a ramdrive block device (on real hardware, perhaps), but we can use c65 for the tutorial and simply mention the ramdrive version as an alternative. I'm hoping to have more time this summer to work on the documentation, and we can add that to the list.