| Ubuntu>minicom>kermit ( NOT A HW ? ) [message #9167] |
Wed, 29 September 2021 08:54  |
curbie
Messages: 55
Registered: June 2021
|
Member |
|
|
I labeled the title, so the hardware folks don't waste their time reading a software question.
Well, I've been playing with kermit for a couple days now, and there is just so many potential problem spots in this Ubuntu>minicom>kermit chain, that I don't know where start trouble shooting. My question is, does any Linux/Ubuntu users use kermit through minicom, and do they have a setup link for me?
For those interested in what I done so far:
It started with studying the "File transfer protocols" screen ^A-O, then opening a terminal window to check /usr/bin/ for kermit, when typing 'kermit' I got back a:
"kermit is not currently installed, you can install it by typying:
sudo apt-get install ckermit" which I did.
I used the guide at https://lists.denx.de/pipermail/u-boot/2003-June/001527.html to setup kermit in minicom. And don't understand points:
2. when you configure minicom by "minicom -s"(you have to be root),
3. make sure your serial port devices are 'rw' to non-root users
On point 2, does configue = run?, on point 3, don't think Ubunu Ver 20.x+ will allow that and will lock that port if you try? I think I ran into the same thing setting up my USB eprom reader/writer, my recollection getting that to work was, I had to monkey with user privileges.
a:gkermit -r & minicom>send>kermit>abc.txt
s:gkermit -s asmtst.s & minicom>recieve>kermit
always ends with "Too many retries_"
did lots more like trying to run kermit directly through terminal window, couldn't get anything to work.
curbie
|
|
|
|
| Re: Ubuntu>minicom>kermit ( NOT A HW ? ) [message #9168 is a reply to message #9167] |
Wed, 29 September 2021 14:26  |
mikemac
Messages: 250
Registered: March 2017
|
Senior Member |
|
|
I've never managed to get kermit to successfully work inside minicom. Run? Yes. Transfer files? No. "Too many retries" sounds familiar. I eventually gave up and went back to physically moving the flash chip between the programmer and the embedded board. I stuck a ZIF socket in the flash socket on the board so I wouldn't wear out the soldered down socket. It works reasonably well, just not as nice as just clicking a button or two.
#2 The minicom menu will have two exit options. The first is to exit the config screen and continue running minicom. The second to to exit the whole program and return to the command line.
Mike
[Updated on: Wed, 29 September 2021 14:26] Report message to a moderator |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
RetroBrew Computers Forum
Members
Search
Help
Login
Home
it seemed like the text 'cut' in Ubuntu, so building on plasmo's pip suggestion after a lot of tests I finally succeeded with pip on the CB030, and using mimicom's ^A-S Ascii then ^Z to close the pip file. The only caveat so far is, the sending file needs at least one, I use two returns to end the file to kill me's "File has funny line at EOF" message.
