On Fri, Jan 31, 2025 at 5:26 PM Sebastien Lorquet wrote:
> Dont loose too many time, reversing the commit already fixed the problem.
> Or I'll charge you my own time :)
> I think the two cancel anyway :)
> It's a stm32f429 cpu, so you have all the stm32 "common" board stuff
> inbetween.
> host is
Thanks again, Petro 🙂
I think I understand the MCUboot side of things well now.
In the arm V7 code, that I believe you're familiar
with, there's a that "assumes" the stack
pointer is the first address after the number of bytes specified by the
header length as passed by MCUboot (which is th
> That is not excuse. Maintaining old API is not hard. Usually it's just a
simple
call to new API, which will not require further maintenence. You can even
kick
it to separate file so it does not break code aesthetics ;)
If it were that simple it wouldn't be a problem. But no, it isn't.
I just gi
Hi Kevin,
welcome to the community and mailing list.
Please submit the code as it is and mark the PR as WIP. This way the
community may be able to check the implementation and provide feedback
Attached are the contribution guidelines
https://nuttx.apache.org/docs/latest/contributing/index.html
B
Hello NuttX!_
This is my first mail to an open source mailing list.
Currently, I am working on adding SX126x support. This is currently the
most common LoRa chip. It is newer than the already supported SX127x, even
when the number is lower for some reason.
The chip is a requirement for a project
Apart from the tool issue, what we miss the most are processes, in the
sense of
project management, not osdev ;). We have distributed teams and individuals
that
work towards their established goals. The problem is that the community
doesn't
know these goals. It may even be the case that the company
