Hello,
Yes, the inability to write individual bits in already programmed
sectors is a HUGE constraint. We have flash like this in some high
security embedded products, and it required a full redesign of our flash
interface.
Wear leveling is doable, but the particular bit that made us think
Hi,
Random hangs can be related to insufficient stack sizes. Stack size
requirements are sometimes surprising and the most unexpected. NuttX
defaults are sometimes quite small and dont include size variations for
different CPU architectures.
Also, there are tons of stack size parameters,
oh, that is cool!
Sebastien
On 22/04/2024 23:26, Alan C. Assis wrote:
Dear NuttXers,
Probably all saw about it, case don't here it goes:
https://developer.sony.com/posts/apache-nuttx-powers-worlds-smallest-lunar-robot-in-japans-historic-autonomous-lunar-exploration-mission
This is a small
Hi,
I dont want to have anything serious to do with rust, but I like your
article, as it gives a kind of rosetta stone to interop basic rust with
C and the usual toolchains, which I did not see anywhere else (I did not
search for long).
I'll keep it as a reference doc.
Thanks,
Sebastien
a little
more effort.
I think there are options, but without PRs on github, I don't see how
you could independently make changes.
On 3/21/2024 4:08 PM, Sebastien Lorquet wrote:
Hi,
I plan to leave github completely and delete my account, because of
this: https://huggingface.co/spaces/bigcode/in-the-st
Hi,
I plan to leave github completely and delete my account, because of
this: https://huggingface.co/spaces/bigcode/in-the-stack
It is the last of reasons that make me want to leave this place for good.
How can we imagine a process so I (and others) can continue to
contribute to NuttX
to the sim.
Sebastien
Le 19/03/2024 à 07:50, Sebastien Lorquet a écrit :
hi Tomek
I'll have a try and report.
Sebastien
On 3/19/24 01:36, Tomek CEDRO wrote:
Hey there Sebastien!
Sorry to hear that :-(
Would it be possible to try those tests in SIM ?
If yes are results the same?
This could b
hi Tomek
I'll have a try and report.
Sebastien
On 3/19/24 01:36, Tomek CEDRO wrote:
Hey there Sebastien!
Sorry to hear that :-(
Would it be possible to try those tests in SIM ?
If yes are results the same?
This could be included into CI tests with a SIM if that helps..?
--
CeDeROM,
hello,
Trying to migrate an old project to latest code. I have this config
after migration.
$ ag LITTLEFS .config
1928:CONFIG_FS_LITTLEFS=y
1929:CONFIG_FS_LITTLEFS_PROGRAM_SIZE_FACTOR=1
1930:CONFIG_FS_LITTLEFS_READ_SIZE_FACTOR=1
1931:CONFIG_FS_LITTLEFS_BLOCK_SIZE_FACTOR=1
Hi,
My position is : not in the core OS.
Why is everyone not surprised about that lol
I have actual Reasons for this, not just my bad mood or resistance to
novelty:
-only one toolchain, no alternative
-this excludes anything not supported by vanilla clang, eg
ARM/intel/riscv (I think).
Hello,
Yes, stm32h7 uart transmission has issues. You can easily test this in
nsh with just an echo command and a very long string, eg > 64 ascii
chars. At first I believed it was buffering problems.
This caused me some headaches 1.5 years ago, but the DMA serial driver
is too complex for
with porting to NuttX:
See my developments:
https://github.com/suarezvictor/micropython/tree/litex-rebase/ports/litex#readme
Who else can contribute?
On Fri, Feb 9, 2024 at 2:27 PM Sebastien Lorquet
wrote:
Hi,
Not sure I'm going to wait24Q3 :-) I'm certainly not focussed enough :-)
https
fork repo and
play there when stuff is ready we can push to both upstreams..? :-)
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
On Fri, Feb 9, 2024 at 6:07 PM Sebastien Lorquet wrote:
Hi,
I found the deletion commit:
https://github.com/apache/nuttx-apps/commit/abcb66cb20d85b910d55854de51b197ea
efficient "rapid prototyping" so I had no more need to use MicoPython
as it turned out memory hungry for bigger applications.
But still I am fan of Python so we could resurrect the idea :-)
Tomek
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
On Fri, Feb 9, 2024 at 4:04 PM Sebastien Lorq
more need to use MicoPython
as it turned out memory hungry for bigger applications.
But still I am fan of Python so we could resurrect the idea :-)
Tomek
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
On Fri, Feb 9, 2024 at 4:04 PM Sebastien Lorquet wrote:
Hi,
I think I may like to have microp
Hi,
I think I may like to have micropython work again on NuttX.
Where can I find the latest efforts on this project, to try my hand on it?
Sebastien
Le 26/10/2021 à 04:16, Tomasz CEDRO a écrit :
On Mon, Oct 25, 2021 at 7:45 PM Xiang Xiao wrote:
On Mon, Oct 25, 2021 at 11:37 PM Tomasz CEDRO
our boards the romfs is mounted by the board, so our nuttx own apps
already have this change.
Sebastien
Le 06/02/2024 à 16:32, Nathan Hartman a écrit :
On Tue, Feb 6, 2024 at 8:45 AM Sebastien Lorquet
wrote:
However, the default network configuration provided in NuttX examples is
cumbersome an
The phy on the nucleo-h743zi is supported, I have it working in an
industrialized product.
It does not have an interrupt line, so cable state detection requires a
polling daemon.
However, the default network configuration provided in NuttX examples is
cumbersome and too much linked with
n,
I have NUCLEO-H755ZI-Q on my table, but could not find a board package
in the tree. Is it supported?
Regards,
Simon
--
Hard- and Softwaredevelopment Consultant
Ingenieurbüro-Filgis
USt-IdNr.: DE305343278
On Tue, Feb 6, 2024 at 10:34 AM Sebastien Lorquet
wrote:
Hi,
The nucle
Hi,
The nucleo-h7 board series definitely work, there are several models
with ethernet.
Sebastien
Le 06/02/2024 à 10:26, Simon Filgis a écrit :
Dear all,
Can anybody recommend a stm32h7 board with ethernet that is well supported
by nuttx?
Thanks in advance,
Simon
Hi,
This is cool.
Two remarks:
- it would be nice to have tcc supported as an official compiler along
gcc and llvm. Probably just for fun with no "commercial interest" for nuttx.
- in the 80s, CP/M had C compilers that executed in less than 64k of RAM...
Sebastien.
Le 05/02/2024 à 05:16,
with it. The USB peripheral on Nordic chips is a nightmare and the current
support
in NuttX has a bug that I haven't had a chance to fix yet - so another
argument
to avoid dongle for now.
For development, I would recommend nrf52840-dk but it costs much more.
pt., 2 lut 2024 o 11:27 Sebastien Lorquet napisał
Hello,
Just a noob question: does NuttX support developing a BLE peripheral on
a NRF component, and if so, does it support low power modes so the
peripheral could run for years on a battery? I've seen the nrf52 is a
supported target.
I'm just looking to see if I can replace my home network
Hi,
I dont think you can use losetup to create a mtd device. loop devices
are regular block devices. This will only work if littlefs can mount a
block device (no idea if thats possible)
what you need is an adaptation layer that will implement a mtd device on
an eeprom.
You can duplicate a
.
On Mon, Nov 20, 2023 at 11:15 PM Sebastien Lorquet
wrote:
Nice: "While writing this, I could not find the source code for Xiaomi
Vela"
So where is it?
Sebastien
Le 18/11/2023 à 01:37, Gregory Nutt a écrit :
Worth taking a look at:
https://news.itsfoss.com/xiaomi-vela-open-source/
Nice: "While writing this, I could not find the source code for Xiaomi Vela"
So where is it?
Sebastien
Le 18/11/2023 à 01:37, Gregory Nutt a écrit :
Worth taking a look at: https://news.itsfoss.com/xiaomi-vela-open-source/
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
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
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
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
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
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,
I thought it would be interesting for other people on this mailing list:
https://nibbler.de/attic/P10.pdf
Sebastien
HW loader or SW
loader, but have drivers immune to that assumption and hard reset the
peripheral in driver init routine.
Best regards,
Petro
пн, 3 лип. 2023 р. о 13:20 Sebastien Lorquet пише:
Le 01/07/2023 à 18:41, Gregory Nutt a écrit :
On 7/1/2023 10:27 AM, Tim Hardisty wrote:
Lots of w
Le 01/07/2023 à 18:41, Gregory Nutt a écrit :
On 7/1/2023 10:27 AM, Tim Hardisty wrote:
Lots of work to do a full u-boot replacement, yes. But a basic one
using existing NuttX stuff such as RNDIS, dfu, mtd etc. - for MY
board at least - would not be much work. He said...naively!
You often
Hi,
The automatic mount of the ROMFS assumes that it is stored at a
predefined location in the board config, that it will be mounted at
/etc, and that it is mounted for the goal of using rc scripts, which may
not be the case at all.
I have a changes in my local apps directory that decouples
Yes, this is surprising.
The raspberry pi foundation had some dubious behaviours before.
The online dev communities will undoubtedly look into this with great
detail and clarify the thing.
I would stay cautious about this for a while.
Sebastien
Le 14/06/2023 à 14:27, Alan C. Assis a écrit
Hi,
This eeprom is not an mtd device, it is too small for any filesystem, usually.
So it's just a character device that makes the eeprom appear as a fixed size
file.
If you need an eeprom mtd, the driver could be extended to make it behave as a
mtd device.
Sebastien
Le 25 mai 2023 16:35:00
<
hartman.nat...@gmail.com>:
On Mon, May 22, 2023 at 9:29 AM Sebastien Lorquet
wrote:
If the untold reason is to speed up github tests, then run less tests.
Do we really need to test build on 13 or 20 arm platforms when only one
config of the other architectures is tested, and the actual
Hello Tomek,
Whatever is decided, the mere fact of wanting to make a decision on this
point will lead to more split.
either from people that want cmake
or from people who dont.
this is an intrinsically bad decision
Sebastien
Le 23/05/2023 à 01:41, Tomek CEDRO a écrit :
I can see that
rent.
I think I depicted the three more important point, case someone else
thing about some other important point of each side, please bring it
to the table.
BR,
Alan
On 5/22/23, Sebastien Lorquet wrote:
I very much agree with all of these arguments.
Thats a too large disruption for too littl
certification?
Would it be possible to get early access to your code? Could I help you in
developing this?
Thanks!
Michael
On Tue, May 9, 2023 at 7:13 PM Sebastien Lorquet
wrote:
Hi,
it is time!
I am, right now, starting to implement the smart card mode for STM32
USART, starting with STM32H7
I very much agree with all of these arguments.
Thats a too large disruption for too little benefits.
I dont want to be forced to use cmake.
Everything we use here to integrate NuttX is based on makefiles.
Why do we have to bring in yet another dependency? No, cmake is not
installed in our
one help me, by trying to reproduce this, with a kthread_create
in their board_init ?
Thanks,
Sebastien
Le 12/05/2023 à 11:08, Sebastien Lorquet a écrit :
Some more gdb stuff found that *something* is corrupting the contents
of argv, silently.
I have used an access watchpoint to catch acces
return OK;
(gdb) n
473 }
That's a context switch ???
Why is a context switch corrupting the argv contents of this task?
Sebastien
Le 12/05/2023 à 10:18, Sebastien Lorquet a écrit :
Well it's not the stack, same crash with the stack doubled from 4096
to 8192, BFAR still contains the suspic
te the TCBs via gdb at any point in time?
Sebastien
Le 11/05/2023 à 21:17, Sebastien Lorquet a écrit :
The stack is a good candidate, I see that I reported
stack_alloc_ptr = 0x38004328, stack_base_ptr = 0x38004368
but at the crash we have :
R2: 38003a1c
SP: 380038c0
I will try that t
the stack size for NSH ? Stack overflow in NSH
can cause some really weird hard faults, not that easy to diagnose.
czw., 11 maj 2023 o 18:34 Sebastien Lorquet
napisał(a):
Hello,
I have a stm32h7 board, based on the stm32h743zi2 nucleo.
I have activated the watchdog.
The method to do the kthread
Hello,
I have a stm32h7 board, based on the stm32h743zi2 nucleo.
I have activated the watchdog.
The method to do the kthread was copied from this :
https://github.com/apache/nuttx/blob/master/boards/arm/stm32/photon/src/stm32_wdt.c#LL146C7-L146C7
The watchdog works, the system is stable
to what you are saying!
This is a nice place to show what NuttX can do!
BR,
Alan
On 5/10/23, Sebastien Lorquet wrote:
Hello,
What is the use of a hackster channel and how will that dilute the
communication around the project? :p
I really hope no important official project communication
Hello,
What is the use of a hackster channel and how will that dilute the
communication around the project? :p
I really hope no important official project communication goes there
bypassing the list.
Apart from that I have no doubt that this will be a good tool to reach
more community.
Hi,
seems like it was not /dev/null after all but a /dev/pipe since my smart
card messages finally went through without any action on my side.
Sebastien
Le 09/05/2023 à 19:16, Alan C. Assis a écrit :
It seems that since (at least) yesterday Apache mailing list was
silently dropping emails.
HI,
No idea why this message did not make it through.
Resending with small updates.
Hi,
it is time!
I am, right now, starting to implement the smart card mode for STM32
USART, starting with STM32H7, this will be portable to other STM32
Hi,
it is time!
I am, right now, starting to implement the smart card mode for STM32
USART, starting with STM32H7, this will be portable to other STM32 chips
I guess.
The UART mode will just configure the uart for smartcard shenanigans,
eg, put it in working order for this mode.
Smart
Hello,
I have a similar feeling about this.
Remember, if it isn't broken, dont fix it.
Sebastien
On 4/23/23 13:32, Tomek CEDRO wrote:
hey there Yun, i am also strongly against removing working code that had
been here for a long time has been carefully designed gives granular
control etc.
Hi all,
As Tomek said, whatever you choose to do, please make sure everything of
this is absolutely kept optional, at least during the merge and
community validation phase.
I dont think connecting these proposals to CONFIG_BUILD_KERNEL is
granular enough.
Thanks,
Sebastien
Le 18/04/2023
Originating here:
https://mastodon.social/@marnanel@queer.party/110192469727439582
Copied for archival purposes:
Fun fact: the Jupiter Icy Moons Explorer can't use a real-time operating
system.
This is because it's Io bound.
That's all for me :-)
Sebastien
Thanks for the notification.
Your proposal is mostly OK for me, I hope others will send reactions
too. I have just one concern.
If I attempt to rephrase the proposal: Starting from a commit in a
future, stm32h7 GPIO definitions will not include speed indications
anymore, and these will
Hi,
If you use the spi_xx25xx EEPROM driver I submitted in 2014, please see
this pull request:
https://github.com/apache/nuttx/pull/8852
It contains a SPI bus lock bug that was silent and could have resulted
in bus conflicts if several devices interleaved accesses.
New libc code now has
/23, Sebastien Lorquet wrote:
Hi,
Dont you need the full ESP-IDF to build the bootloader and stubs?
If you have a simplified build method I am interested.
Last time I checked esp32-c3, it worked perfectly, but the bootloader
build was a bit cumbersome (fortunately it's only needed once, which
Hi,
Dont you need the full ESP-IDF to build the bootloader and stubs?
If you have a simplified build method I am interested.
Last time I checked esp32-c3, it worked perfectly, but the bootloader
build was a bit cumbersome (fortunately it's only needed once, which is
okay).
IIRC it even
Definitely a good thing we get the opportunity to talk about these
changes on this list, then.
We need technical overview from several people to determine the best way
to do things.
Sebastien
Le 10/03/2023 à 14:49, Gregory Nutt a écrit :
Thank you for this good change for better posix
Hello,
I think that, in order to organize, people need a better idea of what
"around 5-6 freight boxes of hardware, perhaps more" means exactly.
That would help plan what is needed to get them to another location.
Sebastien
Le 10/03/2023 à 14:51, Alan C. Assis a écrit :
Hi Greg,
Yes, I
Well, there it is
https://github.com/apache/nuttx-apps/issues/1653
Note that I dont get this behaviour with readline.
We can continue to discuss this in the issue.
Sebastien
Le 10/03/2023 à 11:47, Sebastien Lorquet a écrit :
Hi,
I have tested CLE and noticed this side effect.
My system
Hi,
I have tested CLE and noticed this side effect.
My system has background tasks at boot. these tasks write messages on
the console. At boot, a DHCP thread gets an IP after a delay.
When I typed the help command, the first h appeared twice: at first
position of the line, and also at the
Hello,
Thank you for this good change for better posix compliance.
In my setup nsh is used via a stm32h7 serial port.
I have my updated custom apps with your changes and everything works as
expected. I am using readline.
For better coverage I also tested CLE (with history) with NSH and did
Yes on this. Distribution provided bare metal arm toolchains have always
been a disappointment for me.
Sebastien
Le 09/03/2023 à 12:03, Petro Karashchenko a écrit :
I think the best way is to install GCC from the ARM website and not using
OS package manager.
sorry wrong calculation, I meant 7 days * 0.5 hour * 50% * 4 weeks = 7
hours per month.
Still a lot, which could be saved by a few minutes of your company time
per week for specific PRs. Cause not all them need careful review.
Sebastien
Le 09/03/2023 à 11:49, Sebastien Lorquet a écrit :
I
likely xiaomi will fork nuttx like Samuang and make our own
change. We don't want to spend the time to prepare the patch but no
feedback guarantee, since it consumes a huge resource to prepare the patch.
On Thu, Mar 9, 2023 at 6:15 PM Sebastien Lorquet
wrote:
Hi,
This sounds like a corporate rule
Hi,
If I am not mistaken, the existing NSH_CMDPARMS feature will just
execute the command once and copy the stdout into the var?
Aliases are more like virtual commands, that execute their contents when
run.
This is distinct from built-in commands and user implemented programs.
Sebastien
Hello,
I think you did things very,very well, thank you for this.
Here is some feedback:
1 - aliases are not required for me, but It could still be a worthwile
feature for others, and it's a requirement for you.
2 - this feels ok for me, since this is generally a better behaviour of
the
ed by the same
company)
Thanks
Alin
-Original Message-
From: Alan C. Assis
Sent: den 8 mars 2023 19:15
To: dev@nuttx.apache.org
Cc: Sebastien Lorquet
Subject: Re: DISCUSSION - Usage of mailing lists for apache projects
Hi Lwazi,
It is not sarcarm, I'm talking about facts.
Also I didn'
tion of the
Nuttx PR template about notifying the list in the case of a breakage change.
czw., 9 mar 2023 o 10:24 Sebastien Lorquet
napisał(a):
Notify the list!
Simple as that.
If there is no progress, it means this is a complex PR that needs
attention.
Just adding reviewers keep the issue github-cen
Alan C. Assis
Sent: den 8 mars 2023 19:15
To: dev@nuttx.apache.org
Cc: Sebastien Lorquet
Subject: Re: DISCUSSION - Usage of mailing lists for apache projects
Hi Lwazi,
It is not sarcarm, I'm talking about facts.
Also I didn't say Sebastien points aren't valid, but is diverting from the
real
...@sony.com
Sent: Thursday, March 9, 2023 4:13 AM
To: dev@nuttx.apache.org
Cc: Sebastien Lorquet
Subject: RE: DISCUSSION - Usage of mailing lists for apache projects
Hi all,
I agree with David but in my opinion this information should go in the
commit message and no commit without message should
company merges a patch submitted by another employee from the same company, for
a board provided by the same company)
Thanks
Alin
-Original Message-
From: Alan C. Assis
Sent: den 8 mars 2023 19:15
To: dev@nuttx.apache.org
Cc: Sebastien Lorquet
Subject: Re: DISCUSSION - Usage of mailing
This needs to be in its own thread.
Your collection of boards probably got some historical value.
Sebastien
On 3/8/23 23:31, Gregory Nutt wrote:
Slightly different topic: I have almost every board that ever ran
NuttX from about 2005 through 2020 or so. That is probably several
hundred
You are right about posix compliance, this is a valuable goal, but at
the same time it raises the hard remark:
At some point NuttX will grow too large for deep embedded platforms.
Sebastien
On 3/8/23 21:41, Gregory Nutt wrote:
Historically, whenever we find a POSIX issue we have always fixed
Hi,
This is a good idea to better follow posix.
This is typically the kind of stuff that would have deserved a message
on the dev list to say:
Hey friends we are improving terminals, expect bugs because it's hard to
get right, oh btw apps need to be updated too, otherwise strange things
ull/7944
We are still growing as a project and people being more active in the
review process will go a long way, but we need the people to do that. While
I have not committed much code in sometime, I still try to scan through the
PRs in my inbox for content of interest.
--Brennan
On Wed, Mar 8, 2
(Espressif, Sony, NXP, etc).
BR,
Alan
On 3/8/23, Sebastien Lorquet wrote:
I dont think your point of view is very realistic. You seem to be
turning the situation into something that pleases you but is not really
compatible with what can be observed from outside.
In the archive for 2023
to the project.
BR,
Alan
On 3/8/23, Sebastien Lorquet wrote:
Hi,
I had a look and this mailing list is not made for human consumption.
No one has ever sent a message on it manually, right?
In practice, important changes are still NOT discussed on the DEV
mailing list.
You said yourself that &quo
.html?comm...@nuttx.apache.org to receive
all commits messages and discussions.
Everything is archived on apache side!
BR,
Alan
On 3/8/23, Sebastien Lorquet wrote:
Apache projects are required to use mailing lists for long term archival
purposes.
It seems to me that this project is avoiding that rule and
/readline_common.c#L644
The low-level serial driver should not echo just because /isconsole
/is true. Console echo is always handled by the application. I would
say that that is a bug.
On 3/7/2023 9:45 AM, Sebastien Lorquet wrote:
Hi,
I am connecting to my board using
python3 -m serial --raw
Apache projects are required to use mailing lists for long term archival
purposes.
It seems to me that this project is avoiding that rule and moved all
development to github
This is in contradiction with the Apache project rules.
I request clarification on this situation and requirement
Hi,
I am connecting to my board using
python3 -m serial --raw --eol cr /dev/ttyUSB0 115200
This has ALWAYS worked.
Today it does not work anymore.
Every character I send to NSH is echoed TWICE, see below just typing help:
--
seb@lap:~$ python3 -m serial
Greg,
Thanks. The commit link is there:
https://github.com/apache/nuttx/commit/e6227e19433c4999d500437d0a8a5c05f476ceb1
Here is the pull request
https://github.com/apache/nuttx/pull/8623
This pull request was written and reviewed by xiaomi (again) and only
ONE independent review (thanks for
The commit 03b164f59ce40a3f5677b0588af2aee8d9697bf6 tools/makefile: silent all
compile output
It has been reviewed and approved by several members
https://github.com/apache/nuttx/pull/8378
Best regards
Alin
-Original Message-----
From: Sebastien Lorquet
Sent: den 7 mars 2023 14:12
To: dev@nuttx.apache.org
S
made".
Sebastien
On 3/7/23 13:45, Nathan Hartman wrote:
On Tue, Mar 7, 2023 at 7:23 AM Tomek CEDRO wrote:
On Tue, Mar 7, 2023 at 9:24 AM Sebastien Lorquet wrote:
No
V=1 is an entirely different thing.
I dont want to see the output mangled with tons of arm-none-eabi-gcc
command lines.
en
On 3/7/23 09:50, alin.jerpe...@sony.com wrote:
Hi Sebastien,
I checked the logs and the lib_strsignal.c is untouched for a long time
I would start debugging with make -j1
Best regards
Alin
-Original Message-----
From: Sebastien Lorquet
Sent: den 7 mars 2023 09:26
To: dev@nuttx.apach
revert that?
Sebatien
On 3/7/23 09:50, alin.jerpe...@sony.com wrote:
Hi Sebastien,
I checked the logs and the lib_strsignal.c is untouched for a long time
I would start debugging with make -j1
Best regards
Alin
-Original Message-
From: Sebastien Lorquet
Sent: den 7 mars 2023 09:26
://community.apache.org/contributors/etiquette
BTW, the new building system is strange, but more clean.
I think it should at least give some users feedback, like a text
progress bar, etc.
For course it needs improvement, but you don't need to do this way.
BR,
Alan
On 3/7/23, Sebastien Lorquet wrote
What is this?
NuttX is broken.
I ran make distclean, used the same defconfig, and I get this:
CC: string/lib_strsignal.c string/lib_strsignal.c: In function 'strsignal':
string/lib_strsignal.c:169:7: error: duplicate case value
169 | case SIGWORK:
| ^~~~
No
V=1 is an entirely different thing.
I dont want to see the output mangled with tons of arm-none-eabi-gcc
command lines.
This stuff is another breakage
Sebastien
On 3/7/23 09:22, Marco Casaroli wrote:
Try
make V=1
On Tue, 7 Mar 2023 at 09:18, Sebastien Lorquet wrote:
Hi
Hi,
This morning I updated my working copy, ran git pull origin master and
rebuilt my OS
Now when I run make I get no output. But the cpu fan works.
Only the last line of the console shows text, there is no log makefile
anymore.
This is AWFUL!
What happened?
Was make updated by linux
Hi,
ESP32-C3 worked perfectly out-of-the-box for me so I guess it is "fully
supported"
Sebastien
Le 03/03/2023 à 15:48, Tomek CEDRO a écrit :
Hello world :-)
There is a platform support update request on RISC-V tech mailinglists
(see forward below).. on the referenced site I can see that
Oh come on you are just trying to circumvent the GPL here
Sebastien
Le 01/03/2023 à 15:50, Xiang Xiao a écrit :
On Wed, Mar 1, 2023 at 10:45 PM Alan C. Assis wrote:
oh, I just found it:
"The fee depends on the number of distinct Products in which Yaffs
will be used, and there is a base
I am not confortable with NuttX having features that you have to pay for.
In this case yaffs should be provided as an external patch, but should
not be in mainline.
At the very least such features should not be advertised on public websites.
That is just my opinion but I find it good to
lly return -ENOSYS or -ENXIO
(cant remember).
Sebastien
Le 01/03/2023 à 15:41, Sebastien Lorquet a écrit :
the callbacks are not activated by conditional compilation and are in
the middle of struct mtd_dev_s , so how are these optional?
Sebastien
Le 01/03/2023 à 15:36, Xiang Xiao a écrit :
the callbacks are not activated by conditional compilation and are in
the middle of struct mtd_dev_s , so how are these optional?
Sebastien
Le 01/03/2023 à 15:36, Xiang Xiao a écrit :
On Wed, Mar 1, 2023 at 10:26 PM Sebastien Lorquet
wrote:
Hi,
Please dont break the mtd
Hi,
Please dont break the mtd interface, make it compatible with the
previous one.
Sebastien
Le 01/03/2023 à 14:53, Xiang Xiao a écrit :
On Wed, Mar 1, 2023 at 8:43 PM Alan C. Assis wrote:
Hi Xiang Xiao,
This is a great news, but I'm afraid yaffs is not a good option for
everybody
1 - 100 of 204 matches
Mail list logo
