Fastspin Terminal - ESC TO EXIT
msrobots
Posts: 3,709
in Propeller 2
Hi @ersmith ,
Houston we have a problem here.
If you use @Cluso99 debugger/monitor you need the ESC key to go back to TAQOZ. But you can't do that because the terminal window is closing.
is it possible to change the 'close' key to say shift-esc or ctrl-esc? or just use the close button of the window?
Enjoy!
Mike
Houston we have a problem here.
If you use @Cluso99 debugger/monitor you need the ESC key to go back to TAQOZ. But you can't do that because the terminal window is closing.
is it possible to change the 'close' key to say shift-esc or ctrl-esc? or just use the close button of the window?
Enjoy!
Mike
Comments
ctrl-] is standard on every keyboard and will gives 29 decimal (1D hex) and is know as GS or Group Seperator
ESC produces 27 decimal (1B hex)
Shift-esc and control-esc have no standard mapping on keyboards, and can only be done with scan codes,
and its likely different keyboards will NOT produce the same result.
I modify loadp2 or any other terminal program to do this.
OTOH you can always use another terminal program.
screen /dev/ttyUSB0 115200
To disconnect, ^Ak
Thank you @"Dave Hein", I really like the terminal provided, but need the ESC button...
Enjoy!
Mike
I currently use your terminal to test my ROM hijacking and can talk to TAQOZ then press ctrl-D to get to @Cluso99 's monitor, but it requires ESC to get back to TAQOZ.
Enjoy!
Mike
And, it seems that maybe the findp2 code, which has never worked on macOS, is no longer even able to pass through when the port description is given on the command line. macOS, does not use a Linux-style iterative port naming convention (like: "/dev/ttyUSBn", where 'n' is a number. It names the port like this: "/dev/cu.usbserial-P2EEI8V", with no number iteration), so the findp2 code was not able to find a macOS port. It was getting-by with version 0.007, by taking the port name from the command line. Not sure if 0.008 can handle macOS portnames at all (I could be wrong but have tested extensively and not found a 'cure').
With version 0.007, I also received "Unsupported baudrate" errors unless I use "-b 115200", which has always worked. There's something in the code about the 'B20000000' definition that does not work on macOS. And, since that is the loading default, it gets a failure. Perhaps there's a header file in Linux that differs from macOS in defining those baudrate constants.
Just my best guesses as to some issues...
dgately
Should I add an option to set the loading baud rate? This is currently fixed at 2 MBaud. Maybe a different loading rate would cure some of the problems with the Mac.
Maybe, but it's a shame that it can't behave like Linux and just use 2 MBaud. Do you know which header file defines the baud rates in Linux (i.e. B20000000, B115200, etc...)? I'm not finding the USB Serial C example code that Apple used to publish, so I'm at a loss as to why B2000000 is not defined. Maybe an #ifdef _macosx_ and define of the missing baud rates will work? I will try to test that idea.
dgately
I added a "-l" option that allows setting the loader baud rate. So you can now specify a loader baud rate other than 2 Mbaud.
I did not change osint_linux.c. There are a couple of recent changes in there that might be affecting the Mac, but if I back those out it would break Linux. If need be, I could create an osint_macos.c so that the Mac and Linux would no longer conflict.