Re: [VOTE] Apache NuttX 12.5.1 RC0 release

2024-04-10 Thread Tiago Medicci Serrano 
[+1] for all Espressif-supported boards and chips, namely:

   - esp32_devkitc
   - esp32_ethernet_kit
   - esp32_lyrat
   - esp32_pico_kit
   - esp32_wrover_kit
   - esp32c3_devkit
   - esp32c3_generic
   - esp32c6_devkitc
   - esp32c6_devkitm
   - esp32h2_devkit
   - esp32s2_saola
   - esp32s3_devkit
   - esp32s3_lcd_ev

Tested with our internal CI with all defconfigs (including `ostest`).

Compilers:

root@11bcb68b5d68:/nuttx# xtensa-esp32-elf-gcc --version
xtensa-esp32-elf-gcc (crosstool-NG esp-12.2.0_20230208) 12.2.0

root@11bcb68b5d68:/nuttx# xtensa-esp32s2-elf-gcc --version
xtensa-esp32s2-elf-gcc (crosstool-NG esp-12.2.0_20230208) 12.2.0

root@11bcb68b5d68:/nuttx# xtensa-esp32s3-elf-gcc --version
xtensa-esp32s3-elf-gcc (crosstool-NG esp-12.2.0_20230208) 12.2.0

root@11bcb68b5d68:/nuttx# riscv-none-elf-gcc --version
riscv-none-elf-gcc (xPack GNU RISC-V Embedded GCC x86_64) 12.3.0

Em ter., 9 de abr. de 2024 às 14:11, Tim Hardisty 
escreveu:

> +1 non-binding. On my custom board:
>
> NuttX  12.5.1-RC0 3fcd063148 Apr  9 2024 16:22:37 arm jti-xxx
>
> arm-none-eabi-gcc -v
> Supported LTO compression algorithms: zlib
> gcc version 13.2.1 20231009 (Arm GNU Toolchain 13.2.rel1 (Build arm-13.7))
>
> On 09/04/2024 08:40, Alin Jerpelea wrote:
> > Hello all,
> > Apache NuttX 12.5.1 RC0 has been staged under [1] and it's
> > time to vote on accepting it for release. Voting will be open for 72hr.
> >
> > A minimum of 3 binding +1 votes and more binding +1 than binding -1 are
> > required to pass.
> >
> > The Apache requirements for approving a release can be found here [3]
> > "Before voting +1 PMC members are required to download the signed
> > source code package, compile it as provided, and test the resulting
> > executable on their own platform, along with also verifying that the
> > package meets the requirements of the ASF policy on releases."
> >
> > A document to walk through some of this process has been published on
> > our project wiki and can be found here [4].
> >
> > [ ] +1 accept (indicate what you validated - e.g. performed the non-RM
> > items in [4])
> > [ ] -1 reject (explanation required)
> >
> > Thank you all,
> > Alin Jerpelea
> >
> > SCM Information:
> >Release tag: nuttx-12.5.1-RC0
> >Hash for the release nuttx tag:
> 9e8753d6256619a7bfa72f4596eb1e481f1c97a2
> >Hash for the release nuttx-apps tag:
> 63dd3547fdc9a0412f0e04df5d8a8be480dd6935
> >
> > [1] https://dist.apache.org/repos/dist/dev/nuttx/12.5.1-RC0/
> > [2]
> https://raw.githubusercontent.com/apache/nuttx/nuttx-12.5.1-RC0/ReleaseNotes
> > [3] https://www.apache.org/dev/release.html#approving-a-release
> > [4]
> https://cwiki.apache.org/confluence/display/NUTTX/Validating+a+staged+Release
> >
>


-- 
Tiago Medicci Serrano

Embedded Software Engineer
MSc Electronics/Microelectronics
m: +55 (19) 981403886 <+55+(19)+981403886>
e: tiago.medi...@gmail.com
a: Campinas, Brazil
Follow me:

Re: Nano-x porting

2024-04-10 Thread Alan C. Assis 
Hi Pavel,

Thank you very much for that!

Actually Shijo decided not to participate in GSoC2024, but opted to do the
port in his free time.

I'm also interested in Nano-X support on NuttX because we could use FLTK
with it and maybe we could get Dillo Browser running with it as well.

BR,

Alan

On Wed, Apr 10, 2024 at 2:31 AM Pavel Pisa  wrote:

