General • Re: eidt program with WiFi connection only

maybe utelnetserver isn't doing the right rfc2217 thing

Could be. It has a "discard telnet control characters and null bytes" section so could be sinking and ignoring what's sent, not replying when it should or is expected to.

I'm not familiar with RFC2217, but do recall worrying about Telnet negotiation at start up when working on a non-Pi TCP Telnet server. I recall it just worked without supporting that but that was also using a Telnet client. As that works with this 'utelnet' perhaps it's 'mpremote' waiting for something which isn't guaranteed to be returned ?

I get the same "it may be in use by another program" as you, but does seem to have tried to negotiate. So I guess it's a case of trying to figure out what 'mpremote' doesn't like, isn't getting -

Using 'telnet 192.168.0.206'Using 'mpremote connect rfc2217://192.168.0.206:23'Aha; RFC2217 is more than just 'telnet -> TCP -> server' seems to be 'client -> TCP -> proxy+serial -> server' so maybe it's waiting for some acknowledgement of configuring the serial port, making the connection. I think there's some reading to do.

Update : Seems it may be that 'FF FD/FB 2C' which is expecting a response. Responding does leave the Pico in Raw REPL mode which is different to previously, but 'mpremote' still bales.

Statistics: Posted by hippy — Wed Apr 10, 2024 4:35 pm

---