ker which gives us ability to
develop those that are not hardware dependent (like UI app) on the PC but with
a real data from the board and for that we use Meson to build Linux version of
the app. It really depends on your use case.
> Thank you again for sharing this, it is very much appreciat
piled object files in the NuttX build.
Feel free to inspire yourself, comment our setup, or share your own.
With regards,
Karel Kočí
signature.asc
Description: PGP signature
On Wed 30 Apr 2025 03:45:36 PM , Tim Hardisty wrote:
> >> I think that this system already exists and is the syslog.
>
> I cannot find anywhere to configure NuttX syslog to send output to
> stdout or stderr...I am sure it is my inexperience but not being able to
> do is in part what drove m
opriate API changes so your application can
be implemented (such as passing pointer to the callback function to
nxboot_perform_update for progress reporting). That for example requires no
modification of the upstream code to introduce your fallback because you can add
it in the error handling branch of your own application. At least that was our
intended way to use NXBoot when we were designing it.
And I agree that suggestion to have board defined fallback is outside of the
scope for sure. It was just an idea.
Hopefully I helped,
Karel Kočí
signature.asc
Description: PGP signature
opriate API changes so your application can
be implemented (such as passing pointer to the callback function to
nxboot_perform_update for progress reporting). That for example requires no
modification of the upstream code to introduce your fallback because you can add
it in the error handling branch of your own application. At least that was our
intended way to use NXBoot when we were designing it.
And I agree that suggestion to have board defined fallback is outside of the
scope for sure. It was just an idea.
Hopefully I helped,
Karel Kočí
signature.asc
Description: PGP signature
gt; idea of this address being in the header, and added by the loader
> functions, using a Kconfig board-specific setting. Need to make sure it
> is backwards compatible though.
>
> On 29/04/2025 22:17, Tim Hardisty wrote:
> > I believe I am over-thinking this and genuinely appreciate y
On Tue 29 Apr 2025 08:45:11 PM , Tim Hardisty wrote:
>
> The structures are available in the apps space but not kernel space,
> unless you include a convoluted path to get from the board directory
> (out-of-tree in my case). I have been trying to include to my board
> stuff as I thought that's
to do so. 😇
With regards
Karel Kočí
The promised script (placed in tool directory in our projects). It is not ideal
but it works:
#!/usr/bin/env bash
set -eu
# We want to make sure that our board sources are formatted correctly
according
# the NuttX code style. At the same ti
Excerpts from Tim Hardisty's message of February 26, 2023 12:17 pm:
>
> On 25/02/2023, 11:47, "Karel Kočí" mailto:cyn...@email.cz>>
> wrote:
>
>>I would use union (that is host ordering) and to convert to specific ordering
>>you can use functions
Hi
I would use union (that is host ordering) and to convert to specific ordering
you can use functions like htobe32 (big endian) and htole32 (little endian),
those are available.
K.K.
Excerpts from Tim Hardisty's message of February 25, 2023 11:26 am:
> As is so often the case, I need to pack
Excerpts from Alan Carvalho de Assis's message of July 21, 2022 1:20 pm:
> Hi Karel,
>
> On Thursday, July 21, 2022, Karel Kočí wrote:
>
>> Hi
>>
>> Excerpts from Alan Carvalho de Assis's message of July 20, 2022 5:21 pm:
>> > Hi Karel,
Hi
Excerpts from Alan Carvalho de Assis's message of July 20, 2022 5:21 pm:
> Hi Karel,
>
> On 7/20/22, Karel Kočí wrote:
>> Hi
>>
>> I discovered that commit 664d45dcbace03a879017aa99566592be31f4308 broke LCD
>>
>> framebuffer (at least f
Excerpts from Nathan Hartman's message of July 20, 2022 4:32 pm:
> On Wed, Jul 20, 2022 at 10:24 AM Karel Kočí wrote:
>>
>> Sorry for the late response.. I was busy with life.
>>
>> No, NuttX's crc32 is returning 0x2DFD2D88!
>> My modified code with m
Sorry for the late response.. I was busy with life.
Excerpts from Alan Carvalho de Assis's message of July 15, 2022 7:36 pm:
> On 7/15/22, Karel Kočí wrote:
>> The impact might be pretty significant from my search and that is also why I
>>
>> rather discuss ins
t
to actuall API documentation in 'include/nuttx/lcd/lcd.h' 😡.
Thus, what do you think? Revert or propagation of the new behavior?
With regards
Karel Kočí
pgp7eajyGqGrL.pgp
Description: PGP signature
Excerpts from Nathan Hartman's message of July 15, 2022 6:47 pm:
> On Fri, Jul 15, 2022 at 12:45 PM Karel Kočí wrote:
>>
>> The impact might be pretty significant from my search and that is also why I
>> rather discuss instead of suggesting changes.
>>
>> T
ion is already used in many places on NuttX I don't
> know the impact of including the bitwise "~" to return the most common
> CRC32 value.
>
> BR,
>
> Alan
>
> On 7/15/22, Karel Kočí wrote:
>>
>> Excerpts from Nathan Hartman's message o
Excerpts from Nathan Hartman's message of July 15, 2022 2:59 pm:
> On Fri, Jul 15, 2022 at 8:10 AM Karel Kočí wrote:
>>
>> Hi
>>
>> I hit an issue with crc32 implementation in NuttX's LibC and it took me some
>> time to figure out that crc32 is
cept of not matching with common implementations. Either way this discrepancy
should be at least documented with suggestion to use `~crc32part(msg, msgsiz,
0x)`. What do you think?
With regards
Karel Kočí
pgp6TVLW_iARV.pgp
Description: PGP signature
Hi everyone
I am trying to port NuttX to NXP KL8xZ chips. I already did memory map, irq,
pinmux, rom config and other tweaks but now when I want to get UART up and
running I kind of started thinking if I am doing the right thing. Let me
explain...
I forked kl25z support in hopes that it is clo
20 matches
Mail list logo
