Jump to content

Lorin Millsap

Members
  • Content Count

    114
  • Joined

  • Last visited

  • Days Won

    10

Everything posted by Lorin Millsap

  1. Just make sure that will work electrically. Basically those lines are meant to be pulled into certain states which may not be compatible with what you want to use it for. Sent from my iPhone using Tapatalk
  2. Just so you know the IEC lines have diodes and buffers on them, so while you could use them other as intended you are also limited in how the pins can be used. As a whole SPI and a few others are certainly possible. Not a lot of point in it though as there is nothing to be gained by doing so. Sent from my iPhone using Tapatalk
  3. Nope. VERA is complete. The spec is set. Only bug fixes if there are any here on out. Sent from my iPhone using Tapatalk
  4. See, there are workarounds that you haven’t even thought of. Some of the demos exploit the limits. Sent from my iPhone using Tapatalk
  5. The RAM in the Vera is integral to the VERA. We did look at external RAM but it would require a complete overhaul due to timing. And it substantially increases the cost. The next FPGA that has more RAM puts us into a package we don’t want. For the record they types of RAM that are compatible are quite expensive. Not to sound rude, but as is we have way more video memory and color depth than any other 8 bit system and part of the point is for you to come up with workarounds to the limitations. Sent from my iPhone using Tapatalk
  6. If the YM2151 becomes unavailable it would be replaced with an FPGA on a daughter card with pin headers to plug into a dip socket. But we are only crossing that bridge if it becomes necessary. Sent from my iPhone using Tapatalk
  7. Yes and no. It’s wired up such that it can. But at the moment there are no burst routines. Sent from my iPhone using Tapatalk
  8. No, VPOKE is not meant to take advantage of auto increment. VPOKE more fully takes advantage of direct access, but for speed once you set up auto increment you would just keep poking additional values. So if you are sending a sequence you would enable auto increment then VPOKE the first byte in the sequence and POKE the rest. Sent from my iPhone using Tapatalk
  9. One thing to note though is you should from a good coding standpoint, never attempt to read the keyboard or mouse directly. You should use the KERNAL routines instead. If you try to write your own routines it will cause several bad side effects. One is that if the way the keyboard works changes, it will break your code every time. What if a future version used a USB keyboard or a direct matrix? If you use the KERNAL routines you will always work and it would be the KERNAL that would change to match the hardware. Also we have found some keyboards have different requirements. We are making our routine as robust as possible. Custom routines may not be as forgiving. Sent from my iPhone using Tapatalk
  10. We have new code in testing that the emulator doesn’t reflect. When then code passes and we know it works reliably we will update the emulator and documentation. How it works now is not how it will work down the road. Sent from my iPhone using Tapatalk
  11. Again to all the people discussing serial over the user port. RS232 serial is already planned. The routines just have to be written and the vectors are there. Sent from my iPhone using Tapatalk
  12. Valid point to a large degree. Less of an issue here if the system always closes its files, but I can see wear being an issue. To minimize swapping you will have serial. And if you do all your testing in the emulator you will not need to swap cards as much. Sent from my iPhone using Tapatalk
  13. It’s not like it’s large or heavy. Just reach back and pop it out. Sent from my iPhone using Tapatalk
  14. These chips are readily available through our supply channels. This chip was an exception because firstly it met our cost goals and secondly developing an open source FPGA core if the supply dries up isn’t a problem. Yes it is paired with the YM3012. Sent from my iPhone using Tapatalk
  15. You should be using VPOKE. Sent from my iPhone using Tapatalk
  16. The VERA card is exposed to the back of the machine. You just stick the card in. No worries. Sent from my iPhone using Tapatalk
  17. No, that’s 5 lines. These are already decoded active low lines. Only one goes active at any given time. Sent from my iPhone using Tapatalk
  18. Not needed as there is an integrated SD card which is orders of magnitude faster than SD2IEC. No sense in implementing a fast loader for legacy devices when firstly it can be done in software for the cases that need it, which realistically will be rarely. Sent from my iPhone using Tapatalk
  19. It already has it technically. Part of GEOS is already built in. Sent from my iPhone using Tapatalk
  20. This effectively nerfs most of the reasons for the X16s existence. Sent from my iPhone using Tapatalk
  21. I don’t believe we will support REL files on the integrated DOS. Sent from my iPhone using Tapatalk
  22. Have you tried dropping the volume on the channel you want to fade. Or you can play samples. Sent from my iPhone using Tapatalk
  23. No. You are not understanding that at all. The bank registers are mapped are located in memory locations $00 and $01. They are latches that capture writes to those locations. As long a the memory model doesn’t change then you can read those locations too and the value they contain is always the same as what is written. But if you make that area of memory swappable suddenly the value stored in those locations will not match what is stored in the latches. There is no practical or simple way to do it. Our goal is a simple memory model. As I’ve stated before the use case is not really that useful. A relocatable ZP makes more sense and that requires a different CPU. Once you start remapping too much you are moving away from banking and starting to look more like a full MMU. Sent from my iPhone using Tapatalk
  24. The system is not intended to multitask. It is a direct to hardware system and while you could do simple multitasking, it’s not our design goal. They are used as quick access stash points for code, most programs will only use maybe a couple dozen tops. If you aren’t using BASIC you can repurpose all the ones reserved for BASIC and the same goes for KERNAL ones. So from a dev standpoint it’s not needed furthermore your dev tools would have to keep track of which ZP you are accessing. The ZP banking is already shadowed. What you are asking is not a simple change. This lands firmly in the category of the hardware is set and this isn’t going to happen. In fact most future changes are bug fixes. Sent from my iPhone using Tapatalk
  25. Because how many variables do you need? It adds complexity and it’s not as useful as you think. Also the banking is stored in zero page so that wouldn’t work. Sent from my iPhone using Tapatalk
×
×
  • Create New...

Important Information

Please review our Terms of Use