Lines Matching +full:qemu +full:- +full:mips
5 - Getting Help
6 - Mailing Lists
7 - Issue Tracker
8 - Source Code
9 - Website Source Code
11 - Installing Cygwin
12 - Ubuntu Bash under Windows 10
13 - Using macOS
15 - Download and Unpack
16 - Semi-Optional apps/ Package
17 - Installation Directories with Spaces in the Path
18 - Downloading from Repositories
19 - Related Repositories
20 - Notes about Header Files
22 - Instantiating "Canned" Configurations
23 - Refreshing Configurations
24 - NuttX Configuration Tool
25 - Finding Selections in the Configuration Menus
26 - Reveal Hidden Configuration Options
27 - Make Sure that You are on the Right Platform
28 - Comparing Two Configurations
29 - Making defconfig Files
30 - Incompatibilities with Older Configurations
31 - NuttX Configuration Tool under DOS
33 - Cross-Development Toolchains
34 - NuttX Buildroot Toolchain
37 - Building
38 - Re-building
39 - Build Targets and Options
40 - Native Windows Build
41 - Installing GNUWin32
43 - Strange Path Problems
44 - Window Native Toolchain Issues
49 Apache NuttX is a real-time operating system (RTOS) with an emphasis on
50 standards compliance and small footprint. Scalable from 8-bit to 64-bit
55 deeply-embedded environments (such as fork()).
70 - Use our project and provide feedback.
71 - Provide us with use-cases.
72 - Report bugs and submit patches.
73 - Contribute code or documentation.
85 * To subscribe, send an email to <dev-subscribe@nuttx.apache.org>.
86 * To unsubscribe, send an email to <dev-unsubscribe@nuttx.apache.org>.
88 <https://www.mail-archive.com/dev@nuttx.apache.org/>
90 * <commits@nuttx.apache.org> is a read-only list that notifies subscribers
92 * To subscribe, send an email to <commits-subscribe@nuttx.apache.org>.
93 * To unsubscribe, send an email to <commits-unsubscribe@nuttx.apache.org>.
95 <https://www.mail-archive.com/commits@nuttx.apache.org/>
109 - Verify that the bug does in fact exist.
111 - Search the mailing list archives to verify there is no existing issue
114 - Consider tracking down the bug yourself in the NuttX source code and
128 and the apps repository is in nuttx-apps. These are housed in GitBox on
132 - NuttX core OS repository:
134 - Primary:
137 - GitHub Mirror:
140 - Apps repository:
142 - Primary:
143 <https://gitbox.apache.org/repos/asf?p=nuttx-apps.git>
145 - GitHub Mirror:
146 <https://github.com/apache/nuttx-apps>
153 - Primary:
154 <https://gitbox.apache.org/repos/asf?p=nuttx-website.git>
156 - GitHub Mirror:
157 <https://github.com/apache/nuttx-website>
166 - An installation of Linux on a virtual machine (VM) in Windows. I have
171 confusing; Using Windows tools (such as Segger J-Link) with files
174 - The Cygwin environment. Instructions for installation of Cygwin on a
176 Cygwin". Cygwin is a mature, well-tested, and very convenient
181 - Ubuntu/Bash shell under Windows 10. This is a new option under
193 - The MSYS environment. MSYS derives from an older version of Cygwin
198 lighter weight; it uses only a minimal number of add-on POSIX-land
207 - MSYS2 appears to be a re-write of MSYS based on a newer version of
212 simple system updates. For example, 'pacman -S git' will install the
215 - Other POSIX environments. Check out:
217 - UnxUtils: <https://sourceforge.net/projects/unxutils/>,
219 - MobaXterm: <https://mobaxterm.mobatek.net/>
220 - Gow: <https://github.com/bmatzelle/gow/wiki>
224 not some less-than-obvious issues.
227 some potential tool-related issues (see the discussion "Native Windows
275 packages that are pre-selected in the default configuration.
279 make (GNU make) bison libgmp3-dev
280 gcc-core byacc libmpfr-dev
281 gcc-g++ gperf libmpc-dev
282 flex gdb automake-1.15
283 libncurses-dev libgmp-dev curl
303 pacman -S git
304 pacman -S make
305 pacman -S gcc
306 pacman -S gdb
309 build and install kconfig-frontends per the instructions of the top-level
313 pacman -S bison
314 pacman -S curl
315 pacman -S gperf
316 pacman -S ncurses-devel
317 pacman -S automake-wrapper
318 pacman -S autoconf
319 pacman -S pkg-config
322 running the kconfig-frontends configure script. See "Configuring NuttX"
325 Unlike Cygwin, MSYS does not support symbolic links. The 'ln -s' command
341 pacman -S zlib-devel
362 A better version of a command-line only Ubuntu under Windows 10 (beta)
371 - Open *Settings*.
373 - Click on *Update & security*.
375 - Click on *For Developers*.
377 - Under *Use developer features*, select the *Developer mode* option to
380 - A message box should pop up. Click *Yes* to turn on developer mode.
382 - After the necessary components install, you'll need to restart your
387 - Open *Control Panel*.
389 - Click on *Programs*.
391 - Click on *Turn Windows features on or off*.
393 - A list of features will pop up, check the *Windows Subsystem for Linux
396 - Click *OK*.
398 - Once the components installed on your computer, click the *Restart
406 - Open *Start*, do a search for `bash.exe`, and press *Enter*.
408 - On the command prompt, type `y` and press Enter to download and install
411 - Then you'll need to create a default UNIX user account. This account
416 - Close the `bash.exe` command prompt.
435 ln -s /mnt/c/Documents/projects projects
460 /mnt/c/Program\ Files\ \(x86\)/Microchip/xc32/v1.43/bin/xc32-gcc.exe --version
462 xc32-gcc.exe (Microchip Technology) 4.8.3 MPLAB XC32 Compiler v1.43 Build date: Mar 1 2017
472 Use `sudo apt-get install <package name>`. As examples, this is how
475 sudo apt-get install git
479 sudo apt-get install gcc
483 sudo apt-get install gcc-arm-none-eabi
485 **NOTE**: That is just an example. I am not sure if apt-get will give you a
489 You will also need to get the kconfig-frontends configuration as
491 kconfig-frontends configuration tool you will also need: `make`, `gperf`,
492 `flex`, `bison`, and `libncurses-dev`.
504 with Cygwin through the use of the `cygpath -w` tool that converts paths
511 The Ubuntu version support by Microsoft is a command-line only version.
515 Microsoft is willing to support. If you install a X-Server, then you
518 …<http://www.howtogeek.com/261575/how-to-run-graphical-linux-desktop-applications-from-windows-10s-…
532 brew install x86_64-elf-gcc
545 up with a directory called nuttx-version (where version is the NuttX
559 ## Semi-Optional apps/ Package
562 the NuttX source tree. As of NuttX-6.0, this application code was
569 It is called "Semi-optional" because if you don't have some `apps/`
578 will have a new directory called apps-version (where the version
587 +----+----+
610 `/home/nuttx/nuttx-code`.
619 git config --global core.autocrlf false
630 -or-
634 And the semi-optional apps/ application directory and be cloned like:
636 git clone https://gitbox.apache.org/repos/asf/nuttx-apps.git apps
638 -or-
640 git clone https://github.com/apache/nuttx-apps.git apps
645 +----+----+
656 git config --global user.name "My Name"
657 git config --global user.email my.name@example.com
661 git config --global color.branch auto
662 git config --global color.diff auto
663 git config --global color.interactive auto
664 git config --global color.status auto
668 git config --list
676 git config --global core.autocrlf false
682 * <https://gitbox.apache.org/repos/asf/nuttx-apps>
684 <https://github.com/apache/nuttx-apps.git>
708 NuttX: kconfig-frontends, genromfs, and others.
712 ### Other C-Library Header Files
717 environment. NuttX provides its own, built-in C library. So the
730 If you use some other, third-party tool chain, this will not be the
736 NuttX built-in C-Library. For such toolchains that include header
737 files from a foreign C-Library, NuttX must be compiled without using
751 (i.e., with `-nostdinc`). If that is the case, one solution is to copy
765 Even though you should not use a foreign C-Library, you may still need
767 need to use the math library, libm.a. NuttX supports a generic, built-in
780 header file can be used to "redirect" the inclusion to an architecture-
784 top-level Makefile will copy the stub math.h header file from
787 than to include that architecture-specific `math.h` header file as the
792 If you enable the generic, built-in math library, then that math library
807 you can use an architecture-specific `stdarg.h` header file by defining
821 boards/<arch-name>/<chip-name>/<board-name>/configs/<config-dir>
823 Where `<board-name>` is the name of your development board and `<config-dir>`
824 is the name of the sub-directory containing a specific configuration for
825 that board. `<arch-name>` and `<chip-name>` refer to characteristics of the
826 MCU used on the board: `<arch-name>` is the CPU architecture implemented
827 by the MCU; `<chip-name>` identifies the MCU chip family. Only a few
830 sub-directory combines those simple steps into one command.
832 There is one tool for use with any Bash-like shell that does configuration
835 tools/configure.sh <board-name>:<config-dir>
840 tools\configure.bat <board-name>:<config-dir>
851 {TOPDIR}/boards/<arch-name>/<chip-name>/<board-name>/README.txt
862 `<config-dir>` to the directory where you installed NuttX (TOPDIR):
864 …* Copy `boards/<arch-name>/<chip-name>/<board-name>/configs/<config-dir>/Make.def` to `{TOPDIR}/Ma…
868 * Copy `boards/<arch-name>/<chip-name>/<board-name>/scripts/Make.def`
878 …* Copy `boards/<arch-name>/<chip-name>/<board-name>/configs/<config-dir>/defconfig` to `{TOPDIR}/.…
885 * Copy other, environment-specific files to `{TOPDIR}`
913 The configuration step copied the .config file into place in the top-level
915 file to bring it up-to-date.
940 An automated tool has been incorporated to support re-configuration
941 of NuttX. This tool is based on the kconfig-frontends application available
942 at <https://bitbucket.org/nuttx/tools/src/master/kconfig-frontends/>. (This
943 is a snapshot of the old <http://ymorin.is-a-geek.org/projects/kconfig-frontends>
945 `kconfig-mconf` that is used by the NuttX top-level Makefile. The following
953 not been converted to use the kconfig-frontends tools! This will
955 <https://cwiki.apache.org/confluence/display/NUTTX/Converting+Legacy+Configurations+to+Use+kconfig-…
958 which is a Kconfig tool implemented in Python 2/3. Compared with kconfig-frontends,
959 kconfiglib provides NuttX with the possibility of multi-platform support(configure
966 If you are a working on Windows, which also need the support of windows-curses:
968 pip install windows-curses
971 (<https://github.com/ulfalizer/Kconfiglib/blob/master/kconfiglib.py#L3239-L3254>,
987 see kconfig-language.txt in the tools repository at
990 2. The `kconfig-mconf` tool. `kconfig-mconf` is part of the
991 kconfig-frontends package. You can download that package from the
994 Building kconfig-frontends under Linux may be as simple as
997 the more detailed build instructions in the top-level README.txt
1000 The `make install` step will, by default, install the `kconfig-mconf`
1002 install `kconfig-mconf`, make certain that your PATH variable includes
1005 The kconfig-frontends tools will not build in a native Windows
1006 environment directly "out-of-the-box". For the Windows native
1007 case, you can use the modified version of kconfig-frontends
1010 <http://uvc.de/posts/linux-kernel-configuration-tool-kconfig-under-windows.html>
1014 <http://reclonelabs.com/more-kconfig-awesomeness-for-windows/>.
1016 The basic configuration order is "bottom-up":
1018 - Select the build environment,
1019 - Select the processor,
1020 - Select the board,
1021 - Select the supported peripherals
1022 - Configure the device drivers,
1023 - Configure the application options on top of this.
1028 Another ncurses-based tool that is an option to kconfig-mconf is
1029 kconfig-nconf. The differences are primary in in the aesthetics of the
1030 UI. If you have kconfig-nconf built, then you can invoke that front end
1037 GTK installed), then you can also build the graphical kconfig-frontends,
1038 kconfig-qconf and kconfig-gconf. In these case, you can start the
1047 Some keyboard shortcuts supported by kconfig-mconf, the tool that runs
1050 - `?` will bring up the mconfig help display.
1052 - `/` can be used find configuration selections.
1054 - `Z` can be used to reveal hidden configuration options
1076 If you type `Z`, then `kconfig-mconf` will change what is displayed.
1086 will be shown the `-` for the selection and for the value (since it
1092 Saved configurations may run on Linux, Cygwin (32- or 64-bit), or other
1108 tools/sethost.sh -l
1110 Or, if you are on a Windows/Cygwin 64-bit platform:
1112 tools/sethost.sh -c
1116 tools/sethost.sh -g
1121 tools/sethost.sh -h
1128 tools/configure.sh -l board:configuration
1132 tools/configure.sh -c board:configuration
1137 tools/configure.sh -h
1152 make -f Makefile.host
1177 kconfig-frontends tools. See the following paragraph.
1188 of versioned NuttX releases are always in the form `apps-xx.yy` where `xx.yy`
1209 That make target will generate a defconfig file in the top-level
1212 wc -l .config defconfig
1266 `defconfig` configuration files generated using the `kconfig-frontends` tools
1269 uncompressed `.config-files-as-defconfig` files was eliminated after
1270 NuttX-7.21. All configurations must now be done using the
1271 `kconfig-frontends` tool. The older manual configurations and the new
1272 `kconfig-frontends` configurations are not compatible. Old legacy
1273 configurations can *not* be used with the `kconfig-frontends` tool and,
1279 > Q: How can I tell if a configuration is a new kconfig-frontends
1285 > kconfig-frontends toolchain.
1287 …://cwiki.apache.org/confluence/display/NUTTX/Converting+Legacy+Configurations+to+Use+kconfig-mconf>
1301 This will make sure that the configuration is up-to-date in the event that
1304 configuration files created with the kconfig-frontends tools.
1311 has not been converted to use the kconfig-frontends tools! This will
1313 <https://cwiki.apache.org/confluence/display/NUTTX/Converting+Legacy+Configurations+to+Use+kconfig-…
1318 console window (see *Native Windows Build* below). But `kconfig-frontends`
1320 now there are two specially modified versions of the `kconfig-frontends`
1322 <http://uvc.de/posts/linux-kernel-configuration-tool-kconfig-under-windows.html>
1325 `kconfig-tweak` tool that is not not available in the the above. However,
1327 `kconfig-tweak`: http://reclonelabs.com/more-kconfig-awesomeness-for-windows/
1329 Source code is available here: <https://github.com/reclone/kconfig-frontends-win32>
1330 and <https://github.com/reclone/kconfig-frontends-win32/releases>
1332 It is also possible to use the version of `kconfig-frontends` built
1348 2. You can, with some effort, run the Cygwin `kconfig-mconf` tool
1353 variable then run `kconfig-mconf` manually like:
1355 kconfig-mconf Kconfig
1363 the Cygwin `kconfig-mconf` running in the Windows console. The
1364 following change to the top-level `Kconfig` file seems to work
1369 - option env="APPSDIR"
1374 ## Cross-Development Toolchains
1376 In order to build NuttX for your board, you will have to obtain a cross-
1379 `boards/<arch-name>/<chip-name>/<board-name>/README.txt`).
1396 `boards/<arch-name>/<chip-name>/<board-name>/README.txt`).
1403 genromfs tools, and the kconfig-frontends tools can be built into your
1411 NOTE: For Cortex-M3/4, there are OABI and EABI versions of the buildroot
1413 the tools will be `arm-nuttx-elf-`; for the EABI toolchain the prefix will
1414 be `arm-nuttx-eabi-`. If you are using the older OABI toolchain with
1415 an ARM Cortex-M3/4, you will need to set CONFIG_ARM_TOOLCHAIN_BUILDROOT_OABI
1422 make CROSSDEV=arm-nuttx-elf
1450 There may still be issues, however, with certain the `bash`-centric scripts
1457 NuttX builds in-place in the source tree. You do not need to create
1460 the path to where your cross-development tools are installed, the
1468 `{TOPDIR}/boards/<arch-name>/<chip-name>/<board-name>/README.txt` to see
1471 ## Re-building
1473 Re-building is normally simple -- just type make again.
1483 a file in one of the linked (i.e., copied) directories, re-build NuttX,
1490 case was the following when you re-build:
1494 This 'make' command will remove of the copied directories, re-copy them,
1503 rm -rf arch/arm/src/chip arch/arm/src/board
1506 will be re-created when you do a normal 'make' and your edits will then be
1513 Below is a summary of the build targets available in the top-level
1571 dependencies under Cygwin using Windows-native toolchains.)
1609 - Uses all Windows style paths
1610 - Uses primarily Windows batch commands from cmd.exe, with
1611 - A few extensions from GNUWin32
1618 Build Tools. The build still relies on some Unix-like commands. I use
1633 Kconfig-frontends: See the section entitled "NuttX Configuration Tool
1634 under DOS" for information about installing the `kconfig-frontend` tools to
1640 2. it still lacks some of the creature-comforts of the more mature
1645 The Windows native build will depend upon a few Unix-like tools that can be
1648 GPL or similar open source license to modern MS-Windows (Microsoft Windows
1666 1. Download `GetGNUWin32-x.x.x.exe` from
1675 directory that contains this README file (`<this-directory>`).
1677 5. After running `GetGNUWin32-0.x.x.exe`, you will have a new directory
1678 `<this-directory>/GetGNUWin32`
1686 6. Change to the directory created by `GetGNUWin32-x.x.x.exe`
1691 about 446 packages! Enough to have a very complete Linux-like environment
1713 directory that contains `libiconv-2.dll`. Apparently the `as.exe` in some
1727 Anti-Virus protection interfering with the build tool program execution.
1731 Protections Settings" screen up: I disable "Real-Time Protection" just
1732 before entering 'make' then turn "Real-Time Protection" back on when the
1764 Examples include CodeSourcery (for Windows), devkitARM, and several vendor-
1770 but you might easily find some new path problems. If so, check out 'cygpath -w'
1787 ## General Pre-built Toolchain Issues
1791 if you use any pre-built toolchain (vs. building the NuttX toolchain from
1795 built-in functions detailed below. For the most part, these issues
1799 1. Header Files. Most pre-built toolchains will build with a foreign C
1807 sure the `-nostdinc` is included in the `CFLAGS`. That will assure that
1814 you will need to add `-nostdlib` to your `CFLAGS` flags to assure that
1818 that you do want (like `libgcc.a` or `libm.a`). These are special-cased
1822 3. Built-Ins. Some compilers target a particular operating system.
1825 operating systems may generate incompatible built-in logic and,
1826 for this reason, `-fno-builtin` should also be included in your
1831 4. NXFLAT. If you use a pre-built toolchain, you will lose all support
1851 Build Setup->Build Host Platform->Windows
1852 Build Setup->Windows Build Environment->Cygwin
1853 System Type->Toolchain Selection->CodeSourcery GNU Toolchain under Windows
1891 |- arch/
1893 | |- arm/
1894 | | `- src
1895 | | |- common
1896 | | | `- README_lwl_console.txt
1897 | | |- lpc214x
1898 | | | `-README.txt
1899 | | `- stm32l4
1900 | | `- README.txt
1901 | |- renesas/
1902 | | |- include/
1903 | | | `-README.txt
1904 | | |- src/
1905 | | | `-README.txt
1906 | |- x86/
1907 | | |- include/
1908 | | | `-README.txt
1909 | | `- src/
1910 | | `-README.txt
1911 | `- z80/
1912 | | `- src/
1913 | | |- z80/README.txt
1914 | | `- z180/README.txt, z180_mmu.txt
1915 | `- README.txt
1916 |- audio/
1917 | `-README.txt
1918 |- boards/
1919 | |- arm/
1920 | | |- a1x/
1921 | | | `- pcduino-a10/
1922 | | | `- README.txt
1923 | | |- am335x/
1924 | | | `- beaglebone-black/
1925 | | | `- README.txt
1926 | | |- c5471/
1927 | | | `- c5471evm/
1928 | | | `- README.txt
1929 | | |- cxd56xx/
1930 | | | `- spresense/
1931 | | | `- README.txt
1932 | | |- dm320/
1933 | | | `- ntosd-dm320/
1934 | | | |- doc/README.txt
1935 | | | `- README.txt
1936 | | |- efm32/
1937 | | | |- efm32-g8xx-stk/
1938 | | | | `- README.txt
1939 | | | |- efm32gg-stk3700/
1940 | | | | `- README.txt
1941 | | | `- olimex-efm32g880f128-stk/
1942 | | | `- README.txt
1943 | | |- imx6/
1944 | | | `- sabre-6quad/
1945 | | | `- README.txt
1946 | | |- imxrt/
1947 | | | |- imxrt1050-evk/
1948 | | | | `- README.txt
1949 | | | |- imxrt1060-evk/
1950 | | | | `- README.txt
1951 | | | `- teensy-4.x/
1952 | | | `- README.txt
1953 | | |- kinetis/
1954 | | | |- freedom-k28f/
1955 | | | | `- README.txt
1956 | | | |- freedom-k64f/
1957 | | | | `- README.txt
1958 | | | |- freedom-k66f/
1959 | | | | `- README.txt
1960 | | | |- kwikstik-k40/
1961 | | | | `- README.txt
1962 | | | |- teensy-3.x/
1963 | | | | `- README.txt
1964 | | | |- twr-k60n512/
1965 | | | | `- README.txt
1966 | | | `- twr-k64f120m/
1967 | | | `- README.txt
1968 | | |- kl/
1969 | | | |- freedom-kl25z/
1970 | | | | `- README.txt
1971 | | | |- freedom-kl26z/
1972 | | | | `- README.txt
1973 | | | `- teensy-lc/
1974 | | | `- README.txt
1975 | | |- lc823450/
1976 | | | `- lc823450-xgevk/
1977 | | | `- README.txt
1978 | | |- lpc17xx_40xx/
1979 | | | |- lincoln60/
1980 | | | | `- README.txt
1981 | | | |- lpc4088-devkit/
1982 | | | | `- README.txt
1983 | | | |- lpc4088-quickstart/
1984 | | | | `- README.txt
1985 | | | |- lpcxpresso-lpc1768/
1986 | | | | `- README.txt
1987 | | | |- lx_cpu/
1988 | | | | `- README.txt
1989 | | | |- mbed/
1990 | | | | `- README.txt
1991 | | | |- mcb1700/
1992 | | | | `- README.txt
1993 | | | |- olimex-lpc1766stk/
1994 | | | | `- README.txt
1995 | | | |- open1788/
1996 | | | | `- README.txt
1997 | | | |- pnev5180b/
1998 | | | | `- README.txt
1999 | | | |- u-blox-c027/
2000 | | | | `- README.txt
2001 | | | `- zkit-arm-1769/
2002 | | | `- README.txt
2003 | | |- lpc214x/
2004 | | | |- mcu123-lpc214x/
2005 | | | | `- README.txt
2006 | | | `- zp214xpa/
2007 | | | `- README.txt
2008 | | |- lpc2378/
2009 | | | `- olimex-lpc2378/
2010 | | | `- README.txt
2011 | | |- lpc31xx/
2012 | | | |- ea3131/
2013 | | | | `- README.txt
2014 | | | |- ea3152/
2015 | | | | `- README.txt
2016 | | | `- olimex-lpc-h3131/
2017 | | | `- README.txt
2018 | | |- lpc43xx/
2019 | | | |- bambino-200e/
2020 | | | | `- README.txt
2021 | | | |- lpc4330-xplorer/
2022 | | | | `- README.txt
2023 | | | |- lpc4337-ws/
2024 | | | | `- README.txt
2025 | | | |- lpc4357-evb/
2026 | | | | `- README.txt
2027 | | | `- lpc4370-link2/
2028 | | | `- README.txt
2029 | | |- lpc54xx/
2030 | | | `- lpcxpresso-lpc54628/
2031 | | | `- README.txt
2032 | | |- max326xx/
2033 | | | `- max32660-evsys/
2034 | | | `- README.txt
2035 | | |- moxart/
2036 | | | `- moxa/
2037 | | |- nrf52/
2038 | | | `- nrf52-generic/
2039 | | | `- README.txt
2040 | | |- nuc1xx/
2041 | | | `- nutiny-nuc120/
2042 | | | `- README.txt
2043 | | |- s32k1xx/
2044 | | | |- s32k118evb/
2045 | | | | `- README.txt
2046 | | | |- s32k146evb/
2047 | | | | `- README.txt
2048 | | | `- s32k148evb/
2049 | | | `- README.txt
2050 | | |- sam34/
2051 | | | |- arduino-due/
2052 | | | | `- README.txt
2053 | | | |- flipnclick-sam3x/
2054 | | | | `- README.txt
2055 | | | |- sam3u-ek/
2056 | | | | `- README.txt
2057 | | | |- sam4cmp-db/
2058 | | | | `- README.txt
2059 | | | |- sam4e-ek/
2060 | | | | `- README.txt
2061 | | | |- sam4l-xplained/
2062 | | | | `- README.txt
2063 | | | |- sam4s-xplained/
2064 | | | | `- README.txt
2065 | | | `- sam4s-xplained-pro/
2066 | | | `- README.txt
2067 | | |- sama5/
2068 | | | |- sama5d2-xult/
2069 | | | | `- README.txt
2070 | | | |- giant-board/
2071 | | | | `- README.md
2072 | | | |- sama5d3x-ek/
2073 | | | | `- README.txt
2074 | | | |- sama5d3-xplained/
2075 | | | | `- README.txt
2076 | | | `- sama5d4-ek/
2077 | | | `- README.txt
2078 | | |- samd2l2/
2079 | | | |- arduino-m0/
2080 | | | | `- README.txt
2081 | | | |- samd20-xplained/
2082 | | | | `- README.txt
2083 | | | |- samd21-xplained/
2084 | | | | `- README.txt
2085 | | | `- saml21-xplained/
2086 | | | `- README.txt
2087 | | |- samd5e5/
2088 | | | `- metro-m4/
2089 | | | `- README.txt
2090 | | |- samv7/
2091 | | | |- same70-qmtech/
2092 | | | | `- README.txt
2093 | | | |- same70-xplained/
2094 | | | | `- README.txt
2095 | | | `- samv71-xult/
2096 | | | `- README.txt
2097 | | |- stm32/
2098 | | | |- axoloti/
2099 | | | | `- README.txt
2100 | | | |- b-g474e-dpow1/
2101 | | | | `- README.txt
2102 | | | |- clicker2-stm32/
2103 | | | | `- README.txt
2104 | | | |- cloudctrl/
2105 | | | | `- README.txt
2106 | | | |- emw3162/
2107 | | | | `- README.txt
2108 | | | |- fire-stm32v2/
2109 | | | | `- README.txt
2110 | | | |- hymini-stm32v/
2111 | | | | `- README.txt
2112 | | | |- maple/
2113 | | | | `- README.txt
2114 | | | |- mikroe-stm32f4/
2115 | | | | `- README.txt
2116 | | | |- nucleo-f103rb/
2117 | | | | `- README.txt
2118 | | | |- nucleo-f207zg/
2119 | | | | `- README.txt
2120 | | | |- nucleo-f302r8/
2121 | | | | `- README.txt
2122 | | | |- nucleo-f303re/
2123 | | | | `- README.txt
2124 | | | |- nucleo-f303ze/
2125 | | | | `- README.txt
2126 | | | |- nucleo-f334r8/
2127 | | | | `- README.txt
2128 | | | |- nucleo-f410rb/
2129 | | | | `- README.txt
2130 | | | |- nucleo-f446re/
2131 | | | | `- README.txt
2132 | | | |- nucleo-f4x1re/
2133 | | | | `- README.txt
2134 | | | |- nucleo-l152re/
2135 | | | | `- README.txt
2136 | | | |- olimexino-stm32/
2137 | | | |- olimex-stm32-e407/
2138 | | | | `- README.txt
2139 | | | |- olimex-stm32-h405/
2140 | | | | `- README.txt
2141 | | | |- olimex-stm32-h407/
2142 | | | | `- README.txt
2143 | | | |- olimex-stm32-p107/
2144 | | | |- olimex-stm32-p207/
2145 | | | | `- README.txt
2146 | | | |- olimex-stm32-p407/
2147 | | | | `- README.txt
2148 | | | |- omnibusf4/
2149 | | | | `- README.txt
2150 | | | |- photon/
2151 | | | | `- README.txt
2152 | | | |- shenzhou/
2153 | | | | `- README.txt
2154 | | | |- stm32_tiny/
2155 | | | | `- README.txt
2156 | | | |- stm3210e-eval/
2157 | | | | `- README.txt
2158 | | | |- stm3220g-eval/
2159 | | | | `- README.txt
2160 | | | |- stm3240g-eval/
2161 | | | | `- README.txt
2162 | | | |- stm32butterfly2/
2163 | | | |- stm32f103-minimum/
2164 | | | | `- README.txt
2165 | | | |- stm32f334-disco/
2166 | | | | `- README.txt
2167 | | | |- stm32f3discovery/
2168 | | | | `- README.txt
2169 | | | |- stm32f411e-disco/
2170 | | | | `- README.txt
2171 | | | |- stm32f429i-disco/
2172 | | | | `- README.txt
2173 | | | |- stm32f4discovery/
2174 | | | | `- README.txt
2175 | | | |- stm32ldiscovery/
2176 | | | | `- README.txt
2177 | | | |- stm32vldiscovery/
2178 | | | | `- README.txt
2179 | | | `- viewtool-stm32f107/
2180 | | | `- README.txt
2181 | | |- stm32f0l0g0/
2182 | | | |- b-l072z-lrwan1/
2183 | | | | `- README.txt
2184 | | | |- nucleo-f072rb/
2185 | | | | `- README.txt
2186 | | | |- nucleo-f091rc/
2187 | | | | `- README.txt
2188 | | | |- nucleo-g070rb/
2189 | | | | `- README.txt
2190 | | | |- nucleo-g071rb/
2191 | | | | `- README.txt
2192 | | | |- nucleo-l073rz/
2193 | | | | `- README.txt
2194 | | | |- stm32f051-discovery/
2195 | | | | `- README.txt
2196 | | | `- stm32f072-discovery/
2197 | | | `- README.txt
2198 | | |- stm32f7/
2199 | | | |- nucleo-144/
2200 | | | | `- README.txt
2201 | | | |- stm32f746g-disco/
2202 | | | | |- configs/fb/README.txt
2203 | | | | |- configs/nxdemo/README.txt
2204 | | | | |- configs/nxterm/README.txt
2205 | | | | `- README.txt
2206 | | | |- stm32f746-ws/
2207 | | | `- stm32f769i-disco/
2208 | | | `- README.txt
2209 | | |- stm32h7/
2210 | | | `- nucleo-h743zi/
2211 | | | `- README.txt
2212 | | |- stm32l4/
2213 | | | |- b-l475e-iot01a/
2214 | | | | `- README.txt
2215 | | | |- nucleo-l432kc/
2216 | | | | `- README.txt
2217 | | | |- nucleo-l452re/
2218 | | | | `- README.txt
2219 | | | |- nucleo-l476rg/
2220 | | | | `- README.txt
2221 | | | |- nucleo-l496zg/
2222 | | | | `- README.txt
2223 | | | |- stm32l476-mdk/
2224 | | | | `- README.txt
2225 | | | |- stm32l476vg-disco/
2226 | | | | `- README.txt
2227 | | | `- stm32l4r9ai-disco/
2228 | | | `- README.txt
2229 | | |- str71x/
2230 | | | `- olimex-strp711/
2231 | | | `- README.txt
2232 | | |- tiva/
2233 | | | |- dk-tm4c129x/
2234 | | | | `- README.txt
2235 | | | |- eagle100/
2236 | | | | `- README.txt
2237 | | | |- ekk-lm3s9b96/
2238 | | | | `- README.txt
2239 | | | |- launchxl-cc1310/
2240 | | | | `- README.txt
2241 | | | |- launchxl-cc1312r1/
2242 | | | | `- README.txt
2243 | | | |- lm3s6432-s2e/
2244 | | | | `- README.txt
2245 | | | |- lm3s6965-ek/
2246 | | | | `- README.txt
2247 | | | |- lm3s8962-ek/
2248 | | | | `- README.txt
2249 | | | |- lm4f120-launchpad/
2250 | | | | `- README.txt
2251 | | | |- tm4c123g-launchpad/
2252 | | | | `- README.txt
2253 | | | `- tm4c1294-launchpad/
2254 | | | `- README.txt
2255 | | |- tms570/
2256 | | | |- launchxl-tms57004/
2257 | | | | `- README.txt
2258 | | | `- tms570ls31x-usb-kit/
2259 | | | `- README.txt
2260 | | `- xmc4/
2261 | | `- xmc4500-relax/
2262 | | `- README.txt
2263 | |- avr/
2264 | | |- at32uc3/
2265 | | | `- avr32dev1/
2266 | | | `- README.txt
2267 | | |- at90usb/
2268 | | | |- micropendous3/
2269 | | | | `- README.txt
2270 | | | `- teensy-2.0/
2271 | | | `- README.txt
2272 | | `- atmega/
2273 | | |- amber/
2274 | | | `- README.txt
2275 | | |- arduino-mega2560/
2276 | | | `- README.txt
2277 | | `- moteino-mega/
2278 | | `- README.txt
2279 | |- hc/
2280 | | `- m9s12/
2281 | | |- demo9s12ne64/
2282 | | | `- README.txt
2283 | | `- ne64badge/
2284 | | `- README.txt
2285 | |- mips/
2286 | | |- pic32mx/
2287 | | | |- mirtoo/
2288 | | | | `- README.txt
2289 | | | |- pic32mx7mmb/
2290 | | | | `- README.txt
2291 | | | |- pic32mx-starterkit/
2292 | | | | `- README.txt
2293 | | | |- sure-pic32mx/
2294 | | | | `- README.txt
2295 | | | `- ubw32/
2296 | | | `- README.txt
2297 | | `-pic32mz/
2298 | | |- chipkit-wifire/
2299 | | | `- README.txt
2300 | | |- flipnclick-pic32mz/
2301 | | | `- README.txt
2302 | | `- pic32mz-starterkit/
2303 | | `- README.txt
2304 | |- misoc/
2305 | | `- lm32/
2306 | | `- misoc/
2307 | | `- README.txt
2308 | |- or1k/
2309 | | `- mor1kx/
2310 | | `- or1k/
2311 | | `- README.txt
2312 | |- renesas/
2313 | | |- m16c/
2314 | | | `- skp16c26/
2315 | | | `- README.txt
2316 | | `-sh1/
2317 | | `- us7032evb1/
2318 | | `- README.txt
2319 | |- risc-v/
2320 | |- sim/
2321 | | `- sim/
2322 | | `- sim/
2323 | | |- include/README.txt
2324 | | `- README.txt
2325 | |- x86/
2326 | | `- qemu/
2327 | | `- qemu-i486/
2328 | | `- README.txt
2329 | |- xtensa/
2330 | | `- esp32/
2331 | | `- esp32-core/
2332 | | `- README.txt
2333 | |- z16/
2334 | | `- z16f/
2335 | | `- z16f2800100zcog/
2336 | | |- configs/nsh/README.txt
2337 | | |- configs/ostest/README.txt
2338 | | |- configs/pashello/README.txt
2339 | | `- README.txt
2340 | |- z80/
2341 | | |- ez80/
2342 | | | |- ez80f910200kitg/
2343 | | | | |- configs/ostest/README.txt
2344 | | | | `- README.txt
2345 | | | |- ez80f910200zco/
2346 | | | | |- configs/dhcpd/README.txt
2347 | | | | |- configs/httpd/README.txt
2348 | | | | |- configs/nettest/README.txt
2349 | | | | |- configs/nsh/README.txt
2350 | | | | |- configs/poll/README.txt
2351 | | | | `- README.txt
2352 | | | |- makerlisp/
2353 | | | | |- configs/nsh_flash/README.txt
2354 | | | | |- configs/nsh_ram/README.txt
2355 | | | | |- configs/sdboot/README.txt
2356 | | | | `- README.txt
2357 | | | `- z80x/
2358 | | | |- configs/nsh_flash/README.txt
2359 | | | |- configs/nsh_ram/README.txt
2360 | | | |- configs/sdboot/README.txt
2361 | | | `- README.txt
2362 | | |- z180/
2363 | | | `- p112/
2364 | | | `- README.txt
2365 | | |- z8/
2366 | | | |- z8encore000zco/
2367 | | | | |- configs/ostest/README.txt
2368 | | | | `- README.txt
2369 | | | `- z8f64200100kit/
2370 | | | |- configs/ostest/README.txt
2371 | | | `- README.txt
2372 | | `- z80/
2373 | | `- z80sim/
2374 | | `- README.txt
2375 | `-README.txt
2376 |- drivers/
2377 | |- eeprom/
2378 | | `- README.txt
2379 | |- lcd/
2381 | | `- pcf8574_lcd_backpack_readme.txt
2382 | |- mtd/
2383 | | `- README.txt
2384 | |- sensors/
2385 | | `- README.txt
2386 | |- syslog/
2387 | | `- README.txt
2388 | `- README.txt
2389 |- fs/
2390 | |- binfs/
2391 | | `- README.txt
2392 | |- cromfs/
2393 | | `- README.txt
2394 | |- mmap/
2395 | | `- README.txt
2396 | |- nxffs/
2397 | | `- README.txt
2398 | |- smartfs/
2399 | | `- README.txt
2400 | |- procfs/
2401 | | `- README.txt
2402 | |- spiffs/
2403 | | `- README.md
2404 | `- unionfs/
2405 | `- README.txt
2406 |- graphics/
2407 | `- README.txt
2408 |- libs/
2409 | |- README.txt
2410 | |- libc/
2411 | | |- zoneinfo
2412 | | | `- README.txt
2413 | | `- README.txt
2414 | |- libdsp/
2415 | | `- README.txt
2416 | |- libnx/
2417 | | |- nxfongs
2418 | | | `- README.txt
2419 | | `- README.txt
2420 | |- libxx/
2421 | `- README.txt
2422 |- mm/
2423 | |- shm/
2424 | | `- README.txt
2425 | `- README.txt
2426 |- net/
2427 | |- sixlowpan
2428 | | `- README.txt
2429 | `- README.txt
2430 |- pass1/
2431 | `- README.txt
2432 |- syscall/
2433 | `- README.txt
2434 `- tools/
2435 `- README.txt
2437 Below is a guide to the available README files in the semi-optional apps/
2441 |- examples/
2442 | |- bastest/README.txt
2443 | |- json/README.txt
2444 | |- pashello/README.txt
2445 | `- README.txt
2446 |- gpsutils/
2447 | `- minmea/README.txt
2448 |- graphics/
2449 | |- tiff/README.txt
2450 | `- traveler/tools/tcledit/README.txt
2451 |- interpreters/
2452 | |- bas/
2453 | | `- README.txt
2454 | |- ficl/
2455 | | `- README.txt
2456 | `- README.txt
2457 |- modbus/
2458 | `- README.txt
2459 |- netutils/
2460 | |- discover/
2461 | | `- README.txt
2462 | |- ftpc/
2463 | | `- README.txt
2464 | |- json/
2465 | | `- README.txt
2466 | |- telnetd/
2467 | | `- README.txt
2468 | `- README.txt
2469 |- nshlib/
2470 | `- README.txt
2471 |- NxWidgets/
2472 | `- README.txt
2473 |- system/
2474 | |- cdcacm/
2475 | | `- README.txt
2476 | |- i2c/
2477 | | `- README.txt
2478 | |- inifile/
2479 | | `- README.txt
2480 | |- install/
2481 | | `- README.txt
2482 | |- nsh/
2483 | | `- README.txt
2484 | |- nxplayer/
2485 | | `- README.txt
2486 | |- psmq/
2487 | | `- README.txt
2488 | |- symtab/
2489 | | `- README.txt
2490 | |- termcurses/
2491 | | `- README.txt
2492 | |- usbmsc/
2493 | | `- README.txt
2494 | `- zmodem/
2495 | `- README.txt
2496 `- wireless
2497 |- bluetooth/
2498 | `- btsak/
2499 | `- README.txt
2500 `- ieee802154
2501 `- i8sak/
2502 `- README.txt
2507 |- Doxygen
2508 | `- README.txt
2509 |- tools
2510 | `- README.txt
2511 |- UnitTests
2512 | `- README.txt
2513 `- README.txt
2516 `- README.txt
2519 `- README.txt
2522 `- README.txt