Jump to content

pzembrod

Members
  • Posts

    70
  • Joined

  • Last visited

  • Days Won

    1

pzembrod last won the day on November 16 2020

pzembrod had the most liked content!

1 Follower

Recent Profile Visitors

270 profile views

pzembrod's Achievements

Newbie

Newbie (1/14)

  • Week One Done
  • One Month Later
  • One Year In Rare

Recent Badges

76

Reputation

  1. Hi @Kevin Williams, @Michael Steil, I might be able to offer some help around the 65c22 bit-bang approach. It's unusual that this works fine at lower and runs into problems at higher clock rates. Just reach out. Cheers /Philip
  2. @Wavicle, did you see any indication where the DOS for the SDCard might be living? On the X16 it occupies an entire ROM bank, IIUC. Just realized that this would be tricky with only 64K of memory overall ...
  3. I've said it before and am saying it again: Give them a break. Also, you are starting to sound somewhat entitled, which probably isn't your intention. Careful hint : You may be, just maybe, overestimating the value of your so far released X16 software. David is currently dealing with a major shakeup of his project. He's asked a question 5 days ago to feel the water about the option of an X8, and could probably spend some significant portion of his time just reading and digesting all the replies he's getting here in the forum, plus keeping an eye on all the other discussions, such as this one. He has given us an overview of the X8's specs, and I'm not surprised at all if he didn't have the time yet to reply to all the questions that came up. It shouldn't be all that hard for all of us to muster the patience that is called for at the moment. See above - let's be more considerate of all the other things on the project owners' table at the moment. And keep in mind - they have day jobs, too. This here isn't really it, not even for David, IIUC.
  4. Now this is a fun idea! Hadn't thought about that ...
  5. @The 8-Bit Guy Hi David, I don't have a clear opinion wrt your questions 2 and 3, but wrt question 1 I would say do release the X8 - I probably would buy one just because it's cheap and it's there. My main interest in the project at the moment is as a platform to develop VolksForth and cc64 for, and at least the former I would likely port to the X8. Regarding the X16 phases, I'm not sure what I would buy. I'm still attracted to self-soldering RC2014-style 65C02 machine, so I might fall into the camp that would consider buying a VERA Cheers /Philip
  6. As others have pointed out before: Things aren't as clear as you believe them to be.
  7. I'll wait for more info and decisions from the project owners, and then decide what will be feasible. If the BASIC at $8000-$BFFF assumption holds, then VolksForth likely will be. For cc64 I'd have to overwrite the BASIC interpreter, and it would still be a close call.
  8. That won't fly in many cases. E.g. cc64 would exhibit abysmal compile speeds if I were to swap out significant parts of the compiler code to and from SDCard.
  9. It's quite fascinating, really, and also provides a nice study in software architecture heritage. The 1541's DOS still shows this structure, only it simulates the second CPU with an interrupt driven disk controller routine. The job codes in the zero page that the file system and the disk controller communicate through - that was the shared memory in the 2-CPU drives.
  10. I feel you may want to dial it down a bit. Give them a break! Let's wait for Frank or David to chime in, but if Wavicle is right, then I'd rather expect the BASIC interpreter to live from $8000-$BFFF - unless I'm mistaken the extended X16 BASIC is 16k; at least it lives in a 16k ROM bank.
  11. Did anyone on this thread already mention that this is exactly what the big CBM disk drives did? The 4040, 8050, 8250, etc...? One 6502 was doing the IEC bus and file stuff and the other did block level disk access. They would communicate through memory locations.
  12. Depends on circumstances and who you are. Way back when the C64 was my main computing device, I found Forth to be the most productive language, by far, that I could lay my hands on. Which is why cc64 is implemented in Forth.
  13. Done, thanks, Tom, I should have thought of that. Here it is:
  14. @The 8-Bit Guy @Frank van den Hoef Hi David, hi Frank, (taking this topic off the "Change of product direction, good and bad news!" thread as @TomXP411 rightly suggested) it's cc64's author here. Can I ask a question about the X8's RAM layout? Where do the 64K live? Is there RAM underlying the ROM, C64-style? Are the 24K RAM that aren't needed for $0000-$9EFF mapped in as 3 RAM banks at $A000-BFFF? Are there just regular 8K mapped in at $A000-BFFF, as in: just 1 bank? I'm asking because the base RAM from $0800-$9EFF turns out to be the limiting factor for further development of cc64, and I'm thinking about how to use banked RAM for code to overcome that limit; if banked RAM isn't available, then that would cap cc64 development on the X8. And even now, just compiling cc64 on the X16 needs one bank at $A000 to be present. Cheers /Philip
  15. Hi David, cc64's author here. Can I ask a question about the X8's RAM layout? Where do the 64K live? Is there RAM underlying the ROM, C64-style? Are the 24K RAM that aren't needed for $0000-$9EFF mapped in as 3 RAM banks at $A000-BFFF? I'm asking because the base RAM from $0800-$9EFF turns out to be the limiting factor for further development of cc64, and I'm thinking about how to use banked RAM for code to overcome that limit; if banked RAM isn't available, then that would cap cc64 development on the X8. And even now, just compiling cc64 on the X16 needs one bank at $A000 to be present. Cheers /Philip
×
×
  • Create New...

Important Information

Please review our Terms of Use