 Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me. |
Forum Index : Microcontroller and PC projects : Serial console apps for Linux....
| Author | Message | ||||
Grogster Admin Group  Joined: 31/12/2012 Location: New ZealandPosts: 9757 |
Hiya.  I am aware of Minicom and PUTTY - are there any others? I am looking for one that can log anything received on the serial port, to a text file for examination later. Not sure if Minicom or PUTTY can do that already - I am off to research that aspect of both of those programs now. Smoke makes things work. When the smoke gets out, it stops! |
||||
| robert.rozee Guru  Joined: 31/12/2012 Location: New ZealandPosts: 2466 |
GFXterm64 can do this - either logging directly to a text file, or if launched from a console/terminal window there is a menu option to echo all incoming serial data in human-readable form with timestamps to the launching console/terminal (this output can be redirected, just as in DOS). cheers, rob :-) |
||||
| Grogster Admin Group Joined: 31/12/2012 Location: New ZealandPosts: 9757 |
Hey Rob! I did not think that GFXterm had a Linux version? I thought it was Windoze only? Can you please tell me more? GFXterm is my go-to terminal software in Windoze. It would be fabulous if I could use it in Linux!!!!  Smoke makes things work. When the smoke gets out, it stops! |
||||
| JohnS Guru Joined: 18/11/2011 Location: United KingdomPosts: 4147 |
Some more: screen moserial gtkterm picocom gterm qqtterm cutecom screen does lots of things... I'm not sure which may care whether you run them from the command line / need a sane TERM setting. John |
||||
| robert.rozee Guru Joined: 31/12/2012 Location: New ZealandPosts: 2466 |
the last release of GFXterm64 for linux on the forums can be found here: https://www.thebackshed.com/forum/ViewTopic.php?FID=16&TID=12154 remember to change the properties of the file to allow running it. in linux mint this can be found under the 'permissions' tab of the file's properties. or you can use chmod from a console window: chmod 775 ./GFXterm64 you will also need to add your current user to the dialout group to enable access to serial ports: sudo adduser $USER dialout once up and running (by typing ./GFXterm64 from a console window), you can then turn on sending output to the console window with: right-mouse-click -> "diagnostics" -> "Rx Data -> console" (windows doesn't support GUI applications writing to the console, hence why this was handled quite differently in the win32 version). or for just saving the ascii text verbatim, you can use: right-mouse-click -> "LOG to file" exactly as in the win32 version. since RC3 there have been some changes, but nothing major. hopefully i'll get round to releasing an updated version soon, with a few enhancements. only the linux version (compiled with lazarus rather than delphi) is still being maintained, but one of the things i'd like to do is create a version that is cross-platform - as lazarus itself is - that can also be compiled for OsX, win32, RPi/ARM, etc. cheers, rob :-) Edited 2021-07-04 00:34 by robert.rozee |
||||
CaptainBoing Guru Joined: 07/09/2016 Location: United KingdomPosts: 2171 |
in putty...  |
||||
hitsware2 Guru Joined: 03/08/2019 Location: United StatesPosts: 735 |
https://www.digitalpeer.com/blog/serial-terminal-program-rundown-for-linux my site |
||||
panky Guru Joined: 02/10/2012 Location: AustraliaPosts: 1116 |
Rob, Been using GFXterm on Mint 20 and it works fine. One thing I note when using it with the Pico, any time the Pico resets (eg. software upgrades etc.), GFXterm looses the connection and I have to manually re-connect. I also use minicom and it registers the disconnect but also automatically re-connects without me having to do anything (including plugging/unplugging the USB). Is there any setup facility for GFXterm to get around having to manually restart after a disconnect? Doug. ... almost all of the Maximites, the MicromMites, the MM Extremes, the ArmMites, the PicoMite and loving it! |
||||
| robert.rozee Guru Joined: 31/12/2012 Location: New ZealandPosts: 2466 |
hi Doug, the simple workaround is to press control-space and GFXterm for linux will reconnect to the last port it was connected to. GFXterm for windows uses alt-space to do the same thing. the more complex answer is... it is complicated! when the pico (running either peter's port of mmbasic, or micropython) disconnects then immediately reconnects the USB from the pico end, it can end up doing any of the below: 1. reappear as the same port name, or, 2. reappear as a different port name, or, 3. not reappear at all (requiring a reset or re-plug), or, 4. knock over the USB sub-system, requiring some tinkering to fix. it is pretty much impossible to be certain which one will happen. often, simply reopening the same port when it reappears would work. also often, opening the next USB port that appears (irrespective of name) will work. also, not infrequently, the USB sub-system of the host will require manually unbinding/rebinding to get it back up and running again - something that requires elevated privileges. as such, any fully automatic solution will only work, at best, most of the time. sometimes, the wrong port may be opened (if you open the next port that appears). much the same set of problems apply to windows. in the end, i decided that it was simpler to just have the user click 'ok' on the error message popup, then press control-space to attempt to reconnect to the same port. i did also feel that hiding the fact that the target had (intentionally or not) reset, was a sub-optimal idea. cheers, rob :-) Edited 2021-07-04 22:14 by robert.rozee |
||||
| panky Guru Joined: 02/10/2012 Location: AustraliaPosts: 1116 |
Hi Rob, Thanks for the detailed explanation, Regards, Doug. ... almost all of the Maximites, the MicromMites, the MM Extremes, the ArmMites, the PicoMite and loving it! |
||||
| panky Guru Joined: 02/10/2012 Location: AustraliaPosts: 1116 |
Hi Rob, Been doing quite a bit of work with the Pico and while your method above works, it is frustrating that I can never see the startup banner from the Pico and as MM.VER only gives the major version eg. 5.07, I have no real way to check which beta I have loaded. Would it be possible to have GFXTerm64, when it detects the USB connection has dropped, to attempt to re-connect to the same port for say, 2 seconds before erroring out to the pop up window? In my experience here (Mint 20.2), the Pico always comes back on the same port. For your consideration, Regards, Doug. ... almost all of the Maximites, the MicromMites, the MM Extremes, the ArmMites, the PicoMite and loving it! |
||||
| robert.rozee Guru Joined: 31/12/2012 Location: New ZealandPosts: 2466 |
see: http://www.thebackshed.com/forum/ViewTopic.php?FID=16&TID=13973#174034 disconnecting, then reconnecting with ctrl-space within 500ms of resetting the pico works. i have also confirmed that this approach also works with unplugging and then replugging the USB cable - assuming the port name doesn't end up changing. mine does change a percentage of the time. it would be rather handy if the pico responded to a break signal with a leisurely reset, as the problem interactions with linux seem to be, in good part, due to the pico coming back to life before the linux USB subsystem has had time to release the port. cheers, rob :-) |
||||
 Print this page |
 |
The Back Shed's forum code is written, and hosted, in Australia. | © JAQ Software 2025 |
