Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Ju+Te's Achievements


Apprentice (3/14)

  • Dedicated Rare
  • Week One Done
  • Collaborator Rare
  • Conversation Starter Rare
  • First Post Rare

Recent Badges



  1. For that price point I would expect high-quality PBT keycaps for Cherry-MX keyboards.
  2. I wanted to say, an FPGA as a first thing shipped to end-users might be a good idea so people get hands on the hardware quickly. If it turns out - based on the feedback of the early adopters, that the wiring needs to be changed, they don't have a board incompatible with future versions, but simply can reprogram it. Yes, such an early state FPGA would be more expensive than a later iteration, but I expect it to be cheaper than an initial generic parts kit.
  3. After thinking to have understood the FPGA thing, I would not mind getting an X16 in FPGA only. I don't have to solder it. IMHO the success of such a project depends on the amount of the community. Getting the price down seems for me the most important part in the equation (having a physical thing instead of just an ARM based emulation). Could an FPGA for the early adopters have the option to "change the wiring" if it seems necessary to fix something later?
  4. Wow, this looks like a really good programming environment! Much more structured and high-level than pure assembler language - approximately that what I had dreamed of. And, as a Java developer by heart, I also like how it is made.
  5. If I would treat VERA as a black box, how is it accessed from outside (the 6502 CPU)? Does it have a couple of address input and 8 bit data in/output pins that are connected just like RAM or RAM to the bus of the CPU? How this internally works? Do some FPGA already have some processor built-in or are there standard libraries available for the FPGA-programming software that "wire" certain virtual processors inside the FPGA? Do I understand it from the datasheet correctly, that level shifters are needed to communicate with a 5V bus because it operates at 1.2V?
  6. I'm not experienced with FPGA at all, but it sounded to me like they could be programmed that they form some kind of PCB of some generic (TTL) parts. If I understood this correctly, the schematic already exists (as "program" for the FPGA). I might be completely wrong, so please correct me.
  7. Small correction: the Z8 clone was made in East Germany, not the USSR. What I really like about the Ju+Te computer in the 320x192 pixel variant is the brilliant idea to use a second processor with nop and jump commands to create the timing for the monitor signal and the addresses for reading the video RAM.
  8. <snip> deleted, because I wasn't aware of David's answer on Aug-21</snip>
  9. @sundownAt least for the VERA an FPGA seems to be necessary, unfortunately. So having an FPGA-free X16 based solely on standard "factory new parts" seems not to be an option.
  10. An external keyboard (with a state-of-the-art connector) allows to change it, it allows to position it where it's best for you. As a software developer a decent keyboard is one of my mostly used tool. Hence I'm using good ones for a longer time. Haven't thought of bad keyboards because I would not buy bad ones. Having a floppy sounds like a strange thing to me, but for some it might contribute to the retro feeling. And finally, retro computers are nearly only for the feelings of the "good old times", for the feeling of youth, like an affordable time machine.
  11. This would be an anti-feature for me. Even my old 8-bit machine has an external keyboard - it is much more ergonomic. I hate using notebook keyboards/mousepad for the very same reason. IMHO, for a new 8-bit system, it is useful to combine the advantages of the 8-bit world (direct hardware) with more modern parts and ideas (hence I prefer the x16 to have a USB keyboard connector). Maybe for some customers the bad usability also is a feature of the nostalgia, but I like to avoid this.
  12. So this won't work for debugging the ROM? PS: Sorry for having hijacked this thread.
  13. Would it technically be possible to have a debugger work on the 6502, e.g. by setting an ultra short timer that fires an interrupt after having executed one command?
  14. What exactly the Basic is used for? For doing the ultimative first steps in programming it is OK. But for writing real nontrivial programs or games with it, it would be much too cumbersome for me (I'm used to IntelliJ IDEA since nearly 20 years). Whatever language I would use for developing serious software for the X8/16 hardware using a PC (even if it is just assembler) - it would be very cool to have some kind of hardware debugger available that allows me to step through the commands (in the language I use), see all the registers and memory contents. I had a disassembler and debugger on my 8-bit machine - without them I would not have been able to write that much code.
  15. What means the suffix after "X16"?
  • Create New...

Important Information

Please review our Terms of Use