Jump to content

JimmyDansbo

Members
  • Content Count

    274
  • Joined

  • Last visited

  • Days Won

    8

JimmyDansbo last won the day on March 13

JimmyDansbo had the most liked content!

Community Reputation

170 Excellent

5 Followers

About JimmyDansbo

  • Birthday 08/03/1979

Recent Profile Visitors

447 profile views
  1. Seems to be straight forward (said the blind mand) Thanks. I will look into it.
  2. It is not something I had thought about, but since you ask, I might look into it. Would you be able to point me in a direction that explains what should be done to create a C API? I am guessing you are talking about cc65?
  3. ... also links to the PiModem page
  4. I would be very interested. Please be sure to advertise it ahead of time and record the live-stream for future reference.
  5. I actually had to copy the i686-w64-mingw32 directory to /opt/local/ Even when I provided a different path to WIN_SDL2, it still tried to find the files in /opt/local/i686-w64-mingw32 Thanks for your help
  6. Hi Nadia and welcome If the X16 is indeed going to be your first ever coding experience, I suggest that you start out with BASIC and work your way up. As the Commander X16 is using the same BASICv2 as the Commodore 64, there are plenty of resources online to help you get startet. I suggest starting here: https://www.c64-wiki.com/wiki/BASIC and specifically the list of commands https://www.c64-wiki.com/wiki/BASIC#Overview_of_BASIC_Version_2.0_.28second_release.29_Commands When you want to go X16 specific, the Commander X16 Programmers Reference Guide is an excellent resource and of course the VERA Programmers Reference when you want to get very graphics specific. @DusanStrakl has some very nice tutorials on both BASIC and assembler programming for the Commander X16 here: https://www.8bitcoding.com/p/commander-x16.html If/when you want to start doing assembler, @SlithyMatt is creating great content on Youtube: https://www.youtube.com/user/slithymatt/playlists There are probably other good resources that I have forgotten or have not yet found, but generally I find this forum to be very friendly and helpful so go ahead and ask away if you have any questions. Happy coding
  7. I see no reason why we could not use #2. If we have to use something different, I was thinking that we might as well choose something that is recognizable from other platforms such as the PC, like $3F8. Only after I submitted my answer, I realized that we probably only have a single byte for the ID.
  8. I am mostly using 2.7.2.255 that can be found here: https://sourceforge.net/projects/circuit/files/2.7.x/2.7.x Development/ So far I have had no issues with it.
  9. I have been using Logisim for a couple of years now. I have also tried Digital and other's, but still like Logisim best. Would love to see a modern (read no-java-based) port of Logisim that has the same functionality.
  10. It seems to me like you are mixing your variables? Your DATA statement includes numbers, but your READ statement reads them as strings. Code should be: 10 DATA $1000, $FF 20 READ A, D 30 POKE A, D 40 PRINT A,D
  11. Unfortunately not in the manual yet, but DATA$ and DA$ are definately built into the KERNAL as string representations of current date. https://github.com/commanderx16/x16-rom/commit/f01870d7cf11b34c8cc372d5d04b571bf2574d54 Just tested it in the emulator: As you can see, when the DA$ has been set, it will be updated by the kernal.
  12. Nope, v39 will be using $00 and $01 for bank switching and generally be closer to the actual hardware. v38 has always- and is still using $9F60 and $9F61.
  13. I am also in the process of building an 8-bit CPU/computer. The CPU is designed and running in Logisim and I have actually started hardware development although I have already hit a snag in moving my Ben Eater-style clock-module from breadboard to prototype PCB. I hope that you will get the time to play around with the Commander X16 emulator and eventually the hardware. Looking forward to seeing what you come up with
×
×
  • Create New...

Important Information

Please review our Terms of Use