Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

62 Excellent

About mr_gw454

  • Rank
    Chopper Commander

Recent Profile Visitors

2,290 profile views
  1. Thanks for that update -- it's been an interesting journey watching you develop this!
  2. I really want to join and have tried applying a couple of times. I have not received any email confirmation yet (checking my SPAM folder, etc.). @skr - Perhaps there's a new process for applying/registering?
  3. MAME has a incredibly powerful scripting language built in (LUA) that can allow for various interactions with the running machine driver. I recently started using it and find it very capable (perhaps a bit overkill for what you need it for). More information about LUA in MAME can be found here: https://docs.mamedev.org/techspecs/luaengine.html Command syntax can be found in the built-in help: https://github.com/mamedev/mame/blob/master/src/frontend/mame/luaengine.cpp Here's a video of an emulated Color Computer (in MAME) auto-playing a game called Timber Man: ... and the LUA code for it: https://gist.github.com/tlindner/0199ee5ee64ab6fb1e3340856bfdece9 Here's sample LUA code that presses keys for a Coco in a MOD Tracker program by Sockmaster: rint("registering callback"); emu.register_start(function() coroutine.resume(co) end) co = coroutine.create(function () print("waiting to LOAD program") emu.wait(3); print("sending RUN\"MOD13.BAS\"\n") emu.keypost("RUN\"MOD13.BAS\"\n") print("waiting to select DRIVE 1") emu.wait(15); print("selecting DRIVE 1") emu.keypost("1"); print("waiting to select MOD file A") emu.wait(10); print("selecting MOD file A") emu.keypost("A"); resetcounter = 1 end) if resetcounter == nil then print(coroutine.resume(co)) else print("Clear already done") end
  4. The master branch issue is something I experienced (and thank you to you and Greg for getting me back up and running yesterday). Fortunately, I make backup SD images frequently so it's easy to fall back to just before an attempted upgrade. No idea on how my branch was set for 'master' rather than 'release' as I have not used any manual git commands. Either way, it looks like you are addressing it in future upgrades. A move to python3 is good and it makes sense. Backing up our TIPI shares, etc., should not be an issue. I actually installed tms9900-gcc and many other TI based development tools (which is why I occasionally ask you about things related to compiling fcmd, etc.). I'll need to start over with those types of installations with a move to a current Raspbian version. It goes without saying (but will anyway) how much I appreciate all your efforts with this project. Thank you.
  5. It just keeps getting better and better. Looking forward to using this with 80 column support one day. Thanks, jedimatt42!
  6. I appreciate the info. It sounds like there are some easy options for resolving the issue. Thanks!
  7. Hi ralphb, I see that python3 is now required for your tools. For many Linux users, python version 2 is the system default and is usually required to stay that way because of underlying system requirements (at least on my Linux Mint 19.3 workstation). In order to use your tools, it looks like I need to specifically call them using 'python3 <full path to script> otherwise it will default to using python2 and fail. For example: [email protected]:~/source/xdt99$ ./xas99.py File "./xas99.py", line 839 raise AsmError(f'Invalid symbol name {name}') ^ SyntaxError: invalid syntax [email protected]:~/source/xdt99$ python3 /usr/local/bin/xas99.py usage: xas99.py [-h] [-b | -i | -c | -t [<format>] | --embed-xb] [-l <file> [<file> ...] | -ll <file> [<file> ...]] [-5] [-18] [-s] [-n <name>] [-R] [-C] [-L <file>] [-S] [-E <file>] [-q] [-a <addr>] [-I <paths>] [-D <sym=val> [<sym=val> ...]] [-o <file>] [<source> [<source> ...]] xas99.py: error: One of <source> or -l/-ll is required. I guess I could also edit each of your scripts to add #!/usr/bin/python3, but is there a better/preferred way to force your scripts to use python3? Thank you for any help you can provide!
  8. As always, thanks for your continued support of the TIPI.
  9. Many thank you's to Mizapf for taking the time to answer numerous MAME related questions and helping me get up and running. You've done a terrific job enhancing and supporting TI emulation in MAME and just wanted to let you know how much it's appreciated. It's nice to have great emulation options, including Tursi's excellent Classic99. Thank you!
  10. Compiling fine again on Linux Mint 19.3 64 bit. Thank you for resolving that issue!
  11. If it helps: "Using Qt version 5.9.5 in /usr/lib/x86_64-linux-gnu"
  12. I just got the same error during my compile. I was able to build the previous release(s) without issue (using the ebiguy repo). I am using Linux Mint 19.3 64bit (based on Ubuntu 18.04).
  13. I think I forgot this before compiling: export MAKEINFO=missing
  14. Hello everyone, Trying to compile on a Raspberry Pi 4, latest version of Raspbian. Getting an error for binutils: make[1]: Entering directory '/home/pi/source/gcc-ti99/build/binutils-2.19.1' make[2]: Entering directory '/home/pi/source/gcc-ti99/build/binutils-2.19.1/libiberty' make[3]: Entering directory '/home/pi/source/gcc-ti99/build/binutils-2.19.1/libiberty/testsuite' make[3]: Nothing to be done for 'all'. make[3]: Leaving directory '/home/pi/source/gcc-ti99/build/binutils-2.19.1/libiberty/testsuite' make[2]: Leaving directory '/home/pi/source/gcc-ti99/build/binutils-2.19.1/libiberty' make[2]: Entering directory '/home/pi/source/gcc-ti99/build/binutils-2.19.1/intl' make[2]: Nothing to be done for 'all'. make[2]: Leaving directory '/home/pi/source/gcc-ti99/build/binutils-2.19.1/intl' make[2]: Entering directory '/home/pi/source/gcc-ti99/build/binutils-2.19.1/bfd' Making info in doc make[3]: Entering directory '/home/pi/source/gcc-ti99/build/binutils-2.19.1/bfd/doc' make chew make[4]: Entering directory '/home/pi/source/gcc-ti99/build/binutils-2.19.1/bfd/doc' make[4]: 'chew' is up to date. make[4]: Leaving directory '/home/pi/source/gcc-ti99/build/binutils-2.19.1/bfd/doc' ./chew -f ../.././bfd/doc/doc.str <../.././bfd/doc/../targets.c >targets.tmp /bin/bash ../.././bfd/doc/../../move-if-change targets.tmp targets.texi restore=: && backupdir=".am$$" && \ rm -rf $backupdir && mkdir $backupdir && \ if (makeinfo --split-size=5000000 --split-size=5000000 --version) >/dev/null 2>&1; then \ for f in bfd.info bfd.info-[0-9] bfd.info-[0-9][0-9] bfd.i[0-9] bfd.i[0-9][0-9]; do \ if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \ done; \ else :; fi && \ if makeinfo --split-size=5000000 --split-size=5000000 -I ../.././bfd/doc \ -o bfd.info `test -f 'bfd.texinfo' || echo '../.././bfd/doc/'`bfd.texinfo; \ then \ rc=0; \ else \ rc=$?; \ $restore $backupdir/* `echo "./bfd.info" | sed 's|[^/]*$||'`; \ fi; \ rm -rf $backupdir; exit $rc ./elf.texi:11: raising the section level of @subsubsection which is too low make[3]: *** [Makefile:394: bfd.info] Error 1 make[3]: Leaving directory '/home/pi/source/gcc-ti99/build/binutils-2.19.1/bfd/doc' Making info in po make[3]: Entering directory '/home/pi/source/gcc-ti99/build/binutils-2.19.1/bfd/po' make[3]: Nothing to be done for 'info'. make[3]: Leaving directory '/home/pi/source/gcc-ti99/build/binutils-2.19.1/bfd/po' make[3]: Entering directory '/home/pi/source/gcc-ti99/build/binutils-2.19.1/bfd' make[3]: Nothing to be done for 'info-am'. make[3]: Leaving directory '/home/pi/source/gcc-ti99/build/binutils-2.19.1/bfd' make[2]: *** [Makefile:1094: info-recursive] Error 1 make[2]: Leaving directory '/home/pi/source/gcc-ti99/build/binutils-2.19.1/bfd' make[1]: *** [Makefile:3094: all-bfd] Error 2 make[1]: Leaving directory '/home/pi/source/gcc-ti99/build/binutils-2.19.1' make: *** [Makefile:717: all] Error 2 Here's the gcc version I'm using: gcc (Raspbian 8.3.0-6+rpi1) 8.3.0 Copyright (C) 2018 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. I've compiled all GCC for the TI on older versions of Raspbian, etc., without issue. Any idea on what may up? Thank you
  • Create New...