-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
serial support for Pico1140? #6
Comments
|
Dear Guido, Thanks for this. I am afraid that the Pico-SDK serial IO scheme is not great as several changes need to be made to change from SerialUSB to Serial. I would note that I have found the SerialUSB system to be quite reliable. However, I assume you wish to connect the Pico to a 'proper' terminal. I think your code is fine. Regards, Ian. |
Dear Ian, Normally I also like the easy way to connect to USB ;) Also I had talked to some people and they would connect - as you wrote - a proper terminal like a read DEC Terminal or a serial Bluetooth-Converter :) I also like this serial2Telnet-Thing. I was surprised that my code did worked so well. Its great to hear that you will find my code "fine" too ;) Kind Regards, |
|
Dear Ian, I did it now the following way: The huy who wants to connect the Pico_1140 serial to a real VT100 did need a 9600 Baud version. In the first try the version did also use 115200 Baud because the So I did after the normal init a full_uart _init Kind Regards & a happy new Year 2023, |
|
Dear Guido, Thanks again. I am not surprised about the apparent serial speed. The serial I/O is throttled at 1 transaction per 10000 cpu cycles. You could reduce this (see line 161 in avr11.cxx (500) and kl11.cxx (20)) a bit but other problems may arise. I think the speed is about right and is about 9600 baud or so. Regards, Ian. |
|
Please see the latest info in the images directory of the repo. The .UF2 file has been built with both serial and USB support. |
Dear Ian, Great to this would be a top-notch for reading a config-file before starting the real Pico_1140 emulation and to set the parameters of Pico_1140.cxx and hw_config.c from from the config-file in a format like this: Do you think thats possible? Thats would be very hepfull for a simple and universal "onthefly" Kind regards |
|
Hmmm, new version from git, build on linux VS-Code, I have only one USB port after power on. |
|
Hi Bruno,
I had forgotten to add this to the repo.
1. Update the tusb_config.h which is on my system at /home/pi/pico/pico-sdk/src/rp2_common/pico_stdio_usb/include
Change the line
#define CFG_TUD_CDC (1)
to
#define CFG_TUD_CDC (2)
1. Copy the attached file to : /home/pi/pico/pico-sdk/src/rp2_common/pico_stdio_usb
I hope you can find the correct paths on your system as I use VSCode in windows. I have had a guess above for the path that might be used under Raspbian.....
If you still have a problem, let me know and I will install the PicoSDK under Linux and see what is going on....
When I have enough info about the options for various dev environments, I will update the repo.
Regards, Ian.
…________________________________
From: Bruno Novak ***@***.***>
Sent: 15 February 2023 2:00 PM
To: Isysxp/Pico_1140 ***@***.***>
Cc: Ian Schofield ***@***.***>; State change ***@***.***>
Subject: Re: [Isysxp/Pico_1140] serial support for Pico1140? (Issue #6)
⚠ External sender. Take care when opening links or attachments. Do not provide your login details.
Hmmm, new version from git, build on linux VS-Code, I have only one USB port after power on.
Do I need to configure some special in source for extra USB port?
[1058248.390690] usb 3-1: new full-speed USB device number 14 using xhci_hcd
[1058248.568727] usb 3-1: New USB device found, idVendor=2e8a, idProduct=000a, bcdDevice= 1.00
[1058248.568737] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[1058248.568740] usb 3-1: Product: Pico
[1058248.568742] usb 3-1: Manufacturer: Raspberry Pi
[1058248.568744] usb 3-1: SerialNumber: E6616407E34A7E22
[1058248.573907] cdc_acm 3-1:1.0: ttyACM0: USB ACM device
—
Reply to this email directly, view it on GitHub<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIsysxp%2FPico_1140%2Fissues%2F6%23issuecomment-1431415424&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C3a7801c0e8b74ce86da808db0f5d06e0%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638120664436674608%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=xIOy%2FAj%2BHO%2BKWEeTsWDf4xUhXtr%2FEik%2BWIQ527piGtA%3D&reserved=0>, or unsubscribe<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACYZOB7EODIRIPVJHZJLPTTWXTOQTANCNFSM6AAAAAATLFG4YU&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C3a7801c0e8b74ce86da808db0f5d06e0%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638120664436674608%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=AYxpMeibIIwws4qxizbIQyOaiGYM8ZKZ9R89%2BvbE4u4%3D&reserved=0>.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
|
Nope, it doesn't work. |
Hi Spoofy-zz, I changed and copied and it worked after the compile with 2 USB-ports: Please check if the first part of your pico-sdk path is /pico-sdk/ or /PICO-SDK/ for changing the first file. |
|
YES, it was wrong PICO_SDK path in VSCode. |
|
rsx 4.0 with FORTRAN IV and Cobol compilers, Basic is planned but need to solve some problems first. Two terminals are defined, so you can log in on the second terminal too. |
|
Hello,
It is C compiler too, but it cannot be installed on this image while some
symbols are missing.
I am working on generating a new v4.6 image that the C compiler works on.
I'll send it as soon as it's done.
Bruno Novak
…On Fri, Feb 17, 2023 at 7:34 PM Ian Schofield ***@***.***> wrote:
Dear Bruno,
Thaks again for this image. It works fine and mounting an RK05 image works
as well. In the meanwhile, just for a little challenge,
is there a c compiler for RSX11??????
Regards, Ian.
________________________________
From: Bruno Novak ***@***.***>
Sent: 16 February 2023 12:39 PM
To: Isysxp/Pico_1140 ***@***.***>
Cc: Ian Schofield ***@***.***>; State change ***@***.***>
Subject: Re: [Isysxp/Pico_1140] serial support for Pico1140? (Issue #6)
⚠ External sender. Take care when opening links or attachments. Do not
provide your login details.
rsx 4.0 with FORTRAN IV and Cobol compilers, Basic is planned but need to
solve some problems first.
Image has support for RL and RK devices, so you can mount one additional
DK disk when image is running.
One TS tape device is also genned, so you can install software from tapes
if image is running in simh, and perhaps
for the future tape device when is available in Pico emulation :-) .
rsxm32-for-cbl.rl02.zip<
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIsysxp%2FPico_1140%2Ffiles%2F10756015%2Frsxm32-for-cbl.rl02.zip&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C4af02cb9ac3e4913005708db101ad6e0%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638121480557747547%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=X0BxDFQgYu%2FYUyQcZcnFwU17j7Yk74XZmUCe79BDRjI%3D&reserved=0>
Two terminals are defined, so you can log in on the second terminal too.
Maybe some cleaning is also needed, but that some later.
—
Reply to this email directly, view it on GitHub<
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIsysxp%2FPico_1140%2Fissues%2F6%23issuecomment-1433026878&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C4af02cb9ac3e4913005708db101ad6e0%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638121480557747547%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=fpGMVHdyGvTxOK7o3vBSECZiRiV6EHpvMH1o1apN45c%3D&reserved=0>,
or unsubscribe<
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACYZOBZ4JCSRFQGTXI7LBADWXYNX3ANCNFSM6AAAAAATLFG4YU&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C4af02cb9ac3e4913005708db101ad6e0%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638121480557903783%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9kHTgLfONrs%2FfzlrUrp7VhaJywWN1kHz2VokcfKJOJk%3D&reserved=0>.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
—
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABRBMWCHAXDOHBXFIZSGNLWX7ABXANCNFSM6AAAAAATLFG4YU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Hello. |
|
DCL:
|
|
Basic2 is a tough nut to crack, but I think I'll make it. |
|
Here is an image with Basic Plus 2, running good on simh, but crashed on Pico_1140. |
|
Here is BP2 install with EIS, but same result. It must be other problems. |
|
Dear Bruno,
Sorry for the delay. Your disk image is valid and works OK with Simh. However, I have now found out by a very circuitous route
that there is an underlying major fault with the emulation. Put simply, the original code places the general registers in the IOPAGE
(which is correct) but, at an arbitrary and unmapped location which does not match the true 11/40 cpu map.
This will take a bit of time to sort out as it is a fundamental design flaw. I am amazed it has not been seen before.
Anyway, do continue with a combined Fortan/Cobol/Basic build if you can as I am sure I will get this to work.
Regards, Ian.
…________________________________
From: Bruno Novak ***@***.***>
Sent: 23 February 2023 5:44 PM
To: Isysxp/Pico_1140 ***@***.***>
Cc: Ian Schofield ***@***.***>; State change ***@***.***>
Subject: Re: [Isysxp/Pico_1140] serial support for Pico1140? (Issue #6)
⚠ External sender. Take care when opening links or attachments. Do not provide your login details.
Here is BP2 install with EIS, but same result. It must be other problems.
Maybe is a problem with intensive disk I-O because BP2 is not installed with resident library, which I can not
make while it ask for too big partitions for RMSRES and BP2RES.
I am trying for 2 days, but unsuccessfully, 124 KW is the minimum for this. Perhaps an experienced RSX system programmer can do this.
rsx11m46-bp2.rl02.zip<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIsysxp%2FPico_1140%2Ffiles%2F10816551%2Frsx11m46-bp2.rl02.zip&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7Cef1024b0c838408db2f708db15c59e2f%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638127711832464248%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=eAafOdM3D5g7EtMZMTDjpfHnRDEOTkNqWZzhUihbBdk%3D&reserved=0>
—
Reply to this email directly, view it on GitHub<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIsysxp%2FPico_1140%2Fissues%2F6%23issuecomment-1442184009&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7Cef1024b0c838408db2f708db15c59e2f%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638127711832464248%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=BbYjKyhnkPs%2BmNqbovazRMWc%2BZq9WH2jr%2B6YPA9IF9Q%3D&reserved=0>, or unsubscribe<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACYZOBZYYQ4MDTRF2E4A2XTWY6OX3ANCNFSM6AAAAAATLFG4YU&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7Cef1024b0c838408db2f708db15c59e2f%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638127711832464248%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=qIg7drXGvoijhOvwOIawKK5Pu7DbwOOjzzM66A5QZXI%3D&reserved=0>.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
|
Hello Ian! Thank you very much. I will continue to work on images. Basic now works.
|
Dear Ian/Bruno Kind regards |
|
Hmmm. How much RAM you have in your uf2? I have built from Ian's git, and it has 112 KW. . |
Strange - I added the latest changes for kl.* and kb.* from the commits to my source, but only have 96.K MAPPED And in your file rsx11m40-for-cbl.rl02.zip is only a version rsxm32-for-cbl.rl02 With this rl02 I do get: |
|
Sorry, wrong image. There is one more time. |
Found the 112KW change in unibus.* when the RL-handler was updated. ;) With your new image it does work :) |
|
Dear Bruno,
Re: KERMIT. I have updated the DL0 interface for 8 bit I/O. New .UF2 in repo/images.
Does this work?
Regards, Ian.
________________________________
From: Bruno Novak ***@***.***>
Sent: 01 March 2023 5:25 PM
To: Isysxp/Pico_1140 ***@***.***>
Cc: Ian Schofield ***@***.***>; State change ***@***.***>
Subject: Re: [Isysxp/Pico_1140] serial support for Pico1140? (Issue #6)
⚠ External sender. Take care when opening links or attachments. Do not provide your login details.
Hello Ian!
Thank you very much. I will continue to work on images. Basic now works.
I wonder what the next error will be!
:-) No problem, if you really want:
Kermit crashes when you are in local mode connected to remote Linux running Kermit in server mode and issuing remote commands. It is not so essential, but that is also one issue. I can transfer files to image with SIMH or with second DK disc.
Best wishes, Bruno.
KERMIT
Kermit-11 T3.60 Last edit: 21-Mar-89
Check SHOW RELEASE_NOTES for possible incompatabilities
with previous releases of Kermit-11 and other Kermits.
Linked for RSX11M/M+ and P/OS
Kermit-11>set line tt1:
Link device: TT1: Speed not settable
Kermit-11>remote dir *.*
Packets received : 0 Naks: 0 Timeouts: 0
00:06:59 Task "...KER" terminated
Memory protect violation
R0=177666
R1=015377
R2=155161
R3=000002
R4=164501
R5=011206
SP=071352
PC=155162
PS=170010
—
Reply to this email directly, view it on GitHub<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIsysxp%2FPico_1140%2Fissues%2F6%23issuecomment-1450543024&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C40448eec12014dc99c7c08db1a7a020d%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638132883535472392%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Tr8GzSivYRJuQ8XHE1MJ8uDUh5i8I9UiqAxxBBKOk5c%3D&reserved=0>, or unsubscribe<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACYZOB3KQHLT7VEBN7X5LO3WZ6BB7ANCNFSM6AAAAAATLFG4YU&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C40448eec12014dc99c7c08db1a7a020d%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638132883535472392%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=e0sqJUxpcSCZpTVf5%2B5DRgrdsBhYnB1AO3W3WUVQeKY%3D&reserved=0>.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
|
Unfortunately, I can't try it because I don't have a serial interface on the Pico. USB only. Can you please send me a change in the code, so I can try to build a new image myself? |
|
Dear Bruno,
No problem. At risk of getting out of sync, here is the new DL11.CXX.
Regards, Ian.
…________________________________
From: Bruno Novak ***@***.***>
Sent: 02 March 2023 5:14 PM
To: Isysxp/Pico_1140 ***@***.***>
Cc: Ian Schofield ***@***.***>; State change ***@***.***>
Subject: Re: [Isysxp/Pico_1140] serial support for Pico1140? (Issue #6)
⚠ External sender. Take care when opening links or attachments. Do not provide your login details.
Unfortunately, I can't try it because I don't have a serial interface on the Pico. USB only. Can you please send me a change in the code, so I can try to build a new image myself?
—
Reply to this email directly, view it on GitHub<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIsysxp%2FPico_1140%2Fissues%2F6%23issuecomment-1452227935&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7Ce35a0ee334e24638649e08db1b418569%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638133740439570632%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9nZvLFC%2Bkh6VAyt6etQH2woigwHoJCi6HMbWNKOIQHw%3D&reserved=0>, or unsubscribe<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACYZOB2WC73TFUTMSYISKS3W2DINTANCNFSM6AAAAAATLFG4YU&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7Ce35a0ee334e24638649e08db1b418569%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638133740439570632%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=6rDJEQM9bhJQjuvhCs226u9cd3p6APJ0Nmxg0lqx6uo%3D&reserved=0>.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
#include <cstdlib>
#include <fcntl.h>
#include <signal.h>
#include <stdint.h>
#include <stdio.h>
#include "kb11.h"
#include "dl11.h"
#include <stdio.h>
#include "tusb.h"
#include "pico/stdlib.h"
extern KB11 cpu;
static bool keypressed = false;
DL11::DL11() {
}
void DL11::clearterminal() {
rcsr = 0;
xcsr = 0x80;
rbuf = 0;
xbuf = 0;
count = 0;
}
static int _kbhit()
{
return tud_cdc_n_available(1) || uart_is_readable(uart1);
}
void DL11::serial_putchar(char c)
{
if (tud_cdc_n_connected(1)) {
tud_cdc_n_write_char(1,c);
tud_cdc_n_write_flush(1);
}
uart_putc(uart1,c);
}
char DL11::serial_getchar()
{
if (tud_cdc_n_available(1))
return tud_cdc_n_read_char(1);
return uart_getc(uart1);
}
void DL11::poll() {
if (!rcvrdone()) {
// unit not busy
if (count++ > 20)
if (_kbhit() || keypressed) {
char ch = serial_getchar();
count = 0;
if (ch) {
//rbuf = ch & 0x7f;
rbuf = ch;
rcsr |= 0x80;
if (rcsr & 0x40) {
cpu.interrupt(INTDLR, 4);
}
}
else {
keypressed = false;
}
}
}
if (xbuf) {
xcsr |= 0x80;
xbuf = 0;
if (xcsr & 0x40) {
cpu.interrupt(INTDLT, 4);
}
}
else {
if (iflag == 1) {
cpu.interrupt(INTDLT, 4);
iflag = 2;
}
}
}
uint16_t DL11::read16(uint32_t a) {
int i;
switch (a & 7) {
case 00:
return rcsr;
case 02:
rcsr &= ~0x80;
return rbuf;
case 04:
return xcsr;
case 06:
return xbuf;
default:
printf("Dl11: read from invalid address %06o\n", a);
trap(INTBUS);
}
}
void DL11::write16(uint32_t a, uint16_t v) {
switch (a & 7) {
case 00:
rcsr = ((rcsr & 0200) ^ (v & ~0200));
break;
case 02:
//rcsr &= ~0x80;
break;
case 04:
xcsr = ((xcsr & 0200) ^ (v & ~0200));
if ((xcsr & 0300) == 0300 && iflag == 0)
iflag = 1;
if (iflag == 2)
iflag = 0;
break;
case 06:
xbuf = v & 0x7f;
serial_putchar(v);
xbuf |= 0200; // Allow for nulls !!!!
//xcsr &= ~0x80;
iflag = 0;
break;
default:
printf("Dl11: write to invalid address %06o\n", a);
trap(INTBUS);
}
}
|
|
No, it still crashes, but it's interesting that sending from Pico to Linux works without problems, but the reverse direction generates "memory protect violation". I will try to somehow install kermit on the RT image and see if the problem is the same there. |
|
Dear Bruno,
If you mean RT11,:I have just had a go at this with (I think) the Columbia build
… KRTMIN.SAV under the SJ monitor. It say that I am short of memory. I will check again using Simh to see if there is another problem.
Regards, Ian.
…Sent from my iPad
On 2 Mar 2023, at 17:40, Bruno Novak ***@***.***> wrote:
⚠ External sender. Take care when opening links or attachments. Do not provide your login details.
No, it still crashes, but it's interesting that sending from Pico to Linux works without problems, but the reverse direction generates "memory protect violation". I will try to somehow install kermit on the RT image and see if the problem is the same there.
But it may take some time. I need to remember how RT works with disks and see how to transfer the kermit binary from DECUS tape to an RT disk.
—
Reply to this email directly, view it on GitHub<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIsysxp%2FPico_1140%2Fissues%2F6%23issuecomment-1452262152&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C8790c701b4074a10708608db1b453bc0%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638133756384703734%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=NkN8vbK%2FlA1EmI8wuHsts7aoFI%2BOj1B8tVBSP52dD7s%3D&reserved=0>, or unsubscribe<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACYZOB7CJA3R4YAGSPNJWL3W2DLRJANCNFSM6AAAAAATLFG4YU&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C8790c701b4074a10708608db1b453bc0%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638133756384703734%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=U%2BttFgmJYC1uftJ4QNXy4pMXE1k4uQTDdN9m4Ds3WkE%3D&reserved=0>.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
|
Same case in SIMH RT-11 FB monitor. |
|
Hi Bruno,
Much coffee required! Anyway, Used Kermit under Rasbian to connect to the Pico booted with the RT11XM monitor.
Via a connect from Rasbian, I activated the Pico Kermit with VRUN KRTMIN and then put it in server mode.
Returned to the Rasbian end, disconnected and then tried RDIR *.*, SEND <file> and GET <file>and everthing worked!!!
It appears that the RT11 version I have cannot use the DL11 ... only the console.
In regard of the RSX11M version on the Pico, don't forget that there is a terminal listener on the DL11 interface (ie you can login etc)
I wonder if you need to stop this before using the DL11 from Kermit?????
Regards, Ian.
…________________________________
From: Bruno Novak ***@***.***>
Sent: 03 March 2023 9:35 AM
To: Isysxp/Pico_1140 ***@***.***>
Cc: Ian Schofield ***@***.***>; State change ***@***.***>
Subject: Re: [Isysxp/Pico_1140] serial support for Pico1140? (Issue #6)
⚠ External sender. Take care when opening links or attachments. Do not provide your login details.
Same case in SIMH RT-11 FB monitor.
I don't know, I will be trying later. It is time for a cup of Coffee.
—
Reply to this email directly, view it on GitHub<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIsysxp%2FPico_1140%2Fissues%2F6%23issuecomment-1453236423&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7Cb31b613b7aaa4a9795e508db1bca913b%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638134329047345858%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=aA8BrlrFq7ZCIhXioOFe%2Ffp3HRxwdVBpcgXU64i5EBU%3D&reserved=0>, or unsubscribe<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACYZOB6VIG4T5E277UV5L4TW2G3MNANCNFSM6AAAAAATLFG4YU&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7Cb31b613b7aaa4a9795e508db1bca913b%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638134329047345858%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2FP7id%2BvC3zvLfBasYl3rYL3E3JiPFv31gANez0Yx%2FIk%3D&reserved=0>.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
|
I don't know. However, i can send file from Pico to my Linux with c-kermit in server mode. It crashes when I run remote commands from Pico. Here is my rsx11 image, on which is kermit installed and from which I tested if you wish to test. |
|
Dear Bruno,
I have been looking at Kermit. The whole area of file transfer is a bit involved as you know.
To get to the point, I used Teraterm to send/receive files and it works fine. (Not sure about binaries). ... Pico in server mode ...
However, modern versions of Kermit are still a problem and can cause a memory fault.
This seem to happen if the Pico is in master mode and the other Kermits in server mode.
In this case, a simple remote dir command causes a crash even after very few characters have been sent. (or a get <file>)
I do not know if this might be a problem with the DL11, a protocol error or an emulation error.
I have just managed to connect RSX11 under simh to a kermit (RSX11 is server). And, it crashed on send file to RSX11. ...KER disappears from the task map.
As I have to use the console for kermit, I can't see the error message but I suspect it is due to a memory fault.
Increasing the simh memory to 256K does not help.
Therefore, I wonder if this is a protocol error such that the modern kermits are not backwards compatible.
It looks like SecureCRT/Teraterm are the only option at the moment. As simh crashes as well, I don't think this can be resolved.
Regards, Ian.
…________________________________
From: Bruno Novak ***@***.***>
Sent: 03 March 2023 11:17 AM
To: Isysxp/Pico_1140 ***@***.***>
Cc: Ian Schofield ***@***.***>; State change ***@***.***>
Subject: Re: [Isysxp/Pico_1140] serial support for Pico1140? (Issue #6)
⚠ External sender. Take care when opening links or attachments. Do not provide your login details.
I don't know. However, i can send file from Pico to my Linux with c-kermit in server mode. It crashes when I run remote commands from Pico.
And what is more weird, I use SecureCRT which have built-in kermit support and can send files to Pico kermit in server mode.
Combining these two methods, a can send files to both direction.
I don't know how separate point of failure.
rsx11m46-ccc.rl02.zip<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIsysxp%2FPico_1140%2Ffiles%2F10881341%2Frsx11m46-ccc.rl02.zip&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C76178ab9f05441e019c808db1bd8ded0%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638134391830658376%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GuBrI5tp2RybVy2HzG62etbU3GHZ754CZ1N7oJY1Ygw%3D&reserved=0>
Here is my rsx11 image, on which is kermit installed and from which I tested if you wish to test.
To run kermit it is task installed as KER.
—
Reply to this email directly, view it on GitHub<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIsysxp%2FPico_1140%2Fissues%2F6%23issuecomment-1453374604&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C76178ab9f05441e019c808db1bd8ded0%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638134391830658376%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=bc%2FMK5MdYqmfpm82hnLmpLPey3VZMyBkZ5Vtl0ZxLQU%3D&reserved=0>, or unsubscribe<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACYZOB2MGEFTAW457V463ETW2HHMLANCNFSM6AAAAAATLFG4YU&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C76178ab9f05441e019c808db1bd8ded0%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638134391830658376%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=1bGUPXSqdR4tV1oMOsm7tdpg%2BHeYhX20g8gugrPkL08%3D&reserved=0>.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
|
Dear Bruno,
Sorry for another post. Apparently, this is a known problem ... should have looked harder: Importing files to simh RSX? (narkive.com)<https://alt.sys.pdp11.narkive.com/0UyJNmJ6/importing-files-to-simh-rsx>
The trick is to enter 'set attributes off' on the newer versions of Kermit eg K95 etc.
This partly solves the problem as the transfer is not always reliable but the RSX kermit does not crash anymore in either direction.
I am not really sure if this is a usable option as the transfer is sooooo slow! Probably need another method.......
Regards, Ian.
…________________________________
From: Bruno Novak ***@***.***>
Sent: 03 March 2023 11:17 AM
To: Isysxp/Pico_1140 ***@***.***>
Cc: Ian Schofield ***@***.***>; State change ***@***.***>
Subject: Re: [Isysxp/Pico_1140] serial support for Pico1140? (Issue #6)
⚠ External sender. Take care when opening links or attachments. Do not provide your login details.
I don't know. However, i can send file from Pico to my Linux with c-kermit in server mode. It crashes when I run remote commands from Pico.
And what is more weird, I use SecureCRT which have built-in kermit support and can send files to Pico kermit in server mode.
Combining these two methods, a can send files to both direction.
I don't know how separate point of failure.
rsx11m46-ccc.rl02.zip<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIsysxp%2FPico_1140%2Ffiles%2F10881341%2Frsx11m46-ccc.rl02.zip&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C76178ab9f05441e019c808db1bd8ded0%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638134391830658376%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GuBrI5tp2RybVy2HzG62etbU3GHZ754CZ1N7oJY1Ygw%3D&reserved=0>
Here is my rsx11 image, on which is kermit installed and from which I tested if you wish to test.
To run kermit it is task installed as KER.
—
Reply to this email directly, view it on GitHub<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIsysxp%2FPico_1140%2Fissues%2F6%23issuecomment-1453374604&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C76178ab9f05441e019c808db1bd8ded0%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638134391830658376%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=bc%2FMK5MdYqmfpm82hnLmpLPey3VZMyBkZ5Vtl0ZxLQU%3D&reserved=0>, or unsubscribe<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACYZOB2MGEFTAW457V463ETW2HHMLANCNFSM6AAAAAATLFG4YU&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C76178ab9f05441e019c808db1bd8ded0%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638134391830658376%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=1bGUPXSqdR4tV1oMOsm7tdpg%2BHeYhX20g8gugrPkL08%3D&reserved=0>.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
|
Hallo Ian, |
|
Dear Bruno,
Thanks for your note. I have to admit to not being too impressed with the Kermit apps for windows/linux> I cannot get binary files to transfer.
However, binary send/receive from Teraterm works absolutely fine and the sent/received files match up correctly.
I assume it must use a very basic kermit protocol. I am just in the process of trying to speed up the transfers a bit but I doubt if it is possible
to get much faster than the 200 bytes/sec at the moment. Will, let you know.
Regards, Ian.
…________________________________
From: Bruno Novak ***@***.***>
Sent: 05 March 2023 6:26 AM
To: Isysxp/Pico_1140 ***@***.***>
Cc: Ian Schofield ***@***.***>; State change ***@***.***>
Subject: Re: [Isysxp/Pico_1140] serial support for Pico1140? (Issue #6)
⚠ External sender. Take care when opening links or attachments. Do not provide your login details.
Hallo Ian,
Perfect, all works now.
I read that article a few days ago, and I'm surprised that I didn't come across that part where it was mentioned. I should have read more carefully. Thank you again, you made my day.
—
Reply to this email directly, view it on GitHub<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FIsysxp%2FPico_1140%2Fissues%2F6%23issuecomment-1455003079&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C14af848865bc456e6a3408db1d4283b6%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638135943734567486%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=DP2k91%2Bg2JtkhFXPcIsC6VMtqruzS1c6dzRM%2FiyBMoY%3D&reserved=0>, or unsubscribe<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACYZOBYWIODELBR4ZWBQJKTW2QWYFANCNFSM6AAAAAATLFG4YU&data=05%7C01%7Cian.schofield%40newcastle.ac.uk%7C14af848865bc456e6a3408db1d4283b6%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C638135943734567486%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=B0wxZ5qfYtCon7ezy%2BC6UKvGQ2yw2myECNIa8nILFPg%3D&reserved=0>.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|


Hi Ian,
do you think its possible to get serial-port-support for the terminal-output
(against the USB-CDC-serial)?
I did try to get it working myself, but failed.
In CMakeLists.txt I changed
from
pico_enable_stdio_usb(Pico_1140 1)
pico_enable_stdio_uart(Pico_1140 0)
to
pico_enable_stdio_usb(Pico_1140 0)
pico_enable_stdio_uart(Pico_1140 1)
In getline.cxx and kl11.cxx i replaced
tud_cdc_write_char ==> uart_putc
tud_cdc_flush ==> couldnt find the same for serial/uart - maybe stdio_flush
tud_cdc_available ==> uart_is_readable
tud_cdc_read_char ==> uart_getc
I also did add the configuration/init of the uart to getline.cxx
and commented out the wait for SB-conected in Pico_1140.cxx
[EDIT]
I did it get working in the 2nd try - was mainly my non-working serial-telnet-server on a ESP8266, now the serial-telnet-server is on a ESP32S2 ;)
But only small thing I which dont like in my part-of-code - I dont know to get the right SCOPE for 2 settings - which I have to include in getline.cxx, kl111.cxx and Pico_1140.cxx:
The follwing I only have in the Pico_1140.cxx:
As attachment my changed files:
Pico1140_serial.zip
And I got no clue how to wait for the serial connection like you do with USB.
I got such a thing for RunCPM in the Arduino-IDE:
But dont knwo how to program it in the Pico-SDK:
Kind regards
Guido
The text was updated successfully, but these errors were encountered: