Hi Tim, there is already an open issue about it:
https://github.com/apache/nuttx/issues/11390
Please take a look at that discussion, POSIX SIGNALS are still required for
PSE51, but for NXBoot it could be disabled as well.
BR,
Alan
On Tue, Mar 25, 2025 at 6:47 AM Tim Hardisty
wrote:
> I think
On Fri, Mar 28, 2025 at 10:13 AM Alan C. Assis wrote:
> Hi Nathan,
>
> It could be just:
>
> default y if LCD_FRAMEBUFFER
>
> This way it will be "ON" for boards with LCD and Framebuffer enabled and
> "OFF" for all other boards.
That is a good combination. If there's a framebuffer there's a sp
Out of interest, I took a 800x480 png (that I currently use as a
splashscreen):
* png size: 56KiB
* C file, using LVGL image converter: 5.4MiB
Eek!
On 28/03/2025 13:06, Nathan Hartman wrote:
Replying inline below:
On Thu, Mar 27, 2025 at 5:15 PM Tim Hardisty
wrote:
Hi Nathan,
Thanks for
Hi Nathan,
It could be just:
default y if LCD_FRAMEBUFFER
This way it will be "ON" for boards with LCD and Framebuffer enabled and
"OFF" for all other boards.
Maybe we need to think about how to get NXlogo working for LCD_DEV too.
BR,
Alan
On Fri, Mar 28, 2025 at 10:07 AM Nathan Hartman
wro
Replying inline below:
On Thu, Mar 27, 2025 at 5:15 PM Tim Hardisty
wrote:
> Hi Nathan,
>
> Thanks for your thoughts. It has made me think more logically (I hope)
> about why and when you might want a splashscreen.
>
> I'm currently thinking that it is only a pretty "hello world" that
> allows
Hello Tim,
On Friday 28 of March 2025 11:22:06 Tim Hardisty wrote:
> Pavel - I have been thinking about your point regarding copying the
> (simple) nxboot_main and using it as a starting point for a more
> sophisticated application. What *I* want is probably not want *others*
> want and it could g
Pavel - I have been thinking about your point regarding copying the
(simple) nxboot_main and using it as a starting point for a more
sophisticated application. What *I* want is probably not want *others*
want and it could grow out of hand.
Let's leave it as is...so it covers the stdout/stderr/
Hi Nathan,
Thanks for your thoughts. It has made me think more logically (I hope)
about why and when you might want a splashscreen.
I'm currently thinking that it is only a pretty "hello world" that
allows branding. With that in mind:
* Embedded devices, using NuttX, may not have an LCD of
Thanks for joining in the conversation Pavel.
I currently have my INIT_ENTRYPOINT set to the (new) fbcon
example app, so any stdout and stderr output appear on the
framebuffer LCD, and that then calls NXboot to load my app
from flash etc.
I want a splashscreen for, let's say, marketing/branding
Hello Tim and Alan,
I think that splash screen should be separate component/
application in the NuttX Apps.
In the fact, for bigger system and more complex boot
process you can use NSH and script calling some
spash application which can setup frame buffer
and then register listener to the system
On Thu, Mar 27, 2025 at 9:18 AM Alan C. Assis wrote:
> Hi Tim,
>
> Yes, maybe it could be an option inside your fbcon app.
>
> My initial thought was that having a nxlogo inside the kernel (like Linux)
> could make it available for all boards that register a framebuffer.
If nxlogo is in the ker
Hmm, ok I was thinking it would be done after registering the frame buffer but
could be as part of registration of course. Doh!
I’ll look again :-)
Regards,
Tim.
> On 27 Mar 2025, at 13:18, Alan C. Assis wrote:
>
> Hi Tim,
>
> Yes, maybe it could be an option inside your fbcon app.
>
> My
I am still unsure about where a framebuffer splashscreen best "lives".
* If a framebuffer device is used for a given board, this would be
registered in a board bringup file. Or, at least, that's what my
board does. So a splashscreen could be done there - but is then not
a "generic" thin
Hi Tim,
Yes, maybe it could be an option inside your fbcon app.
My initial thought was that having a nxlogo inside the kernel (like Linux)
could make it available for all boards that register a framebuffer.
But since using your fbcon with the NSH terminal on LCD, the users will see
the NuttX Log
I think I’ll leave that for someone with more experience… and time! This could
be raised as a specific issue on GitHub if someone could take the time to do
that and capture the details?
I can do quick win fixes as they benefit me and hopefully others too :-)
Regards,
Tim.
> On 25 Mar 2025, at
Hello,
I agree that for compacity, reintroducing the possibility to disable the
VFS entirely would be quite interesting.
That is a large challenge!
Sebastien
On 24/03/2025 20:38, Alan C. Assis wrote:
Hi Tim,
Yes, these suggestions make sense!
I think for NXBoot should be nice to have the
Hi Tim,
Yes, these suggestions make sense!
I think for NXBoot should be nice to have the option to disable features
that were used for minsh board profile:
#
# RTOS Features
#
CONFIG_DISABLE_SIGNALS=y
#
# Files and I/O
#
CONFIG_SDCLONE_DISABLE=y
CONFIG_NFILE_DESCRIPTORS=0
CONFIG_NFILE_STREAMS=0
I am just starting to use NXboot (having migrated from Uboot, then to
MCUboot, and finally settled on NXboot) and I'm wondering whether it
would benefit from some changes and/or enhancements now I've used all three.
Thoughts, observations, suggestions welcomed.
In no particular order:
1. Uboo
18 matches
Mail list logo
