My dream computer project. Dream Computer Setup 2022-10-08
My dream computer project Rating:
My dream computer project would be a platform that brings together all of the tools and resources needed for computer science education, research, and development in one easy-to-use, intuitive interface.
This platform would include a wide range of programming languages and tools, including both established options like C++, Python, and Java, as well as newer and more specialized languages like R and Julia. It would also include a variety of integrated development environments (IDEs) and other tools for testing, debugging, and deploying code.
In addition to these technical resources, the platform would also provide a range of educational resources and support. This could include access to online courses, tutorials, and documentation, as well as opportunities for students and researchers to connect with mentors and experts in their field.
One key aspect of my dream computer project would be its focus on collaboration and community. The platform would include features like online code repositories and project management tools, as well as forums and discussion boards where users can share ideas and ask for help. By fostering a sense of community and collaboration, the platform would provide a supportive environment for students and researchers to learn, grow, and innovate.
Ultimately, my dream computer project would be a one-stop-shop for all things computer science. It would provide a wealth of resources and support for learners and researchers at all levels, helping to democratize access to the field and encourage the next generation of computer scientists to pursue their dreams.
CSC 134 MY Dream Computer
In order for the system to be a standard design, it needs to have a design set it stone, much like a C64 does now. Choose Intro to Computers on the gray menu bar. After doing a little research, there are already several platforms that may be better fits than some guy, or a small team of people doing a new design from scratch. But every one of them falls short in some way or another from what I dream of. I consider BASIC itself more part of this than any of the former. I jumped in on the kickstarter and am eagerly awaiting mine. And, yes, it is Arduino supported.
No need to stuff that into a FPGA. These days, I commonly see young software developers who have a profound lack of knowledge of the underlying hardware operation itself. Or perhaps that just affected us in the PAL world? Part-2 would include new key caps. Building USB-able devices is damn hard, and believe me, I tried already when I wanted to build a device that could achieve privacy against Keytrack-mechanisms. After all, an 8 Mhz 6502 would have about the same performance as a 32 mhz X86 chip, and so I think there would be no issues. An issue is possibly the level of FPGA that the Mega65 is being implemented with, which is not particularly an inexpensive part! Would that be acceptable? And cheaply, without an expensive FPGA, or a large PCB full of discrete TTL. The Z80 design offered lots of hooks to help manage your DRAM, but at a cost that it is quite prescriptive in describing how your motherboard architecture will look.
A dedicated video driver circuit with VGA, composite, HDMI, DP would complete the board, along with a USB keyboard decoder of sorts. I like the horizontal and vertical expansion on the 64 and will include that. In mode 1, you could have the main CPU put a character grid into the discrete area, with the discrete CPUs converting that into the pixel area. Once you've decided what kind of PC you want to build, you can begin to research and purchase the hardware. So that could be lowered significantly in bulk. As FPGA should be avoided, you could use some 154s 4-to-16 line decoder to generate the chip selects for RAM, ROM, peripherals… And for interfacing slow peripherals, is there any reason not to use the IRQ? Thanks again for your thoughtful comments. They are really cool when you need to reproduce something specific, like a C64, but if we wanted to build a simple, open, hand-replicable system without compatibility requirements, I think an FPGA would be a major hindrance.
. Memory — Amount needed no-paged and minimum amount paged. The stickers would include all the characters the C64 uses, but some keys may be in different locations. First, identify the kind of module your system uses by the form factor the physical form of the module — generally, desktops use UDIMMs, laptops use SODIMMs , then figure out the memory technology Second, your system can only handle so many GBs of memory. In the c64, one 8-pixel segment is drawn over one cycle.
If you have fast RAM like SDRAM or DDR1, the FPGA DRAM controller can even do some caching and bus sharing allowing the graphics subsystem and the processor share the same DRAM. Things I could do little about. Whether this is implemented in a VIC chip, or a large board of discrete logic chips, or in a seperate graphics processor of some sort , is not really that relevant to the system programmer! One idea I am building is a CGA-compatible graphics card with both character SRAM and a flexible output mapper, mapping two neighboring 16-color CGA pixels into two RGB888 pixels, allowing for displaying using HDMI or DisplayPort links. I could imagine a board as follows: Processor — Select one 6502, 6809, Z80 whatever. But not Andrew - he made a choice to give it a try. Alternatively, a RaspberryPi running the RISCOS operating system is programmable in BBC BASIC which has a built in ARM Assembler.
Graphics CPUs: 10x 6502 USD 6 each. There will be 8MB of RAM when the SDRAM controller is working a which time I plan to rework the video to use the SRAM for that purpose. I know it takes little bit of sleuthing on mouser but Seiko-Epson makes graphic controllers that interface as a direct 8-bit Intel80 bus as control and framebuffer. The lowest end plan is roughly a modular, fully static semi-clone of the original IBM PC. The YouTube channel smbakeryt played around for it a bit and hooked it up to a few peripherals.
That includes custom chips from Atari or Commodore or whatever. And as for being at the mercy of the manufacturer for the life of your project, I trust a manufacturer more than and open source project. The 65C02 and 65C816 are both evolved versions of the original chip. Start basic with the CPU board and a UART interface, for example, and add VGA later. Although originally a Motorola fan, I never did build a 68K system.
If a retro gaming computer is needed, then a keyboard encoder and memory mapped video is needed. All of the complex bits for a section could go into a FPGA but state that the internal FPGA design must be available to everyone, and at least one or maybe two other chips not the same series available that can do the job someone has taken the design and ported it to another FPGA and got it to work. For us in the East, it was the most ubiquitous microcomputer for several years. And everyone would be able to make videos on their channels about the process. The keyboard is larger, and uses relatively large keys.
A large circuit board covered in TTL logic the VIC-II chip is estimated at 5000 transistors , would be more expensive than a FPGA! Not at the moment. Memory I would want 128K or 256 of static RAM, with possibly the ability to upgrade it. It can very easily look like a complete joke. In the long run, however, you'll save money because it's less likely you'll need to replace components, and, if you do need to, they're easier to fix. Emulation at hardware level and virtual expansion by updating programming for FPGA. The Altairduino also runs a perfect 8080 simulation on the Arduino Due, which has a 48MHz clock. Or do you really want it to use the identical byte encodings for the characters, including its really weird way of doing lowercase? Who would blame him for deciding that life was too short to venture into the scary and unknown world of computers? It doesn't get much better than having an account with us! I got rid of my C64 at the end of college.