Cosmetic: Updates to TODO anre README text
This commit is contained in:
parent
150ec1f19c
commit
49a5c9a3c5
@ -248,6 +248,18 @@ mount
|
||||
cd <nuttx-directory>/tools
|
||||
./configure.sh sim/mount
|
||||
|
||||
NOTES
|
||||
-----
|
||||
|
||||
1. This configuration uses the mconf-based configuration tool. To
|
||||
change this configuration using that tool, you should:
|
||||
|
||||
a. Build and install the kconfig-mconf tool. See nuttx/README.txt
|
||||
and misc/tools/
|
||||
|
||||
b. Execute 'make menuconfig' in nuttx/ in order to start the
|
||||
reconfiguration process.
|
||||
|
||||
mtdpart
|
||||
|
||||
This is the apps/examples/mtdpart test using a MTD RAM driver to
|
||||
@ -268,6 +280,12 @@ nettest
|
||||
- The NuttX network is not, however, functional on the Linux TAP
|
||||
device yet.
|
||||
|
||||
UPDATE: The TAP device does apparently work according to a NuttX
|
||||
user (provided that it is not used with NSH: NSH waits on readline()
|
||||
for console input. When it calls readline(), the whole system blocks
|
||||
waiting from input from the host OS). My failure to get the TAP
|
||||
device working appears to have been a cockpit error.
|
||||
|
||||
- As of NuttX-5.18, when built on Windows, this test does not try
|
||||
to use the TAP device (which is not available on Cygwin anyway),
|
||||
but inside will try to use the Cygwin WPCAP library. Only the
|
||||
|
@ -1,10 +1,10 @@
|
||||
README.txt
|
||||
^^^^^^^^^^
|
||||
==========
|
||||
|
||||
This is the README file for the NuttX port to the ZiLog ZNEO MCU.
|
||||
|
||||
ZDS-II Compiler Versions
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
========================
|
||||
|
||||
Version 4.10.2
|
||||
|
||||
@ -54,11 +54,12 @@ Other Versions
|
||||
5.0.1 to whatever.
|
||||
|
||||
Issues
|
||||
^^^^^^
|
||||
======
|
||||
|
||||
There are several, important open issues with the ZNEO port (8 as of this writing).
|
||||
There are several, important open issues with the ZNEO port (9 as of this writing).
|
||||
See the TODO file in the top-level NuttX directory. One of these should be
|
||||
mentioned here because it causes a failure to compile Nuttx:
|
||||
mentioned here because it causes a failure to compile with older versions of
|
||||
Nuttx:
|
||||
|
||||
Description: The file drivers/mmcsd/mmcsd_sdio.c generates an internal compiler
|
||||
error like:
|
||||
@ -68,18 +69,17 @@ mentioned here because it causes a failure to compile Nuttx:
|
||||
File <c3>, Args(562,46)
|
||||
|
||||
Status: Open. Recommended workaround: remove mmcsd_sdio.c from
|
||||
drivers/mmcsd/Make.defs. There is no SDIO support for the Z16 anyway
|
||||
drivers/mmcsd/Make.defs. There is no SDIO support for the Z16
|
||||
anyway
|
||||
Priority: Low
|
||||
|
||||
This is bug in ZDS-II. It was discovered in version 4.11.0 and still exists
|
||||
in version 4.11.1.
|
||||
in version 4.11.1. I don't know about 5.0.1. It is not a problem with recent
|
||||
versions of NuttX using any version because the file mmcsd_sdio.c is no longer
|
||||
built unconditionally.
|
||||
|
||||
Configuration Subdirectories
|
||||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
||||
|
||||
- source/ and include/
|
||||
These directories contain common logic for all z16f2800100zcog
|
||||
configurations.
|
||||
Selecting Configurations
|
||||
========================
|
||||
|
||||
Variations on the basic z8f162800100zcog configuration are maintained
|
||||
in subdirectories. To configure any specific configuration, do the
|
||||
@ -92,7 +92,16 @@ following steps:
|
||||
|
||||
Where <sub-directory> is the specific board configuration that you
|
||||
wish to build. The following board-specific configurations are
|
||||
available:
|
||||
available.
|
||||
|
||||
Configuration Sub-directories
|
||||
=============================
|
||||
|
||||
source/ and include/
|
||||
--------------------
|
||||
|
||||
These directories contain common logic for all z16f2800100zcog
|
||||
configurations.
|
||||
|
||||
nsh
|
||||
---
|
||||
|
Loading…
Reference in New Issue
Block a user