Jump to content
IGNORED

SDrive-MAX ATX support


Farb

Recommended Posts

I'll clean those up but just to be clear, the SDrive-Max works fine when not plugged into the 850. Now, I just thought of something. I'm using my USB port as the additional power supply for the SDrive-Max and now wondering if I need use a dedicated 7-12v power supply.

As far as if the software needs BASIC, it's PlatoTerm and it does not because it boots up just fine when the SDrive-Max is not plugged into the 850.\

 

Another possibility is my 850 isn't fully functioning. I have another one but that doesn't turn on. I'll test that out next.

Edited by Justin Payne
Link to comment
Share on other sites

I'm pretty sure my SDrive is putting 5 volts back into the machine. Someone suggest that I was having an issue with my PIA on my 800 so I stepped down my power supply on my Arduino from 12v to 5V. I then plugged the SDrive into my 130XE and powered it on. The touchscreen looked strange but after touching it was fine. I went to switch off the power to my 130XE but the power was still slightly on. I'm a bit worried now that the 12v power supply went into my 800 and damaged the PIA chip.

Thoughts?

Edited by Justin Payne
Link to comment
Share on other sites

I'm pretty sure my SDrive is putting 5 volts back into the machine. Someone suggest that I was having an issue with my PIA on my 800 so I stepped down my power supply on my Arduino from 12v to 5V. I then plugged the SDrive into my 130XE and powered it on. The touchscreen looked strange but after touching it was fine. I went to switch off the power to my 130XE but the power was still slightly on. I'm a bit worried now that the 12v power supply went into my 800 and damaged the PIA chip.

Thoughts?

 

What exactly do you mean by the part I've highlighted … What was "still slightly on"? The SDrive-Max or the 130XE?

 

If you've soldered everything properly, with no bridges or hidden shorts in the wiring, your Arduino shouldn't be putting anything back onto the bus. And just to be 100%, you've got things wired so that the +5V line on the SIO port is NOT connected, right?

Link to comment
Share on other sites

I noticed the other day that the 1.1 beta branch has had a few changes, some of which could be significant (some bug fixes and tightening up of FAT code, for instance), But also saw the most recent commits were to add multi-line support for long file names. I downloaded the code this morning, compiled it on my Ubuntu virtual machine (so much easier and more straightforward than doing it in Windows!) and flashed it to my device.

 

Two obvious changes beside the version number increment: first, when you tap a name in the file list, the top line display scrolls faster. Not as fast as I'd like it personally, but much better than it was before. Even better however, is that the long file name is now displayed across multiple lines at the bottom in the status panel. This is a very useful change, since a LOT of the files we all use come from various archives, with naming conventions that include year, publisher, NTSC/PAL, etc. And in the case of ATX files, sometimes even describe label variations so we can tell one version and copy protection scheme apart from the next.

 

I've attached a ZIP of all the files. Programming your device is left as an exercise for the reader. :) Basically if you know how already, great. If not, there are instructions back in the bowels of this thread.

 

 

sdrive-max-11b-20190224.zip

  • Like 6
Link to comment
Share on other sites

I've attached a ZIP of all the files. Programming your device is left as an exercise for the reader. :) Basically if you know how already, great. If not, there are instructions back in the bowels of this thread.

 

 

 

Thank you for continuing to upload these compiled updates, I very much appreciate it. :)

  • Like 2
Link to comment
Share on other sites

  • 2 weeks later...

I'm using the 4 pin header in your pic but I'm trying to keep this as small as possible so it's as easy and cheap as possible for people to order one from OSHPark. I couldn't justify the increased width to stretch over to the A5 pin and really wanted to keep the 6pin header as an anchor for the board, it has to put up with quite a bit of torquing from the sio lead. I tried to reposition the IC over that side but I couldn't get it small enough to keep me happy.

 

If v2 still feels too fiddly/difficult I'll revisit the idea for v3 :D

Hi,

I just got my order from OSH Park and I have an issue, the board lines up with the wrong connectors on the Uno R3, it lines up with the second row of pins, the SCL, SOA, 5V, GND, not the first row RX, TX, 5V, GND. Anyone else having this issue?

 

