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
