Looks like some kind of conflict with syslog settings in the config (either "default SYSLOG device" or "Use SYSLOG for /dev/console". I've not been using syslog, so probably something I'd tried (i.e. stab in the dark!) for some reason in the past that was benign in 10.2 and not in 10.4.
Working again on Minicom with either readline or CLE. Back to development now...until 11.0 comes along and I go through it all again lol. >-----Original Message----- >From: TimH <t...@jti.uk.com> >Sent: 18 August 2022 10:59 >To: dev@nuttx.apache.org >Subject: RE: 10.3 merge issues > >>-----Original Message----- >>From: Gregory Nutt <spudan...@gmail.com> >>Sent: 17 August 2022 19:16 >>To: dev@nuttx.apache.org >>Subject: Re: 10.3 merge issues >> >> >>> >>> It all boots and I get the nsh prompt but I get continuous: >>> >>> nsh_session: cle failed: 22 >>> >>> I'm assuming that's EINVAL, but I can't work out why? >>> >>> >> >>What kind of terminal do you use? CLE only works with a >>VT100-compatible terminal and will return -EINVAL to nsh_session if the >>terminal does not respond correctly to a VT100 request for the current >cursor position. >> >[Tim] Vt102 on Minicom. Putty behaves the same. > >If I disable CLE and use the basic readline console I get a different error >and it >hangs: > >NuttShell (NSH) NuttX-10.3.0 >nsh> nsh: nsh_session: readline failed: 0 > >Undoubtedly some conflict in my .config from a change between 10.2 and 10.3 >but seems a pretty basic thing to have been changed/broken? Any >suggestions very welcome!
