Jump to content

Search the Community

Showing results for tags 'Raspberry Pi'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Atari Systems
    • Atari 2600
    • Atari 5200
    • Atari 7800
    • Atari Lynx
    • Atari Jaguar
    • Dedicated Systems
    • Atari 8-Bit Computers
    • Atari ST/TT/Falcon Computers
  • Gaming General
    • Classic Gaming General
    • Classic Computing
    • Modern Gaming
    • Prototypes
    • Arcade and Pinball
    • Emulation
    • Hardware
    • Gaming Publications and Websites
    • International
  • Marketplace
  • Community
  • Game Programming
  • Site
  • Classic Gaming News
  • The Club of Clubs's Discussion
  • I Hate Sauron's Topics
  • 1088 XEL/XLD Owners and Builders's Topics
  • Atari BBS Gurus's Community Chat
  • Atari BBS Gurus's BBS Callers
  • Atari BBS Gurus's BBS SysOps
  • Atari BBS Gurus's Resources
  • Atari Lynx Programmer Club's CC65
  • Atari Lynx Programmer Club's ASM
  • Atari Lynx Programmer Club's Lynx Programming
  • Atari Lynx Programmer Club's Music/Sound
  • Atari Lynx Programmer Club's Graphics
  • The Official AtariAge Shitpost Club's Shitty meme repository
  • The Official AtariAge Shitpost Club's Read this before you enter too deep
  • Tesla's Vehicles
  • Tesla's Solar
  • Tesla's PowerWall
  • Tesla's General
  • Harmony/Melody's General
  • ZeroPage Homebrew's Discussion
  • Furry Club's Chat/RP
  • PSPMinis.com's General PSP Minis Discussion and Questions
  • PSPMinis.com's Reviews

Blogs

There are no results to display.

There are no results to display.

Calendars

  • AtariAge Calendar
  • The Club of Clubs's Events
  • Atari BBS Gurus's Calendar
  • ZeroPage Homebrew's Schedule

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website


Facebook


Twitter


Instagram


YouTube


eBay


GitHub


Custom Status


Location


Interests


Currently Playing


Playing Next