Thanks,

Gavin

Link to comment
Share on other sites

Wondering about adding a switch (read... pinheader) to the UNO2SIO board between +5v and SIO pin 10. Would mean everyone would have to add a jumper or bridge if not using a switch. Thoughts?

I have been adding switches to the drive I have been building for months. I would love to see it added to the board.

 

Thanks,

Gavin

Link to comment
Share on other sites

Yes, I've noticed there are many variations in the layout of the UNO board but these two seem to be the most common.

arduino-UNO-R3.pngarduino-UNO-R3-3.png

 

 

The board was designed for the second one of those, you are using the first.

There is another common UNO variant (a genuine UNO) and it doesn't have that pin header at all, nor the holes on the top for soldering wires to. I don't have any of these variants except two rows of headers version, if anyone wants to send me a different one I'm more than happy to produce a variant board to match it.

 

  • Like 1
Link to comment
Share on other sites

Thanks!

 

I'm a bit curious though, as isn't there supposed to be a problem with the circuit ("recipe for disaster"), as described in http://atariage.com/forums/topic/288901-sdrive-max-installation-help/- never quite sure how bad these problems actually can be though.

 

Also, isn't it © 2018 - 2019, though this is obviously nit-picking?

 

Thanks again!

Link to comment
Share on other sites

Thanks!

 

I'm a bit curious though, as isn't there supposed to be a problem with the circuit ("recipe for disaster"), as described in http://atariage.com/forums/topic/288901-sdrive-max-installation-help/- never quite sure how bad these problems actually can be though.

The "recipe for disaster" has nothing to do with this board, it's just that the uno has 2 ways to power it and adding the SIO port gives it a third. Potentially someone might plug in both the SIO plug and the Power plug at the same time, there is a risk of damaging something. I was actually helping someone in PM the other day who was doing this, despite being asked repeatedly if they were, and they saying that they weren't. The only problem they had was a corrupt screen display and the device wouldn't work. Once we solved the 'mystery' everything was ok and it did no harm. I can't say that would be true for everyone.

 

V3 above now has a switch point on it to break the connection between the UNO and 5v from the SIO (Pin 10). As wired it will not connect the SIO 5v, but if you are wishing to power from the SIO port, you can bridge that point, either with a switch or a blob of solder or a bit of wire.

 

Also, isn't it © 2018 - 2019, though this is obviously nit-picking?

 

Thanks again!

 

Yes that is nit-picking! it's also up to @BigBen if he wishes to retain his © on this design. I'm sure he'll let me know if he is unhappy with the © message I've used.

Link to comment
Share on other sites

I have just started assembling my sdrive-max.

It seems I have LCD HX8347G. I have downloaded firmware 1.0 and took files from appropriate directory matching my screen.

Flashing process succeeded (I was using batch file from the thread).

My Arduino is powered via usb only. After restart it has white screen. No crosses for calibration. It seems the firmware does not recognize the screen.

What else can I do to get it working?

  • Like 1
Link to comment
Share on other sites

I did run Arduino IDE with TFT example. Screen works fine

It is reporting HX8347G

 

00:42:27.956 -> Found HX8347G LCD driver
00:42:28.198 -> Benchmark Time (microseconds)
00:42:28.233 -> Screen fill 449344
00:42:29.134 -> Text 105688
00:42:32.284 -> Lines 679384
00:42:35.660 -> Horiz/Vert Lines 55444
00:42:36.281 -> Rectangles (outline) 39756
00:42:36.867 -> Rectangles (filled) 1259092
00:42:38.693 -> Circles (filled) 340072
00:42:39.108 -> Circles (outline) 280276
00:42:39.871 -> Triangles (outline) 150444
00:42:40.561 -> Triangles (filled) 803996
00:42:42.074 -> Rounded rects (outline) 112324
00:42:42.732 -> Rounded rects (filled) 1316376
00:42:44.600 -> Done!

Link to comment
Share on other sites

I have just started assembling my sdrive-max.

It seems I have LCD HX8347G. I have downloaded firmware 1.0 and took files from appropriate directory matching my screen.

Flashing process succeeded (I was using batch file from the thread).

