> In NuttX 9.1.0, how can I add my own board-specific drivers?
You do that by providing a driver folder in your board.
nuttx/drivers/platform always points to nuttx/drivers/dummy because
you don't have a driver folder.
Note that "common" and "drivers" were added at about the same time and
the or
├── driver.h
> ├── Kconfig
> └── Make.defs
>
> But still it does not work.
>
> Any ideas what may break it?
>
> Στις Τρί, 11 Αυγ 2020 στις 5:39 μ.μ., ο/η Abdelatif Guettouche <
> abdelatif.guettou...@gmail.com> έγραψε:
>
> > > In NuttX 9.
> It's the drivers/Kconfig that
defines it (i.e. you add it), you can then enable it from menuconfig.
To be clear I meant the "drivers" folder that's linked to "platform"
not the toplevel nuttx/drivers.
On Wed, Aug 12, 2020 at 12:51 PM Abdelatif Guettouche
wro
As far as I can tell it's the same, current master[1], 9.1[2], 9.0[3], 8.1[4]
I do have some flashes about the necessity of a drivers folder
alongside the board folder with custom boards, but I can't remember.
That was an issue, it's now resolved.
> But the code is not included in the build. I che
they be located, instead of implying things.
>
> Or, at a minimum, I believe CONFIG_SPECIFIC_DRIVERS could be defined in
> nuttx/drivers/Kconfig. Since the build system uses this symbol, nuttx
> should define it, instead of relying on external Kconfigs.
>
> Στις Τετ, 12 Αυγ 2020
.μ., ο/η David Sidrane <
> david.sidr...@nscdg.com> έγραψε:
>
> > I am volunteering to help test any of these type changes. There were many
> > subtle breakages in the past that tended to slip through. Also once all
> > this
> > settles out, it so needs to be docu
It's PR1571, there was no need to update any config as I kept the same name.
On Wed, Aug 12, 2020 at 3:51 PM Abdelatif Guettouche
wrote:
>
> I'll provide a PR for review.
> The change by itself is simple, we just need to add one config option
> to nuttx/drivers/Kconfig
tory.
>
> Best,
> Matias
>
> On Wed, Aug 12, 2020, at 12:13, Abdelatif Guettouche wrote:
> > It's PR1571, there was no need to update any config as I kept the same name.
> >
> > On Wed, Aug 12, 2020 at 3:51 PM Abdelatif Guettouche
> > wrote:
> > &g
> Seems doable. Does anyone have any objections to me creating a board like
this for NuttX?
Not from me, I think with Github's projects (or milestones) and
consistent labeling of issues and PRs people would have a better
overview.
Anyone can then follow the development of the feature of interest.
> Well I just made a board for us:
Was it intentional to create it in Apache's and not here:
https://github.com/apache/incubator-nuttx/projects?
On Wed, Aug 12, 2020 at 7:39 PM Gregory Nutt wrote:
>
> Jira is another option available to us.
>
>
We've already agreed on the version numbering. It's pretty much the
same as it was + the patch number. So if there is incompatible change
to the APIs, we need to bump the major number to 10.
> wouldn't you like to create a milestone for next version as well?
We used Github Project last time to
Just a reminder, the N.O.W is live on youtube, we still have a couple
of presentations for today, you can join us from the link below.
https://www.youtube.com/watch?v=t49wq_ovT50
You must be missing CONFIG_TELNET_CHARACTER_MODE
On Sun, Aug 16, 2020 at 3:32 PM Oleg Evseev wrote:
>
> Hi Alan,
>
> I can open an issue, but I can't check the latest NuttX master in the near
> future, so I would like not to additionally disturb people yet :)
>
> вс, 16 авг. 2020 г. в 17:07, Alan
> If you can make LVGL optionally NOT generate its own config.h and .config we
> could indeed just include the Kconfig and Make.defs (as it is done now).
I think generating the config file would be part of a "toplevel" LVGL
build system which we would completely bypass.
> maybe allowing LVGL use
Generating the Kconfig file has to be done during preconfig otherwise
anything kconfig related won't work. We can't source a file that
doesn't exist yet.
As it is now LVGL is downloaded during context (the usual), I think
sourcing or just copying the Kconfig file from the LVGL folder would
cause t
Maybe we keep a dummy Kconfig and override it during context?
(thinking out loud...)
On Wed, Aug 26, 2020 at 3:49 PM Abdelatif Guettouche
wrote:
>
> Generating the Kconfig file has to be done during preconfig otherwise
> anything kconfig related won't work. We can't source a
I've been checking the last release's date this morning.
I think it's about time we started planning for the next release. We
had a talk the other day about the incompatibility of certain changes
with earlier releases and if we should bump the major number. I guess
the general consensus was to *
> Do we want to adopt that?
Yes this is what we agreed on.
> Oh the reason for 8.x to 9.0 was a sort of potential
"incompatibility": We changed the version number because the license
begins to change from BSD to Apache. That could be considered
"incompatible" to some users.
I'd also like to add
> providing
> > > > > > an I2C driver, and use it without ever caring about the actual
> > board.
> > > > > >
> > > > > > How I actually plan to use it.
> > > > > > I want to make various "driver packs"
We also had the discussion after entering the incubator and if I'm not
mistaken mentors have said that it's possible to bring those
repositories under Apache.
Maybe we should take the initiative and try to move forward with this.
On Mon, Sep 21, 2020 at 8:25 PM Nathan Hartman wrote:
>
> On Mon, S
quot;
> I believe Greg did this before but we only had a discussion, we didn't
> reach an agreement.
> This time, it's more of a heads up, unless someone has an objection.
>
On Mon, Sep 21, 2020 at 11:08 PM Nathan Hartman
wrote:
> On Mon, Sep 21, 2020 at 3:51 PM Abdelati
I'm clicking the send button too fast... I meant we wait for some time (72
hours?) If no one has an objection we go ahead and create the new repos.
On Tue, Sep 22, 2020, 16:26 Abdelatif Guettouche <
abdelatif.guettou...@gmail.com> wrote:
> Sorry, dropped the dev list..
>
>
> Would you like to start that thread (I'd recommend a [DISCUSS] in the
subject) or shall I?
I did.
On Wed, Sep 23, 2020 at 2:33 PM Nathan Hartman
wrote:
> On Tue, Sep 22, 2020 at 10:29 AM Abdelatif Guettouche
> wrote:
> >
> > > The question is: what do we ha
Hi,
We have had discussions on several occasions regarding the GPL licensed
Buildroot and Tools repository. We were told that it's possible to make
exceptions to well-known projects and host them under Apache.
We would like to come to a final decision and move forward with this.
Is there anythi
Was this resolved?
Anthony, your name is now present here:
https://github.com/orgs/apache/teams/nuttx-committers/members which means
you should have access now.
On Thu, Sep 17, 2020 at 5:02 PM Nathan Hartman
wrote:
> Hi folks,
>
> Can we get this sorted out please:
>
> On Thu, Sep 17, 2020 at 10
> I did notice a fair number of patches for bug fixes this week that we may
> want to be applying to this release including the spresense and esp, but
> there may have been others as well. It would be nice if those could be
> backported as needed prior to cutting the RC.
Regarding Xtensa/ESP32, I
y to add PRs to different columns depending
on labels. Did anyone use that before? If that's usable we can
create the 10.1 Project now.
Also, we finished working on the old 9.1 Project, it should be close, right?
On Sat, Oct 10, 2020 at 10:49 AM Abdelatif Guettouche
wrote:
>
> >
> root@edi-laptop:/mnt/d/Work/Development/Git/GitHub/nuttx# make V=1
> make -C tools -f Makefile.host mkconfig.exe
> I also checked the tools directory and there is a mkconfig.exe
When you build using Ubuntu for Windows 10 you get a *.exe file?
The error is that tools/mkconfig is not found. This
It looks like the extension got messed up. If that's the case
renaming mkconfig.exe to mkconfig should at least build.
On Tue, Oct 13, 2020 at 10:45 PM Eduard Niesner wrote:
>
> Yeah, there is definitely something wrong - I just tried again (ubuntu for
> windows 10).
>
>1. Cleaned everythin
ted a better way.
Ah okay, good! Feel free to delete the Project I just created then. We
will use your script once finished.
On Tue, Oct 13, 2020 at 10:42 PM Brennan Ashton
wrote:
> On Tue, Oct 13, 2020, 2:12 PM Abdelatif Guettouche <
> abdelatif.guettou...@gmail.com> wrote:
>
&
he PR description, commits
messages or changed files.
All these tools combined would help tremendously.
On Wed, Oct 14, 2020 at 10:08 AM Brennan Ashton
wrote:
>
> On Tue, Oct 13, 2020, 2:59 PM Abdelatif Guettouche <
> abdelatif.guettou...@gmail.com> wrote:
>
> > >
Can someone please merge the backport PRs?
Brennan, now that the cards are in place, we will continue sorting
them as we did last time? I added some minor PRs to their column the
other day.
On Wed, Oct 14, 2020 at 10:13 PM Abdelatif Guettouche
wrote:
>
> That did the job! Thanks! It
f testing last weekend. Hopefully we
> can cut an RC Sunday or Monday at the latest.
>
> --Brennan
>
> On Sat, Oct 17, 2020, 1:16 AM Abdelatif Guettouche <
> abdelatif.guettou...@gmail.com> wrote:
>
> > Can someone please merge the backport PRs?
> >
> >
Thanks Brennan! That was a lot of work!
On Mon, Oct 19, 2020 at 6:25 AM Brennan Ashton
wrote:
>
> On Sat, Oct 17, 2020 at 6:37 AM Abdelatif Guettouche
> wrote:
> >
> > Thanks for merging, Brennan!
> >
> > I'll work on some more today.
> > It'd be
It's nice to revive this discussion.
As I was saying in Github, I don't see a "not too awkward" way to
include the Kconfig file directly and use it as any Kconfig we have.
BTW, is LVGL going to provide a script to convert the Kconfig to a
lv_config.h of some sort? If that's the case we'll only h
> What I mentioned previously is that maybe it can be done so that
> > they can accept an external header providing the Kconfig defitions
> > (in our case nuttx/config.h).
> >
> > Or maybe I'm missing something...
> >
> > On Sat, Oct 31, 2020, at 20:27, Abdelat
I'll create a PR for this one.
The patch didn't apply cleanly so I did a search/replace.
On Fri, Nov 6, 2020 at 1:07 PM Gregory Nutt wrote:
>
> In case the attachment does not make it through the mailing list. I put
> the content inline below:
>
> Problem was introduced by patch "Re-rename the s
Any news on when we are going to be able to take a look?
On Fri, Nov 6, 2020 at 12:19 AM Alan Carvalho de Assis
wrote:
>
> Kudos Xiaomi
>
> We are glad to have you all here!!
>
> https://www.gizmochina.com/2020/11/05/xiaomi-launches-a-new-iot-software-platform-xiaomi-vela-based-on-nuttx-os/
The NuttX support in OpenOCD relies on post file hooks to get the offsets.
You don't need to reorder them. That's more flexible than tempering with
the TCB.
Other RTOSs that use fixed offsets require a certain configuration to be
used in order to use OpenOCD.
On Mon, Nov 23, 2020, 04:10 Matias N.
Sounds good. Will be testing on some hardware as well when the RC is cut.
On Mon, Nov 23, 2020 at 2:20 AM Brennan Ashton
wrote:
>
> I am looking to cut the RC0 early this week. There have been a lot of
> bug fixes that have gone in in the last few weeks (almost 60 patched
> backported), and I h
> This is what I tried and works. This is much better than being forced
> to use a specific configuration to get the offsets right or having to rebuild
> openocd each time.
> I will polish the approach and open a draft PR to show how it works.
As I said above, you don't have to do that. The Ope
>~"* 2 Thread 536871672 (Name: Idle Task, pid:0, RUNNING) 0x74a0 in
> >up_idle () at chip/nrf52_idle.c:191\n"
>
> >~" 5 Thread 536876144 (Name: init, pid:1, WAIT_SEM) 0x2000037c in g_idletcb
> >()\n"
>
>
> So for some reason the PC of
e
> could do the same
> to pass register addresses for other architectures and to set the array of
> state names?
>
> On Mon, Nov 23, 2020, at 14:12, Abdelatif Guettouche wrote:
> > Can you see that NuttX was detected and the offsets are correct from
> > OpenOCD?
+1
I checked:
- Valid GPG signatures.
- Valid checksums.
- Both repos contain LICENSE, NOTICE and DISCLAIMER files.
- Can build from source.
On Thu, Nov 26, 2020 at 2:53 PM Alan Carvalho de Assis
wrote:
>
> Hi Brennan,
>
> My vote: +1
>
> Great work! Kudos again!
>
> I want to suggest fo
> The "mux (almost) any peripheral to any pin" is great (any other chip does
> that?).
The ESP32 does that. Although, for better performance, there is a
selected group of pins for every peripheral.
Regarding the boards, right now I mostly use the ESP WROVER Kit.[1]
This board is populated with
The nightly build was building all the configurations which is better
coverage than the per PR we have.
Would be great to have it back. Doesn't matter if it's on Jenkins or elsewhere.
On Thu, Dec 24, 2020 at 3:55 PM Brennan Ashton
wrote:
>
> I never added it back after infrastructure moved Jenki
Unity (https://github.com/ThrowTheSwitch/Unity) is a test harness that
we can use both for applications and OS code. Isn't it better to have
it in libs/libtesting instead of apps/testing?
ld still be
> as
> > an application.
> >
> > --Brennan
> >
> > On Mon, Dec 28, 2020, 10:40 AM Abdelatif Guettouche <
> > abdelatif.guettou...@gmail.com> wrote:
> >
> >> Unity (https://github.com/ThrowTheSwitch/Unity) is a test harness that
> &g
t? You can always violate the kernel boundary for testing
> much like is done with some of the other tests in apps.
>
> On Mon, Dec 28, 2020, 11:13 AM Abdelatif Guettouche <
> abdelatif.guettou...@gmail.com> wrote:
>
> > The interface is actually configurable.
> >
>
Hmm... and I was blaming it on Github... Thanks for the heads up!
On Tue, Dec 29, 2020 at 7:23 PM Brennan Ashton
wrote:
>
> Hey just wanted to give people a heads up. Apache Intra has broken
> our CI with a change that just landed blocking almost all external
> Actions which we use in multiple p
> One problem was I didn't understand current CS definition. I thought
> #define GPIO_MCP2515_CS (GPIO_OUTPUT|GPIO_CNF_OUTPP|GPIO_MODE_50MHz|\
>GPIO_OUTPUT_SET|GPIO_PORTA|GPIO_PIN4)
> created a bitmask named GPIO_MCP2515_CS but no, it creates an ASCII string
> that do
ent for this being part
> of the generic SPI interface structure.
Some drivers do do that. They accept a "devno" argument in their init
function and then pass it with the SPI calls.
On Fri, Jan 8, 2021 at 7:41 PM Brennan Ashton wrote:
>
> On Fri, Jan 8, 2021
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,
> Nath
> 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
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 n
; ioctl(SIOCSIWSCAN): 25
> 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 P
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?
t 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
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, F
0 AM David 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 els
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 mat
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 Fl
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.
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 "side-effects"
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 th
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 b
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,
Mar 28, 2021 at 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 Guett
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
Looks like Apache's runners are having issues. Other projects using
Github Actions have stuck queues as well.
On Tue, Mar 30, 2021 at 10:04 PM Nathan Hartman
wrote:
>
> On Tue, Mar 30, 2021 at 3:30 PM Matias N. wrote:
> >
> > It appears we overwhelmed CI. There are a couple of running jobs (not
> 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 se
> 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 shoul
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. wrot
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
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
nsk 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
> 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:
ted, 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
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
https://github.com/apache/incubator-nuttx/blob/master/boards/risc-v/esp32
> 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 suggest
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 Mess
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: Nu
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
CON
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
gt; There is no way 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
../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
> 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:
>
a custom board"
> >
> > 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
> >
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 bre
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.
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
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:
>>
> > 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 an
> 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
bi
> 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 state
*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 contri
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 disc
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 on
> 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 want
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
1 - 100 of 319 matches
Mail list logo
