Re: Problem with running nuttx on imxrt1020

On 2025-02-17 08:48:28, Simin Feng (CW) wrote: > dump_assert_info: Assertion failed panic: at file: :0 task: Idle_Task > process: Kernel 0x600031dd Seems like you need to enable debug as there is file and line missing from log. Enable debug symbols and more debug prints, also canaries for stac

Problem with running nuttx on imxrt1020

Hello, I am attempting to runing nuttx on NXP imxrt1020 board. I have downloaded the latest version from the https://nuttx.apache.org/ and follow the getting started steps: 1../tools/configure.sh imxrt1020-evk:nsh 2.make menuconfig 3.make However, After I flashed the nuttx.hex with J-Link into

Re: [VOTE] NuttX Contributing Guidelines update 202502.

Hi! Thanks, Tomek, for summarizing it. I liked Nathan's proposal. Instead of simply increasing the number of reviewers from 2 to 4, we can adopt tags (we can even evaluate if the bot can do it automatically), and, based on such categories, we have new requirements for the reviewers. Considering

Re: ESP32C3 Using UART1 in RS485 mode with HW flowcontrol

Hi Erik, Would you mind opening an issue at https://github.com/apache/nuttx/issues? It isn't clear which SoC you are testing, but it seems to be a RISC-V-based Espressif SoC (ESP32-C3, perhaps). For ESP32-C3, we have two implementations: a legacy

Re: FB console/terminal

Just thinking out loud... Would NuttX benefit from a FrameBuffer stdout driver (e.g. /dev/fbcon) that allowed a pipe/dup to replace stdout, or the use of CONFIG_NSH_ALTSTDOUT and/or CONFIG_ALTSTDERR for console output? In my case, this is just for MCUboot messages in the case of bootloader i

ESP32C3 Using UART1 in RS485 mode with HW flowcontrol

While kiddo is home from school with a fever, I thought i would give NuttX a go again, living mostly in the Zephyr-world for the past years. Great job starting to implement cmake buildsystem, as keeping out-of-tree build directories greatly reduces the cases where you need to reclone the entire pro

Re: FB console/terminal

Yes that would be a nice feature also for testing the LCD and should be easy to implement for output only mode when no input is required :-) Input would require serial port like transport, keyboard, or on-screen keyboard that makes things a bit more complicated :-) Tomek On Mon, Feb 17, 2025 at 8:

Re: FB console/terminal

Hi Tim, Actually that could be a great idea! Maybe even the debug and initialization message from syslog could be printed to this fbcon interface. BR, Alan On Mon, Feb 17, 2025 at 4:11 PM Tim Hardisty wrote: > Just thinking out loud... > > Would NuttX benefit from a FrameBuffer stdout driver

Re: FB console/terminal

Input could be usb keyboard, otherwise the lvgl terminal app with its lvgl keyboard works. Output only mode for this I think. > On 17 Feb 2025, at 21:25, Tomek CEDRO wrote: > > Yes that would be a nice feature also for testing the LCD and should > be easy to implement for output only mode when

Re: [VOTE] NuttX Contributing Guidelines update 202502.

On Mon, Feb 17, 2025 at 12:20 PM Tiago Medicci Serrano wrote: > Hi! > Thanks, Tomek, for summarizing it. > > I liked Nathan's proposal. Instead of simply increasing the number of > reviewers from 2 to 4, we can adopt tags (we can even evaluate if the bot > can do it automatically), and, based on s