Jump to content

  2. View New Content
  3.  
  2. → Viewing Profile: Posts: c0nsumer


c0nsumer's Photo

  • Overview
  • Profile Feed
  • Likes
  • Friends
  • Topics
  • Recent Activity
  • Gallery
  • Blog
  • Issues
  • Stats

c0nsumer

Member Since 3 Feb 2009
OFFLINE Last Active Feb 11 2012 8:02 PM

Posts I've Made

In Topic: Sdrive Issue with 130xe

Wed Oct 19, 2011 6:41 AM

View PostHiassofT, on Wed Oct 19, 2011 6:25 AM, said:

Jakub did this with the SIO2SD and put the traces online at his website:
http://sio2sd.gucio....ki/HighSpeed_en

Since SIO2SD and SDrive aren't that different, I'd expect the SDrive results to be similar.

Thanks! That's exactly what I was hoping for. With those caps in place it looks really bad...

In Topic: Sdrive Issue with 130xe

Wed Oct 19, 2011 5:45 AM

A bit off topic, but would any of you happen to have scope output showing these lines with and without the caps? I'm just curious how they affect the signals... I've got a scope here, but no 130XE to do the testing with.

In Topic: Any Interest in a new SDrive NUXX Run?

Tue Oct 18, 2011 8:37 AM

View Postorpheuswaking, on Tue Oct 18, 2011 8:35 AM, said:

Has he removed the offending FCC caps from the SIO port? (I've had issues with random peripherals not working on 130XEs due to this - After discussing with Metalguy I now always snip them off)

No idea, but good thought. I don't have a 130XE so I wasn't really aware of this. Hopefully he'll see this. I'll send him a link to be sure.

In Topic: Any Interest in a new SDrive NUXX Run?

Tue Oct 18, 2011 8:26 AM

View Postvenom4728a, on Sun Oct 16, 2011 10:33 PM, said:

just tried out my Sdrive Nuxx today, and I think something is wrong with it, it loads very very slow, have a buzzing noise coming from speakers, you only hear the a beep every so often. I have another sdrive and it works just fine, loads really fast. Anyone have this sort of problem? Robert Miller

To add to this, after talking with Robert via PMs it seems his issue when using the SDrive NUXX only with a 130XE, yet the a8maestro SDrive works fine with the 130XE. With an 800XL both SDrive implementations work just fine. Multiple SD cards and ATRs were tried, and the differentiating factor between right or not seems to be the Atari hardware itself.

I'm at a loss to explain this, but perhaps the 130XE doesn't provide enough power (or perhaps not clean enough power or something?) and the SDrive NUXX is less tolerant of that than the a8maestro version? This surprises me because the SDrive NUXX implementation is the same design as the original Raster/CPU version; the only differences are in the voltage regulator and LEDs and such. The only way I could see a variance like this causing an issue is if the 130XE can't provide quite enough power and thus the AVR is running quirky.

Anyone else have any suggestions / ideas?

(UPDATE: Note that the SDrive NUXX ships with original firmware from Raster/CPU. It's possible that the a8maestro version has different firmware? I haven't investigated this yet...)

In Topic: SDrive at 126kbit/sec - please help testing

Fri Sep 23, 2011 10:00 AM

View PostHiassofT, on Sat Sep 10, 2011 10:51 AM, said:

View PostFaicuai, on Sat Sep 10, 2011 9:47 AM, said:

Is it necessary to upgrade the SDrive controller to the above revised firmware, or are we dealing with a limitation on my 800XL's Pokey/chipset?
Yes, you need this firmware to use the highest speed, the original firmware won't go faster than ~90kbit/sec.

If you are already using this firmware (better ask c0nsumer which firmware he programmed into the SDrive), make sure you don't have more than 1-2 other SIO devices connected, and that the caps on the SIO lines are removed in the Atari and also the floppy drives (1050s also have these nasty caps, for example).

so long,

Hias

For what it's worth, the SDrive NUXX uses the straight-up stock SDrive firmware taken from the SDrive081012.zip or SDrive20090403.zip packages. More info here.

So yes, if you want to do something that requires new firmware you'll need to flash the AVR with whatever that new firmware is. This exact scenario is why there's a programmer built on to the PCB. Reprogramming the AVR in situ is covered here.

  1. AtariAge Forums
  2. → Viewing Profile: Posts: c0nsumer
  3. Guidelines