Re: [RFC] Add "Description:" header to defconfig file
On Sat, Jun 24, 2023 at 3:53 PM Alan C. Assis wrote: > Dear NuttXers, > As some people here know, recently Espressif added support for USB OTG > Device on ESP32S3 (thanks to Dong Heng). BIG TANKS!! :-) > And it opened the possibility to have USB Console using this USB OTG > Device or using the USB_SERIAL_JTAG (see TRM: "33 USB Serial/JTAG > Controller (USB_SERIAL_JTAG)" ). > > So, to "avoid" confusion we will follow this convention: usbconsole > when referring to USB console using USB_SERIAL_JTAG and usbnsh when > referring to USB console using USB Device. > > However for a newcomer who never saw his email, it will be difficult > to understand what each one does. Same apply to many board profiles we > already have currently. The defconfig name should and can be self-explanatory: 1. usbconsole when referring to USB console using USB_SERIAL_JTAG is not self-explanatory. Why not just use usbnshespserialjtag? I know it looks ugly (can be usbnsh_esp_serialjtag?) but its grepable and most times it is copied / typed only once? :-) 2. usbnsh when referring to USB console using USB Device... as for other devices so there is no confusion. > Of course, the best way to solve it is creating a documentation for > each board profile, but it is something that doesn't happen easily. Just let me know what to put and where and I will help with updating the documentation.. lets keep things coherent and make folks used to the process :-) > So, I think having a "Description: " in the defconfig could help here. > People could read it to know what it does or we could use: > "./tools/configure.sh info boardname:profile" to print this information. I like the idea! It would be nice to have "Description" field within the "Defconfig" itself, that would create self-explanatory solution right at the code and on the `-L` list :-) Right now some options are obvious only for people who already know them and this is not the way.. for instance some CONFIG options also could be more verbose :-) > This is just a RFC, I opened it here: > https://github.com/apache/nuttx/issues/9598 My comments inside too :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
Re: Article: 64-bit RISC-V with NuttX
On Sat, Jun 24, 2023 at 2:11 AM Lee, Lup Yuen wrote: > Thanks Tomek! Yep I'm starting to port NuttX to the StarFive JH7110 SoC > (64-bit RISC-V) and Pine64 Star64 SBC. Should be really interesting :-) > https://doc-en.rvspace.org/Doc_Center/jh7110.html > https://wiki.pine64.org/wiki/STAR64 I was also hunting for STAR64 last year but it was reschedules several times.. now I missed the short window to buy it so I need to wait for next batch.. it uses the same CPU but there is a PCI-E connector so much more possible applications :-) This is at the moment my low-priority task but if you need any help / support / testing just let me know, we both have two different boards with the same SoC/CPU :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
C++ Support
I’m currently working on a home project with NuttX and my preferred language is really C++ for what I am doing. I can work in C if necessary but I’d like to use some C++ features. So far I have managed to get the framework of what is needed configured and the next step is to start some application implementation. So I’m thinking core logic unit tested using the simulator and basic C++ application on the laptop. So I have started a fairly basic test scenario and hit a problem with the C++ support in NuttX. My application is going to be using some of the STL, at the moment I’m hitting issues with string and vector, two fairly basic and simple classes. I’m not getting any application to compile successfully. I have tried: - Basic C++ support - LLVM with both the LLVM and GNU low level libraries - uCLib++ with both LLVM and GNU libraries I have tried this with both the sim:nsh and the raspberrypi-pico-w:nsh configurations. The classes I am using are fairly basic so I could implement them myself, I would prefer to use a library version though. Has anyone managed to use the C++ libraries with NuttX ? Regards, Mark _ Blog: blog.thepcsite.co.uk Twitter: @nevynuk
[RFC] Add "Description:" header to defconfig file
Dear NuttXers, As some people here know, recently Espressif added support for USB OTG Device on ESP32S3 (thanks to Dong Heng). And it opened the possibility to have USB Console using this USB OTG Device or using the USB_SERIAL_JTAG (see TRM: "33 USB Serial/JTAG Controller (USB_SERIAL_JTAG)" ). So, to "avoid" confusion we will follow this convention: usbconsole when referring to USB console using USB_SERIAL_JTAG and usbnsh when referring to USB console using USB Device. However for a newcomer who never saw his email, it will be difficult to understand what each one does. Same apply to many board profiles we already have currently. Of course, the best way to solve it is creating a documentation for each board profile, but it is something that doesn't happen easily. So, I think having a "Description: " in the defconfig could help here. People could read it to know what it does or we could use: "./tools/configure.sh info boardname:profile" to print this information. This is just a RFC, I opened it here: https://github.com/apache/nuttx/issues/9598 BR, Alan
