Re: SAMA5D2 DMA

On Fri, Sep 9, 2022 at 7:44 AM TimH wrote: > >From: TimH > >Sent: 07 September 2022 12:14 > > > >A quick dabble with DMA for the SAMA5D2 chip I'm using suggests the native > >NuttX support for this is incorrect and probably applies to SAMA5D3 chips > etc. > >There are refences in sam_xdmac.c to

Re: Driver for combined battery charger and regulator

On Wed, Sep 7, 2022 at 1:34 PM Tim Hardisty wrote: > On Wed, Sep 7, 2022 at 1:03 PM Tim Hardisty > wrote: > >> > >> > >> >>> Please correct me if I'm still missing something, as there > are zero > >> >>> clues I can find as to what each ops function (for example) >

Re: Driver for combined battery charger and regulator

On Wed, Sep 7, 2022 at 1:03 PM Tim Hardisty wrote: > > > >>> Please correct me if I'm still missing something, as there are zero > >>> clues I can find as to what each ops function (for example) is > >>> actually supposed to do. > >> > >> > >> > >>Here is two examples:

Re: Crash in ostest prioinherit?

On Tue, Sep 6, 2022 at 5:36 AM Fotis Panagiotopoulos wrote: > > Hello, > > Priority inheritance has a known bug, and it is not working correctly. > See issue #6310: https://github.com/apache/incubator-nuttx/issues/6310 > > I had to disable it in our application, as it causes lots of problems. > >

Re: Question about ESP32 PC address.

On Tue, Sep 6, 2022 at 8:12 PM Gregory Nutt wrote: > Might be a corrupted address; 0x7278 is ASCII "rx". Could be stack > overflow corrupting the address. Interesting! I hadn't considered to check what the ASCII values of the pointer address might be. This will be a valuable addition to my

Re: Question about ESP32 PC address.

On Tue, Sep 6, 2022 at 6:35 PM Victor Benso wrote: > Besides all the SMP related issues that most likely I failed to figure out, > I would really like to know what kind of address is this at the APP CPU > 0x7278b09a > Addr2line failed to decode that address. The most similar address that I >

Re: Crash in ostest prioinherit?

On Tue, Sep 6, 2022 at 5:36 AM Fotis Panagiotopoulos wrote: > Priority inheritance has a known bug, and it is not working correctly. > See issue #6310: https://github.com/apache/incubator-nuttx/issues/6310 > > I had to disable it in our application, as it causes lots of problems. Thanks for

Crash in ostest prioinherit?

Has anyone ended up in __stack_chk_fail() from nxsig_nanosleep()? I am running ostest on tiva and consistently getting a panic in the "priority_inheritance: Restoration Test" (priority_inheritance() in apps/testing/ostest/prioinherit.c). It always happens in the same place: The above-mentioned

Re: Networking on simulator

On Fri, Sep 2, 2022 at 8:21 AM Fotis Panagiotopoulos wrote: > I used wireshark both on the bridge and the network interface. > I can see the simulator sending packets to the bridge, but these packets do > not appear on the netif! > > It seems that the bridge does not want to forward the traffic

Re: Re: Reevaluate the C89 Requirement

On Wed, Aug 31, 2022 at 11:06 AM Gregory Nutt wrote: > > > There used to be one defining inline to be nothing for ZDS-II . It would > > > only be necessary to restore it for ZDS-II. This does not fix the > > function > > > duplication of static inline functions in header files, however. > > > >

Re: Re: Reevaluate the C89 Requirement

On Tue, Aug 30, 2022 at 10:45 AM Gregory Nutt wrote: > z8, ez80, and ZNEO using the ZiLOG ZDS-II compiler. I don't know the > current outstanding issues with that compiler. The Z80 parts currently use > SDCC but could also use one of several other open source compilers > such as Z88dk > which I

Re: Re: Reevaluate the C89 Requirement

On Tue, Aug 30, 2022 at 4:16 PM Gregory Nutt wrote: > > > compiler.h has changed a lot. Does it still support compilers without > > > inline support? It appears not. I used to define inline to be nothing > > for > > > ZDS-II which worked okay except for static inline functions in header > >

Re: Networking on simulator

