Hi @FelipeMdeO !
Adding to what @eren-terzioglu said: SPI is a full-duplex bus, so it's expected that the first exchange receives all zeros from the slave device (even running the tx/rx copy exa...
### Description / Steps to reproduce the issue
Issue present in Master branch.
1 - Connect 2 devices, one as master and other as slave - I followed comments in this PR.
2 - Run simple example ...
[**\[Experimental Bot, please feedback here\]**](https://github.com/search?q=repo%3Aapache%2Fnuttx+13552&type=issues)
The provided PR description does not meet all of the NuttX requirements. Her...
[**\[Experimental Bot, please feedback here\]**](https://github.com/search?q=repo%3Aapache%2Fnuttx+13552&type=issues)
The PR summary is missing some key information:
* **What functional part of...
@xiaoxiang781216 @lupyuen what are these errors:
```
Cmake in present: nucleo-f722ze/cansock,CONFIG_ARM_TOOLCHAIN_CLANG
Configuration/Tool: nucleo-f722ze/cansock,CONFIG_ARM_TOOLCHAIN_CLANG
20...
[**\[Experimental Bot, please feedback here\]**](https://github.com/search?q=repo%3Aapache%2Fnuttx+13552&type=issues)
__Fill In The Commit Message:__ This PR contains a Commit with an Empty Commit...
## Summary
Blocking while running a signal handler is not advisable, instead write the log string character by character.
There is also a potential for a deadlock, as discussed in #6618
No...
use 33-bit (+/-4GB) pc-relative addressing to load the address of arm64_fatal_handle
## Summary
*Update this section with information on why change is necessary,
what it exactly does and ho...
## Summary
The comment about the CPU index remaining stable is incorrect. There is no guarantee the task does not yield during the exit process, meaning the CPU can most definitely change. Also,...
[**\[Experimental Bot, please feedback here\]**](https://github.com/search?q=repo%3Aapache%2Fnuttx+13552&type=issues)
This PR does not meet the NuttX requirements. Here's why:
* **Insufficient ...
[**\[Experimental Bot, please feedback here\]**](https://github.com/search?q=repo%3Aapache%2Fnuttx+13552&type=issues)
The provided PR information is **incomplete** and **does not meet the NuttX ...
This PR exceeds the recommended size of 1000 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size.
This PR exceeds the recommended size of 1000 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size.
[**\[Experimental Bot, please feedback here\]**](https://github.com/search?q=repo%3Aapache%2Fnuttx+13552&type=issues)
The PR summary is missing some key information:
* **What functional part of...
This PR exceeds the recommended size of 1000 lines. Please make sure you are NOT addressing multiple issues with one PR. Note this PR might be rejected due to its size.
## Summary
Currently up_ndelay & up_udelay are completely broken; they always sleep very long time (at least to the end of currently ongoing tick), due to the current time is obtained from "on...
Steps to reproduce:
Enable:
CONFIG_DEBUG_FEATURES=y
CONFIG_DEBUG_SCHED_INFO=y
tools/configure.sh rv-virt:ksmp64
Start qemu and run ostest.
It will get stuck in one of the signal handler tes...
*Note: Please adhere to [Contributing Guidelines](https://github.com/apache/nuttx/blob/master/CONTRIBUTING.md).*
## Summary
There is a feature which to pre message with same can_id reordering. ...
This is not an issue of ESP32-S3, but for NuttX. Did you test with `kconfiglib` [too](https://nuttx.apache.org/docs/latest/quickstart/install.html#kconfig-frontend)?
How did the CI test on MacOS?
LF to CRLF has been converted in syslog framework
*Note: Please adhere to [Contributing Guidelines](https://github.com/apache/nuttx/blob/master/CONTRIBUTING.md).*
## Summary
rm LF to CRLF co...
> > @jasonbu
> > please try the same on releases/12.7 branch
> > Thanks Alin
>
> it means you can confirm in your environment, the releases/12.7 can still re-produce the problem? if you can pr...
### Description / Steps to reproduce the issue
There is a serious issue with the current asynchronous signal delivery system; it will forcibly make another CPU resume
code at places where this mu...