On 31/01/2025 13:16, Tomek CEDRO wrote:
On Fri, Jan 31, 2025 at 10:30 AM Sebastien Lorquet <sebast...@lorquet.fr> wrote:
Many problems arise when the nuttx and nuttx-apps are not in sync.
I always keep its masters in sync.. if there is no info on the website
we need to update documentation :-)
This is not possible with an actual product deployed at a customer, you
know. The product has a life and we dont touch it once it works! Only
when it breaks!
I dont spend 100% of my 5 days a week to update nuttx as a leisure.
Please read my mail carefully to understand all steps.
How does in work in a real company like mine?
Initial development after contract is done
- get current nuttx
- clone apps in our board specific repo, add some custom apps
- build, release product after some months
- product is done, tested, deployed.
- stop working on this project, do a million other things without any
relation to nuttx
Several months later: customer asks an improvement (or fix, like the
embedded server in our nuttx apps cant be contacted anymore - connection
did not close because of network failure and client disconnection)
Analyze situation: this happens when network goes down / test computer
goes to sleep.
Deduce it's probably a keepalive problem
Lurk google, see nuttx commits related to keepalive
- get back all project files from archive
- put everything back in your head because you've not worked on this for
MONTHS
- negotiate work time with management, of course it's restricted
- update nuttx,
- mess with nuttx update problems for several days, including TIME,
PROJECT COST, and RAGE
- eventually it works again so we send the updated firmware for
deployment, which can take several weeks since there are lots of
products all over paris region and they are only updated at maintenance
periods.
Thats how it works. Thats how practical companies work. it's not easy or
ideal. Dont tell me to change anything here, I cant.
I cant keep nuttx up to date every day or week.
-I have no time to pull and build everyday
-I have no possibilty (OR WISH! remember, dont fix it if it aint broken)
to quickly deploy updates daily
Please try to imagine that everything can be as ideal as you wish it was.
And I guess for the user its best to use release packages of nuttx and
nuttx-apps that are supposed to work. Master contains development
stuff in this case :-)
slo@slolin:~/Sources/product-env/nuttx$ cd ../apps
slo@slolin:~/Sources/product-env/apps$ git log -1
commit 66231194be3de611c18bfaa2e63eece604184041 (HEAD)
Author: chao an <anc...@lixiang.com>
Date: Fri Dec 27 14:20:37 2024 +0800
apps/system: replace CONFIG_NSH_LINELEN to LINE_MAX
Applications should not depend on any properties of nshlib
Signed-off-by: chao an <anc...@lixiang.com>
This particular commit is set of commits that aligns us with POSIX's
LINIE_MAX :-)
Yes I messed my copy paste.
Of course I also tried with the commit before that one, and it didnt
work either.
Sebastien
