I would rather use an IRC channel than slack :p
Where is this channel? Freenode? #nuttx ?
Sebastien
On 12/15/19 11:05 PM, Gregory Nutt wrote:
Communication stuff
I still see the slack channels, but they will go away? The IRC
channel will get back up in IRC apache? Linked in yes no? What
hello,
I am not favorable personally with submodules. They are a pain to keep
in sync across multiple remotes and branches.
This was used in the past in NuttX, and it was aborted.
Sebastien
On 12/13/19 3:28 AM, Anthony Merlino wrote:
I think submodules are a good way to go. That would
why completely change what has worked for years?
2 repos as always. Submodules are an absolute pain to manage when you have
branches.
people have always been cloning two repos.
devs were sending patches for one of them.
Now they send pull request instead. Better tracking, ability to fix while
Wait,
what advantage does in fact the submodule method bring?
Even with a hat repository that contains two submodules (apps and nuttx), you
will have to send separate pull requests for each submodule, right?
Sebastien
Le 18/12/2019 à 14:40, Gregory Nutt a écrit :
> On 12/18/2019 4:23 AM, David
ter nuttx
>
> NuttX master shal point to (still builds and runs)
> \nuttx master shal
> \apps master shal
>
> But the branch master of the submodules
>
> \nuttx master shal aaa
> \apps master shal bbb
>
>
> merge PR from NuttX to master NuttX
Hello,
I dont agree. A fundamental feature to avoid widespread developement of
the so-called Internet of Shit is basic embedded security.
Some thoughts:
An embedded system can have a minimal security. Of course security has
several levels from non-existent to ideal.
Not having a full PKI
hello
IIRC the config menus allow you to flip the display direction. Did you have a
look over there?
Sebastien
Le 24/12/2019 à 08:39, Nii Jyeni a écrit :
> Hi~
> I am trying the graphics module of nuttx. I just used the nxtext sample
> program and found that the text displayed on oled is
Not sure throwing more tools at the current mess will fix anthing.
Full support to Greg for benevolent dictatorship extension until things are
settled.
Sebastien
Le 24/12/2019 à 08:03, Disruptive Solutions a écrit :
> A platform like this could help? Samsung seems to use it? Does Apache has
>
Hello,
I have seriously slowed down my nuttx contributions because of the
apache turmoil but I am still reading this list and will have to work on
this topic at one point.
See my opinions below.
Sebastien
Le 22/05/2020 à 09:41, Takashi Yamamoto a écrit :
hi,
i'm working on mbedtls
Hello
Le 22/05/2020 à 10:05, Takashi Yamamoto a écrit :
can you explain what's "real nuttx code"?
For me, code specifically written for NuttX with good integration and
performance. Different from a third-party library.
The makefile glue is OK for NuttX contribution.
Crypto is a directory
Le 22/05/2020 à 17:00, Takashi Yamamoto a écrit :
On Fri, May 22, 2020 at 7:26 PM Sebastien Lorquet wrote:
Hello
Le 22/05/2020 à 10:05, Takashi Yamamoto a écrit :
can you explain what's "real nuttx code"?
For me, code specifically written for NuttX with good integration and
p
I think the web client could be rewritten to benefit from the curl port
I started a while a go, which is available upstream:
https://github.com/apache/incubator-nuttx-apps/tree/master/netutils/libcurl4nx
Improving this curl port would benefit any app using it, not just the
web client.
Never seen this done but I am highly interested.
An extremely cool 68k platform to run nuttx would be the Texas
Instruments 68k calculators. The V200 has 4M of flash and 256k of RAM.
The TI89 and 92+ also have that kind of memories. There is a fully
working emulator with a built in debugger,
Hello
my previous board has the same setup 32f427 and mac in eeprom.
To achieve this programmatically (without using a shell command), I have
used my application.
The application boots a system app instead of NSH. This app starts some
useful threads.
If I need to use NSH, I can start the
So sorry to be a radical humorist.
Sebastien
Le 03/06/2020 à 15:57, Gregory Nutt a écrit :
-1
I like it the way it is. And thoroughly opposed to increate the
default line width. There has been BS talk about it. But it is just
BS and amounts to nothing. No one should be taking this
Or, Let's stick with usual console widths and make it 132?
sebastien
Le 01/06/2020 à 15:30, David Sidrane a écrit :
Let's one up them and keep it binary at the same time 128! :)
-Original Message-
From: Alan Carvalho de Assis [mailto:acas...@gmail.com]
Sent: Monday, June 01, 2020 4:22
Please make sure the readmes are still easily readable in vim and other
plain text editors.
Plain text is good.
underlined plain text interpreted by github is still readable (markdown?)
anything that requires writing explicit tag in the readme text files
should be avoided imho.
also,
it's impossible for nuttx.
in case you are asking if i volunteer to create such a rich framework,
no, i don't. (sorry!)
BR,
Alan
On 5/29/20, Takashi Yamamoto wrote:
hi,
On Fri, May 29, 2020 at 11:53 PM Sebastien Lorquet
wrote:
I think the web client could be rewritten to benefit from
Hello,
I believe in a stong principle, applied successfully numerous time in my
embedded development company:
It it's not broken, dont fix it.
That applies precisely to this change.
The build system we have have the following characteristics
-it works for its intended purposes
-it is
ent to let the community make the
decision. I suspect that the advocates of CMake are having a larger
voice in the decision.
On 6/9/2021 7:38 AM, Sebastien Lorquet wrote:
Hello,
I believe in a stong principle, applied successfully numerous time in
my embedded development company:
It it's
Le 10/06/2021 à 16:34, Nathan Hartman a écrit :
Second, we need a new Documentation page, "Migrating From Older
NuttX." In this documentation, every compatibility change should be
documented, going from the present to at least as far back as NuttX
7.31. We can get all of these from the
Hello,
The correct syntax is:
.isramdata (NOLOAD) : /*<- this is the segment name in the output,
NOLOAD means that this segment is not to be initialized, like BSS, but
the linker alread knows that BSS is NOLOAD*/
{
*(.isramdata) /*<- this is the input sections from the
what I would check here (just a live tought process)
* check that the ld file is actually used (ld file is pointed by main
Make.defs IIRC) (easy: just add garbage in it and verify build actually
breaks)
* check that the driver source with the definition is being recompiled
* check that the
Hello,
I have to update the nuttx in our project from pre-apache to last version.
We would like to use the external board feature.
As a test I copied the nucleo-f446re folder in boards/arm to somewhere
else (sibling to apps and nuttx), renamed it, and pointed to it in the
configuration. make
done, what a process for a 7-character change...
The PHY and cable detection worked perfectly fine in our project.
Sebastien
Le 24/05/2021 à 23:04, Nathan Hartman a écrit :
On Mon, May 24, 2021 at 11:36 AM Sebastien Lorquet wrote:
Hello,
There is a typo in the PCA9555 driver at line 817
. But there is no way back now.Just less contributions
from me.
Sebastien
Le 25/05/2021 à 16:11, Nathan Hartman a écrit :
On Tue, May 25, 2021 at 10:05 AM Sebastien Lorquet wrote:
done, what a process for a 7-character change...
The PHY and cable detection worked perfectly fine in our project
it will be easier next time.
Does any of the 21 queued test that I see waiting in github enable this
driver?
Because if they dont (which I suspect, hence this typo) these tests are
useless.
Sebastien
Le 25/05/2021 à 16:17, Sebastien Lorquet a écrit :
No, the workflow is very clear
in mm which doesn't
make sense and it was due to outdated board Make.defs.
śr., 26 maj 2021 o 17:21 Sebastien Lorquet
napisał(a):
Update: stack dump and register analysis are in fact pointing to a crash
in mm_alloc
I have enabled memory management debug:
mm_initialize: Heap: start=0x1000
n board (on which I based my board).
Sebastien
Le 25/05/2021 à 21:26, Nathan Hartman a écrit :
On Tue, May 25, 2021 at 12:02 PM Sebastien Lorquet
wrote:
Back to the business
After this we managed to recompile our project using the latest NuttX
sources, but it fails when trying to init
Back to the business
After this we managed to recompile our project using the latest NuttX
sources, but it fails when trying to init the PHY irq on our STM32F427
board: We get "unexpected IRQ".
Yes I know that's pretty vague :-)
Is there anything obvious I should have been careful with in this
Assis <
acas...@gmail.com> escreveu:
I agree, it should a good idea if it could be turned into a Documentation
page!
BR,
Alan
On 5/20/21, Sebastien Lorquet wrote:
:o
it worked.
How am I supposed to guess this?
Your email should be copied verbatim in the official documentation
som
:o
it worked.
How am I supposed to guess this?
Your email should be copied verbatim in the official documentation
somewhere under "how to create and build a custom board"
Also I woud advise against this common dir in boards, since it prevents
users from creating custom boards from built-in
Hello,
Migrating our system from NuttX 7.30 to current trunk
Nothing very bad, just up_arch.h changed to arm_arch.h and it's mostly
compiling fine.
One of our custom drivers use sigqueue, which requires different types
according to CONFIG_CAN_PASS_STRUCTS
This config seems to not exist
unction inside a board or inside an arch, it shouldn't return a
function with same name from other board or from other arch.
So, at end-of-day, these modifications you are complain about, will
make the life of all users better.
BR,
Alan
On 5/27/21, Sebastien Lorquet wrote:
I sill wonder what is the purpo
0x2000?
CONFIG_MM_REGIONS needs to be set up correctly if you have multiple
heap regions.
On Wed, May 26, 2021 at 5:22 PM Sebastien Lorquet wrote:
Hello,
Thanks for the remarks.
I am using the flat (monolithic build) and I see no place that define
this flag, at all.
I dont even s
then. It seems that this change
was made during this time.
Sebastien
Le 27/05/2021 à 09:38, Sebastien Lorquet a écrit :
Boom, that was the extrastuff. The board now boots. We're going to run
a lot of functional tests to make sure everything is okay, but I dont
have this strange hardfault at boot.
Thank
I will try to continue testing my custom board with upcoming releases to
detect such breaks. Even if I dont get to vote in your committees I will
tell you if I find some problem.
Yes I skipped two years of nuttx development, starting christmas holiday
2019, followed by covid lockdowns and a
: Sebastien Lorquet [mailto:sebast...@lorquet.fr]
Sent: Wednesday, May 26, 2021 9:22 AM
To: dev@nuttx.apache.org
Subject: Re: Port of project from NuttX 7.30 to 10.1 RC1: Unexpected IRQ
Hello,
Thanks for the remarks.
I am using the flat (monolithic build) and I see no place that define
this flag, at all
:06 AM Sebastien Lorquet wrote:
Hello,
Migrating our system from NuttX 7.30 to current trunk
Nothing very bad, just up_arch.h changed to arm_arch.h and it's mostly
compiling fine.
One of our custom drivers use sigqueue, which requires different types
according to CONFIG_CAN_PASS_STRUCTS
https://github.com/apache/incubator-nuttx/issues/3769
Le 24/05/2021 à 17:36, Sebastien Lorquet a écrit :
Hello,
There is a typo in the PCA9555 driver at line 817:
CONFIG_TCA64XX_INT_NCALLBACKS is a bad copy paste, should be
CONFIG_PCA9555_INT_NCALLBACKS.
After this we managed to recompile
Hello
Note that in "real" field-deployed product this sector512 layer should
NOT be used since it will wear the flash much faster than using a real
MTD filesystem.
One thing to keep in mind is that flash takes a significant time to
erase and write, and that if interrupted, a flash memory
I see that around the time of this discussion the userland API of
task_spawn has been changed in incompatible ways.
by this commit:
https://github.com/apache/incubator-nuttx-apps/commit/58293abb8e896bb04f3a76bf8b48206debe68f26?branch=58293abb8e896bb04f3a76bf8b48206debe68f26=unified
My apps,
hello,
cool if you have a proper storage system :)
The STM32F4 also has these variable sector sizes, and IIRC it is not
accessible as MTD.
Yes, usually, the write size is much smaller than the erase size.
Sebastien
Le 08/07/2021 à 16:47, Fotis Panagiotopoulos a écrit :
The pagesize should
Hello,
I need to implement an asynchronous server in NuttX.
What infrastructure is currently working best? performance and
functionality wise...
select or epoll?
Thanks for any advice
Sebastien
Hello
I did that and it works in a consumer product with a stm32 since, well,
2018 I think. Also in an open source product.
my board uses a custom linker script that locates the start of the flash
a bit farther than the usual start (one stm32 block or 16k IIRC) . Then
I compile nuttx as
val lo*/ \n\t"
"movt r1, #0x0800 /*val hi*/ \n\t"
"str r1, [r0] /*store value at address*/ \n\t"
"bx lr /*take the jump*/ \n"
);
}
Le 22/04/2021 à 09:59, Sebastien Lorquet a écrit :
Hello
I d
SmartFS DOES actually works and will not shred the flash sectors to
pieces as it's aware of flash memory behaviour and limited erases.
Reading the original paper I found that LittleFS was VERY well made to
ensure FS operations are atomic and recoverable in the event of a power cut.
that is the best and usual way to get documentation about nuttx
you need some grep-fu
the system.map trick is a generic debug technique that you can't invent
if someone else doesnt tell you about it :)
sebastien
Le 24/08/2021 à 18:57, Tim a écrit :
No, it's not in the system map. Having
PB, "offset",
180 CONFIG_EXAMPLES_UNIONFS_MOUNTPT);
apps/thttpd also has an option to mount a binfs with "real" file
system on other media. This permits in-FLASH builtin apps to be
intermixed or replaced by ELF modules in the "real" file system.
Greg
On 11/30/2021 11:01 AM, Sebas
Hello,
just an idea:
When adding more nested function calls causes a crash, I check stack
overflows.
Sometimes the default stack size specified when defining apps (2048) is
too small, specially you have buffers on this stack, and printf consumes
a lot of stack itself when calling nested
recently the linker command was changed from ld to gcc
The release notes for 10.2 indicates required changes in local board
files. I did that.
however I found that the required changes are not in local files, but in
nuttx itself, eg for arm it's at arch/arm/src/Makefile
A grep call
,
Alan
On Monday, November 29, 2021, Sebastien Lorquet
wrote:
recently the linker command was changed from ld to gcc
The release notes for 10.2 indicates required changes in local board
files. I did that.
however I found that the required changes are not in local files, but in
nuttx itself, eg
lora is just a RF modulation scheme like FSK or BPSK
lorawan is the network protocol.
it can work with "any" rf transceiver, on top of any RF modulation,
usually it's used with lora, but can also be used with FSK or any other.
Sebastien
Le 13/12/2021 à 14:06, MIGUEL ALEXANDRE WISINTAINER a
...has been submitted and hopefully will be ok.
https://github.com/apache/incubator-nuttx/pull/4924
Sebastien
Hello,
For history our board need 128 Mbit of flash, but the 128 Mbit parts are
slw and have gigantic erase blocks.
So as an alternative our plan was to have two 64 Mbit SST parts (fast
and small erases) and aggregate them in software, so that we can present
the other drivers a single
Hello
new board has a new flash part that is smaller than the previous one.
however without changing the rest of my code, the creation of a
partition that is too large for the new small device was accepted.
I noticed that erase sector numbers were compared to write blocks
(calculated
Hi,
SDCC recently added a 6502 port, based on their HC08 port. I think it
has a chance to be better than cc65 or any gcc arsenal.
Yes, the 6502 8-bit hardware stack is very limited, but by paying the
price of a less efficient code, a software stack is possible.
Of course, such a port would
Hi,
It's great to get a compiler for a mainstream programming language
inside NuttX!
I will try to get a look at this.
Thank you!
Sebastien
Le 12/03/2022 à 01:51, Gregory Nutt a écrit :
Now that I am not longer on the critical path for NuttX support, I am much
less involved in the RTOS.
In this example it's Xiaomi and Sony.
NuttX has a code review problem and it has to be identified and addressed.
I have the same feeling here, last time I tried to send a pull request,
it took several day to fix style issues for a ONE LINE code typo.
And a lot of board breaking changes are
it :
On 3/28/22, Sebastien Lorquet wrote:
In this example it's Xiaomi and Sony.
NuttX has a code review problem and it has to be identified and addressed.
I have the same feeling here, last time I tried to send a pull request,
it took several day to fix style issues for a ONE LINE code ty
Hello,
If the Die Erase is similar in function to the bulk erase, then it can
be used instead, but this has to be done at runtime to support all the
chips in the same driver. So no @define or CONFIG_ option, because
choosing one would excude the others, and if you have both on a board
this
Hi
The closest way to achieve this, eg if you want to exercise the SD
drivers, would be to simulate a SPI/SD device that the main SD driver
could talk to.
The simulated SPI or SD would have to get,recognize and execute SD
commands, and it would get its storage from the host disk or memory.
h as
file systems or wear-leveling layers.
Most EEPPROMs are small, however, and it may not be practical to
support a file system on top of the EEPROM. So the lightweight
character driver layer from Sebastien Lorquet. This lightweight layer
will support only character-oriented I/O via l
Are you seriously taking legal advice, on behalf of an apache project,
from a generative language model?
Sebastien
Le 17/10/2023 à 22:22, Alan C. Assis a écrit :
Oops, it was: you cannot enforce both at same time.
Actually I think I was wrong (not about enforcing), but the main issue
about
ewing" millions of thread about license issues.
BR,
Alan
On 10/19/23, Sebastien Lorquet wrote:
Are you seriously taking legal advice, on behalf of an apache project,
from a generative language model?
Sebastien
Le 17/10/2023 à 22:22, Alan C. Assis a écrit :
Oops, it was: you cannot enfor
Hi,
Le 25/08/2023 à 11:48, raiden00pl a écrit :
Forcing people using cmake to support make is the worst thing that can
happen.
Open source is voluntary, any contribution is voluntary, any form of
forcing
others to do anything is unacceptable.
Modifying both systems will be good practice (and an
Hello
Why should you change the experience and make life difficult for
everyone, just to support a pair of specific configuration?
If you need to build twice, build twice, one project for h7, one project
for m4, then one python or other script to combine the images.
All users matter (eg,
into a Linux-only, GCC-only, and
ARM-only solution.
So the question asked in this thread should be answered : No, out of
tree builds should not be standard.
Sebastien
Le 25/08/2023 à 09:38, Sebastien Lorquet a écrit :
Hello
Why should you change the experience and make life difficult
Hi,
I have a nucleo-h743zi, in which I have enabled network.
It seems to work so far.
When I enable Network Info Debug, I get a crash.
The crash does not happen with Network info disabled (Enabling network
warnings and errors is ok)
I am writing on the mailing list to get feedback and
hi,
yes, this solution "just" requires a sed on all defconfig files, and
avoids having to specify the directory name in the git clone command,
which can easily be forgotten.
if I can express my taste on this extra minor choice I think nuttx-apps
looks better than nuttx_apps
Sebastien
On
Hi,
Currently in ipv4_input.c we have a warning that a packet was not for us
and was dropped. This pollutes the output of the console for no real
value when connected to a real network.
I suggest we turn this warning into an info to keep things clean.
The file contains real warnings that
, 2022 at 12:45 AM Sebastien Lorquet
wrote:
Hi,
Currently in ipv4_input.c we have a warning that a packet was not for us
and was dropped. This pollutes the output of the console for no real
value when connected to a real network.
I suggest we turn this warning into an info to keep things clean
Here it is, I hope it does not take two full days for merging :)
https://github.com/apache/incubator-nuttx/pull/6399
Sebastien
Le 09/06/2022 à 14:30, Sebastien Lorquet a écrit :
Hello,
I also agree an option is useless. I was just suggesting this in case
some people still want to see
@Nathan:
Yes, of course.
@Alan:
Of course not, the structure passed to init can be set up to describe
the required algorithm.
But the partial update situation can be useful for protocols where the
message is fragmented (eg radio transceivers with short FIFOs), or where
only some fields
Hi,
I'm working with the exact same board and struggled for several days
with a similar problem.
Breakpoints did not help since the issue was fugitive and not always
crashing at the same place.
There also were debug/release variations.
It turned out to be a stack issue.
The default stack
Hi,
We have deployed hundreds of boards with stm32f427 and ethernet, they
have all been working reliably for months without stopping, we know it
because they critically depend on network functionality and we have
reports if a card becomes unreachable. None has so far outside of
dedicated
just tried.
It passed all the tests.
On Tue, Jul 19, 2022 at 4:44 PM Sebastien Lorquet
wrote:
Hi,
We have deployed hundreds of boards with stm32f427 and ethernet, they
have all been working reliably for months without stopping, we know it
because they critically depend on network functionality
Hi,
The NuttX page should obviously not be deleted by it is not exactly
written in an encyclopedic style
I see text like (because Mr Greg did something and something) - you
should try to edit that so that it sounds more formal and neutral
This is not biased opinions, but is clearly not
Hi,
Sorry to throw a rock in the pond but having a single function named
"crc32" is very wrong and is not sufficient.
As you have discussed the polynomial length is just not enough to
describe a crc, the initial value, bit orders of input and output, and
bit inversion on input and output
Hi,
That would be -1 for me too.
Reason 1 from Nathan could change my vote.
But reason 2 would be a shame. We have one of the few a RTOS that
support CPUs outside ARM.
TBH, there is no solid technical reason to change this rule. Most of the
things mentioned in this comment are syntactic
Hi all,
SPI bus driver in STM32H7 requires the CONFIG_EXPERIMENTAL feature.
Is that still true as of today?
I will do some tests later but I would like to know if someone has
information about these peripherals, are these working or not, with
interrupt, dma etc?
Thanks for any info
on the clock.
*Regards,*
*David*
On Wed, Aug 31, 2022 at 6:26 AM Sebastien Lorquet
wrote:
Hi all,
SPI bus driver in STM32H7 requires the CONFIG_EXPERIMENTAL feature.
Is that still true as of today?
I will do some tests later but I would like to know if someone has
information about
tcp_close_eventhandler().
All these are happening within the same execution of tcp_input().
Any ideas?
On Tue, Jul 26, 2022 at 3:44 PM Sebastien Lorquet
Hi,
good find but
-I dont think any usual application tinkers with PHY regs during its
lifetime except the ethernet monitor
+1: Apache NuttX is ready to graduate to TLP
Sebastien
On 10/23/22 19:53, Abdelatif Guettouche wrote:
+1!
On Sat, Oct 22, 2022 at 5:28 AM Xiang Xiao
wrote:
+1!!!
On Fri, Oct 21, 2022 at 8:47 PM Nathan Hartman
wrote:
Dear Apache NuttX Community,
Following the [DISCUSS] thread which has
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
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,
IIRC the idea was that we dont integrate code fom externally maintained
projects?
Also IIRC the acceptable method is a specific makefile that downloads
code and patch/builds it.
I agree that such libs go into apps.
Sebastien
Le 27/10/2022 à 19:28, Nathan Hartman a écrit :
On Thu, Oct 27,
Hi,
I'm copying below the text of github issue #7138 I just opened, so that
more people can help.
I think this is quite an important bug to be fixed for the quality of
all upcoming releases.
Sebastien
Hi,
The stm32h7 does not properly drain the UARTs on close().
The console works
Hi,
I think there is an important issue in the stm32h7 uarts that was
untested up to now and is quite worrying.
Not sure this qualifies as a blocker for a release.
See my other email.
Sebastien
Le 19/09/2022 à 23:42, Alan Carvalho de Assis a écrit :
Guys, please help!!!
The idea is to
Hi,
If you want to play with 68k, tell me, the ti68k calculators
(ti89,92+,v200,titanium) should be great platforms: 256K RAM and 2-4M
flash, full keyboard and lcd screen.
They have some peculiarities, I could help with drivers or find friends
that could.
The cemetech/tiplanet communities
Hi,
+1
NuttX 12.0.0-RC1 building and working fine on my proprietary STM32H7 board.
Compiler: arm-none-eabi-gcc (GNU Arm Embedded Toolchain
10-2020-q4-major) 10.2.1 20201103 (release)
Sebastien
Le 11/01/2023 à 10:32, Alin Jerpelea a écrit :
Hello all,
Apache NuttX 12.0.0 RC1 has been
be
similar.
(later)
So the esp32c3-devkit:usbconsole configuration works on the m5stamp-c3u.
nsh> uname -a
NuttX 10.1.0-RC1 512be93c36 Dec 9 2022 12:32:21 risc-v esp32c3-devkit
Nice.
Sebastien
Le 09/12/2022 à 11:21, Sebastien Lorquet a écrit :
Hi,
As an introduction to the RISCV, I wo
Hi,
As an introduction to the RISCV, I would like to use NuttX on my M5stamp
C3U, which I can get for 8 dollars at a local store.
https://docs.m5stack.com/en/core/stamp_c3u
The module does not use a usb serial chip but direct USB connection
(there is a schematic in the bottom of the page).
nuttx and nuttxapps
Sébastien
Le 18/11/2022 à 17:30, Gregory Nutt a écrit :
why can’t we just have :
nuttx, apps
as it has been for a long time (before Apache) …
Ultimately, the repository names would appear here:
https://github.com/orgs/apache/repositories
nuttx/ would probably be
Hi,
I would also very much prefer nuttx and nuttx_apps but the other option
will not prevent me from sleeping well at night.
Sebastien
Le 18/11/2022 à 15:46, Gregory Nutt a écrit :
But NuttX has more features than traditional RTOS(e.g. FreeRTOS).
Actually,
Xiaomi uses it in the IoT space
Hi,
Also voting to let as-is
One more reason to keep the OS code under the "nuttx" name without some
sort of suffix: this is the main name of the project, and has been for
years.
When you want to clone this repo from a command line, you dont want to
go check on github if this is nuttx-core
Congrats!
Sébastien
Le 17/11/2022 à 17:20, Nathan Hartman a écrit :
Hi All,
NuttX graduated from the Incubator! Kudos to the whole NuttX
community. Here's to a great continuation of this journey for many
years to come!
Some post-graduation TODOs -- Help will be appreciated!!
* Change NuttX
, Sebastien Lorquet wrote:
Hi,
If your OS is built in monolithic mode (no protected mode) then
applications are just routines, so you can put a breakpoint in any
app routine and let it run until there.
To replace nsh by your app, do make menuconfig, menu RTOS features,
menu Tasks and scheduling, text
Hi,
If your OS is built in monolithic mode (no protected mode) then
applications are just routines, so you can put a breakpoint in any app
routine and let it run until there.
To replace nsh by your app, do make menuconfig, menu RTOS features, menu
Tasks and scheduling, text config
+1, too
Sébastien
Le 22/11/2022 à 14:30, Nathan Hartman a écrit :
After hearing back from Infra about the repository naming convention,
all the recent feedback has been to stay with the default and just
remove "incubator-" from our repo names, giving:
https://github.com/apache/nuttx
1 - 100 of 203 matches
Mail list logo
