Re: Yet another MK14 tape interface (ESP32).
Just a point of order, the scope trace you included with #159 actually looks as though the clock is falling in mid-bit rather than rising in mid-bit, so maybe you could take another look at that and let me know?
(Normally if you are 'reading' synchronous serial data you do it in mid-bit rather than near the edge of the bit, so you do the 'read' on whichever edge of the clock - falling or rising - coincides with the centre of the bit).
So, some files which do not contain an execution address at FFFE-FFFF...
1) kdtest.hex, this is a test routine which, whenever a single key is held down on the MK14 keyboard, displays the row and column at the intersection of which the keypress was detected, and a symbolic representation of the key which should be at that row / column intersection. Load address is 0F12, but you have to manually run it from 0F20 after loading.
2) 2 x 512-byte image files which are intended to load (one at a time) directly into screen RAM at 0200h, assuming this RAM area is present and there is a VDU connected to display it (So, RealView set to display 0200-03FF for example). These are data-only and not intended to be executed.
|