On Wed, Aug 31, 2022 at 5:12 AM Fotis Panagiotopoulos wrote: > I enabled all network prints. > > I can see some ARP packets being sent and received, but nothing else. > I get a bunch of warnings like the following: > > netdriver_recv_work: WARNING: Unsupported Ethernet type 3465 > > (where the

Re: Re: Reevaluate the C89 Requirement

On Mon, Aug 29, 2022 at 7:54 PM Alan Rosenthal wrote: > Hi! > > What needs to be done to open the discussion to consider changing the > rules? > > Also please see a very detailed comment on the github issue here by > @robertlipe: >

Re: Article: NuttX on Arm Cortex-A53 and PinePhone

On Wed, Aug 24, 2022 at 8:05 PM Lee, Lup Yuen wrote: > > NuttX now supports 64-bit Arm Cortex-A53 with Multi-Core SMP... Will it run > on Pine64's PinePhone? This article explores how we might run NuttX on a > real phone... > > https://lupyuen.github.io/articles/arm Thank you for this article!

Re: Reevaluate the C89 Requirement

On Tue, Aug 23, 2022 at 8:33 PM Alan Rosenthal wrote: > Hello NuttXers, > > I recently posted an issue to the NuttX Github page: > https://github.com/apache/incubator-nuttx/issues/6896 > > I'll summarize my thoughts here. > > Currently NuttX has a C89 requirement. However, there is code in the >

Re: Conflicts with network and PWM on stm32f7 nucleo-144

On Mon, Aug 22, 2022 at 9:14 AM raiden00pl wrote: > Do you use the default TIM3 outputs configuration from > nucleo-144/include/board.h ? It uses PA7 as the TIM3 channel 2 output which > is also used for RMII_CRS_DV. > > From the nucleo 144 user manual: > > > 2. PA7 is used as D11 and connected

Re: 10.3 merge issues

On Thu, Aug 18, 2022 at 6:40 AM TimH wrote: > Looks like some kind of conflict with syslog settings in the config > (either "default SYSLOG device" or "Use SYSLOG for /dev/console". I've not > been using syslog, so probably something I'd tried (i.e. stab in the dark!) > for some reason in the

Re: 10.3 merge issues

On Wed, Aug 17, 2022 at 3:27 PM Tim Hardisty wrote: > I realise, now, I compared mine against 10.2 variants not 10.3...not sure > why, but there you go. I'll give that a try tomorrow - thanks! Sure thing! Let us know if that fixes it. I'm pretty sure that change in your board's Make.defs (and

Re: 10.3 merge issues

On Wed, Aug 17, 2022 at 3:15 PM Nathan Hartman wrote: > > On Wed, Aug 17, 2022 at 2:38 PM TimH wrote: > > >> no rule to make target '-T/home/{rest of the path}' > > See commit: > https://github.com/apache/incubator-nuttx/commit/8defb843aa2e1d49b08b1cb7155aea97e1721b

Re: 10.3 merge issues

On Wed, Aug 17, 2022 at 2:38 PM TimH wrote: > >> no rule to make target '-T/home/{rest of the path}' See commit: https://github.com/apache/incubator-nuttx/commit/8defb843aa2e1d49b08b1cb7155aea97e1721b6c There have been some refactorings in the build system to reduce code duplication. So

Re: 10.3 merge issues

On Wed, Aug 17, 2022 at 12:56 PM TimH wrote: > 1. Final change that allowed a compile was when I changed the defconfig > to have the new: > > > > CONFIG_INIT_ENTRYPOINT="nsh_main" > > CONFIG_INIT_ENTRYNAME="nsh" > > > > It all boots and I get the nsh prompt but I get continuous: > > > >

Re: LCD Framebuffer putarea and display redraw

On Wed, Jul 20, 2022 at 10:09 AM Karel Kočí wrote: > I discovered that commit 664d45dcbace03a879017aa99566592be31f4308 broke LCD > framebuffer (at least for ST7789). The issue is with `putarea` call. > Originally > it was called only when full display redraw was requested but now it is called >

Re: CRC32 what gives?

On Wed, Jul 20, 2022 at 10:24 AM Karel Kočí wrote: > > Sorry for the late response.. I was busy with life. > > No, NuttX's crc32 is returning 0x2DFD2D88! > My modified code with missing negation returns that 0x340BC6D9 but that is now > probably no longer relevant. We should now probably only

Re: STM32F4 Ethernet Issues

On Tue, Jul 19, 2022 at 7:47 AM Fotis Panagiotopoulos wrote: > Hello! > > I am using Ethernet on an STM32F427 target, but I am facing some issues. > > Initially the device works correctly. After some hours of continuous > operation I completely lose all network communications. > Trying to

Re: CRC32 what gives?

On Fri, Jul 15, 2022 at 1:40 PM Alan Carvalho de Assis wrote: > > Hi Sebastien, I think we don't need these three functions for each > CRC, just one like in the Linux kernel is enough: > > https://www.kernel.org/doc/htmldocs/kernel-api/API-crc-ccitt.html > > BR, > > Alan Could have one generic

Re: CRC32 what gives?

On Fri, Jul 15, 2022 at 12:45 PM Karel Kočí wrote: > > The impact might be pretty significant from my search and that is also why I > rather discuss instead of suggesting changes. > > The significant place where the current crc32 implementation is used is in > file systems (such as smartfs or

Re: [DISCUSS] Graduate NuttX as TLP

On Fri, Jul 15, 2022 at 6:55 AM 张铎(Duo Zhang) wrote: > > Let's first make sure we have done all the things in the check list? > > Abdelatif Guettouche 于2022年7月13日周三 19:40写道： > > > It would be nice to hear from the mentors or anyone from the IPMC. We still need to: (1) Fill in the STATUS file:

Re: CRC32 what gives?

On Fri, Jul 15, 2022 at 8:10 AM Karel Kočí wrote: > > Hi > > I hit an issue with crc32 implementation in NuttX's LibC and it took me some > time to figure out that crc32 is implemented differently in NuttX than I was > expecting. Let me explain... > > Common implementations are using same

Re: Can musl libc replace the libc of nuttx system？

On Thu, Jul 14, 2022 at 5:30 PM Alan Carvalho de Assis wrote: > > You are right, currently Apex RTOS and RT-Thread (only their "Smart > brand" that only works on CPU with MMU) are using musl lib. > > So it could be useful to have musl support for NuttX. Why not make NuttX libc as good as

Serial UART O_NONBLOCK stale data after close()

In uart_close() of drivers/serial/serial.c, we have this: /* There are no more references to the port */ dev->open_count = 0; /* Stop accepting input */ uart_disablerxint(dev); /* Prevent blocking if the device is opened with O_NONBLOCK */ if ((filep->f_oflags & O_NONBLOCK) == 0)

Re: [DISCUSS] Graduate NuttX as TLP

, Nathan On Fri, Jun 24, 2022 at 12:46 PM Nathan Hartman wrote: > > Hi folks, > > It's time to start the [DISCUSS] thread about GRADUATION! > > Project Highlights Since Incubation: > > * Incubating since 2019-12-09 > * New website, nuttx.apache.org > * Shipped 8 re

Re: net/if_arp.h - standard header?

On Wed, Jun 29, 2022 at 12:23 PM Xiang Xiao wrote: > > On Wed, Jun 29, 2022 at 4:44 AM Nathan Hartman > wrote: > > > On Tue, Jun 28, 2022 at 4:05 PM Nathan Hartman > > wrote: > > > > > > I have a program that builds under Linux, BSD, and macOS wh

Re: Podling Nuttx Report Reminder - July 2022

On Tue, Jun 28, 2022 at 10:03 PM wrote: > Dear podling, > > This email was sent by an automated system on behalf of the Apache > Incubator PMC. It is an initial reminder to give you plenty of time to > prepare your quarterly board report. > > The board meeting is scheduled for Wed, 20 July 2022.

Re: net/if_arp.h - standard header?

On Tue, Jun 28, 2022 at 4:05 PM Nathan Hartman wrote: > > I have a program that builds under Linux, BSD, and macOS which > includes the net/if_arp.h header. > > This header does not seem to exist under NuttX. > > It is included for the ARPHRD_ETHER define (and possibly oth

net/if_arp.h - standard header?

I have a program that builds under Linux, BSD, and macOS which includes the net/if_arp.h header. This header does not seem to exist under NuttX. It is included for the ARPHRD_ETHER define (and possibly other things). I see that under NuttX, this is defined in net/arp.h, rather than

Re: [DISCUSS] Graduate NuttX as TLP

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 our mentors: > > > > 1. Demonstrate ability to create Apache releases > > 2. Demonstrate

Re: Fwd: [MENTORS] Podling reports for July

On Mon, Jun 20, 2022 at 8:23 AM Pavel Pisa wrote: > > Hello everybody, > > the is mirror shift of past to the future by some time-machine > > Date of last release: > > NuttX-10.2.0 was released on 2022-11-23. > NuttX-10.3.0-RC4 is currently pending IPMC voting. Thanks Pavel. This should be fixed

Re: [DISCUSS] Graduate NuttX as TLP

On Fri, Jun 24, 2022 at 12:46 PM Nathan Hartman wrote: > > Hi folks, > > It's time to start the [DISCUSS] thread about GRADUATION! > > Project Highlights Since Incubation: > > * Incubating since 2019-12-09 > * New website, nuttx.apache.org > * Shipped 8 releases unde

Re: Weird problem with CONFIG_NETINIT_THREAD

On Sun, Jun 26, 2022 at 1:25 PM Gregory Nutt wrote: > > Sounds like nothing is calling netinit_bringup(). Normally this is part > of the console initialization: > > nsh_altconsole.c: netinit_bringup(); > nsh_consolemain.c: netinit_bringup(); > nsh_telnetd.c: netinit_bringup(); >

Weird problem with CONFIG_NETINIT_THREAD

Hi all, I am programming a custom board which has Ethernet, but does not have UART or USB connections, so I need to access NSH via Telnet. The board is configured to use DHCP client. I am using latest master: commit # c6c0baa233594dd8e5319a82a6708121e8e94349 in incubator-nuttx tree. The weird

[DISCUSS] Graduate NuttX as TLP

Hi folks, It's time to start the [DISCUSS] thread about GRADUATION! Project Highlights Since Incubation: * Incubating since 2019-12-09 * New website, nuttx.apache.org * Shipped 8 releases under the ASF Incubator, including our first non-WIP release * Merged more than 7000 PRs across

Re: [ANNOUNCE] Apache NuttX 10.3.0-incubating released

On Fri, Jun 24, 2022 at 7:16 AM Abdelatif Guettouche < abdelatif.guettou...@gmail.com> wrote: > > What are next steps? > > Release wise, nothing -- we just need to keep making releases. > > For graduation that's a different story that we need to discuss. > There is a checklist here: >

Re: [NuttX] mailing list messages subject prefix

On Mon, Jun 20, 2022 at 9:46 AM Tomek CEDRO wrote: > > hello world :-) > > would that be possible to add "[NuttX]" or "[Nuttx-dev]" prefix to mailing > list messages? > > that would help in quick messages identification among hundreds of other > emails :-) > > thanks for considering :-) > > -- >

Fwd: [MENTORS] Podling reports for July

Our podling report is due by end of day on 6 July 2022. I have staged an initial draft here: https://cwiki.apache.org/confluence/display/NUTTX/2022+-+07+-+July Of course we are waiting for voting to complete on the latest NuttX release. Hopefully that will happen well before July 6th, in which

Re: Network debug info level breaks nx_start -> group_setupidlefiles

On Thu, May 19, 2022 at 12:40 PM Sebastien Lorquet wrote: > > Hi, > > I have a nucleo-h743zi, in which I have enabled network. > > It seems to work so far. > > When I enable Network Info Debug, I get a crash. > > The crash does not happen with Network info disabled (Enabling network > warnings

Re: LDFLAGS -nostdlib for arm-nuttx-elf?

On Wed, May 18, 2022 at 1:32 PM Xiang Xiao wrote: > > -nostdlib is specific to clang/gcc toolchain, not specific to arm or elf. > Only gcc/clang toolchain add this flag, other toolchain(e.g. z80) still > keep as before. Okay that makes sense. Thanks for the explanation. Cheers, Nathan

LDFLAGS -nostdlib for arm-nuttx-elf?

I noticed that we are unconditionally using: LDFLAGS += -nostdlib Is that correct when building with arm-nuttx-elf toolchain? Thanks, Nathan

Re: Add license Kconfig for 3rd party binary blobs?

On Sun, May 15, 2022 at 10:51 AM Tomek CEDRO wrote: > > On Sun, May 15, 2022 at 4:23 PM Nathan Hartman wrote: > > I noticed that we are downloading a 3rd party precompiled library, > > libphy62xxble.a from www.phyplusinc.com. (One of the Linux build tests > > on PR-6266 fa

Add license Kconfig for 3rd party binary blobs?

I noticed that we are downloading a 3rd party precompiled library, libphy62xxble.a from www.phyplusinc.com. (One of the Linux build tests on PR-6266 failed because curl failed to download it.) This download is done in arch/arm/src/phy62xx/Make.defs: if [ ! -f libphy62xxble.a ]; then \ echo

Re: ICMP responses on UDP broadcasts

On Fri, May 13, 2022 at 5:14 AM Fotis Panagiotopoulos wrote: > > Hi Nathan, > > There is such a macro, it is net_ipv4addr_broadcast(). > I just used it, as you describe above, and I created PR #6262. > > I checked the result with Wireshark, and indeed it solves the issue. > > Thank you all!

Re: Network deadlock and priority inheritance.

On Fri, May 13, 2022 at 6:43 AM Fotis Panagiotopoulos wrote: > > Hello! > > I am facing various issues with networking in NuttX, including a nasty > deadlock. > > I tried to track down this deadlock, and it seems that it is related to > g_netlock. > I am not sure yet what is the sequence that

Re: ICMP responses on UDP broadcasts

On Thu, May 12, 2022 at 5:18 AM Bernd Walter wrote: > > On Wed, May 11, 2022 at 07:13:17PM -0400, Nathan Hartman wrote: > > On Wed, May 11, 2022 at 5:19 AM Fotis Panagiotopoulos > > wrote: > > > > > > I was thinking the same thing. > > > > > &g

Re: ICMP responses on UDP broadcasts

On Wed, May 11, 2022 at 5:19 AM Fotis Panagiotopoulos wrote: > > I was thinking the same thing. > > Which layer is responsible for this check? > IP, UDP, or ICMP? Logically it would seem to me that UDP should do the check and trigger sending the ICMP unreachable reply when appropriate, though

Re: [VOTE] Apache NuttX 10.3.0 (incubating) RC2 release

Summary: +1 to release (binding) Per Alan's request for size information [1]: * NuttX-10.3.0-RC2, b-g474e-dpow1:nsh configuration: $ arm-none-eabi-size nuttx text databssdechex filename 117843636 2256 120735 1d79f nuttx * This is a slight improvement from

Re: ICMP responses on UDP broadcasts

On Tue, May 10, 2022 at 6:01 AM Fotis Panagiotopoulos wrote: > Hello, > > I just noticed that NuttX responds with an ICMP port unreachable on UDP > broadcasts. > AFAIK this shouldn't happen. > > I followed the code, and I found that the broadcast reaches udp_input.c: > line 256, where the ICMP

Re: Podling Nuttx Report Reminder - May 2022

On Wed, Apr 27, 2022 at 8:50 PM wrote: > > Dear podling, > > This email was sent by an automated system on behalf of the Apache > Incubator PMC. It is an initial reminder to give you plenty of time to > prepare your quarterly board report. > > The board meeting is scheduled for Wed, 18 May 2022.

Re: Simple question about network in Nuttx

On Wed, Apr 27, 2022 at 5:21 AM Roberto Bucher wrote: > I've configured my STM32 board (nucleo-144) to use the network. UIt was > ok some months ago, but now it seems to be not in the network... > > It seems that the configuration is ok, but I can't see a /dev/eth0 on my > device list... I have

Re: [VOTE] Release Apache NuttX (Incubating) 10.3.0 [RC0]

On Thu, Apr 14, 2022 at 10:39 AM 张铎(Duo Zhang) wrote: > > Ah, then let me just post them as the content. I've removed several files > from the list by the information you provided. And I suggested that when > you specify a library, better also provide the place where the related > files are

Re: The real-time performance of nuttx

On Sun, Apr 3, 2022 at 3:52 AM fft wrote: > > Hi team: > > I've been puzzled by a strange problem for a long time, when i use FOC > motor control. It seems that the FOC control thread failed to be scheduled > in real time. The code structure of ./apps/examples/foc/foc_float_thr.c can > be

Re: [VOTE] Apache NuttX 10.3.0 (incubating) RC0 release

On Wed, Mar 30, 2022 at 12: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 accepting it for release. If approved we will seek > final release approval from the IPMC. Voting will be open for 72hr. > > A

Re: NuttX 10.3 release plan

On Mon, Mar 28, 2022 at 8:32 AM alin.jerpe...@sony.com < alin.jerpe...@sony.com> wrote: > > @Nathan Hartman please check if you can fix the format > https://cwiki.apache.org/confluence/display/NUTTX/NuttX+10.3 > Hi Alin, What needs to be fixed? Cheers Nathan > >

Re: NuttX 10.3 release plan

On Wed, Mar 16, 2022 at 7:04 AM alin.jerpe...@sony.com wrote: > > Hi all, > > I crested the release 10.3 branch and started working on the release notes > > Please PR backports to the branch Thank you, Alin. Please note there is a draft Release Notes here:

Re: I does an app know it is building on NuttX

On Tue, Feb 22, 2022 at 2:14 PM Gregory Nutt wrote: > One option would be to define __NUTTX_ in tools/Config.mk instead of in > each individual apps/Makefile. That would provide a single point > definition coordinate all usage. Just one (possible) correction: IIRC it is capitalized as

Re: [DISCUSS] Default state of NDEBUG

On Thu, Feb 17, 2022 at 4:08 AM Petro Karashchenko wrote: > My point about two config options was more because I think that apps > and kernel are two separate entities and if there is a need to add > extra debugging capabilities to the kernel it does not mean that it > needs to be added for apps

Re: [DISCUSS]: Self merge and Single company/organization merge gating

On Fri, Feb 18, 2022 at 5:27 AM Xiang Xiao wrote: > > On Fri, Feb 18, 2022 at 3:52 PM Petro Karashchenko < > petro.karashche...@gmail.com> wrote: > > > Hi, > > > > I agree that auto-merge should not be used. > > > > But I disagree that "as it is now since almost all patches follow the > > rule

Re: [DISCUSS]: Self merge and Single company/organization merge gating

On Mon, Feb 14, 2022 at 2:01 PM Brennan Ashton wrote: > > Background: > I am generally opposed to both of these. It is quite rare that we need a > crazy fast merge turn around on a PR. And if something is approved and > straight up broken in master that needs to get in then I think forgiveness >

Re: Graduation?

On Sat, Feb 12, 2022 at 2:32 AM 张铎(Duo Zhang) wrote: > > It depends. We need to start a discuss thread on the incubator-general > mailing list to see if IPMC members have any concerns. Hi all, I suggest we go ahead and start that thread. Does anyone need more time first? Cheers, Nathan

Re: Graduation?

On Wed, Feb 9, 2022 at 12:30 PM Brennan Ashton wrote: > There is also some code still in the repo with restrictions on use to a > single microcontroller. That have come up in votes before. Can we wrap code like that with a Kconfig, e.g., ALLOW_NONFREE_CODE, like we already have for GPL and BSD

Graduation?

Are we missing any major requirements to graduate to Top Level Project? If no showstoppers, how does everyone feel about starting the discuss thread at the incubator? Cheers, Nathan

Re: Alternatives to FAT for msd

On Fri, Jan 21, 2022 at 8:19 AM Alan Carvalho de Assis wrote: > I think there is some issues in the Apache Foundation email infra, > this is the second time it happens. The same email is send again after > some days. Perhaps the emails in question have been waiting on a human moderator? I

Re: Qencoder position value range

On Thu, Jan 13, 2022 at 9:50 AM Petro Karashchenko wrote: > > Thank you. I would appreciate that, but I think that will work only if > there is no complete cycle between two reads, so it is potentially a > possibility to get wrong position. Yes, that is correct. If you know what the application

Re: Qencoder position value range

On Thu, Jan 13, 2022 at 8:19 AM Petro Karashchenko < petro.karashche...@gmail.com> wrote: > Hi, > > I've been working to add SAMv7 Qencoder interface and see that Qencoder > driver expects QEIOC_POSITION to be int32_t value. The issue is that SAMv7 > has 16 bit timer counter interface and the SW

Re: kconfig-frontends upstream

On Sat, Oct 16, 2021 at 8:19 AM Tomasz CEDRO wrote: > > Hello Yann, > > You are marked as the author of the kconfig-frontends in a release > package AUTHORS file. This package is a core dependency of the NuttX > RTOS. It seems that development of the package has been abandoned..? > > Can you

Re: Move to C99 for common code

On Mon, Jan 10, 2022 at 9:15 AM Gregory Nutt wrote: > > > > > Speaking of the Z80, would it be possible to run NuttX in a Grant Searle > > / RC2014 platform with a 8k ROM /56k RAM split, or would any attempt > > require banked memory? > > > > I don't know if it is possible or not. I don't know

Re: Move to C99 for common code

On Sat, Jan 8, 2022 at 11:34 AM Alan Carvalho de Assis wrote: > I agree! There are few places where designated initializer list are used in > the common code (in arch/ and boards/ they can be used without further > concern), so it can be fixed at no time. > > In the other hand this flexibility

Re: Change default behavior of semaphores?

On Wed, Jan 5, 2022 at 10:30 PM Xiang Xiao wrote: > On Thu, Jan 6, 2022 at 4:23 AM Gregory Nutt wrote: > > > > I truly believe that priority inheritance on counting semaphores should > > be > > > > explicitly enabled (disabled by default) and enabling it by default might > > > > lead to

Re: Top Apache Projects

On Tue, Jan 4, 2022 at 9:08 PM Gregory Nutt wrote: > > Interesting: > https://thestack.technology/top-apache-projects-in-2021-from-superset-to-nuttx/ Wow that's cool! Thanks for sharing. Now all we have to do is graduate. :-) Cheers and Happy New Year, Nathan

Change default behavior of semaphores?

PR-5070 [1] proposes to change the default behavior of semaphores. If implemented, this will be a breaking change that affects downstream projects. Please help review this PR for correctness and standards compliance, keeping in mind the Inviolable principles of NuttX [2], particularly the

Re: FUSB302

On Wed, Dec 1, 2021 at 11:29 AM Tim wrote: > > OK, thanks - should have thought to check for any updates - sorry. > > Yes, still got the 10.1 tree I think it is, from 7 or 8 months. Will need to > do whatever I need to do to get the latest but not a priority right now: > GitHub still scares me!

Re: MTD partition check error

On Tue, Nov 30, 2021 at 9:53 AM Sebastien Lorquet wrote: > > Hello > > new board has a new flash part that is smaller than the previous one. > > however without changing the rest of my code, the creation of a > partition that is too large for the new small device was accepted. > > I noticed that

Re: Kernel ticking and progmem writes

On Tue, Nov 30, 2021 at 8:05 AM Fotis Panagiotopoulos wrote: > I found the issue. > > From the STM32F427 manual: > > > Any attempt to read the Flash memory on STM32F4xx while it is being > written or erased, > > causes the bus to stall. Read operations are processed correctly once the > program

Re: [VOTE] Apache NuttX 10.2.0 (incubating) RC0 release

Summary: +1 to release (binding) Per Alan's request for size information: * NuttX-10.2.0-RC0, b-g474e-dpow1:nsh configuration: $ arm-none-eabi-size nuttx textdata bss dec hex filename 115331 6242500 118455 1ceb7 nuttx * For comparison, same configuration on

Re: FreeBSD / BSD

On Tue, Oct 19, 2021 at 1:17 AM Tomasz CEDRO wrote: > > Sorry for yesterday, I just need to remember about zfs snap before > root experiments or simply experiment in vm ;-) > > kconfig-frontends port for FreeBSD is ready: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=259256 > > Port

Re: FreeBSD / BSD

On Sun, Oct 17, 2021 at 9:32 PM Tomasz CEDRO wrote: > By the way, did anyone since 1998 of genromfs existence notice this > part of Makefile that may cripple your system files ?! > > install-man: > # genromfs 0.5 installed the man page in this file, > # remove it before someone

Re: github nuttx/nuttx vs apache/incubator-nuttx

On Sun, Oct 17, 2021 at 9:10 AM Abdelatif Guettouche wrote: > > We've been told before that we can host well known projects even if > they are in an incompatible license. We discussed moving them to > Apache. > I'm not sure if we want to revive that discussion as it always went > unnoticed, but

Re: github nuttx/nuttx vs apache/incubator-nuttx

On Sat, Oct 16, 2021 at 10:27 AM Tomasz CEDRO wrote: > Regarding kconfig-frontends I am in touch with Espressif and Debian > maintainers, also contacted initial author Yann MORIN. Maybe putting > this package into the Apache organization would be a good idea if > possible..? It occurred to me

Re: FreeBSD / BSD

On Thu, Oct 14, 2021 at 12:23 PM Gregory Nutt wrote: > > > > >> The Linux Foundation and the ASF are both not-for-profit > >> organizations, but they different significantly in their legal > >> organizations. I forget the non-project corporation types but > >> basically, the Linux

Re: FreeBSD / BSD

On Tue, Oct 12, 2021 at 12:49 PM Gregory Nutt wrote: > > Matias N. made some progress before; > > Unified device interface, callback based initialization and devicetree > > (DTS) · Issue #3031 · apache/incubator-nuttx (github.com) > > > >

Re: FreeBSD / BSD

On Mon, Oct 11, 2021 at 8:31 AM Tomasz CEDRO wrote: > > On Sun, Oct 10, 2021, 18:36 Gregory Nutt wrote: > > > Device tree is another technology that has been advocated for NuttX with > > a few strong advocates but with no clear mandate from the community. > > > > Linux and Zephyr RTOS uses DTS to

Re: Podling Nuttx Report Reminder - October 2021

ort to the official location? Thanks for > summary the accurate information. > > On Thu, Sep 30, 2021 at 9:41 PM Nathan Hartman > wrote: > > > Hi all, > > > > I've updated the initial draft of our report for October 6. > > > > Please review and feel free

Re: NuttX-10.2 release

oposed 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 Message- > From: Alin Jerpelea > Sent

Re: FreeBSD / BSD

On Fri, Oct 8, 2021 at 7:54 PM Tomasz CEDRO wrote: > On Fri, Oct 8, 2021 at 8:38 PM Gregory Nutt wrote: > > > > I don't think that there is any particular reason to "forbid" Python in > the > > build. The current build does not depend on Python and, hence, adding > the > > requirement for

Re: FreeBSD / BSD

On Thu, Oct 7, 2021 at 11:51 PM Tomasz CEDRO wrote: > On Fri, Oct 8, 2021 at 5:15 AM Tomasz CEDRO wrote: > > On Fri, Oct 8, 2021 at 4:47 AM Nathan Hartman wrote: > > > There is a NuttX Tools repo at > > > https://bitbucket.org/nuttx/tools/downloads/ > > &g

Re: FreeBSD / BSD

On Thu, Oct 7, 2021 at 10:29 PM Tomasz CEDRO wrote: > Hello world :-) > > My first steps with NuttX on FreeBSD. I will ask some questions here > for support and make it working on BSD :-) > > First one: > > % ./tools/configure.sh esp32c3-devkit:ble > Copy files >

