Please follow these steps:
https://nuttx.apache.org/community/
On Fri, Feb 7, 2025 at 3:25 AM Daniel Byshkin wrote:
> Empty Message
>
Hi Tomek,
Try to compile using "make -j" it will reduce the time from minutes to
seconds (but will consume more power).
BR,
Alan
On Thu, Feb 6, 2025 at 10:54 PM Tomek CEDRO wrote:
> On Thu, Feb 6, 2025 at 7:30 PM Alan C. Assis wrote:
> > Something to keep in mind about this distributed (buil
Hi!
I didn't say that `citest` should test "everything": of course, peripherals
can't be tested (at least most of them), but it's the most basic test for
every architecture/chip/board because it can run `ostest` and other test
applications (`smp`, for instance). IMHO, it's the most important test
Support for peripherals in QEMU is very limited, and some peripherals
supported by QEMU are not available in new hardware. So the same
tests for qemu and real HW are just not possible for some targets.
Also configurations with all peripherals/features enabled are not possible
for many chips - we a
Hi!
citest config: I suggest to keep citest and hardware test absolutely
> separate. You want to be able to change one and not the other. Not the
> same components will be tested.
CI tests *include* HW testing...
For now, we have the `citest` defconfig for some boards and they are
intended to
On 2025-02-06 16:02:18, Matteo Golin wrote:
> I've got:
> - Raspberry Pi Pico
> - Raspberry Pi Pico W
> - XIAO RP2040
> - XIAO SAMD21
> - Raspberry Pi 4B
>
> And would also be willing to help test, provided it's easy enough for me to
> automate.
Just looked into my lost and forgotten drawer. As of
Hi,
a bit of a summary of the 10 previous messages
NDTS: NuttX Distributed Test System
NDHT: NuttX Distributed Hardware Test
nuttx-hwtest as we already have nuttx-apps
It's not original, I know lol
citest config: I suggest to keep citest and hardware test absolutely
separate. You want to b
