Finally I have a chance to look at this again. If I have CONFIG_NSH_CLE, the board boots, gets a DHCP lease, and responds to telnet, but with that ^[[62;6R business... and doesn't seem to function much beyond that.
If I have CONFIG_NSH_READLINE instead (the two options are mutually exclusive, right?), the board does *not* get a DHCP lease and I can't locate it on the network, let alone try to telnet to it. I'm single-stepping through the NSH initialization to see where things are taking a wrong turn... Nathan On Fri, Feb 10, 2023 at 4:31 PM Gregory Nutt <spudan...@gmail.com> wrote: > > On 2/10/2023 3:19 PM, Nathan Hartman wrote: > > You know what, I think that might be it. I think I did notice that CLE was > > enabled and didn't think about it. Let me look into it... > > Even if that is the case, it is still and error if the escape sequence > from the host appears on the NSH console. It should be completely > consumed by the function cle_getcursor() at line 479 of > apps/system/cle/cle.c > >
