MrMartian

I have this board in a 400 and it just worked the first time. One thought I had, when you put the board in what are you doing with the ROM on the main board?

I used Quartus Lite 18.1 to build, but the programmer part shouldn't matter for the .pof file.. I don't know if there is any way to program the part without installing all of Quartus either. As for whether or not this fix will work, when I was reading through my backlog of posts (since I haven't been on here for a while again) I found in the other Ultimate SD cart thread this same discussion, and a user determined the cause to the same issue I discovered and fixed basically the same way. So I believe this will fix it. Too bad I hadn't read that message before I spent time thinking it through myself..

You will need an Altera USB Blaster (search ebay, often around $5) and then the Quartus software to transfer it.

I don't have an actual right-slot cartridge, so I couldn't reproduce that problem. But, looking at the HDL I can see how it can happen. Please try the attached and let me know if this fixes your problems. The only change in this version is for proper data output, no other changes have been made. Max10_SD.pof

I can say for #2, there is no software way to wake up the card after you’ve chosen a cartridge or hit X to disable the cart. Only the reset button. What use case do you have for this?

I am still working on this system and have made a number of changes but life has been way too busy lately to release anything. I will dig through these issues next week. And obvious ways to test / reproduce what you’re seeing?

I guess I'll have to download SuperBunny and see why it fails on my firmware for the Indus.. ??

According to the attached schematic, there is a 33ohm resistor as a bypass around the 7805 (R203). This would mean, that without a load I would expect the voltage to be pretty close to the input voltage.

That memory test is from the Ultraspeed+ OS

Hello all, life is slowing down a bit again for me so I'm back to digging into Atari stuff.. If I could just get Quartus II downloaded again, I could continue my WIP... I was working on adding direct SD card support but have since figured out how to add IDE (CF) emulation, so like the AVG cart these could act like an SIDE cart. Since Intel can't figure out how to make my account work to download the software, any got a copy of a recent version of Quartus somewhere I could download? Windows or Linux...

Hey look, I've dragged myself out of the boonies.. I like questions like this! The drive uses a hardware UART (the 6850) so ultra speed would be difficult. But, I will look at what is possible with a hardware + software mod

Sigh, I don't know how I missed this. Sorry to be one of those guys, but 85 pages of forum sounds hard to dig through.. How much, and how would I order?

This is based of 1.0b, and until it gets all accepted upstream I will do what I can to keep it updated. As for hiding dotfiles, would you want a toggle or just automatically hide them?

Sure! Basically, when I sent my 'no-diode' changes upstream, the concern was the the six bytes it added to the program were not worth it to remove the need to solder in a diode... Plus I've heard other times that feature x can't be added due to so little free space.. So I started an audit of the code. avr-gcc is not always so smart on optimization so by refactoring loops and things, the program gets smaller. Also, using various functions pull in large chunks of code from libraries, that for what's needed could be coded direct also saving memory. This is my current resulting code, which should have no functional differences at all, just freeing up code space to add more fun!

Can someone test this out? I'm down to ~29.5K freeing up lots more room for adding more features.. I've tested this a bunch and haven't had a problem yet myself, but more eyes find more bugs.. In case there is something drastic, please use a blank SD card or have a backup first.. sdrive-nodiode.zip

Unfortunately, it likely killed it. The voltages on those old cards (+/-5v and 12v) would fry things not expecting them. Do you have another ram card at all to see if the machine still works?

If the crystal is the biggest problem, generating 8.33Mhz is not that difficult a problem, it's easily produced by 25Mhz divided by 3. An oscillator and some logic, possibly a GAL type device..

I have some notes so far about taking the SDrive-MAX (ATMega32) and adapting it up to the Mega2560... It would give all the SD card goodness there is now, plus two serial ports with full flow control, parallel port, and if I'm feeling jaunty I may also add in the hardware for a WD1772 to control real floppies. I've been toying with an All-in-one SIO peripheral so long, and never thought about developing on an arduino until the SDrive thingy.. So, all the pieces are finally coming together for me.. Except time..

You've pretty much summed up the additional features. I would say, personally, that the sio2sd is still the more reliable choice.... But I am working on the code to clean it up.. Others probably are too..

Did you make sure the eeprom file was written first? Or, at least just do it again and then put the sdrive.hex on it. The symptoms you indicate are typically caused by bad eeprom data.

I will probably grab one as well, I have one XF board that's giving me a pain. Do I just order it on your webpage, and it ships whenever?

According to Arduino themselves, officially it will be the ATMega16U2... It only seems to be clones that have a basic USB->Serial adapter... But, if having that works for some, it should work for all..

I looked at the high res pictures, and then googled some more and found that your board seems to use a CH340 usb to serial adapter. Many people seem to dislike these clones as they have problems with them overall.. I will go with this being the root of the problem.

Looking back through the posts, and the picture of your board piques my interest, as it isn't using another ATMega for the programming interface. Do you know if the manufacturer of your board posted schematics? I would expect that we'll see that the serial programming ports are interfering...

Odd... You have things set right. If you put a disk in the SDrive D1: and have your 1050 set to D2:, does it screw up as well?