The basic gist of the problem is that the -T argument no longer seems to successfully provide a carriage return at the end of the text that it remotely types, and this was impacting M65Connect's mechanism to upload new ROMs, which after uploading the ROM, would try to remotely type a SYS58552+enter in order to jump from c64-mode back to mega65-mode.
I'll preserve the details of the old discord thread below, though some of it may be a slight red-herring:
In discord, Tayger mentioned he experienced a problem using m65 to upload a new bitstream and latest 920181.BIN ROM.
With the latest m65 I have loaded the latest bitstream (R2) to do some tests... Then I have loaded ROM 920181.BIN that then keeps hanging in C64 mode that way:
When I press RETURN it switches to MEGA65 mode
I assume this is m65 related
Got further clarification of the issue from Tayger in today's Discord thread:
The basic gist of the problem is that the
-Targument no longer seems to successfully provide a carriage return at the end of the text that it remotely types, and this was impacting M65Connect's mechanism to upload new ROMs, which after uploading the ROM, would try to remotely type aSYS58552+enter in order to jump from c64-mode back to mega65-mode.I'll preserve the details of the old discord thread below, though some of it may be a slight red-herring:
In discord, Tayger mentioned he experienced a problem using m65 to upload a new bitstream and latest
920181.BINROM.Specifics of the commands he typed are here: