Re: NSH Not Responding to Commands Over Serial on STM32F446RET
will do - thanks for your help On Tue, Dec 10, 2024 at 3:27 PM Alan C. Assis wrote: > Hi Russel, > > Please look at the schematics of both boards, sometimes ST change pins used > on different board revisions. > > Also, if you discover some important detail about these boards, please > submit a PR updating the board Documentation/ this way you make the life of > the next developer/user easier. > > BR, > > Alan > > On Mon, Dec 9, 2024 at 10:21 PM Russell Haley > wrote: > > > For what it's worth: I had issues using ST-Link and serial with a Nucleo > > board for that MCU. I luckily had two boards and found that one worked > and > > one didn't. From the list archive: > > > > I say was, because I eventually did gain access. It turns out that I have > > two different kinds of nucleo boards but only one variant works. The main > > boards are all MB1136 Rev C (STM32F446RE), but the ST-Link attached to > the > > boards is different. The ones that do not work say 1940 on the BACK of > the > > ST-Link, where as the ones I can connect with say IQE 1915 on the FRONT > of > > the ST-Link. So it appears that the older revision of ST-Link works, > where > > as the newer revision does not? > > > > On Fri, Dec 6, 2024 at 11:20 AM Russell Burgett < > [email protected] > > > > > wrote: > > > > > I am using NuttX on a STM32F446RET. > > > > > > I have the console enabled (serial) and am able to receive data from my > > > target, however NSH is not responding to commands sent over serial. > > > > > > I can execute commands from my nsh_romfsimg.h file, although cd fails > > with > > > code 2 and ls fails with the message "out of memory". > > > > > > Oddly when I run my own application and send commands to the console > > while > > > the app is running they appear to buffered, read and executed by NSH > > after > > > the app exits. > > > > > > running ps I get > > > PID PRI POLICY TYPENPX STATEEVENT SIGMASK STACK > COMMAND > > > 0 0 FIFO Kthread N-- Ready 00 Idle > > Task > > > 1 224 FIFO Kthread --- Waiting Signal 002028 > hpwork > > > 2 100 FIFO Kthread --- Waiting Signal 002028 > lpwork > > > 3 100 FIFO Task--- Running 002028 init > > > > > > df . gives me > > > Block Number > > > Size Blocks Used Available Mounted on > > > 6444 0 /etc > > > 000 0 /proc > > > > > > Could anyone provide insights into why these issues might be occurring, > > > especially the "out of memory" error and the failure of NSH to execute > > > commands ? > > > > > > Thank you > > > > > > here is my .config file > > > # > > > # Automatically generated file; DO NOT EDIT. > > > # Nuttx/ Configuration > > > # > > > > > > # > > > # Build Setup > > > # > > > # CONFIG_EXPERIMENTAL is not set > > > # CONFIG_DEFAULT_SMALL is not set > > > CONFIG_HOST_LINUX=y > > > # CONFIG_HOST_MACOS is not set > > > # CONFIG_HOST_WINDOWS is not set > > > # CONFIG_HOST_OTHER is not set > > > > > > # > > > # Build Configuration > > > # > > > CONFIG_APPS_DIR="../apps" > > > CONFIG_BUILD_FLAT=y > > > # CONFIG_BUILD_2PASS is not set > > > > > > # > > > # Binary Output Formats > > > # > > > # CONFIG_RRLOAD_BINARY is not set > > > # CONFIG_CXD56_BINARY is not set > > > CONFIG_INTELHEX_BINARY=y > > > # CONFIG_MOTOROLA_SREC is not set > > > CONFIG_RAW_BINARY=y > > > # CONFIG_UBOOT_UIMAGE is not set > > > # CONFIG_DFU_BINARY is not set > > > > > > # > > > # Customize Header Files > > > # > > > # CONFIG_ARCH_HAVE_STDINT_H is not set > > > # CONFIG_ARCH_HAVE_STDBOOL_H is not set > > > # CONFIG_ARCH_HAVE_MATH_H is not set > > > CONFIG_ARCH_FLOAT_H=y > > > CONFIG_ARCH_HAVE_STDARG_H=y > > > # CONFIG_ARCH_STDARG_H is not set > > > CONFIG_ARCH_HAVE_SETJMP=y > > > # CONFIG_ARCH_SETJMP_H is not set > > > # CONFIG_ARCH_DEBUG_H is not set > > > > > > # > > > # Debug Options > > > # > > > CONFIG_DEBUG_ALERT=y > > > CONFIG_DEBUG_FEATURES=y > > > > > > # > > > # Debug SYSLOG Output Controls > > > # > > > CONFIG_DEBUG_ERROR=y > > > CONFIG_DEBUG_WARN=y > > > CONFIG_DEBUG_INFO=y > > > # CONFIG_DEBUG_ASSERTIONS is not set > > > > > > # > > > # Subsystem Debug Options > > > # > > > # CONFIG_DEBUG_BINFMT is not set > > > # CONFIG_DEBUG_FS is not set > > > # CONFIG_DEBUG_GRAPHICS is not set > > > # CONFIG_DEBUG_LIB is not set > > > CONFIG_DEBUG_MM=y > > > CONFIG_DEBUG_MM_ERROR=y > > > # CONFIG_DEBUG_MM_WARN is not set > > > # CONFIG_DEBUG_MM_INFO is not set > > > # CONFIG_DEBUG_POWER is not set > > > # CONFIG_DEBUG_SCHED is not set > > > > > > # > > > # OS Function Debug Options > > > # > > > # CONFIG_DEBUG_IRQ is not set > > > > > > # > > > # Driver Debug Options > > > # > > > CONFIG_DEBUG_ANALOG=y > > > CONFIG_DEBUG_ANALOG_ERROR=y > > > CONFIG_DEBUG_ANALOG_WARN=y > > > # CONFIG_DEBUG_ANALOG_INFO is not set > > > CONFIG_DEBUG_CAN=y > > > CONFIG_DEBUG_CAN_ERROR=y > > > CONFIG_DEBUG_CAN_WARN=y > > > # CONF
Re: NSH Not Responding to Commands Over Serial on STM32F446RET
Hi Russel, Please look at the schematics of both boards, sometimes ST change pins used on different board revisions. Also, if you discover some important detail about these boards, please submit a PR updating the board Documentation/ this way you make the life of the next developer/user easier. BR, Alan On Mon, Dec 9, 2024 at 10:21 PM Russell Haley wrote: > For what it's worth: I had issues using ST-Link and serial with a Nucleo > board for that MCU. I luckily had two boards and found that one worked and > one didn't. From the list archive: > > I say was, because I eventually did gain access. It turns out that I have > two different kinds of nucleo boards but only one variant works. The main > boards are all MB1136 Rev C (STM32F446RE), but the ST-Link attached to the > boards is different. The ones that do not work say 1940 on the BACK of the > ST-Link, where as the ones I can connect with say IQE 1915 on the FRONT of > the ST-Link. So it appears that the older revision of ST-Link works, where > as the newer revision does not? > > On Fri, Dec 6, 2024 at 11:20 AM Russell Burgett > > wrote: > > > I am using NuttX on a STM32F446RET. > > > > I have the console enabled (serial) and am able to receive data from my > > target, however NSH is not responding to commands sent over serial. > > > > I can execute commands from my nsh_romfsimg.h file, although cd fails > with > > code 2 and ls fails with the message "out of memory". > > > > Oddly when I run my own application and send commands to the console > while > > the app is running they appear to buffered, read and executed by NSH > after > > the app exits. > > > > running ps I get > > PID PRI POLICY TYPENPX STATEEVENT SIGMASK STACK COMMAND > > 0 0 FIFO Kthread N-- Ready 00 Idle > Task > > 1 224 FIFO Kthread --- Waiting Signal 002028 hpwork > > 2 100 FIFO Kthread --- Waiting Signal 002028 lpwork > > 3 100 FIFO Task--- Running 002028 init > > > > df . gives me > > Block Number > > Size Blocks Used Available Mounted on > > 6444 0 /etc > > 000 0 /proc > > > > Could anyone provide insights into why these issues might be occurring, > > especially the "out of memory" error and the failure of NSH to execute > > commands ? > > > > Thank you > > > > here is my .config file > > # > > # Automatically generated file; DO NOT EDIT. > > # Nuttx/ Configuration > > # > > > > # > > # Build Setup > > # > > # CONFIG_EXPERIMENTAL is not set > > # CONFIG_DEFAULT_SMALL is not set > > CONFIG_HOST_LINUX=y > > # CONFIG_HOST_MACOS is not set > > # CONFIG_HOST_WINDOWS is not set > > # CONFIG_HOST_OTHER is not set > > > > # > > # Build Configuration > > # > > CONFIG_APPS_DIR="../apps" > > CONFIG_BUILD_FLAT=y > > # CONFIG_BUILD_2PASS is not set > > > > # > > # Binary Output Formats > > # > > # CONFIG_RRLOAD_BINARY is not set > > # CONFIG_CXD56_BINARY is not set > > CONFIG_INTELHEX_BINARY=y > > # CONFIG_MOTOROLA_SREC is not set > > CONFIG_RAW_BINARY=y > > # CONFIG_UBOOT_UIMAGE is not set > > # CONFIG_DFU_BINARY is not set > > > > # > > # Customize Header Files > > # > > # CONFIG_ARCH_HAVE_STDINT_H is not set > > # CONFIG_ARCH_HAVE_STDBOOL_H is not set > > # CONFIG_ARCH_HAVE_MATH_H is not set > > CONFIG_ARCH_FLOAT_H=y > > CONFIG_ARCH_HAVE_STDARG_H=y > > # CONFIG_ARCH_STDARG_H is not set > > CONFIG_ARCH_HAVE_SETJMP=y > > # CONFIG_ARCH_SETJMP_H is not set > > # CONFIG_ARCH_DEBUG_H is not set > > > > # > > # Debug Options > > # > > CONFIG_DEBUG_ALERT=y > > CONFIG_DEBUG_FEATURES=y > > > > # > > # Debug SYSLOG Output Controls > > # > > CONFIG_DEBUG_ERROR=y > > CONFIG_DEBUG_WARN=y > > CONFIG_DEBUG_INFO=y > > # CONFIG_DEBUG_ASSERTIONS is not set > > > > # > > # Subsystem Debug Options > > # > > # CONFIG_DEBUG_BINFMT is not set > > # CONFIG_DEBUG_FS is not set > > # CONFIG_DEBUG_GRAPHICS is not set > > # CONFIG_DEBUG_LIB is not set > > CONFIG_DEBUG_MM=y > > CONFIG_DEBUG_MM_ERROR=y > > # CONFIG_DEBUG_MM_WARN is not set > > # CONFIG_DEBUG_MM_INFO is not set > > # CONFIG_DEBUG_POWER is not set > > # CONFIG_DEBUG_SCHED is not set > > > > # > > # OS Function Debug Options > > # > > # CONFIG_DEBUG_IRQ is not set > > > > # > > # Driver Debug Options > > # > > CONFIG_DEBUG_ANALOG=y > > CONFIG_DEBUG_ANALOG_ERROR=y > > CONFIG_DEBUG_ANALOG_WARN=y > > # CONFIG_DEBUG_ANALOG_INFO is not set > > CONFIG_DEBUG_CAN=y > > CONFIG_DEBUG_CAN_ERROR=y > > CONFIG_DEBUG_CAN_WARN=y > > # CONFIG_DEBUG_CAN_INFO is not set > > CONFIG_DEBUG_GPIO=y > > CONFIG_DEBUG_GPIO_ERROR=y > > CONFIG_DEBUG_GPIO_WARN=y > > # CONFIG_DEBUG_GPIO_INFO is not set > > # CONFIG_DEBUG_I2C is not set > > # CONFIG_DEBUG_SPI is not set > > CONFIG_DEBUG_TIMER=y > > CONFIG_DEBUG_TIMER_ERROR=y > > CONFIG_DEBUG_TIMER_WARN=y > > # CONFIG_DEBUG_TIMER_INFO is not set > > CONFIG_ARCH_HAVE_STACKCHECK=y > > # CONFIG_STACK_COLORATION is not set > > CONFIG_ARCH_HAVE_H
Re: NSH Not Responding to Commands Over Serial on STM32F446RET
thanks for the help all started using gdb yesterday in an effort to track down the issue - found that NSH runs just fine both with my app and the nuttx example my test board has a ST-LINK interface permanently attached and am wondering (vaguely) if this is part of the issue may defer looking at the NSH issue until I have an actual target board On Tue, Dec 10, 2024 at 5:06 AM Tomek CEDRO wrote: > Have you tried upgrading st-link firmware? I also noticed similar problem, > st-link firmware upgrade helped :-) > > -- > CeDeROM, SQ7MHZ, http://www.tomek.cedro.info > > On Tue, Dec 10, 2024, 02:21 Russell Haley wrote: > > > For what it's worth: I had issues using ST-Link and serial with a Nucleo > > board for that MCU. I luckily had two boards and found that one worked > and > > one didn't. From the list archive: > > > > I say was, because I eventually did gain access. It turns out that I have > > two different kinds of nucleo boards but only one variant works. The main > > boards are all MB1136 Rev C (STM32F446RE), but the ST-Link attached to > the > > boards is different. The ones that do not work say 1940 on the BACK of > the > > ST-Link, where as the ones I can connect with say IQE 1915 on the FRONT > of > > the ST-Link. So it appears that the older revision of ST-Link works, > where > > as the newer revision does not? > > > > On Fri, Dec 6, 2024 at 11:20 AM Russell Burgett < > [email protected] > > > > > wrote: > > > > > I am using NuttX on a STM32F446RET. > > > > > > I have the console enabled (serial) and am able to receive data from my > > > target, however NSH is not responding to commands sent over serial. > > > > > > I can execute commands from my nsh_romfsimg.h file, although cd fails > > with > > > code 2 and ls fails with the message "out of memory". > > > > > > Oddly when I run my own application and send commands to the console > > while > > > the app is running they appear to buffered, read and executed by NSH > > after > > > the app exits. > > > > > > running ps I get > > > PID PRI POLICY TYPENPX STATEEVENT SIGMASK STACK > COMMAND > > > 0 0 FIFO Kthread N-- Ready 00 Idle > > Task > > > 1 224 FIFO Kthread --- Waiting Signal 002028 > hpwork > > > 2 100 FIFO Kthread --- Waiting Signal 002028 > lpwork > > > 3 100 FIFO Task--- Running 002028 init > > > > > > df . gives me > > > Block Number > > > Size Blocks Used Available Mounted on > > > 6444 0 /etc > > > 000 0 /proc > > > > > > Could anyone provide insights into why these issues might be occurring, > > > especially the "out of memory" error and the failure of NSH to execute > > > commands ? > > > > > > Thank you > > > > > > here is my .config file > > > # > > > # Automatically generated file; DO NOT EDIT. > > > # Nuttx/ Configuration > > > # > > > > > > # > > > # Build Setup > > > # > > > # CONFIG_EXPERIMENTAL is not set > > > # CONFIG_DEFAULT_SMALL is not set > > > CONFIG_HOST_LINUX=y > > > # CONFIG_HOST_MACOS is not set > > > # CONFIG_HOST_WINDOWS is not set > > > # CONFIG_HOST_OTHER is not set > > > > > > # > > > # Build Configuration > > > # > > > CONFIG_APPS_DIR="../apps" > > > CONFIG_BUILD_FLAT=y > > > # CONFIG_BUILD_2PASS is not set > > > > > > # > > > # Binary Output Formats > > > # > > > # CONFIG_RRLOAD_BINARY is not set > > > # CONFIG_CXD56_BINARY is not set > > > CONFIG_INTELHEX_BINARY=y > > > # CONFIG_MOTOROLA_SREC is not set > > > CONFIG_RAW_BINARY=y > > > # CONFIG_UBOOT_UIMAGE is not set > > > # CONFIG_DFU_BINARY is not set > > > > > > # > > > # Customize Header Files > > > # > > > # CONFIG_ARCH_HAVE_STDINT_H is not set > > > # CONFIG_ARCH_HAVE_STDBOOL_H is not set > > > # CONFIG_ARCH_HAVE_MATH_H is not set > > > CONFIG_ARCH_FLOAT_H=y > > > CONFIG_ARCH_HAVE_STDARG_H=y > > > # CONFIG_ARCH_STDARG_H is not set > > > CONFIG_ARCH_HAVE_SETJMP=y > > > # CONFIG_ARCH_SETJMP_H is not set > > > # CONFIG_ARCH_DEBUG_H is not set > > > > > > # > > > # Debug Options > > > # > > > CONFIG_DEBUG_ALERT=y > > > CONFIG_DEBUG_FEATURES=y > > > > > > # > > > # Debug SYSLOG Output Controls > > > # > > > CONFIG_DEBUG_ERROR=y > > > CONFIG_DEBUG_WARN=y > > > CONFIG_DEBUG_INFO=y > > > # CONFIG_DEBUG_ASSERTIONS is not set > > > > > > # > > > # Subsystem Debug Options > > > # > > > # CONFIG_DEBUG_BINFMT is not set > > > # CONFIG_DEBUG_FS is not set > > > # CONFIG_DEBUG_GRAPHICS is not set > > > # CONFIG_DEBUG_LIB is not set > > > CONFIG_DEBUG_MM=y > > > CONFIG_DEBUG_MM_ERROR=y > > > # CONFIG_DEBUG_MM_WARN is not set > > > # CONFIG_DEBUG_MM_INFO is not set > > > # CONFIG_DEBUG_POWER is not set > > > # CONFIG_DEBUG_SCHED is not set > > > > > > # > > > # OS Function Debug Options > > > # > > > # CONFIG_DEBUG_IRQ is not set > > > > > > # > > > # Driver Debug Options > > > # > > > CONFIG_DEBUG_ANALOG=y > > > CONFIG_DEBUG_ANALOG_ERROR=y > > > CONFIG_DEBUG_ANALOG_W
Re: NSH Not Responding to Commands Over Serial on STM32F446RET
Have you tried upgrading st-link firmware? I also noticed similar problem, st-link firmware upgrade helped :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info On Tue, Dec 10, 2024, 02:21 Russell Haley wrote: > For what it's worth: I had issues using ST-Link and serial with a Nucleo > board for that MCU. I luckily had two boards and found that one worked and > one didn't. From the list archive: > > I say was, because I eventually did gain access. It turns out that I have > two different kinds of nucleo boards but only one variant works. The main > boards are all MB1136 Rev C (STM32F446RE), but the ST-Link attached to the > boards is different. The ones that do not work say 1940 on the BACK of the > ST-Link, where as the ones I can connect with say IQE 1915 on the FRONT of > the ST-Link. So it appears that the older revision of ST-Link works, where > as the newer revision does not? > > On Fri, Dec 6, 2024 at 11:20 AM Russell Burgett > > wrote: > > > I am using NuttX on a STM32F446RET. > > > > I have the console enabled (serial) and am able to receive data from my > > target, however NSH is not responding to commands sent over serial. > > > > I can execute commands from my nsh_romfsimg.h file, although cd fails > with > > code 2 and ls fails with the message "out of memory". > > > > Oddly when I run my own application and send commands to the console > while > > the app is running they appear to buffered, read and executed by NSH > after > > the app exits. > > > > running ps I get > > PID PRI POLICY TYPENPX STATEEVENT SIGMASK STACK COMMAND > > 0 0 FIFO Kthread N-- Ready 00 Idle > Task > > 1 224 FIFO Kthread --- Waiting Signal 002028 hpwork > > 2 100 FIFO Kthread --- Waiting Signal 002028 lpwork > > 3 100 FIFO Task--- Running 002028 init > > > > df . gives me > > Block Number > > Size Blocks Used Available Mounted on > > 6444 0 /etc > > 000 0 /proc > > > > Could anyone provide insights into why these issues might be occurring, > > especially the "out of memory" error and the failure of NSH to execute > > commands ? > > > > Thank you > > > > here is my .config file > > # > > # Automatically generated file; DO NOT EDIT. > > # Nuttx/ Configuration > > # > > > > # > > # Build Setup > > # > > # CONFIG_EXPERIMENTAL is not set > > # CONFIG_DEFAULT_SMALL is not set > > CONFIG_HOST_LINUX=y > > # CONFIG_HOST_MACOS is not set > > # CONFIG_HOST_WINDOWS is not set > > # CONFIG_HOST_OTHER is not set > > > > # > > # Build Configuration > > # > > CONFIG_APPS_DIR="../apps" > > CONFIG_BUILD_FLAT=y > > # CONFIG_BUILD_2PASS is not set > > > > # > > # Binary Output Formats > > # > > # CONFIG_RRLOAD_BINARY is not set > > # CONFIG_CXD56_BINARY is not set > > CONFIG_INTELHEX_BINARY=y > > # CONFIG_MOTOROLA_SREC is not set > > CONFIG_RAW_BINARY=y > > # CONFIG_UBOOT_UIMAGE is not set > > # CONFIG_DFU_BINARY is not set > > > > # > > # Customize Header Files > > # > > # CONFIG_ARCH_HAVE_STDINT_H is not set > > # CONFIG_ARCH_HAVE_STDBOOL_H is not set > > # CONFIG_ARCH_HAVE_MATH_H is not set > > CONFIG_ARCH_FLOAT_H=y > > CONFIG_ARCH_HAVE_STDARG_H=y > > # CONFIG_ARCH_STDARG_H is not set > > CONFIG_ARCH_HAVE_SETJMP=y > > # CONFIG_ARCH_SETJMP_H is not set > > # CONFIG_ARCH_DEBUG_H is not set > > > > # > > # Debug Options > > # > > CONFIG_DEBUG_ALERT=y > > CONFIG_DEBUG_FEATURES=y > > > > # > > # Debug SYSLOG Output Controls > > # > > CONFIG_DEBUG_ERROR=y > > CONFIG_DEBUG_WARN=y > > CONFIG_DEBUG_INFO=y > > # CONFIG_DEBUG_ASSERTIONS is not set > > > > # > > # Subsystem Debug Options > > # > > # CONFIG_DEBUG_BINFMT is not set > > # CONFIG_DEBUG_FS is not set > > # CONFIG_DEBUG_GRAPHICS is not set > > # CONFIG_DEBUG_LIB is not set > > CONFIG_DEBUG_MM=y > > CONFIG_DEBUG_MM_ERROR=y > > # CONFIG_DEBUG_MM_WARN is not set > > # CONFIG_DEBUG_MM_INFO is not set > > # CONFIG_DEBUG_POWER is not set > > # CONFIG_DEBUG_SCHED is not set > > > > # > > # OS Function Debug Options > > # > > # CONFIG_DEBUG_IRQ is not set > > > > # > > # Driver Debug Options > > # > > CONFIG_DEBUG_ANALOG=y > > CONFIG_DEBUG_ANALOG_ERROR=y > > CONFIG_DEBUG_ANALOG_WARN=y > > # CONFIG_DEBUG_ANALOG_INFO is not set > > CONFIG_DEBUG_CAN=y > > CONFIG_DEBUG_CAN_ERROR=y > > CONFIG_DEBUG_CAN_WARN=y > > # CONFIG_DEBUG_CAN_INFO is not set > > CONFIG_DEBUG_GPIO=y > > CONFIG_DEBUG_GPIO_ERROR=y > > CONFIG_DEBUG_GPIO_WARN=y > > # CONFIG_DEBUG_GPIO_INFO is not set > > # CONFIG_DEBUG_I2C is not set > > # CONFIG_DEBUG_SPI is not set > > CONFIG_DEBUG_TIMER=y > > CONFIG_DEBUG_TIMER_ERROR=y > > CONFIG_DEBUG_TIMER_WARN=y > > # CONFIG_DEBUG_TIMER_INFO is not set > > CONFIG_ARCH_HAVE_STACKCHECK=y > > # CONFIG_STACK_COLORATION is not set > > CONFIG_ARCH_HAVE_HEAPCHECK=y > > # CONFIG_HEAP_COLORATION is not set > > CONFIG_DEBUG_SYMBOLS=y > > CONFIG_ARCH_HAVE_CUSTOMOPT=y > > # CONFIG_DEBUG_NOOPT is not set > > #
Re: NSH Not Responding to Commands Over Serial on STM32F446RET
For what it's worth: I had issues using ST-Link and serial with a Nucleo board for that MCU. I luckily had two boards and found that one worked and one didn't. From the list archive: I say was, because I eventually did gain access. It turns out that I have two different kinds of nucleo boards but only one variant works. The main boards are all MB1136 Rev C (STM32F446RE), but the ST-Link attached to the boards is different. The ones that do not work say 1940 on the BACK of the ST-Link, where as the ones I can connect with say IQE 1915 on the FRONT of the ST-Link. So it appears that the older revision of ST-Link works, where as the newer revision does not? On Fri, Dec 6, 2024 at 11:20 AM Russell Burgett wrote: > I am using NuttX on a STM32F446RET. > > I have the console enabled (serial) and am able to receive data from my > target, however NSH is not responding to commands sent over serial. > > I can execute commands from my nsh_romfsimg.h file, although cd fails with > code 2 and ls fails with the message "out of memory". > > Oddly when I run my own application and send commands to the console while > the app is running they appear to buffered, read and executed by NSH after > the app exits. > > running ps I get > PID PRI POLICY TYPENPX STATEEVENT SIGMASK STACK COMMAND > 0 0 FIFO Kthread N-- Ready 00 Idle Task > 1 224 FIFO Kthread --- Waiting Signal 002028 hpwork > 2 100 FIFO Kthread --- Waiting Signal 002028 lpwork > 3 100 FIFO Task--- Running 002028 init > > df . gives me > Block Number > Size Blocks Used Available Mounted on > 6444 0 /etc > 000 0 /proc > > Could anyone provide insights into why these issues might be occurring, > especially the "out of memory" error and the failure of NSH to execute > commands ? > > Thank you > > here is my .config file > # > # Automatically generated file; DO NOT EDIT. > # Nuttx/ Configuration > # > > # > # Build Setup > # > # CONFIG_EXPERIMENTAL is not set > # CONFIG_DEFAULT_SMALL is not set > CONFIG_HOST_LINUX=y > # CONFIG_HOST_MACOS is not set > # CONFIG_HOST_WINDOWS is not set > # CONFIG_HOST_OTHER is not set > > # > # Build Configuration > # > CONFIG_APPS_DIR="../apps" > CONFIG_BUILD_FLAT=y > # CONFIG_BUILD_2PASS is not set > > # > # Binary Output Formats > # > # CONFIG_RRLOAD_BINARY is not set > # CONFIG_CXD56_BINARY is not set > CONFIG_INTELHEX_BINARY=y > # CONFIG_MOTOROLA_SREC is not set > CONFIG_RAW_BINARY=y > # CONFIG_UBOOT_UIMAGE is not set > # CONFIG_DFU_BINARY is not set > > # > # Customize Header Files > # > # CONFIG_ARCH_HAVE_STDINT_H is not set > # CONFIG_ARCH_HAVE_STDBOOL_H is not set > # CONFIG_ARCH_HAVE_MATH_H is not set > CONFIG_ARCH_FLOAT_H=y > CONFIG_ARCH_HAVE_STDARG_H=y > # CONFIG_ARCH_STDARG_H is not set > CONFIG_ARCH_HAVE_SETJMP=y > # CONFIG_ARCH_SETJMP_H is not set > # CONFIG_ARCH_DEBUG_H is not set > > # > # Debug Options > # > CONFIG_DEBUG_ALERT=y > CONFIG_DEBUG_FEATURES=y > > # > # Debug SYSLOG Output Controls > # > CONFIG_DEBUG_ERROR=y > CONFIG_DEBUG_WARN=y > CONFIG_DEBUG_INFO=y > # CONFIG_DEBUG_ASSERTIONS is not set > > # > # Subsystem Debug Options > # > # CONFIG_DEBUG_BINFMT is not set > # CONFIG_DEBUG_FS is not set > # CONFIG_DEBUG_GRAPHICS is not set > # CONFIG_DEBUG_LIB is not set > CONFIG_DEBUG_MM=y > CONFIG_DEBUG_MM_ERROR=y > # CONFIG_DEBUG_MM_WARN is not set > # CONFIG_DEBUG_MM_INFO is not set > # CONFIG_DEBUG_POWER is not set > # CONFIG_DEBUG_SCHED is not set > > # > # OS Function Debug Options > # > # CONFIG_DEBUG_IRQ is not set > > # > # Driver Debug Options > # > CONFIG_DEBUG_ANALOG=y > CONFIG_DEBUG_ANALOG_ERROR=y > CONFIG_DEBUG_ANALOG_WARN=y > # CONFIG_DEBUG_ANALOG_INFO is not set > CONFIG_DEBUG_CAN=y > CONFIG_DEBUG_CAN_ERROR=y > CONFIG_DEBUG_CAN_WARN=y > # CONFIG_DEBUG_CAN_INFO is not set > CONFIG_DEBUG_GPIO=y > CONFIG_DEBUG_GPIO_ERROR=y > CONFIG_DEBUG_GPIO_WARN=y > # CONFIG_DEBUG_GPIO_INFO is not set > # CONFIG_DEBUG_I2C is not set > # CONFIG_DEBUG_SPI is not set > CONFIG_DEBUG_TIMER=y > CONFIG_DEBUG_TIMER_ERROR=y > CONFIG_DEBUG_TIMER_WARN=y > # CONFIG_DEBUG_TIMER_INFO is not set > CONFIG_ARCH_HAVE_STACKCHECK=y > # CONFIG_STACK_COLORATION is not set > CONFIG_ARCH_HAVE_HEAPCHECK=y > # CONFIG_HEAP_COLORATION is not set > CONFIG_DEBUG_SYMBOLS=y > CONFIG_ARCH_HAVE_CUSTOMOPT=y > # CONFIG_DEBUG_NOOPT is not set > # CONFIG_DEBUG_CUSTOMOPT is not set > CONFIG_DEBUG_FULLOPT=y > > # > # System Type > # > CONFIG_ARCH_ARM=y > # CONFIG_ARCH_AVR is not set > # CONFIG_ARCH_HC is not set > # CONFIG_ARCH_MIPS is not set > # CONFIG_ARCH_MISOC is not set > # CONFIG_ARCH_RENESAS is not set > # CONFIG_ARCH_RISCV is not set > # CONFIG_ARCH_SIM is not set > # CONFIG_ARCH_X86 is not set > # CONFIG_ARCH_XTENSA is not set > # CONFIG_ARCH_Z16 is not set > # CONFIG_ARCH_Z80 is not set > # CONFIG_ARCH_OR1K is not set > CONFIG_ARCH="arm" > > # > # ARM Option
Re: NSH Not Responding to Commands Over Serial on STM32F446RET
Hi Russell, Thanks for confirming. In this case, you can try to start with the original nsh example that works and then start adding new features from the bad configuration, until you find the guilt. Another approach is using GDB to debug and see where it is blocking. This approach could be faster, but follow the previous suggestion you will learn more about the existing features and memory consume. BR, Alan On Mon, Dec 9, 2024 at 9:27 AM Russell Burgett wrote: > The nuttx example ran with no issues > > On Mon, Dec 9, 2024 at 7:26 AM Russell Burgett > wrote: > > > thanks Alan, > > I inherited the project from another developer and have been using his > > settings - will start turning things off > > right after I posted I built the Nuttx example for this board so I am > > going to use this as basis for my project > > russ > > > > On Fri, Dec 6, 2024 at 2:54 PM Alan C. Assis wrote: > > > >> Hi Russell, > >> > >> Question: if you use the original board nsh example, does it work? > >> > >> About the out of memory, please try to run the "free" command, it could > >> return the amount of free memory. > >> > >> I noticed you enabled many features (and debugging), also I noticed you > >> are > >> enabling cu terminal, but you have only a UART enabled, so it is using > >> /dev/ttyS0 that is also the /dev/console. > >> > >> I suppose you are not running it yet, but when you run it it could > >> interfere in your nsh> in a similar way you described. > >> > >> BR, > >> > >> Alan > >> > >> On Fri, Dec 6, 2024 at 4:21 PM Russell Burgett < > [email protected] > >> > > >> wrote: > >> > >> > I am using NuttX on a STM32F446RET. > >> > > >> > I have the console enabled (serial) and am able to receive data from > my > >> > target, however NSH is not responding to commands sent over serial. > >> > > >> > I can execute commands from my nsh_romfsimg.h file, although cd fails > >> with > >> > code 2 and ls fails with the message "out of memory". > >> > > >> > Oddly when I run my own application and send commands to the console > >> while > >> > the app is running they appear to buffered, read and executed by NSH > >> after > >> > the app exits. > >> > > >> > running ps I get > >> > PID PRI POLICY TYPENPX STATEEVENT SIGMASK STACK > >> COMMAND > >> > 0 0 FIFO Kthread N-- Ready 00 Idle > >> Task > >> > 1 224 FIFO Kthread --- Waiting Signal 002028 > hpwork > >> > 2 100 FIFO Kthread --- Waiting Signal 002028 > lpwork > >> > 3 100 FIFO Task--- Running 002028 init > >> > > >> > df . gives me > >> > Block Number > >> > Size Blocks Used Available Mounted on > >> > 6444 0 /etc > >> > 000 0 /proc > >> > > >> > Could anyone provide insights into why these issues might be > occurring, > >> > especially the "out of memory" error and the failure of NSH to execute > >> > commands ? > >> > > >> > Thank you > >> > > >> > here is my .config file > >> > # > >> > # Automatically generated file; DO NOT EDIT. > >> > # Nuttx/ Configuration > >> > # > >> > > >> > # > >> > # Build Setup > >> > # > >> > # CONFIG_EXPERIMENTAL is not set > >> > # CONFIG_DEFAULT_SMALL is not set > >> > CONFIG_HOST_LINUX=y > >> > # CONFIG_HOST_MACOS is not set > >> > # CONFIG_HOST_WINDOWS is not set > >> > # CONFIG_HOST_OTHER is not set > >> > > >> > # > >> > # Build Configuration > >> > # > >> > CONFIG_APPS_DIR="../apps" > >> > CONFIG_BUILD_FLAT=y > >> > # CONFIG_BUILD_2PASS is not set > >> > > >> > # > >> > # Binary Output Formats > >> > # > >> > # CONFIG_RRLOAD_BINARY is not set > >> > # CONFIG_CXD56_BINARY is not set > >> > CONFIG_INTELHEX_BINARY=y > >> > # CONFIG_MOTOROLA_SREC is not set > >> > CONFIG_RAW_BINARY=y > >> > # CONFIG_UBOOT_UIMAGE is not set > >> > # CONFIG_DFU_BINARY is not set > >> > > >> > # > >> > # Customize Header Files > >> > # > >> > # CONFIG_ARCH_HAVE_STDINT_H is not set > >> > # CONFIG_ARCH_HAVE_STDBOOL_H is not set > >> > # CONFIG_ARCH_HAVE_MATH_H is not set > >> > CONFIG_ARCH_FLOAT_H=y > >> > CONFIG_ARCH_HAVE_STDARG_H=y > >> > # CONFIG_ARCH_STDARG_H is not set > >> > CONFIG_ARCH_HAVE_SETJMP=y > >> > # CONFIG_ARCH_SETJMP_H is not set > >> > # CONFIG_ARCH_DEBUG_H is not set > >> > > >> > # > >> > # Debug Options > >> > # > >> > CONFIG_DEBUG_ALERT=y > >> > CONFIG_DEBUG_FEATURES=y > >> > > >> > # > >> > # Debug SYSLOG Output Controls > >> > # > >> > CONFIG_DEBUG_ERROR=y > >> > CONFIG_DEBUG_WARN=y > >> > CONFIG_DEBUG_INFO=y > >> > # CONFIG_DEBUG_ASSERTIONS is not set > >> > > >> > # > >> > # Subsystem Debug Options > >> > # > >> > # CONFIG_DEBUG_BINFMT is not set > >> > # CONFIG_DEBUG_FS is not set > >> > # CONFIG_DEBUG_GRAPHICS is not set > >> > # CONFIG_DEBUG_LIB is not set > >> > CONFIG_DEBUG_MM=y > >> > CONFIG_DEBUG_MM_ERROR=y > >> > # CONFIG_DEBUG_MM_WARN is not set > >> > # CONFIG_DEBUG_MM_INFO is not set > >> > # CONFIG_DEBUG_POWER is n
Re: NSH Not Responding to Commands Over Serial on STM32F446RET
The nuttx example ran with no issues On Mon, Dec 9, 2024 at 7:26 AM Russell Burgett wrote: > thanks Alan, > I inherited the project from another developer and have been using his > settings - will start turning things off > right after I posted I built the Nuttx example for this board so I am > going to use this as basis for my project > russ > > On Fri, Dec 6, 2024 at 2:54 PM Alan C. Assis wrote: > >> Hi Russell, >> >> Question: if you use the original board nsh example, does it work? >> >> About the out of memory, please try to run the "free" command, it could >> return the amount of free memory. >> >> I noticed you enabled many features (and debugging), also I noticed you >> are >> enabling cu terminal, but you have only a UART enabled, so it is using >> /dev/ttyS0 that is also the /dev/console. >> >> I suppose you are not running it yet, but when you run it it could >> interfere in your nsh> in a similar way you described. >> >> BR, >> >> Alan >> >> On Fri, Dec 6, 2024 at 4:21 PM Russell Burgett > > >> wrote: >> >> > I am using NuttX on a STM32F446RET. >> > >> > I have the console enabled (serial) and am able to receive data from my >> > target, however NSH is not responding to commands sent over serial. >> > >> > I can execute commands from my nsh_romfsimg.h file, although cd fails >> with >> > code 2 and ls fails with the message "out of memory". >> > >> > Oddly when I run my own application and send commands to the console >> while >> > the app is running they appear to buffered, read and executed by NSH >> after >> > the app exits. >> > >> > running ps I get >> > PID PRI POLICY TYPENPX STATEEVENT SIGMASK STACK >> COMMAND >> > 0 0 FIFO Kthread N-- Ready 00 Idle >> Task >> > 1 224 FIFO Kthread --- Waiting Signal 002028 hpwork >> > 2 100 FIFO Kthread --- Waiting Signal 002028 lpwork >> > 3 100 FIFO Task--- Running 002028 init >> > >> > df . gives me >> > Block Number >> > Size Blocks Used Available Mounted on >> > 6444 0 /etc >> > 000 0 /proc >> > >> > Could anyone provide insights into why these issues might be occurring, >> > especially the "out of memory" error and the failure of NSH to execute >> > commands ? >> > >> > Thank you >> > >> > here is my .config file >> > # >> > # Automatically generated file; DO NOT EDIT. >> > # Nuttx/ Configuration >> > # >> > >> > # >> > # Build Setup >> > # >> > # CONFIG_EXPERIMENTAL is not set >> > # CONFIG_DEFAULT_SMALL is not set >> > CONFIG_HOST_LINUX=y >> > # CONFIG_HOST_MACOS is not set >> > # CONFIG_HOST_WINDOWS is not set >> > # CONFIG_HOST_OTHER is not set >> > >> > # >> > # Build Configuration >> > # >> > CONFIG_APPS_DIR="../apps" >> > CONFIG_BUILD_FLAT=y >> > # CONFIG_BUILD_2PASS is not set >> > >> > # >> > # Binary Output Formats >> > # >> > # CONFIG_RRLOAD_BINARY is not set >> > # CONFIG_CXD56_BINARY is not set >> > CONFIG_INTELHEX_BINARY=y >> > # CONFIG_MOTOROLA_SREC is not set >> > CONFIG_RAW_BINARY=y >> > # CONFIG_UBOOT_UIMAGE is not set >> > # CONFIG_DFU_BINARY is not set >> > >> > # >> > # Customize Header Files >> > # >> > # CONFIG_ARCH_HAVE_STDINT_H is not set >> > # CONFIG_ARCH_HAVE_STDBOOL_H is not set >> > # CONFIG_ARCH_HAVE_MATH_H is not set >> > CONFIG_ARCH_FLOAT_H=y >> > CONFIG_ARCH_HAVE_STDARG_H=y >> > # CONFIG_ARCH_STDARG_H is not set >> > CONFIG_ARCH_HAVE_SETJMP=y >> > # CONFIG_ARCH_SETJMP_H is not set >> > # CONFIG_ARCH_DEBUG_H is not set >> > >> > # >> > # Debug Options >> > # >> > CONFIG_DEBUG_ALERT=y >> > CONFIG_DEBUG_FEATURES=y >> > >> > # >> > # Debug SYSLOG Output Controls >> > # >> > CONFIG_DEBUG_ERROR=y >> > CONFIG_DEBUG_WARN=y >> > CONFIG_DEBUG_INFO=y >> > # CONFIG_DEBUG_ASSERTIONS is not set >> > >> > # >> > # Subsystem Debug Options >> > # >> > # CONFIG_DEBUG_BINFMT is not set >> > # CONFIG_DEBUG_FS is not set >> > # CONFIG_DEBUG_GRAPHICS is not set >> > # CONFIG_DEBUG_LIB is not set >> > CONFIG_DEBUG_MM=y >> > CONFIG_DEBUG_MM_ERROR=y >> > # CONFIG_DEBUG_MM_WARN is not set >> > # CONFIG_DEBUG_MM_INFO is not set >> > # CONFIG_DEBUG_POWER is not set >> > # CONFIG_DEBUG_SCHED is not set >> > >> > # >> > # OS Function Debug Options >> > # >> > # CONFIG_DEBUG_IRQ is not set >> > >> > # >> > # Driver Debug Options >> > # >> > CONFIG_DEBUG_ANALOG=y >> > CONFIG_DEBUG_ANALOG_ERROR=y >> > CONFIG_DEBUG_ANALOG_WARN=y >> > # CONFIG_DEBUG_ANALOG_INFO is not set >> > CONFIG_DEBUG_CAN=y >> > CONFIG_DEBUG_CAN_ERROR=y >> > CONFIG_DEBUG_CAN_WARN=y >> > # CONFIG_DEBUG_CAN_INFO is not set >> > CONFIG_DEBUG_GPIO=y >> > CONFIG_DEBUG_GPIO_ERROR=y >> > CONFIG_DEBUG_GPIO_WARN=y >> > # CONFIG_DEBUG_GPIO_INFO is not set >> > # CONFIG_DEBUG_I2C is not set >> > # CONFIG_DEBUG_SPI is not set >> > CONFIG_DEBUG_TIMER=y >> > CONFIG_DEBUG_TIMER_ERROR=y >> > CONFIG_DEBUG_TIMER_WARN=y >> > # CONFIG_DEBUG_TIMER_INFO is not set >> > CONFIG_ARCH_HAVE_STACKCHECK=y >> >
Re: NSH Not Responding to Commands Over Serial on STM32F446RET
thanks Alan, I inherited the project from another developer and have been using his settings - will start turning things off right after I posted I built the Nuttx example for this board so I am going to use this as basis for my project russ On Fri, Dec 6, 2024 at 2:54 PM Alan C. Assis wrote: > Hi Russell, > > Question: if you use the original board nsh example, does it work? > > About the out of memory, please try to run the "free" command, it could > return the amount of free memory. > > I noticed you enabled many features (and debugging), also I noticed you are > enabling cu terminal, but you have only a UART enabled, so it is using > /dev/ttyS0 that is also the /dev/console. > > I suppose you are not running it yet, but when you run it it could > interfere in your nsh> in a similar way you described. > > BR, > > Alan > > On Fri, Dec 6, 2024 at 4:21 PM Russell Burgett > wrote: > > > I am using NuttX on a STM32F446RET. > > > > I have the console enabled (serial) and am able to receive data from my > > target, however NSH is not responding to commands sent over serial. > > > > I can execute commands from my nsh_romfsimg.h file, although cd fails > with > > code 2 and ls fails with the message "out of memory". > > > > Oddly when I run my own application and send commands to the console > while > > the app is running they appear to buffered, read and executed by NSH > after > > the app exits. > > > > running ps I get > > PID PRI POLICY TYPENPX STATEEVENT SIGMASK STACK COMMAND > > 0 0 FIFO Kthread N-- Ready 00 Idle > Task > > 1 224 FIFO Kthread --- Waiting Signal 002028 hpwork > > 2 100 FIFO Kthread --- Waiting Signal 002028 lpwork > > 3 100 FIFO Task--- Running 002028 init > > > > df . gives me > > Block Number > > Size Blocks Used Available Mounted on > > 6444 0 /etc > > 000 0 /proc > > > > Could anyone provide insights into why these issues might be occurring, > > especially the "out of memory" error and the failure of NSH to execute > > commands ? > > > > Thank you > > > > here is my .config file > > # > > # Automatically generated file; DO NOT EDIT. > > # Nuttx/ Configuration > > # > > > > # > > # Build Setup > > # > > # CONFIG_EXPERIMENTAL is not set > > # CONFIG_DEFAULT_SMALL is not set > > CONFIG_HOST_LINUX=y > > # CONFIG_HOST_MACOS is not set > > # CONFIG_HOST_WINDOWS is not set > > # CONFIG_HOST_OTHER is not set > > > > # > > # Build Configuration > > # > > CONFIG_APPS_DIR="../apps" > > CONFIG_BUILD_FLAT=y > > # CONFIG_BUILD_2PASS is not set > > > > # > > # Binary Output Formats > > # > > # CONFIG_RRLOAD_BINARY is not set > > # CONFIG_CXD56_BINARY is not set > > CONFIG_INTELHEX_BINARY=y > > # CONFIG_MOTOROLA_SREC is not set > > CONFIG_RAW_BINARY=y > > # CONFIG_UBOOT_UIMAGE is not set > > # CONFIG_DFU_BINARY is not set > > > > # > > # Customize Header Files > > # > > # CONFIG_ARCH_HAVE_STDINT_H is not set > > # CONFIG_ARCH_HAVE_STDBOOL_H is not set > > # CONFIG_ARCH_HAVE_MATH_H is not set > > CONFIG_ARCH_FLOAT_H=y > > CONFIG_ARCH_HAVE_STDARG_H=y > > # CONFIG_ARCH_STDARG_H is not set > > CONFIG_ARCH_HAVE_SETJMP=y > > # CONFIG_ARCH_SETJMP_H is not set > > # CONFIG_ARCH_DEBUG_H is not set > > > > # > > # Debug Options > > # > > CONFIG_DEBUG_ALERT=y > > CONFIG_DEBUG_FEATURES=y > > > > # > > # Debug SYSLOG Output Controls > > # > > CONFIG_DEBUG_ERROR=y > > CONFIG_DEBUG_WARN=y > > CONFIG_DEBUG_INFO=y > > # CONFIG_DEBUG_ASSERTIONS is not set > > > > # > > # Subsystem Debug Options > > # > > # CONFIG_DEBUG_BINFMT is not set > > # CONFIG_DEBUG_FS is not set > > # CONFIG_DEBUG_GRAPHICS is not set > > # CONFIG_DEBUG_LIB is not set > > CONFIG_DEBUG_MM=y > > CONFIG_DEBUG_MM_ERROR=y > > # CONFIG_DEBUG_MM_WARN is not set > > # CONFIG_DEBUG_MM_INFO is not set > > # CONFIG_DEBUG_POWER is not set > > # CONFIG_DEBUG_SCHED is not set > > > > # > > # OS Function Debug Options > > # > > # CONFIG_DEBUG_IRQ is not set > > > > # > > # Driver Debug Options > > # > > CONFIG_DEBUG_ANALOG=y > > CONFIG_DEBUG_ANALOG_ERROR=y > > CONFIG_DEBUG_ANALOG_WARN=y > > # CONFIG_DEBUG_ANALOG_INFO is not set > > CONFIG_DEBUG_CAN=y > > CONFIG_DEBUG_CAN_ERROR=y > > CONFIG_DEBUG_CAN_WARN=y > > # CONFIG_DEBUG_CAN_INFO is not set > > CONFIG_DEBUG_GPIO=y > > CONFIG_DEBUG_GPIO_ERROR=y > > CONFIG_DEBUG_GPIO_WARN=y > > # CONFIG_DEBUG_GPIO_INFO is not set > > # CONFIG_DEBUG_I2C is not set > > # CONFIG_DEBUG_SPI is not set > > CONFIG_DEBUG_TIMER=y > > CONFIG_DEBUG_TIMER_ERROR=y > > CONFIG_DEBUG_TIMER_WARN=y > > # CONFIG_DEBUG_TIMER_INFO is not set > > CONFIG_ARCH_HAVE_STACKCHECK=y > > # CONFIG_STACK_COLORATION is not set > > CONFIG_ARCH_HAVE_HEAPCHECK=y > > # CONFIG_HEAP_COLORATION is not set > > CONFIG_DEBUG_SYMBOLS=y > > CONFIG_ARCH_HAVE_CUSTOMOPT=y > > # CONFIG_DEBUG_NOOPT is not set > > # CONFIG_DEBUG_CUSTOMOPT is not set > > CONFIG_DEBUG_FULLOPT=y > >
Re: NSH Not Responding to Commands Over Serial on STM32F446RET
Hi Russell, Question: if you use the original board nsh example, does it work? About the out of memory, please try to run the "free" command, it could return the amount of free memory. I noticed you enabled many features (and debugging), also I noticed you are enabling cu terminal, but you have only a UART enabled, so it is using /dev/ttyS0 that is also the /dev/console. I suppose you are not running it yet, but when you run it it could interfere in your nsh> in a similar way you described. BR, Alan On Fri, Dec 6, 2024 at 4:21 PM Russell Burgett wrote: > I am using NuttX on a STM32F446RET. > > I have the console enabled (serial) and am able to receive data from my > target, however NSH is not responding to commands sent over serial. > > I can execute commands from my nsh_romfsimg.h file, although cd fails with > code 2 and ls fails with the message "out of memory". > > Oddly when I run my own application and send commands to the console while > the app is running they appear to buffered, read and executed by NSH after > the app exits. > > running ps I get > PID PRI POLICY TYPENPX STATEEVENT SIGMASK STACK COMMAND > 0 0 FIFO Kthread N-- Ready 00 Idle Task > 1 224 FIFO Kthread --- Waiting Signal 002028 hpwork > 2 100 FIFO Kthread --- Waiting Signal 002028 lpwork > 3 100 FIFO Task--- Running 002028 init > > df . gives me > Block Number > Size Blocks Used Available Mounted on > 6444 0 /etc > 000 0 /proc > > Could anyone provide insights into why these issues might be occurring, > especially the "out of memory" error and the failure of NSH to execute > commands ? > > Thank you > > here is my .config file > # > # Automatically generated file; DO NOT EDIT. > # Nuttx/ Configuration > # > > # > # Build Setup > # > # CONFIG_EXPERIMENTAL is not set > # CONFIG_DEFAULT_SMALL is not set > CONFIG_HOST_LINUX=y > # CONFIG_HOST_MACOS is not set > # CONFIG_HOST_WINDOWS is not set > # CONFIG_HOST_OTHER is not set > > # > # Build Configuration > # > CONFIG_APPS_DIR="../apps" > CONFIG_BUILD_FLAT=y > # CONFIG_BUILD_2PASS is not set > > # > # Binary Output Formats > # > # CONFIG_RRLOAD_BINARY is not set > # CONFIG_CXD56_BINARY is not set > CONFIG_INTELHEX_BINARY=y > # CONFIG_MOTOROLA_SREC is not set > CONFIG_RAW_BINARY=y > # CONFIG_UBOOT_UIMAGE is not set > # CONFIG_DFU_BINARY is not set > > # > # Customize Header Files > # > # CONFIG_ARCH_HAVE_STDINT_H is not set > # CONFIG_ARCH_HAVE_STDBOOL_H is not set > # CONFIG_ARCH_HAVE_MATH_H is not set > CONFIG_ARCH_FLOAT_H=y > CONFIG_ARCH_HAVE_STDARG_H=y > # CONFIG_ARCH_STDARG_H is not set > CONFIG_ARCH_HAVE_SETJMP=y > # CONFIG_ARCH_SETJMP_H is not set > # CONFIG_ARCH_DEBUG_H is not set > > # > # Debug Options > # > CONFIG_DEBUG_ALERT=y > CONFIG_DEBUG_FEATURES=y > > # > # Debug SYSLOG Output Controls > # > CONFIG_DEBUG_ERROR=y > CONFIG_DEBUG_WARN=y > CONFIG_DEBUG_INFO=y > # CONFIG_DEBUG_ASSERTIONS is not set > > # > # Subsystem Debug Options > # > # CONFIG_DEBUG_BINFMT is not set > # CONFIG_DEBUG_FS is not set > # CONFIG_DEBUG_GRAPHICS is not set > # CONFIG_DEBUG_LIB is not set > CONFIG_DEBUG_MM=y > CONFIG_DEBUG_MM_ERROR=y > # CONFIG_DEBUG_MM_WARN is not set > # CONFIG_DEBUG_MM_INFO is not set > # CONFIG_DEBUG_POWER is not set > # CONFIG_DEBUG_SCHED is not set > > # > # OS Function Debug Options > # > # CONFIG_DEBUG_IRQ is not set > > # > # Driver Debug Options > # > CONFIG_DEBUG_ANALOG=y > CONFIG_DEBUG_ANALOG_ERROR=y > CONFIG_DEBUG_ANALOG_WARN=y > # CONFIG_DEBUG_ANALOG_INFO is not set > CONFIG_DEBUG_CAN=y > CONFIG_DEBUG_CAN_ERROR=y > CONFIG_DEBUG_CAN_WARN=y > # CONFIG_DEBUG_CAN_INFO is not set > CONFIG_DEBUG_GPIO=y > CONFIG_DEBUG_GPIO_ERROR=y > CONFIG_DEBUG_GPIO_WARN=y > # CONFIG_DEBUG_GPIO_INFO is not set > # CONFIG_DEBUG_I2C is not set > # CONFIG_DEBUG_SPI is not set > CONFIG_DEBUG_TIMER=y > CONFIG_DEBUG_TIMER_ERROR=y > CONFIG_DEBUG_TIMER_WARN=y > # CONFIG_DEBUG_TIMER_INFO is not set > CONFIG_ARCH_HAVE_STACKCHECK=y > # CONFIG_STACK_COLORATION is not set > CONFIG_ARCH_HAVE_HEAPCHECK=y > # CONFIG_HEAP_COLORATION is not set > CONFIG_DEBUG_SYMBOLS=y > CONFIG_ARCH_HAVE_CUSTOMOPT=y > # CONFIG_DEBUG_NOOPT is not set > # CONFIG_DEBUG_CUSTOMOPT is not set > CONFIG_DEBUG_FULLOPT=y > > # > # System Type > # > CONFIG_ARCH_ARM=y > # CONFIG_ARCH_AVR is not set > # CONFIG_ARCH_HC is not set > # CONFIG_ARCH_MIPS is not set > # CONFIG_ARCH_MISOC is not set > # CONFIG_ARCH_RENESAS is not set > # CONFIG_ARCH_RISCV is not set > # CONFIG_ARCH_SIM is not set > # CONFIG_ARCH_X86 is not set > # CONFIG_ARCH_XTENSA is not set > # CONFIG_ARCH_Z16 is not set > # CONFIG_ARCH_Z80 is not set > # CONFIG_ARCH_OR1K is not set > CONFIG_ARCH="arm" > > # > # ARM Options > # > # CONFIG_ARCH_CHIP_A1X is not set > # CONFIG_ARCH_CHIP_AM335X is not set > # CONFIG_ARCH_CHIP_C5471 is not set > # CONFIG_ARCH_CHIP_DM320 is not se
NSH Not Responding to Commands Over Serial on STM32F446RET
I am using NuttX on a STM32F446RET. I have the console enabled (serial) and am able to receive data from my target, however NSH is not responding to commands sent over serial. I can execute commands from my nsh_romfsimg.h file, although cd fails with code 2 and ls fails with the message "out of memory". Oddly when I run my own application and send commands to the console while the app is running they appear to buffered, read and executed by NSH after the app exits. running ps I get PID PRI POLICY TYPENPX STATEEVENT SIGMASK STACK COMMAND 0 0 FIFO Kthread N-- Ready 00 Idle Task 1 224 FIFO Kthread --- Waiting Signal 002028 hpwork 2 100 FIFO Kthread --- Waiting Signal 002028 lpwork 3 100 FIFO Task--- Running 002028 init df . gives me Block Number Size Blocks Used Available Mounted on 6444 0 /etc 000 0 /proc Could anyone provide insights into why these issues might be occurring, especially the "out of memory" error and the failure of NSH to execute commands ? Thank you here is my .config file # # Automatically generated file; DO NOT EDIT. # Nuttx/ Configuration # # # Build Setup # # CONFIG_EXPERIMENTAL is not set # CONFIG_DEFAULT_SMALL is not set CONFIG_HOST_LINUX=y # CONFIG_HOST_MACOS is not set # CONFIG_HOST_WINDOWS is not set # CONFIG_HOST_OTHER is not set # # Build Configuration # CONFIG_APPS_DIR="../apps" CONFIG_BUILD_FLAT=y # CONFIG_BUILD_2PASS is not set # # Binary Output Formats # # CONFIG_RRLOAD_BINARY is not set # CONFIG_CXD56_BINARY is not set CONFIG_INTELHEX_BINARY=y # CONFIG_MOTOROLA_SREC is not set CONFIG_RAW_BINARY=y # CONFIG_UBOOT_UIMAGE is not set # CONFIG_DFU_BINARY is not set # # Customize Header Files # # CONFIG_ARCH_HAVE_STDINT_H is not set # CONFIG_ARCH_HAVE_STDBOOL_H is not set # CONFIG_ARCH_HAVE_MATH_H is not set CONFIG_ARCH_FLOAT_H=y CONFIG_ARCH_HAVE_STDARG_H=y # CONFIG_ARCH_STDARG_H is not set CONFIG_ARCH_HAVE_SETJMP=y # CONFIG_ARCH_SETJMP_H is not set # CONFIG_ARCH_DEBUG_H is not set # # Debug Options # CONFIG_DEBUG_ALERT=y CONFIG_DEBUG_FEATURES=y # # Debug SYSLOG Output Controls # CONFIG_DEBUG_ERROR=y CONFIG_DEBUG_WARN=y CONFIG_DEBUG_INFO=y # CONFIG_DEBUG_ASSERTIONS is not set # # Subsystem Debug Options # # CONFIG_DEBUG_BINFMT is not set # CONFIG_DEBUG_FS is not set # CONFIG_DEBUG_GRAPHICS is not set # CONFIG_DEBUG_LIB is not set CONFIG_DEBUG_MM=y CONFIG_DEBUG_MM_ERROR=y # CONFIG_DEBUG_MM_WARN is not set # CONFIG_DEBUG_MM_INFO is not set # CONFIG_DEBUG_POWER is not set # CONFIG_DEBUG_SCHED is not set # # OS Function Debug Options # # CONFIG_DEBUG_IRQ is not set # # Driver Debug Options # CONFIG_DEBUG_ANALOG=y CONFIG_DEBUG_ANALOG_ERROR=y CONFIG_DEBUG_ANALOG_WARN=y # CONFIG_DEBUG_ANALOG_INFO is not set CONFIG_DEBUG_CAN=y CONFIG_DEBUG_CAN_ERROR=y CONFIG_DEBUG_CAN_WARN=y # CONFIG_DEBUG_CAN_INFO is not set CONFIG_DEBUG_GPIO=y CONFIG_DEBUG_GPIO_ERROR=y CONFIG_DEBUG_GPIO_WARN=y # CONFIG_DEBUG_GPIO_INFO is not set # CONFIG_DEBUG_I2C is not set # CONFIG_DEBUG_SPI is not set CONFIG_DEBUG_TIMER=y CONFIG_DEBUG_TIMER_ERROR=y CONFIG_DEBUG_TIMER_WARN=y # CONFIG_DEBUG_TIMER_INFO is not set CONFIG_ARCH_HAVE_STACKCHECK=y # CONFIG_STACK_COLORATION is not set CONFIG_ARCH_HAVE_HEAPCHECK=y # CONFIG_HEAP_COLORATION is not set CONFIG_DEBUG_SYMBOLS=y CONFIG_ARCH_HAVE_CUSTOMOPT=y # CONFIG_DEBUG_NOOPT is not set # CONFIG_DEBUG_CUSTOMOPT is not set CONFIG_DEBUG_FULLOPT=y # # System Type # CONFIG_ARCH_ARM=y # CONFIG_ARCH_AVR is not set # CONFIG_ARCH_HC is not set # CONFIG_ARCH_MIPS is not set # CONFIG_ARCH_MISOC is not set # CONFIG_ARCH_RENESAS is not set # CONFIG_ARCH_RISCV is not set # CONFIG_ARCH_SIM is not set # CONFIG_ARCH_X86 is not set # CONFIG_ARCH_XTENSA is not set # CONFIG_ARCH_Z16 is not set # CONFIG_ARCH_Z80 is not set # CONFIG_ARCH_OR1K is not set CONFIG_ARCH="arm" # # ARM Options # # CONFIG_ARCH_CHIP_A1X is not set # CONFIG_ARCH_CHIP_AM335X is not set # CONFIG_ARCH_CHIP_C5471 is not set # CONFIG_ARCH_CHIP_DM320 is not set # CONFIG_ARCH_CHIP_EFM32 is not set # CONFIG_ARCH_CHIP_IMX1 is not set # CONFIG_ARCH_CHIP_IMX6 is not set # CONFIG_ARCH_CHIP_IMXRT is not set # CONFIG_ARCH_CHIP_KINETIS is not set # CONFIG_ARCH_CHIP_KL is not set # CONFIG_ARCH_CHIP_LC823450 is not set # CONFIG_ARCH_CHIP_LM is not set # CONFIG_ARCH_CHIP_LPC17XX_40XX is not set # CONFIG_ARCH_CHIP_LPC214X is not set # CONFIG_ARCH_CHIP_LPC2378 is not set # CONFIG_ARCH_CHIP_LPC31XX is not set # CONFIG_ARCH_CHIP_LPC43XX is not set # CONFIG_ARCH_CHIP_LPC54XX is not set # CONFIG_ARCH_CHIP_MAX326XX is not set # CONFIG_ARCH_CHIP_MOXART is not set # CONFIG_ARCH_CHIP_NRF52 is not set # CONFIG_ARCH_CHIP_NUC1XX is not set # CONFIG_ARCH_CHIP_S32K1XX is not set # CONFIG_ARCH_CHIP_SAMA5 is not set # CONFIG_ARCH_CHIP_SAMD2X is not set # CONFIG_ARCH_CHIP_SAML2X is not set # CONFIG_ARCH_CHIP_SAMD5X is not set # CONFIG_ARCH_CHIP_SAME5X is
