Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by mozzwald

  1. Just a few more notes about the setup... You can flash the nodemcu with the usb port as normal. When Zimodem starts up, it switches the TX & RX lines from the default GPIO 1 & 3 to GPIO 15 & 13. This prevents the bootloader messages from being spewed out to the atari at powerup. This also means, you will not see anything on a serial terminal on the computer when connected with the usb port (also the command & motor lines would need to be pulled low for transmission to occur). The 1k resistor on GPIO 15 is required to prevent the nodemcu bootloader from trying to boot from SD card at powerup. The pull down on Atari side Motor Control was needed as the level shifter wasn't pulled down enough to register a low reading. Can anyone recommend a bbs that has files available for download with Xmodem? I want to see if it will work with bobterm.
  2. Definitely not using i2c on the nodemcu. Not really sure what was causing the problem. I got garbage on both the atari and pc when testing with a usb to uart adapter. Also tried 2 different boards to make sure it wasn't a bad one.
  3. I tried a similar level shifter and it didn't work (TXS0108) so I got the fet based one instead.
  4. I've been fiddling around with my nodemcu (esp8266) board, Zimodem firmware and the atari and have been successful with using the modem while allowing the atari to still use the sio bus with minimal parts. I have a simple fet based level shifter (wiring diagram below, amazon part) that adds the motor control and command lines to nodemcu inputs. When either line is asserted, the Zimodem firmware allows other devices to communicate on the bus and ignores the transmission. The modified firmware adds a new Flow Control type (FCT_AMTRCTL) which must be enabled for it to work. If you wish to flash the firmware to a previously used zimodem/esp board you should format the SPIFFS before flashing so that the new flow control will be selected by default, otherwise you will have issues with it not communicating as it will be set for some other flow control scheme (this issue bit me a couple times during testing). The modified Zimodem (v3.5) firmware is in my github (atari branch) at https://github.com/mozzwald/Zimodem/tree/atari
  5. http://www.maxkeyboard.com/ansi-layout-custom-color-cherry-mx-keycap-set.html I *think* it can be done with the ANSI 87 Key Layout (6.50x Spacebar and Top Printed Keys) but I haven't completely verified it yet. Depending on available extra keys, might need to use the 104 layout. Yes, I had that idea also and should be possible to 3d print something. Can add some screw holes to the keyboard pcb for attachment of the bezel
  6. I've been looking into making a new keyboard for the 400 and picked up some sample switches and keys for experimentation. Regular cherry keys are quite tall but the low profile kailh brand keys are a bit shorter. To use the Kailh switches with Cherry keycaps you need an adapter which I 3D printed. Cherry keycaps are 18mm square and are meant to be on 19.05mm centers which does not allow the original 400 layout to be used. I came up with this layout. Any recommendations are welcome. The keycap samples I got are from MaxKeyboard. They seem a bit thin but I think they would be alright to use. It looks like you can get a complete set of custom printed keycaps for less than $50. This would allow for custom legends on the keycaps. I had one key printed as a sample and it looks good. The brown, orange and yellow keys don't match the original 400 colors but I think would look alright. I also made this 3D printed chicklet style key that fits the Kaihl switches. It's only 16mm square and I think would be possible to get the original A400 layout. Problem is making the legends on the keys. I had the idea to make an indent on the top of the keycap and have custom cut stickers with the legend to put in them. Then perhaps clear coat it for protection. This path seems like the most work and I'm not really sure how the sticker idea would hold up over time. But, this is probably the only way to keep the original layout (other than having expensive custom injection molded ones made).
  7. These low profile Cherry MX keys might be an option for a new replacement keyboard: https://www.cherrymx.de/en/mx-low-profile/mx-low-profile-red.html Not sure if keycaps are available for them specifically. Edit: Just found these (different brand) keys and keycaps: https://novelkeys.xyz/products/kailh-low-profile-switches https://novelkeys.xyz/collections/keycaps/products/kailh-low-profile-keycaps-with-legends
  8. Could you connect the motor line to the esp and modify the modem firmware (on esp) to buffer data when the Atari SIO is busy (motor line asserted)?
  9. Join us at Peoria Pizza Works in Peoria Heights for our 3rd celebration of pizza, beer and retro video games! We will have a variety of classic video game systems and computers set up and ready to play including Atari 2600, Atari 800XL & 400, Commodore 128, NES, SNES, Intellivision, Colecovision, TI-99/4A, Famicom, Sega Genesis and more! Saturday, March 16 12 PM - 8 PM ADMISSION IS FREE! Peoria Pizza Works 3921 N Prospect Peoria Heights, IL 61616
  10. Awesome, I'm glad it's useful for someone else too! --- I haven't had much time to experiment with the ESP and A400 until recently. Today, I was able to get SIO2Arduino running on the ESP-01 and load an ATR image file from the ESP internal flash using SPIFFS. Writing to disk doesn't work, it's read only, but I tried several different disk images which loaded ok. The timing may be off a bit as it seems to pause a couple times during the disk load, but eventually does finish. My plan for this is to use SIO2Arduino in conjunction with the modem firmware so I can plug this in and autorun bobterm or ice-t or whatever and telnet over wifi. Could probably be used to load disk images over wifi and/or save them to an sd card. Some sort of SDrive over wifi to download ATR's from a server would be cool. I need to get an esp12 that has more pins for sd card. Attached is the modified SIO2Arduino code that can be flashed with the Arduino IDE and esp8266 core. Warning, I'm not a programmer, this is a hack job and unfinished, but it worked for me. My esp01 flash size is 512K with 128K SPIFFS which is just enough room for a disk image. This instructable shows how to upload files into SPIFFS from the Arduino IDE. GPIO2 on the esp01 is used for the COMMAND pin. I'll update if/when I get any further SIO2ESP_Testing_20170708.zip
  11. We do this once a year. There was some chatter about getting together at River City Labs makerspace in Peoria, but nothing solid.
  12. I'm guessing the handshaking would hafta be done through a joystick port? The code was chosen because it has many features I was looking for in a modem. I searched for commodore modems since I couldn't find any Atari ones and this popped up. I tested ok on a PC so I figured it would work with with the RS232.COM handler (is it called bobverter or Rverter?) Google Translation Here but it's still a difficult read I did a little more testing with bobterm and occationally the system would "freeze" and keyboard input would stop working (pokey overloaded?) but after resetting the esp modem it would start working again. I will do some more testing at a slower baud rate when time permits.
  13. I recently started working on getting my Atari 400 connected to a bbs over telnet/wifi with an esp8266 and wanted to share. I didn't find much about using an esp8266 as a modem with the Atari 8-bits. I don't have much atari hardware and no SIO cable so, I first made a SIO23v3 breakout. More info on the board at the OSHPark Project page. The idea came from the atari8warez Poor Man's SIO cable and is an edge connector that fits between the two SIO port pin rows. The Data In, Data Out and Command pins are level shifted with mosfets (based off the SparkFun Bi-Directional Level Shifter). This board could also be used for connecting to a Raspberry Pi or other lower voltage device. I'm planning to build another for use with my Zipit Z2 Handheld and sio2bsd. I have an ESP-01 board that I'm using with this modem emulator. The code is built and uploaded to the esp8266 with the Arduino IDE. The esp8266 is powered by the Atari 5V through a regulator. The command pin is not used at the moment. The ESP-01 is very minimal with few pins but other esp8266 versions have more pins available (can add sd card socket). The modem software uses AT commands for connecting to access points, speed dial, baud rate, saving settings, etc. I tested both bobterm and icet with the RS232.COM handler and was able to connect to a bbs. The modem also allows incoming connections over telnet which worked from my linux pc. This is the extent of my testing so far and only at 9600 baud. A couple of other ideas I had (unsure of the feasibility): add SIO2Arduino to load the term software and handler add SIO2Arduino and sd card; use wifi/webserver on esp8266 to load floppies (plus modem emu?) 850 emulation? Anyhow, as a plain old telnet modem it seems to work well
  14. I'm new to Qt myself, hence the problems I'm having Qt does have linux framebuffer support and I have been able to get RespeQt running on my Zipit handheld. I tweaked the main screen of the ui to run in fullscreen mode and reduced the size of the icons/widgets. Still a lot of work to be done to make it completely usable, and it's a bit slow with only 32MB RAM. Need to actually test it on the Atari next. My patches are at https://github.com/openwrt-zipit/openwrt-zipit-packages/tree/master/respeqt
  15. I am able to get the ui to display on screen by setting the qt environment variables for linuxfb. Unfortunately my LCD is only 320x240 so I'll be attempting to redo the ui xml to fit the screen.
  16. I suspect it's an issue with the cross compiling environment. Maybe it's pulling in the host libraries since I don't have xcb/xlib support in the openwrt build system. Do you have a list of the required qt5 plugins/modules (ie, network, xml, printsupport)? I could not find it in the github readme. Thanks
  17. I have built RespeQT using the openwrt build system (musl libc, qt5) for an armv5 computer that does not run X. The build completes and the binary does run on the target platform, but it complains about missing libxcb plugin. From what I gather, libxcb is a X11 related library and in my case would not be needed (unless, of course, it is required by respeqt to run). My question is, can respeqt run on linux framebuffer only or is X11 required? [email protected]:~/a8b# respeqt This application failed to start because it could not find or load the Qt platform plugin "xcb" in "". Available platform plugins are: linuxfb, minimal. Reinstalling the application may fix this problem. Aborted
  18. It was a lot of fun! By chance, a boy scout troop came for pizza after an outing and ended up playing a lot of games Great time showing the kids old hardware! Would be great to have more machines next time. I talked with one of the troop leaders who is also a member of River City Labs (Peoria makerspace) and he wanted to try getting something together sooner than next year, probably at the makerspace.
  • Create New...