Finished C5471 Integration

git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@48 42af7a65-404d-4744-a932-0658087f49c3
This commit is contained in:
patacongo 2007-03-09 17:22:55 +00:00
parent 04be124b7e
commit 3f8a1c1ea4
2 changed files with 14 additions and 38 deletions

View File

@ -28,8 +28,8 @@
NuttX operates on the ARM7 of this dual core processor.
This port uses the <a href="http://www.spectrumdigital.com/">Spectrum Digital</a>
evaluation board with a GNU arm-elf toolchain*.
This port is in progress and partially functional (However,
my board is dead at the moment so it will be awhile before I fix it)</li>
This port is complete, verified, and included in the initial NuttX
release.</li>
<li><b>8051 Microcontroller</b>.
This port uses the <a href="http://www.pjrc.com/">PJRC</a> 87C52 development system
and the <a href="http://sdcc.sourceforge.net/">SDCC</a> toolchain.
@ -43,17 +43,18 @@ is available that be used to build a NuttX-compatible arm-elf toolchain.</blockq
<h1>Memory Footprint</h1>
<p>Details to be provided</p>
<p>
I have a complete build for an ARM7 target that includes most of the OS
features and a broad range of OS tests.
That builds to an executable that requires about 85Kb for .text, .data., and .bss.
<p><b>C5471 (Arm7)</b>
The build for this ARM7 target that includes most of the OS features and
a broad range of OS tests. The size of this executable as given by the
Linux <tt>size</tt> command is:
</p>
<p>
I have a stripped down OS test for the 8051 target that requires only
18Kb. A substantial effort was required to get to this size
(see <a href="codesize-070301.xls">spreadsheet</a> for details).
<pre>
text data bss dec hex filename
53272 428 3568 57268 dfb4 nuttx
</pre>
<p><b>87C52</b>
A reduced functionality OS test for the 8051 target requires only
about 18Kb (see <a href="codesize-070301.xls">spreadsheet</a> for details).
</p>
<h1>Licensing</h1>

View File

@ -27,7 +27,7 @@ Gregory Nutt
<H1>1.0 <A NAME="Introduction">Introduction</A></H1>
<P>
This user's manual is divided into five sections:
This user's manual is divided into three sections:
<UL>
<LI><B>Section 1.0, <A HREF="#Introduction">Introduction</A></B>:
This section provides an overview of the Nuttx user's manual.
@ -48,8 +48,6 @@ into several paragraphs that describe different groups of OS interfaces:
<LI><B>Section 3.0, <A HREF="#Data_Structures">OS Data Structures</A></B>:
This section documents the data structures that are used at the Nuttx
interface.
<LI><B>Section 4.0, <A HREF="#Problems">Known Problems</A></B>. This section
lists known problems in the latest release of Nuttx.
</UL>
<HR>
@ -4113,28 +4111,5 @@ notify a task when a message is available on a queue.
have to do some redesign.
</p>
<HR>
<H1>4.0 <A NAME="Problems">Known Problems</A></H1>
<P>
This section documents know problems with Nuttx at the time
of this writing.
<P>
<HR>
<B>Problem</B>:
There is a problem with the unblock logic in os_signal.c when message queue
becomes not-empty -- sig_mqnotempty() calls sig_received().
sig_received() relies on task_state == TSTATE_WAIT_SIG and will ignore
tasks that are waiting on a message queue to become non-empty.
<P>
<B>Priority</B>: <B>LOW</B>. If a task is blocked a waiting for a message
queue to become non-empty, it will be re-started anyway.
<HR>
<B>Problem</B>: task_restart won't restart a running task
<P>
<B>Priority</B>: <B>LOW</B>.
</BODY>
</HTML>