Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation on 03/16/21 in all areas

  1. 3 points
    I wanted a CRT for my retro computers, but I didn’t want to deal with the weight and the size... so I found a 6 inches TV/radio combo for sale, that has video and audio input, and it was cheap! (€10, around $12). i’m really happy with my purchase, and thought you guys may appreciate it.
  2. 2 points
    The 65C22 VIAs, any expansion cards, and the YM2151 (as you mentioned) are additional components of the system that are not part of VERA.
  3. 1 point
    He has run my game "Chase Vault" on there, and the YM2151 music plays back perfectly. I'm doing a busy loop waiting for ready before each write, and it all seems to work the same between the emulator and the prototype. The only difference is on the emulator, the status always reads as "ready", so it may be a bit faster when updates need to be made to the YM2151. Good news is, most of the time cycles go by without needing to write an update. 60Hz is pretty fast! Even loading a large patch still won't take a huge amount of time, and could be split up across cycles if necessary.
  4. 1 point
    [1] Source? Is this referring to MMIO "ports"? [2] As the kid who would be the first (and ultimately only) one on the block whose parents got him a Plus/4 instead of the C64 he wanted, I remember that the defining characteristic of those chips was that they sucked. 120 colors couldn't make up for the fact that it had no sprites and sad audio consisting of two channels of square waves. (Or one channel could be noise instead... yay?) [3] The copper and blitter lived on Agnus, the DMA controller, not Denise, the video chip. Much of what the blitter was needed for (compositing rectangular graphics with transparency on top of a playfield) can be accomplished less expensively on CX16 using VERA's sprites and those won't steal CPU cycles while doing it. In no case could the Amigas of the 80s display 8 bit plane graphics or sprites that were more than 16 pixels wide (and I think limited to 4 colors, or 16 colors when grouped together). Hence why I say VERA is "competitive" with. (Side note: since the "world's first" (Nvidia's phrasing) "graphical processing unit" (GeForce 256, 1999), that term has always referred to a chip that contains a pixel pipeline capable of doing, at a minimum, texture and lighting. Hardware bit blitters were common in mid and high end SVGA cards (e.g. ET4000/W32) from the early 90s and didn't use that moniker. I don't think anyone has been seriously asking for a texture or shader engine in VERA.)
  5. 1 point
    Now there is an input_str function... That took up a lot of space. Library size went from 900 bytes in 0.7 to 1008 now in 0.8
  6. 1 point
    Upon re-reading the datasheet, you are correct. The block RAM can be pseudo-dual ported (section 3.1.5), not the SPRAM (which I should have known since it stands for "single port RAM").
  7. 1 point
    Yep that’s the problem I’ve had! But I’m sure one will turn up. Perifractic, X16 Visual Designer http://youtube.com/perifractic
  8. 1 point
    I go with 4 column tabs, as this gives a clear indent, but doesn't walk the text all the way across the screen. If I find I've indented more than 20 columns, that means I've got too many nested blocks, and I probably need a procedure, CASE statement, or more complex IF predicates. And I've never appreciated the habit of the Commodore community to write crunched code... while it's often necessary from a performance of space standpoint, don't do it while explaining things to other people. I've seen people give example code like FORI=1TO20STEP3 to new programmers, and I always have to stop and say something. It's fine to crunch code when you know what you're doing and need the bytes, but never, ever give crunched code in an example. (Unless the topic is "how to crunch code.")
  9. 1 point
    Yes it's nice to know there are many signs of success on the horizon for this project. I hope to all who are in charge of this, you all profit handsomely as I know we all will benefit from these new creations! Hope we can buy things before Christmas! Will be an excellent holiday if we can!
  10. 1 point
    Hey, that little clock was the first kit I ever soldered together. (It took me a while to realize it, but you can indeed peel that clear sheet of the front of the display). Feeling confident, the next project I did was to 'pro sound' mod a used GameBoy. And then, the third thing I tried was this oscilloscope kit: https://jyetech.com/dso138mini-oscilloscope-diy-kit/ What's fun about that one is, you can actually use it for electronics projects when you're done with it. I used it to help diagnose the C64 I rescued from the trash, for example, by checking for 'clock' signals at the appropriate pins. (It was also fun to hook up it up to the sound output of the GameBoy and look at the waveforms.) If what you need is an oscilloscope, then this is obviously this isn't the best one out there. But if what you want is more stuff to solder, why not solder something you can use afterward? (The pin header leading to the screen is very small, with not much space between the pins. It was, so far, the most challenging single component I've ever soldered. But I got through it!) Beyond that, I have to give a shoutout to the PE6502, which took me about three afternoons to build. At the end, you have your own little 6502-based computer, which I am still enjoying working with. It'd good prep for the upcoming X16p kit. The official page is here: http://www.putnamelectronics.com/ ...but you might check with @Corneleous Worthington to see what the current buying options are.
  11. 1 point
    Yep. LOAD and SAVE are the only things that you can do on the host's file-system. If you really want to avoid those extra bytes, then you must work with an SD card image. You had the right idea with cbm_read(). Here's some example code: #include <stdint.h> #include <stdio.h> #include <peekpoke.h> #include <cbm.h> #include <errno.h> uint8_t readbin2bank(char name[], uint8_t bank) { uint8_t err; int len; POKE(REG_RAMBANK, bank); err = cbm_open(2, 8, 2, name); if (err != 0) { return err; } len = cbm_read(2, 0xA000, 0x2000); // Read as much as allowed into current RAM bank. if (len < 0) { cbm_close(2); return _oserror; } printf("Read %d bytes into RAM bank %u.\n", len, bank); cbm_close(2); return 0; }
  12. 1 point
    I think if you look for “portable color tv radio” you can get some results on eBay... This model is a Contec, but there are other brands. Some are at reasonable prices. Edit: it seems that the most prevalent ones in the US are the Emersons and the GEs, but those don't seem to have VIDEO and AUDIO IN like the Contec, so your only option if you get one of those is using the RF modulator and the antenna connector.
  13. 1 point
    Beautiful! I’ve been looking for something similar for my repair workbench. The search continues… Perifractic, X16 Visual Designer http://youtube.com/perifractic
  14. 1 point
    And the flip side of that argument is... there's no way a 6551 based expansion card will cost less than that, and someone has to write the drivers - whether before or after launch.
  15. 1 point
    Not everything is documented in funcref.html, but most of it is. Sometimes it will say "incomplete", others functions are simply missing from the documentation, but the headers do at least show the function prototype, sometimes with some additional documentation about the function in the comments.
  16. 1 point
    The X16 documentation also lists all kernal functions inherited from the C64 and C128, although it provides no description (this is particularly annoying for functions that have been modified, such as LOAD). As for C functions, the cc65 documentation has a list of all C equivalents of system functions from various machines, including the C64, at https://cc65.github.io/doc/funcref.html. This list will eventually include X16 functions, but for now, you can find any X16 C functions that have been implemented so far in the header file at https://github.com/cc65/cc65/blob/master/include/cx16.h. I believe any functionality not in either list currently has no C implementation, and must be called manually.
  17. 1 point
    I find these functions difficult to track down documentation for - The C64 Kernal functions themselves are well-documented, and the official X16-Documentation repository on Github defines some of the system-specific Kernal APIs, but I recall once coming across a complete list of the X16 Kernal API somewhere off the beaten path, and for the life of me I can't find it. I find it much harder to locate a good reference for the cc65 functionality, especially where system-specific funtionality is concerned. Anyone with a good link to a C reference for this stuff?
  18. 1 point
    I think it looks a good bit like Algol, from which C and Pascal descend, but with fewer parentheses.
×
×
  • Create New...

Important Information

Please review our Terms of Use