Re: NUCLEO-L496ZG - clock misconfig

In the board's board.h there are some defines that affect how the sysclk is setup. If e.g. the PLL params are off you'll see an issue like this. It should also be possible to singlestep through the very first arch init steps and see if it's taking a wrong turn somewhere. On Wed, Oct 6, 2021 at

Re: Podling Nuttx Report Reminder - October 2021

located here: https://cwiki.apache.org/confluence/display/NUTTX/2021-10+-+October Soon it will need to be moved to the Incubator report. Please review! Thanks! Cheers, Nathan On Fri, Sep 24, 2021 at 10:19 AM Nathan Hartman wrote: > > Hi all, > > I've written the initial draft o

Re: Which control version software are you using? //was Re: Poll: Which OS are you using to compile NuttX?

On Sat, Sep 25, 2021 at 2:21 PM David S. Alessio wrote: > Hi, Simon, > > It addresses the problem of knowing exactly what version of NuttX is > running on a platform. This problem often occurs, when in testing or > deployment, one discovers a problem which may or may not have already been >

Re: Which control version software are you using? //was Re: Poll: Which OS are you using to compile NuttX?

On Fri, Sep 24, 2021 at 6:58 PM Alan Carvalho de Assis wrote: > > On 9/24/21, David S. Alessio wrote: > > Hi, Alan, > > > > It’d be good to know how developers are managing their code: > > 1) git > > 2) mercurial > > 3) SVN > > 4) zip files on floppies > > 5) none Subversion, both personally

Re: Podling Nuttx Report Reminder - October 2021

Hi all, I've written the initial draft of the report for October 6. It is located here: https://cwiki.apache.org/confluence/display/NUTTX/2021-10+-+October Please take a look. If you find errors, feel free to update/correct/add, or let me know. Cheers, Nathan On Mon, Sep 20, 2021 at 4:57 AM

<    1   2   3   4   5   6   7   8   9   >