Add g_ prefix to fs file_operations and mountpt_operations

>From https://nuttx.apache.org/docs/latest/contributing/coding_style.html: - Global variable prefix. All global variables begin with the prefix g_ to indicate the scope of variable. Most global variables follow this guide except a few subsystem, which is fixed here: https://github.com/

Re: Add g_ prefix to fs file_operations and mountpt_operations

On 4/24/23, Xiang Xiao wrote: > From https://nuttx.apache.org/docs/latest/contributing/coding_style.html: > > >- > >Global variable prefix. All global variables begin with the prefix g_ to >indicate the scope of variable. > > Most global variables follow this guide except a few subsyst

Re: NuttX PTP Support

Could be relevant to this thread: https://github.com/apache/nuttx/pull/9084 On 1/30/23, Alan C. Assis wrote: > Hi James, > > Yes, Espressif is doing a good work adding support to it. > > I hope in the future others silicon vendors start to contribute as > well (hello ST, Microchip, Renesas, ...)

Re: Add g_ prefix to fs file_operations and mountpt_operations

On 4/24/2023 6:57 AM, Xiang Xiao wrote: From https://nuttx.apache.org/docs/latest/contributing/coding_style.html: - Global variable prefix. All global variables begin with the prefix g_ to indicate the scope of variable. Most global variables follow this guide except a few subsys

Re: Telnet broken?

I am having some trouble understanding how NSH_TELNET is supposed to work in NuttX now. It used to work for me on real hardware. I saw that some people had problems because of not synchronized nuttx and apps repos, because some PRs were merged at different times. My nuttx and apps are both based o

Re: Telnet broken?

Hi Nathan, Yes, same happens to duktape prompt: $ ./nuttx login: admin password: User Logged-in! nsh> duk ((o) Duktape 2.5.0 (v2.5.0) duk> hheellpp ReferenceError: identifier 'help' undefined at [anon] (duktape/src-noline/duktape.c:83732) internal at global (input:1) preventsyield duk>

Re: Telnet broken?

$ ./nuttx login: admin password: User Logged-in! nsh> duk ((o) Duktape 2.5.0 (v2.5.0) duk> hheellpp Note that only the characters sent from the remote peer and echoed by the driver are corrupted. ReferenceError: identifier 'help' undefined at [anon] (duktape/src-noline/duktape.c:83732) i

Re: Telnet broken?

On Mon, Apr 24, 2023 at 2:06 PM Gregory Nutt wrote: > > > > $ ./nuttx > > login: admin > > password: > > User Logged-in! > > nsh> duk > > ((o) Duktape 2.5.0 (v2.5.0) > > duk> hheellpp > Note that only the characters sent from the remote peer and echoed by > the driver are corrupted. > > ReferenceE

Re: Telnet broken?

Including the doubling of characters and momentary display of some characters which seem to change rapidly? That probably comes from NSH.  I think it still sends an escape sequence to clear to the end of the line.  So any additional garbage at the end after the first four characters would o

Re: Telnet broken?

On Mon, Apr 24, 2023 at 4:54 PM Gregory Nutt wrote: > > > Including the doubling of characters and momentary display of some > > characters which seem to change rapidly? > > That probably comes from NSH. I think it still sends an escape sequence > to clear to the end of the line. So any additio

Debugging userspace with Nuttx protected build

Are there any examples of a gdb setup to debug a userspace process? One key issue is to setup the section offsets to match the final application location once it has been loaded. I was actually quite surprised that Nuttx applications are still partially linked with a protected build and that all s

Re: NuttX PTP Support

i’ll take a look at it as soon as I get some free time ; I have a working, GPS master clock. On Mon, Apr 24, 2023 at 6:45 AM Alan C. Assis wrote: > Could be relevant to this thread: > https://github.com/apache/nuttx/pull/9084 > > On 1/30/23, Alan C. Assis wrote: > > Hi James, > > > > Yes, Espre

Re: Debugging userspace with Nuttx protected build

On 4/24/2023 7:27 PM, Andrew Dennison wrote: Are there any examples of a gdb setup to debug a userspace process? One key issue is to setup the section offsets to match the final application location once it has been loaded. You don't describe your build, so I only give you a general answer.