You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nuttx.apache.org by Nathan Hartman <ha...@gmail.com> on 2022/10/26 01:55:58 UTC
[DISCUSS] NuttX graduation: Draft Resolution
Dear NuttX community,
As our community VOTE [1] for graduation to Top Level Project has
PASSED [2], the next steps are:
(1) Draft our Charter/Resolution
(2) Decide members of the initial Project Management Committee (PMC)
(3) Choose the 1st Vice President of the proposed Apache NuttX PMC
Please participate so we can get this done efficiently!
Regarding item #1, below please find a 1st Draft Resolution for review
and discussion -- this draft was generated by Whimsy (there's a button
at the bottom of our podling page [3] to draft the resolution). Please
read it anyway and provide feedback!!!
Regarding item #2, currently the draft resolution lists all members of
the Apache NuttX (Incubating) PPMC to become members of the proposed
Apache NuttX PMC. If anyone feels there should be changes, please let
us know.
Regarding item #3, the draft resolution has [!! INSERT NAME HERE !!]
where the name of the proposed Vice President should be written. We
need to decide who that will be. The Vice President reports to the
board 4 times each year, similarly to how we have been reporting to
the Incubator PMC (IPMC), but there are no mentors who need to sign
off on it. Speak up if you're interested in being the Vice President
of Apache NuttX!
1st draft of our Resolution:
[[[
Establish the Apache NuttX Project
WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to
establish a Project Management Committee charged with the creation and
maintenance of open-source software, for distribution at no charge to
the public, related to a mature, real-time embedded operating system
(RTOS).
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache NuttX Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache NuttX Project be and hereby is responsible
for the creation and maintenance of software related to a mature, real-
time embedded operating system (RTOS); and be it further
RESOLVED, that the office of "Vice President, Apache NuttX" be and
hereby is created, the person holding such office to serve at the
direction of the Board of Directors as the chair of the Apache NuttX
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache NuttX
Project; and be it further
RESOLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache NuttX Project:
* Abdelatif Guettouche <ag...@apache.org>
* Alan Carvalho de Assis <ac...@apache.org>
* Alin Jerpelea <je...@apache.org>
* Anthony Merlino <an...@apache.org>
* Brennan Ashton <bt...@apache.org>
* David Sidrane <da...@apache.org>
* Duo Zhang <zh...@apache.org>
* Flavio Paiva Junqueira <fp...@apache.org>
* Gregory Nutt <gn...@apache.org>
* Gustavo Henrique Nihei <gu...@apache.org>
* Junping Du <ju...@apache.org>
* Justin Mclean <jm...@apache.org>
* Lup Yuen Lee <lu...@apache.org>
* Masayuki Ishikawa <ma...@apache.org>
* Mohammad Asif Siddiqui <as...@apache.org>
* Nathan Hartman <ha...@apache.org>
* Sara Monteiro <sa...@apache.org>
* Xiang Xiao <xi...@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that [!! INSERT NAME HERE !!]
be appointed to the office of Vice President, Apache NuttX, to serve in
accordance with and subject to the direction of the Board of Directors
and the Bylaws of the Foundation until death, resignation, retirement,
removal or disqualification, or until a successor is appointed; and be
it further
RESOLVED, that the Apache NuttX Project be and hereby is tasked with
the migration and rationalization of the Apache Incubator NuttX
podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache Incubator
NuttX podling encumbered upon the Apache Incubator PMC are hereafter
discharged.
]]]
References:
[1] https://lists.apache.org/thread/r1tn6qstkqmhh52szy4j2bgnnydbjmx4
[2] https://lists.apache.org/thread/ss1dqyh8b80zlkq42cp5so4qth7z08q2
[3] https://whimsy.apache.org/roster/ppmc/nuttx
[4] https://incubator.apache.org/guides/graduation.html
Thanks to everyone!
Cheers,
Nathan
Re: Dev-Board for Nuttx
Posted by Sebastien Lorquet <se...@lorquet.fr>.
Hi,
-The external wifi antenna is the best option. I also agree that wired
ethernet is essential and preferred in an industrial application. So
thats fine.
-SD cards are very unreliable and to achieve their goal (be usable on
desktop computers), they have to use FAT filesystems, which are
EXTREMELY NOT reliable in case of surprise power loss, which is an
unavoidable design constraint in an embedded system, so I disagree with
you on the choice of a SD card, because this does not match the level of
reliability you seem to intend with the rest of this board (which is
really well done).
ISSI now has some large fast and available flash chips with 4KB erase
blocks.
Which are VERY RELIABLE and very well managed by LittleFS regarding to
wear leveling, with atomic/or replayable filesystem operations. I insist
a lot, mass storage reliability in embedded devices is CRITICAL and very
OVERLOOKED. I am a smart card engineer, and we constantly have to deal
with half-erased data bits, undefined and unstable bits that can change
every time you read them, duration and energy required for correct page
erases, etc. So even if a "normal" embedded system does not need to deal
with this, at least a reliable flash storage is a must, IMHO. With a
large cap on the power rail to finish the current write, and ideally a
powerok GPIO to disable further flash writes in case of power failure.
I could understand that reliable storage is not in your scope, but the
rest of the board seems to be reliable, so thats a surprise. A broken
out SPI+power and a few /CS lines from the ESP32 could be a solution on
a crowded board, so that spi flash storage can be added as an optional
daugter board.
Yes, this board would be cool to test. Times having changed, we could
even use that kind of esp32+rp2040 system in future products.
Sebastien
Le 26/10/2022 à 11:39, michael.schmid@mdc-service.de a écrit :
> Hello Sebastian,
>
> thanks for your interest! About the Wifi antenna: The used
> ESP32-WROVER-I has the wifi signal connected to the uFL connector by
> default, the PCB antenna would request to solder a 0 Ohm resistor, to
> use it. Because of the space limitations, we drop the idea to use the
> PCB antenna. In our use cases, the EsPiFF is build into a metal
> enclosure, what makes the useage of an PCB antenna impossible. As the
> EsPiFF is optimized for high availability applications, the wired
> Ethernet also prefered over Wifi. Because the PCB antenna is not used,
> the placement close to the IO header is no problem.
>
> It would be great, if there where smaller ESP32 modules, with 16 MB of
> flash and 8 MB of PSRAM available. But unfortunatly, the smaller ESP32
> modules does not have 8 MB PSRAM, and we see this as a killer feature
> of the ESP32.
>
> About data logging: There is the SDcard socket, and this is the
> prefered way for data logging. Otherwise, the 16MB flash on the ESP32
> could be used as well, but frequent writing on the flash limit its
> live time. Nuttx have special flash files systems, to minimize this
> problem, but with the SDcard available, I would prefer this. Finally,
> all pins from the 40 pol header go to he RP2040, so a RasPi HAT can
> add any functionality.
>
> About FRAM: the initial idea was, to mount the FRAM into the malloc()
> address range, as a fast non-volatile memory. After a power cut, a
> program could continue where it was stopping before. The FRAM is byte
> adressable, and with 20MHz not so slow. Footprint and protocol
> compatible FRAMs are offered in various sizes, up to 256 kBytes. If
> needed, we could offer a version with more FRAM, what would then cost
> a little more. By also having the SDcard, what size for the FRAM would
> you choose?
>
> We will make a board revsion with JTAG headers. I will update you as
> soon as we have it.
>
> regards,
> Michael
>
> Am 2022-10-26 10:44, schrieb Sebastien Lorquet:
>> Hi,
>>
>> A devboard with no jtag makes no sense for me! When you have a hw
>> revision with both the esp32 and the rp2040 debug ports broken out on
>> HE10-1.27mm headers (or pads if space is tight), I'm interested to get
>> one :)
>>
>> The internal wifi antenna close to the IO header metal pins is also
>> not RF-optimal. Your version 2 was better on this aspect.
>>
>> Also another suggestion, a large user flash available on esp32 or
>> rp2040 spi gpios would be very useful for data logging and storage.
>> Using the esp32 code flash for this is not the best design. The 2KB
>> fram is good for parameter storage but is quite limited, no useful FS
>> can be mounted on it.
>>
>> Best regards,
>>
>> Sébastien
>>
>> Le 26/10/2022 à 08:57, michael.schmid@mdc-service.de a écrit :
>>> Dear Nuttx developers,
>>>
>>> we have developed the EsPiff (ESP32+RP2040 on the Raspberry Pi Form
>>> Factor), a open source board to replace RasPi's and there clones,
>>> where the high processing power and/or Linux is not needed, but
>>> stability and the reuse of RasPi HATs are required.
>>>
>>> The github home is https://github.com/MDCservice/EsPiFF
>>>
>>> We will also offer the EsPiFF on CrowdSupply
>>> https://www.crowdsupply.com/mdc-service-wittenburg-gmbh/espiff
>>>
>>> We would like to send a few boards for free to Nuttx developers, to
>>> improve Nuttx compatibility. Would there be interest?
>>>
>>> A high level summary about the EsPiFF:
>>> An ESP32-WROVER-I module with 16 MB Flash, 8 MB PSRAM is taking care
>>> - wired Ethernet via a IP101 PHY,
>>> - Wifi (need an external Wifi Antenna with uFL connector),
>>> - 3 serial UARTs,
>>> - one the 3 serial UARTs is used for programming via a CH340
>>> USB-UART chip, what can be enabled/disabled with jumpers,
>>> - I2C port expander PCA 9557 for some chip select signals and 3 user
>>> LEDs,
>>> - SDcard in SPI mode,
>>> - external real time clock, with supervisior,
>>> - 2kB FRAM,
>>> - USB Type-C connector for up to 5V/3A, connected to the CH340
>>> USB-UART to program the ESP32
>>>
>>> An RP2040 (Pi Pico) what takes care the 40 pin RasPi header,
>>> - connected to the ESP32 via SPI,
>>> - UAB-A connector, also used to program the RP2040 (need to hold the
>>> boot button while power the board).
>>>
>>> In earlier versions, we had the LAN8720 PHY, but as others (Olimex,
>>> wESP) we also got problems and replaced it with the IP101 since v3.1.
>>>
>>> Currently, there is no HW debugging broken out on the board. But we
>>> could add a JTAG header on the bottom side, with TDO, TDI, TCK, TMS,
>>> GND, 3V3 in the next board production run. The ESP32 has the JTAG
>>> pins on GPIO12, 13, 14, 15, what are used for SPI on the EsPiFF, so
>>> code using the SPI could not be debugged while JTAG is using the
>>> pins. Would it still make sense to build in the JTAG header?
>>>
>>> Would be glad to get your feedback,
>>> Michael
>
Re: Dev-Board for Nuttx
Posted by mi...@mdc-service.de.
Hello Sebastian,
thanks for your interest! About the Wifi antenna: The used
ESP32-WROVER-I has the wifi signal connected to the uFL connector by
default, the PCB antenna would request to solder a 0 Ohm resistor, to
use it. Because of the space limitations, we drop the idea to use the
PCB antenna. In our use cases, the EsPiFF is build into a metal
enclosure, what makes the useage of an PCB antenna impossible. As the
EsPiFF is optimized for high availability applications, the wired
Ethernet also prefered over Wifi. Because the PCB antenna is not used,
the placement close to the IO header is no problem.
It would be great, if there where smaller ESP32 modules, with 16 MB of
flash and 8 MB of PSRAM available. But unfortunatly, the smaller ESP32
modules does not have 8 MB PSRAM, and we see this as a killer feature of
the ESP32.
About data logging: There is the SDcard socket, and this is the prefered
way for data logging. Otherwise, the 16MB flash on the ESP32 could be
used as well, but frequent writing on the flash limit its live time.
Nuttx have special flash files systems, to minimize this problem, but
with the SDcard available, I would prefer this. Finally, all pins from
the 40 pol header go to he RP2040, so a RasPi HAT can add any
functionality.
About FRAM: the initial idea was, to mount the FRAM into the malloc()
address range, as a fast non-volatile memory. After a power cut, a
program could continue where it was stopping before. The FRAM is byte
adressable, and with 20MHz not so slow. Footprint and protocol
compatible FRAMs are offered in various sizes, up to 256 kBytes. If
needed, we could offer a version with more FRAM, what would then cost a
little more. By also having the SDcard, what size for the FRAM would you
choose?
We will make a board revsion with JTAG headers. I will update you as
soon as we have it.
regards,
Michael
Am 2022-10-26 10:44, schrieb Sebastien Lorquet:
> Hi,
>
> A devboard with no jtag makes no sense for me! When you have a hw
> revision with both the esp32 and the rp2040 debug ports broken out on
> HE10-1.27mm headers (or pads if space is tight), I'm interested to get
> one :)
>
> The internal wifi antenna close to the IO header metal pins is also
> not RF-optimal. Your version 2 was better on this aspect.
>
> Also another suggestion, a large user flash available on esp32 or
> rp2040 spi gpios would be very useful for data logging and storage.
> Using the esp32 code flash for this is not the best design. The 2KB
> fram is good for parameter storage but is quite limited, no useful FS
> can be mounted on it.
>
> Best regards,
>
> Sébastien
>
> Le 26/10/2022 à 08:57, michael.schmid@mdc-service.de a écrit :
>> Dear Nuttx developers,
>>
>> we have developed the EsPiff (ESP32+RP2040 on the Raspberry Pi Form
>> Factor), a open source board to replace RasPi's and there clones,
>> where the high processing power and/or Linux is not needed, but
>> stability and the reuse of RasPi HATs are required.
>>
>> The github home is https://github.com/MDCservice/EsPiFF
>>
>> We will also offer the EsPiFF on CrowdSupply
>> https://www.crowdsupply.com/mdc-service-wittenburg-gmbh/espiff
>>
>> We would like to send a few boards for free to Nuttx developers, to
>> improve Nuttx compatibility. Would there be interest?
>>
>> A high level summary about the EsPiFF:
>> An ESP32-WROVER-I module with 16 MB Flash, 8 MB PSRAM is taking care
>> - wired Ethernet via a IP101 PHY,
>> - Wifi (need an external Wifi Antenna with uFL connector),
>> - 3 serial UARTs,
>> - one the 3 serial UARTs is used for programming via a CH340 USB-UART
>> chip, what can be enabled/disabled with jumpers,
>> - I2C port expander PCA 9557 for some chip select signals and 3 user
>> LEDs,
>> - SDcard in SPI mode,
>> - external real time clock, with supervisior,
>> - 2kB FRAM,
>> - USB Type-C connector for up to 5V/3A, connected to the CH340
>> USB-UART to program the ESP32
>>
>> An RP2040 (Pi Pico) what takes care the 40 pin RasPi header,
>> - connected to the ESP32 via SPI,
>> - UAB-A connector, also used to program the RP2040 (need to hold the
>> boot button while power the board).
>>
>> In earlier versions, we had the LAN8720 PHY, but as others (Olimex,
>> wESP) we also got problems and replaced it with the IP101 since v3.1.
>>
>> Currently, there is no HW debugging broken out on the board. But we
>> could add a JTAG header on the bottom side, with TDO, TDI, TCK, TMS,
>> GND, 3V3 in the next board production run. The ESP32 has the JTAG pins
>> on GPIO12, 13, 14, 15, what are used for SPI on the EsPiFF, so code
>> using the SPI could not be debugged while JTAG is using the pins.
>> Would it still make sense to build in the JTAG header?
>>
>> Would be glad to get your feedback,
>> Michael
--
Chief engineer & consultant
MDC-Service Wittenburg GmbH
Bergstiftsgasse 11
09599 Freiberg, Germany
Office Gen. +49 3731 7832310
Fax +49 3731 2442369
Re: Dev-Board for Nuttx
Posted by Sebastien Lorquet <se...@lorquet.fr>.
Hi,
A devboard with no jtag makes no sense for me! When you have a hw
revision with both the esp32 and the rp2040 debug ports broken out on
HE10-1.27mm headers (or pads if space is tight), I'm interested to get
one :)
The internal wifi antenna close to the IO header metal pins is also not
RF-optimal. Your version 2 was better on this aspect.
Also another suggestion, a large user flash available on esp32 or rp2040
spi gpios would be very useful for data logging and storage. Using the
esp32 code flash for this is not the best design. The 2KB fram is good
for parameter storage but is quite limited, no useful FS can be mounted
on it.
Best regards,
Sébastien
Le 26/10/2022 à 08:57, michael.schmid@mdc-service.de a écrit :
> Dear Nuttx developers,
>
> we have developed the EsPiff (ESP32+RP2040 on the Raspberry Pi Form
> Factor), a open source board to replace RasPi's and there clones,
> where the high processing power and/or Linux is not needed, but
> stability and the reuse of RasPi HATs are required.
>
> The github home is https://github.com/MDCservice/EsPiFF
>
> We will also offer the EsPiFF on CrowdSupply
> https://www.crowdsupply.com/mdc-service-wittenburg-gmbh/espiff
>
> We would like to send a few boards for free to Nuttx developers, to
> improve Nuttx compatibility. Would there be interest?
>
> A high level summary about the EsPiFF:
> An ESP32-WROVER-I module with 16 MB Flash, 8 MB PSRAM is taking care
> - wired Ethernet via a IP101 PHY,
> - Wifi (need an external Wifi Antenna with uFL connector),
> - 3 serial UARTs,
> - one the 3 serial UARTs is used for programming via a CH340 USB-UART
> chip, what can be enabled/disabled with jumpers,
> - I2C port expander PCA 9557 for some chip select signals and 3 user
> LEDs,
> - SDcard in SPI mode,
> - external real time clock, with supervisior,
> - 2kB FRAM,
> - USB Type-C connector for up to 5V/3A, connected to the CH340
> USB-UART to program the ESP32
>
> An RP2040 (Pi Pico) what takes care the 40 pin RasPi header,
> - connected to the ESP32 via SPI,
> - UAB-A connector, also used to program the RP2040 (need to hold the
> boot button while power the board).
>
> In earlier versions, we had the LAN8720 PHY, but as others (Olimex,
> wESP) we also got problems and replaced it with the IP101 since v3.1.
>
> Currently, there is no HW debugging broken out on the board. But we
> could add a JTAG header on the bottom side, with TDO, TDI, TCK, TMS,
> GND, 3V3 in the next board production run. The ESP32 has the JTAG pins
> on GPIO12, 13, 14, 15, what are used for SPI on the EsPiFF, so code
> using the SPI could not be debugged while JTAG is using the pins.
> Would it still make sense to build in the JTAG header?
>
> Would be glad to get your feedback,
> Michael
libpq and libscpi: how to start
Posted by mi...@mdc-service.de.
Dear all,
i would like to see Nuttx support for the PostgreSQL client library
libpq(https://github.com/postgres/postgres/tree/master/src/interfaces/libpq),
and a library for SCPI(https://www.jaybee.cz/scpi-parser/api/). These
scpi parser lib could then be used for USBTMC and LXI, 2 standards to
expose lab instruments in a standardized way to software like LabView,
GNU Octave, ect.
Both projects are under BSD license, so they should be compatible from
the license side with Nuttx.
I think, as common libraries for other app, and maybe service, they
should be placed under nuttxspace/nuttx/libs in the Nuttx tree, not in
the application tree. At least the PostgreSQL client library requires
network. What would be the advice, where to place these kind of
libraries?
For the PostgreSQL client library, there are implementations for
Arudino, additional to the PC based implementations. But because the
POSIX compatibility of Nuttx, starting from the Linux version should
make more sense, or?
regards,
Michael
Re: Dev-Board for Nuttx
Posted by "Alan C. Assis" <ac...@gmail.com>.
Hi Michael,
Yes, this is the way to go!
Actually NuttX already supports loading ELF from SDCard or USB Thumb
Driver (called "pendrive" in some countries).
I created a video demonstrating it, see here:
https://www.youtube.com/watch?v=oL6KAgkTb8M
Also there is a PR in progress that will extend the ELF loading to
enable loading libraries:
https://github.com/apache/incubator-nuttx/pull/7202
About the JTAG, I think it should be nice to have an standard
connector, but of course it uses a lot of space in the board.
BR,
Alan
On 10/26/22, michael.schmid@mdc-service.de
<mi...@mdc-service.de> wrote:
> Hi Alan,
>
> I am really happy to got your interest. Replacing the Pi with an EsPiFF
> with Nuttx is also our intention.
>
> The SWD for the RP2040 is alredy broken out, on J5, pin 6(SWCLK) and pin
> 8 (SWDIO). The connector J5 is a DF11, 2mm spacing connector, we will
> add cables with 2.54 Duponts on the other side. The RP2040 have
> exclusive pins for SWD, so no limit on functionality. Just for the
> ESP32, we need to add the JTAG header. We used that DF11 connector, to
> make these pins accesable from outside, when the EsPiFf is in a
> Raspberry Pi 4 enclosure, what have 2 mini HDMI connectors at this
> position. Other connectors would be too big for the openings for mini
> HDMI.
>
> In the past, I did also STM32 boards, until the chip crisis made most of
> the STM32Fxxx unavailable. This is the big advantage of the ESP32, they
> are always available. I have not yet jumped on the GD32xxx and friends
> as pincompatible? replacement, that could be an way out. But 8 MB RAM on
> a board, means for most MCUs external RAM, whats included with the
> ESP32-WROVER. I am hoping, that (one day) to load ELF binaries from
> SDcard into memory and execute it, as Linux is doing. This will open a
> new chapter in using microcontrollers, and Nuttx is already nearly
> there.
>
> Would be happy to see the EsPiFF one day in your Nuttx Videos!
>
> best regards,
> Michael
>
> Am 2022-10-26 14:56, schrieb Alan C. Assis:
>> Hi Michael,
>>
>> Congratulations! You created a really great board!!!
>>
>> I'm sure that many people here will be interested on it, those who are
>> really interested to contribute.
>>
>> The idea of using RPI form-factor is really good. Actually we were
>> discussing about the idea of creating some RPI-like board to replace
>> high level Linux system with a system running NuttX RTOS.
>>
>> I think adding JTAG for ESP32 and SWD for RP2040 will be very useful,
>> please include it for the final board.
>>
>> A friend of mine created a nice and simple board for NuttX that he
>> released as open-source:
>>
>> https://github.com/lucaszampar/NuttX_STM32F4_RS485_DevBoard
>>
>> He send me some pictures that I put on my flickr:
>>
>> https://live.staticflickr.com/65535/52456145643_97eca8e9b1_o.jpg
>>
>> https://live.staticflickr.com/65535/52455885674_94eba29fcc_b.jpg
>>
>> Soon, he will submit support to mainline.
>>
>> BR,
>>
>> Alan
>>
>> On 10/26/22, michael.schmid@mdc-service.de
>> <mi...@mdc-service.de> wrote:
>>> Dear Nuttx developers,
>>>
>>> we have developed the EsPiff (ESP32+RP2040 on the Raspberry Pi Form
>>> Factor), a open source board to replace RasPi's and there clones,
>>> where
>>> the high processing power and/or Linux is not needed, but stability
>>> and
>>> the reuse of RasPi HATs are required.
>>>
>>> The github home is https://github.com/MDCservice/EsPiFF
>>>
>>> We will also offer the EsPiFF on CrowdSupply
>>> https://www.crowdsupply.com/mdc-service-wittenburg-gmbh/espiff
>>>
>>> We would like to send a few boards for free to Nuttx developers, to
>>> improve Nuttx compatibility. Would there be interest?
>>>
>>> A high level summary about the EsPiFF:
>>> An ESP32-WROVER-I module with 16 MB Flash, 8 MB PSRAM is taking care
>>> - wired Ethernet via a IP101 PHY,
>>> - Wifi (need an external Wifi Antenna with uFL connector),
>>> - 3 serial UARTs,
>>> - one the 3 serial UARTs is used for programming via a CH340 USB-UART
>>> chip, what can be enabled/disabled with jumpers,
>>> - I2C port expander PCA 9557 for some chip select signals and 3 user
>>> LEDs,
>>> - SDcard in SPI mode,
>>> - external real time clock, with supervisior,
>>> - 2kB FRAM,
>>> - USB Type-C connector for up to 5V/3A, connected to the CH340
>>> USB-UART
>>> to program the ESP32
>>>
>>> An RP2040 (Pi Pico) what takes care the 40 pin RasPi header,
>>> - connected to the ESP32 via SPI,
>>> - UAB-A connector, also used to program the RP2040 (need to hold the
>>> boot button while power the board).
>>>
>>> In earlier versions, we had the LAN8720 PHY, but as others (Olimex,
>>> wESP) we also got problems and replaced it with the IP101 since v3.1.
>>>
>>> Currently, there is no HW debugging broken out on the board. But we
>>> could add a JTAG header on the bottom side, with TDO, TDI, TCK, TMS,
>>> GND, 3V3 in the next board production run. The ESP32 has the JTAG pins
>>> on GPIO12, 13, 14, 15, what are used for SPI on the EsPiFF, so code
>>> using the SPI could not be debugged while JTAG is using the pins.
>>> Would
>>> it still make sense to build in the JTAG header?
>>>
>>> Would be glad to get your feedback,
>>> Michael
>>>
>
> --
> Chief engineer & consultant
> MDC-Service Wittenburg GmbH
> Bergstiftsgasse 11
> 09599 Freiberg, Germany
>
> Office Gen. +49 3731 7832310
> Fax +49 3731 2442369
>
Re: Dev-Board for Nuttx
Posted by mi...@mdc-service.de.
Hi Alan,
I am really happy to got your interest. Replacing the Pi with an EsPiFF
with Nuttx is also our intention.
The SWD for the RP2040 is alredy broken out, on J5, pin 6(SWCLK) and pin
8 (SWDIO). The connector J5 is a DF11, 2mm spacing connector, we will
add cables with 2.54 Duponts on the other side. The RP2040 have
exclusive pins for SWD, so no limit on functionality. Just for the
ESP32, we need to add the JTAG header. We used that DF11 connector, to
make these pins accesable from outside, when the EsPiFf is in a
Raspberry Pi 4 enclosure, what have 2 mini HDMI connectors at this
position. Other connectors would be too big for the openings for mini
HDMI.
In the past, I did also STM32 boards, until the chip crisis made most of
the STM32Fxxx unavailable. This is the big advantage of the ESP32, they
are always available. I have not yet jumped on the GD32xxx and friends
as pincompatible? replacement, that could be an way out. But 8 MB RAM on
a board, means for most MCUs external RAM, whats included with the
ESP32-WROVER. I am hoping, that (one day) to load ELF binaries from
SDcard into memory and execute it, as Linux is doing. This will open a
new chapter in using microcontrollers, and Nuttx is already nearly
there.
Would be happy to see the EsPiFF one day in your Nuttx Videos!
best regards,
Michael
Am 2022-10-26 14:56, schrieb Alan C. Assis:
> Hi Michael,
>
> Congratulations! You created a really great board!!!
>
> I'm sure that many people here will be interested on it, those who are
> really interested to contribute.
>
> The idea of using RPI form-factor is really good. Actually we were
> discussing about the idea of creating some RPI-like board to replace
> high level Linux system with a system running NuttX RTOS.
>
> I think adding JTAG for ESP32 and SWD for RP2040 will be very useful,
> please include it for the final board.
>
> A friend of mine created a nice and simple board for NuttX that he
> released as open-source:
>
> https://github.com/lucaszampar/NuttX_STM32F4_RS485_DevBoard
>
> He send me some pictures that I put on my flickr:
>
> https://live.staticflickr.com/65535/52456145643_97eca8e9b1_o.jpg
>
> https://live.staticflickr.com/65535/52455885674_94eba29fcc_b.jpg
>
> Soon, he will submit support to mainline.
>
> BR,
>
> Alan
>
> On 10/26/22, michael.schmid@mdc-service.de
> <mi...@mdc-service.de> wrote:
>> Dear Nuttx developers,
>>
>> we have developed the EsPiff (ESP32+RP2040 on the Raspberry Pi Form
>> Factor), a open source board to replace RasPi's and there clones,
>> where
>> the high processing power and/or Linux is not needed, but stability
>> and
>> the reuse of RasPi HATs are required.
>>
>> The github home is https://github.com/MDCservice/EsPiFF
>>
>> We will also offer the EsPiFF on CrowdSupply
>> https://www.crowdsupply.com/mdc-service-wittenburg-gmbh/espiff
>>
>> We would like to send a few boards for free to Nuttx developers, to
>> improve Nuttx compatibility. Would there be interest?
>>
>> A high level summary about the EsPiFF:
>> An ESP32-WROVER-I module with 16 MB Flash, 8 MB PSRAM is taking care
>> - wired Ethernet via a IP101 PHY,
>> - Wifi (need an external Wifi Antenna with uFL connector),
>> - 3 serial UARTs,
>> - one the 3 serial UARTs is used for programming via a CH340 USB-UART
>> chip, what can be enabled/disabled with jumpers,
>> - I2C port expander PCA 9557 for some chip select signals and 3 user
>> LEDs,
>> - SDcard in SPI mode,
>> - external real time clock, with supervisior,
>> - 2kB FRAM,
>> - USB Type-C connector for up to 5V/3A, connected to the CH340
>> USB-UART
>> to program the ESP32
>>
>> An RP2040 (Pi Pico) what takes care the 40 pin RasPi header,
>> - connected to the ESP32 via SPI,
>> - UAB-A connector, also used to program the RP2040 (need to hold the
>> boot button while power the board).
>>
>> In earlier versions, we had the LAN8720 PHY, but as others (Olimex,
>> wESP) we also got problems and replaced it with the IP101 since v3.1.
>>
>> Currently, there is no HW debugging broken out on the board. But we
>> could add a JTAG header on the bottom side, with TDO, TDI, TCK, TMS,
>> GND, 3V3 in the next board production run. The ESP32 has the JTAG pins
>> on GPIO12, 13, 14, 15, what are used for SPI on the EsPiFF, so code
>> using the SPI could not be debugged while JTAG is using the pins.
>> Would
>> it still make sense to build in the JTAG header?
>>
>> Would be glad to get your feedback,
>> Michael
>>
--
Chief engineer & consultant
MDC-Service Wittenburg GmbH
Bergstiftsgasse 11
09599 Freiberg, Germany
Office Gen. +49 3731 7832310
Fax +49 3731 2442369
Re: Dev-Board for Nuttx
Posted by "Alan C. Assis" <ac...@gmail.com>.
Hi Michael,
Congratulations! You created a really great board!!!
I'm sure that many people here will be interested on it, those who are
really interested to contribute.
The idea of using RPI form-factor is really good. Actually we were
discussing about the idea of creating some RPI-like board to replace
high level Linux system with a system running NuttX RTOS.
I think adding JTAG for ESP32 and SWD for RP2040 will be very useful,
please include it for the final board.
A friend of mine created a nice and simple board for NuttX that he
released as open-source:
https://github.com/lucaszampar/NuttX_STM32F4_RS485_DevBoard
He send me some pictures that I put on my flickr:
https://live.staticflickr.com/65535/52456145643_97eca8e9b1_o.jpg
https://live.staticflickr.com/65535/52455885674_94eba29fcc_b.jpg
Soon, he will submit support to mainline.
BR,
Alan
On 10/26/22, michael.schmid@mdc-service.de
<mi...@mdc-service.de> wrote:
> Dear Nuttx developers,
>
> we have developed the EsPiff (ESP32+RP2040 on the Raspberry Pi Form
> Factor), a open source board to replace RasPi's and there clones, where
> the high processing power and/or Linux is not needed, but stability and
> the reuse of RasPi HATs are required.
>
> The github home is https://github.com/MDCservice/EsPiFF
>
> We will also offer the EsPiFF on CrowdSupply
> https://www.crowdsupply.com/mdc-service-wittenburg-gmbh/espiff
>
> We would like to send a few boards for free to Nuttx developers, to
> improve Nuttx compatibility. Would there be interest?
>
> A high level summary about the EsPiFF:
> An ESP32-WROVER-I module with 16 MB Flash, 8 MB PSRAM is taking care
> - wired Ethernet via a IP101 PHY,
> - Wifi (need an external Wifi Antenna with uFL connector),
> - 3 serial UARTs,
> - one the 3 serial UARTs is used for programming via a CH340 USB-UART
> chip, what can be enabled/disabled with jumpers,
> - I2C port expander PCA 9557 for some chip select signals and 3 user
> LEDs,
> - SDcard in SPI mode,
> - external real time clock, with supervisior,
> - 2kB FRAM,
> - USB Type-C connector for up to 5V/3A, connected to the CH340 USB-UART
> to program the ESP32
>
> An RP2040 (Pi Pico) what takes care the 40 pin RasPi header,
> - connected to the ESP32 via SPI,
> - UAB-A connector, also used to program the RP2040 (need to hold the
> boot button while power the board).
>
> In earlier versions, we had the LAN8720 PHY, but as others (Olimex,
> wESP) we also got problems and replaced it with the IP101 since v3.1.
>
> Currently, there is no HW debugging broken out on the board. But we
> could add a JTAG header on the bottom side, with TDO, TDI, TCK, TMS,
> GND, 3V3 in the next board production run. The ESP32 has the JTAG pins
> on GPIO12, 13, 14, 15, what are used for SPI on the EsPiFF, so code
> using the SPI could not be debugged while JTAG is using the pins. Would
> it still make sense to build in the JTAG header?
>
> Would be glad to get your feedback,
> Michael
>
Dev-Board for Nuttx
Posted by mi...@mdc-service.de.
Dear Nuttx developers,
we have developed the EsPiff (ESP32+RP2040 on the Raspberry Pi Form
Factor), a open source board to replace RasPi's and there clones, where
the high processing power and/or Linux is not needed, but stability and
the reuse of RasPi HATs are required.
The github home is https://github.com/MDCservice/EsPiFF
We will also offer the EsPiFF on CrowdSupply
https://www.crowdsupply.com/mdc-service-wittenburg-gmbh/espiff
We would like to send a few boards for free to Nuttx developers, to
improve Nuttx compatibility. Would there be interest?
A high level summary about the EsPiFF:
An ESP32-WROVER-I module with 16 MB Flash, 8 MB PSRAM is taking care
- wired Ethernet via a IP101 PHY,
- Wifi (need an external Wifi Antenna with uFL connector),
- 3 serial UARTs,
- one the 3 serial UARTs is used for programming via a CH340 USB-UART
chip, what can be enabled/disabled with jumpers,
- I2C port expander PCA 9557 for some chip select signals and 3 user
LEDs,
- SDcard in SPI mode,
- external real time clock, with supervisior,
- 2kB FRAM,
- USB Type-C connector for up to 5V/3A, connected to the CH340 USB-UART
to program the ESP32
An RP2040 (Pi Pico) what takes care the 40 pin RasPi header,
- connected to the ESP32 via SPI,
- UAB-A connector, also used to program the RP2040 (need to hold the
boot button while power the board).
In earlier versions, we had the LAN8720 PHY, but as others (Olimex,
wESP) we also got problems and replaced it with the IP101 since v3.1.
Currently, there is no HW debugging broken out on the board. But we
could add a JTAG header on the bottom side, with TDO, TDI, TCK, TMS,
GND, 3V3 in the next board production run. The ESP32 has the JTAG pins
on GPIO12, 13, 14, 15, what are used for SPI on the EsPiFF, so code
using the SPI could not be debugged while JTAG is using the pins. Would
it still make sense to build in the JTAG header?
Would be glad to get your feedback,
Michael
Re: [DISCUSS] NuttX graduation: Draft Resolution
Posted by Michael Jung <mi...@secore.ly>.
I think this is a great idea! Thanks for the offer, Alin.
Alin Jerpelea <je...@gmail.com> schrieb am Fr., 28. Okt. 2022, 08:10:
> If none has a better idea I can step in
>
> Best Regards
> Alin
>
> On Fri, 28 Oct 2022, 06:35 Nathan Hartman, <ha...@gmail.com>
> wrote:
>
> > Ping... Folks, we need to choose a Vice President for the proposed
> > Apache NuttX TLP.
> >
> >
> > On Tue, Oct 25, 2022 at 9:55 PM Nathan Hartman <hartman.nathan@gmail.com
> >
> > wrote:
> > >
> > > Dear NuttX community,
> > >
> > > As our community VOTE [1] for graduation to Top Level Project has
> > > PASSED [2], the next steps are:
> > >
> > > (1) Draft our Charter/Resolution
> > > (2) Decide members of the initial Project Management Committee (PMC)
> > > (3) Choose the 1st Vice President of the proposed Apache NuttX PMC
> > >
> > > Please participate so we can get this done efficiently!
> > >
> > > Regarding item #1, below please find a 1st Draft Resolution for review
> > > and discussion -- this draft was generated by Whimsy (there's a button
> > > at the bottom of our podling page [3] to draft the resolution). Please
> > > read it anyway and provide feedback!!!
> > >
> > > Regarding item #2, currently the draft resolution lists all members of
> > > the Apache NuttX (Incubating) PPMC to become members of the proposed
> > > Apache NuttX PMC. If anyone feels there should be changes, please let
> > > us know.
> > >
> > > Regarding item #3, the draft resolution has [!! INSERT NAME HERE !!]
> > > where the name of the proposed Vice President should be written. We
> > > need to decide who that will be. The Vice President reports to the
> > > board 4 times each year, similarly to how we have been reporting to
> > > the Incubator PMC (IPMC), but there are no mentors who need to sign
> > > off on it. Speak up if you're interested in being the Vice President
> > > of Apache NuttX!
> > >
> > > 1st draft of our Resolution:
> > >
> > > [[[
> > >
> > > Establish the Apache NuttX Project
> > >
> > > WHEREAS, the Board of Directors deems it to be in the best interests of
> > > the Foundation and consistent with the Foundation's purpose to
> > > establish a Project Management Committee charged with the creation and
> > > maintenance of open-source software, for distribution at no charge to
> > > the public, related to a mature, real-time embedded operating system
> > > (RTOS).
> > >
> > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > > (PMC), to be known as the "Apache NuttX Project", be and hereby is
> > > established pursuant to Bylaws of the Foundation; and be it further
> > >
> > > RESOLVED, that the Apache NuttX Project be and hereby is responsible
> > > for the creation and maintenance of software related to a mature, real-
> > > time embedded operating system (RTOS); and be it further
> > >
> > > RESOLVED, that the office of "Vice President, Apache NuttX" be and
> > > hereby is created, the person holding such office to serve at the
> > > direction of the Board of Directors as the chair of the Apache NuttX
> > > Project, and to have primary responsibility for management of the
> > > projects within the scope of responsibility of the Apache NuttX
> > > Project; and be it further
> > >
> > > RESOLVED, that the persons listed immediately below be and hereby are
> > > appointed to serve as the initial members of the Apache NuttX Project:
> > >
> > > * Abdelatif Guettouche <ag...@apache.org>
> > > * Alan Carvalho de Assis <ac...@apache.org>
> > > * Alin Jerpelea <je...@apache.org>
> > > * Anthony Merlino <an...@apache.org>
> > > * Brennan Ashton <bt...@apache.org>
> > > * David Sidrane <da...@apache.org>
> > > * Duo Zhang <zh...@apache.org>
> > > * Flavio Paiva Junqueira <fp...@apache.org>
> > > * Gregory Nutt <gn...@apache.org>
> > > * Gustavo Henrique Nihei <gu...@apache.org>
> > > * Junping Du <ju...@apache.org>
> > > * Justin Mclean <jm...@apache.org>
> > > * Lup Yuen Lee <lu...@apache.org>
> > > * Masayuki Ishikawa <ma...@apache.org>
> > > * Mohammad Asif Siddiqui <as...@apache.org>
> > > * Nathan Hartman <ha...@apache.org>
> > > * Sara Monteiro <sa...@apache.org>
> > > * Xiang Xiao <xi...@apache.org>
> > >
> > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that [!! INSERT NAME HERE !!]
> > > be appointed to the office of Vice President, Apache NuttX, to serve in
> > > accordance with and subject to the direction of the Board of Directors
> > > and the Bylaws of the Foundation until death, resignation, retirement,
> > > removal or disqualification, or until a successor is appointed; and be
> > > it further
> > >
> > > RESOLVED, that the Apache NuttX Project be and hereby is tasked with
> > > the migration and rationalization of the Apache Incubator NuttX
> > > podling; and be it further
> > >
> > > RESOLVED, that all responsibilities pertaining to the Apache Incubator
> > > NuttX podling encumbered upon the Apache Incubator PMC are hereafter
> > > discharged.
> > >
> > > ]]]
> > >
> > > References:
> > >
> > > [1] https://lists.apache.org/thread/r1tn6qstkqmhh52szy4j2bgnnydbjmx4
> > >
> > > [2] https://lists.apache.org/thread/ss1dqyh8b80zlkq42cp5so4qth7z08q2
> > >
> > > [3] https://whimsy.apache.org/roster/ppmc/nuttx
> > >
> > > [4] https://incubator.apache.org/guides/graduation.html
> > >
> > > Thanks to everyone!
> > >
> > > Cheers,
> > > Nathan
> >
>
Re: [DISCUSS] NuttX graduation: Draft Resolution
Posted by "Alan C. Assis" <ac...@gmail.com>.
Agree! Alin is actively helping this project!
BR,
Alan
On 10/28/22, Alin Jerpelea <je...@gmail.com> wrote:
> If none has a better idea I can step in
>
> Best Regards
> Alin
>
> On Fri, 28 Oct 2022, 06:35 Nathan Hartman, <ha...@gmail.com>
> wrote:
>
>> Ping... Folks, we need to choose a Vice President for the proposed
>> Apache NuttX TLP.
>>
>>
>> On Tue, Oct 25, 2022 at 9:55 PM Nathan Hartman <ha...@gmail.com>
>> wrote:
>> >
>> > Dear NuttX community,
>> >
>> > As our community VOTE [1] for graduation to Top Level Project has
>> > PASSED [2], the next steps are:
>> >
>> > (1) Draft our Charter/Resolution
>> > (2) Decide members of the initial Project Management Committee (PMC)
>> > (3) Choose the 1st Vice President of the proposed Apache NuttX PMC
>> >
>> > Please participate so we can get this done efficiently!
>> >
>> > Regarding item #1, below please find a 1st Draft Resolution for review
>> > and discussion -- this draft was generated by Whimsy (there's a button
>> > at the bottom of our podling page [3] to draft the resolution). Please
>> > read it anyway and provide feedback!!!
>> >
>> > Regarding item #2, currently the draft resolution lists all members of
>> > the Apache NuttX (Incubating) PPMC to become members of the proposed
>> > Apache NuttX PMC. If anyone feels there should be changes, please let
>> > us know.
>> >
>> > Regarding item #3, the draft resolution has [!! INSERT NAME HERE !!]
>> > where the name of the proposed Vice President should be written. We
>> > need to decide who that will be. The Vice President reports to the
>> > board 4 times each year, similarly to how we have been reporting to
>> > the Incubator PMC (IPMC), but there are no mentors who need to sign
>> > off on it. Speak up if you're interested in being the Vice President
>> > of Apache NuttX!
>> >
>> > 1st draft of our Resolution:
>> >
>> > [[[
>> >
>> > Establish the Apache NuttX Project
>> >
>> > WHEREAS, the Board of Directors deems it to be in the best interests of
>> > the Foundation and consistent with the Foundation's purpose to
>> > establish a Project Management Committee charged with the creation and
>> > maintenance of open-source software, for distribution at no charge to
>> > the public, related to a mature, real-time embedded operating system
>> > (RTOS).
>> >
>> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>> > (PMC), to be known as the "Apache NuttX Project", be and hereby is
>> > established pursuant to Bylaws of the Foundation; and be it further
>> >
>> > RESOLVED, that the Apache NuttX Project be and hereby is responsible
>> > for the creation and maintenance of software related to a mature, real-
>> > time embedded operating system (RTOS); and be it further
>> >
>> > RESOLVED, that the office of "Vice President, Apache NuttX" be and
>> > hereby is created, the person holding such office to serve at the
>> > direction of the Board of Directors as the chair of the Apache NuttX
>> > Project, and to have primary responsibility for management of the
>> > projects within the scope of responsibility of the Apache NuttX
>> > Project; and be it further
>> >
>> > RESOLVED, that the persons listed immediately below be and hereby are
>> > appointed to serve as the initial members of the Apache NuttX Project:
>> >
>> > * Abdelatif Guettouche <ag...@apache.org>
>> > * Alan Carvalho de Assis <ac...@apache.org>
>> > * Alin Jerpelea <je...@apache.org>
>> > * Anthony Merlino <an...@apache.org>
>> > * Brennan Ashton <bt...@apache.org>
>> > * David Sidrane <da...@apache.org>
>> > * Duo Zhang <zh...@apache.org>
>> > * Flavio Paiva Junqueira <fp...@apache.org>
>> > * Gregory Nutt <gn...@apache.org>
>> > * Gustavo Henrique Nihei <gu...@apache.org>
>> > * Junping Du <ju...@apache.org>
>> > * Justin Mclean <jm...@apache.org>
>> > * Lup Yuen Lee <lu...@apache.org>
>> > * Masayuki Ishikawa <ma...@apache.org>
>> > * Mohammad Asif Siddiqui <as...@apache.org>
>> > * Nathan Hartman <ha...@apache.org>
>> > * Sara Monteiro <sa...@apache.org>
>> > * Xiang Xiao <xi...@apache.org>
>> >
>> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that [!! INSERT NAME HERE !!]
>> > be appointed to the office of Vice President, Apache NuttX, to serve in
>> > accordance with and subject to the direction of the Board of Directors
>> > and the Bylaws of the Foundation until death, resignation, retirement,
>> > removal or disqualification, or until a successor is appointed; and be
>> > it further
>> >
>> > RESOLVED, that the Apache NuttX Project be and hereby is tasked with
>> > the migration and rationalization of the Apache Incubator NuttX
>> > podling; and be it further
>> >
>> > RESOLVED, that all responsibilities pertaining to the Apache Incubator
>> > NuttX podling encumbered upon the Apache Incubator PMC are hereafter
>> > discharged.
>> >
>> > ]]]
>> >
>> > References:
>> >
>> > [1] https://lists.apache.org/thread/r1tn6qstkqmhh52szy4j2bgnnydbjmx4
>> >
>> > [2] https://lists.apache.org/thread/ss1dqyh8b80zlkq42cp5so4qth7z08q2
>> >
>> > [3] https://whimsy.apache.org/roster/ppmc/nuttx
>> >
>> > [4] https://incubator.apache.org/guides/graduation.html
>> >
>> > Thanks to everyone!
>> >
>> > Cheers,
>> > Nathan
>>
>
Re: Native Windows build
Posted by fft <ff...@feedforward.com.cn>.
Thanks for your advice, i will try it!
BR,
Zouboan
------------------ Original ------------------
From: "xiaoxiang781216"<xiaoxiang781216@gmail.com>;
Date: Sun, Nov 13, 2022 11:15 PM
To: "dev"<dev@nuttx.apache.org>;
Subject: Re: Native Windows build
First, you need to update
https://github.com/apache/incubator-nuttx/blob/master/tools/ci/cibuild.sh
to install the tool required by the build in a refresh Windows installation.
Second, Update
https://github.com/apache/incubator-nuttx/blob/master/.github/workflows/build.yml
to select Windows as build server.
Re: Native Windows build
Posted by Xiang Xiao <xi...@gmail.com>.
On Sat, Nov 12, 2022 at 9:43 PM fft <ff...@feedforward.com.cn> wrote:
> Dear all,
>
>
> Through the efforts of Petro and me , NuttX Windows native build is
> finally restored again:
>
>
> https://github.com/apache/incubator-nuttx/pull/7572
> https://github.com/apache/incubator-nuttx/pull/7580
> https://github.com/apache/incubator-nuttx-apps/pull/1407
>
>
> As Alan's suggestion, is better to add Windows Native Environment build in
> CI to avoid breaking it again. but i'm not expert in ci and docker, i don't
> know how to construct a Windows environment in docker on github. If someone
> have interesting in construct Windows Native Environment ci , i can be able
> to help.
>
>
First, you need to update
https://github.com/apache/incubator-nuttx/blob/master/tools/ci/cibuild.sh
to install the tool required by the build in a refresh Windows installation.
Second, Update
https://github.com/apache/incubator-nuttx/blob/master/.github/workflows/build.yml
to select Windows as build server.
>
> BR,
>
> Zouboan
>
>
> ------------------ Original ------------------
> From: "Alan Carvalho de Assis"<acassis@gmail.com>;
> Date: Thu, Nov 3, 2022 00:22 AM
> To: "dev"<dev@nuttx.apache.org>;
>
> Subject: Re: Native Windows build
>
>
>
> Hi Zouboan,
>
> Unfortunately there is nobody working with Windows Native Environment
> and some time ago someone reported it was delaying about 10 minutes to
> compile NuttX.
>
> So I think it is not an issue with your tools, but with NuttX Building
> System.
>
> My suggestion is if someone fixes it we add Windows Native Environment
> build in our CI to avoid breaking it again.
>
> BR,
>
> Alan
>
> On 11/2/22, fft <fft@feedforward.com.cn> wrote:
> > Dear all,
> >
> >
> > A few years ago, I successfully configure and build NuttX-8.2 in a
> native
> > Windows environment (the toolchains is GNU-Win32 +
> > kconfig-frontends-win32-3.12.1 + MinGW, and the host OS is both XP
> and Win7
> > ) , I can even debug NuttX through Code::Blocks IDE under Windows.
> But now i
> > find the NuttX can not build in native Windows environment anymore,
> the
> > environment and toolchains is exactly what i had configured a few
> years ago,
> > but now it failed at configure stage, I tried to fix the configure,
> but i
> > found there's too many changes involved. So I have to ask, is there
> anybody
> > build NuttX in native Windows environment recently? or is the issues
> of my
> > toolchains?
> >
> >
> > regards,
> > Zouboan
Re: Native Windows build
Posted by Xiang Xiao <xi...@gmail.com>.
On Sun, Nov 13, 2022 at 10:33 PM fft <ff...@feedforward.com.cn> wrote:
> A few years ago, i build NuttX-8.2 in Windows native build it takes about
> 1 minutes. the latest nuttx use temporary .ddc to generate Make.dep because
> there's so many .ddc file, one type command to process all .ddc file will
> give an error: input line is too long in Windows native build. i have
> to type .ddc to Make.dep one by one, and this waste a lot of time.
> now build lateset NUttX(stm32f4discovery:nsh) take 3.34 minutes in first
> time and 1.15 minutes second time(make clean rather than make distclean).
>
>
You may try to revert:
https://github.com/apache/incubator-nuttx/pull/2335
https://github.com/apache/incubator-nuttx/pull/2544
>
> As suggested in NuttX's README.md, i configure NuttX-8.2 in Windows native
> build use kconfig-frontends-win32 from:
> https://github.com/reclone/kconfig-frontends-win32 and
> https://github.com/reclone/kconfig-frontends-win32/releases
> but https://github.com/reclone/kconfig-frontends-win32 last version is
> v3.12.1, and it stop update since 2017, since v9.1.0 nuttx use
> kconfig-frontends v4.11.0 to configure nuttx and there's some expression
> in Kconfig (for example: if PWM_MULTICHAN && PWM_NCHANNELS > 1)
> can not support by kconfig-frontends-win32-3.12.1, and will give an error
> when make olddefconfig in configure stage. to configure latest NuttX
> in Windows native build, i update kconfig-frontends-win32 to v4.11.0 and
> create a PR: https://github.com/reclone/kconfig-frontends-win32/pull/1
> ,but kconfig-frontends-win32 hasn't been updated for so many years, i don't
> know whether there's any body to merge this patch. So before this patch was
> merged,if anybody who want configure latest NuttX use
> kconfig-frontends-win32, please download from my branch:
> https://github.com/zouboan/kconfig-frontends-win32/releases/tag/v4.11.0
>
>
Again, the community needs to find a place to host the unmaintained
projects like kconfig-frontends.
>
> BR,
>
>
> Zouboan
>
>
> ------------------ Original ------------------
> From: "Brennan Ashton"<bashton@brennanashton.com>;
> Date: Sat, Nov 12, 2022 11:05 PM
> To: "dev"<dev@nuttx.apache.org>;
>
> Subject: Re: Native Windows build
>
>
>
> I can probably help revive my past effort to run some native builds in CI
> to at least prevent it from getting fully broken. One of the blockers last
> time, was just how slow it was and the limited number of Windows workers.
>
> Let's see what we can do.
>
> --Brennan
Re: Native Windows build
Posted by fft <ff...@feedforward.com.cn>.
A few years ago, i build NuttX-8.2 in Windows native build it takes about 1 minutes. the latest nuttx use temporary .ddc to generate Make.dep because there's so many .ddc file, one type command to process all .ddc file will give an error: input line is too long in Windows native build. i have to type .ddc to Make.dep one by one, and this waste a lot of time.
now build lateset NUttX(stm32f4discovery:nsh) take 3.34 minutes in first time and 1.15 minutes second time(make clean rather than make distclean).
As suggested in NuttX's README.md, i configure NuttX-8.2 in Windows native build use kconfig-frontends-win32 from:
https://github.com/reclone/kconfig-frontends-win32 and https://github.com/reclone/kconfig-frontends-win32/releases
but https://github.com/reclone/kconfig-frontends-win32 last version is v3.12.1, and it stop update since 2017, since v9.1.0 nuttx use
kconfig-frontends v4.11.0 to configure nuttx and there's some expression in Kconfig (for example: if PWM_MULTICHAN && PWM_NCHANNELS > 1) can not support by kconfig-frontends-win32-3.12.1, and will give an error when make olddefconfig in configure stage. to configure latest NuttX in Windows native build, i update kconfig-frontends-win32 to v4.11.0 and create a PR: https://github.com/reclone/kconfig-frontends-win32/pull/1 ,but kconfig-frontends-win32 hasn't been updated for so many years, i don't know whether there's any body to merge this patch. So before this patch was merged,if anybody who want configure latest NuttX use kconfig-frontends-win32, please download from my branch: https://github.com/zouboan/kconfig-frontends-win32/releases/tag/v4.11.0
BR,
Zouboan
------------------ Original ------------------
From: "Brennan Ashton"<bashton@brennanashton.com>;
Date: Sat, Nov 12, 2022 11:05 PM
To: "dev"<dev@nuttx.apache.org>;
Subject: Re: Native Windows build
I can probably help revive my past effort to run some native builds in CI
to at least prevent it from getting fully broken. One of the blockers last
time, was just how slow it was and the limited number of Windows workers.
Let's see what we can do.
--Brennan
Re: Native Windows build
Posted by Gregory Nutt <sp...@gmail.com>.
On Sat, Nov 12, 2022 at 9:28 AM Gregory Nutt <sp...@gmail.com> wrote:
> There was also IAR/uVision IDE support in the repository for STM32. All
> of the IAR/uVision helper tools are still present (I think), but the IAR
> board support was removed
> https://bitbucket.org/patacongo/obsoleted/src/60ec01456d8b09f5b813a5fd8865cdbd5a0ccc20/ChangeLog#lines-357
>
The only special support that IAR needed was special assembly language
source files because the GNU asm source file syntax was not compatible with
IAR. But I I see that these special IAR files were also deleted for
ARMv7-M:
https://github.com/apache/incubator-nuttx/commit/1320e5add4771718c6da3fdd850583a2b2694ddb
Re: Native Windows build
Posted by Gregory Nutt <sp...@gmail.com>.
On 11/12/2022 9:05 AM, Brennan Ashton wrote:
> I can probably help revive my past effort to run some native builds in CI
> to at least prevent it from getting fully broken. One of the blockers last
> time, was just how slow it was and the limited number of Windows workers.
Did we ever really have a native windows build in CI? I don't think
that the native build has been working since NuttX moved to the ASF
incubator. Are you sure this wasn't a Cygwin build? The Cygwin build
is not a "native" build since it still depends on the POSIX environment
provided by Cygwin. So it is really just like the Linux build but
slower. Cygwin is slow due primarily to the emulation of fork() which
does not exist in Windows. But would not think that a truly native
build would depend on the emulated fork() and should not be so slow.
Last time I measured, I used a script with a loop that forked some
trivial process as fast as possible. The emulated fork() limited
performance to about 7 forks/sec under Cygwin.
Some "native" Windows tools are still based on Cygwin (like MinGW which
is usually bundled with MSYS/MSYS2) are still based on Cygwin and
probably still have some fork-related performance issues. If someone
really cared about the native build performance, a Visual C++ port might
be work considering.
There was alsoIAR/uVisionIDEsupport in the repository for STM32. All of
the IAR/uVision helper tools are still present (I think), but the IAR
board support was removed
https://bitbucket.org/patacongo/obsoleted/src/60ec01456d8b09f5b813a5fd8865cdbd5a0ccc20/ChangeLog#lines-357
Re: Native Windows build
Posted by Brennan Ashton <ba...@brennanashton.com>.
I can probably help revive my past effort to run some native builds in CI
to at least prevent it from getting fully broken. One of the blockers last
time, was just how slow it was and the limited number of Windows workers.
Let's see what we can do.
--Brennan
On Sat, Nov 12, 2022, 5:43 AM fft <ff...@feedforward.com.cn> wrote:
> Dear all,
>
>
> Through the efforts of Petro and me , NuttX Windows native build is
> finally restored again:
>
>
> https://github.com/apache/incubator-nuttx/pull/7572
> https://github.com/apache/incubator-nuttx/pull/7580
> https://github.com/apache/incubator-nuttx-apps/pull/1407
>
>
> As Alan's suggestion, is better to add Windows Native Environment build in
> CI to avoid breaking it again. but i'm not expert in ci and docker, i don't
> know how to construct a Windows environment in docker on github. If someone
> have interesting in construct Windows Native Environment ci , i can be able
> to help.
>
>
> BR,
>
> Zouboan
>
>
> ------------------ Original ------------------
> From: "Alan Carvalho de Assis"<acassis@gmail.com>;
> Date: Thu, Nov 3, 2022 00:22 AM
> To: "dev"<dev@nuttx.apache.org>;
>
> Subject: Re: Native Windows build
>
>
>
> Hi Zouboan,
>
> Unfortunately there is nobody working with Windows Native Environment
> and some time ago someone reported it was delaying about 10 minutes to
> compile NuttX.
>
> So I think it is not an issue with your tools, but with NuttX Building
> System.
>
> My suggestion is if someone fixes it we add Windows Native Environment
> build in our CI to avoid breaking it again.
>
> BR,
>
> Alan
>
> On 11/2/22, fft <fft@feedforward.com.cn> wrote:
> > Dear all,
> >
> >
> > A few years ago, I successfully configure and build NuttX-8.2 in a
> native
> > Windows environment (the toolchains is GNU-Win32 +
> > kconfig-frontends-win32-3.12.1 + MinGW, and the host OS is both XP
> and Win7
> > ) , I can even debug NuttX through Code::Blocks IDE under Windows.
> But now i
> > find the NuttX can not build in native Windows environment anymore,
> the
> > environment and toolchains is exactly what i had configured a few
> years ago,
> > but now it failed at configure stage, I tried to fix the configure,
> but i
> > found there's too many changes involved. So I have to ask, is there
> anybody
> > build NuttX in native Windows environment recently? or is the issues
> of my
> > toolchains?
> >
> >
> > regards,
> > Zouboan
Re: Native Windows build
Posted by fft <ff...@feedforward.com.cn>.
Dear all,
Through the efforts of Petro and me , NuttX Windows native build is finally restored again:
https://github.com/apache/incubator-nuttx/pull/7572
https://github.com/apache/incubator-nuttx/pull/7580
https://github.com/apache/incubator-nuttx-apps/pull/1407
As Alan's suggestion, is better to add Windows Native Environment build in CI to avoid breaking it again. but i'm not expert in ci and docker, i don't know how to construct a Windows environment in docker on github. If someone have interesting in construct Windows Native Environment ci , i can be able to help.
BR,
Zouboan
------------------ Original ------------------
From: "Alan Carvalho de Assis"<acassis@gmail.com>;
Date: Thu, Nov 3, 2022 00:22 AM
To: "dev"<dev@nuttx.apache.org>;
Subject: Re: Native Windows build
Hi Zouboan,
Unfortunately there is nobody working with Windows Native Environment
and some time ago someone reported it was delaying about 10 minutes to
compile NuttX.
So I think it is not an issue with your tools, but with NuttX Building System.
My suggestion is if someone fixes it we add Windows Native Environment
build in our CI to avoid breaking it again.
BR,
Alan
On 11/2/22, fft <fft@feedforward.com.cn> wrote:
> Dear all,
>
>
> A few years ago, I successfully configure and build NuttX-8.2 in a native
> Windows environment (the toolchains is GNU-Win32 +
> kconfig-frontends-win32-3.12.1 + MinGW, and the host OS is both XP and Win7
> ) , I can even debug NuttX through Code::Blocks IDE under Windows. But now i
> find the NuttX can not build in native Windows environment anymore, the
> environment and toolchains is exactly what i had configured a few years ago,
> but now it failed at configure stage, I tried to fix the configure, but i
> found there's too many changes involved. So I have to ask, is there anybody
> build NuttX in native Windows environment recently? or is the issues of my
> toolchains?
>
>
> regards,
> Zouboan
Re: Native Windows build
Posted by "Alan C. Assis" <ac...@gmail.com>.
Hi Zouboan,
Unfortunately there is nobody working with Windows Native Environment
and some time ago someone reported it was delaying about 10 minutes to
compile NuttX.
So I think it is not an issue with your tools, but with NuttX Building System.
My suggestion is if someone fixes it we add Windows Native Environment
build in our CI to avoid breaking it again.
BR,
Alan
On 11/2/22, fft <ff...@feedforward.com.cn> wrote:
> Dear all,
>
>
> A few years ago, I successfully configure and build NuttX-8.2 in a native
> Windows environment (the toolchains is GNU-Win32 +
> kconfig-frontends-win32-3.12.1 + MinGW, and the host OS is both XP and Win7
> ) , I can even debug NuttX through Code::Blocks IDE under Windows. But now i
> find the NuttX can not build in native Windows environment anymore, the
> environment and toolchains is exactly what i had configured a few years ago,
> but now it failed at configure stage, I tried to fix the configure, but i
> found there's too many changes involved. So I have to ask, is there anybody
> build NuttX in native Windows environment recently? or is the issues of my
> toolchains?
>
>
> regards,
> Zouboan
Native Windows build
Posted by fft <ff...@feedforward.com.cn>.
Dear all,
A few years ago, I successfully configure and build NuttX-8.2 in a native Windows environment (the toolchains is GNU-Win32 + kconfig-frontends-win32-3.12.1 + MinGW, and the host OS is both XP and Win7 ) , I can even debug NuttX through Code::Blocks IDE under Windows. But now i find the NuttX can not build in native Windows environment anymore, the environment and toolchains is exactly what i had configured a few years ago, but now it failed at configure stage, I tried to fix the configure, but i found there's too many changes involved. So I have to ask, is there anybody build NuttX in native Windows environment recently? or is the issues of my toolchains?
regards,
Zouboan
Re: [DISCUSS] NuttX graduation: Draft Resolution
Posted by Nathan Hartman <ha...@gmail.com>.
On Fri, Oct 28, 2022 at 2:10 AM Alin Jerpelea <je...@gmail.com> wrote:
>
> If none has a better idea I can step in
>
> Best Regards
> Alin
>
> On Fri, 28 Oct 2022, 06:35 Nathan Hartman, <ha...@gmail.com> wrote:
>
> > Ping... Folks, we need to choose a Vice President for the proposed
> > Apache NuttX TLP.
Hi all,
Thank you Alin!
I have updated our draft resolution (see below).
I'll wait 72 hours for any comments etc and unless there is anything
else to do, I'll start the IPMC vote for our graduation!
2nd draft of our Resolution:
[[[
Establish the Apache NuttX Project
WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to
establish a Project Management Committee charged with the creation and
maintenance of open-source software, for distribution at no charge to
the public, related to a mature, real-time embedded operating system
(RTOS).
NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
(PMC), to be known as the "Apache NuttX Project", be and hereby is
established pursuant to Bylaws of the Foundation; and be it further
RESOLVED, that the Apache NuttX Project be and hereby is responsible
for the creation and maintenance of software related to a mature, real-
time embedded operating system (RTOS); and be it further
RESOLVED, that the office of "Vice President, Apache NuttX" be and
hereby is created, the person holding such office to serve at the
direction of the Board of Directors as the chair of the Apache NuttX
Project, and to have primary responsibility for management of the
projects within the scope of responsibility of the Apache NuttX
Project; and be it further
RESOLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache NuttX Project:
* Abdelatif Guettouche <ag...@apache.org>
* Alan Carvalho de Assis <ac...@apache.org>
* Alin Jerpelea <je...@apache.org>
* Anthony Merlino <an...@apache.org>
* Brennan Ashton <bt...@apache.org>
* David Sidrane <da...@apache.org>
* Duo Zhang <zh...@apache.org>
* Flavio Paiva Junqueira <fp...@apache.org>
* Gregory Nutt <gn...@apache.org>
* Gustavo Henrique Nihei <gu...@apache.org>
* Junping Du <ju...@apache.org>
* Justin Mclean <jm...@apache.org>
* Lup Yuen Lee <lu...@apache.org>
* Masayuki Ishikawa <ma...@apache.org>
* Mohammad Asif Siddiqui <as...@apache.org>
* Nathan Hartman <ha...@apache.org>
* Sara Monteiro <sa...@apache.org>
* Xiang Xiao <xi...@apache.org>
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Alin Jerpelea be
appointed to the office of Vice President, Apache NuttX, to serve in
accordance with and subject to the direction of the Board of Directors
and the Bylaws of the Foundation until death, resignation, retirement,
removal or disqualification, or until a successor is appointed; and be
it further
RESOLVED, that the Apache NuttX Project be and hereby is tasked with
the migration and rationalization of the Apache Incubator NuttX
podling; and be it further
RESOLVED, that all responsibilities pertaining to the Apache Incubator
NuttX podling encumbered upon the Apache Incubator PMC are hereafter
discharged.
]]]
References:
[1] [VOTE] Apache NuttX Community Graduation
https://lists.apache.org/thread/r1tn6qstkqmhh52szy4j2bgnnydbjmx4
[2] [RESULT][VOTE] Apache NuttX Community Graduation
https://lists.apache.org/thread/ss1dqyh8b80zlkq42cp5so4qth7z08q2
[3] NuttX podling roster: https://whimsy.apache.org/roster/ppmc/nuttx
[4] Incubator Guide to Successful Graduation
https://incubator.apache.org/guides/graduation.html
Thanks to everyone!
Cheers,
Nathan
Re: [DISCUSS] NuttX graduation: Draft Resolution
Posted by Alin Jerpelea <je...@gmail.com>.
If none has a better idea I can step in
Best Regards
Alin
On Fri, 28 Oct 2022, 06:35 Nathan Hartman, <ha...@gmail.com> wrote:
> Ping... Folks, we need to choose a Vice President for the proposed
> Apache NuttX TLP.
>
>
> On Tue, Oct 25, 2022 at 9:55 PM Nathan Hartman <ha...@gmail.com>
> wrote:
> >
> > Dear NuttX community,
> >
> > As our community VOTE [1] for graduation to Top Level Project has
> > PASSED [2], the next steps are:
> >
> > (1) Draft our Charter/Resolution
> > (2) Decide members of the initial Project Management Committee (PMC)
> > (3) Choose the 1st Vice President of the proposed Apache NuttX PMC
> >
> > Please participate so we can get this done efficiently!
> >
> > Regarding item #1, below please find a 1st Draft Resolution for review
> > and discussion -- this draft was generated by Whimsy (there's a button
> > at the bottom of our podling page [3] to draft the resolution). Please
> > read it anyway and provide feedback!!!
> >
> > Regarding item #2, currently the draft resolution lists all members of
> > the Apache NuttX (Incubating) PPMC to become members of the proposed
> > Apache NuttX PMC. If anyone feels there should be changes, please let
> > us know.
> >
> > Regarding item #3, the draft resolution has [!! INSERT NAME HERE !!]
> > where the name of the proposed Vice President should be written. We
> > need to decide who that will be. The Vice President reports to the
> > board 4 times each year, similarly to how we have been reporting to
> > the Incubator PMC (IPMC), but there are no mentors who need to sign
> > off on it. Speak up if you're interested in being the Vice President
> > of Apache NuttX!
> >
> > 1st draft of our Resolution:
> >
> > [[[
> >
> > Establish the Apache NuttX Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best interests of
> > the Foundation and consistent with the Foundation's purpose to
> > establish a Project Management Committee charged with the creation and
> > maintenance of open-source software, for distribution at no charge to
> > the public, related to a mature, real-time embedded operating system
> > (RTOS).
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache NuttX Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache NuttX Project be and hereby is responsible
> > for the creation and maintenance of software related to a mature, real-
> > time embedded operating system (RTOS); and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache NuttX" be and
> > hereby is created, the person holding such office to serve at the
> > direction of the Board of Directors as the chair of the Apache NuttX
> > Project, and to have primary responsibility for management of the
> > projects within the scope of responsibility of the Apache NuttX
> > Project; and be it further
> >
> > RESOLVED, that the persons listed immediately below be and hereby are
> > appointed to serve as the initial members of the Apache NuttX Project:
> >
> > * Abdelatif Guettouche <ag...@apache.org>
> > * Alan Carvalho de Assis <ac...@apache.org>
> > * Alin Jerpelea <je...@apache.org>
> > * Anthony Merlino <an...@apache.org>
> > * Brennan Ashton <bt...@apache.org>
> > * David Sidrane <da...@apache.org>
> > * Duo Zhang <zh...@apache.org>
> > * Flavio Paiva Junqueira <fp...@apache.org>
> > * Gregory Nutt <gn...@apache.org>
> > * Gustavo Henrique Nihei <gu...@apache.org>
> > * Junping Du <ju...@apache.org>
> > * Justin Mclean <jm...@apache.org>
> > * Lup Yuen Lee <lu...@apache.org>
> > * Masayuki Ishikawa <ma...@apache.org>
> > * Mohammad Asif Siddiqui <as...@apache.org>
> > * Nathan Hartman <ha...@apache.org>
> > * Sara Monteiro <sa...@apache.org>
> > * Xiang Xiao <xi...@apache.org>
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that [!! INSERT NAME HERE !!]
> > be appointed to the office of Vice President, Apache NuttX, to serve in
> > accordance with and subject to the direction of the Board of Directors
> > and the Bylaws of the Foundation until death, resignation, retirement,
> > removal or disqualification, or until a successor is appointed; and be
> > it further
> >
> > RESOLVED, that the Apache NuttX Project be and hereby is tasked with
> > the migration and rationalization of the Apache Incubator NuttX
> > podling; and be it further
> >
> > RESOLVED, that all responsibilities pertaining to the Apache Incubator
> > NuttX podling encumbered upon the Apache Incubator PMC are hereafter
> > discharged.
> >
> > ]]]
> >
> > References:
> >
> > [1] https://lists.apache.org/thread/r1tn6qstkqmhh52szy4j2bgnnydbjmx4
> >
> > [2] https://lists.apache.org/thread/ss1dqyh8b80zlkq42cp5so4qth7z08q2
> >
> > [3] https://whimsy.apache.org/roster/ppmc/nuttx
> >
> > [4] https://incubator.apache.org/guides/graduation.html
> >
> > Thanks to everyone!
> >
> > Cheers,
> > Nathan
>
Re: [DISCUSS] NuttX graduation: Draft Resolution
Posted by Nathan Hartman <ha...@gmail.com>.
Ping... Folks, we need to choose a Vice President for the proposed
Apache NuttX TLP.
On Tue, Oct 25, 2022 at 9:55 PM Nathan Hartman <ha...@gmail.com> wrote:
>
> Dear NuttX community,
>
> As our community VOTE [1] for graduation to Top Level Project has
> PASSED [2], the next steps are:
>
> (1) Draft our Charter/Resolution
> (2) Decide members of the initial Project Management Committee (PMC)
> (3) Choose the 1st Vice President of the proposed Apache NuttX PMC
>
> Please participate so we can get this done efficiently!
>
> Regarding item #1, below please find a 1st Draft Resolution for review
> and discussion -- this draft was generated by Whimsy (there's a button
> at the bottom of our podling page [3] to draft the resolution). Please
> read it anyway and provide feedback!!!
>
> Regarding item #2, currently the draft resolution lists all members of
> the Apache NuttX (Incubating) PPMC to become members of the proposed
> Apache NuttX PMC. If anyone feels there should be changes, please let
> us know.
>
> Regarding item #3, the draft resolution has [!! INSERT NAME HERE !!]
> where the name of the proposed Vice President should be written. We
> need to decide who that will be. The Vice President reports to the
> board 4 times each year, similarly to how we have been reporting to
> the Incubator PMC (IPMC), but there are no mentors who need to sign
> off on it. Speak up if you're interested in being the Vice President
> of Apache NuttX!
>
> 1st draft of our Resolution:
>
> [[[
>
> Establish the Apache NuttX Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to
> establish a Project Management Committee charged with the creation and
> maintenance of open-source software, for distribution at no charge to
> the public, related to a mature, real-time embedded operating system
> (RTOS).
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache NuttX Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache NuttX Project be and hereby is responsible
> for the creation and maintenance of software related to a mature, real-
> time embedded operating system (RTOS); and be it further
>
> RESOLVED, that the office of "Vice President, Apache NuttX" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache NuttX
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache NuttX
> Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache NuttX Project:
>
> * Abdelatif Guettouche <ag...@apache.org>
> * Alan Carvalho de Assis <ac...@apache.org>
> * Alin Jerpelea <je...@apache.org>
> * Anthony Merlino <an...@apache.org>
> * Brennan Ashton <bt...@apache.org>
> * David Sidrane <da...@apache.org>
> * Duo Zhang <zh...@apache.org>
> * Flavio Paiva Junqueira <fp...@apache.org>
> * Gregory Nutt <gn...@apache.org>
> * Gustavo Henrique Nihei <gu...@apache.org>
> * Junping Du <ju...@apache.org>
> * Justin Mclean <jm...@apache.org>
> * Lup Yuen Lee <lu...@apache.org>
> * Masayuki Ishikawa <ma...@apache.org>
> * Mohammad Asif Siddiqui <as...@apache.org>
> * Nathan Hartman <ha...@apache.org>
> * Sara Monteiro <sa...@apache.org>
> * Xiang Xiao <xi...@apache.org>
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that [!! INSERT NAME HERE !!]
> be appointed to the office of Vice President, Apache NuttX, to serve in
> accordance with and subject to the direction of the Board of Directors
> and the Bylaws of the Foundation until death, resignation, retirement,
> removal or disqualification, or until a successor is appointed; and be
> it further
>
> RESOLVED, that the Apache NuttX Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator NuttX
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> NuttX podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>
> ]]]
>
> References:
>
> [1] https://lists.apache.org/thread/r1tn6qstkqmhh52szy4j2bgnnydbjmx4
>
> [2] https://lists.apache.org/thread/ss1dqyh8b80zlkq42cp5so4qth7z08q2
>
> [3] https://whimsy.apache.org/roster/ppmc/nuttx
>
> [4] https://incubator.apache.org/guides/graduation.html
>
> Thanks to everyone!
>
> Cheers,
> Nathan