On Sat, Jan 25, 2025 at 1:01 AM Matteo Golin wrote:
> We managed to boot into NSH later this afternoon! Thanks again for the help!
> (..)
> Thanks again for the help! I'll likely email here again later to show our
> flight computer once we confirm we can talk to the sensors and GPS.
Congratz Matt
Hello Alan,
We managed to boot into NSH later this afternoon! Thanks again for the help!
It appears after some grep searching that `board_autoled_on(LED_STARTED)`
is never called by any architecture startup code. Most boards seem to turn
on the start LED in the initialize function themselves. But
On Wed, Jan 15, 2025 at 11:40 PM Tomek CEDRO wrote:
> Google Summer of Code 2025 is coming, we already can and should
> register ideas for NuttX :-)
> https://community.apache.org/gsoc/
Kind reminder that the Google Summer of Code 2025 is coming :-)
Please read rules at https://community.apache.
Hi Matteo,
Nice to know you are doing processes!
The diagnostic LEDs (CONFIG_ARCH_LEDS) is also "very board specific", the
Documentation highlights it here:
https://nuttx.apache.org/docs/latest/reference/os/led.html
Also, the board_autoled_on/off depends on how your LED is physically
connected o
Thank you Alan, looking forward to continuing to contribute to this amazing
project!
Matteo
On Fri, Jan 24, 2025 at 10:25 AM Alan C. Assis wrote:
> Hi Matteo,
>
> Congratulations for achieving it! I just posted about it on LinkedIn too!
>
> We are grateful for all you have done for NuttX too! T
Hello,
I've been able to get our board to boot with the help of this video on the
NuttX channel. At least, we can see LEDs. However I only get noise on the
USART console right now, so I am going to try running off of the HSI
instead of the HSE and see if anything changes. I think the shell is ther
Neo,
Thanks for the explanation - I've modified my gdbstub to inspect xPSR
and if STKALIGN is set then "unalign" the stack pointer. With this
change I'm able to inspect threads and unwind callstacks from the
captured Nuttx-12.6 crash dumps.
I'll look at creating a patch to threads.py to hand
Trying again with the screenshot in text of what's going on.
> It happens that NuttX release 12.6.0 generates code that has SP not
aligned to 4 bytes as shown below, right before triggering SVC.
```
│ 170 /* SVC with SYS_ call number and two parameters */ │
│ 171 │
│ 172 static inline uintptr_t
It turns out the issue comes from the wrong SP register value getting
restored by python script.
TLDR, If you happen to met that GDB cannot unwind correctly, try set
$sp=$sp+4
The issue is that when an exception happened, armv7-m could push 4 bytes to
stack, to make sure SP is 8bytes aligned.
Se
Hi,
I'm implementing the CAN statistics in Nuttx but I have some doubts about
where to increase the drop counter. The data that is not accepted by the
application is handled in the `can_datahandler` function. As the function
documentation says, this function may be called either from the data
rece
Hi Matteo,
Congratulations for achieving it! I just posted about it on LinkedIn too!
We are grateful for all you have done for NuttX too! The Raspberry Pi 4
port for example will open new possibilities for NuttX!
BR,
Alan
On Fri, Jan 24, 2025 at 12:00 AM Matteo Golin
wrote:
> Hello everyone,
11 matches
Mail list logo
