On 1/23/25 21:27, 徐兴良 wrote:
Hi Peter,
The error message reported in version 12.8.0 means that macro
`CONFIG_NFILE_DESCRIPTORS_PER_BLOCK` is failed to parse. It may due to
insufficient debug level(`-g3`). But it won't affect other commands
like `info threads` etc.
> Looking further, I g
Yep, The doc has already been updated. :-)
On 1/24/25 12:05, Tomek CEDRO wrote:
On Fri, Jan 24, 2025 at 5:00 AM Andy Gao wrote:
The GDB plugin should work as you mentioned in you terminal output 🙂.
But the way `source` the python plugin has changed as well.
Looks like documentation for master
On Fri, Jan 24, 2025 at 5:00 AM Andy Gao wrote:
> The GDB plugin should work as you mentioned in you terminal output 🙂.
> But the way `source` the python plugin has changed as well.
Looks like documentation for master and NuttX 12.8 is okay and needs no update?
https://nuttx.apache.org/docs/12.8
Hi Peter,
I've just tested with the GDB python plugin shipped with 12.6.0 release.
What I got seems like the same error what you've got:
```
(gdb) i threads
Id Thread Info Frame
*0 Thread 0x20001688 (Name: Idle_Task, State: Running, Priority:
0, Stack: 1008) 0xab
On Fri, Jan 24, 2025 at 4:18 AM Matteo Golin wrote:
> Thanks Tomek!
> Also it appears I posted the wrong link to the design files and instead put
> the Telemetrum page. Here they are: https://github.com/linguini1/pygmy
Yup :D Nice stuff congratz!! :-)
I was playing with some space tech at univer
Thanks Tomek!
Also it appears I posted the wrong link to the design files and instead put
the Telemetrum page. Here they are: https://github.com/linguini1/pygmy
On Thu, Jan 23, 2025, 10:04 PM Tomek CEDRO wrote:
> On Fri, Jan 24, 2025 at 4:00 AM Matteo Golin
> wrote:
> > Hello everyone,
> > I j
On Fri, Jan 24, 2025 at 4:00 AM Matteo Golin wrote:
> Hello everyone,
> I just wanted to share that I have finished developing a flight computer for
> my L1 rocket, which I have designed from scratch with the intent of running
> NuttX (right down to the LED status indicators).
Thank You Matteo
Hello everyone,
I just wanted to share that I have finished developing a flight computer for my
L1 rocket, which I have designed from
scratch with the intent of running NuttX (right down to the LED status
indicators). This is distinct from the InSpace
flight computer designed this year that I ha
Hi Peter,
The error message reported in version 12.8.0 means that macro
`CONFIG_NFILE_DESCRIPTORS_PER_BLOCK` is failed to parse. It may due to
insufficient debug level(`-g3`). But it won't affect other commands like `info
threads` etc.
> Looking further, I got the GDB command args wrong for
On Fri, Jan 24, 2025 at 2:23 AM Peter Barada wrote:
> Looking further, I got the GDB command args wrong for version for 12.8 (12.8
> calls for gdbinit.py, not __init__.py), here's updated 12.8 output (which
> allows looking at threads and nsh_main callstack, but generates warnings on
> start):
On 1/23/25 19:20, Tomek CEDRO wrote:
Hey there Peter :-)
Are you sure this is not a bug in gdb?
If not, then this is called thread aware debug and probably gdb
changed some api or invocation parameters if that still works in older
versions. Maybe simple update to tools/gdb/__init__.py will do
Hey there Peter :-)
Are you sure this is not a bug in gdb?
If not, then this is called thread aware debug and probably gdb
changed some api or invocation parameters if that still works in older
versions. Maybe simple update to tools/gdb/__init__.py will do the
job?
--
CeDeROM, SQ7MHZ, http://ww
I'm coming up to speed in Nuttx over the past few months, and I've run
into an issue where gdb can't show the call stack for a thread in
version 12.6.0, but can in version 12.5.1 (and can't show threads in
version 12.8.0):
I followed the instructions at
https://nuttx.apache.org/docs/12.6.0/gu
Hi Matesz,
Yes, LWL is slow because it is working using a polling approach (AFAIK ARM
DAP has support for interruption, but it is not implemented yet).
The main purpose of the LWL is to be the initial console before the real
serial driver is not implemented yet.
I think J-Link is a nice tool and
> To be honest I didn't hear about this LWL (Lightweight Link) before,
what a great discovery, nsh directly over JTAG/SWD with no UART!!
Thank you Alan!! :-)
There is also RTT console support in NuttX, so you can use JLink debuggers
without any UART.
Also there are more powerful tools for Segger d
15 matches
Mail list logo