> Hello Lup
>
> On Wednesday 10 of April 2024 06:57:00 Lee, Lup Yuen wrote:
> > Hi Pavel: I'm sorry the GSoC Proposal Submission has closed last week.
> > Though Shijo is still keen to do NanoX on NuttX in his spare time.
> >
> > I asked Shijo to bounce some ideas with you. If you could help him, that
> > would be great. Thanks :-)
>
> Yes, I want to help and I have interrest in the project,
> so I try to help when I am pinged. If I do not respond
> in a week, please, send me reminder. I am really busy with
> teaching at CTU and remotely in https://spacemaster.eu/ where
> CTU participates, so my remaining energy is limited.
>
> It is shame that the Nano-X for NuttX has not succeed
> in NuttX GSoC.
>
> I have thought that
>   Add X11 graphic support on NuttX using NanoX
> has been on the official list of proposed project.
>
> But project wort to try anyway. I expect that use for
> GDI and local functions calls would work smoothly.
> Nano-X layer which allows remote access and rendering
> is really interesting but I expect that its speed
> (responsiveness) will be limited on MCUs.
> On the other hand speed of today MCUs is higher
> than PCs in middle of 90 and full featured X11
> worked on them and has been with Slackware Linux my
> main and only desktop these days. So even this
> setup worth to test on NuttX if it will work
> good enough.
>
> Best wishes,
>
> Pavel
> --
> Pavel Pisa
>
> e-mail: p...@cmp.felk.cvut.cz
> Department of Control Engineering FEE CVUT
> Karlovo namesti 13, 121 35, Prague 2
> university: http://control.fel.cvut.cz/
> personal:   http://cmp.felk.cvut.cz/~pisa
> company:https://pikron.com/ PiKRON s.r.o.
> Kankovskeho 1235, 182 00 Praha 8, Czech Republic
> projects:   https://www.openhub.net/accounts/ppisa
> social: https://social.kernel.org/ppisa
> CAN related:http://canbus.pages.fel.cvut.cz/
> RISC-V education: https://comparch.edu.cvut.cz/
> Open Technologies Research Education and Exchange Services
> https://gitlab.fel.cvut.cz/otrees/org/-/wikis/home
>

Re: paid support to understand and resolve some open issues

2024-04-10 Thread Alan C. Assis 
Hi Andrew,

Could you please open a public issue to report these issues (case you
haven't yet).

Also if you have some testing examples to trigger these issues, we could
include it into our ostest to avoid it happening again.

BR,

Alan

On Tue, Apr 9, 2024 at 3:45 AM Andrew Dennison 
wrote:

> Hi Nuttx community,
>
> We are actively working with nuttx and RISCV (RV32) and have contributed
> several PR to improve support for kernel mode with litex:
>
> https://nuttx.apache.org/docs/latest/platforms/risc-v/litex/cores/vexriscv_smp/index.html
> .
>
> Along the way we have identified several issues and would like to offer to
> pay for someone with appropriate experience to investigate and upstream any
> fixes identified. Some examples:
>
> Experiencing possible race condition with pthread_cond_timedwait. #9840
> 
> Unexpected behaviour with poll and tickless scheduler #11189
> 
>
> Please contact us directly if you feel you could help with either of these
> issues or potentially some of the other recent issues here:
> https://github.com/apache/nuttx/issues?q=is%3Aopen+author%3Ag2gps+
>
> Kind regards,
>
> Andrew Dennison
> Chief Architect and Hardware Team Lead
>
> --
> *MoTeC Pty Ltd*
>
> 121 Merrindale Drive
> Croydon South 3136
> Victoria Australia
> *T: *61 3 9761 5050
> *W: *www.motec.com.au 
>
>
> --
>  
> 
> 
> 
>
>
> --
>  
>
> --
>
>
> Disclaimer Notice: This message, including any attachments, contains
> confidential information intended for a specific individual and purpose
> and
> is protected by law. If you are not the intended recipient you should
> delete this message. Any disclosure, copying, or distribution of this
> message or the taking of any action based on it is strictly prohibited.
>

Re: [VOTE] Apache NuttX 12.5.1 RC0 release

2024-04-10 Thread Tomek CEDRO 
On Tue, Apr 9, 2024 at 9:41 AM Alin Jerpelea wrote:
>
> Hello all,
> Apache NuttX 12.5.1 RC0 has been staged under [1] and it's
> time to vote on accepting it for release. Voting will be open for 72hr.

+1 here :-)

Thank you folks! :-)

Tomek


=== BUILD HOST ===

