Jump to content

SolidState

Members
  • Posts

    13
  • Joined

  • Last visited

  • Days Won

    1

SolidState last won the day on January 4

SolidState had the most liked content!

Recent Profile Visitors

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

SolidState's Achievements

Newbie

Newbie (1/14)

Collaborator Rare First Post Reacting Well Dedicated Week One Done

Recent Badges

14

Reputation

  1. This doesn't include all the overheads. A typical "retail" price would be 2.5 to 3x the COGS. If you run it as a one-off Kickstarter project with no after sales support then you could get away with 2x COGS. That puts the price of the base kit at around $500-$550. If you want to assemble and ship a finished product then the costs go way up. You would easily be getting to the $1,000 price point.
  2. I'm not too sure. I took a couple of screenshots of the prototype board in action.
  3. PC power supplies have minimum load requirements to regulate correctly. The original IBM PC power supply (192W) had a minimum load requirement of 7A on the 5v line (35W). Modern supplies are going to have much lower minimums, but pulling only 0.5W from a 300W is going to be problematic. Is the PC case/power supply still part of the plan?
  4. Frank posted a demo on Facebook a couple of years ago. It was streaming 320x240 video from the SD card at 4 bits per pixel. He estimated about 300kB/s reading full sectors, with normal accesses around 200kB/s read, 64kB/s write. I'm not too familiar with the IEC Bus, but Wikipedia quotes a speed of 400 B/s for the Commodore 64 with a theoretical top speed of 6.25 kB/s. So best case scenario is about an order or magnitude slower.
  5. I've bit-banged the PS/2 protocol by inhibiting the clock and checking it periodically (15 times per second). I tested against a wide range of keyboards and found it can take up to 4000us for some keyboards to respond when the clock is released. And I would say it is often the case that a keyboard will respond fast (within 100us) and then take a while (>2000us) on a fairly random basis. I have the Perixx keyboard (the same model planned for this project) and it tends to be more on the temperamental side. I think that's why bit-banging with the 6502 has been abandoned and the plan is to now use the AVR processor for the keyboard interface.
  6. David hasn't checked this forum in over three weeks and frankly I don't blame him. His interests and productivity lie elsewhere. There is still substantial technical work to do here and even a basic kit release will involve a financial risk I doubt anyone is willing to take. Someone will need deep pockets or start remortgaging property when the unforeseen crowd funding logistics go wrong. I think the only way forward at this point is to open source the entire project. Sharing all the details with the community will bring in the missing resources and energy to help push this over the line. There could be a sunk cost fallacy here though and that might explain why things have stalled out in this near-permanent limbo.
  7. Me too From what I understand these are volatile devices, so it forgets all the "circuitry" when powered off. The serial FLASH is used to store the firmware/RAM image and it gets pulled into the chip on power up. The VERA board would be the same way and probably has an identical FLASH chip on it.
  8. What was posted was a complete standalone project. I have a copy of the following repos: commanderx8 / x8-emu - emulator commanderx8 / x8-rom - X8 ROM containing BASIC and KERNAL commanderx8 / x8-fpga - FPGA image in Verilog commanderx8 / x8-pcb - KiCAD files of schematic/PCB I played around with it using an iCEBreaker board a few months ago. I can't remember if that board had enough I/O breakout to support everything. If it did then could create an X8 breakout board for the iCEBreaker ecosystem. I'm buried in another project so didn't pursue it much further. It looks like there's close to 100 people interested in an X8 board, so this might be one way to get them the hardware. It's amazing how much work went into the X8 now I take another look at it. I don't understand why you wouldn't release it.
  9. What was posted was a complete standalone project. I have a copy of the following repos: commanderx8 / x8-emu - emulator commanderx8 / x8-rom - X8 ROM containing BASIC and KERNAL commanderx8 / x8-fpga - FPGA image in Verilog commanderx8 / x8-pcb - KiCAD files of schematic/PCB I played around with it using an iCEBreaker board a few months ago. I can't remember if that board had enough I/O breakout to support everything. If it did then could create an X8 breakout board for the iCEBreaker ecosystem. I'm buried in another project so didn't pursue it much further. It looks like there's close to 100 people interested in an X8 board, so this might be one way to get them the hardware. It's amazing how much work went into the X8 now I take another look at it. I don't understand why you wouldn't release it.
  10. The board has a Wifi UART. It provides a basic AP that you connect to and then telnet to the board to establish a serial connection. You could also do TFTP to transfer files to/from the memory.
  11. There was a discussion about the X8 files on this thread. It looks like the repos were made private, but I think there are some forks out there (the image was a render I did just now from KiCAD).
  12. I'm not sure what all the trepidation is all about. Frank released the entire design files for the X8 under a 2-Clause BSD License at the end of last year. The Cloanto IP makes it a bit problematic to build and ship as a finished product though. It could be done as a "dev kit" and you get to flash the firmware. The board comes with an integrated Cortex-M0 host processor, so it's already setup for this.
×
×
  • Create New...

Important Information

Please review our Terms of Use