Found 20 results

  1. nicknickuk

    IMG 0721

    From the album: Raspberry Pi Custom Atari case designs

    My Raspberry Pi case inspired by Atari the 2600 Berzerk cartridge. Black plastic case and I used Paint Shop Pro to design labels for Berzerk which the end result has a very good resemblance to an Atari 2600 cartridge. This looks amazing in the flesh.
  2. nicknickuk

    IMG 0715

    From the album: Raspberry Pi Custom Atari case designs

    My Raspberry Pi case inspired by Atari 7800. Black metal case and I designed the centre vinyl sticker faceplate using paint Shop Pro
  3. From the album: Raspberry Pi Custom Atari case designs

    My Raspberry Pi case inspired by the upcoming Atari VCS. Made with Vinyl wrap and an Atari Vinyl logo sticker
  4. Hey guys, In my ongoing effort to play my favorite old video games with original controllers on my modern living room TV, instead of being banished to the CRT in my cold, dark basement, I've come up with the Ultimate Atari FB! Here's the software in action: Why trash a perfectly good Flashback? • Crisp full-screen HDMI output. • The ability to add any 2600 game. • Upgraded menu selection screen with woodgrain goodness! • The FB's make great Raspberry Pi cases! What you'll need: • Any Atari FB with front facing ports (FB's 3-7) • Raspberry Pi 3 • Two 2600-daptor II's sans cases • Upgraded FB 2A power supply • Two USB A-B cables, on 6" and the other 12" • Four 4-40 by 3/4" machine screws • Wires and soldering skills • Custom RetroPie software (see link below) With the custom software, the console buttons all work, and holding down Select and Start (Reset) will get you back to the game menu. See the attached manual below. Console Button Wiring (Starting closest to power button): 1. 5V Power at GPIO 2 2. Ground at GPIO 6 (or any other GPIO ground) 3. GPIO 20 4. GPIO 16 5. GPIO 26 6. GPIO 21 Suggestions: • Remove the capacitor on the console PCB and solder in a jumper wire or you won't have enough power to the Pi. • I suggest pairing a Bluetooth keyboard with the Pi or running a USB extension cable out the back. You'll need this for adding box art, editing file names, transferring roms via USB, etc. Software Manual (thanks to timdu!): Ultimate Atari FB Manual.pdf Micro-SD Card Image: • Download it here. • Contains several great homebrews that have been publicly released in rom form! Credits: Thanks to fdr4pres, Tom Hafner, pimpmaul69, timdu, and intvdave for all the help!
  5. Hi, I am trying to get file2pc.obj to work - as I understand it I can use it to transfer files to the PC-Link folder on my Raspberry Pi (or any server that supports PC-Link). I have installed sio2bsd, and can boot the ATARI.ATR that has file2pc.obj from the Rasberry Pi fine (see attached ATARI.ATR). However, when I try to use file2pc.obj on the (real) 8-bit, I get "BAD STATUS from PC. Restarting" when I try and give the path to the PC-Link directory. In the log for sio2bsd (displayed in the terminal) I get: 24 -> 'S': $31, $53, $0001 ($85) 25 -> 'R': $31, $52, $0169 ($ed) 26 -> 'R': $31, $52, $0033 ($b6) 27 -> 'S': $3a, $53, $0033 ($c0) 28 -> 'S': $3a, $53, $0033 ($c0) 29 -> 'S': $3a, $53, $0033 ($c0) 30 -> 'S': $3a, $53, $0033 ($c0) 31 -> 'S': $3a, $53, $0033 ($c0) 32 -> 'S': $3a, $53, $0033 ($c0) 33 -> 'S': $3a, $53, $0033 ($c0) 34 -> 'S': $3a, $53, $0033 ($c0) 35 -> 'S': $3a, $53, $0033 ($c0) 36 -> 'S': $3a, $53, $0033 ($c0) 37 -> 'S': $3a, $53, $0033 ($c0) 38 -> 'S': $3a, $53, $0033 ($c0) 39 -> 'S': $3a, $53, $0033 ($c0) 40 -> 'S': $3a, $53, $0033 ($c0) 41 -> 'S': $3a, $53, $0033 ($c0) 42 -> 'S': $3a, $53, $0033 ($c0) 43 -> 'S': $3a, $53, $0033 ($c0) 44 -> 'S': $3a, $53, $0033 ($c0) 45 -> 'S': $3a, $53, $0033 ($c0) 46 -> 'S': $3a, $53, $0033 ($c0) 47 -> 'S': $3a, $53, $0033 ($c0) 48 -> 'S': $3a, $53, $0033 ($c0) 49 -> 'S': $3a, $53, $0033 ($c0) 50 -> 'S': $3a, $53, $0033 ($c0) 51 -> 'S': $3a, $53, $0033 ($c0) 52 -> 'S': $3a, $53, $0033 ($c0) 53 -> 'S': $3a, $53, $0033 ($c0) 54 -> 'S': $3a, $53, $0033 ($c0) I'm starting sio2bsd on the Raspberry Pi with: $ sio2bsd ATARI.ATR /tmp/ D1: 720 sectors, 92160 bytes total, mounted on ATARI.ATR PERCOM: trk 40, step 3, spt 18, heads 1, bps 128, flags 00 (SMALL-FM-5.25INCH) PCL1: mounted on /tmp PCLink directory filter allows lower case names Serial port: /dev/ttyAMA0 POKEY quartz 1781618.500000 Hz and HS Index 0 constant 7.186100 is assumed Default speed: HSINDEX=40 (19200 bits/sec.) Default turbo: HSINDEX=0 (123963 bits/sec.) User selected: HSINDEX=0 (123963 bits/sec.) And giving a variety of PC pathnames when prompted by the file2pc.obj program, but am getting nowhere. I built sio2bsd using "make -f Makefile.linux", and set the serial device as /dev/ttyAMA0 in Makefile.linux. Anyone have any ideas on how to get this to work? I would like to hack the file2pc sources so I can write files to the PC-Link folder, but I need to be able to test this is possible, e.g. that file2pc.obj works OK in the first place. Also, I don't have SpartaDos X, so can't test sio2bsd with the PC-Link.sys driver for that DOS. If anyone knows how to get file2pc.obj to work with another server than sio2bsd, that would also be a good to know. Thanks! ATARI.ATR SIO2BSD-master.zip
  6. This is an updated video of the image capture project I started 3 years ago, with much enhanced image processing in half-tone. Was supposed to be demoed at the Chicago Faire but it did not happen... https://youtu.be/-ZkSfssnfv8 Details in my blog: http://atariage.com/forums/blog/659/entry-15260-image-capture-on-the-ti-994a-computer/
  7. MurdockScott

    PI994a 2208

    From the album: Pi99/4a Project

    Back top view.

    © Murdock Scott

  8. MurdockScott

    PI994a 2205

    From the album: Pi99/4a Project

    As did this... It is a little tricky getting an ethernet cable plugged in but I think I can live with that.

    © Murdock Scott

  9. MurdockScott

    PI994a 2199

    From the album: Pi99/4a Project

    Had to make a minor mod to the case, but it fits well and won't prevent me from using it as a real TI in the future.

    © Murdock Scott

  10. I'm not sure whether is possible or practical but thought I would ask to see if any of the following is possible: How is the Harmony emulation (is that the right term?) dealt with on an Arm processor does it run natively and if not would this be possible? Would would be the feasibility in adapting Stella + Batari Basic into an retro type interpreter? Is it worth using Batari Basic as the base for a bare metal coding platform for the Pi? Any thoughts input on this? Barnie
  11. Intel has announced plans to release a quad-core Atom-based computer-on-a-stick later this year. For less than a hundred bucks, it will come pre-loaded with Linux. For about sixty bucks more it will have more RAM, more SSD memory, and will be pre-loaded with Windows 8.1. This thread seemed to reach the conclusion that the most pain-free approach to building an emulation PC should use some version of Windows. The new device, dubbed the "Compute Stick" seems to imply a more "ready to go" device than what we've seen with Beagle bone, Raspberry Pi, and the host of various Android plug-and-play sticks. It will include Bluetooth and WiFi, connect directly to your high def display via HDMI, and is powered (or charged?) through a USB port. I have been a big supporter of the idea of repurposing off-lease desktop computers as a way of getting inexpensive Windows computing power and supporting sustainability for aging technology, but if this product lives up to its promises, it could be a game changer...
  12. MurdockScott

    PI994a 2210

    From the album: Pi99/4a Project

    Installed and working!

    © Murdock Scott

  13. MurdockScott

    PI994a 2203

    From the album: Pi99/4a Project

    This worked out well.

    © Murdock Scott

  14. MurdockScott

    PI994a 2193

    From the album: Pi99/4a Project

    Need to get proper ties to secure the cables in place. The HDMI is a bit stiff, should have spent extra on a thinner one...

    © Murdock Scott

  15. MurdockScott

    PI994a 2192

    From the album: Pi99/4a Project

    It all fit together amazingly well, no real electronics skill involved... more of an art project. : )

    © Murdock Scott

  16. Twitter user @Tom7 uses a Raspberry Pi in an NES cartridge to display custom content and to emulate a SNES game on the NES https://blog.adafruit.com/2018/05/29/reverse-emulation-on-a-nintendo-nes-nintendoamerica-tom7-raspberry_pi-nes/
  17. While archiving my collection it hit me: That Banana Pi I use at the bi monthly Retro meeting here in the Netherlands can also make use of the trick that The Montezuma used to connect a Raspberry Pi as a disk drive for the Atari. Up until now I dragged along SIO2PC device(s). With the Raspberry Pi craze, several parties also wanted a piece of the pie. LeMaker came up with the Banana Pi, also a SoC, but with a little beefier specs, like gigabit ethernet, more RAM and a power switch. Another thing the Banana Pi has more of than the Raspberry Pi is four(!) UART interfaces. So, plenty of ways to connect to the SIO port. I picked the UART1, located on J12, as on the same row there is 3.3V and GND available, making it very easy to use a 4 pin connector I had lying around (an old CD Rom sound cable). The PinOut of the Banana Pi, as you can see J12 consist of 2 rows with 4 GPIO pins, the top four (2,4,6, being 3.3V, RXD, TXD, GND: Details of all pins: I haven't created a nice graphic representation of the connections, but the text version looks like this: Connect Banana Pi J12 pins 2,4,6,8 to a level converter at its LV side. On the HV side of the level converter, connect a 1N581[789] Diode between the level converter and pin 3 of the SIO port. The connections should match below matrix: *** Atari TO Level Shifter SIO 3 (Data IN) - DIODE (1N581?) - HV1 * Via diode (for example 1N581[789]) direction from Atari to the level shifter * SIO 5 (Data OUT) - HV2 SIO 10 (+5V) - HV SIO 4 (GND) - GND *** Level Shifter TO Banana Pi LV1 - J12 Pin 6 (TxD) LV2 - J12 Pin 4 (RxD) LV - J12 Pin 2 (+3,3V) GND - J12 Pin 8 (GND) As you may notice, I did not connect SIO 7 (COMMAND), it should not be needed when you use sio2bsd or Respeqt. You can use the software attached to these posts on the Banana Pi as well. Depending on the linux distribution you use, it could be that your UART is connected to something other than ttyS3, to be sure, put an ATR on the SD card and use the following script to check 1. whether your cable works, 2. what terminal the J12 UART is connected to: ### Note: this runs as user root. If you are not running as root user, run 'sudo su -' first. for DEV in {0..3}; do echo -e "\nTesting connection on ttyS${DEV}\n\n" sio2bsd -s /dev/ttyS${DEV} -f /root/atari/disks/demo/numen.atr done The output should be something like: Testing connection on ttyS0 D1: 769 sectors, 196480 bytes total, mounted on /root/atari/disks/demo/numen.atr PERCOM: trk 1, step 3, spt 769, heads 1, bps 256, flags 04 (SMALL-MFM-5.25INCH) PCLink directory filter allows lower case names Serial port: /dev/ttyS0 POKEY quartz 1781618.500000 Hz and HS Index 0 constant 7.186100 is assumed Default speed: HSINDEX=40 (19200 bits/sec.) Default turbo: HSINDEX=0 (123963 bits/sec.) User selected: HSINDEX=0 (123963 bits/sec.) Next, power on the Atari connected to the Banana Pi. If your cable works and the script arrived at the correct terminal, you should see something like: 0 -> 'S': $31, $53, $0000 ($84) ... 3 -> 'R': $31, $52, $0003 ($86) If not, on the Banana Pi terminal, press CTRL+C and reset the atari from the Self Test screen (at the READY prompt, type 'BYE' and at the green screen press RESET). If your machine doesn't boot for the selected floppy, check the connections between the Pi and the Atari, verify if the floppy file on the Banana Pi exists and can be accessed (sio2bsd will display an error if it can't open the .atr file). If you want to be really fancy, create a second cable and connect it to another UART and use the banana pi as a terminal for bbs access at the same time. Hope that you too can put that Banana Pi to good use now.
  18. It's been a while since posting, but I found some time to (re-)start the daunting task of archiving my fl[oi]ppy collection. As I am in possession of both a Raspberry Pi (raspi) and SIO2PC hardware, I thought about putting both to good use. Archiving my floppy collection is something I think of as good use. I wrote about my setup here before, so I will leave the details of installing the raspi and sio2bsd toolkit out of this post, if you need help with either, check my other posts, or send a PM. For the Atari side of things, I start with booting the recommended 'Copymate XE 3.7'. I have two 1050's connected to my Atari (D1 and D2), so after booting the copymate application from the raspi, I kill the sio2bsd application and run the diskarchive.sh script I wrote for the archiving job. The script is a quick hack to speed up the job a bit of manually starting sio2bsd all the time. In the script, there are three variables that need to be adapted to your own setup: BLANCO=( "/var/www/html/disks/Blank_MD130k.atr" "/var/www/html/disks/Blank_SD90k.atr" "/var/www/html/disks/Blank_DD180k.atr" ) DISKDIR="/var/www/html/disks/_personal/" SIOPARM="-s /dev/ttyUSB0 - - - ${DISKDIR}" The BLANCO array contains a list of blank disks that I created that are copied to a new location with the name you enter for your disk. Note that the order of the image locations matter, as they are used later in the script if you need to switch to another density for the destination disk. I default to the 130k image when using the script. String DISKDIR tells where to store the archive of images you're about to create. In this direcory, for each image you will create, there will be three files: .atr (the actual image), .nfo (the one line descriptive text you entered, more about that later) and .log (the output of the sio2bsd tool during the creation of the image). The other string SIOPARM has the parameters for the sio2bsd program used. Remember, if you use a level converter to the GPIO ports of your raspi, you need to change ttyUSB0 to ttyAMA0. In the above example settings, the image drive will be D4. Copymate XE When the application starts, it display usage information, but after you press a key on that screen, the program guides itself on the main screen. Tip: If you haven't started the script and/or turned on your drives, do that first (and make sure the script is actualy running sio2bsd (enter disk name and description)) then press the RESET button on the Atari so the program will redetect(?) the active drives. diskarchive.sh I think the script is self explanatory to me that is, but then again, I wrote it. It asks for some info before starting the sio2bsd program, but remember, it will kill all running instances of sio2bsd! So when you run the script, it prompts for the 'Disk Name', the filename that will be stored (threefold) in the archive directory. Stick to letters and numbers, no spaces and you'll be fine. Up next is the 'One line description for the disk', where you can enter some text describing the content of the disk. Don't make it too complex but the input is less restrictive than the Disk Name. Now the script will spin up sio2bsd on D4 so copymate can write to it. Make sure the Source and Destination drives on the Atari are correct and press START to start archiving your first disk. If for some reason, your source floppy is not in the enhanced density format but is single density, press the s key and the script will restart sio2bsd with a blank SD image, if that is what the second item in the BLANCO array is. Once the copy is completed, press any key (but the 'e', 's' and 'd' keys) to continue to the next disk. If you're done archiving for the day, enter 'q' as disk name, to quit the script. You'll find the script attached to this post. Copy it to a location you prefer (your home directory on the raspi ?) and run it as root (sudo ~/diskarchive.sh). NOTE: I haven't bothered to remove the message './diskarchive.sh: line 3: 2201 Killed sio2bsd ${SIOPARM}${DISK}.atr 2>&1 > ${DISKDIR}${DISK}.log' you'll see when switching disks. If it really is a concern, let me know. diskarchive.zip
  19. Maybe I'm having a false memory or something, but I could have sworn someone posted a thread sometime last year, either here or at the yahoo group, that contained a distro for the Raspberry Pi that used MESS to run all of the PLATO software on it. Now I can't find it. So am I remembering incorrectly, or did someone actually put something like this together? I recently bought a Pi and am playing around with it every few days. Just amazing how technology has advanced. Thanks to anyone who can verify this and point me in the right direction! (Or set me straight and tell me I was dreaming...)
  20. Apart from trying to get the Raspberry to fit a 2600 jr without hacking away to much of it, I have been looking at wiring up some Atari joystick ports with the GPIO method of which there are a few documented options out there. At the moment I using a ps2 keyboard mouse adapter in one usb port and the other port for a usb to midi interface. I don't want to overload with to many options so was considering the options of a GPIO board with more features, I've come across some examples of expanding the capabilities of the breakout board using a cpld +i2c combination. Examples I've thought of are an FPGA, some original 8 bit chips such as TIA+6502/6507. Ideally Jeri Ellsworth would get her stockpile of chips on the market! https://twitter.com/...325244607832066 Either that or Curt bring out a flashback 2 breakout board with the 2600 on a chip. Anyway possible problems with this? Would the GPIO be fast enough to handle the data transfer? Finally Why? 1. Just Because 2. Raspberry Pi is gaining a lot of interest 2. An 8-bit type system interface to the Pi might make for a nice intro system educationally Any thoughts?
×
×
  • Create New...