Jump to content

Kalvan

Members
  • Posts

    94
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Kalvan

  1. True, however, the 65816 features 16-bit integer instruction arguments and register sizes.
  2. Since I don't consider the Panasonic MSX Turbo-R Machines to be 8-bit computers (the ASCII R800 featured 16-bit integer instruction arguments, registers, and at least one 16-bit data bus), the 8-bit computers with the most standard RAM would be the final production year Tandy CoCo 3 and Fujitsu FM-77, with 512-640K system RAM each (plus 128-384K separate VideoRAM in the case of the FM-77 AV40 Level 3). That said, the Apple IIc+ and IIe Anniversary Edition, Sharp X-1 Turbo Z and X, and NEC PC8816/18 have O/S memory maps capable of addressing up to 2MB, and Atari 8-bit computers equipped with the FREDDIE MMU/DMA can address up to 4MB. Back in the day, two full megabytes of High RAM+124K Video RAM, 4K PCM Buffer, and 64K Low RAM would together be seen as overkill until Ca. 1990-91, with only the Apple IIGS and Amiga 750 and then 1200 possessing similar memory amounts among contemporary non-PC Clone competition.* *I do not consider the Macintosh III and Quadra, Sharp X68000, High End Amigas, or Acorn Archimedes A4000/A6000 series to be anything close to hypothetical market segment competitors.
  3. I had a wild, wacky idea that you might want to follow up on: How about a tilemode consisting of tiles 36 horzontal X 28 vertical pixels. In a 400x225 16:9 aspect ratio display, with the leftover columns and rows used for line buffering, you get 11x8, or 88 tiles per screen. Each tile would consist of four stacks of 7 pixels, 36 stacks wide. You can map the biits of each stack so that 7 bits are used to map colors from a given CLUT, with an eighth set of seven bits used to select the CLUT. This means that you can have a hypothetical maximum of 16,192 colors (128 CLUTs of 128 colors each) onscreen, and with Video RAM at 128K mapped half and half between the tile data and the scrolling field tile map, there's room for 74 unique tiles and a screen map of 256x256 tiles in a single field, or 23x32 screens (737 total) at that 16:9 aspect ratio. If you reduce the pixel bitwidth, you can have even more tiles and/or an even larger scrolling field. Of course, one drawback is the memory requirement for all those CLUTs, which may cut into either the tile data or the screen tile map. And this still doesn't account for necessary Video RAM for BOBs...
  4. It looks like you can either take two clock cycles to use the DMA to use the Dual-Port RAM as audio buffer, or else use the DMA or the CPU to take four cycles (at least) to use the DDR2 as sound RAM, which may be necessary if you've exceeded your total sprite, or scanline limit, and wanted to add in some BOBs as extra enemies, bullets, fireballs, or clouds in your vertical-scrolling shoot-'em-up, or bit-bang in more parallax scrolling fields? Question No. 1: While it doesn't look like it will happen in hardware, do you plan to designate specific stretches of Dual Port and/or DDR2 as sound buffer? Or will programmers have to be doubly careful about reads and writes to prevent the use of sound data as general logic code, or the YM2149s from reading data meant for A.I. routines and spitting out garbage from the speakers. Question No. 2: Do you believe you have enough fabric RAM to stick a YM2151 on the Nexys A7-100T?
  5. Oh yeah! This means that you could recreate the waterfall effects of, say, the Sonic games, but make them work with (relatively) sharp A/V Multi-Out or VGA video output. @epsilon537, if you're reading this, would this addition compromise the geometry of the softcore of the BoxLamda too much?
  6. Well, The X1-010 was used in a whole bunch of arcade games by the likes of Seta, Alumer, Visco, Athena, Tecmo, Sammy (Before the merger with Sega), Data East, and especially Banpresto. As I've seen footage of Twin Eagle: Revenge Joe's Brother running on the MISTer platform on YouTube, I'm certain that it's out there to find. Or, one can theoretically find the source code for core for the Seta 1st Generation Arcade Hardware and try to isolate the HDL code for the X1-010 that way. The Phillips SAA-1099 was used in the SAM Coupe, The Creative Labs GameBlaster and early SoundBlaster series cards, a couple of Mid-Late Eighties Digital Equipment and Silicon Graphics workstations (as a timer generator and peripheral I/O controller), and several arcade games by Century Electronics. The really tricky one would be the YM2414. It's an eight channel, four operator FM synthesizer with eight possible waveforms that was only used in Yamaha keyboards, and (second sourced) in midrange keyboards and synth modules by the likes of Moog, Budcla, Korg, and Casio. I fell in love with its sound on YouTube, but if it's not available, the YM2151 will work fine. Dumb question: How fast are you going to clock that 32-bit RISC V core? I ask this because you may need a separate Sound CPU and audio buffer, especially if you want to experiment with the joys of PCM polyphony at high sample rates without bogging down the rest of the system. I would suggest either the Hudson HuC6280 (Also used as a Sound CPU in arcade games by Taito and Data East), or the Zilog Z180, as each can address 1 MB plus of memory on their own. Another Dumb Question: Which FPGA are you planning to use, and how much I/O will you able to play with?
  7. Well, for the audio solution, I would like to suggest a combination of the Seta X1-010, X2 Phillips SAA1099, and the Yamaha YM2414. All those sound chips would have been from the '80s, there's plenty of tracker music for each of them on YouTube, and together, they cover almost all the basics (Geometry Synthesis, PCM, Wavetable, and FM Synthesis) except Mathematical Synthesis like Additive (Atari AMY) or Subtractive (Like the Roland MT and Sound Canvas families). If the YM2414 is unavailable as a softcore, I'm certain the YM2151 is definitely out there.
  8. I suspect the setup should be able to run SymbOS no problem.
  9. Well, my idea might not be retro enough, but it would basically be a DE-10 Nano FPGA Board, with a few other boards (SDRAM or QDR SRAM, various retro port headers, possibly an onboard scan multiplier with options for letterboxing, as the monitor resolution is 2256x1504) attached via ribbon cables, stuffed into a Framework laptop chassis, with a whole bunch of interface cards (and dongles, for ports and jacks too wide to fit onto a Framework interface card). That way, the computer can be as retro as you're willing to make the FPGA softcore for it, or you can look to the MISTer FPGA project to ask yourself what if a specific company could (and did) develop a fully software compatible laptop version of the machine of your youth. But that's just my idea. YMMV.
  10. It would depend on how many FPGA resources were left over, and whether or not the MMU would fit in the FPGA geometrically...
  11. This is in reference to the thread here. Personally, while I have several concepts for projects involving the FPGA core, I'd say that I would first like propose possible ideas for alterations and improvements to the core before its reimplementation in new projects: 1: The removal of the sound channels, and the reimplementation of the audio buffer as more video RAM. That way, if the system has its own sound CPU, there won't be timing issues between it and VERA. 2: Changes to the resolution and aspect ratio, to mimic classic arcade, console, or computer resolutions, multiples thereof, or allow for more even addressing math for Video RAM. 3: The use of larger FPGAs with more SRAM in the fabric, to allow for more Video RAM, and more graphical features, such as more sprites, more frames per sprite, affine/scaling and rotation for sprites, a wider master palette, more and/or bigger CLUTs, wider bitmap modes with scrolling registers, some sort of blitter function, more scrolling fields, and/or the elimination scanline limits for sprites. 4: A larger memory bus and/or a separate external memory interface, both to allow more video RAM than the fabric can provide, and to allow separate video RAM for things like sprites, fonts, tiles, or possibly BOBs 5: A possible Video CPU interface, so that the main CPU doesn't have to babysit the blanking cycles and keep track of things like sprite placement or the screen window's place in the bitmap or tilemap. As for specific implementation projects, well, that's what this tread is for.
  12. Here are a few more perspective porting targets for Mr. Murray's latest software project: Exidy Sorcerer Sharp MZ Sharp X1/NEC PC88 (they both ran Microsoft Basic and CP/M and have similar port architectures. The biggest differences between them seem to be sound chips.) Sharp X68000 (Pretty sure there are porting projects for the Atari ST and Sinclair QL already under way) Apple Macintosh (System 3 or lower) Texas Instruments TI 99/4A Ohio Scientific Challenger Tatung Einstein series ColecoVision/Sega SG1000/ADAM/MSX1 (The specifications are so similar that a single build could theoretically be made, and then simply hand tweaked for each individual system). MSX 2, 2+, and Turbo R Commodore CBM 400+ machines (Successors to the PET) Fujitsu FM 8/7/77 (Architecture is close enough to the Tandy CoCo that the latter can be used as a preliminary code base)
  13. Wow, definitely getting late-stage Sonic series vibes from it. It seems like you're using every channel of the YM2151 for most of the instruments, at least three geometry synthesis channels in triangle and/or sawtooth for the base line, another two in white noise for the snares, and the PCM channel for the rest of the percussion. But I could be wrong...
  14. I just updated the published specs of the Mega65 on page 3.
  15. Well, maybe for the Xosera II, they could use a bigger FPGA to implement hardware sprites. Since this version doesn't seem to include the sound channels and FIFO, presumably that should leave some room in the FPGA for more features.
  16. I had this wild, wacky idea: There's this company, called Framework. Admittedly, their first model uses a 13.5 inch form factor with a previous-generation Mac Book style with all the problems that implies, and because the keyboard lacks a number pad means that the number line characters will need the shift key to put into functionality (which means slightly rewriting the BIOS ROM), and it simply won't be able to access PET peripherals without a specially made USB hub, (unless someone wants to try their hand at Centronics, PET Floppy, and Datasette expansion cards) and I don't know for certain if your current motherboard will fit into the chassis, but it looks like another option to look at for people considering similar projects.
  17. Well, for me, it would be: QuadPOKEY or X2 Phillips 1099 Yamaha YM2414+YM3012 DAC Seta X1-010 or Ensoniq DOC, DOC II, or OTIS
  18. Then again, there are a few "crochet hook" ideas that in hindsight, should have been dope slap obvious, but back in the day no one ever thought of. Take stacked RAM. The idea of stacking four to eight DRAM dies using through-silicon vias, plus DRAM refresh logic and possibly a DMA and/or MMU on a package no larger than a then-typical DIP should have been blindingly obvious, but it didn't happen. Done right, a 64K Pseudo-SRAM version should have drawn no more power and/or generated no more heat than an 8K SRAM on the same package, and massively reduced the chip count of, say, the Commodore 64 and subsequent follow-up motherboards. Unity Semiconductor, creators of CMOx Flash, was poised to turn the nonvolatile RAM market upside-down, but then they were bought out by Rambus, which scared all possible potential licensees off, due to Rambus' reputation as sharks. They had white papers that it could have been produced on conventional CMOS tools, and tested the concept at a five micron node.
  19. There are a few things that need to be taken into account: 1: The OTL OPN series, which included the AY-3-8910 component in many of its chips, was second-source licensed by Casio and Phillips for their own kiddie keyboard designs. As the SID component would likely have to be separately licensed from Commodore, it could put some extra money into Commodore's pocket. It also possibly butterflies away the development of the SAA-1099. 2. The YM2209 features a grand total of 6 channels. The YM 2610 has a grand total of 7 Channels. The YM 2610A has 9 Channels, and the YM2608 adds seven ADPCM channels for percussion. Even the most barebones versions of those chips has 50% more polyphony than PAULA, a much smaller memory footprint, and far less need of processor time to babysit it and feed it data. Considering that Yamaha will have enough sales from other ventures to make bulk prices fairly cheap, is it possible for the Amiga to pack an OPN series chip, and restrict PAULA to keyboard, floppy, and hard drive access? Would this development make the Commodore 65 project easier to make a business case for?
  20. Personally, I have no problem with including a 3.5" floppy drive on a project that is meant to be a speculative recreation of an unreleased piece of computer hardware from the mid 1990s. That said, In my Hibana Series I concept, I would have also included a Sabrent All-in-one flash card reader, assuming there was a way I could hack an OS interface to it.
  21. Frankly, the only hardware improvement one could make to the CommanderX16 to accelerate BASIC without completely reengineering the system would be to add an IEEE half-precision FPU (with 8 extra bits of spillover precision) to better handle the lone floating point numeric data type.
  22. Time for me to eat some marvelous, delicious crow!
  23. You make it sound less like Out Run and more like Turbo. That's not necessarily a bad thing. Also, using sprites for the centerline and shoulders means that 1. they won't be available for things like trees billboards, clouds, or cars, and 2 how do you plan for them to not overlap the cars on the road?
  24. Dumb question: Does this 6502 implementation support the original illegal opcodes, or does it include the extra instructions and addressing modes from the 65C02 and 65CE02? Or neither?
  25. I'm still a big fan of the number pad, but otherwise, not bad. It looks like the late-80s Dell or Zenith Data Systems MSX Turbo-R machine that never was but woulda-coulda-shoulda been. Uh, does Madame Allaire have plans for the blank key between Z and left Shift?
×
×
  • Create New...

Important Information

Please review our Terms of Use