Timeline for What are my options for fast bidirectional transfer between a C64 and a 1541?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 10, 2020 at 4:05 | answer | added | cjs | timeline score: 2 | |
| Mar 10, 2020 at 4:00 | history | became hot network question | |||
| Mar 9, 2020 at 21:32 | answer | added | Tommy | timeline score: 5 | |
| Mar 9, 2020 at 21:29 | comment | added | Tim Locke | A 1581 has 8 KB of RAM. | |
| Mar 9, 2020 at 21:27 | answer | added | Tim Locke | timeline score: 2 | |
| Mar 9, 2020 at 20:41 | comment | added | Raffzahn | This is an extrem broad question - unless you narrow the requirements down a bit more - like what interface is to be used, what kind of messages and basic protocol requirements. -- In general I could think of a host clocked transfer, much like Supercat suggested, leaving the path set by Commodore. With fixed formats and sequences, using ATN and SRQ for protocol handling. | |
| Mar 9, 2020 at 20:38 | comment | added | Tommy | What's a usable amount of RAM? You're starting with only 2kb if memory serves. Otherwise, key observation: the 1541 and the C64 are very close to the same clock speed, so you should seriously consider using both the data and clock lines as data, if you can persuade yourself that the inevitable drift won't cause a fault within 40 bytes. | |
| Mar 9, 2020 at 20:37 | comment | added | Brian H | Burst mode to a burst capable device, like C1571, may be more realistic option. | |
| Mar 9, 2020 at 20:34 | comment | added | user722 | One problem is that you may run into is that the faster you transfer data, the more CPU time is spent on both ends bitbanging the data across the serial bus. At some point you'd lose any advantage of using the 1541 CPU as a coprocessor. | |
| Mar 9, 2020 at 19:56 | history | asked | Omar and Lorraine | CC BY-SA 4.0 |