Re: [VOTE] Apache NuttX 12.2.1 RC0 release
+1 for PinePhone = Compiler + aarch64-none-elf-gcc -v Using built-in specs. COLLECT_GCC=aarch64-none-elf-gcc COLLECT_LTO_WRAPPER=/Applications/ArmGNUToolchain/11.3.rel1/aarch64-none-elf/bin/../libexec/gcc/aarch64-none-elf/11.3.1/lto-wrapper Target: aarch64-none-elf Configured with: /Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/src/gcc/configure --target=aarch64-none-elf --prefix=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/install --with-gmp=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/host-tools --with-mpfr=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/host-tools --with-mpc=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/host-tools --with-isl=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/host-tools --disable-shared --disable-nls --disable-threads --disable-tls --enable-checking=release --enable-languages=c,c++,fortran --with-newlib --with-gnu-as --with-gnu-ld --with-sysroot=/Volumes/data/jenkins/workspace/GNU-toolchain/arm-11/build-aarch64-none-elf/install/aarch64-none-elf --with-pkgversion='Arm GNU Toolchain 11.3.Rel1' --with-bugurl= https://bugs.linaro.org/ Thread model: single Supported LTO compression algorithms: zlib gcc version 11.3.1 20220712 (Arm GNU Toolchain 11.3.Rel1) = Configuration + ./tools/configure.sh pinephone:nsh = Size + aarch64-none-elf-size nuttx text databssdechex filename 221404 12921 41615 275940 435e4 nuttx = NSH Info and Free NuttShell (NSH) NuttX-12.2.1 nsh> uname -a NuttX 12.2.1 148c631a2d Jul 11 2023 09:07:11 arm64 pinephone nsh> free total used freelargest nused nfree Umem: 133410808 551480 132859328 132859232 58 2 Complete Log: https://gist.github.com/lupyuen/8ffc4633da0d5a22885e1ab51753f1f9 Validation Script: https://gist.github.com/lupyuen/78238b05b94f3140a83ae187f6df4c98 Lup On Mon, Jul 10, 2023 at 10:46 PM Alin Jerpelea wrote: > Hello all, > > Apache NuttX 12.2.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 [P]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.2.1-RC0 > > Hash for the release nuttx tag: 148c631a2d252d4d59ae4cd90d1890d2daed381d > > Hash for the release nuttx-apps tag: > 86efbcbee77bc0a29af07807080f4804a37f46a3 > > > [1] https://dist.apache.org/repos/dist/dev/nuttx/12.2.1-RC0/ > [2] > https://raw.githubusercontent.com/apache/nuttx/nuttx-12.2.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 >
Re: adding a new board - files?
Hi Krasimir, On 7/10/23, Krasimir Cheshmedzhiev wrote: > Hi all, > > > > I am working on adding a nucleo-u5a5zj-q to nuttx supported boards. How > (where I can read) to prepare files - those which I created and those which > I changed, to make them part of main source tree? > Please follow the contribution steps: https://nuttx.apache.org/docs/latest/contributing/index.html Any issue, please let us to know. BR, Alan
adding a new board - files?
Hi all, I am working on adding a nucleo-u5a5zj-q to nuttx supported boards. How (where I can read) to prepare files - those which I created and those which I changed, to make them part of main source tree? Best regards
Re: Testing Xbox One S controller on NuttX RTOS
On Mon, Jul 10, 2023 at 6:00 PM Alan C. Assis wrote: > STM32F407, I think you didn't read the blog! :-p Not the whole blog, just the link, sorry :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
Re: [VOTE] Apache NuttX 12.2.1 RC0 release
+1 Tested on STM32F746ZG and STM32H743ZI2 Report: STM32F746ZG with config nucleo144-pysim -rwxr-xr-x 1 bucher bucher 446360 Jul 10 17:43 nuttx -rwxr-xr-x 1 bucher bucher 285336 Jul 10 17:43 nuttx.bin -rw-r--r-- 1 bucher bucher 37 Jul 10 17:43 nuttx.manifest -rw-r--r-- 1 bucher bucher 1598492 Jul 10 17:43 nuttx.map -rw-r--r-- 1 bucher bucher 2406481 Jul 10 17:47 nuttx-export-12.2.1.tar.gz nsh> nsh> ? help usage: help [-v] [] . basename dd false ls nslookup route truncate [ break delroute free lsmod printf set uname ? cat df help mkdir ps sleep umount addroute cd dmesg hexdump mkfifo pwd source unset alias cp echo ifconfig mkrd rm test uptime unalias cmp exec insmod mount rmdir time usleep arp dirname exit kill mv rmmod true xd Builtin Apps: nsh ping renew sh telnetd nsh> ls dev /dev: adc0 can0 console gpio0 gpio1 gpio10 gpio11 gpio12 gpio2 gpio3 gpio4 gpio5 gpio6 gpio7 gpio8 gpio9 null ptmx pwm0 qe2 qe3 telnet ttyS0 nsh> ifconfig eth0 Link encap:Ethernet HWaddr 5e:11:f1:23:d9:ce at UP mtu 1486 inet addr:192.168.178.160 DRaddr:192.168.178.1 Mask:255.255.255.0 lo Link encap:Local Loopback at RUNNING mtu 1518 inet addr:127.0.0.1 DRaddr:127.0.0.1 Mask:255.0.0.0 IPv4 TCP UDP ICMP Received 0009 0009 Dropped IPv4 VHL: Frg: Checksum TCP ACK: SYN: RST: Type Sent 0003 0003 Rexmit nsh> STM32H743ZI2 with config nucleo-h743zi2:pysim -rwxr-xr-x 1 bucher bucher 3454260 Jul 10 17:57 nuttx -rwxr-xr-x 1 bucher bucher 305568 Jul 10 17:57 nuttx.bin -rw-r--r-- 1 bucher bucher 4929643 Jul 10 17:57 nuttx-export-12.2.1.tar.gz -rw-r--r-- 1 bucher bucher 859555 Jul 10 17:57 nuttx.hex -rw-r--r-- 1 bucher bucher 47 Jul 10 17:57 nuttx.manifest -rw-r--r-- 1 bucher bucher 2263304 Jul 10 17:57 nuttx.map nsh> ? help usage: help [-v] [] . basename dd exit ls printf sleep umount [ break delroute false mkdir ps source unset ? cat df free mkfatfs pwd test uptime addroute cd dmesg help mkrd rm time usleep alias cp echo hexdump mount rmdir true wget unalias cmp env ifconfig mv route truncate xd arp dirname exec kill nslookup set uname Builtin Apps: nsh ping renew sh telnetd nsh> ls dev /dev: adc0 console gpio0 gpio1 gpio10 gpio11 gpio12 gpio2 gpio3 gpio4 gpio5 gpio6 gpio7 gpio8 gpio9 null pwm2 qe0 telnet ttyS0 nsh> ifconfig eth0 Link encap:Ethernet HWaddr 52:d3:8e:aa:5d:41 at UP mtu 1486 inet addr:192.168.178.161 DRaddr:192.168.178.1 Mask:255.255.255.0 lo Link encap:Local Loopback at RUNNING mtu 1518 inet addr:127.0.0.1 DRaddr:127.0.0.1 Mask:255.0.0.0 IPv4 TCP UDP ICMP Received 0005 0005 Dropped IPv4 VHL: Frg: Checksum TCP ACK: SYN: RST: Type Sent 0003 0003 Rexmit nsh> Bye Roberto On 7/10/23 16:46, Alin Jerpelea wrote: Hello all, Apache NuttX 12.2.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 [P]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.2.1-RC0 Hash for the release nuttx tag: 148c631a2d252d4d59ae4cd90d1890d2daed381d Hash for the release nuttx-apps tag: 86efbcbee77bc0a29af07807080f4804a37f46a3 [1] https://dist.apache.org/repos/dist/dev/nuttx/12.2.1-RC0/ [2] https://raw.githubusercontent.com/apache/nuttx/nuttx-12.2.1-RC0/ReleaseNotes [3] https://www.apache.org/dev/release.html#approving-a-release [4]
Re: Testing Xbox One S controller on NuttX RTOS
Hi Tomek, On 7/10/23, Tomek CEDRO wrote: > On Mon, Jul 10, 2023 at 3:16 PM Alan C. Assis wrote: >> I decided to test the Xbox Controller driver existent on NuttX source >> tree and it worked, but after few seconds it is loosing the device > > Hey there Alan :-) > > How do you connect to the controller? Is it wireless Bluetooth or USB > cable? > USB Cable, the driver is for USB: drivers/usbhost/usbhost_xboxcontroller.c > What is the chip that you run the NuttX on? ESP32? > STM32F407, I think you didn't read the blog! :-p > If ESP32 and BLE then disconnects may be related to the BLE stack > problems, I think Petro got into that issue recently..? > I think Xbox requires Bluetooth Classic, that currently it not supported on NuttX. Maybe using BlueKitchen on NuttX it could work, but AFAIK nobody integrated it yet. BR, Alan
[VOTE] Apache NuttX 12.2.1 RC0 release
Hello all, Apache NuttX 12.2.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 [P]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.2.1-RC0 Hash for the release nuttx tag: 148c631a2d252d4d59ae4cd90d1890d2daed381d Hash for the release nuttx-apps tag: 86efbcbee77bc0a29af07807080f4804a37f46a3 [1] https://dist.apache.org/repos/dist/dev/nuttx/12.2.1-RC0/ [2] https://raw.githubusercontent.com/apache/nuttx/nuttx-12.2.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
Re: Testing Xbox One S controller on NuttX RTOS
On Mon, Jul 10, 2023 at 3:16 PM Alan C. Assis wrote: > I decided to test the Xbox Controller driver existent on NuttX source > tree and it worked, but after few seconds it is loosing the device Hey there Alan :-) How do you connect to the controller? Is it wireless Bluetooth or USB cable? What is the chip that you run the NuttX on? ESP32? If ESP32 and BLE then disconnects may be related to the BLE stack problems, I think Petro got into that issue recently..? -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
RE: Testing Xbox One S controller on NuttX RTOS
cool De: Alan C. Assis Enviado: segunda-feira, 10 de julho de 2023 13:16 Para: dev Assunto: Testing Xbox One S controller on NuttX RTOS Dear NuttXers, I decided to test the Xbox Controller driver existent on NuttX source tree and it worked, but after few seconds it is loosing the device file: https://acassis.wordpress.com/2023/07/08/testing-xbox-one-s-controller-on-nuttx-rtos/ I'm investigating the issue, case someone else wants to help, please find attached by board config. BR, Alan
Testing Xbox One S controller on NuttX RTOS
Dear NuttXers, I decided to test the Xbox Controller driver existent on NuttX source tree and it worked, but after few seconds it is loosing the device file: https://acassis.wordpress.com/2023/07/08/testing-xbox-one-s-controller-on-nuttx-rtos/ I'm investigating the issue, case someone else wants to help, please find attached by board config. BR, Alan # # Automatically generated file; DO NOT EDIT. # NuttX/x86_64 Configuration # # # License Setup # # CONFIG_ALLOW_BSD_COMPONENTS is not set # CONFIG_ALLOW_GPL_COMPONENTS is not set # CONFIG_ALLOW_MIT_COMPONENTS is not set # # Build Setup # # CONFIG_EXPERIMENTAL is not set # CONFIG_DEFAULT_SMALL is not set CONFIG_HOST_LINUX=y # CONFIG_HOST_MACOS is not set # CONFIG_HOST_WINDOWS is not set # CONFIG_HOST_OTHER is not set # # Build Configuration # CONFIG_APPS_DIR="../apps" CONFIG_BASE_DEFCONFIG="stm32f4discovery:usbmsc-dirty-dirty-dirty-dirty-dirty" CONFIG_BUILD_FLAT=y # CONFIG_BUILD_2PASS is not set # # Binary Output Formats # CONFIG_INTELHEX_BINARY=y # CONFIG_MOTOROLA_SREC is not set CONFIG_RAW_BINARY=y # CONFIG_UBOOT_UIMAGE is not set # CONFIG_DFU_BINARY is not set # # Customize Header Files # # CONFIG_ARCH_HAVE_STDINT_H is not set # CONFIG_ARCH_HAVE_STDBOOL_H is not set # CONFIG_ARCH_HAVE_MATH_H is not set # CONFIG_ARCH_FLOAT_H is not set CONFIG_ARCH_HAVE_STDARG_H=y # CONFIG_ARCH_STDARG_H is not set CONFIG_ARCH_HAVE_SETJMP=y # CONFIG_ARCH_SETJMP_H is not set CONFIG_ARCH_NONE_DEBUG_H=y # CONFIG_ARCH_DEBUG_H is not set # CONFIG_ARCH_CHIP_DEBUG_H is not set # # Debug Options # CONFIG_FORTIFY_SOURCE=0 CONFIG_NDEBUG=y CONFIG_DEBUG_ALERT=y # CONFIG_DEBUG_FEATURES is not set # CONFIG_DEBUG_TCBINFO is not set CONFIG_ARCH_HAVE_STACKCHECK=y # CONFIG_STACK_COLORATION is not set # CONFIG_STACK_CANARIES is not set # CONFIG_STACK_USAGE is not set CONFIG_ARCH_HAVE_HEAPCHECK=y # CONFIG_HEAP_COLORATION is not set CONFIG_DEBUG_SYMBOLS=y # CONFIG_FRAME_POINTER is not set CONFIG_ARCH_HAVE_CUSTOMOPT=y CONFIG_DEBUG_NOOPT=y # CONFIG_DEBUG_CUSTOMOPT is not set # CONFIG_DEBUG_FULLOPT is not set CONFIG_DEBUG_OPT_UNUSED_SECTIONS=y CONFIG_DEBUG_LINK_MAP=y # CONFIG_CCACHE is not set # # System Type # CONFIG_ARCH_ARM=y # CONFIG_ARCH_ARM64 is not set # CONFIG_ARCH_AVR is not set # CONFIG_ARCH_HC is not set # CONFIG_ARCH_MIPS is not set # CONFIG_ARCH_MISOC is not set # CONFIG_ARCH_RENESAS is not set # CONFIG_ARCH_RISCV is not set # CONFIG_ARCH_SIM is not set # CONFIG_ARCH_X86 is not set # CONFIG_ARCH_X86_64 is not set # CONFIG_ARCH_XTENSA is not set # CONFIG_ARCH_Z16 is not set # CONFIG_ARCH_Z80 is not set # CONFIG_ARCH_OR1K is not set # CONFIG_ARCH_SPARC is not set CONFIG_ARCH="arm" # # ARM Options # # CONFIG_ARM_TOOLCHAIN_IAR is not set # CONFIG_ARM_TOOLCHAIN_BUILDROOT is not set # CONFIG_ARM_TOOLCHAIN_BUILDROOT_OABI is not set CONFIG_ARM_TOOLCHAIN_GNU_EABI=y # CONFIG_ARM_TOOLCHAIN_GNU_OABI is not set # CONFIG_ARM_TOOLCHAIN_CLANG is not set # CONFIG_ARM_TOOLCHAIN_ARMCLANG is not set # CONFIG_ARCH_CHIP_FVP_ARMV8R_AARCH32 is not set # CONFIG_ARCH_CHIP_C5471 is not set # CONFIG_ARCH_CHIP_DM320 is not set # CONFIG_ARCH_CHIP_EFM32 is not set # CONFIG_ARCH_CHIP_EOSS3 is not set # CONFIG_ARCH_CHIP_GD32F4 is not set # CONFIG_ARCH_CHIP_IMX1 is not set # CONFIG_ARCH_CHIP_IMXRT is not set # CONFIG_ARCH_CHIP_KINETIS is not set # CONFIG_ARCH_CHIP_KL is not set # CONFIG_ARCH_CHIP_LC823450 is not set # CONFIG_ARCH_CHIP_LM is not set # CONFIG_ARCH_CHIP_LPC17XX_40XX is not set # CONFIG_ARCH_CHIP_LPC214X is not set # CONFIG_ARCH_CHIP_LPC2378 is not set # CONFIG_ARCH_CHIP_LPC31XX is not set # CONFIG_ARCH_CHIP_LPC43XX is not set # CONFIG_ARCH_CHIP_LPC54XX is not set # CONFIG_ARCH_CHIP_MAX326XX is not set # CONFIG_ARCH_CHIP_MOXART is not set # CONFIG_ARCH_CHIP_NRF52 is not set # CONFIG_ARCH_CHIP_NUC1XX is not set # CONFIG_ARCH_CHIP_RP2040 is not set # CONFIG_ARCH_CHIP_S32K1XX is not set # CONFIG_ARCH_CHIP_S32K3XX is not set # CONFIG_ARCH_CHIP_SAMA5 is not set # CONFIG_ARCH_CHIP_SAMD2X is not set # CONFIG_ARCH_CHIP_SAML2X is not set # CONFIG_ARCH_CHIP_SAMD5X is not set # CONFIG_ARCH_CHIP_SAME5X is not set # CONFIG_ARCH_CHIP_SAM34 is not set # CONFIG_ARCH_CHIP_SAMV7 is not set CONFIG_ARCH_CHIP_STM32=y # CONFIG_ARCH_CHIP_STM32F0 is not set # CONFIG_ARCH_CHIP_STM32L0 is not set # CONFIG_ARCH_CHIP_STM32G0 is not set # CONFIG_ARCH_CHIP_STM32F7 is not set # CONFIG_ARCH_CHIP_STM32H7 is not set # CONFIG_ARCH_CHIP_STM32L4 is not set # CONFIG_ARCH_CHIP_STM32L5 is not set # CONFIG_ARCH_CHIP_STM32U5 is not set # CONFIG_ARCH_CHIP_STM32WB is not set # CONFIG_ARCH_CHIP_STM32WL5 is not set # CONFIG_ARCH_CHIP_STR71X is not set # CONFIG_ARCH_CHIP_TMS570 is not set # CONFIG_ARCH_CHIP_TIVA is not set # CONFIG_ARCH_CHIP_XMC4 is not set # CONFIG_ARCH_CHIP_CXD56XX is not set # CONFIG_ARCH_CHIP_PHY62XX is not set # CONFIG_ARCH_CHIP_TLSR82 is not set # CONFIG_ARCH_CHIP_ARM_CUSTOM is not set # CONFIG_ARCH_ARM7TDMI is not set # CONFIG_ARCH_ARM920T is not set # CONFIG_ARCH_ARM926EJS is not set # CONFIG_ARCH_ARM1136J is not
