aotta

Hi RKOTower, happy you successfully made the RTO, and i love the case with golden remarks, i must buy a gold uniposca! 😝 About the folder handling, i used sdfat library that doesn't support "previous directory" command, so i implemented a simple code for handling ONLY ONE subdirectory level (i use the directory 0-9, A, B, C etc. for grouping and sorting roms). Further sub level may be added, but i had no time neither motivation for working on it.

🤣🤣🤣🤣

Yes, i'm an engineer, not a player, but i completed a couple of mission wihout any artifacts!

I can confirm that Antartic Tales works fine without ECS... and with RTO cart with default timing:

Thank you for clarifying it, i red in the thread mentioned on your game that it work on jzintv "with ECS on", but didn't tested myself.

Antartic Tales use ECS commands (you can check it reading the ECS section in its config files), so it works with ECS module, you must test the RTO with ECS harwdare. i'm pretty sure it's not a timing issue! I have my ECS in its box, may be i'll check Antartic Tales with it in next days if i'll find time

Nor me neither the dozen of italian guys that made a batch of RTO carts have had issue with that roms (and bad apple was one of the most tested by me, since i worked a lot for manage his huge banking switch). And we used the default timing, so it seems strange to me the great difference with your tests. Could you test your cart with different console? Which 74245 logic IC did you use?

Yes these errors appear to be caused by a ROM read error so, definitely, a timing issue!

@Tissemon this is the 5-11under's version thread, we should talk about the "original" RTO in its 3ad. Anyway, since 5-11under has found some issue too in beta testing, i could say that there's no perfect way to computer the delay, and a lot of things may interfere (i.e. the compilation option - i used "faster" and not "fastest" or the speed of the Teensy's CPU - i left it to its default), but the value you used for Dracula seems too low in my opinion. Can you test your Inty with original cartridge? one of my friends had issue with Dracula (dark video and blurred portions of the screen) due to grounding external video pin missing, that i hadn't since i use an RGB output and not the RF. In version 1.1 the ext-video should be solved, but maybe it's related to your issue too. RTO is an "active" cart, differently to the original Roms, so grounding and power are more critical and it's not easy to find what's wrong when a game shows glitches. But i tend to exclude it's something wrong in your Intellivision's IC!

Get the correct timing was the most tricky works in creating the RTO, and in my first versions i added a routine in NACT phase handling that changed the delay time with up and down button on the cart, while playing, and showing the value in the display, so i could reset the inty and check new if values was better than previous! I left the actual value (delRD=482; delWR=540) since they worked fine in my PAL Intys, but a smart french guy found that different setting are needed for SECAM Intellys (delRD=626; delWR=702), you can find his RTO version at https://github.com/zx81zx81/RTO-Cart-secam . And, value used for SECAM version are nearer to the ones used by @JohnPCAE in his bird's nest (i'll never stop to thank him for sharing the source!), so may be timing i use it's a bit faster than the very right one. I think you could simply try this value for the Inty II, or use values between the 2 setting. Let us know!

RTO use .bin+.cfg and supports bank switching, ECS, extra ram and hacks pokes. Just not supporting game saving, and personally i think it's a feature rarely used in homebrews and I'm not interested in implementing it. Anyway, Teensy used as engine in RTO has flash ram too and the project is open source, so who's interested could add that feature. Speaking about differences between Backbit, LTO and RTO is not confusing and unnecessary IMO, no more than discussing if it's better a physical rom than the binary file!

Nice work evietron, but implementing only JLP saving schemas seems not very useful to me, that's why i didn't implement it in my RTO multicart. New games that use JLP acceleration code are often encrypted too for anti-piracy purpouse, and i think only LTO original hw & sw could manage them. By the way, i'm fashinated by your multicart, and i'm only waiting since i'm not sure if i want to buy first it or your Chip tester... i love it!

i can agree... only to add that cost of RTO depends in great part by the Teensy 4.1, i bought a couple from the productor in USA so i paid them 27$ each one, but prices are very different around the world and market. On ebay someone started selling the empty PCB for RTO too, but it's cheaper buy 5 of them from china (about 10$ all them). So, total price for a "power user" may be under 60$, and it's not so difficult to assemble it. Of course, if you are not able to solder an IC and you have to pay someone for doing, you could "turn" to Backbit, it's a great piece of hardware, i like it and maybe one day i'll buy one (i didn't realize it's again available!). About compatibility, i think RTO and Backbit are quite the same (and i didn't found any rom bigger than "The big apple" until now, but never say never... ), and some feature LTO has, like encryption or new instructions, won't be implemented in no multicart since they are a LTO "encrypted" solution!

You don't have an RTO, so i don't know how you could think the backbit may be better.... it's for sure a different thing, more expensive and multi platform, it use a proprietary format for roms, and has a 1mb max size limits. No multicart are done for larger audience, but who cares? But the most important thing is that anyone can now choose and make or buy an Intellivision Multicart, since the LTO and before the CC3 went out of production!

no, i made only a couple for me, and given support to some friends that builded a small batch for themself. But 5-11under is building here some of his customized version:

ah, so did you change the splash screen too?

...may be you will thank the author in the box case, as my Italian friends did!

But where is printed the project's author name??

Thank carlsson for the clarifications. So, if somebody wants to play large rom like ” bad apple” demo, and doesn't own a LTO flash, must turn on my RTO cart! 😝

In a very few words, LTO games (ROM encrypted for LTO, or ROM using LTO's new special features) run only on LTO Flash. All other roms build for Intellivision works with backbit (i'm only not sure if chess ROM and its "RAM mapping" was fixed) and RTO cart too.

Yes, i made no BOM for last version since it could be easy to get from kicad, there is only - in the cvs in the "old" folder in github - the one for the previous version. If you want to use the 3d box i designed, you're right with the rectangle "standard" leds (i bought a multicolor box of them since i prefere them to cylindric ones ) and i used 6x6x12mm button, the shell profile go low in the buttons area so you don't need too high ones, unless you want to use some button caps over them.

No, the Pi pico hasn't enough gpio and missing the SDCard, so a porting to this platform is quite impossible withouth redrawing the project from scratch. About adding ECS or Intellivoice emulation, the main issue is that when selected the rom the "loop" cycle must be always "online" to the console to answer to read/write request from Intellivision, so any other code would interfere with normal functionality of the RTO. Maybe a different approach with a GPIO asynchronous routines for I/O ram and rom and multitasking for the emulation, could be implemented, but it's out of my scope (and interest) for now. But i left opensource / openhardware the project for anyone interested in improve it!

But also: Proverbs, 19:15 "Hate of work sends deep sleep on a man: and he who has no industry will go without food." There is no drought of RTO, you can build easily yourself like dozens guys already did.... if you're lazy or have no industry, you have to wait and pray!

I confirm the RTO use the configuration files as Jzintv that are linked in first post of this Joe's topic: RTO looks first for the ".cfg" file with same name of selected BIN in same folder and, if not found, looks for the "0.cfg" file (the "standard" and most used rom map for Intellivision's carts) into root folder and use it. If neither the 0.cfg exists, the RTO shows an error message on display and halts.

I suggest you to read the rto related threads (included the present) and you'll find all the answers. That's the sense of this forum 😜 (edited) well, probably the answer to "how update the firmware" is not so clear in the discussions, but is in the github repository. Anyway, in short: the firmware is inside the Teensy 4.1 board that is the "core" of the multicart, so any update will be a loading of new code in the Teensy board, and the usual way is via usb connection to the Teensy and Arduino IDE tools.