Jump to content

JJB

Members
  • Posts

    126
  • Joined

  • Last visited

1 Follower

About JJB

Profile Information

  • Gender
    Male
  • Location
    Wellington, New Zealand
  • Interests
    Pretty much everything electronic & mechanical; returning to the TI99/4a after 25 years
  • Currently Playing
    with FinalGROM99
  • Playing Next
    with DSK emulation on the cheap

Recent Profile Visitors

2,927 profile views

JJB's Achievements

Chopper Commander

Chopper Commander (4/9)

294

Reputation

  1. I noticed your board is set to "Arduino UNO WiFi" in the IDE but I'm pretty sure the board you purchased is a vanilla R3 without WiFi. I reckon that if you change the board to "Arduino Uno" (see below) you should be good to go:
  2. Those warnings shouldn't prevent uploading the sketch and the amount of program and dynamic memory left is similar with what I get: Sketch uses 29248 bytes (90%) of program storage space. Maximum is 32256 bytes. Global variables use 1435 bytes (70%) of dynamic memory, leaving 613 bytes for local variables. Maximum is 2048 bytes. That seems to indicate you are using the right version of libraries. But I do see "An error occurred while uploading the sketch" which could be a comms problem. Have you tried a to upload an example sketch (Files / Examples) to see if the upload mechanism works? Also, would you be able to send me a link with info on the type of Arduino you are using?
  3. Looks great! The only slightly tricky thing with programming is using the right version of certain libraries; my Github page has some of the required ones but with every new Arduino IDE version some standard libs seem to bloat and could cause the sketch not to fit. Happy to provide a more detailed list of lib versions if you run into that trouble. Awesome you built one.
  4. Here are some pictures on how I modify the Ethernet shield; I have found this the easiest and quickest way. The final piece of heat shrink tubing on the ICSP connector is important to keep the wires from sliding out the connector over time (as they will be upside down).
  5. WiFi would be great as it saves a cable snaking over your desk. I did look at WiFi at some stage but the (standard) library was rather large and the resulting sketch didn't fit into memory. Like for FTP and NTP, there may be a smaller WiFi library available somewhere. Speaking of cables, if I really had thought a little bit longer about the design I made sure the Ethernet, power and USB connectors would be at the back of the unit 🙂 I did integrate an APEDSK99 unit into a speech synthesizer case and made some converter cables to do exactly that.
  6. That looks great although the finger attachment seems rather labor intensive Putting everything in (quality) sockets I can appreciate. The Ethernet shield seems to have those damn short connecting pins too but I guess it doesn't interfere with the underlying real estate? How did you customize the Ethernet shield? I have since found an even easier method with tinned wire and shrink tubing; it's not in the construction doc yet, will update it.
  7. The BOM (Excel file) is saved in the KICAD folder on GitHub. From the BOM: APEDSK-AU-BOM.xlsx
  8. PS the C512 version can be found cheaper on Ebay if you buy 3pcs at once, search on: 3PCS NEW IS61C512-20M ISSI 9521+ DIP-32 The seller I have used multiple times is jiali20160, so far only the genuine article. BTW if you need any parts, I do still have some including PCB's and edge connectors. The latter can usually only be bought in multiples, happy to send individual items. Now, I do live in New Zealand so shipping is not overly cheap; happy to enquire so you can compare.
  9. Great thanks, makes sense now. I did discover that wiki, very helpful.
  10. Thanks! It is certainly interesting. Would you care to elaborate on the decoding? APEDSK99 is still pretty close to a standard TI disk controller and the latter seems to work fine with a Myarc. I am probably missing something fundamental here 🙂 FYI the APEDSK99 GAL does decode A0-A3 to only respond to >4000 - >5000 access so if that is what you were referring to I should be good.
  11. To answer some of the questions: - Has there been any work on making usage of the extra 24k of ram space for larger DSR? Currently the only option is to load different DSR's from SD which is a rather cumbersome way of implementing larger DSR's; it was primarily meant to support developing and testing your own DSR's. The better way to do it would be to load a larger DSR at powerup / reset and add a CALL to switch DSR's (something like CALL SDSR([1,2,3,4]). The Arduino side would then handle copying in the right 8K of DSR in the >4000->5000 memory space. Depending on the DSR you might want to save the current config if your DSR supports writing to >4000->5000 (for example the "FD1771" registers in the current APEDSK99 DSR). - I didn't come across it yet but in regard to the CRU base which one does it use the >1100 one? And is it possible to use other CRU bases? Or even I wonder somehow to assign a different CRU base to each 8k DSR, that could be a way of using the other 24k of space. APEDSK99 is meant to be a cheap and easy way to get back into the TI hobby, i.e. no initial need to hunt down (and ship) a loaded PEB. As the only connected peripheral (besides a Speech Synthesizer) it doesn't need the CRU base selection mechanism. In other words, it is always selected ("SBO 0") and visible on every CRU base. The only CRU-related check is made in the DSR powerup routine: only if R12 = >1000 (first peripheral) it is executed otherwise it would execute for every peripheral check (thanks Fred). - It would be nice still to be able to use the PEB as well See above, concurrent use is not going to work unless some form of CRU selection is added. If you manage to connect the PEB, you would need to disable APEDSK99. There are several ways to this, with the easiest way unlatching the SD card and pressing reset. APEDSK99 will detach itself from the IO bus and flash an error. On a side note, I am running into this very same problem. I am building a stand-alone Myarc and am using APEDSK99 as the only device. It boots fine into MDOS but then the fun stops. The MDOS DSR seems to write to the >4000->5000 area frequently (I guess for housekeeping etc) and this messes up the APEDSK99 DSR (as it is in RAM and always on). I am now adding extra selection logic to only allow writes in the >5FFx memory area (the "FD1771" registers). Thinking a bit further, I am adding this selection logic on an existing small interface board between the APEDSK99 44-pins and the Myarc 60-pins connector. It might be a better idea to actually add CRU selection logic to this board; that way you can even stick APEDSK99 in a PEB 🙂
  12. FYI the 50ns diff turned out to be a red herring. @OLD CS1 I remember you mentioned that particular console was already a bit icky and you would test further; did you in the end?
  13. FYI I use JCLPCB and they charge $5 (New Zealand $ that is) per PCB. Minimum volume is 5.
  14. Great! Let me know if I can help in any way. Pretty much any Arduino Uno R3 should work, I have used 3 or 4 from different online and local vendors so far without any problems; same for the Ethernet shield.
  15. Please check https://github.com/wuntusk/technical-drive
×
×
  • Create New...