On Fri, Jul 31, 2020 at 9:46 AM Schock, Johannes - NIVUS GmbH <
johannes.sch...@nivus.com> wrote:
> Hello,
> I have two questions related PR#1478 (
> https://github.com/apache/incubator-nuttx/pull/1478):
>
> 1. I think there's a configuration error with "Build / macOS (sim)" since
> it is using -W
On Fri, Jul 31, 2020 at 10:55 AM Gregory Nutt wrote:
> > Hmmm... I don't agree.
> >
> > The Coding Standard encourages empty "while loops":
> > https://cwiki.apache.org/confluence/display/NUTTX/Coding+Standard#while
> > Why should this not applicable for "for loops"? I think there are many
> > al
On Fri, Jul 31, 2020 at 1:42 PM Gregory Nutt wrote:
>
> > Before we change the coding standard, I suggest that we get more
> > feedback from the dev community.
> >
> > My opinion: If a loop does not require a body, I suggest to use
> > braces, rather than a semicolon, because it is less prone to
On Sun, Aug 9, 2020 at 9:57 AM Fotis Panagiotopoulos
wrote:
> I just tried the following patch, and the code runs normally.
> Shall I make a PR?
Thank you for finding this. Yes, I think you should make a PR.
Nathan
On Tue, Aug 11, 2020 at 1:14 PM Fotis Panagiotopoulos
wrote:
The structure proposed by Xiang Xiao is not working for me.
>
> By looking in the Makefiles, I did understand that the structure has
> changed a bit.
> Now my structure is:
>
> ├── CustomBoard
> │ ├── defconfig
> │ ├── include
> │
On Wed, Aug 12, 2020 at 12:07 PM Gregory Nutt wrote:
>
> How/who would prioritize and
> schedule implementation of roadmap items? How could accomplish any of
> this with only a volunteer organization and no project management with
> any authority?
Open source tends to be driven by people scrat
On Fri, Aug 14, 2020 at 2:51 PM Gregory Nutt wrote:
>
> > Nathan started this here:
> > https://cwiki.apache.org/confluence/display/NUTTX/NuttX+9.2
> >
> > I would say let's fill that out, we can change it to 10.0 later. I
> > will kick off getting the tracking board and the PR changes going in
On Mon, Aug 17, 2020 at 4:28 PM Matias N. wrote:
> Hi everyone,
>
> just wanted to let you know in case it was lost in the sea of github
> notification emails that today I undraft the
> "new documentation" PR so that you can start reviewing it. Please have a
> look at the PR description to get a
On Sun, Aug 30, 2020 at 2:04 PM Gregory Nutt wrote:
> But look what happens under Cygwin:
>
> $ arm-none-eabi-gcc --print-file-name=libgcc.a
> c:/program files (x86)/gnu tools arm embedded/9
> 2019-q4-major/bin/../lib/gcc/arm-none-eabi/9.2.1/libgcc.a
>
> $ dir `arm-none-eabi-gcc --
On Tue, Sep 1, 2020 at 8:12 AM Bhindhiya Raja
wrote:
> Hello Team,
>
> We are working on adding pre-check support for Renesas RX65N MCU. We are
> getting the below warnings in the common files used across the Renesas MCUs
> (M16, SH1 and RX65N).
>
>
> 1. arch/renesas/src/common/up_blocktask.c:
I ran into a strange issue with serial init for STM32. If the UART is
already enabled/configured, our configuration does not seem to apply.
I discovered this because I used a bootloader to flash and run NuttX
on the arm/stm32/b-g474e-dpow1 board. The bootloader configs the UART
for 115200 baud 8E1
On Thu, Sep 3, 2020 at 7:38 PM Gregory Nutt wrote:
> Perhaps:
>
> Bit 10PCE: Parity control enableThis bit selects the hardware parity
> control (generation and detection). When the parity control is enabled,
> the computedparity is inserted at the MSB position (9th bit if M=1; 8th
> bit if M=0)
On Fri, Sep 4, 2020 at 9:46 AM Gregory Nutt wrote:
>
> > Sometimes the best results (on small systems) are obtained if boot loader
> > leaves the CPU as it found it out of reset.
> >
> > If you think in terms of an OOD life cycle: The "Destructor" for each
> block
> > reset the HW to the reset st
On Fri, Sep 4, 2020 at 11:30 AM David Sidrane wrote:
> I was not suggesting the fix should be in the boot loader, I was just
> commenting on what the right way to do a boot loader.
>
> I am sure the F4/F7 serial drivers deal with the PE bits. It has many test
> cases in the RC lib of PX4, it the l
On Fri, Sep 4, 2020 at 9:40 AM Bhindhiya Raja
wrote:
>
> Hello Nathan,
>
> Thank you for your response. We have submitted 2 separate PRs as recommended
> by you to resolve warnings 6 (#1695) and 8 (#1702).
>
> About warnings 1 to 4, we understand that casting away the 'volatile' type
> qualifier
On Wed, Sep 9, 2020 at 5:50 PM Daniel Mesham wrote:
> I am attempting to port NuttX to the STM32L431CC on a custom board. I have
> done so by copying the config for the Nucleo-L432KC board, using pretty much
> the same procedure as described here:
> https://groups.google.com/g/nuttx/c/3p1ZF1lS8
Hi folks,
There have been many big changes since the last release including work
focused on reducing memory footprint, a major overhaul of the
documentation, and countless other things.
We should get the next release started sometime soon. Is there anything in
particular that we should wait on be
On Sun, Sep 13, 2020 at 6:40 PM Gregory Nutt wrote:
>
> > I've been assiging various PRs from both repos to 10.0 milestone.
> > Please also see if you think not assigned ones are to be surely included
> > and assign them. I've not done this with issues as many are old ones
> > for which no PR was
On Sun, Sep 13, 2020 at 6:40 PM Gregory Nutt wrote:
> Going from 8.x to 9.0 did not follow these rules. There was not
> particular incompatibility at all. The major number changed only
> because it was the first Apache release. Other people have suggested
> boosting the major number to celebrat
On Thu, Sep 17, 2020 at 9:26 AM Gregory Nutt wrote:
>
> > An alternative is to use a workflow. For example this action does
> something in that line:
> https://github.com/marketplace/actions/pull-request-ticket-check-action
> >
> I think including the a PR comment check in the PR checks is a grea
On Thu, Sep 17, 2020 at 10:02 AM Gregory Nutt wrote:
>
> > That's why we have committers. It's been said, but I'll repeat: As
> > committers, I know it's mundane, but we really need to make sure the
> commit
> > and PR messages will be helpful to someone who looks at them in the
> future.
>
> But
Hi folks,
Can we get this sorted out please:
On Thu, Sep 17, 2020 at 10:25 AM Anthony Merlino wrote:
>
> FYI: I STILL do not have access to the Github organization.
>
> I have tried changing my email everywhere in apache to match my primary
> email on Github. I've tried re-adding my Github accou
On Fri, Sep 18, 2020 at 3:17 PM Flavio Castro Alves Filho
wrote:
> I am studying NuttX for a new project. I am using Nucleo-F429ZI as
> reference, which is quite a complete board and has a large memory for
> testing.
>
> I followed some instructions from the internet (mostly from NuttX
> website)
On Sat, Sep 19, 2020 at 7:36 AM Flavio Castro Alves Filho
wrote:
> The problem that I am facing now is that is that the network interface
> is not initializing:
>
> nsh> ifconfig
> nsh: ifconfig: opendir failed: 20
Need to mount procfs for ifconfig to work.
nsh> mount -t procfs /proc
Nathan
On Wed, Sep 16, 2020 at 12:33 PM patacongo wrote:
> I will also remove the Bitbucket mirrors of the Apache repositories.
What is the "official" new location of the tools, buildroot, and
uclibc repositories?
On Mon, Sep 21, 2020 at 1:47 PM Gregory Nutt wrote:
> >> I will also remove the Bitbucket mirrors of the Apache repositories.
> > What is the "official" new location of the tools, buildroot, and
> > uclibc repositories?
>
> They are still at https://bitbucket.org/nuttx/ but are not getting much
>
e should take the initiative and try to move forward with this.
>
> On Mon, Sep 21, 2020 at 8:25 PM Nathan Hartman
> wrote:
> > I am wondering what happened to the discussion that happened very
> > early, before the incubator voted to accept our podling, when we were
>
On Tue, Sep 22, 2020 at 10:29 AM Abdelatif Guettouche
wrote:
>
> > The question is: what do we have to do to move this forward?
>
> I suggest we start by creating a new thread with a clear title,
> something like "Move GPL licensed repos "Buildroot, kconfig-front-ends
> and tools" under Apache"
>
On Wed, Sep 23, 2020 at 9:33 AM Matias N. wrote:
> also sounds good. During that week we could take all issues and PRs with
> unassigned
> milestone in GH and assign them to 10.0 or to an "untargeted" or "future"
> release.
> Those with 10.0 milestone should be merged/addressed to include in rel
On Sat, Sep 19, 2020 at 9:07 PM wrote:
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, October 07).
>
> Please submit
On Wed, Sep 23, 2020 at 9:55 AM Matias N. wrote:
>
> Ok, I created the "future" milestone for this. We should try to get all PRs
> issues in either
> of these two milestones during that week.
>
> Also, I'm not sure how you're finding all PRs for this release to build
> release notes, but one pos
> On Mon, Sep 21, 2020, at 13:34, Nathan Hartman wrote:
> > Need to mount procfs for ifconfig to work.
On Wed, Sep 23, 2020 at 10:48 AM Matias N. wrote:
> It would be really helpful if the "procfs" word appeared in that error. That
> error is really cryptic.
Agreed.
On Wed, Sep 30, 2020 at 2:44 AM Anjana
wrote:
> Hello Team,
>
> In arch/Kconfig, for Renesas architecture, the configuration ARCH_NOINTC
> is selected as mentioned below :
>
> config ARCH_RENESAS
> bool "Renesas"
> select ARCH_NOINTC
> select ARCH_HAVE_INTERRUPTSTACK
> ---help---
> Renesas archit
On Wed, Oct 7, 2020 at 12:11 PM Matias N. wrote:
> Hi,
> I think that for any non-coding/boring task the best bet (barring a paid
> employee)
> is to crowdsource the effort. You could compare this to the task of
> enforcing code style:
> it would be a huge task to convert all NuttX files to follo
On Thu, Oct 8, 2020 at 11:22 PM Matias N. wrote:
>
> > We need all of the above:
> >
> > 1. Integrate license clearing with ongoing work like we are already doing
> > for nxstyle, *AND*
>
> I've created the following issue to remind ourselves of this:
>
> https://github.com/apache/incubator-nuttx
On Wed, Oct 7, 2020 at 12:11 PM Matias N. wrote:
> I think that for any non-coding/boring task the best bet (barring a paid
> employee)
> is to crowdsource the effort. You could compare this to the task of enforcing
> code style:
> it would be a huge task to convert all NuttX files to follow the
On Fri, Oct 16, 2020 at 1:28 PM Eduard Niesner
wrote:
> I attached it as .txt.
>
> *Please note:* I made the code build and the SPI seems to work
> as expected - I am communicating with an at45db flash over SPI and mounted
> smartFS on it and the communication seems to work. I am not sure if
> th
On Wed, Oct 21, 2020 at 2:26 PM wrote:
> Thats correct... so I have to start the conversion every time over
> again... and het the value after that conversion I have seen continuous
> conversions ADC on an STM32...
>
> I will try to find a plausible solution.
>
Zero latency ISR to read ADC
On Fri, Oct 23, 2020 at 12:20 PM Alan Carvalho de Assis
wrote:
> Hi Everyone,
>
> Sparkfun just created an interesting board ecosystem that could let
> people to replace the MCU module and still having access to the base
> board features:
>
> https://www.sparkfun.com/micromoddev
>
> https://www.s
On Tue, Oct 27, 2020 at 4:09 AM Xiang Xiao
wrote:
> On Tue, Oct 27, 2020 at 7:43 AM Matias N. wrote:
>
> > As Greg mentioned in the corresponding open issue, TizenRT took Greg's
> > snippets from the Wiki page and mostly implemented that. Couldn't really
> > find more changes than that, so I'm n
On Tue, Oct 27, 2020 at 10:03 AM Matias N. wrote:
> Hi Nathan,
> as I mentioned in my previous email, this isn't about overhead, is about
> other ISRs delaying mine.
I didn't see your reply until after, but Zero Latency Interrupts should
more aptly be called Zero Jitter Interrupt, because jitte
On Tue, Oct 27, 2020 at 10:21 AM Alan Carvalho de Assis
wrote:
> Hi Nathan,
>
> I totally agree! Zero Jitter Interrupt is a better name.
>
> We don't have zero latency, we have zero jitter.
>
> BR,
>
> Alan
The latency is pretty close to zero too, because it interrupts whatever
else is happenin
On Wed, Oct 28, 2020 at 1:10 PM Matias N. wrote:
> I'm okay with ns jitter. I need to satisfy a 150uS timing response, so
> that is OK.
>
> Outside the context of RTOSs, isn't this just defining your own interrupt
> handler? Maybe
> it should be called "custom interrupt handler"?
>
Well I think
For STM32 family, DAC register mappings are defined in
arch/arm/src/stm32/hardware/stm32_dac.h.
In STM32Gx parts, the DAC has additional features and registers
not in STM32Fx and STM32Lx parts.
I propose to handle this as follows:
* Rename stm32_dac.h to stm32fx_dac.h
* Create a n
On Wed, Oct 14, 2020 at 9:54 AM Matias N. wrote:
>
> The scripts are still in a draft PR, they were not merged. I was waiting for
> confirmation for others to test.
> The remaining issue was about the ability to deal with files in submodules.
> Right now it just errors out.
> I will see I can ad
Is there a mistake in the following comment in include/nuttx/clock.h?
[[[
/* If CONFIG_SCHED_TICKLESS is not defined, then the interrupt interval of
* the system timer is given by USEC_PER_TICK. This is the expected number
* of microseconds between calls from the processor-specific logic to
*
Thanks for confirming. I submitted PR #2378
Cheers,
Nathan
On Sun, Nov 22, 2020 at 5:15 PM Alan Carvalho de Assis
wrote:
> You are right, it should be 100Hz instead 100KHz.
>
> On 11/22/20, Nathan Hartman wrote:
> > Is there a mistake in the following comment in includ
Some months ago I implemented the basic architectural support for
STM32G47xxx and I noticed that occasionally, during startup, I am
getting stuck in _up_assert(). It is not happening consistently. It's
intermittent. I'm not really sure why. Any ideas what I should look
for? Here is the backtrace:
On Mon, Nov 23, 2020 at 5:18 PM Gregory Nutt wrote:
> You can try the section on hardfault debugging here:
> https://nuttx.events/wp-content/uploads/2019/11/DSidrane_nx2019.pdf That
> starts at slide 17:
>
> /Set a breakpoint on up_hardfault and up_assert//Set the PC equal to
> the LR//Se
On Thu, Nov 26, 2020 at 3:36 AM Brennan Ashton wrote:
>
> Hello all,
> Apache NuttX (Incubating) 10.0.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 approval from the IPMC. Voting will be open for 72hr.
Summary:
+1 to
Hi Justin,
Did you intend to vote on the IPMC thread?
Thanks,
Nathan
On Wed, Dec 2, 2020 at 9:11 PM Justin Mclean
wrote:
> Hi,
>
> +1 (binding) but a lot more needs to be done on the LICENSE and headers
>
> I checked:
> - incubating in name
> - DISCLAIMER exists
> - a good start have been made
On Sun, Dec 20, 2020 at 12:57 AM ElzPyiV wrote:
>
> Hello,
>
>
> nuttx-10.0.1/arch/arm/src/stm32h7/hardware/stm32h7x3xx_memorymap.h
>
>
> #define STM32_SRAM3_BASE0x3004c000/* 0x3004-0x30047fff: System
> SRAM3 */
>
>
> Why "0x3004c000" ? Why not "0x3004"
>
>
> Thanks.
Looks like a
On Mon, Dec 21, 2020 at 8:11 AM Gregory Nutt wrote:
> The version in NuttX is based off an older version of SPIFFS (before all
> of the security related changes) and may have incompatibilities with the
> current SPIFFS.
>
> On 12/20/2020 11:26 PM, Takashi Yamamoto wrote:
> > hi,
> >
> > a questio
While working on our board report, I noticed that the nightly build is
no longer found at
https://s.apache.org/wnv2u
Is it still running? If so, where is the new location?
Thanks,
Nathan
On Mon, Dec 28, 2020 at 10:40 AM John Rippetoe
wrote:
> I have actually implemented the FDCAN driver for the H7, but have yet to
> submit a pull request because of a lingering bug I haven't had the time
> to sort out. I could clean up my code and push it to personal repo if
> you wanted to play ar
On Thu, Dec 31, 2020 at 9:48 AM Grr wrote:
> Hello to all.
>
> I'm new into NuttX development and I made an ASCII-art function map of
> NuttX initialization to hep update and improve
>
> https://cwiki.apache.org/confluence/display/NUTTX/NuttX+Initialization+Sequence
> and I'd like to know of Bren
On Thu, Dec 31, 2020 at 10:03 AM Maciej Wójcik wrote:
>
> Hello,
>
> I would suggest making merge request to the documentation inside
> repository. Confluence document could be copied there and then ascii art
> added.
>
> But it is my personal opinion. Not sure what was decided about confluence
>
How do we want to handle mixed case identifiers such as LTDC_LxBFCR_BF1,
LTDC_LxBFCR_BF2, LTDC_LxCFBLR_CFBLL, LTDC_LxCFBLR_CFBP, LTDC_LxCR_CLUTEN,
LTDC_LxCR_COLKEN, LTDC_LxCR_LEN, LTDC_LxWVPCR_WVSPPOS, LTDC_LxWVPCR_WVSTPOS,
STM32_LTDC_LxWHPCR_WHSTPOS, STM32_LTDC_LxWVPCR_WVSTPOS, and
STM32_LTDC_Lx_B
On Thu, Dec 31, 2020 at 1:27 PM Gregory Nutt wrote:
> I just use uppercase 'X' instead.
Ok that's what I'll start doing.
Thanks,
Nathan
I made a custom board using STM32H7 with KSZ8081 Ethernet PHY.
Then I noticed it is necessary to setup CONFIG_STM32H7_PHYSR,
CONFIG_STM32H7_PHYSR_ALTCONFIG, CONFIG_STM32H7_PHYSR_ALTMODE,
CONFIG_STM32H7_PHYSR_10HD, CONFIG_STM32H7_PHYSR_100HD,
CONFIG_STM32H7_PHYSR_10FD, and CONFIG_STM32H7_PHYSR_100F
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,
Nathan
On Fri, Jan 15, 2021 at 10:53 AM Thiha Kyaw wrote:
>
> Dear Nuttx,
>
> I found Digital Signal Processing Library option in Nuttx 10.0.1.
>
> Can you guide me where I can read the documentation to use DSP library?
>
> Thanks.
> --
> Yours Sincerely,
> Thiha Kyaw
Dear Thiha,
Normally I would sugg
On Sun, Jan 17, 2021 at 8:43 AM Flavio Castro Alves Filho <
flavio.al...@gmail.com> wrote:
> Hello,
>
> I am working to port NuttX on a board based on STM32F4DISCOVERY. The
> microcontroller is the STM32F407VET6.
>
> USB CDC support is not initializing.
>
> When I plug the USB on the board, I have
On Sun, Jan 17, 2021 at 11:36 AM Grr wrote:
> Have you tried starting from original, working config and adding and
> testing after _every single_ change?
>
> If you're changing OS elements, maybe one of them is affecting USB without
> you knowing
>
> Testing at every change is tedious but sometim
On Sun, Jan 17, 2021 at 1:34 PM Grr wrote:
>
> Sort of binary search? You're right, that's faster. I tend to see it like a
> sequence rather than a searchable collection
Oh yes, bisect does a binary search of a sequence of commits to find
the one that broke something. I've used it to find which c
Hi folks,
Last year we received 50 ICLAs and 7 SGAs. That is a big
accomplishment and should cover a significant chunk of our code.
It's also a springboard for the next big thing: Let's get closer to
Graduation from the Incubator! The most important step remaining is to
make a dent in license cle
On Fri, Jan 22, 2021 at 3:16 AM wrote:
>
> Hi Nathan,
>
> Count me in
>
> Regards
> Alin
On Sat, Jan 23, 2021 at 7:51 AM Xiang Xiao wrote:
> Nathan, thanks for raising the proposal.
> We want to join the license clearing effort and will resolve some
> engineer resource for it in this year.
Than
On Sun, Jan 31, 2021 at 9:53 PM Maxim Solodovnik
wrote:
> Hello Alan,
>
> On Mon, 1 Feb 2021 at 04:36, Alan Carvalho de Assis
> wrote:
>
> > Thank you Sallu, Maxim and Kevin!
> >
> > We will collect ideas for the projects and create a page where
> >
>
> please re-read these two pages:
> https://
On Mon, Feb 1, 2021 at 7:05 AM Alan Carvalho de Assis
wrote:
> Thank you Maxim!
>
> Nathan, do you know if our JIRA Infra is working or do we need to ask
> Apache Infra to help us?
>
It seems it has been setup and there are even a couple of issues listed
there:
https://issues.apache.org/jira/pr
On Fri, Feb 5, 2021 at 8:32 AM David Sidrane
wrote:
> I totally agree, I was always concerned that commits to the Apache directly
> would get missed. So I had it on.
>
>
> I could not even unsubscribe
>
> Hi! This is the ezmlm program. I'm managing the comm...@nuttx.apache.org
> mailing list.
>
>
On Wed, Feb 3, 2021 at 3:50 PM bryan costanich
wrote:
> Our interests align, maybe we can help? Ping me. :)
>
This looks interesting. Very interesting. I have not heard of MCUBoot
before. Apache2 license (that's what it says on the GitHub) so I suppose
we're compatible on that aspect. Also works
On Sun, Feb 21, 2021 at 11:18 AM Gregory Nutt wrote:
> A breakpoint on up_assert should catch any early crashes as you
> describe. There is a cool debug tip here if you hit the breakpoint:
> *https://nuttx.events/wp-content/uploads/2019/11/DSidrane_nx2019.pdf*
Unfortunately that appears to be a
On Sun, Feb 21, 2021 at 6:13 PM Brennan Ashton
wrote:
>
> On Sun, Feb 21, 2021 at 3:11 PM Nathan Hartman
> wrote:
> >
> > On Sun, Feb 21, 2021 at 11:18 AM Gregory Nutt wrote:
> > > A breakpoint on up_assert should catch any early crashes as you
> > > de
On Thu, Mar 4, 2021 at 3:49 PM John Rippetoe
wrote:
>
> The fact that I have not done this yet has been haunting me for months.
> I think I sorted out the issues in the meantime and am trying to find
> time to at least rebase my changes on master and get a draft PR up for
> people to get eyes on.
On Tue, Mar 23, 2021 at 8:39 PM Matias N. wrote:
> Hi,
> while using getopt() from a task started from NSH I realized subsequent
> calls reused the global optind and similar variables resulting in different
> results each time. I'm aware this is expected in FLAT mode and is related
> to the issue
On Wed, Mar 24, 2021 at 12:37 PM Grr wrote:
> Looking for the right way to create a _very_ short delay (10-100 ns), I
> found clock_nanosleep, whose description says:
>
> "The suspension time caused by this function may be longer than requested
> because the argument value is rounded up to an inte
On Wed, Mar 24, 2021 at 2:53 PM Gregory Nutt wrote:
>
>
> > The way the logic in clock_nanosleep() is written, the minimum delay
> > ends up being 2 such ticks. I don't remember why and I can't seem to
> > find it in the code right now, but I know this because I checked into
> > it recently and fo
On Wed, Mar 24, 2021 at 3:53 PM Johnny Billquist wrote:
>
> Perfectly expected.
> With volatile, the compiler are not allowed to optimize away the memory
> accesses for updating the loop variable. So you are suddenly getting a
> lot of memory read/write cycles that probably didn't happen before.
>
On Wed, Mar 24, 2021 at 4:49 PM Grr wrote:
>
> Since afterstart = 0, there should be no loop to optimize out except ONE
> value test
>
> One hundred cycles for that would seem excessive for me
>
> TWENTY THOUSAND CYCLES for a _zero_ loop?!?
>
> Maybe in Java
We didn't see the value of transfer->d
On Thu, Mar 25, 2021 at 2:22 PM Grr wrote:
> > 1nsec means 1GHz, it is very hard to achieve the required accuracy even
> > with the high end CPU. But since the standard defines nano_sleep,
> up_ndelay
> > looks not so unreasonable.
> >
>
> I don't mean 1 ns
>
> I mean delays in the order of _doze
tl;dr: How do I statically allocate DMA buffers and prevent the heap
from overlapping them?
Details: On STM32H7, BDMA can only reach SRAM4 (64 KB starting at
0x3800:). The armv7m DCache line size means the buffers must be
allocated on a cache line boundary. So a DMA buffer must meet 2
requirem
On Thu, Mar 25, 2021 at 7:54 PM Gregory Nutt wrote:
>
> Just don't add it to the primary heap: Add the region below and the
> region above the DMA buffers with two calls to mm_addregion().
>
> addregion (DMABUF_END, SRAM4_END - DMABUF_END, "SRAM4-A");
>
> addregion (SRAM4_START, DMABUF_START- SRA
On Fri, Mar 26, 2021 at 1:08 AM Gregory Nutt wrote:
> >> Just don't add it to the primary heap: Add the region below and the
> >> region above the DMA buffers with two calls to mm_addregion().
> >>
> >> addregion (DMABUF_END, SRAM4_END - DMABUF_END, "SRAM4-A");
> >>
> >> addregion (SRAM4_START, D
On Fri, Mar 26, 2021 at 11:14 AM Gregory Nutt wrote:
> > Speaking of the linker, is there a way to use a combination of the
> > linker script and __attribute__ incantations in the code to detect
> > automatically the size that g_sram4_reserve should be and entirely
> > eliminate the need for the u
On Fri, Mar 26, 2021 at 4:26 AM David Sidrane wrote:
> As you have noted checking at build time only works for in tree
> configurations. The quick fix to add an CONFIG_..._EXCLUDE_SRAM4... (naming
> TBD) and light it in things that select BDMA to SRAM4 would a good to
> addition, and help in some
On Fri, Mar 26, 2021 at 11:41 AM Gregory Nutt wrote:
> Missing bit of logic:
>
> >> Speaking of the linker, is there a way to use a combination of the
> >> linker script and __attribute__ incantations in the code to detect
> >> automatically the size that g_sram4_reserve should be and entirely
>
On Fri, Mar 26, 2021 at 12:25 PM Fotis Panagiotopoulos
wrote:
>
> I have attached the linkerscripts that I was using in some older projects.
The attachment(s) did not come through. Could you resend them with a
.txt extension to get around the filter?
Thanks,
Nathan
On Fri, Mar 26, 2021 at 12:46 PM Fotis Panagiotopoulos
wrote:
> Oh, sorry.
> Attached again as .txt. Is it OK now?
Yes, the files went through this time. Thanks! More below...
> > A tool that takes the Kconfig + chip+ memorymap and make a linker include
> > file and the config code for the heap
On Fri, Mar 26, 2021 at 11:21 AM Gregory Nutt wrote:
> > So, if I understand correctly, anyone can declare a static buffer like this:
> >
> > static uint8_t g_spi6_txbuf[SPI6_DMABUFSIZE_ADJUSTED]
> > SPI6_DMABUFSIZE_ALGN locate_data(".sram4");
> >
> > and automatically the heap will not overlap it
On Fri, Mar 26, 2021 at 2:34 PM Nathan Hartman wrote:
> FYI my work (in progress) on this is in the branch
> "stm32h7-fix-heap-clobber" in my fork, in case anyone wants to look...
>
> https://github.com/hartmannathan/incubator-nuttx/tree/stm32h7-fix-heap-clobber
Ok,
Hi,
Does anyone know why the GitHub PR prechecks don't seem to be running?
In particular, it seems that these four:
* Build / Fetch-Source (pull_request)
* Build Documentation / build-html (pull_request)
* Check / check (pull_request)
* Lint / YAML (pull_request)
are all stuck in "Queued -- Wai
On Tue, Mar 30, 2021 at 3:30 PM Matias N. wrote:
>
> It appears we overwhelmed CI. There are a couple of running jobs (notably one
> is a macOS run which is taking about 2hrs as of now) but they are for PRs
> from 12hs ago at least. There are a multitude of queued runs for many recent
> PRs. Th
On Tue, Mar 30, 2021 at 1:54 AM wrote:
> The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, April 07).
I've created the CWIKI page to draft our report at [1] with some
initial content.
[1] https:/
On Wed, Mar 31, 2021 at 9:05 AM Matias N. wrote:
> Then situation is a bit better now, since we did not continue to submit as
> many Para. However, the builds are still lagging (there are ones from 20hr
> ago running). I see many of the new "cancelling duplicates" jobs queued but
> they have not
On Wed, Mar 31, 2021 at 1:13 PM Matias N. wrote:
> My reasoning with the per board+config ccache is that it should more or less
> detect
> something like this without hardcoding any rules: only files that are
> impacted by any
> changes in the current PR would be rebuilt, any other file would be
On Sun, Apr 4, 2021 at 9:50 PM Brennan Ashton
wrote:
>
> I can try to update the wiki with some of my notes from handling the
> next few releases including some email templates.
Would it make sense to write all new documentation, including how we roll
releases, in the nuttx repo under Document
On Mon, Apr 12, 2021 at 12:10 AM Brennan Ashton
wrote:
> I generated the project board for all the OS PRs in this release
> cycle. I already sorted out a bunch of minor ones, but there are
> around 1000PRs that came in this cycle.
> https://github.com/apache/incubator-nuttx/projects/9
>
> Nathan
On Mon, Apr 12, 2021 at 12:29 AM Brennan Ashton
wrote:
> On Sun, Apr 11, 2021 at 9:19 PM Nathan Hartman
> wrote:
> >
> > On Mon, Apr 12, 2021 at 12:10 AM Brennan Ashton <
> bash...@brennanashton.com>
> > wrote:
> >
> > > I generated the
On Mon, Apr 12, 2021 at 11:14 AM Erick Rodrigues
wrote:
> Hello everyone,
>
> As a friendly reminder of this project, my submission deadline is in 27
> hours, so if any of you still has suggestions for my proposal, this is the
> time to make them since soon I won't be able to make modifications.
On Tue, Apr 13, 2021 at 11:12 AM wrote:
> Hi Berenan,
>
> Since I did not manage to access confluence I finished sorting all PRs
> from the project board
> Please take a look and if possible transfer them to confluence
>
> Thanks
> Alin
Hi,
I'm sorry to hear that. I don't know why the page won
1 - 100 of 878 matches
Mail list logo
