Em sáb., 22 de mai. de 2021 às 18:01, Gregory Nutt <spudan...@gmail.com> escreveu: > > > > In my application, I am not using nutshell. > > > > But I was wondering if is it the best, or correct or recommended way to do. > > I don't think there is a best or recommended in this case. You should > do what is best for you and for the final product. > > Often people build NSH in their development builds, but omit it from > final production build. Many embedded systems have no easily accessible > to UI and carrying NSH is a waste of FLASH in that case. > > NSH can also be a security hole if you don't carefully check which > commands are available or do not use a login.
I was thinking about that. > > Other people like to keep NSH in FLASH for post-release debugging or for > remote sessions. > > There is no one-size-fits-all answer. > Indeed. In my case, I implemented a single application controlling everything, maybe just like any firmware. And I prepared my environment to work that way. But, then, rethinking a little bit, I could split my "large" application into some "small" applications communicating between each other. Then the environment changes, the build process changes, integration changes. It's nice to see that there are several possibilities. Best regards, Flavio > > -- Flavio de Castro Alves Filho flavio.al...@gmail.com Twitter: http://twitter.com/#!/fraviofii LinkedIn profile: www.linkedin.com/in/flaviocastroalves
