200KB should be the remaining SRAM size.
BLE uses 32KB of SRAM. I don't remember Wifi having a fixed carevout in
SRAM. Then there are other areas used by the ROM bootloader that can be
revoked once the system has fully booted.
On Fri, Apr 26, 2024 at 2:22 PM Nathan Hartman
wrote:
> I
If I remember correctly CONFIG_RAM_SIZE is not used for ESP32. And it was
supposed to be set to 0 to avoid confusion.
For ESP32 only the heap is a bit messed up. Many agents poke holes inside
the SRAM space for their own use. You can check
There is no threshold or a way to decide where malloc will get its memory from.
The memory available for the allocator is both the internal (SRAM) and
external SPIRAM, if your request cannot be honored from the internal
memory then the allocator will look into the external memory (but it's
not
We need to consider this:
https://www.apache.org/foundation/license-faq.html#Apply-My-Software
> Note that the Apache Software Foundation uses a different source header that
> is related to our use of a CLA. Our instructions for our project's source
> headers are here.
On Thu, Dec 15, 2022 at
nuttx and nuttx-apps for me too. For the hyphen, as it was said before
people can clone the repo under any name they want. We've been doing
this ever since we joined the incubator and this is how we're
instructing people too:
> Are there provisions to use a pre-downloaded tarball for external projects?
There is none at the moment. However, an option can be added to just
copy from a local folder instead of downloading them. Or the makefile
can start with that and fallback to downloading if the tarball is not
present.
+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 gone 72 hours without any
> > further issues raised [1]:
> >
> > This is a call to VOTE
Did you check the "external" directory or are you looking for something
else?
Basically the external directory allows you to symlink an out of tree
repository (or repositories) that should contain, at least, the minimal
build glues (Makefile and Make.defs). The build system should pick up the
There is an option for relative links. The you can pass the path to
configure.sh
Like configure.sh ../boards/custom-board/config/nsh
On Thu, Sep 15, 2022 at 12:25 PM TimH wrote:
> A few weeks ago I moved my custom board out of the NuttX
> "nuttx/nuttx/boards" tree to a folder
It would be nice to hear from the mentors or anyone from the IPMC.
On Wed, Jul 13, 2022 at 12:07 AM Nathan Hartman
wrote:
>
> Hi all,
>
> As this [DISCUSS] thread has quieted down for quite some days now,
> shall we have a [VOTE] thread or does anyone have additional thoughts
> to share?
>
>
, 2022 at 12:18 AM Nathan Hartman
wrote:
>
> On Mon, Jun 27, 2022 at 5:56 PM Alan Carvalho de Assis
> wrote:
> >
> > On 6/27/22, Abdelatif Guettouche wrote:
> > > For the checklist, there are two points where we gonna need external
> > > help, probably from
For the checklist, there are two points where we gonna need external
help, probably from our mentors:
1. Demonstrate ability to create Apache releases
2. Demonstrate community readiness
For the first one, Nathan has summarized above the work that has been
done. We believe that the project has
xes.
On Fri, Jun 24, 2022 at 12:43 PM Alan Carvalho de Assis
wrote:
>
> Very nice! Kudo guys!
>
> What are next steps?
>
> BR,
>
> Alan
>
> On Friday, June 24, 2022, Abdelatif Guettouche <
> abdelatif.guettou...@gmail.com> wrote:
>
> > Fi
First non-WIP release! One step closer to graduation!
On Fri, Jun 24, 2022 at 7:47 AM Tomek CEDRO wrote:
>
> CONGRATZ! :-)
>
> --
> CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
> 1) Using OpenOCD + GDB: some years ago Mr. Masayuki-san submitted
support to OpenOCD get thread awareness;
The current support in upstream OpenOCD is outdated. If you want to
use OpenOCD maybe you can try building from
https://github.com/Ouss4/openocd-esp32/tree/nuttx
Although I focused on
>From your .config file:
CONFIG_ARCH_BOARD_CUSTOM_NAME=""
CONFIG_ARCH_BOARD_CUSTOM_DIR=""
Please set these to their correct values.
On Thu, Jun 16, 2022 at 9:43 AM Abdelatif Guettouche
wrote:
>
> > No directory at /home/micha/nuttxspace/nuttx//src
>
&g
> No directory at /home/micha/nuttxspace/nuttx//src
It looks like you are trying to use a custom board but didn't set the
options and the path correctly.
On Thu, Jun 16, 2022 at 8:43 AM wrote:
>
> Dear all,
>
> I am new to Nuttx, and I try to port Nuttx to our ESP32 board. I
> followed this
+1 to release.
The only issue we had with the previous RC was the disclaimer, and now
it's there!
On Wed, Jun 8, 2022 at 8:17 AM Alin Jerpelea wrote:
>
> Hello all,
> Apache NuttX (Incubating) 10.3.0 RC4 has been staged under [1] and it's
> time to vote on accepting it for release. If approved
+1 for making it an ninfo (without the extra option).
On Thu, Jun 9, 2022 at 8:45 AM Michael Jung wrote:
>
> Hi Sebastien,
>
> I have this warning degraded to an informational message in my local
> repository for the exact same reason. In my opinion it should just be
> changed to informational.
Hi,
Regarding the disclaimer, the idea was to remove the WIP part _only_,
to end up with a standard disclaimer file and not a WIP disclaimer
file. [1]
I believe we are required to make at least one non WIP release to be
eligible for graduation and given all the work on licensing that has
been
Do you have the latest tags in your first version?
You can get them with: git pull upstream --tags
On Wed, May 25, 2022 at 4:22 PM Roberto Bucher
wrote:
> Hi
>
> I have a local version of nuttx, and an access to the incubator nuttx
> repository through the git remote with this configuration:
>
+1 to release.
I checked:
1. NOTICE, DISCLAIMER and LICENSE files exist.
2. Incubating in name
3. Can build from source.
Thank you Alin.
On Thu, May 5, 2022 at 12:34 PM Alin Jerpelea wrote:
>
> Hello all,
>
>
> Apache NuttX (Incubating) 10.3.0 RC2 has been staged under [1] and it's
> time to
+1 to release.
I checked:
1. NOTICE, DISCLAIMER and LICENSE files exist.
2. Incubating in name
3. Can build from source.
On Fri, Apr 29, 2022 at 7:35 AM Xiang Xiao wrote:
>
> +1.
> Test with checkrelease.sh.
>
> On Wed, Apr 27, 2022 at 4:01 PM Alin Jerpelea wrote:
>
> > Hello all,
> >
> >
> >
+1
I checked:
1. NOTICE, DISCLAIMER and LICENSE files exist.
2. Incubating in name
3. Can build from source.
Thank you Alin!
On Wed, Mar 30, 2022 at 6:50 PM Alin Jerpelea wrote:
>
> Hello all,
>
>
> Apache NuttX (Incubating) 10.3.0 RC0 has been staged under [1] and it's
> time to vote on
> Have a few custom boards in the test process. we're talking build
> testing, not runtime. No need for a farm.
We actually should do this. It should be possible to have a few
custom boards in another repository (the old testing repo for
instance) and trigger its workflow on PRs.
I believe once
I am OK with removing the disclaimer for 10.3.
Thank you for your work on this, Alin!
On Mon, Mar 28, 2022 at 2:32 PM alin.jerpe...@sony.com
wrote:
>
> Hi all,
>
> I am happy to announce the confluence release notes are ready and we can
> proceed with the NuttX 10.3-RC0 release
>
> @Nathan
;
> > >
> > > 6. tools/configure.sh ../my-folder/my-boards/custom-board/configs/nsh
> > >
> > > 7. make -j8
> > >
> > > Compilation failed, but not because of a common folder but because:
> > > "board/stm32_userleds.c:60:14:
>
> "It could be that they have an old board where the common folder
> structure didn't exist at the time and they don't want to change their
> structure." -- I think this is a weak argument as we change config
> option names sometimes as users are forced
> (set CONFIG_BOARD_STM32_COMMON=n for example with STM32 case).
>
> Or maybe I'm missing the exact use case. If yes, then please describe
> it more clearly and I will try to go through it to see if that can be
> achieved with the current code tree or not.
>
> Best regards,
> Petro
&g
> I think with NuttX 10.2.0 you do not need to perform the next steps any more.
These are necessary when someone is using a custom board without a
common folder copied from a board in-tree that contains a common
folder.
On Thu, Mar 3, 2022 at 11:31 AM Abdelatif Guettouche
wrote:
>
>
for me up to Nuttx version 10.2.0 but now when I try to
> > make I got the errors
>
> I think with NuttX 10.2.0 you do not need to perform the next steps any more.
>
>*Rename src/Make.defs to src/Makefile and append the line *
>include $(TOPDIR)/boards/Board.mk at th
> It seems like Daniel is hitting the same issue
Daniel is actually not using the common folder from the STM32
directory. This is why he had to do that renaming.
The issue is this:
https://github.com/apache/incubator-nuttx/blob/master/tools/Config.mk#L154-L156
Which is forcing a common directory
Please check the common/Make.defs file in-tree of the board you based your
custom board on. There is a new variable introduced.
(Sorry, writing from my phone. I'll try to send a direct link later.)
On Thu, Mar 3, 2022, 07:10 Petro Karashchenko
wrote:
> Hi,
>
> Do you want to use board common
Haltian has submitted an SGA and we can convert their license. You
must have an old tree since all their code now has the ASF header.
https://github.com/apache/incubator-nuttx/pull/4831
https://github.com/apache/incubator-nuttx/blob/master/drivers/usbmisc/fusb301.c#L1-L19
On Wed, Dec 1, 2021 at
Thanks for your work, Alin!
On Sun, Nov 28, 2021, 14:16 Alin Jerpelea wrote:
> The Apache NuttX (incubating) project team is proud to announce
> Apache NuttX 10.2.0-incubating has been released.
>
> The release artifacts and Release Notes can be found
> at:
>
Hi,
+1
I checked:
- Incubator in name
- LICENSE, NOTICE and DISCLAIMER files exist
- Signatures and checksum valid
- Can build from source.
On Tue, Nov 2, 2021 at 3:30 PM Nathan Hartman wrote:
>
> Summary:
> +1 to release (binding)
>
> Per Alan's request for size information:
>
> *
Is this loop from the 1st stage bootloader?
If that is the case, you only need to flash the 2nd stage bootloader.
You can get prebuilt binaries for that on
github.com/espressif/esp-nutt-bootloader and then from NuttX you can flash
with make download ESPTOOL_BINDIR=...
You can also build it
> I would be happy to delete the whole thing. Adbelatif has offered to
> delete the contents as well. But we would need consensus. A few people
> writing emails doesn't constitute consensus. That is why we have formal
> votes so that everyone's voice is heard and the direction is clear.
We
/rv32im/Toolchains.defs.
On Sat, Oct 16, 2021, 23:28 Tomasz CEDRO wrote:
> On Sat, Oct 16, 2021 at 6:15 PM Tomasz CEDRO wrote:
> >
> > On Sat, Oct 16, 2021 at 6:11 PM Abdelatif Guettouche
> > wrote:
> > >
> > > > I could not find detailed info
> I could not find detailed information on how to setup RISC-V toolchain
except just using "generic toolchain":
https://nuttx.apache.org/docs/latest/platforms/risc-v/esp32c3/index.html
There is a link there to download the toolchain used, here:
BTW the version of the OS we have there, is _very_ old. The description says:
> This is an old snapshot of NuttX from when arch/, configs/, and
> Documentation/ were submodules
On Sat, Oct 16, 2021 at 5:43 PM Abdelatif Guettouche
wrote:
>
> I can access it and deleting it is
is going on with those
> repositories.
>
> On Sat, Oct 16, 2021 at 9:09 AM Abdelatif Guettouche <
> abdelatif.guettou...@gmail.com> wrote:
>
> > People who have admin access to that org are all committers/PPMC members.
> > If we want to take it down we
People who have admin access to that org are all committers/PPMC members.
If we want to take it down we can do that.
As Greg mentioned earlier, that was supposed to host GPL repos and the os
and apps version there are outdated.
On Sat, Oct 16, 2021, 16:53 Tomasz CEDRO wrote:
> I have contacted
riginal Message-
> From: Abdelatif Guettouche
> Sent: den 12 oktober 2021 09:22
> To: Jerpelea, Alin
> Cc: Nathan Hartman ; Brennan Ashton
> ; dev@nuttx.apache.org
> Subject: Re: NuttX-10.2 release
>
> > Is there a tool to migrate the notes from github to cwiki?
>
> D
2:59 AM wrote:
>
> Hello all
> According to the proposed plan I will create the 10.2 branches today
>
> @Brennan Ashton @Nathan Hartman @Abdelatif Guettouche
> Can you please generate the RAW release notes so that I can continue
>
> Thanks
> Alin
>
> -Original
Ok, everything should be there. Once the biggest chunk was added I
ran it again on the smaller one.
On Mon, Oct 11, 2021 at 10:12 AM Abdelatif Guettouche
wrote:
>
> > I'm not sure if there is a trick to that or we have
> to add what's missing manually (about a hundred).
>
> Th
> I'm not sure if there is a trick to that or we have
to add what's missing manually (about a hundred).
The script is adding 750 now, it will take a few minutes.
On Mon, Oct 11, 2021 at 10:09 AM Abdelatif Guettouche
wrote:
>
> Hi,
>
> I'm trying to use https://github.com/b
missing manually (about a hundred).
On Mon, Oct 11, 2021 at 8:59 AM wrote:
>
> Hello all
> According to the proposed plan I will create the 10.2 branches today
>
> @Brennan Ashton @Nathan Hartman @Abdelatif Guettouche
> Can you please generate the RAW release notes so t
> When is next release planned with ESP32-C3 already included?
NuttX 10.1.0 already includes support for ESP32-C3 with a fair amount
of drivers including Wifi. BLE is on master however, and will be part
of the next release.
On Fri, Oct 8, 2021 at 6:26 AM Tomasz CEDRO wrote:
>
> On Fri, Oct 8,
> How, multiple slave devices can be used in this situation?
You can define as many CS pins as you need in your board logic. Then
in the corresponding spiXselect function, you enable the correct slave
based on its ID.
On Thu, Sep 30, 2021 at 8:47 AM murat tologlu wrote:
>
> Hi,
>
> I am
> How difficult should be the porting of the ESP32 processor to NuttX? It
is possible to use one of the Expressif configurations?
Yes it is possible. Most of the configurations should work on any board.
For special configs, if there is an external device required, then
that has to be there of
BTW, do we have a driver for MT25Q? I can't see one. Is it compatible with
the M25P series?
On Tue, Aug 24, 2021 at 5:50 PM Abdelatif Guettouche <
abdelatif.guettou...@gmail.com> wrote:
> > but I can't find the way to either mount it, or "probe" it, or anything,
> from
> but I can't find the way to either mount it, or "probe" it, or anything,
from nuttx.
The sequence to initialise the flash and mount NXFFS should look like the
following (to be adapted for chip and device):
spi = stm32_spibus_initialize(1);
if (!spi)
{
ferr("ERROR: Failed to
Please check your board/_path_/src/Makefile and check that your
CONFIG_ are all in the new format, i.e.: CONFIG_LIB_BOARDCTL to
CONFIG_BOARDCTL
On Wed, Aug 11, 2021 at 3:56 PM Simon Filgis
wrote:
>
> Hi Nathan,
>
> You mean this option?
>
>
> Makes no difference.
>
> I checked all the points in
> Regarding my advice from a few minutes ago. Somebody in
> https://github.com/apache/incubator-nuttx/issues/2206#issuecomment-721138548
> complains that
> the process is not working.
That's only when the board is part of a group that has the "common"
directory and the common directory isn't
What's the reason for symlinking the custom board to the in-tree
boards/ folder? The configuration script accepts a relative path to a
custom location.
On Tue, Aug 3, 2021 at 9:56 AM Simon Filgis
wrote:
>
> Dear all,
>
> I have my own board assembled with Atmel SAME70 and I would like to work
The biggest hardle we had was licenses. Alin has made significant progress
and converted most of what can be converted (maybe all). What we need to
do before graduation now is having a release without the WIP Disclaimer.
On Sun, Aug 1, 2021, 05:36 Nathan Hartman wrote:
> Hi all,
>
> As we
*So I've kicked that back in, but it appears I have to wait for a
(gasp)human**to push a button*.
This is actually a Github thing and is outside of our control. It's pretty
new too, so we too have to get used to it. As Nathan said, this only
applies to first time contributors. Subsequent
> Looking at NuttX source code, I couldn't find any example of an
> application that implements the ESP8266 functions. Is there any place
> where I can find reference for this use?
There is a separate application in apps/netutils/esp8266. I've never
tried it though, so I don't now about its
> Even if I dont get to vote in your committees I will
tell you if I find some problem.
You do get to vote, everyone can vote. It's actually helpful to have
more people voting and participating in the whole release process.
Voting for releases is done in the public dev list. PPMC members have
> > 2. Split up the ReleaseNotes file? As it is now, it reads a bit more like a
> > ChangeLog rather than ReleaseNotes. In the past we talked about a
> > Documentation/ReleaseNotes directory that could hold a separate
> > ReleaseNotes for each major version?
> >
> They are broken out per release
It's gonna be there: https://github.com/apache/incubator-nuttx-website/pull/52
On Fri, May 28, 2021 at 1:37 PM Maciej Wójcik wrote:
>
> Hmm, it looks like it is still missing here https://nuttx.apache.org/download
> (or is it intended for some reason?)
>
> On Wed, 26 May 2021, 10:28 , wrote:
Maybe this one could help:
https://cwiki.apache.org/confluence/display/NUTTX/NuttX+9.1#NuttX9.1-CompatibilityConcerns
> I am using the flat (monolithic build) and I see no place that define
>this flag, at all.
>I dont even see a place in the codebase that defines this flag.
__KERNEL__ is defined
Nice work! Thanks for the contribution!
On Mon, May 24, 2021 at 8:34 PM Janne Rosberg
wrote:
> Hi Alan,
>
> Yes, it has FPGA “build-in” so you can do very nice processing with that.
> Also 4+1 cores running on 600+Mhz so it’s almost a supercomputer.
> Let’s see what we can squeeze out of it.
That option was removed in 9.0, it only affects the SDCC compiler, I
think you can remove it in your case.
Here is a snippet from the release notes.
> * Compatibility Concerns
- The configuration option CONFIG_CAN_PASS_STRUCT is now
removed. Previously, it was used (at the cost of
"
> >
> > Also I woud advise against this common dir in boards, since it prevents
> > users from creating custom boards from built-in ones.
> >
> > Duplication is not always bad, as we know...
> >
> > Sebastien
> >
> >
> > Le 20/05/2021 à 15:27, Abdelatif Guettouche a écrit :
> >> Rename Make.defs to Makefile
> >
> Rename Make.defs to Makefile
To be clear, here I'm referring to ../boards/nucleo-f446re/src/Make.defs
On Thu, May 20, 2021 at 2:27 PM Abdelatif Guettouche
wrote:
>
> I just copied the nucleo-fe446re board without the common directory.
>
> Here are the steps I took:
> Add
../boards/nucleo-f446re/configs/nsh
make
Builds fine.
On Thu, May 20, 2021 at 2:14 PM Abdelatif Guettouche
wrote:
>
> (It looks like we dropped the list somehow, I'm bringing it back...)
>
> > There is no way this common file is going into my custom board.
>
> If you don't
this common file is going into my custom board.
>
> What to do? Do I need TWO custom dirs? One for the board and one for the
> custom stuff?
>
> Sebastien
>
> Le 20/05/2021 à 15:08, Abdelatif Guettouche a écrit :
> > It should then also be the same case as #2206, you'll ne
There is this issue that has more details, as well:
https://github.com/apache/incubator-nuttx/issues/2206
On Thu, May 20, 2021 at 12:44 PM Abdelatif Guettouche
wrote:
>
> Hi,
>
> Is it possible to share the defconfig? I just tried with an old one
> (based on STM32) and I hav
Hi,
Is it possible to share the defconfig? I just tried with an old one
(based on STM32) and I have a clean build.
The relevant configs that need to be correctly set are:
CONFIG_ARCH_BOARD_CUSTOM=y
CONFIG_ARCH_BOARD_CUSTOM_DIR="../boards/stm32/board-dir"
CONFIG_ARCH_BOARD_CUSTOM_DIR_RELPATH=y
Do we have any preliminary dates for the event?
On Tue, May 18, 2021 at 3:02 PM David Sidrane wrote:
>
> Please count me in.
>
> -Original Message-
> From: alin.jerpe...@sony.com [mailto:alin.jerpe...@sony.com]
> Sent: Tuesday, May 18, 2021 1:54 AM
> To: dev@nuttx.apache.org
> Subject:
Hi,
+1 :
- LICENSE, NOTICE and DISCLAIMER files exit in both repos.
- Signatures and checksums valid.
- Can build from source.
On Thu, May 6, 2021 at 8:40 AM wrote:
>
> Hi all,
>
> 72h have passed
> Can we get some votes to finish the 10.1 release?
>
> Thanks
> Alin
>
>
> -Original
> I'm not sure if there's support for custom-board common-code (in the same
> sense as for in-tree boards).
There is, it works the same way as the in-tree boards. But I think
what's being asked here is something common between different boards
of different architectures?
I think what you
If you want to use the I2C tool, you'll also have to register the i2c
driver from your board logic.
See:
https://github.com/apache/incubator-nuttx/blob/master/boards/arm/stm32f0l0g0/nucleo-g070rb/src/stm32_bringup.c#L89-L111
orted, not sure if the author saw it:
> https://github.com/apache/incubator-nuttx/pull/3613
>
> Best,
> Matias
>
> On Wed, Apr 28, 2021, at 10:46, Abdelatif Guettouche wrote:
> > > Wasn't the stack restructure behind the 10.1 release?
> >
> > Yes, but that change just expo
> Wasn't the stack restructure behind the 10.1 release?
Yes, but that change just exposed an old issue.
On Wed, Apr 28, 2021 at 2:45 PM Matias N. wrote:
>
> Wasn't the stack restructure behind the 10.1 release?
>
> Best,
> Matias
>
> On Wed, Apr 28, 2021, at 09:57, Gustavo Henrique Nihei wrote:
Thansk for reporing it
>
> Regards
> Alin
>
>
> On Sun, Apr 18, 2021 at 7:25 PM Brennan Ashton
> wrote:
>
> > On Sun, Apr 18, 2021 at 9:38 AM Abdelatif Guettouche
> > wrote:
> > >
> > > Is it just me or there is an issue with the checksum of the a
Is it just me or there is an issue with the checksum of the apps tar?
On Sun, Apr 18, 2021 at 3:06 PM Alin Jerpelea wrote:
>
> Hello all,
> Apache NuttX (Incubating) 10.1.0 RC0 has been staged under [1] and it's
> time to vote on accepting it for release. If approved we will seek
> final release
anager for 10.1
>
>
> Can you please point me to the checklist for the release
>
> Best regards
> Alin
>
>
> On Fri, Mar 19, 2021 at 8:46 PM Abdelatif Guettouche <
> abdelatif.guettou...@gmail.com> wrote:
>
> > Hi,
> >
> > Our latest release
What ESP32S? Is it ESP32-S2? Apparently there is an ESP32S chip from
a different company but from my understanding it's just an ESP32.
ESP32-S2 on the other hand is different from ESP32.
For an ESP32 camera board, maybe the ESP-EYE can work for you?
On Thu, Apr 1, 2021 at 3:49 PM Matias N.
> Anyway, I see the "other" includes a very long list of very different
> platforms. Maybe splitting it into avr, risc-v, xtensa could help?
When Xtensa was merged with "others" it had only 3 configs: nsh,
ostest and smp. Now it contains around 30, and surely more to come..
I agree that we
> Also, I agree about simplifying macOS build if it will help while we get to q
> better situation.
We can have a special test list for macOS that includes just a few
configs from the simulator and other chips.
> There has been some talk about supporting non hosted runners, but there are
some
wrote:
>
> Maybe we should create an issue to track that? Sounds like an important
> problem.
>
> On Sun, Mar 28, 2021, at 17:36, Abdelatif Guettouche wrote:
> > > Abdelatif, let me know if you want me to prepare the PR. If licensing is
> > > taken care of, I can si
t 11:33 PM Matias N. wrote:
>
> Abdelatif, let me know if you want me to prepare the PR. If licensing is
> taken care of, I can simply
> place Apache header and submit it myself, right?
>
> Best,
> Matias
>
> On Thu, Mar 25, 2021, at 19:05, Abdelatif Guettouche wrote:
&g
Matias N. wrote:
> >
> >
> > On Thu, Mar 25, 2021, at 15:21, Alan Carvalho de Assis wrote:
> >> Hi Matias,
> >>
> >> On 3/25/21, Matias N. mailto:matias%40imap.cc>> wrote:
> >> >
> >> >
> >> > On Thu, Mar 25, 2021,
Someone was asking the other day on Linkedin, so I pushed this:
https://github.com/Ouss4/MQTTC_NuttX
> Regarding SSL, is it required to build? Maybe it can be initially integrated
> without
SSL support?
You can use it with no SSL support. But MQTT-C supports multiple
crypto libraries, mbedTLS
Try: mount -t smartfs /dev/smart0 --> mount -t smartfs /dev/smart0 /mnt
On Mon, Mar 22, 2021 at 1:17 PM Flavio Castro Alves Filho
wrote:
>
> Hello Alan,
>
> Enabling the CONFIG_BCH, I could finally run flash_eraseall and
> mksmartfs commands.
>
> But the mount command is not working.
>
> Below
Please note that this issue has been fixed:
https://github.com/apache/incubator-nuttx-apps/pull/624
On Sun, Mar 21, 2021 at 6:03 PM Alan Carvalho de Assis
wrote:
>
> Hi Greg and Anthony,
>
> On 3/21/21, Gregory Nutt wrote:
> >
> >> ... what we can
> >> do to prevent these types of
Hi,
Our latest release was on December 6th. It's fair to say that we
should start planning for NuttX-10.1.
Last time Adam and Alin offered to be release managers, do you guys
still want to do that?
We can start by devising our plan and pick a date to create the branches.
Also, please check the top level LICENSE and NOTICE files for more information.
On Tue, Mar 9, 2021 at 10:46 AM Alan Carvalho de Assis
wrote:
>
> Hi Ganesh,
>
> I think you can use it without any issue.
>
> NuttX has been used in commercial products for over 10 years, some
> examples: Pixhawk
Hi,
I personally haven't used the PIC32 port in a while, but left it
working. At least the PIC32MZ one.
> Are my assumptions that I should just be able to build and run NuttX
on the explorer16/max32 incorrect?
This could work. However, you have to verify that the configurations
in board.h
Sidrane wrote:
>
> Are you getting duplicate same email a day later?
>
> -Original Message-----
> From: Abdelatif Guettouche [mailto:abdelatif.guettou...@gmail.com]
> Sent: Friday, February 05, 2021 2:47 AM
> To: dev@nuttx.apache.org
> Subject: Re: Anyone else gett
All of Gitbox emails are now going to commits@ which you can filter
out or simply unsubscribe.
On Fri, Feb 5, 2021 at 11:40 AM David Sidrane wrote:
>
> Anyone else getting repeated emails from the GitBox?
>
>
>
> -Original Message-
> From: GitBox [mailto:g...@apache.org]
> Sent: Friday,
oes not have these
> instructions.
> I cannot seem to connect though, not sure if it is because my router is set
> to WPA2 TKIP+CCMP.
>
> Best,
> Matias
>
> On Thu, Feb 4, 2021, at 20:06, Abdelatif Guettouche wrote:
> > Basically you can just check the commands in the wlan
We set it manually right?
I mean after reviewing we can set the PR to be merged when the CI
checks are done?
On Fri, Feb 5, 2021 at 10:53 AM David Sidrane wrote:
>
> Hi,
>
> I saw a new option for merging in GH Auto merge when CI completes.
>
> What is the group's opinion on having this enabled?
ERROR: Process command (scan) failed.
>
> Thanks,
> Matias
>
> On Thu, Feb 4, 2021, at 19:36, Abdelatif Guettouche wrote:
> > It could be because there are some issues with getting the paramters from
> > the flash. Please try disabling Save Paramters from the Wifi Configu
It could be because there are some issues with getting the paramters from
the flash. Please try disabling Save Paramters from the Wifi Configuration
menu.
On Thu, Feb 4, 2021, 11:32 PM Matias N. wrote:
> Hi,
> I'm trying to test WiFi support on ESP32 DevKitC (I used wapi config) and
> it does
> What's the purpose of "CONFIG_ESP32_SPI_SWCS" since the SPI CS pin can
> always be controlled by hardware?
Not always. It depends on the pins used. You can check
arch/xtensa/src/esp32/hardware/esp32_pinmap.h, if you use the set of
pins defined there then you don't need ESP32_SPI_SWCS.
There
Cheers!
On Wed, Jan 13, 2021 at 10:37 PM Nathan Hartman
wrote:
>
> We have surpassed our 40,000th commit in the main NuttX repository.
>
> Many thanks to all of our past and present contributors who helped get
> us this far over the years.
>
> Here's to the next 40,000 commits!
>
> Cheers,
>
1 - 100 of 303 matches
Mail list logo
