Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

258 Excellent

About brain

  • Rank

Profile Information

  • Gender

Recent Profile Visitors

3,739 profile views
  1. The Arduino IDE sketch should work as well, but most of the Arduino UNO SD shields have a DS1307 RTC, not a DS3231, which the Arduino sketch expects. So, to address that, comment out the "#define INCLUDE_CLOCK line in config.h and sompile the sketch. The Discord channel does have the native compile, which supports the DS1307 as well as the DS3231 (and PCF8583), but it requires avrdude to load into the Arduino. Catalog does work on the native compile (I'm still working on merging it into the Arduino sketch), so keep that in mind. Jim
  2. Sorry, I thought that was a safe commit. Pull from Reid's master, which I know compiles from Arduino and runs (as that's his dev environment), and let me finish the merge of the code into my repo. Also, note that there's a been a change in wiring, which may not have been noted here. BAV is now on D7, not D2, and LED is on D2, not D7. This allows sleep functionality for the drive. https://github.com/sreid1960/HexTI Jim
  3. Hehe, one would start pulling files after I started merging in the latest code from the master branch. Try this commit: https://github.com/go4retro/HEXTIr/tree/2c82960fc5620fe769a3e3b767dd45c204074b0f I'm not as familiar with the Arduino port, but I didn't have to install any code. I did use 1.8.12 of the IDE, so perhaps it was all in there. Jim
  4. main branch now has a "catalog" functionality, where one can snag the directory by doing old "100.$", courtesy of Manfred. Other functions are still in the sreid_mods branch, which I am planning to merge tomorrow. Jim
  5. A few comments: I would strenuously disagree that the lack of dedicated disk controller was a disadvantage. The lack of dedicated controller meant all disk access had to be "abstracted", since you could not access the direct hardware. As such, the Commodore (like other machines that had such abstraction) has had the easiest transition to newer storage technologies, like the sd2iec. Compare to the Color Computer and other units with dedicated controllers. The sd2iec-like devices have to focus lots of attention on emulating the actual disk controller, presenting disk images of fixed sizes and format, as opposed to the native FAT32 functionality of the sd2iec. Along with that, it's wasn't the lack of disk controller that prevented the inclusion of disk commands. Commodore had placed nice disk commands in BASIC 4.0 (CATALOG, DLOAD, etc.). They could have put the same BASIC in the VIC and the 64, but the disk drive was not considered a must have peripheral for the VIC-20, since it was primarily designed as a cartridge game machine, and so BASIC 2.0 was smaller and cheaper to implement and thus was included. The 64 was essentially a VIC-40 in early stages of development, so the same thought was applied. You espoused the value of the product, but didn't note how folks can legally obtain it. I'm biased, of course, but I think that's a good comment in general.
  6. A few recent updates to the codebase: serial and printer now should work on both Arduino IDE build and native Makefile build All three of us have collectively implemented some catalog functionality. Manfred added an option to "old 100.$" a directory directly, while both Manfred and Stephen have a "open/input#" directory format implemented. I should have them all merged by end of day tomorrow or Monday. soft configuration capability being implemented RTC callable from cc40 (in Arduino IDE build) low power mode enabled when system not active (s_reid) Not sure if anyone is interested, but I set up a discord server for us to use in development: https://discord.gg/vvPCaAQ Jim
  7. Well, I'll put the pics on github as well. They don't format as well for forums.
  8. 1) Yep. That's why you need to also get an Arduino UNO 2) I'm not sure the best way to replicate the cable, but I bought 2 2x4 IDC connectors (think IDE connections, but only 8 pins), had some flat ribbon cable to crimp them to, and I bought this: https://www.ebay.com/itm/10PCS-2X10-Pin-2-54-mm-Stackable-11mm-Long-Legs-Female-Header-For-Arduino-Shield/301724613213?hash=item4640303a5d:g:rhMAAOSwmrlUzYCZ and cut off the excess pins. I put that in the end of the IDC connector, and then plugged the entire thing into the cc40. No soldering involved, just a bit of construction. Alternatively, buy a cc40 modem or some other peripheral, which come with a cable.
  9. As noted, Stephen Reid has modified the cc40 project to build from the Arduino editor, which makes it easier to build and upload. So, here's what folks need to create their own unit: An Arduino Uno (Yes, a Nano or other that is Uno compatible will work, but start with an Uno): eBay option: https://www.ebay.com/itm/Arduino-Uno-R3-USB-Acrylic-Box-Enclosure-Transparent-Case-for-Arduino-Uno-R3/132940030524?hash=item1ef3d7e23c:m:m4lEBwtSZi0JjnWjh4QHRiA Official Option: https://store.arduino.cc/usa/arduino-uno-rev3 A SD card module: https://www.ebay.com/itm/For-Arduino-UNO-SD-Card-Logging-Recorder-Data-Logger-Module-Shield-New-DS1307/164212784718?hash=item263bd83e4e:g:jnoAAOSwby5exgRH The project itself: https://github.com/go4retro/HEXTIr/tree/sreid_mods The Arduino IDE (I know 1.8.12 works, so I'd recommend it: https://www.arduino.cc/en/main/software Download the files from github into a dir, and load up the src.ino file in the IDE. Ctrl U will build and upload the file to the UNO (You'll have to configure the IDE for UNO and for the right COM port). A FAT32 formatted SD card. A bit of wire and a 2x4 straight or right angle set of header pins. Now, before you can use the unit, you need to wire up a few things. Solder the 2x4 header as shown on the board. Place it along the edge if possible, for easier hookup. Solder WP to 9 Solder CD to 8 Solder L1 to 7 Solder the wires underneath the board as shown in the picture Done. Power up your Arduino and load/save files from device 100.
  10. I don't think the HW was ever a concern, but it's the SW that was less robust in the past. HexBus is a pretty simple protocol, electrically.
  11. OK a few updates: Acadiel shipped me his unit and mine back. Mine was working, but it's a bit dodgy on the seating into the Arduino pins, so that was it's issue His had a miswire. Both fixed, and working. Acadiel introduced me to Stephen Reid, who worked on the Hex Bus line back in the day. He took the Arduino source and updated quite a few things. The code now handles drive access, serial access, and parallel port support. Code work is ongoing, and you can check progress at the github repo in the sreid_mods branch. As well, he added a true Arduino build. The files will compile both as native and Arduino. Manfred Korn has also been adding some features (verify, delete, timing fixes) Thanks to both folks for the coding help. It's much easier to get motivated to work on the code when others are working on it. Jim
  12. Isn't there a HexBus Adapter for the 4/A That could be copied to do this?
  13. Someone made a "buffer" board. the 3 '244s buffer the 16 address lines and the control lines (probably R/W, E, Q, CTS, SCS, RESET, but not CART or NMI) and the 245 buffers the 8 data lines. You can then probe all the lines at the cart without risking damage to the CoCo itself. Nice option for experimentors.
  14. PM me an address and I'll send my entire unit. You can mix and match and see what is going on. Jim
  15. Hmm, that is odd. Just %ffs? Any chance I could see the output?
  • Create New...