Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 10/04/21 in all areas

  1. You're in luck. Facebook has been down for at least three hours today.
    2 points
  2. Macros don’t come from the editor. The assembler does that. Technically, it’s part of the preprocessor, but most assemblers just integrate the preprocessor and the actual assembler. So there’s usually a MACRO statement, which you follow with assembly code, like this: name .macro jsr print .null "Hello @1!";first parameter .endm Source: http://tass64.sourceforge.net/#macro Then you will invoke the macro, which replaces the macro call with the actual assembly: #name “Tom” Now you can use that anywhere in your code as a shorthand for a larger procedure. While this is obviously a trivial example, it’s very useful for doing repetitive tasks, like setting up KERNAL calls or 16-bit math. For example: Add16 (adds two 16 bit numbers and stores the result in the specified address) Print (takes the address of a null-terminated string and prints that to the screen using CHROUT) Open and Close (for file I/O) While Add16 seems trivial, it’s much easier to write something like Add16 Addr, 23 than to repeatedly write out the the several lines of code needed for a simple 16 bit add. Another reason macros are useful over copypasta is that you can fix a bugged macro much more easily than dozens or hundreds of places in a program where you repeat a piece of code. If it turns out you forgot to clear the Carry flag before an add, and you pasted that 130 times, you’d have to fix 130 instances of your error. But if you make an Add16 macro, you can do it in the macro, then just re-assemble the program.
    2 points
  3. In this case, the macros are part of the assembler. Even notepad can use assembler macros. If the assembler supports, them, that is.
    2 points
  4. Odd that I didn't see anything about this. Luckily, they are very good at posting replay/YouTube of the live proceedings. Here is/was the agenda: https://www.crxevent.com/CRX2021_Schedule.html Here is the live YouTube link: https://www.youtube.com/channel/UCM-pwz9yoNIAuIyLs_BG5dw and from here you can access prior days (and last year's vids) Lots of very cool PET and related [otherwise] Commodore and Retro content posted to Discord; here is some of what has already occurred; people like Jim Drew, Chris Abbott, Radolfo Fernandez, Stefany Allaire, Chuck Hutchins, Chris Zimmerman and others. C64 Keycap campaign Complete tear down, cleaning, and rebuild of the Commodore Datasette Part 1 The Little Topic of Sound Chips Setting up a Raspberry Pi Amiga The processes of creation of the C256 Foenix C64 productivity software overview Stupid PET Tricks New Bitfixer products A Kernal ROMance What's new in the Ultimate world! Reconstructing Habitat’s world from backups PET history The Runic Commodore 64 Here is what is in store, starting in moments:
    2 points
  5. Version 1.0.0

    9 downloads

    Early Amiga-demoscene inspired raster bars with color gradients. The color gradients are randomly generated. Written in Prog8 with a bit of inline assembly. Source code is available here https://github.com/irmen/prog8/blob/master/examples/cx16/colorbars.p8
    1 point
  6. Much like the VIC 20 had a cartoon character in the manuals, I've prototyped a mascot along the lines of cutie for your new company
    1 point
  7. This is why I dislike Facebook…. Unlike proper forum software, there’s no “catch up” system on Facebook groups, which shows you just the posts you’ve missed. I saw the post by Ian, but never saw Klaus’s reply, David’s reply to him, or Phil’s reply to David… IMO why Facebook groups should be used sparingly and for official announcements, leaving actual conversation to product forums like this one.
    1 point
  8. I think they wanted Mega 65 to look like unreleased Commodore 65 as much as possible. This explains me everything.
    1 point
  9. Hi, David, Sorry to hear of the changes you and the rest of the project team have been going through. It sounds like you are all handling it well, but things change - they always do. It's never easy getting a project like this off the ground. I'm in favor of a "Phase 1+" X16 kit (with all components and sockets) as opposed to a fully assembled product. That's because I have the skills to assemble such a kit. I quite realize others may favor a kit. Board assembly and testing can be sold separately. It sounds like Phase 2 would be more amenable to manufacture/mass production, but I'd be lost trying to assemble SMDs with my old tired eyes. There are options for manufacture other than China (which seems so nightmarish from what I'm told). FineLine PCB out of Philadelphia might be a way to go. X8 sounds like the same mistake others have made, just on the face of it. Stick with the X16 and see it through, and you'll come out better, I would think. As for the case, it looks like the original case is going to be fun to find. Any microATX case will support the Phase 1 board, am I correct? I hope the project continues to progress in one form or another. It would be so very cool to see one of these on sale one fine day.
    1 point
  10. Yeah, I tend to create a load of macros, as well. By the time I’m done, my programs are more macro than assembly. Essentially, what this means is I’m making up my own programming language. And I’m fine with that.
    1 point
  11. I don't know about "have to" ... I'm not in the design team after all .. but the goal for the X16e was that it would be software compatible. Now, whether it could ALSO have upgrades that become possible when the video chip and CPU are literally built in the same FPGA ... well, I suppose it COULD. The "e" might stand for "enhanced". Indeed, it could have a choice of either the X16 or the X8 or both methods of accessing video memory, and there are bits available in various places of the Vera specification that would allow for using more than 128KB of Video RAM, so you might have "fast" Video RAM in the first 64K accessible through the page access as well as "extended" video RAM available in the X16 data port. After all, whether or not the design team wants to fragment the hardware platform like that is for them to decide. I am ambivalent about an "X16+" approach to the X16e, but I kind of like the idea of going ahead with the first X16p and the X8 in parallel, then the X16c, and then if the whole project is going well enough to keep it going, go ahead to an X16e that would also feature an X8 compatibility mode, so it would be One Board to Rule Them All, One Board to Bind Them, One Board To Bring Them All, and In The Darkness Bind Them.
    1 point
  12. "To build the board, you have to find a provider that builds PCBs from Eagle .brd files. Currently no gerbers are provided." Too bad PNG wasn't used...
    1 point
  13. Now live on GitHub, version 1.2.38.0664 of the META/L assembly language editor. https://github.com/edrobotguy/cx16/blob/master/METAL1_2_38_0664update.zip If you down'oad the zip file, extract it into the same folder as your X16 rev 38 emulator. Then you'll find thorough documentation in docs/edit.html the video playlist is here: METAL1_2_38_0664update.zip
    1 point
×
×
  • Create New...

Important Information

Please review our Terms of Use