Re: [VOTE] Apache NuttX 12.6.0 RC1 release
arm-none-eabi-gcc -v Using built-in specs. COLLECT_GCC=arm-none-eabi-gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-none-eabi/13.2.1/lto-wrapper Target: arm-none-eabi Configured with: ../configure --build=x86_64-linux-gnu --prefix=/usr --includedir='/usr/lib/include' --mandir='/usr/lib/share/man' --infodir='/usr/lib/share/info' --sysconfdir=/etc --localstatedir=/var --disable-option-checking --disable-silent-rules --libdir='/usr/lib/lib/x86_64-linux-gnu' --libexecdir='/usr/lib/lib/x86_64-linux-gnu' --disable-maintainer-mode --disable-dependency-tracking --mandir=/usr/share/man --enable-languages=c,c++,lto --enable-multilib --disable-decimal-float --disable-libffi --disable-libgomp --disable-libmudflap --disable-libquadmath --disable-libssp --disable-libstdcxx-pch --disable-nls --disable-shared --disable-threads --enable-tls --build=x86_64-linux-gnu --target=arm-none-eabi --with-system-zlib --with-gnu-as --with-gnu-ld --with-pkgversion=15:13.2.rel1-2 --without-included-gettext --prefix=/usr/lib --infodir=/usr/share/doc/gcc-arm-none-eabi/info --htmldir=/usr/share/doc/gcc-arm-none-eabi/html --pdfdir=/usr/share/doc/gcc-arm-none-eabi/pdf --bindir=/usr/bin --libexecdir=/usr/lib --libdir=/usr/lib --disable-libstdc++-v3 --host=x86_64-linux-gnu --with-headers=no --without-newlib --with-multilib-list=rmprofile,aprofile ASFLAGS= ASFLAGS_FOR_BUILD= CFLAGS='-g -O2 -ffile-prefix-map=/build/reproducible-path/gcc-arm-none-eabi-13.2.rel1=. -fstack-protector-strong -fstack-clash-protection -fcf-protection' 'CFLAGS_FOR_BUILD=-g -O2' CPPFLAGS='-Wdate-time -D_FORTIFY_SOURCE=2' CPPFLAGS_FOR_BUILD= CXXFLAGS='-g -O2 -ffile-prefix-map=/build/reproducible-path/gcc-arm-none-eabi-13.2.rel1=. -fstack-protector-strong -fstack-clash-protection -fcf-protection' 'CXXFLAGS_FOR_BUILD=-g -O2' DFLAGS=-frelease DFLAGS_FOR_BUILD=-frelease FCFLAGS='-g -O2 -ffile-prefix-map=/build/reproducible-path/gcc-arm-none-eabi-13.2.rel1=. -fstack-protector-strong -fstack-clash-protection -fcf-protection' 'FCFLAGS_FOR_BUILD=-g -O2' FFLAGS='-g -O2 -ffile-prefix-map=/build/reproducible-path/gcc-arm-none-eabi-13.2.rel1=. -fstack-protector-strong -fstack-clash-protection -fcf-protection' 'FFLAGS_FOR_BUILD=-g -O2' LDFLAGS=-Wl,-z,relro LDFLAGS_FOR_BUILD= OBJCFLAGS='-g -O2 -ffile-prefix-map=/build/reproducible-path/gcc-arm-none-eabi-13.2.rel1=. -fstack-protector-strong -fstack-clash-protection -fcf-protection' 'OBJCFLAGS_FOR_BUILD=-g -O2' OBJCXXFLAGS='-g -O2 -ffile-prefix-map=/build/reproducible-path/gcc-arm-none-eabi-13.2.rel1=. -fstack-protector-strong -fstack-clash-protection -fcf-protection' 'OBJCXXFLAGS_FOR_BUILD=-g -O2' INHIBIT_LIBC_CFLAGS=-DUSE_TM_CLONE_REGISTRY=0 AR_FOR_TARGET=arm-none-eabi-ar AS_FOR_TARGET=arm-none-eabi-as LD_FOR_TARGET=arm-none-eabi-ld NM_FOR_TARGET=arm-none-eabi-nm OBJDUMP_FOR_TARGET=arm-none-eabi-objdump RANLIB_FOR_TARGET=arm-none-eabi-ranlib READELF_FOR_TARGET=arm-none-eabi-readelf STRIP_FOR_TARGET=arm-none-eabi-strip SED=/bin/sed SHELL=/bin/sh BASH=/bin/bash CONFIG_SHELL=/bin/bash Thread model: single Supported LTO compression algorithms: zlib gcc version 13.2.1 20231009 (15:13.2.rel1-2) Bye Roberto On 7/25/24 3:28 PM, Alan C. Assis wrote: Hi Roberto, What toolchain did you use? Please include it as Mr Lup did in previous email. BR, Alan On Thu, Jul 25, 2024 at 5:28 AM Roberto Bucher wrote: +1 Tested on nucleo-h745ZI-Q, nucleo-H743ZI2 and nucleo-F746ZG In addition I've generated code fusing pysimCoder for a nucleo-F746ZG board (PWM+Encoders) -> OK Ciao Roberto Results: *nucleo-h745zi:pysim_cm7 * -rwxrwxr-x 1 bucher bucher 3681776 Jul 25 10:00 nuttx -rwxrwxr-x 1 bucher bucher 316900 Jul 25 10:00 nuttx.bin -rw-rw-r-- 1 bucher bucher 6194693 Jul 25 10:00 nuttx-export-12.6.0.tar.gz -rw-rw-r-- 1 bucher bucher 891423 Jul 25 10:00 nuttx.hex -rw-rw-r-- 1 bucher bucher 47 Jul 25 10:00 nuttx.manifest -rw-rw-r-- 1 bucher bucher 2317845 Jul 25 10:00 nuttx.map Builtin Apps: nshping renew sh telnetd nsh> ifconfig eth0Link encap:Ethernet HWaddr d2:a8:9c:1c:fc:bf at UP mtu 1486 inet addr:192.168.1.23 DRaddr:192.168.1.1 Mask:255.255.255.0 loLink 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 0002 0002 Dropped IPv4VHL: Frg: Checksum TCP ACK: SYN: RST: Type Sent 0002 0002 Rexmit nsh> free total used freemaxusedmaxfree nused nfree Umem: 678860 18404 660456 18792 481736 55 4 === *nucleo-h743zi2:pysim* -rwxrwxr-x 1 bucher bucher 3670116 Jul 25 10:03 nuttx -rwxrwxr-x 1 bucher bucher 316508 Jul 25 10:03 nutt
Re: [VOTE] Apache NuttX 12.6.0 RC1 release
+1 Tested on nucleo-h745ZI-Q, nucleo-H743ZI2 and nucleo-F746ZG In addition I've generated code fusing pysimCoder for a nucleo-F746ZG board (PWM+Encoders) -> OK Ciao Roberto Results: *nucleo-h745zi:pysim_cm7 * -rwxrwxr-x 1 bucher bucher 3681776 Jul 25 10:00 nuttx -rwxrwxr-x 1 bucher bucher 316900 Jul 25 10:00 nuttx.bin -rw-rw-r-- 1 bucher bucher 6194693 Jul 25 10:00 nuttx-export-12.6.0.tar.gz -rw-rw-r-- 1 bucher bucher 891423 Jul 25 10:00 nuttx.hex -rw-rw-r-- 1 bucher bucher 47 Jul 25 10:00 nuttx.manifest -rw-rw-r-- 1 bucher bucher 2317845 Jul 25 10:00 nuttx.map Builtin Apps: nsh ping renew sh telnetd nsh> ifconfig eth0 Link encap:Ethernet HWaddr d2:a8:9c:1c:fc:bf at UP mtu 1486 inet addr:192.168.1.23 DRaddr:192.168.1.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 0002 0002 Dropped IPv4 VHL: Frg: Checksum TCP ACK: SYN: RST: Type Sent 0002 0002 Rexmit nsh> free total used free maxused maxfree nused nfree Umem: 678860 18404 660456 18792 481736 55 4 === *nucleo-h743zi2:pysim* -rwxrwxr-x 1 bucher bucher 3670116 Jul 25 10:03 nuttx -rwxrwxr-x 1 bucher bucher 316508 Jul 25 10:03 nuttx.bin -rw-rw-r-- 1 bucher bucher 6183828 Jul 25 10:03 nuttx-export-12.6.0.tar.gz -rw-rw-r-- 1 bucher bucher 890314 Jul 25 10:03 nuttx.hex -rw-rw-r-- 1 bucher bucher 47 Jul 25 10:03 nuttx.manifest -rw-rw-r-- 1 bucher bucher 2306841 Jul 25 10:03 nuttx.map Builtin Apps: nsh ping renew sh telnetd nsh> ifconfig eth0 Link encap:Ethernet HWaddr 52:d3:8e:aa:5d:41 at UP mtu 1486 inet addr:192.168.1.251 DRaddr:192.168.1.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 0002 0002 Dropped IPv4 VHL: Frg: Checksum TCP ACK: SYN: RST: Type Sent 0002 0002 Rexmit nsh> free total used free maxused maxfree nused nfree Umem: 973772 18460 955312 18848 481736 58 5 = *nucleo-144:f746-pysim* -rwxrwxr-x 1 bucher bucher 463584 Jul 25 10:04 nuttx/nuttx -rwxrwxr-x 1 bucher bucher 299904 Jul 25 10:04 nuttx/nuttx.bin -rw-rw-r-- 1 bucher bucher 3395033 Jul 25 10:04 nuttx/nuttx-export-12.6.0.tar.gz -rw-rw-r-- 1 bucher bucher 37 Jul 25 10:04 nuttx/nuttx.manifest -rw-rw-r-- 1 bucher bucher 1684836 Jul 25 10:04 nuttx/nuttx.map Builtin Apps: nsh ping renew sh telnetd nsh> ifconfig eth0 Link encap:Ethernet HWaddr 5e:11:f1:23:d9:ce at UP mtu 1486 inet addr:192.168.1.213 DRaddr:192.168.1.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 0002 0002 Dropped IPv4 VHL: Frg: Checksum TCP ACK: SYN: RST: Type Sent 0003 0003 Rexmit nsh> free total used free maxused maxfree nused nfree Umem: 218772 14124 204648 14496 201888 54 4 === On 7/25/24 9:41 AM, Alin Jerpelea wrote: Hello all, Apache NuttX 12.6.0 RC1 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.6.0-RC1 Hash for the release nuttx tag: 7a865b247969a9dbc06eddcaf58c59a14dd05d6d Hash for
Re: Problems Flashing
Hi Felix I use the attache script to flash some F7 boards give simply $ flash_f7 nuttx Bye Roberto On 6/12/24 7:35 AM, Felix Leonbacher wrote: Hey Guys, I am an embedded systems Student in Germany and wanted to use ur apache nuttx in my project. Sadly I am unable to flash it. I have a STM32F207 nucleo-144 and when I come to openocd -f interface/stlink-v2.cfg -f target/stm32f2x.cfg -c 'init' \ -c 'program nuttx/nuttx.bin verify reset' -c 'shutdown', it says checksum mismatch I'd like to use your product, its for a noncommercial use (just my bachelor). #!/usr/bin/sh INSTALL_DIR=/usr OPENOCD_DIR=$INSTALL_DIR/share/openocd/scripts FLASH=$INSTALL_DIR/bin/openocd FLASH_FLAGS="-f $OPENOCD_DIR/interface/stlink.cfg -f $OPENOCD_DIR/target/stm32f7x.cfg" $FLASH $FLASH_FLAGS -c "program $1 verify reset exit"
Re: [VOTE] Apache NuttX 12.5.1 RC0 release
+1 Built on Debian trixie with this toolchains: arm-none-eabi-gcc -v Supported LTO compression algorithms: zlib gcc version 13.2.1 20231009 (15:13.2.rel1-2) nucleo-144:f746-pysim -rwxr-xr-x 1 bucher bucher 463280 Apr 9 10:46 nuttx -rwxr-xr-x 1 bucher bucher 298640 Apr 9 10:46 nuttx.bin -rw-r--r-- 1 bucher bucher 3385642 Apr 9 10:46 nuttx-export-12.5.1.tar.gz -rw-r--r-- 1 bucher bucher 37 Apr 9 10:46 nuttx.manifest -rw-r--r-- 1 bucher bucher 1685524 Apr 9 10:46 nuttx.map nsh> uname -a NuttX 12.5.1 9e8753d625 Apr 9 2024 10:46:16 arm nucleo-144 nsh> free total used free maxused maxfree nused nfree Umem: 220612 16564 204048 17036 202032 58 4 nsh> === nucleo-h745zi:pysim_cm7 -rwxr-xr-x 1 bucher bucher 3691012 Apr 9 10:50 nuttx -rwxr-xr-x 1 bucher bucher 315644 Apr 9 10:50 nuttx.bin -rw-r--r-- 1 bucher bucher 6186858 Apr 9 10:50 nuttx-export-12.5.1.tar.gz -rw-r--r-- 1 bucher bucher 887897 Apr 9 10:50 nuttx.hex -rw-r--r-- 1 bucher bucher 47 Apr 9 10:50 nuttx.manifest -rw-r--r-- 1 bucher bucher 2320429 Apr 9 10:50 nuttx.map nsh> nsh> uname -a NuttX 12.5.1 9e8753d625 Apr 9 2024 10:49:58 arm nucleo-h745zi nsh> free total used free maxused maxfree nused nfree Umem: 680700 22420 658280 22372 481880 59 4 nsh> == nucleo-h743zi2:pysim -rwxr-xr-x 1 bucher bucher 3679324 Apr 9 10:52 nuttx -rwxr-xr-x 1 bucher bucher 315260 Apr 9 10:52 nuttx.bin -rw-r--r-- 1 bucher bucher 6177759 Apr 9 10:52 nuttx-export-12.5.1.tar.gz -rw-r--r-- 1 bucher bucher 886817 Apr 9 10:52 nuttx.hex -rw-r--r-- 1 bucher bucher 47 Apr 9 10:52 nuttx.manifest -rw-r--r-- 1 bucher bucher 2309503 Apr 9 10:52 nuttx.map nsh> uname -a NuttX 12.5.1 9e8753d625 Apr 9 2024 10:52:06 arm nucleo-h743zi2 nsh> free total used free maxused maxfree nused nfree Umem: 975612 22476 953136 22412 481880 62 5 nsh> Generated code for pysimCoder tested on NUCLEO-F746ZG -> OK Bye Roberto
Re: [VOTE] Apache NuttX 12.5.0 RC0 release
Built on Debian trixie with this toolchains: arm-none-eabi-gcc -v Supported LTO compression algorithms: zlib gcc version 13.2.1 20231009 (15:13.2.rel1-2) bucher@debian:~/ToDo/NUTTX_release_test/nuttx$ arm-none-eabi-size nuttx text data bss dec hex filename 296304 2336 36948 335588 51ee4 nuttx -rwxr-xr-x 1 bucher bucher 463280 Apr 1 15:38 nuttx -rwxr-xr-x 1 bucher bucher 298640 Apr 1 15:38 nuttx.bin -rw-r--r-- 1 bucher bucher 3385591 Apr 1 15:38 nuttx-export-12.5.0.tar.gz -rw-r--r-- 1 bucher bucher 37 Apr 1 15:38 nuttx.manifest -rw-r--r-- 1 bucher bucher 1685524 Apr 1 15:38 nuttx.map After downloading of nuttx on the nucleo-f746zg board: nsh> uname -a NuttX 12.5.0 34f182c62a Apr 1 2024 15:37:57 arm nucleo-144 nsh> free total used free maxused maxfree nused nfree Umem: 220612 16564 204048 17036 202032 58 4 For the nucleo--h745zi:pysim_cm7 bucher@debian:~/ToDo/NUTTX_release_test/nuttx$ arm-none-eabi-size nuttx text data bss dec hex filename 313248 2396 36444 352088 55f58 nuttx nsh> uname -a NuttX 12.5.0 34f182c62a Apr 1 2024 15:49:02 arm nucleo-h745zi nsh> free total used free maxused maxfree nused nfree Umem: 680700 22420 658280 22372 481880 59 4 Bye Roberto On 4/1/24 3:33 PM, Alan C. Assis wrote: Roberto, Please send information about your toolchain (i.e. use: arm-none-eabi-gcc -v) and the final binary size (i.e.: arm-none-eabi-size nuttx). BR, Alan On Mon, Apr 1, 2024 at 5:46 AM Roberto Bucher wrote: +1 Built for: nucleo-144:f746-pysim nucleo-h745zi:pysim_cm7 nucleo-h743zi2:pysim Generated export for nucleo-144:f746-pysim and tested with pysimCoder Ciao Roberto On 4/1/24 9:41 AM, Alin Jerpelea wrote: Hello all, Apache NuttX 12.5.0 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.0-RC0 Hash for the release nuttx tag: 34f182c62a857ce1911138e202028616c70a2ac6 Hash for the release nuttx-apps tag: e2805fc9c451afa0953502152c2a61f4a40d6ba5 [1] https://dist.apache.org/repos/dist/dev/nuttx/12.5.0-RC0/ [2] https://raw.githubusercontent.com/apache/nuttx/nuttx-12.5.0-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: [VOTE] Apache NuttX 12.5.0 RC0 release
+1 Built for: nucleo-144:f746-pysim nucleo-h745zi:pysim_cm7 nucleo-h743zi2:pysim Generated export for nucleo-144:f746-pysim and tested with pysimCoder Ciao Roberto On 4/1/24 9:41 AM, Alin Jerpelea wrote: Hello all, Apache NuttX 12.5.0 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.0-RC0 Hash for the release nuttx tag: 34f182c62a857ce1911138e202028616c70a2ac6 Hash for the release nuttx-apps tag: e2805fc9c451afa0953502152c2a61f4a40d6ba5 [1] https://dist.apache.org/repos/dist/dev/nuttx/12.5.0-RC0/ [2] https://raw.githubusercontent.com/apache/nuttx/nuttx-12.5.0-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: [OT] GSoC: We still have two projects waiting for contributors
I tested my last microROS git and I found out that the compilation *is ok* if I do a *"make" with only 1 thread *A soon as I try to do a "make -j2" the compilation failed. I can try to find out where. Bye Roberto On 3/20/24 1:02 AM, Alan C. Assis wrote: Hi NuttX users and developers, We have two projects that are still missing contributors: Device Tree and MicroROS. This is the listing of projects and contributors interested on each project: Rust integration on NuttX - Contributor: RUSHABH GALA NuttX NAND Flash Subsystem -- Contributor: Saurav Pal TinyGL support on NuttX --- Contributor: Victor Suarez Rovere Add X11 graphic support on NuttX using NanoX Contributor: Shijo George Device Tree support for NuttX - Contributor: ? Micro-ROS integration on NuttX -- Contributor: ? If you want to participate, please let me know. Each contributor needs to prepare the Proposal before April 2! It is important to remember that not all projects will be accepted by GSoC, because ASF has a limited slot (I don't know how many slots Google reserves for Apache). Best Regards, Alan
Re: [OT] GSoC: We still have two projects waiting for contributors
Hi Alan at present, my previous MicroROS git doesn't compile correctly (I think that something has changed in the original git). I can help to find out the problem if required, but, as you now, I'm retired now and I can't follow students in the GSoC! Ciao Roberto On 3/20/24 1:02 AM, Alan C. Assis wrote: Hi NuttX users and developers, We have two projects that are still missing contributors: Device Tree and MicroROS. This is the listing of projects and contributors interested on each project: Rust integration on NuttX - Contributor: RUSHABH GALA NuttX NAND Flash Subsystem -- Contributor: Saurav Pal TinyGL support on NuttX --- Contributor: Victor Suarez Rovere Add X11 graphic support on NuttX using NanoX Contributor: Shijo George Device Tree support for NuttX - Contributor: ? Micro-ROS integration on NuttX -- Contributor: ? If you want to participate, please let me know. Each contributor needs to prepare the Proposal before April 2! It is important to remember that not all projects will be accepted by GSoC, because ASF has a limited slot (I don't know how many slots Google reserves for Apache). Best Regards, Alan
Problems by pull request and macos
My Pull request fails on 2 Build: macos (sim-01) with this error: Error: /Applications/Xcode_15.0.1.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/mach/vm_page_size.h:60:44: error: expected ';' after top level declarator extern vm_size_t vm_kernel_page_mask __OSX_AVAILABLE_STARTING(__MAC_10_9, __IPHONE_7_0); andseems to skip the macos (sim-02) I can't understand why, because the files are outside of the usual NuttX tree... Best regards Roberto
Re: STM32H7 board with ethernet
Tested on NUCLEO-H743ZI2 board with ./tools/configure.sh nucleo-h743zi2:pysim My PC has WIFI and the nucleo board connected to the WIFI box bucher@debian:~/sviluppo/NUTTX/nuttx$ tio /dev/ttyACM0 [18:58:30.631] tio v2.7 [18:58:30.631] Press ctrl-t q to quit [18:58:30.631] Connected telnetd [5:100] NuttShell (NSH) NuttX-12.4.0 nsh> ifconfig eth0 Link encap:Ethernet HWaddr 52:d3:8e:aa:5d:41 at UP mtu 1486 inet addr:192.168.1.251 DRaddr:192.168.1.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 0002 0002 Dropped IPv4 VHL: Frg: Checksum TCP ACK: SYN: RST: Type Sent 0002 0002 Rexmit nsh> ping 192.168.1.155 PING 192.168.1.155 56 bytes of data 56 bytes from 192.168.1.155: icmp_seq=0 time=89.0 ms 56 bytes from 192.168.1.155: icmp_seq=1 time=116.0 ms 56 bytes from 192.168.1.155: icmp_seq=2 time=47.0 ms 56 bytes from 192.168.1.155: icmp_seq=3 time=82.0 ms 56 bytes from 192.168.1.155: icmp_seq=4 time=112.0 ms 56 bytes from 192.168.1.155: icmp_seq=5 time=40.0 ms 56 bytes from 192.168.1.155: icmp_seq=6 time=77.0 ms 56 bytes from 192.168.1.155: icmp_seq=7 time=110.0 ms 56 bytes from 192.168.1.155: icmp_seq=8 time=42.0 ms 56 bytes from 192.168.1.155: icmp_seq=9 time=74.0 ms 10 packets transmitted, 10 received, 0% packet loss, time 10010 ms rtt min/avg/max/mdev = 40.000/78.900/116.000/27.332 ms nsh> Best regards Roberto On 2/9/24 18:23, Simon Filgis wrote: Dear all, I'm back at the board (NUCLEO-H743ZI2). Using latest master (with https://github.com/apache/nuttx/commit/31817335e453eec65e8f5d1163c32efd5da373cb) and pysim config is stable. But I am not able to ping. I tried the following setups: PC <-> Nucleo-Board PC <-> Switch <-> Nucleo-Board *Here the output from the board:* nsh> ping 192.168.178.1 PING 192.168.178.1 56 bytes of data No response from 192.168.178.1: icmp_seq=0 time=1000 ms No response from 192.168.178.1: icmp_seq=1 time=1000 ms No response from 192.168.178.1: icmp_seq=2 time=1000 ms No response from 192.168.178.1: icmp_seq=3 time=1000 ms No response from 192.168.178.1: icmp_seq=4 time=1000 ms No response from 192.168.178.1: icmp_seq=5 time=1000 ms No response from 192.168.178.1: icmp_seq=6 time=1000 ms No response from 192.168.178.1: icmp_seq=7 time=1000 ms No response from 192.168.178.1: icmp_seq=8 time=1000 ms No response from 192.168.178.1: icmp_seq=9 time=1000 ms 10 packets transmitted, 0 received, 100% packet loss, time 10010 ms nsh> ifconfig eth0Link encap:Ethernet HWaddr 02:55:10:e5:49:a2 at UP mtu 1486 inet addr:192.168.178.5 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 *0020* 001e *--> there seems to be some traffic* Dropped 0002 IPv4VHL: Frg: Checksum TCP ACK: SYN: RST: Type Sent 000a 000a Rexmit nsh> *And the output of the PC:* ping 192.168.178.5 PING 192.168.178.5 (192.168.178.5) 56(84) bytes of data. From 192.168.178.1 icmp_seq=1 Destination Host Unreachable From 192.168.178.1 icmp_seq=2 Destination Host Unreachable What could it be that I'm doing wrong? Is using DHCP mandatory with this config? I set a initial IP adress via menuconfig and I also tried with ifconfig eth0 192 Thanks for your help, Simon -- Hard- and Softwaredevelopment Consultant Ingenieurbüro-Filgis USt-IdNr.: DE305343278 On Wed, Feb 7, 2024 at 10:58 AM Roberto Bucher < roberto.bucher.2...@gmail.com> wrote: I did some tests and sometimes it works and sometimes (the most times...) it gives the error... The error usually appears when I give the command nsh> ifconfig or nsh> renew eth0 but not all the times. I think that it can be a problem with memory sizes; I'll try more investigations BR Roberto NuttShell (NSH) NuttX-12.4.0-RC0 nsh> ping 192.168.1.155 PING 192.168.1.155 56 bytes of data 56 bytes from 192.168.1.155: icmp_seq=0 time=38.0 ms 56 bytes from 192.168.1.155: icmp_seq=1 time=62.0 ms 56 bytes from 192.168.1.155: icmp_seq=2 time=104.0 ms 56 bytes from 192.168.1.155: icmp_seq=3 time=124.0 ms 56 bytes from 192.168.1.155: icmp_seq=4 time=62.0 ms 56 bytes from 192.168.1.155: icmp_seq=5 time=84.0 ms 56 bytes from 192.168.1.155: icmp_seq=6 time=12.0 ms 56 bytes from 192.168.1.155: icmp_seq=7 time=46.0 ms 56 bytes from 192.168.1.155: icmp_seq=8 time=75.0 ms 56 bytes from 192.168.1.155: icmp_seq=
NuttX correct version
Hi When I create a library export of the NuttX project I receive a library *nuttx-export-12.4.0-RC0.tar.gz*. Is this correct or I have to get a *12.4.0* version? Thanks in advance Roberto
Re: STM32H7 board with ethernet
I did some tests and sometimes it works and sometimes (the most times...) it gives the error... The error usually appears when I give the command nsh> ifconfig or nsh> renew eth0 but not all the times. I think that it can be a problem with memory sizes; I'll try more investigations BR Roberto NuttShell (NSH) NuttX-12.4.0-RC0 nsh> ping 192.168.1.155 PING 192.168.1.155 56 bytes of data 56 bytes from 192.168.1.155: icmp_seq=0 time=38.0 ms 56 bytes from 192.168.1.155: icmp_seq=1 time=62.0 ms 56 bytes from 192.168.1.155: icmp_seq=2 time=104.0 ms 56 bytes from 192.168.1.155: icmp_seq=3 time=124.0 ms 56 bytes from 192.168.1.155: icmp_seq=4 time=62.0 ms 56 bytes from 192.168.1.155: icmp_seq=5 time=84.0 ms 56 bytes from 192.168.1.155: icmp_seq=6 time=12.0 ms 56 bytes from 192.168.1.155: icmp_seq=7 time=46.0 ms 56 bytes from 192.168.1.155: icmp_seq=8 time=75.0 ms 56 bytes from 192.168.1.155: icmp_seq=9 time=106.0 ms 10 packets transmitted, 10 received, 0% packet loss, time 10010 ms rtt min/avg/max/mdev = 12.000/71.300/124.000/32.655 ms nsh> ifconfig eth0 Link encap:Ethernet HWaddr 52:d3:8e:aa:5d:41 at UP mtu 1486 inet addr:192.168.1.251 DRaddr:192.168.1.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 000c 0002 000a Dropped IPv4 VHL: Frg: Checksum TCP ACK: SYN: RST: Type Sent 000c 0002 000a Rexmit On 2/6/24 16:55, Gregory Nutt wrote: The network monitor is part of apps/netutils/netinit so it is not a part of NSH. NSH can automatically perform the network initialization if so configured and which, optionally, starts the network monitor thread. But the logic is not architecturally a part of NSH nor does it depend on N SH. On 2/6/2024 9:32 AM, Nathan Hartman wrote: On Tue, Feb 6, 2024 at 8:45 AM Sebastien Lorquet wrote: However, the default network configuration provided in NuttX examples is cumbersome and too much linked with NSH It can work for simple tests and demos, but you will have to write a proper network management daemon if you plan to use more than one network app. It would be a nice thing if the network management daemon could be factored out of NSH so that boards that don't run NSH could have the same network management without implementing it again. Cheers Nathan
Re: STM32H7 board with ethernet
The STM32H743ZI2 is quite complete. We used it with pysimCoder (ADC, encoders, PWM, digital I/O, network, but not CAN bus yet) Roberto On 2/6/24 11:57, Alan C. Assis wrote: stm32h745i-disco is a great option! Ethernet and LCD On Tuesday, February 6, 2024, Simon Filgis wrote: Dear all, Can anybody recommend a stm32h7 board with ethernet that is well supported by nuttx? Thanks in advance, Simon
Encoder STM32F7
Hi after some tests it seems that the quadratic encoder of the STM32F7 is set in X2 mode. I can't see a method to set it in X4 mode to read both signal edges of signal A and B... It is possible to do this setting? Thanks in advance Roberto
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]
Fwd: [VOTE] Apache NuttX 12.2.0 RC0 release
Hi Alan I hope that these info can are complete: Configuration: nucleo-144:f746-pysim Configuration for pysimCoder including network (DHCP) support ls -l: -rwxr-xr-x 1 bucher bucher 1744196 Jun 22 11:06 nuttx -rwxr-xr-x 1 bucher bucher 134400 Jun 22 11:06 nuttx.bin -rw-r--r-- 1 bucher bucher 2406500 Jun 30 16:11 nuttx-export-12.2.0.tar.gz NuttX shell: 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 main 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 Bye Roberto On 7/1/23 14:16, Alan C. Assis wrote: Hi Roberto, Could you please supply more information? toolchain version used, size of final binary, etc This way to can have a historic of all versions. BR, Alan On 7/1/23, Roberto Bucher wrote: +1 Tested on nucleo-144 (STM32F746ZG) + pysimCoder Roberto On 6/30/23 10:47, Alin Jerpelea wrote: Hello all, Apache NuttX 12.2.0 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.0-RC0 Hash for the release nuttx tag: 26f5e973f68a7bb4ee66915fce2c723641d5e045 Hash for the release nuttx-apps tag: 86efbcbee77bc0a29af07807080f4804a37f46a3 [1] https://dist.apache.org/repos/dist/dev/nuttx/12.2.0-RC0/ [2] https://raw.githubusercontent.com/apache/nuttx/nuttx-12.2.0-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: [VOTE] Apache NuttX 12.2.0 RC0 release
+1 Tested on nucleo-144 (STM32F746ZG) + pysimCoder Roberto On 6/30/23 10:47, Alin Jerpelea wrote: Hello all, Apache NuttX 12.2.0 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.0-RC0 Hash for the release nuttx tag: 26f5e973f68a7bb4ee66915fce2c723641d5e045 Hash for the release nuttx-apps tag: 86efbcbee77bc0a29af07807080f4804a37f46a3 [1] https://dist.apache.org/repos/dist/dev/nuttx/12.2.0-RC0/ [2] https://raw.githubusercontent.com/apache/nuttx/nuttx-12.2.0-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
NUttX and TI boards
Hi We are working with a*Launchpad TMS320F28379D *board and we are looking if somebody already worked with NuttX on this board. Thanks in advance Roberto
Re: V NuttX International Workshop
Hi Alan my idea is to present my contributions to microros-NuttX, but after the retirement from my professor position at SUPSI (31.08.2023!), it is quite difficult for me to be in Brazil. An online presentation should be possible? Best regards Roberto On 4/16/23 16:35, Alan C. Assis wrote: On 4/16/23, Nathan Hartman wrote: ... Perhaps the simplest low-tech way is to video tape the presentations and post the videos online afterwards. In fact, not only will this make it possible to see the event for people who can't attend, but it will also become possible to refer back to the presentations for people who do attend, and can be added to our online video repertoire for people who discover NuttX in the future. So, if it is possible , I hope the presentations can be video taped and put online. Yes, his is an option, but if we can do live stream to let people to participate as in previous Online Workshop will be awesome! :-) Tiago told me that Unicamp has some equipment to do that, let see if we could use it. BR, Alan
Error by make export by extensa ESP32
Hi I've finally reached to generate code for ESP32 using pysimCoder. My board is a OLIMEX ESP32-POE board, Starting from the esp32-devkitc:wifinsh configuration we set CONFIG_ARCH_CHIP_ESP32WROOM32=y and the generation of the nuttx code is ok. The problems start when I do a "make export": The exported file doesn't contain the libraries provided under nuttx/arch/xtensa/src/esp32/esp-wireless-drivers-3rdparty/libs/esp32/ and the Make.defs script doesn't integrate these libraries in the link. After setting these libs manually and after defining HEAD_OBJ = esp32_start.o esp32_wdt.o in Make.defs, the generation of the binary file seems to be ok (not tested yet on the processor) Ciao Roberto
Still problems with ESP32 compilation using nuttx-export
Hi I still have problems by compiling a NuttX project using the exported libraries and the Makefile usually used to compile other targets under pysimCoder. I've recompiled the .ld files as ld.tmp and the I changed the name to .ld again in order to find them in my Makefile... I don't know if it is correct... %.ld.tmp: %.ld $(CPP) -isystem $(NUTTX_EXPORT)/include -D__NuttX__ -DNDEBUG -D__KERNEL__ \ -I$(NUTTX_EXPORT)/arch/chip \ -I $(NUTTX_EXPORT)/arch/os/sched -o $@ $< mv .ld.tmp .ld After this I launch my makefile again and I obtain: xtensa-esp32-elf-ld -nostdlib --gc-sections --cref -Map=/home/bucher/sviluppo/NUTTX/nuttx/nuttx.map -L /home/bucher/CACSD/pysimCoder/CodeGen/nuttx/nuttx-export/libs --entry=__start -o ../test.elf \ -r -e main -T /home/bucher/CACSD/pysimCoder/CodeGen/nuttx/nuttx-export/scripts/gnu-elf.ld \ -Map test.elf.map \ nuttx_main.o test.o /home/bucher/CACSD/pysimCoder/CodeGen/nuttx/lib/libpyblk.a --start-group /home/bucher/sviluppo/GITHUB/xtensa-esp32-elf/bin/../lib/gcc/xtensa-esp32-elf/11.2.0/libgcc.a --end-group ### Created ELF loadable file: test.elf the elf file seems to be correctly generated, but after this I have a lot of errors: xtensa-esp32-elf-ld: warning: cannot find entry symbol __start; not setting start address and a lot of undefined' symbols like for example: xtensa-esp32-elf-ld -nostdlib --gc-sections --cref -Map=/home/bucher/sviluppo/NUTTX/nuttx/nuttx.map -L /home/bucher/CACSD/pysimCoder/CodeGen/nuttx/nuttx-export/libs --entry=__start -T /home/bucher/CACSD/pysimCoder/CodeGen/nuttx/nuttx-export/scripts/esp32_rom.ld -T /home/bucher/CACSD/pysimCoder/CodeGen/nuttx/nuttx-export/scripts/flat_memory.ld -T /home/bucher/CACSD/pysimCoder/CodeGen/nuttx/nuttx-export/scripts/legacy_sections.ld \ -o ../test \ nuttx_main.o test.o nuttx_main-builtintab.o /home/bucher/CACSD/pysimCoder/CodeGen/nuttx/lib/libpyblk.a --start-group -lsched -ldrivers -lboards -lc -lmm -larch -lm -lxx -lapps -lnet -lfs -lbinfmt -lwireless -lboard -lboard /home/bucher/sviluppo/GITHUB/xtensa-esp32-elf/bin/../lib/gcc/xtensa-esp32-elf/11.2.0/libgcc.a --end-group xtensa-esp32-elf-ld: warning: cannot find entry symbol __start; not setting start address xtensa-esp32-elf-ld: /home/bucher/CACSD/pysimCoder/CodeGen/nuttx/nuttx-export/libs/libarch.a(esp32_wifi_adapter.o):(.literal.esp_evt_work_cb+0x14): undefined reference to `esp_wifi_set_ps' ... Any idea? Does exist a a makefile for ESP32 that uses the "nuttx-export" files? Thanks in advance Roberto
Re: Problem with exported lib
Thanks Gustavo sorry for late replay.. Why are not all these flags and the correct ld.tmp files exported when we generate the nuttx-export file? It will be corrected in the future or do we modify our files that automatically generate nuttx binaries to this? Thanks again Roberto On 1/5/23 14:52, Gustavo Henrique Nihei wrote: Hi Roberto, Since https://github.com/apache/nuttx/pull/7208 the NuttX build system preprocesses every linker script file of a given configuration. We've recently updated the makefiles and linker scripts of every supported chip from the ESP32 family to benefit from this. So you may need to update your out-of-tree build system to also preprocess each linker script file (e.g. using "-E" argument from GCC) and pass the output files to xtensa-esp32-elf-ld. Notice that you'll need to provide all the include paths to GCC so that it is able to find the headers required at the processing phase. As a reference, if you build "esp32-devkitc:nsh" with "make V=1", you'll notice that for each ".ld" file the build system will generate a new one suffixed with ".ld.tmp", which are the ones to be passed to the Linker: *CPP: /home/nihei/Projects/NuttX/nuttx/boards/xtensa/esp32/esp32-devkitc/../common/scripts/esp32_rom.ld-> /home/nihei/Projects/NuttX/nuttx/boards/xtensa/esp32/esp32-devkitc/../common/scripts/esp32_rom.ld.tmp xtensa-esp32-elf-gcc -E -P -x c -isystem /home/nihei/Projects/NuttX/nuttx/include -D__NuttX__ -DNDEBUG -D__KERNEL__ -I /home/nihei/Projects/NuttX/nuttx/arch/xtensa/src/chip -I /home/nihei/Projects/NuttX/nuttx/arch/xtensa/src/common -I /home/nihei/Projects/NuttX/nuttx/arch/xtensa/src/lx6 -I /home/nihei/Projects/NuttX/nuttx/sched /home/nihei/Projects/NuttX/nuttx/boards/xtensa/esp32/esp32-devkitc/../common/scripts/esp32_rom.ld -o /home/nihei/Projects/NuttX/nuttx/boards/xtensa/esp32/esp32-devkitc/../common/scripts/esp32_rom.ld.tmp* *CPP: /home/nihei/Projects/NuttX/nuttx/boards/xtensa/esp32/esp32-devkitc/../common/scripts/flat_memory.ld-> /home/nihei/Projects/NuttX/nuttx/boards/xtensa/esp32/esp32-devkitc/../common/scripts/flat_memory.ld.tmpxtensa-esp32-elf-gcc -E -P -x c -isystem /home/nihei/Projects/NuttX/nuttx/include -D__NuttX__ -DNDEBUG -D__KERNEL__ -I /home/nihei/Projects/NuttX/nuttx/arch/xtensa/src/chip -I /home/nihei/Projects/NuttX/nuttx/arch/xtensa/src/common -I /home/nihei/Projects/NuttX/nuttx/arch/xtensa/src/lx6 -I /home/nihei/Projects/NuttX/nuttx/sched /home/nihei/Projects/NuttX/nuttx/boards/xtensa/esp32/esp32-devkitc/../common/scripts/flat_memory.ld -o /home/nihei/Projects/NuttX/nuttx/boards/xtensa/esp32/esp32-devkitc/../common/scripts/flat_memory.ld.tmp* *CPP: /home/nihei/Projects/NuttX/nuttx/boards/xtensa/esp32/esp32-devkitc/../common/scripts/legacy_sections.ld-> /home/nihei/Projects/NuttX/nuttx/boards/xtensa/esp32/esp32-devkitc/../common/scripts/legacy_sections.ld.tmp xtensa-esp32-elf-gcc -E -P -x c -isystem /home/nihei/Projects/NuttX/nuttx/include -D__NuttX__ -DNDEBUG -D__KERNEL__ -I /home/nihei/Projects/NuttX/nuttx/arch/xtensa/src/chip -I /home/nihei/Projects/NuttX/nuttx/arch/xtensa/src/common -I /home/nihei/Projects/NuttX/nuttx/arch/xtensa/src/lx6 -I /home/nihei/Projects/NuttX/nuttx/sched /home/nihei/Projects/NuttX/nuttx/boards/xtensa/esp32/esp32-devkitc/../common/scripts/legacy_sections.ld -o /home/nihei/Projects/NuttX/nuttx/boards/xtensa/esp32/esp32-devkitc/../common/scripts/legacy_sections.ld.tmp* Best regards, Gustavo. On Thu, Jan 5, 2023 at 4:31 AM Roberto Bucher wrote: Hi I have a new configuration for an Olimex-ESP32-PoE board. I can compile and build the nuttx flash without problems. I did a make export and putted the generated nuttx-export folder into another project (pysimCoder). The Makefile of the project, which correctly works with my STM32 boards, fails the compilation of the image for esp32 with this strange message: xtensa-esp32-elf-ld -nostdlib --gc-sections --cref -Map=/home/bucher/sviluppo/NUTTX/nuttx/nuttx.map -L /home/bucher/CACSD/pysimCoder/CodeGen/nuttx/nuttx-export/libs --entry=__start -T /home/bucher/CACSD/pysimCoder/CodeGen/nuttx/nuttx-export/scripts/esp32_rom.ld -T /home/bucher/CACSD/pysimCoder/CodeGen/nuttx/nuttx-export/scripts/flat_memory.ld -T /home/bucher/CACSD/pysimCoder/CodeGen/nuttx/nuttx-export/scripts/legacy_sections.ld \ -o ../test \ nuttx_main.o test.o nuttx_main-builtintab.o /home/bucher/CACSD/pysimCoder/CodeGen/nuttx/lib/libpyblk.a --start-group -lsched -ldrivers -lboards -lc -lmm -larch -lxx -lapps -lnet -lfs -lbinfmt -lwireless -lboard -lboard /home/bucher/sviluppo/GITHUB/xtensa-esp32-elf/bin/../lib/gcc/xtensa-esp32-elf/11.2.0/libgcc.a --end-group *xtensa-esp32-elf-ld:/home/bucher/CACSD/pysimCoder/CodeGen/nuttx/nuttx-export/scripts/flat_memory.ld:32: ignoring invalid character `#' in expression** **xtensa-esp32-elf-ld:/home/bucher/CACSD/pysimCoder/CodeGen/nuttx/nuttx-export/scripts/flat_memory.ld:32
Problem with exported lib
Hi I have a new configuration for an Olimex-ESP32-PoE board. I can compile and build the nuttx flash without problems. I did a make export and putted the generated nuttx-export folder into another project (pysimCoder). The Makefile of the project, which correctly works with my STM32 boards, fails the compilation of the image for esp32 with this strange message: xtensa-esp32-elf-ld -nostdlib --gc-sections --cref -Map=/home/bucher/sviluppo/NUTTX/nuttx/nuttx.map -L /home/bucher/CACSD/pysimCoder/CodeGen/nuttx/nuttx-export/libs --entry=__start -T /home/bucher/CACSD/pysimCoder/CodeGen/nuttx/nuttx-export/scripts/esp32_rom.ld -T /home/bucher/CACSD/pysimCoder/CodeGen/nuttx/nuttx-export/scripts/flat_memory.ld -T /home/bucher/CACSD/pysimCoder/CodeGen/nuttx/nuttx-export/scripts/legacy_sections.ld \ -o ../test \ nuttx_main.o test.o nuttx_main-builtintab.o /home/bucher/CACSD/pysimCoder/CodeGen/nuttx/lib/libpyblk.a --start-group -lsched -ldrivers -lboards -lc -lmm -larch -lxx -lapps -lnet -lfs -lbinfmt -lwireless -lboard -lboard /home/bucher/sviluppo/GITHUB/xtensa-esp32-elf/bin/../lib/gcc/xtensa-esp32-elf/11.2.0/libgcc.a --end-group *xtensa-esp32-elf-ld:/home/bucher/CACSD/pysimCoder/CodeGen/nuttx/nuttx-export/scripts/flat_memory.ld:32: ignoring invalid character `#' in expression** **xtensa-esp32-elf-ld:/home/bucher/CACSD/pysimCoder/CodeGen/nuttx/nuttx-export/scripts/flat_memory.ld:32: syntax error** **make: *** [Makefile:133: ../test] Error 1** * The line 32 of the script "flat_memory.ld" contains simply the line #include Hints are welcomed! Thanks in advance Roberto
ROS and microROS finally working!
Hi all I finally reached to have a system with ROS2 and microROS on Nuttx which seems to work correctly! The main problems were: * Service are not working under galactic, but this seems to be a general problem because the freertos provided code does't work to! NuttX and Freertos are both working under Humble * Nobody seems to handle PR for microROS. I sent 2 PR for the rcutils github but we no reaction! This is quite frustrating. I have a node integrated in pysimCoder that allows to exchange data between the NuttX embedded system and the microROS agent in a PC. It is possible to subscribe and publish up to 4 float64 data between the nodes in ROS2 and the node in microROS. Code i s available (not published yet). I'd like to have contacts with people using ROS2 and microROS with NuttX (there are some presentations at the Workshop!) to exchange info and experience. Best regards Roberto
Re: Intertask communication in NuttX
Thanks! Good idea! Roberto On 12/17/22 10:50, Mark Stevens wrote: Options I would consider would be Message queues Pipes For the project I am involved in we use both of these but mainly use message queues. Message queues should only be used for small messages, I think the limit is about 22 bytes. I get around this by creating the large message and passing the pointer to the message through the message queue interface. Regards, Mark __ mark.stev...@wildernesslabs.co On 17 Dec 2022, at 06:52, Roberto Bucher wrote: Hi after successfully reached to recompile the microROS environment, I'd like to build an intertask communication between a microROS node and a pysimCoder generated code. I think that I can't use a shared memory with my embedded system (nucleo-144), because I can't see the CONFIG_BUILD_KERNEL=y in my .config file. Are there other IPC mechanism that I can use to communicate between the 2 tasks? Thanks in advance Roberto
Intertask communication in NuttX
Hi after successfully reached to recompile the microROS environment, I'd like to build an intertask communication between a microROS node and a pysimCoder generated code. I think that I can't use a shared memory with my embedded system (nucleo-144), because I can't see the CONFIG_BUILD_KERNEL=y in my .config file. Are there other IPC mechanism that I can use to communicate between the 2 tasks? Thanks in advance Roberto
Re: NUTTX definition
Thanks: it works! Ciao Roberto On 12/5/22 16:36, Alan C. Assis wrote: Hi Roberto, You can use __NuttX__ BR, Alan On 12/5/22, Roberto Bucher wrote: Hi Which is the "#ifdef" that I can use to check if I've been compiling for NuttX (like for example #ifdef _WIN32...)? Thanks in advance Roberto
NUTTX definition
Hi Which is the "#ifdef" that I can use to check if I've been compiling for NuttX (like for example #ifdef _WIN32...)? Thanks in advance Roberto
microROS
Hi thanks for the help in the last days! microROS on NuttX works again after a couple of days of debugging, tests and changes. I'll reached to communicate from ROS2+agent with a publisher on the nucleo-144 board via LAN and UDP, under galactic. There are some few modifications compared to the original files: * In the file "micro_ros_src/src/rcutils/src/filesystem.c" there is a redefinition of "DIR" which conflicts with the definition in NuttX dirent.h * The colcon.meta file has been completely modified * The microros_main.c has some little modifications and now it is more similar to the files provided by freertos. I'll try in the next days to better formalize the files, to contact the developpers of microros to get the modifications and when the conflict on "DIR" is corrected I'll prepare a PR for the micros/NuttX page Roberto
Re: Debugging a specific application
Danke Sebastien The application (microros) is configured and compiled by the nuttx generation. But if the routine is in the shell, how can I start it from the debugger? Thanks in advance Roberto On 11/30/22 22:17, Sebastien Lorquet wrote: Hi, If your OS is built in monolithic mode (no protected mode) then applications are just routines, so you can put a breakpoint in any app routine and let it run until there. To replace nsh by your app, do make menuconfig, menu RTOS features, menu Tasks and scheduling, text config "Application entry point". But it is not necessary to replace the default app, you can launch it with nsh and still hit a breakpoint in your launched app. Sebastien On 11/30/22 06:40, Roberto Bucher wrote: Hi I'm working on my nucleo-144 board, trying to get a microROS working again under NuttX. Thanks to a unique change in a microROS file, I've reached to recompile all the files again and I can obtain the microros application as described here: https://github.com/micro-ROS/micro_ros_nuttx_app apps/microros The application doesn't correctly work yet, and I'm looking for the problem. I'd like to debug the microros application, but the debugger shows (as expected) the nsh task. It is possible to start the specific "microros" generated program or I have to set it as entry point? Otherwise, how can I attach this task to the debugger? I'm able to debug the nsh application with the methods described on the NuttX documentation about debugger. Thanks in advance Roberto
Debugging a specific application
Hi I'm working on my nucleo-144 board, trying to get a microROS working again under NuttX. Thanks to a unique change in a microROS file, I've reached to recompile all the files again and I can obtain the microros application as described here: https://github.com/micro-ROS/micro_ros_nuttx_app apps/microros The application doesn't correctly work yet, and I'm looking for the problem. I'd like to debug the microros application, but the debugger shows (as expected) the nsh task. It is possible to start the specific "microros" generated program or I have to set it as entry point? Otherwise, how can I attach this task to the debugger? I'm able to debug the nsh application with the methods described on the NuttX documentation about debugger. Thanks in advance Roberto
Re: ROS2 and microROS
Thanks Alan I'm doing some tests with Freertos to see the mechanism behind microROS, but my idea is to get the old example described here https://github.com/micro-ROS/micro_ros_nuttx_app and try to rewrite the test to work again with humble and galactic + NuttX-11 I'll give you feedback as soon as I have some results. My dream is to have a node that I can link with ROS2 from a side and to pysimCoder on the other side... Ciao Roberto On 11/20/22 11:47, Alan C. Assis wrote: Hi Roberto, Nice to see your interest in using NuttX with ROS2. I think the guy that was working on NuttX and ROS (the first MicroROS was based on NuttX) went out to work on other things. We need to find someone to help to fix it. If you are interested to get it working again I offer to help you to get things fixed, but I never worked with ROS, ROS2, MicroROS, but it is on my never-ending TODO list :-D BR, Alan On 11/18/22, Roberto Bucher wrote: Hi we are starting a project in out University based on ROS2 and microROS, but I can't find recent documentation about it. Some project doesn't work with Nuttx-11 and other doesn't have firmware for NuttX anymore... https://github.com/micro-ROS/micro_ros_nuttx_app -> this description doesn't work with NuttX 11 and this one ( https://micro.ros.org/docs/tutorials/core/first_application_rtos/nuttx/) fails at this command: ros2 run micro_ros_setup create_firmware_ws.sh nuttx olimex-stm32-e407 because no cards are defined for NuttX! Any idea? Thanks in advance Roberto
ROS2 and microROS
Hi we are starting a project in out University based on ROS2 and microROS, but I can't find recent documentation about it. Some project doesn't work with Nuttx-11 and other doesn't have firmware for NuttX anymore... https://github.com/micro-ROS/micro_ros_nuttx_app -> this description doesn't work with NuttX 11 and this one ( https://micro.ros.org/docs/tutorials/core/first_application_rtos/nuttx/) fails at this command: ros2 run micro_ros_setup create_firmware_ws.sh nuttx olimex-stm32-e407 because no cards are defined for NuttX! Any idea? Thanks in advance Roberto
Re: Conflicts with network and PWM on stm32f7 nucleo-144
Today I test the possibility to exchange PA07 and PB05 as described here, be removing SB121 and closing SB122 solder bridges on the back of the nucleo board. https://os.mbed.com/teams/ST/wiki/Nucleo-144pins-ethernet-spi-conflict This an HW patch, but quite simple to be done. Roberto On 8/23/22 04:27, Nathan Hartman wrote: 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 to CN7 pin14 by default, if JP6 is ON, it is also connected to both Ethernet PHY as RMII_DV and CN9 pin15. In this case only one function of Ethernet or D11 could be used. I wonder if a compile-time check for this conflict could be added somewhere to prevent this kind of impossible pinout assignment from being done again in the future? Cheers Nathan
Re: Conflicts with network and PWM on stm32f7 nucleo-144
Exactly! The problem is there. Setting the PWM channel to #define GPIO_TIM3_CH2OUT GPIO_TIM3_CH2OUT_2 the problem disappears. I need this PA07 to connect the Arduino Motor Shield (Motor B)... I check the JP6, perhaps it solves the conflict. Thanks and best regards Roberto On 8/22/22 15:14, 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 to CN7 pin14 by default, if JP6 is ON, it is also connected to both Ethernet PHY as RMII_DV and CN9 pin15. In this case only one function of Ethernet or D11 could be used. pon., 22 sie 2022 o 14:22 Roberto Bucher napisał(a): Hi I've configured a NUCLEO-F746ZG board with different devices: * PWM (TIM3 3xOutput) * QE * ADC * GPIO CONFIG_PWM=y CONFIG_STM32F7_PWM_MULTICHAN=y CONFIG_STM32F7_TIM3_PWM=y CONFIG_STM32F7_TIM1=y CONFIG_STM32F7_TIM1_QE=y CONFIG_STM32F7_TIM2=y CONFIG_STM32F7_TIM2_ADC=y CONFIG_STM32F7_TIM3=y CONFIG_STM32F7_TIM3_CH1OUT=y CONFIG_STM32F7_TIM3_CH2OUT=y CONFIG_STM32F7_TIM3_CHANNEL1=y CONFIG_STM32F7_TIM3_CHANNEL2=y CONFIG_STM32F7_TIM3_PWM=y but I have problems when I have PWM and UDP working together in a pysimCoder block diagram. Starting the application, the socket to the UDP is opened , but I don't receive signals to the UDP server. In addition, I can't open the RCP channel to the SIlicon Heaven application correctly. The problem disappears when I remove the PWM block in my diagram... I've increased all the stacks, but without success. Any Idea? Roberto
Re: Conflicts with network and PWM on stm32f7 nucleo-144
This is my configuration: #define GPIO_TIM3_CH1OUT GPIO_TIM3_CH1OUT_2 #define GPIO_TIM3_CH2OUT GPIO_TIM3_CH2OUT_1 #define GPIO_TIM3_CH3OUT GPIO_TIM3_CH3OUT_1 #define GPIO_TIM3_CH4OUT GPIO_TIM3_CH4OUT_1 PA07 for PWM channel 2 is required by the Arduino Motor Shield, used to control an external motor. I can try to set another channel, and see if the problem disappears. Thanks Roberto On 8/22/22 15:14, 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 to CN7 pin14 by default, if JP6 is ON, it is also connected to both Ethernet PHY as RMII_DV and CN9 pin15. In this case only one function of Ethernet or D11 could be used. pon., 22 sie 2022 o 14:22 Roberto Bucher napisał(a): Hi I've configured a NUCLEO-F746ZG board with different devices: * PWM (TIM3 3xOutput) * QE * ADC * GPIO CONFIG_PWM=y CONFIG_STM32F7_PWM_MULTICHAN=y CONFIG_STM32F7_TIM3_PWM=y CONFIG_STM32F7_TIM1=y CONFIG_STM32F7_TIM1_QE=y CONFIG_STM32F7_TIM2=y CONFIG_STM32F7_TIM2_ADC=y CONFIG_STM32F7_TIM3=y CONFIG_STM32F7_TIM3_CH1OUT=y CONFIG_STM32F7_TIM3_CH2OUT=y CONFIG_STM32F7_TIM3_CHANNEL1=y CONFIG_STM32F7_TIM3_CHANNEL2=y CONFIG_STM32F7_TIM3_PWM=y but I have problems when I have PWM and UDP working together in a pysimCoder block diagram. Starting the application, the socket to the UDP is opened , but I don't receive signals to the UDP server. In addition, I can't open the RCP channel to the SIlicon Heaven application correctly. The problem disappears when I remove the PWM block in my diagram... I've increased all the stacks, but without success. Any Idea? Roberto
Conflicts with network and PWM on stm32f7 nucleo-144
Hi I've configured a NUCLEO-F746ZG board with different devices: * PWM (TIM3 3xOutput) * QE * ADC * GPIO CONFIG_PWM=y CONFIG_STM32F7_PWM_MULTICHAN=y CONFIG_STM32F7_TIM3_PWM=y CONFIG_STM32F7_TIM1=y CONFIG_STM32F7_TIM1_QE=y CONFIG_STM32F7_TIM2=y CONFIG_STM32F7_TIM2_ADC=y CONFIG_STM32F7_TIM3=y CONFIG_STM32F7_TIM3_CH1OUT=y CONFIG_STM32F7_TIM3_CH2OUT=y CONFIG_STM32F7_TIM3_CHANNEL1=y CONFIG_STM32F7_TIM3_CHANNEL2=y CONFIG_STM32F7_TIM3_PWM=y but I have problems when I have PWM and UDP working together in a pysimCoder block diagram. Starting the application, the socket to the UDP is opened , but I don't receive signals to the UDP server. In addition, I can't open the RCP channel to the SIlicon Heaven application correctly. The problem disappears when I remove the PWM block in my diagram... I've increased all the stacks, but without success. Any Idea? Roberto
Re: Assertion failed using the nucleo-H743ZI2 board
Thanks Sebastien It seems that this new stack size solves the problems. No more crashes in the first new tests. Best regards Roberto On 7/12/22 22:13, Sebastien Lorquet wrote: Hi, I'm working with the exact same board and struggled for several days with a similar problem. Breakpoints did not help since the issue was fugitive and not always crashing at the same place. There also were debug/release variations. It turned out to be a stack issue. The default stack size for new stacks is 2048 and all problems went away by defining a 4k default stack size. You may not have the same issue, but it's worth trying that point. Sebastien On 7/12/22 21:34, Roberto Bucher wrote: Hi I' working on a STM32 NUCLEO-H743ZI2 board, and I have sporadic errors in the shell when I launch some utilities like "ifconfig" or "renew" (but it seems not to be related to the network). Sometimes the command runs without problems, sometimes it gives an Assertion failure and I have to switch off and on the board to restart the shall. It seems to be a problem related to the shell application. Does somebody have similar problems? How can I try to find out the bugs related to this error? (breakpoints where?) Thanks in advance Roberto
Assertion failed using the nucleo-H743ZI2 board
Hi I' working on a STM32 NUCLEO-H743ZI2 board, and I have sporadic errors in the shell when I launch some utilities like "ifconfig" or "renew" (but it seems not to be related to the network). Sometimes the command runs without problems, sometimes it gives an Assertion failure and I have to switch off and on the board to restart the shall. It seems to be a problem related to the shell application. Does somebody have similar problems? How can I try to find out the bugs related to this error? (breakpoints where?) Thanks in advance Roberto
Re: nucleo-stm32h7zi vs nucleo-stm32h7zi2 boards
Thanks Alan I'll try to move the different devices to the new architecture. I'll already tried to port the stm32_pwm.c under the zi2 board and it works without problems. In the next weeks I'll try to port other devices (ADC, Encoders etc.). It seems the SocketCan is already implemented. One additional problems has raised when I modified the "System timer tick period" I can't see relations between this configuration and the network... Network is ok with values of this timer set to 1 and 1000, but when I modify it to 100, the network doesn't work anymore... BR Roberto On 6/29/22 14:26, Alan Carvalho de Assis wrote: Hi Roberto, I found both boards listed on Digikey: NUCLEO-H743ZI: https://www.digikey.com/en/products/detail/stmicroelectronics/NUCLEO-H743ZI/7809236 NUCLEO-H743ZI2: https://www.digikey.com/en/products/detail/stmicroelectronics/NUCLEO-H743ZI2/10130892 The ZI board was replaced with ZI2 by ST according with a note here: https://www.st.com/content/ccc/resource/technical/document/data_brief/group1/8c/c9/8a/9b/3e/f0/45/bb/DM00357737/files/DM00357737.pdf/jcr:content/translations/en.DM00357737.pdf Also according with this note ZI uses ST-LINK/V2 and ZI2 uses ST-LINK/V3, I didn't look the schematics to do further comparison. If you do the schematic comparison and realize they are identical, then it should be nice to copy the code from ZI board to ZI2 because ZI was discontinued and users normally will by ZI2. The board ZI has reference code MB1137 and ZI2 has MB1364. BR, Alan On 6/29/22, Roberto Bucher wrote: Hi What are the main differences between the nucleo-stm32h743zi and the nucleo-stm32h743zi2 boards? I have a stm32743zi2 board but the available files under "boards" for nucleo-stm32h743zi2 are limited compared to the files available for the nucleo-stm32h743zi version. I need different devices (PWM, ADC, encoder, CAN) and I don't know exactly if I have to new implement them for the ZI2 version or if it is possible to work using the ZI version. I tried the netnsh configuration of the ZI on my ZI2 board and it works... Thanks in advance for any hints Roberto
nucleo-stm32h7zi vs nucleo-stm32h7zi2 boards
Hi What are the main differences between the nucleo-stm32h743zi and the nucleo-stm32h743zi2 boards? I have a stm32743zi2 board but the available files under "boards" for nucleo-stm32h743zi2 are limited compared to the files available for the nucleo-stm32h743zi version. I need different devices (PWM, ADC, encoder, CAN) and I don't know exactly if I have to new implement them for the ZI2 version or if it is possible to work using the ZI version. I tried the netnsh configuration of the ZI on my ZI2 board and it works... Thanks in advance for any hints Roberto
Complementary PWM channels on stm32f7
Hi Did somebody already an implementation of the complementary PWM channels on stm32f7 systems? Thanks in advance Roberto
Question about versions
Hi I have a local version of nuttx, and an access to the incubator nuttx repository through the git remote with this configuration: bucher@debian:~/sviluppo/NUTTX/nuttx$ git remote -v origin g...@github.com:robertobucher/incubator-nuttx.git (fetch) origin g...@github.com:robertobucher/incubator-nuttx.git (push) upstream https://github.com/apache/incubator-nuttx.git (fetch) upstream https://github.com/apache/incubator-nuttx.git (push) I did a git pull upstream master and it seems that my local version is updated When I build an image, the version that I have in the nsh is 10.1.0! I cloned another nuttx folder directly from the incubator, I built an image, but in this new build the version is NuttX-10.3.0-RC2 What is wrong in my local version? Thanks in advance Roberto
Still problems with network on the ARM - STM32F7 - Nucleo-144 board
Hi I have still problems with my nucleo-144 board (stm32F746ZG) and the network. I've tried both static and dynamic IP. The eth0 doesn't receive an IP from the DHCP server (still 0.0.0.0). When I give nsh> ifup etho I get the message ifup eth0...OK but the card is still down nsh> ifconfig eth0 Link encap:Ethernet HWaddr 5e:11:f1:23:d9:ce at DOWN inet addr:0.0.0.0 DRaddr:192.168.178.1 Mask:255.255.255.0 when I launch: nsh> renew eth0 I get ERROR: dhcpc_request() failed What is wrong in my configuration? (attached# # This file is autogenerated: PLEASE DO NOT EDIT IT. # # You can use "make menuconfig" to make any modifications to the installed .config file. # You can then do "make savedefconfig" to generate a new defconfig file that includes your # modifications. # # CONFIG_ARCH_LEDS is not set # CONFIG_DISABLE_OS_API is not set # CONFIG_STM32F7_DTCMEXCLUDE is not set CONFIG_ADC=y CONFIG_ADC_FIFOSIZE=16 CONFIG_ANALOG=y CONFIG_ARCH="arm" CONFIG_ARCH_BOARD="nucleo-144" CONFIG_ARCH_BOARD_NUCLEO_144=y CONFIG_ARCH_BUTTONS=y CONFIG_ARCH_CHIP="stm32f7" CONFIG_ARCH_CHIP_STM32F746ZG=y CONFIG_ARCH_CHIP_STM32F7=y CONFIG_ARCH_STACKDUMP=y CONFIG_ARMV7M_DCACHE=y CONFIG_ARMV7M_DCACHE_WRITETHROUGH=y CONFIG_ARMV7M_DTCM=y CONFIG_ARMV7M_ICACHE=y CONFIG_BOARDCTL_USBDEVCTRL=y CONFIG_BOARD_LATE_INITIALIZE=y CONFIG_BOARD_LOOPSPERMSEC=43103 CONFIG_BUILTIN=y CONFIG_CAN_USE_RTR=y CONFIG_CDCACM=y CONFIG_CDCACM_CONSOLE=y CONFIG_DEBUG_FEATURES=y CONFIG_DEBUG_NET=y CONFIG_DEV_GPIO=y CONFIG_DRVR_READAHEAD=y CONFIG_ETH0_PHY_LAN8742A=y CONFIG_EXAMPLES_HELLO=y CONFIG_FS_PROCFS=y CONFIG_FS_PROCFS_MAX_TASKS=16 CONFIG_FS_PROCFS_REGISTER=y CONFIG_FS_TMPFS=y CONFIG_HAVE_CXX=y CONFIG_HAVE_CXXINITIALIZE=y CONFIG_IDLETHREAD_STACKSIZE=2048 CONFIG_INIT_ENTRYPOINT="nsh_main" CONFIG_IOEXPANDER=y CONFIG_IOEXPANDER_MULTIPIN=y CONFIG_LIBC_FLOATINGPOINT=y CONFIG_LIBM=y CONFIG_MM_REGIONS=2 CONFIG_MODULE=y CONFIG_MQ_MAXMSGSIZE=256 CONFIG_NET=y CONFIG_NETDB_DNSCLIENT=y CONFIG_NETDEV_LATEINIT=y CONFIG_NETINIT_DHCPC=y CONFIG_NETINIT_DRIPADDR=0xc0a8b201 CONFIG_NETUTILS_DISCOVER=y CONFIG_NETUTILS_TELNETD=y CONFIG_NETUTILS_WEBCLIENT=y CONFIG_NET_ARP_IPIN=y CONFIG_NET_ARP_SEND=y CONFIG_NET_BROADCAST=y CONFIG_NET_ETH_PKTSIZE=1500 CONFIG_NET_ICMP=y CONFIG_NET_ICMP_SOCKET=y CONFIG_NET_IGMP=y CONFIG_NET_LOOPBACK=y CONFIG_NET_ROUTE=y CONFIG_NET_STATISTICS=y CONFIG_NET_TCP=y CONFIG_NET_UDP=y CONFIG_NET_UDP_CHECKSUMS=y CONFIG_NSH_ARCHINIT=y CONFIG_NSH_BUILTIN_APPS=y CONFIG_NSH_FILEIOSIZE=512 CONFIG_NSH_LINELEN=64 CONFIG_NSH_READLINE=y CONFIG_NUCLEO_CONSOLE_VIRTUAL=y CONFIG_NUCLEO_SPI2_TEST=y CONFIG_NUCLEO_SPI2_TEST_FREQ=400 CONFIG_NUCLEO_SPI2_TEST_MODE0=y CONFIG_NUCLEO_SPI_TEST=y CONFIG_PIPES=y CONFIG_PREALLOC_TIMERS=4 CONFIG_PRIORITY_INHERITANCE=y CONFIG_PTHREAD_CLEANUP=y CONFIG_PTHREAD_MUTEX_DEFAULT_PRIO_INHERIT=y CONFIG_PTHREAD_MUTEX_TYPES=y CONFIG_PTHREAD_STACK_MIN=1024 CONFIG_PWM=y CONFIG_PWM_MULTICHAN=y CONFIG_PWM_NCHANNELS=4 CONFIG_RAM_SIZE=245760 CONFIG_RAM_START=0x2001 CONFIG_RAW_BINARY=y CONFIG_READLINE_CMD_HISTORY=y CONFIG_READLINE_TABCOMPLETION=y CONFIG_RR_INTERVAL=10 CONFIG_SCHED_HPWORK=y CONFIG_SCHED_LPWORK=y CONFIG_SCHED_WAITPID=y CONFIG_SENSORS=y CONFIG_SENSORS_QENCODER=y CONFIG_SERIAL_TERMIOS=y CONFIG_START_DAY=30 CONFIG_START_MONTH=11 CONFIG_START_YEAR=2015 CONFIG_STM32F7_ADC1=y CONFIG_STM32F7_ADC1_DMA=y CONFIG_STM32F7_ADC1_SAMPLE_FREQUENCY=5000 CONFIG_STM32F7_ADC_NO_STARTUP_CONV=y CONFIG_STM32F7_CAN1=y CONFIG_STM32F7_CAN1_BAUD=50 CONFIG_STM32F7_CAN_TSEG1=5 CONFIG_STM32F7_CAN_TSEG2=6 CONFIG_STM32F7_DMA1=y CONFIG_STM32F7_DMA2=y CONFIG_STM32F7_DMACAPABLE=y CONFIG_STM32F7_ETHMAC=y CONFIG_STM32F7_OTGFS=y CONFIG_STM32F7_PHYADDR=0 CONFIG_STM32F7_PHYSR=31 CONFIG_STM32F7_PHYSR_100FD=0x0018 CONFIG_STM32F7_PHYSR_100HD=0x0008 CONFIG_STM32F7_PHYSR_10FD=0x0014 CONFIG_STM32F7_PHYSR_10HD=0x0004 CONFIG_STM32F7_PHYSR_ALTCONFIG=y CONFIG_STM32F7_PHYSR_ALTMODE=0x001c CONFIG_STM32F7_PWM_MULTICHAN=y CONFIG_STM32F7_SPI2=y CONFIG_STM32F7_SYSCFG_IOCOMPENSATION=y CONFIG_STM32F7_TIM1=y CONFIG_STM32F7_TIM1_ADC=y CONFIG_STM32F7_TIM2=y CONFIG_STM32F7_TIM2_QE=y CONFIG_STM32F7_TIM3=y CONFIG_STM32F7_TIM3_CH1OUT=y CONFIG_STM32F7_TIM3_CH2OUT=y CONFIG_STM32F7_TIM3_CH3OUT=y CONFIG_STM32F7_TIM3_CH4OUT=y CONFIG_STM32F7_TIM3_CHANNEL1=y CONFIG_STM32F7_TIM3_CHANNEL2=y CONFIG_STM32F7_TIM3_CHANNEL3=y CONFIG_STM32F7_TIM3_CHANNEL4=y CONFIG_STM32F7_TIM3_PWM=y CONFIG_SYSTEMTICK_HOOK=y CONFIG_SYSTEM_DHCPC_RENEW=y CONFIG_SYSTEM_NSH=y CONFIG_SYSTEM_PING=y CONFIG_SYSTEM_SPITOOL=y CONFIG_SYSTEM_TIME64=y CONFIG_TASK_NAME_SIZE=0 CONFIG_USBDEV=y CONFIG_USEC_PER_TICK=100 CONFIG_USERLED=y CONFIG_USERLED_LOWER=y # # 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 # # 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 #
Still problems with network on stm32f7 nucleo-144 board
Hi I'v configured the network for my nucleo board and I get the following info on the NuttX nsh: nsh> ifup eth0 ifup eth0...OK nsh> route SEQ TARGET NETMASK ROUTER 1. 0.0.0.0 0.0.0.0 192.168.178.109 nsh> ifconfig eth0 Link encap:Ethernet HWaddr 5e:11:f1:23:d9:ce at DOWN inet addr:192.168.178.178 DRaddr:192.168.178.109 Mask:255.255.0.0 lo Link encap:Local Loopback at RUNNING inet addr:127.0.0.1 DRaddr:127.0.0.1 Mask:255.0.0.0 IPv4 TCP UDP ICMP Received Dropped IPv4 VHL: Frg: Checksum TCP ACK: SYN: RST: Type Sent Rexmit nsh> If I set set the flag "NETDEV_LATEINIT" the eth0 disappears... I can't ping from and to the board nsh> ping -c1 192.168.178.109 PING 192.168.178.109 56 bytes of data No response from 192.168.178.109: icmp_seq=0 time=1000 ms 1 packets transmitted, 0 received, 100% packet loss, time 1000 ms nsh> Any idea? BR Roberto
Simple question about network in Nuttx
Hi 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 a /dev/telnet device but not the eth0... BR Roberto
NuttX Presenrtation
Hi I'm preparing a short presentation of NuttX to be given in my University (SUPSI). Does exist an "official presentation" of NuttX? Thanks in advance Roberto
NuttX timers
Hi
I've tried to modify the base timer from 10ms to 1ms, but in the
execution of the generated RT Thread i get a overrun (of about 5ms...).
I modified for this the "CONFIG_SCHED_TICKLESS" from 1 to 1000.
My board is a the STM32F746:nucleo-144 board. Are there other
possibilities to get a shorter sampling time in my RT thread?
The code for the sampling time is programmed as:
-
while(!end){
/* periodic task */
T = calcdiff(t_current,T0);
NAME(MODEL,_isr)(T);
t_next.tv_sec = t_current.tv_sec + t_isr.tv_sec;
t_next.tv_nsec = t_current.tv_nsec + t_isr.tv_nsec;
tsnorm(_next);
/* Check if Overrun */
clock_gettime(CLOCK_MONOTONIC,_current);
if (t_current.tv_sec > t_next.tv_sec ||
(t_current.tv_sec == t_next.tv_sec && t_current.tv_nsec >
t_next.tv_nsec)) {
int usec = (t_current.tv_sec - t_next.tv_sec) * 100 +
(t_current.tv_nsec -
t_next.tv_nsec)/1000;
fprintf(stderr, "Base rate overrun by %d us\n", usec);
t_next= t_current;
}
clock_nanosleep(CLOCK_MONOTONIC, TIMER_ABSTIME, _next, NULL);
t_current = t_next;
}
-
Thanks in advance
Roberto
Re: SPI problem
Thanks again Petro!
Your hint was perfect and now the SPI perct works on the nucleo-144 board!
Best regards
Roberto
On 3/8/22 22:31, Petro Karashchenko wrote:
Hello Roberto,
I've created https://github.com/apache/incubator-nuttx/pull/5697 to
fix the problem.
Best regards,
Petro
пн, 7 бер. 2022 р. о 16:54 Roberto Bucher пише:
Sorry! Forgot my previous error!
devtype was 23 and not 0x23!!! My fault
Best regards
Roberto
On 3/7/22 16:48, Roberto Bucher wrote:
Thanks Petro!
This solve one part of the problem: I don't receive any crash now.
There is another thinks tht is not clear to me: the macro
SPIDEV_ID(spitool->devtype, spitool->csn) is defined as
#define SPIDEV_ID(type,index) uint32_t)(type) & 0x) <<
16) | \
((uint32_t)(index) & 0x))
in the file include/nuttx/spi/spi.h.
This should means that calling it with the parameters
spitool->devtype=0x23 and spitool->csn=0 should give 0x23 as
return value and not 0x17...
Best regards
Roberto
On 3/7/22 16:22, Petro Karashchenko wrote:
Hello Roberto,
I think that the problem is in the line's:
"stm32_gpiowrite(g_spigpio[devid], !selected);". Those should be
"stm32_gpiowrite(g_spigpio[SPIDEVID_INDEX(devid)], !selected);".
Please try to see if that helps.
Best regards,
Petro
пн, 7 бер. 2022 р. о 12:46 Roberto Bucher
пише:
I reached to move a little forward by analyzing the SPI on
the nucleo-144 STM32F7 board, and I found out that the
problem is now in the calling of SPI_SELECT in the
nuttx/drivers/spi/spi_transfer.c and the spi_transfer function.
This are the values in the seq structure before launching
the SPI_SELECT command.
nsh> spi bus
BUS EXISTS?
Bus 0: NO
Bus 1: NO
Bus 2: YES
Bus 3: NO
nsh> spi exch -b2 -x4 aabbccdd
Sending: AA BB CC DD
seq -> dev: 0x17, mode: 3, nbits: 8, ntrans: 1, freq:
400
Received: FF FF FF FF
To avoid the dump error I modified the seq->dev from
0x17 to 0x0004...
It seems that the seq->dev value is not correct...
Best regards
Roberto
On 3/6/22 13:47, Roberto Bucher wrote:
Thanks Petro
I've modified the nucleo-144/src/stm32_spi.c file by simply
adding:
struct spi_dev_s *g_spiX;
and by adding
spi_register(g_spiX, X);
in the
where X is the spi device number (in my example spi2)
in the shell the /dev/spi2 is available.
Best regards
Roberto
On 3/6/22 12:49, Petro Karashchenko wrote:
Hello Roberto,
I'm asking this because I examined nucleo-144 board source
code and currently I do not see a "spi_register" call in
board init files. So I assume that you have some modified
code and it is very hard to make any conclusions while not
seeing the code.
Best regards,
Petro
нд, 6 бер. 2022 р. о 13:40 Petro Karashchenko
пише:
Hello Roberto,
It would be good if you can dump assembly that is
generated. What I see is that "intspi_register(FAR
structspi_dev_s *spi, intbus)", so I'm assuming that
R0 should be "spi" and R1 should be "bus", but in your
dump "R0: 0001 R1: 2004e840" those seems to be
inverted (0001 seems to be a "bus" and "2004e840"
seems to be a "spi" pointer). The assembly code will
show light on the dump that you provided. As an
alternative you can provide the defconfig that you use
if you are not using a custom board.
Best regards,
Petro
нд, 6 бер. 2022 р. о 10:54 Roberto Bucher
пише:
When I enable some dubug configs
I get the following error by enter in the serial
shell:
sert: Assertion failed at file:spi/spi_driver.c
line: 358
arm_registerdump: R0: 0001 R1: 2004e840 R2:
40004800 R3: 20010684
arm_registerdump: R4: 2004e7a0 R5: 0002 R6:
2004f370 FP: 20010670
arm_registerdump: R8: SB: SL:
R11:
arm_registerdump: IP: 0003 SP: 2004f370 LR:
08005fad PC: 0800648e
arm_registerdump: xPSR: 6100 PRIMASK:
CONTROL: 0004
arm_registerdump: EXC_RETURN: ffe9
arm_dump_stack: User Stack:
Re: SPI problem
Sorry! Forgot my previous error!
devtype was 23 and not 0x23!!! My fault
Best regards
Roberto
On 3/7/22 16:48, Roberto Bucher wrote:
Thanks Petro!
This solve one part of the problem: I don't receive any crash now.
There is another thinks tht is not clear to me: the macro
SPIDEV_ID(spitool->devtype, spitool->csn) is defined as
#define SPIDEV_ID(type,index) uint32_t)(type) & 0x) << 16) | \
((uint32_t)(index) & 0x))
in the file include/nuttx/spi/spi.h.
This should means that calling it with the parameters
spitool->devtype=0x23 and spitool->csn=0 should give 0x23 as
return value and not 0x17...
Best regards
Roberto
On 3/7/22 16:22, Petro Karashchenko wrote:
Hello Roberto,
I think that the problem is in the line's:
"stm32_gpiowrite(g_spigpio[devid], !selected);". Those should be
"stm32_gpiowrite(g_spigpio[SPIDEVID_INDEX(devid)], !selected);".
Please try to see if that helps.
Best regards,
Petro
пн, 7 бер. 2022 р. о 12:46 Roberto Bucher пише:
I reached to move a little forward by analyzing the SPI on the
nucleo-144 STM32F7 board, and I found out that the problem is now
in the calling of SPI_SELECT in the
nuttx/drivers/spi/spi_transfer.c and the spi_transfer function.
This are the values in the seq structure before launching the
SPI_SELECT command.
nsh> spi bus
BUS EXISTS?
Bus 0: NO
Bus 1: NO
Bus 2: YES
Bus 3: NO
nsh> spi exch -b2 -x4 aabbccdd
Sending: AA BB CC DD
seq -> dev: 0x17, mode: 3, nbits: 8, ntrans: 1, freq: 400
Received: FF FF FF FF
To avoid the dump error I modified the seq->dev from 0x17 to
0x0004...
It seems that the seq->dev value is not correct...
Best regards
Roberto
On 3/6/22 13:47, Roberto Bucher wrote:
Thanks Petro
I've modified the nucleo-144/src/stm32_spi.c file by simply adding:
struct spi_dev_s *g_spiX;
and by adding
spi_register(g_spiX, X);
in the
where X is the spi device number (in my example spi2)
in the shell the /dev/spi2 is available.
Best regards
Roberto
On 3/6/22 12:49, Petro Karashchenko wrote:
Hello Roberto,
I'm asking this because I examined nucleo-144 board source code
and currently I do not see a "spi_register" call in board init
files. So I assume that you have some modified code and it is
very hard to make any conclusions while not seeing the code.
Best regards,
Petro
нд, 6 бер. 2022 р. о 13:40 Petro Karashchenko
пише:
Hello Roberto,
It would be good if you can dump assembly that is
generated. What I see is that "intspi_register(FAR
structspi_dev_s *spi, intbus)", so I'm assuming that R0
should be "spi" and R1 should be "bus", but in your dump
"R0: 0001 R1: 2004e840" those seems to be inverted
(0001 seems to be a "bus" and "2004e840" seems to be a
"spi" pointer). The assembly code will show light on the
dump that you provided. As an alternative you can provide
the defconfig that you use if you are not using a custom board.
Best regards,
Petro
нд, 6 бер. 2022 р. о 10:54 Roberto Bucher
пише:
When I enable some dubug configs
I get the following error by enter in the serial shell:
sert: Assertion failed at file:spi/spi_driver.c line: 358
arm_registerdump: R0: 0001 R1: 2004e840 R2:
40004800 R3: 20010684
arm_registerdump: R4: 2004e7a0 R5: 0002 R6:
2004f370 FP: 20010670
arm_registerdump: R8: SB: SL:
R11:
arm_registerdump: IP: 0003 SP: 2004f370 LR:
08005fad PC: 0800648e
arm_registerdump: xPSR: 6100 PRIMASK:
CONTROL: 0004
arm_registerdump: EXC_RETURN: ffe9
arm_dump_stack: User Stack:
On the line 358 of spi_driver.c there is this assertion:
/* Sanity check */
DEBUGASSERT(spi != NULL && (unsigned)bus < 1000);
Any Idea?
Best regards
Roberto
Re: SPI problem
Thanks Petro! This solve one part of the problem: I don't receive any crash now. There is another thinks tht is not clear to me: the macro SPIDEV_ID(spitool->devtype, spitool->csn) is defined as #define SPIDEV_ID(type,index) uint32_t)(type) & 0x) << 16) | \ ((uint32_t)(index) & 0x)) in the file include/nuttx/spi/spi.h. This should means that calling it with the parameters spitool->devtype=0x23 and spitool->csn=0 should give 0x23 as return value and not 0x17... Best regards Roberto On 3/7/22 16:22, Petro Karashchenko wrote: Hello Roberto, I think that the problem is in the line's: "stm32_gpiowrite(g_spigpio[devid], !selected);". Those should be "stm32_gpiowrite(g_spigpio[SPIDEVID_INDEX(devid)], !selected);". Please try to see if that helps. Best regards, Petro пн, 7 бер. 2022 р. о 12:46 Roberto Bucher пише: I reached to move a little forward by analyzing the SPI on the nucleo-144 STM32F7 board, and I found out that the problem is now in the calling of SPI_SELECT in the nuttx/drivers/spi/spi_transfer.c and the spi_transfer function. This are the values in the seq structure before launching the SPI_SELECT command. nsh> spi bus BUS EXISTS? Bus 0: NO Bus 1: NO Bus 2: YES Bus 3: NO nsh> spi exch -b2 -x4 aabbccdd Sending: AA BB CC DD seq -> dev: 0x17, mode: 3, nbits: 8, ntrans: 1, freq: 400 Received: FF FF FF FF To avoid the dump error I modified the seq->dev from 0x17 to 0x0004... It seems that the seq->dev value is not correct... Best regards Roberto On 3/6/22 13:47, Roberto Bucher wrote: Thanks Petro I've modified the nucleo-144/src/stm32_spi.c file by simply adding: struct spi_dev_s *g_spiX; and by adding spi_register(g_spiX, X); in the where X is the spi device number (in my example spi2) in the shell the /dev/spi2 is available. Best regards Roberto On 3/6/22 12:49, Petro Karashchenko wrote: Hello Roberto, I'm asking this because I examined nucleo-144 board source code and currently I do not see a "spi_register" call in board init files. So I assume that you have some modified code and it is very hard to make any conclusions while not seeing the code. Best regards, Petro нд, 6 бер. 2022 р. о 13:40 Petro Karashchenko пише: Hello Roberto, It would be good if you can dump assembly that is generated. What I see is that "intspi_register(FAR structspi_dev_s *spi, intbus)", so I'm assuming that R0 should be "spi" and R1 should be "bus", but in your dump "R0: 0001 R1: 2004e840" those seems to be inverted (0001 seems to be a "bus" and "2004e840" seems to be a "spi" pointer). The assembly code will show light on the dump that you provided. As an alternative you can provide the defconfig that you use if you are not using a custom board. Best regards, Petro нд, 6 бер. 2022 р. о 10:54 Roberto Bucher пише: When I enable some dubug configs I get the following error by enter in the serial shell: sert: Assertion failed at file:spi/spi_driver.c line: 358 arm_registerdump: R0: 0001 R1: 2004e840 R2: 40004800 R3: 20010684 arm_registerdump: R4: 2004e7a0 R5: 0002 R6: 2004f370 FP: 20010670 arm_registerdump: R8: SB: SL: R11: arm_registerdump: IP: 0003 SP: 2004f370 LR: 08005fad PC: 0800648e arm_registerdump: xPSR: 6100 PRIMASK: CONTROL: 0004 arm_registerdump: EXC_RETURN: ffe9 arm_dump_stack: User Stack: On the line 358 of spi_driver.c there is this assertion: /* Sanity check */ DEBUGASSERT(spi != NULL && (unsigned)bus < 1000); Any Idea? Best regards Roberto
Re: SPI problem
I reached to move a little forward by analyzing the SPI on the nucleo-144 STM32F7 board, and I found out that the problem is now in the calling of SPI_SELECT in the nuttx/drivers/spi/spi_transfer.c and the spi_transfer function. This are the values in the seq structure before launching the SPI_SELECT command. nsh> spi bus BUS EXISTS? Bus 0: NO Bus 1: NO Bus 2: YES Bus 3: NO nsh> spi exch -b2 -x4 aabbccdd Sending: AA BB CC DD seq -> dev: 0x17, mode: 3, nbits: 8, ntrans: 1, freq: 400 Received: FF FF FF FF To avoid the dump error I modified the seq->dev from 0x17 to 0x0004... It seems that the seq->dev value is not correct... Best regards Roberto On 3/6/22 13:47, Roberto Bucher wrote: Thanks Petro I've modified the nucleo-144/src/stm32_spi.c file by simply adding: struct spi_dev_s *g_spiX; and by adding spi_register(g_spiX, X); in the where X is the spi device number (in my example spi2) in the shell the /dev/spi2 is available. Best regards Roberto On 3/6/22 12:49, Petro Karashchenko wrote: Hello Roberto, I'm asking this because I examined nucleo-144 board source code and currently I do not see a "spi_register" call in board init files. So I assume that you have some modified code and it is very hard to make any conclusions while not seeing the code. Best regards, Petro нд, 6 бер. 2022 р. о 13:40 Petro Karashchenko пише: Hello Roberto, It would be good if you can dump assembly that is generated. What I see is that "intspi_register(FAR structspi_dev_s *spi, intbus)", so I'm assuming that R0 should be "spi" and R1 should be "bus", but in your dump "R0: 0001 R1: 2004e840" those seems to be inverted (0001 seems to be a "bus" and "2004e840" seems to be a "spi" pointer). The assembly code will show light on the dump that you provided. As an alternative you can provide the defconfig that you use if you are not using a custom board. Best regards, Petro нд, 6 бер. 2022 р. о 10:54 Roberto Bucher пише: When I enable some dubug configs I get the following error by enter in the serial shell: sert: Assertion failed at file:spi/spi_driver.c line: 358 arm_registerdump: R0: 0001 R1: 2004e840 R2: 40004800 R3: 20010684 arm_registerdump: R4: 2004e7a0 R5: 0002 R6: 2004f370 FP: 20010670 arm_registerdump: R8: SB: SL: R11: arm_registerdump: IP: 0003 SP: 2004f370 LR: 08005fad PC: 0800648e arm_registerdump: xPSR: 6100 PRIMASK: CONTROL: 0004 arm_registerdump: EXC_RETURN: ffe9 arm_dump_stack: User Stack: On the line 358 of spi_driver.c there is this assertion: /* Sanity check */ DEBUGASSERT(spi != NULL && (unsigned)bus < 1000); Any Idea? Best regards Roberto
Re: SPI problem
Thanks Petro I've modified the nucleo-144/src/stm32_spi.c file by simply adding: struct spi_dev_s *g_spiX; and by adding spi_register(g_spiX, X); in the where X is the spi device number (in my example spi2) in the shell the /dev/spi2 is available. Best regards Roberto On 3/6/22 12:49, Petro Karashchenko wrote: Hello Roberto, I'm asking this because I examined nucleo-144 board source code and currently I do not see a "spi_register" call in board init files. So I assume that you have some modified code and it is very hard to make any conclusions while not seeing the code. Best regards, Petro нд, 6 бер. 2022 р. о 13:40 Petro Karashchenko пише: Hello Roberto, It would be good if you can dump assembly that is generated. What I see is that "intspi_register(FAR structspi_dev_s *spi, intbus)", so I'm assuming that R0 should be "spi" and R1 should be "bus", but in your dump "R0: 0001 R1: 2004e840" those seems to be inverted (0001 seems to be a "bus" and "2004e840" seems to be a "spi" pointer). The assembly code will show light on the dump that you provided. As an alternative you can provide the defconfig that you use if you are not using a custom board. Best regards, Petro нд, 6 бер. 2022 р. о 10:54 Roberto Bucher пише: When I enable some dubug configs I get the following error by enter in the serial shell: sert: Assertion failed at file:spi/spi_driver.c line: 358 arm_registerdump: R0: 0001 R1: 2004e840 R2: 40004800 R3: 20010684 arm_registerdump: R4: 2004e7a0 R5: 0002 R6: 2004f370 FP: 20010670 arm_registerdump: R8: SB: SL: R11: arm_registerdump: IP: 0003 SP: 2004f370 LR: 08005fad PC: 0800648e arm_registerdump: xPSR: 6100 PRIMASK: CONTROL: 0004 arm_registerdump: EXC_RETURN: ffe9 arm_dump_stack: User Stack: On the line 358 of spi_driver.c there is this assertion: /* Sanity check */ DEBUGASSERT(spi != NULL && (unsigned)bus < 1000); Any Idea? Best regards Roberto
SPI problem
When I enable some dubug configs I get the following error by enter in the serial shell: sert: Assertion failed at file:spi/spi_driver.c line: 358 arm_registerdump: R0: 0001 R1: 2004e840 R2: 40004800 R3: 20010684 arm_registerdump: R4: 2004e7a0 R5: 0002 R6: 2004f370 FP: 20010670 arm_registerdump: R8: SB: SL: R11: arm_registerdump: IP: 0003 SP: 2004f370 LR: 08005fad PC: 0800648e arm_registerdump: xPSR: 6100 PRIMASK: CONTROL: 0004 arm_registerdump: EXC_RETURN: ffe9 arm_dump_stack: User Stack: On the line 358 of spi_driver.c there is this assertion: /* Sanity check */ DEBUGASSERT(spi != NULL && (unsigned)bus < 1000); Any Idea? Best regards Roberto
Re: SPI Example
I followed a bit the problem with the SPI bus and I reached to find
where I have the first problem:
1) In the shell: spi bus gives me that the BUS 2 is available
2) I launch "spi -b2 -x4 aabbccdd" and I pass through the following files:
apps/system/spi/spi_exch.c -> apps/system/spi/spi_devif.c ->
nuttx/drivers/spi/spi_driver.c -> /nuttx/drivers/spi/spi_transfer.c
which sould be ok.
3) In spi_transfer.c , the line "SPI_LOCK(spi, true)" causes the dump!
When I try to set the DEBUG ASSERTION in "make menuconfig", this causes
a dump directly when I enter the nuttx shell in my nucleo-144 board...
It is quite difficult to find out an idea to follow the problem yet...
Best regards
Roberto
On 3/4/22 13:34, Alan Carvalho de Assis wrote:
Hi Roberto,
Enable the DEBUG ASSERTION to see where the crash is happening?
What you get when you run:
nsh> spi bus
Maybe you passing an invalid bus number.
BR,
Alan
On 3/4/22, Roberto Bucher wrote:
Thanks Alan, but the main problem is that this test gives me an error by
the execution on my STM32F7 nucleo-144 board...
nsh> spi exch -b 2 -x 4 aabbccdd
Seup_assert: Assertion failed at file:armv7-m/arm_hardfault.c line: 174
arm_registerdump: R0: R1: 2001a334 R2: 0001 R3: 2201
arm_registerdump: R4: R5: 2201 R6: 2004f774 FP: 2004f770
arm_registerdump: R8: 2001a380 SB: 0005 SL: 2001a358 R11: 2001a35c
arm_registerdump: IP: 0018 SP: 2001a2b0 LR: 08016f63 PC: 0801700c
arm_registerdump: xPSR: 6100 PRIMASK: CONTROL:
arm_registerdump: EXC_RETURN: ffe9
arm_dump_stack: User Stack:
arm_dump_stack: sp: 2001a170
arm_dump_stack: base: 20019c70
arm_dump_stack: size: 07c8
arm_stackdump: 2001a160: 20019c70 2001a170 20011d50 0801b447
0801700c
arm_stackdump: 2001a180: 08021224 0801700a 080236b8 2004f774
2004f770 2
BR
Roberto
On 3/4/22 12:29, Alan Carvalho de Assis wrote:
Hi Roberto,
We have the SPI Tool that does exactly what you want:
Application Configuration --->
System Libraries and NSH Add-Ons --->
[*] SPI tool --->
BR,
Alan
On 3/4/22, Roberto Bucher wrote:
Hi
where can I found a simple example that send n bytes to the SPI and
receive m bytes?
I can now see the /dev/spi but using simple methods like open and write
doesn't give me any signal on the bus...
Thanks in advance
Roberto
Re: SPI Example
Thanks Alan, but the main problem is that this test gives me an error by the execution on my STM32F7 nucleo-144 board... nsh> spi exch -b 2 -x 4 aabbccdd Seup_assert: Assertion failed at file:armv7-m/arm_hardfault.c line: 174 arm_registerdump: R0: R1: 2001a334 R2: 0001 R3: 2201 arm_registerdump: R4: R5: 2201 R6: 2004f774 FP: 2004f770 arm_registerdump: R8: 2001a380 SB: 0005 SL: 2001a358 R11: 2001a35c arm_registerdump: IP: 0018 SP: 2001a2b0 LR: 08016f63 PC: 0801700c arm_registerdump: xPSR: 6100 PRIMASK: CONTROL: arm_registerdump: EXC_RETURN: ffe9 arm_dump_stack: User Stack: arm_dump_stack: sp: 2001a170 arm_dump_stack: base: 20019c70 arm_dump_stack: size: 07c8 arm_stackdump: 2001a160: 20019c70 2001a170 20011d50 0801b447 0801700c arm_stackdump: 2001a180: 08021224 0801700a 080236b8 2004f774 2004f770 2 BR Roberto On 3/4/22 12:29, Alan Carvalho de Assis wrote: Hi Roberto, We have the SPI Tool that does exactly what you want: Application Configuration ---> System Libraries and NSH Add-Ons ---> [*] SPI tool ---> BR, Alan On 3/4/22, Roberto Bucher wrote: Hi where can I found a simple example that send n bytes to the SPI and receive m bytes? I can now see the /dev/spi but using simple methods like open and write doesn't give me any signal on the bus... Thanks in advance Roberto
SPI Example
Hi where can I found a simple example that send n bytes to the SPI and receive m bytes? I can now see the /dev/spi but using simple methods like open and write doesn't give me any signal on the bus... Thanks in advance Roberto
SPI on STM32F746RE (nucleo-144)
Hi I'm trying to get the SPI working on the nucleo-144:f746 board, but I can't see the /dev/spi on the generated binary... This means that the SPI on this card is not (yet) implemented? Thanks in advance Roberto
Briki board
Hi we have this little board (www.briki.org) with 2 different cores: MBC-WB01-BPN: SAMD211 – ESP322 – EXT 64 Mbit flash3 – PCB Antenna4 – No Crypto5 SAMD211: ATSAMD21G18A ARM® Cortex®-M0+ ESP32: ESP32-D0WD dual-core Tensilica Xtensa LX6 running @240MHz How difficult should be the porting of the ESP32 processor to NuttX? It is possible to use one of the Expressif configurations? What about the ATSAMD21G18A board? Thanks in advance!
Troubles with CAN bus on STM32 Nucleo-F446RE
Hi I'm trying to send messages using the CAN bus on the nucleo-f446re. The RX and TX of the STM32 is connected to a MIKROE transceiver (the same working without problems with the nucleo-STM32F746ZG board, but the bus stop after 8 messages (I think that stops because of the full output buffer...) Does somebody reaches to communicate with CAN bus using this board? Thanks in advance BR Roberto
Roberto Bucher's Zoom Meeting
Roberto Bucher is inviting you to a scheduled Zoom meeting. Topic: Roberto Bucher's Zoom Meeting Time: May 18, 2021 01:00 PM Zurich Join Zoom Meeting https://supsi.zoom.us/j/61553219775?pwd=TkcwNkJ3YWhUYXFxa2xmQW5Za0hxUT09 Meeting ID: 615 5321 9775 Passcode: 133097 BR Roberto
Re: Google Summer of Code
I have a meeting till for 1:45PM to 3:15PM UTC in the afternoon, so for
me is possible to do something starting at 3:30PM. Otherwise it is
possible for me to do an additional meeting with Brennan and Michal
tomorrow later in the afternoon, and something today with Pavel and
Michal at 11:15
BR
Roberto
On 5/18/21 10:05 AM, Brennan Ashton wrote:
I am in PT so 11:00 UTC is 4AM (and tonight is already a very late
night for me, so if we could possibly do it a little later that would
be ideal if possible.
--Brennan
On Tue, May 18, 2021, 12:59 AM <mailto:lencm...@fel.cvut.cz>> wrote:
Hello all,
firstly I would like to thank you all for your support during the
proposal period. I am looking forward to cooperating on pysimCoder
integration with NuttX.
I forked pysimCoder GIT few days ago and started with implementation
of SocketCAN support. I can successfully send and receive CAN
messages, thought RT receive is yet to be done. The GIT branch can be
seen at <<https://github.com/michallenc/pysimCoder/tree/socketcan
<https://github.com/michallenc/pysimCoder/tree/socketcan>>.
Regarding the meeting, I have a consultation for semestral project
starting at 11 UTC. I have just a one question about the project,
so I
expect it would take just a few minutes, would it be ok to move our
meeting to 11:15 UTC?
Regarding some place for updates about the project, I think NuttX
GitHub Issue would be the most appropriate as it should have the most
amount of readers.
Best regards,
Michal Lenc
Cituji Roberto Bucher mailto:roberto.buc...@supsi.ch>>:
> Hi
>
> for me it's ok to do a meeting today at 11:00 UTC. Do I have to
> organize a zoom meeting?
>
> BR
>
> Roberto
>
> On 5/18/21 9:22 AM, Pavel Pisa wrote:
>> Hello Roberto and others,
>>
>> I am happy that the project has been selected and hope that
>> it helps to advance usesfull toll and OS/HW combination.
>>
>> My availability, today 11:00 to 12:00 UTC, then after 18:00 UTC.
>> Tomorrow, Wednesday till 11:00 UTC and after 18:00 UTC.
>> Thusday is ideal, I can schedule activities at my will.
>> I want to have leave on this Friday and weekend, we plan
>> boat trip. Next week Tueday and even better Thursday
>> and evenings after 18:00 UTC other days are possible.
>>
>> Best wishes,
>>
>> Pavel
>>
>> PS: we should probably define some place where to collect
>> information to coordinate the work. May it be corresponding
>> NuttX Apache issue or pysimCoder Wiki, NuttX Wiki
>> Michal Lenc's GitHub wiki
>>
>> On Tuesday 18 of May 2021 07:34:42 Roberto Bucher wrote:
>>> Buongiorno Michal
>>>
>>> I'd like to congratulate with you about the acceptance of the
NuttX
>>> project "NuttX Support for RapidControl Applications
Development with
>>> pysimCoder" a the GSOC!
>>>
>>> I'm very excited to share with you my experience during this
project,
>>> and I hope that your contribution can help in develop and sharing
>>> pysimCoder with the community.
>>>
>>> I think that we can organize ASAP a video meeting, perhaps
with Prof.
>>> Pisa and Brennan Ashton.
>>>
>>> Best regards
>>>
>>> Prof. Roberto Bucher
Re: Google Summer of Code
Hi for me it's ok to do a meeting today at 11:00 UTC. Do I have to organize a zoom meeting? BR Roberto On 5/18/21 9:22 AM, Pavel Pisa wrote: Hello Roberto and others, I am happy that the project has been selected and hope that it helps to advance usesfull toll and OS/HW combination. My availability, today 11:00 to 12:00 UTC, then after 18:00 UTC. Tomorrow, Wednesday till 11:00 UTC and after 18:00 UTC. Thusday is ideal, I can schedule activities at my will. I want to have leave on this Friday and weekend, we plan boat trip. Next week Tueday and even better Thursday and evenings after 18:00 UTC other days are possible. Best wishes, Pavel PS: we should probably define some place where to collect information to coordinate the work. May it be corresponding NuttX Apache issue or pysimCoder Wiki, NuttX Wiki Michal Lenc's GitHub wiki On Tuesday 18 of May 2021 07:34:42 Roberto Bucher wrote: Buongiorno Michal I'd like to congratulate with you about the acceptance of the NuttX project "NuttX Support for RapidControl Applications Development with pysimCoder" a the GSOC! I'm very excited to share with you my experience during this project, and I hope that your contribution can help in develop and sharing pysimCoder with the community. I think that we can organize ASAP a video meeting, perhaps with Prof. Pisa and Brennan Ashton. Best regards Prof. Roberto Bucher
Google Summer of Code
Buongiorno Michal I'd like to congratulate with you about the acceptance of the NuttX project "NuttX Support for RapidControl Applications Development with pysimCoder" a the GSOC! I'm very excited to share with you my experience during this project, and I hope that your contribution can help in develop and sharing pysimCoder with the community. I think that we can organize ASAP a video meeting, perhaps with Prof. Pisa and Brennan Ashton. Best regards Prof. Roberto Bucher
CAN on STM32H7 platforms under NuttX
Hi For a bachelor project with a student, which will start on may 2021, I have to implement a CAN communication between a STM32H743ZI2 board and 2 STM32F446 boards. I'd like to propose to my student to work with micro-ROS and NuttX on both platforms. Basically it seems that the CAN bus files are not yet implemented in the NuttX tree for the STM32H7 board. Did somebody work on implementation of CAN bus for the STM32H7 architecture? Thanks in advance Roberto
Re: {Spam?} Google Summer of Code Proposal
Thanks Michal I'll read your document ASAP. I think that I'll be your mentor in this project and I can give you my help and all the required info on pysimCoder and on the tools provided for implementing new blocks. Best regards Roberto Bucher On 3/15/21 4:38 PM, lencm...@fel.cvut.cz wrote: Hello, as some of you already know, I would like to take part in Google Summer of Code with project NuttX Support for Rapid Control Applications Development with pysimCoder (https://issues.apache.org/jira/browse/NUTTX-3). Student application period begins on March 29, but some discussion with community should take place prior to that. I have written the draft of my GSoC proposal, which can be seen at <https://docs.google.com/document/d/13jipDxufiD3QGfJ0Udnp_B_3JxieoPO3lvrCUvLVNhQ/edit?usp=sharing>. Project goals and scheduled timeline can be seen on pages 3 to 5. I would like to ask for feedback from potential mentors and other members of NuttX community to proposed goals and timeline. The shared document should allow everyone to add comments and suggestions, or we can keep the discussion just here in mailing list. Thank you. Best regards, Michal Lenc
