Jump to content

ricortes

Members
  • Content Count

    732
  • Joined

  • Last visited

Community Reputation

288 Excellent

About ricortes

  • Rank
    Dragonstomper

Profile Information

  • Gender
    Male
  1. Accuse me of being pedantic with a pedantic reply? OK Sheesh, read the text I was referring to one more time. "Those mcufriend screens seem to cause more trouble then it's worth. I have two that are worthless and not usable with any of the drivers. Ended up with two ILI9341's and they work flawlessly." We will have to agree to disagree me thinks. This strong of a statement needs to be qualified. I didn't point out your post as being a problem because it was qualified rather then a blanket statement like the above.
  2. Qualified yes. I've used that exact display and it works fine. Problems are similar to people saying our Atari RS232 pin out is non standard: They say the IBM PC is 'the standard' but it came out ~3 years after the Atari so you could correctly say IBM is the non standard. There is nothing inherently wrong with the MCUFriend displays other then being really cheaply made. The problem is IIRC the screen layouts are different between what is the considered the 'standard' Sdrive Max i.e. the upper right of the display of one is the lower left of the other. The other problem is they use a different addressing/pins for the touchscreen. When the Sdrive software tries to read it, it just comes up ~floating or no input when used with the MCUFriend display. Which brings us to a dilemma: Even if the authors of the SDrive software wanted to support other displays, where would it all end? I mean they don't own every display ever made to test it out with. Kind of an impossible task to support everything ever made and everything that will be made. Easiest way to do it is as they have done, support a good choice of available devices. I kind of object to the characterization of the MCUFriend being more trouble then they are worth because the way it is stated, it reads like there is something inherently wrong with them. If the designers of SDrive happened to chose the MCUFriend display it would be the standard. Here is a link to a tutorial where they put the exact display traindriver69 is trying to use through its paces. https://electropeak.com/learn/arduino-2-4-touch-screen-lcd-shield-tutorial/ I can also vouch for the SD card on these working just fine.
  3. I buy a lot of parts from China. It has been my experience for anything going as individual items i.e. a TPA2030 audio IC for instance, you really have a better then average chance of getting something that is a manufacturer fallout if not just plain mislabeled. Seems to make sense in that I've heard a lot of projects never get done. You find a barrel of TPA2030 in the dumpster outside a factory, sell them on eBay as new. You refund maybe 30% of sales but for the 70% or so of projects that never get put together, nobody knows and you keep the dough. I do get good luck with assembled devices or sub assemblies. Apparently the manufacturers of devices know how the game is played there and use legit suppliers. Some of the stuff, particularly with displays, go under such cost cutting I'm more surprised we get anything that works. Stuff designed to work with headers and connectors just soldered directly to the board kind of things. I still have some displays I bought 2-4 years ago made this way and they are still chugging away.
  4. IDK. I have grandchildren and the funny thing is, they literally don't know what FM radio is and could care less about what is available on it. Me on the other hand, I constantly listen to the radio at home and in my car. I have become a parody of myself. Bought a new 3 in 1 workstation [hot air, power supply, solder]. Promptly turned several boards to charcoal: DOH! Solder composition has gone through several iterations to low melting stuff that flows when you look at it. All the old junk I have i.e. Atari, boards catch on fire before the solder melts. Setting up a home brew Bluetooth amplifier sent the power supply into shock, taking out the adjustable power supply which sent full current to the soldering iron which failed shortly after turning red hot. DOH! Preset volume at full 50 Watts/channel will do that to your power supply. I am now on my second 3 in 1 workstation. hehe Trying hard to get up to speed on modern techniques and methods. I've bought a number of practice boards for surface mount and a couple of tubes of solder paste. Seems hopeless in that even if I do get going with something that uses current technology, my grand kids will still prefer YouTube. That is the problem with anything we can do or conceive. About the only project they seem to think has merit is me building a ridiculous electric guitar + amplifier that uses the old spring type reverb. It's hard to stay relevant. I am satisfied winning small battles. After taking over my tablet a couple of months ago my girlfriend told me yesterday she wanted an upgrade and is interested in a Bluetooth amplifier for her home entertainment center: Small wins.
  5. There are a lot more practical reasons for being upset with the direction things are headed if some wags are to be believed. I actually have a Yahoo mail account that is virtually unusable because of the level of advertisements and junk they shovel at you. According to one wag, 40% of the Internet is tracking and advertising. You pay for that with your connection fees and slower response from web sites. Think about it if that figure is right, it is in the face of all the streaming Netflix, YouTube, et al that goes on. It has the ring of truth to it in that one of my friends from Mexico only pays $11/month for his cellphone service. Not funny particularly. I made a 911 call because of a psycho that refused to leave my house. Once they knew police were on the way she agreed to leave and I gave her a ride back to town. I notified the police their services were no longer needed. About 8 miles from my house a cop car came up behind me and pulled me over to the side of the road. I then went through ~an hour of searches and questioning and genuinely rude questions and accusations on the side of the road. Understand for some reason I get swatted a lot. I've had two people call in that I was armed and murdering someone. I've had people say I own a 100 lb pitbull that was attacking people in the neighborhood. I've had people call in domestic violence reports as in wife beater, I live alone.<sic> I've had people call in my house was on fire with choking black smoke coming in their house through the foundation, fake of course. I won't own a cellphone that doesn't have a removable battery. Understand a lot of this I've brought on myself. I do some charity work with homeless and their mental problems are an impediment to their own best interests. One woman showed me a report from 911 where she had called them 19 times to report the same guy as proof she wash't paranoid.
  6. This. Not that I agree with that particular set of goals, just that it narrows down what can be done with what is available. I don't think it could be approached by an Arduino and an RPi would have some latency problems due to its multi tasking environment. Electrotrains did an excellent fpga in a cart. You start to run into acceptance problems with costs when you go this route of course. I *THINK* they were about $95 with all options. Don't get me wrong, adding a RPi to something like this would be good for Bluetooth, HDMI, WiFi, et al, just that the RPi with SD card and interface will add another $50-$100 to the $95 price tag. When stuff starts approaching $200, I usually opt out.
  7. To what end? A simple interface like is done for 8 bit data could be done similar to the SPI. The protocols are usually pretty simple like first write is command and subsequent bytes specify parameters followed by data. i.e. first write say $0 is write memory, next two bytes are start location, next two bytes are number of bytes, data. It would have some speed advantage, just that what would be the purpose? We already have fast I/O parallel devices, you are limited to what you can display on an Atari screen to ~8k bytes. It's possible to do something like a quick 80 column screen, just that a lot of people that need 80 columns just switch to a Intel platform cross compiler/assembler.
  8. Right, only 16k RAM BUT the carts have 32k address space. Natively the 800XL only has room for 16k of cart space. Probably a lot of ways to do it, all tough. You would need some way of banking the 5200 cart in an XL to read out the 16k that isn't normally accessible. Somebody hot could probably do it. Something like a latch/decoder circuit like the OSS Supercarts<74ls74 + decoding of Phase 2 clock<?> and cartridge select line> to bank it, a bit of program to copy the 16k that can't be addressed to the XL RAM area, switch to the upper 16k of the cart in to appear in the normal XL/5200 area. You would probably have to see if the XL could run the 5200 OS ROM w/o crashing since it uses different vectors IIRC. The thing is some Atari 800 cassette programs were converted to CARTs. All they did from the cart was add a bit of code to copy the program to low RAM i.e. $1000-$4000 like they may have been loaded from a cassette, then jump to the code. IDK, if someone was to say do something like an Infocom game, you could probably program it in C and assemble it to run at ~$600-$3FFF. All the unchangeable maps, DLs, and responses could remain in the CART and run from there. You can use old analog joysticks from IBM/Apple on an 8 bit, just need to rewire them for different resist/caps. Not a lot of stuff could be used with them though. I think Blazing Paddles and maybe Rambrant.
  9. It would be really hard w/o some extensive work under the hood. Making a simple plug in adapter to read the 5200 carts would be easy with a little bit of work but the 32k of address space just won't fit into an 8 bit's memory map. You would have to modify the 8 bit to something like copy the first 16k of ROM into RAM and let the remainder reside in CART space. Keyboard input vs joystick would probably be a little silly i.e. pressing q for up, z for down, ... not sure as I have never done key codes on a 5200. Just a by the by. OCD kicked in and I ordered parts for a 5200 expansion adapter. Just some proto board with enough fingers and a 36 pin edge card connector. I used to have a lot of left over 1489s laying around but seem to have misplaced them. *IF*<big if> I do put soldering iron to contacts I will be back begging for someone to risk their real 5200 to see if we can get it talking RS232. I'll take a look at getting my 5200 to work, little chance of that as it has suffered greatly from improper storage. It was never much of a system anyway, just a populated board I got surplus for $7.50 at Halted Specialties.
  10. I think I see a black wire under the other two running to the DB25 which makes it make sense. There were a lot of file transfer utilities between the ST and 8 bit, I even wrote one myself using the ST joystick. There was the original ST Xformer that used the ST printer port to read a 1050 and ST 800xlDJ which was the ST equivalent of SIO2PC. I also see a 7805 there so with the diodes and caps, implies they needed or thought they needed a 5V supply. => The ~200 mamp available on the SIO bus is more then enough for an interface ergo they were either being cautious or they actually needed 5V! Is that is the case, then this interface is likely to be an ST equivalent of 1050toPC for reading an 8 bit drive. I can't remember the female/male DB25 of the printer vs. serial port of the ST, but that should narrow it down a bit more. There's lots of ways to get 5V out of a printer port or serial port 'cheaper' but the 5V supply really suggests to me 1050toST because the drives don't work without it being available. Could be the designer just had the parts laying around and decided to throw them in.
  11. IDK, I can understand not being a fan of hot plugging stuff, it's just that we have progressed so far it is possible to have a system that doesn't use SIO for anything other then an RS232 device. It would be pretty simple to add the circuitry to isolate the device so it wouldn't be sending garbage out when you accessed a 1050 or ??? on SIO bus. Simple double throw switch if you could accept doing it manually or tristate buffer like a 74ls245 if you wanted to make it compatible. It would add to the complexity of course but maybe $.40? Probably easier/cheaper ways to do it then that like using the command line on half of a NOR/NAND gate or sumtin. That's what the Sider's did https://www.google.com/url?sa=i&source=images&cd=&cad=rja&uact=8&ved=2ahUKEwiOkYeShKHkAhVdHzQIHWO2DCcQjRx6BAgBEAQ&url=https%3A%2F%2Fatariage.com%2Fforums%2Ftopic%2F284097-mss-100rverter-connection-help%2F&psig=AOvVaw2M2AKeH2LyfMtLzbUJ-Lx6&ust=1566925873484199
  12. Mostly agree on Command line in that if you wanted to use 90%+ of Atari stuff like a 1050 it is essential. Looking at the schematic, the only thing needed for a simple interface to a RS232 protocol would be a chip like the 1489 or one of the ttl to USB chips like the FTDI offerings. An IDE 36 contact edge connector and either wire wrap or prototype board. IMO: It REALLY looks like a designers dream from a capability standpoint. I mean it brings the system clocks and has an interrupt line, everything is already wired with a terminating resistor, that kind of stuff. If I have it right, the substitutions of connections vs an 800 serial bus would be pin 12 SIO DATA IN pin 15 SIO DATA OUT pin 1 &/or 36 5V pin [3, 11, 28, 34] Ground https://atariage.com/5200/archives/schematics/Schematic_5200_IO_Low.html The use of 800 OS serial control. Well it could just be lifted right out of 800 OS with a text editor and cleaned up to run from cart space but as Rybags points points out, it is set to use the handshaking lines. Ditto for SIO2PC and Atari Classics in that they both rely on the Command line. Someone recently posted some code for bypassing the OS and use direct reads and writes to the POKEY chip, I can't recall who. In that mode on the lowest level I believe you poll the POKEY chip rather then write IRQ code. That is, you would just write a byte to the POKEY chip and wait for it to ACK completion of send in its register. Ditto for receive, just read the POKEY register to see if it has a byte ready.
  13. Options dilemma. Hard to tell what people would want since I think most people just opt for ~Atari Classic expanded cart. If it just copied the disk handler from the 800 with DISKINV<?$E453?> and made storage the responsibility of the CART/programmer, it should work with something like RespeQT since it doesn't use the Command line me thinks. You would be limited to a 8 meg disk!<sic> Lost of couple of computers so I don't even think I have a working development system at the moment. Just saying a slug now and can't be of much help.
  14. Do you have any idea how many 5200s are out in the wild? I tried booting my on a plate 5200 recently and it seems to have given up the ghost. But yes, could'a, should'a, would'a. I mean with a 32k of cart space, you could stick an 800/400 OS + BASIC and still have room for 14k of other stuff. The POKEY SIO is brought out on the expansion connector so another could'a, should'a, would'a. No excuse for me as it is something I could'a, should'a, would'a done but for getting into a dozen other things like sailing and restoring motorcycles.
×
×
  • Create New...