My current state is that the outline is formed and that the filling per "chapter" is on its way and that the purpose of the book is set. Its public is also for people who come across Nuttx for the first time and do not have seen movies or other tutorials from Nuttx and did not have the privilege to meet all of you as I have. Say like people who start with a platform like Arduino. So there is a global introduction to all the aspects which I already mentioned: Architecture, Concepts, etc...
Also, the outline base is on real use cases, and the book will take you through hands-on situations. So you do not only read about the Architecture of Nuttx, but also you are taken on a journey by really make things happen. It also concerns setting up a development process (IDE, debugging, etc.). Arduino has its IDE. I am writing all the examples in Visual Studio Code and here I have to get the debugging solid. In Eclipse, it looks more advanced. And using a Segger is also an option, but OpenOCD is free and open for STM32. So a choice is made here. It has to be around for many years and not have a Vendor Lock-in. But before I can write out the use cases, I have to do them myself so I know all the written use cases and code tested thoroughly. There is nothing more killing then referring something in a book and it's not working. Also, I had to choose a reference platform for the book on which all the use cases are implemented. Even I do know what an RTOS is and its nota bout hardware... one has to choose a reference platform for the book. And for this, I have chosen the STM32 hardware. I do not have any commitment to a hardware supplier, but one has to make a choice. And STM32 has some good criteria for real beginners... especially in costs vs. functionality. So I am doing a lot of work daily (next to a job I have to do) to get all the things done. But writing a book has to be fun and a learning experience. I also am in contact with Alan concerning the use cases and testing. And a publisher who has understanding fort he previous matters. Better do things right than in chaos. If some-one wants an update, I am always willing to share this. I am also very anxious to see the progress on Nuttx and I do not see a roadmap here. My roadmap is clear... but I now have all the links to Nuttx on the bitbucket repo and the BSD platform. So I cannot bring out anything until I know ho wand what and when the Apache release is ready in a state like the previous platform was, where I could commit my patches, which now have a link with this writing process. Good luck tot he PMC and people who are doing this great job, and I am reading all the emails about status and progress. Ben -----Oorspronkelijk bericht----- Van: Gregory Nutt <spudan...@gmail.com> Verzonden: woensdag 18 december 2019 20:31 Aan: dev@nuttx.apache.org Onderwerp: Re: Getting Started (Was Re: [DISCUSS - NuttX Workflow]) Ben vd Veen has been working on a NuttX getting started book for a few months. I don't know the current state. There was a channel on the old NuttX Slack devoted to the book, but it has not been updated in a very long time. Perhaps Ben could fill us in on the current state, progress, and where it is going. BTW: I have archived the channels and deactivated most of the members. It is no longer viable for anything and I may as well shut down that Slack now. There is nothing to see there now. On 12/18/2019 1:34 PM, Abdelatif Guettouche wrote: >> I'd prefer that the Getting Started guide should be reachable by one >> click from the front page of the NuttX website (which doesn't exist >> yet), so that a TOTAL newbie who hasn't even gotten the code yet can >> read and get a feel for what's involved. > Agree. > I wanted to point out that much of the content needed to make such a > document is already in place. > >> Yes, much of the information is in the README file. Perhaps we can >> modify text files like that to be in Markdown format, which unlike >> HTML, leaves the file looking like a normal ASCII file, but allows >> the file to be converted to other formats, including HTML, using >> automated tools. Then we could convert that information and display >> it directly on the website. > That would helpful. > Some of the readme files are already (almost) in Markdown format. > > > On Wed, Dec 18, 2019 at 5:46 PM Nathan Hartman <hartman.nat...@gmail.com> > wrote: >> On Wed, Dec 18, 2019 at 12:01 PM Gregory Nutt <spudan...@gmail.com> wrote: >>> There is this: http://www.nuttx.org/doku.php?id=wiki:getting-started >>> where the "external tutorials" is quite extensive: >>> http://www.nuttx.org/doku.php?id=wiki:getting-started:external-tutor >>> ials >> That's great but I think we need our own basic Getting Started guide >> that gets a total newbie off the ground quickly; it can, of course, >> have an "Additional Resources" section with links to all of these >> other resources. >> >> On Wed, Dec 18, 2019 at 12:31 PM Abdelatif Guettouche >> <abdelatif.guettou...@gmail.com> wrote: >>> Boards readme files contain all the information needed to get >>> started with a particular board. >> Again, that's great, but it presumes that you have the code, know >> about the board READMEs, know where they are... >> >> I'd prefer that the Getting Started guide should be reachable by one >> click from the front page of the NuttX website (which doesn't exist >> yet), so that a TOTAL newbie who hasn't even gotten the code yet can >> read and get a feel for what's involved. >> >> Yes, much of the information is in the README file. Perhaps we can >> modify text files like that to be in Markdown format, which unlike >> HTML, leaves the file looking like a normal ASCII file, but allows >> the file to be converted to other formats, including HTML, using >> automated tools. Then we could convert that information and display >> it directly on the website. >> >> Nathan
