You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cycle power or press the reset button. Upload the RAMdisk image 't68kram.s68 '. This will take 30 minutes to complete. t68kram.s68 contains the files from CP/M-68K ver 1.3 distribution disks plus microEMACS, gkermit, and BASIC executables. All executables are in relocatable format and will be converted to .68K executable format.
`Tiny68kbug
12/19/17 v0.7, type "he" for help
bo
Copying CP/M 68K from Compact Flash...
no valid CP/M code, command cancelled`
Would appreciate suggestion, where to get proper binary image file.
Thank you for making py68k!
Thanks for sharing your experiences. It may be possible to reproduce Bill's instructions for creating the CP/M disk image using cpmtools, I might look into this as an alternative.
Dear John,
I have problem with finding t68k_cpm_disk.bin file under link to Retrobrew, T68kbug_r07.BIN was easier to find.
Tried to download this RAM image: https://www.retrobrewcomputers.org/lib/exe/fetch.php?media=boards:sbc:tiny68k:t68kram.zip.
Downloaded it to targets folder.
Then converted it to bin using bincopy (https://bincopy.readthedocs.io/en/latest/):
bincopy convert -i srec targets/T68KRAM.S68 -o binary targets/T68KRAM.bin
Run console:
py68k.py --console-server
./py68k.py --target tiny68k --diskfile targets/T68KRAM.bin --eeprom targets/T68kbug_r07.BIN
I got rombug prompt:
`Tiny68kbug
12/19/17 v0.7, type "he" for help
Though when typed
bo
, as is suggested on https://www.retrobrewcomputers.org/doku.php?id=boards:sbc:tiny68k:create_new_cf:`Tiny68kbug
12/19/17 v0.7, type "he" for help
Would appreciate suggestion, where to get proper binary image file.
Thank you for making py68k!
In installation dependencies this page was helpful:
http://tingo.homedns.org/emulators/py68k/fedora/
It seems, one need to enter musahi folder, and type
make
to compile it.The text was updated successfully, but these errors were encountered: