RE: 10.3 merge issues
>-Original Message- >From: Nathan Hartman >Sent: 18 August 2022 03:01 >To: dev@nuttx.apache.org >Subject: Re: 10.3 merge issues > >On Wed, Aug 17, 2022 at 3:27 PM Tim Hardisty wrote: > >> I realise, now, I compared mine against 10.2 variants not 10.3...not >> sure why, but there you go. I'll give that a try tomorrow - thanks! > > >Sure thing! Let us know if that fixes it. I'm pretty sure that change in your >board's Make.defs (and there might be a couple of others, that's why I >suggest to compare it to the up-to-date Make.defs of the board you cloned) >should fix the compile issues... > [Tim]Don't know why I compared against previous make.defs examples - silly me! Using the revised syntax it now works - thanks :)
RE: 10.3 merge issues
>-Original Message- >From: Gregory Nutt >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!
RE: 10.3 merge issues
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 >Sent: 18 August 2022 10:59 >To: dev@nuttx.apache.org >Subject: RE: 10.3 merge issues > >>-Original Message- >>From: Gregory Nutt >>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!
Re: Quectel BG770A support on NuttX
Hi Bill, Thank Bill, I will follow more info for you. Sure, I think this time you could contribute back to mainline :-) BR, Alan On 8/18/22, Bill Rees wrote: > > > > Hi Alan, > > > >I am interested in this work. > > > >I am an embedded engineer and have worked with nuttx for several > years porting to a couple of nordic mcus . > > > >At zGlue I was heavily involved porting nimBLE to nuttx, precision > ring gyros, and more mundane sensors. > > > >None of the code made it out of legal review so no opportunity to > upstream arose > > > > Bill Rees > > > > > > > > > > > > >> >> On Aug 17, 2022 at 1:03 PM, > (mailto:acas...@gmail.com)> wrote: >> >> >> >> Hi Everyone, By the chance, did you know if someone already added support >> to this modem on NuttX? A friend of mine from a USA company is willing to >> use this modem and they are interested to contract someone from community >> to do the port, case this modem is not support yet. At the end of the day >> this support will be integrated back to NuttX mainline. So, if you are >> interested to work on that, please let me know. BR, Alan >> >> > > >
Re: 10.3 merge issues
On Thu, Aug 18, 2022 at 6:40 AM TimH wrote: > 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. Well, if you ever figure out what it was, let us know!! Could be some kind of regression that should be fixed. Glad those two issues were straightened out. Cheers, Nathan