My Arduino is powered via usb only. After restart it has white screen. No crosses for calibration. It seems the firmware does not recognize the screen.

What else can I do to get it working?

 

Let's break this down a bit more. First, when you say "took files from appropriate directory" did you copy both the eeprom_writer.hex and SDrive.hex files from the screen directory and copy them to the root directory you're flashing from, overwriting the default versions? Second, when you flashed the Arduino, did you follow the steps of the batch file completely, including unplugging the board after both files when prompted? And third, are you certain you used the correct screen files? Currently both hx8347g and hx8347i model screens are supported.

  • Like 2
Link to comment
Share on other sites

I did exactly that. Everytime I took files from hx8347g subdir (both)

I also tried 1.1b files (also coping to the directory of the averdude tool.

Every time I did the test I unplugged power (usb) waited few seconds and plugged it back. flashing was successful.

                     You selected COM4

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.01s

avrdude: Device signature = 0x1e950f (probably m328p)
avrdude: NOTE: "flash" memory has been specified, an erase cycle will be performed
         To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: reading input file "eeprom_writer.hex"
avrdude: input file eeprom_writer.hex auto detected as Intel Hex
avrdude: writing flash (3544 bytes):

Writing | ################################################## | 100% 0.76s

avrdude: 3544 bytes of flash written
avrdude: verifying flash memory against eeprom_writer.hex:
avrdude: load data flash data from input file eeprom_writer.hex:
avrdude: input file eeprom_writer.hex auto detected as Intel Hex
avrdude: input file eeprom_writer.hex contains 3544 bytes
avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 0.54s

avrdude: verifying ...
avrdude: 3544 bytes of flash verified

avrdude: safemode: Fuses OK (E:00, H:00, L:00)

avrdude done.  Thank you.





              Diconnect USB cable from PC and reconnect.
                 RESETting the UNO will NOT suffice !!!
             Wait until the PCs COM-port is active again
                        then press any key

Press any key to continue . . .

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.01s

avrdude: Device signature = 0x1e950f (probably m328p)
avrdude: NOTE: "flash" memory has been specified, an erase cycle will be performed
         To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: reading input file "SDrive.hex"
avrdude: input file SDrive.hex auto detected as Intel Hex
avrdude: writing flash (31098 bytes):

Writing | ################################################## | 100% 5.34s

avrdude: 31098 bytes of flash written
avrdude: verifying flash memory against SDrive.hex:
avrdude: load data flash data from input file SDrive.hex:
avrdude: input file SDrive.hex auto detected as Intel Hex
avrdude: input file SDrive.hex contains 31098 bytes
avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 3.98s

avrdude: verifying ...
avrdude: 31098 bytes of flash verified

avrdude: safemode: Fuses OK (E:00, H:00, L:00)

avrdude done.  Thank you.





           The programming has ended.


Press any key to continue . . .
Edited by MADRAFi
Link to comment
Share on other sites

Hi,

 

Did you attach the screen before or after programming the Arduino? I wrote up how I went about setting up my sdrive-max a while ago (possibly earlier in this thread), but I only attached the screen after programming. One of the comments was that if you attach the screen before programming, there is some feedback on the screen during programming - did you see anything? It might be worth checking for good physical contact, and maybe cleaning the pins, though they should be good from the factory. Also check the wiring - can you upload some photos of how you have wired everything up?

 

I would also suggest checking the file sizes of the files in the folder against the file sizes in the log file, just to make sure you are uploading the right ones (I don't have access to my pc/8-bit, so can't help you out with this).

 

Hope this helps a bit.

Link to comment
Share on other sites

The screen works if I use Arduino IDE and send sketch from TFTLCD-Library-master->graphicstest

 

the screen ID which works:

identifier == 0x7575

 

I am sure I am uploading the right files

 

PS I have only arduino and LCD connected- trying to flash it before start soldering.

Edited by MADRAFi
Link to comment
Share on other sites

Hi,

 

I think you need to solder up the connection - I haven't checked the code, but A5 needs to be connected up to the SIO socket (COMMAND pin for A5), possibly there is a check on the value in the code, which may be undefined if it isn't connected (this is all guesswork though).

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...