% uname -a
FreeBSD octagon 13.2-RELEASE-p11 FreeBSD 13.2-RELEASE-p11 GENERIC amd64

% lscpu
Architecture:amd64
Byte Order:  Little Endian
Total CPU(s):8
Thread(s) per core:  1
Core(s) per socket:  8
Socket(s):   1
Vendor:  AuthenticAMD
CPU family:  21
Model:   2
Model name:  AMD FX(tm)-8320 Eight-Core Processor
Stepping:0
L1d cache:   16K
L1i cache:   64K
L2 cache:2048K
L3 cache:8M
Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep
mtrr pge mca cmov pat pse36 cflsh mmx fxsr sse sse2 htt sse3 pclmulqdq
monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave osxsave avx f16c
syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm lahf_lm cmp_legacy svm
extapic cr8_legacy lzcnt sse4a misalignsse 3dnowprefetch osvw ibs xop
skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb

=== TARGETS ===
1. ESP32.
2. ESP32-C3.
3. ESP32-S2.


=== ESP32 ===

% xtensa-esp32-elf-cc --version
xtensa-esp32-elf-cc (crosstool-NG esp-2021r2-patch5) 8.4.0
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

% gmake clean distclean

% /usr/bin/time -h ./tools/configure.sh -a ../nuttx-apps.git -B
esp32-devkitc:nsh
7,04s real  1,81s user  2,43s sys

% /usr/bin/time -h gmake -j8
21,63s real 1m2,32s user39,64s sys

% /usr/bin/time -h gmake flash
14,10s real 2,64s user  3,27s sys

% cu -l /dev/cuaU0 -s 115200
Connected

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:4540
ho 0 tail 12 room 4
load:0x40078000,len:12344
ho 0 tail 12 room 4
load:0x40080400,len:4124
entry 0x40080680

NuttShell (NSH) NuttX-12.5.1
nsh> uname -a
NuttX 12.5.1 9e8753d625 Apr 11 2024 00:37:28 xtensa esp32-devkitc
nsh> help
help usage:  help [-v] []

.   cp  exitmkdir   rmdir   umount
[   cmp exprmkrdset unset
?   dirname false   mount   sleep   uptime
alias   dd  fdinfo  mv  source  usleep
unalias df  freepidof   testxd
basenamedmesg   helpprintf  time
break   echohexdump ps  true
cat env killpwd truncate
cd  execls  rm  uname

Builtin Apps:
nshsh
nsh> echo hello world
hello world
nsh> uptime
00:00:19 up  0:00, load average: 0.00, 0.00, 0.00
nsh> env
PWD=/
nsh> ls
/:
 dev/
 proc/


% /usr/bin/time -h gmake clean distclean
13,03s real 5,28s user  8,47s sys

% /usr/bin/time -h ./tools/configure.sh -a ../nuttx-apps.git -B
esp32-devkitc:coremark
3,98s real  1,74s user  2,54s sys

% /usr/bin/time -h gmake -j8
21,23s real 1m2,89s user39,04s sys

% /usr/bin/time -h gmake flash
12,75s real 2,36s user  2,73s sys

% cu -l /dev/cuaU0 -s 115200
Connected
ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:4540
ho 0 tail 12 room 4
load:0x40078000,len:12344
ho 0 tail 12 room 4
load:0x40080400,len:4124
entry 0x40080680
Running CoreMark...
2K performance run parameters for coremark.
CoreMark Size: 666
Total ticks  : 1218
Total time (secs): 12.18
Iterations/Sec   : 985.221675
Iterations   : 12000
Compiler version : GCC8.4.0
Compiler flags   : -O3 -fno-strict-aliasing -fomit-frame-pointer
-ffunction-sections -fdata-sections
Parallel PThreads : 2
Memory location  : HEAP
seedcrc  : 0xe9f5
[0]crclist   : 0xe714
[1]crclist   : 0xe714
[0]crcmatrix : 0x1fd7
[1]crcmatrix : 0x1fd7
[0]crcstate  : 0x8e3a
[1]crcstate  : 0x8e3a
[0]crcfinal  : 0xa14c
[1]crcfinal  : 0xa14c
Correct operation validated. See README.md for run and reporting rules.
CoreMark 1.0 : 985.221675 / GCC8.4.0 -O3 -fno-strict-aliasing
-fomit-frame-pointer -ffunction-sections -fdata-sections / HEAP /
2:PThreads


% /usr/bin/time -h gmake clean distclean
12,86s real 5,12s user  8,43s sys

% /usr/bin/tim