9
0
Fork 0
git-svn-id: https://nuttx.svn.sourceforge.net/svnroot/nuttx/trunk@3333 7fd9a85b-ad96-42d3-883c-3090e2eb8679
This commit is contained in:
patacongo 2011-03-03 23:15:50 +00:00
parent 7be47905d7
commit 07f97f51cf
3 changed files with 36 additions and 9 deletions

View File

@ -12,7 +12,7 @@
<h1><big><font color="#3c34ec">
<i>NuttX RTOS Porting Guide</i>
</font></big></h1>
<p>Last Updated: February 25, 2011</p>
<p>Last Updated: March 3, 2011</p>
</td>
</tr>
</table>
@ -970,7 +970,7 @@ tools/
This could be done manually as follows:
</p>
<ul>
<li>Copy <code>configs/</code><i>&lt;board-name&gt;</i><code>/[</code><i>&lt;config-dir&gt;</i><code>/]Make.def</code> to <code>${TOPDIR}/Make.defs</code>,<li>
<li>Copy <code>configs/</code><i>&lt;board-name&gt;</i><code>/[</code><i>&lt;config-dir&gt;</i><code>/]Make.defs</code> to <code>${TOPDIR}/Make.defs</code>,<li>
<li>Copy <code>configs/</code><i>&lt;board-name&gt;</i><code>/[</code><i>&lt;config-dir&gt;</i><code>/]setenv.sh</code> to <code>${TOPDIR}/setenv.sh</code>, and</li>
<li>Copy <code>configs/</code><i>&lt;board-name&gt;</i><code>/[</code><i>&lt;config-dir&gt;</i><code>/]defconfig</code> to <code>${TOPDIR}/.config</code></li>
</ul>

View File

@ -368,9 +368,36 @@ LEDs
Glowing Glowing This is also a normal healthy state: The OS successfully initialized,
is running in reduced power mode, but taking interrupts. The glow
is very faint and you may have to dim the lights to see that LEDs are
active at all!
active at all! See note below.
ON Flashing Ooops! We crashed sometime after initialization.
NOTE: In glowing/glowing case, you get some good subjective information about the
behavior of your system by looking at the level of the LED glow (or better, by
connecting O-Scope and calculating the actual duty):
1. The intensity of the glow is determined by the duty of LED on/off toggle --
as the ON period becomes larger with respect the OFF period, the LED will
glow more brightly.
2. LED2 is turned ON when entering an interrupt and turned OFF when returning from
the interrupt. A brighter LED2 means that the system is spending more time in
interrupt handling.
3. LED1 is turned OFF just before the processor goes to sleep. The processor
sleeps until awakened by an interrupt. LED1 is turned back ON after the
processor is re-awakened -- actually after returning from the interrupt that
cause the processor to re-awaken (LED1 will be off during the execution of
that interrupt). So a brighter LED1 means that the processor is spending
less time sleeping.
When my STM32 sits IDLE -- doing absolutely nothing but processing timer interrupts --
I see the following:
1. LED1 glows dimly due to the timer interrupts.
2. But LED2 is even more dim! The LED ON time excludes the time processing the
interrupt that re-awakens the processing. So this tells me that the STM32 is
spending more time processing timer interrupts than doing any other kind of
processing. That, of course, makes sense if the system is truly idle and only
processing timer interrupts.
Using OpenOCD and GDB with an FT2232 JTAG emulator
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

View File

@ -81,7 +81,7 @@ mount
selected as follows:
cd <nuttx-directory>/tools
./Configure.sh sim/mount
./configure.sh sim/mount
nettest
@ -90,7 +90,7 @@ nettest
be selected via:
cd <nuttx-directory>/tools
./Configure.sh sim/nettest
./configure.sh sim/nettest
NOTES:
- The NuttX network is not, however, functional on the Linux TAP
@ -112,14 +112,14 @@ nsh
may be selected as follows:
cd <nuttx-directory>/tools
./Configure.sh sim/nsh
./configure.sh sim/nsh
nx
Configures to use examples/nx. This configuration may be
selected as follows:
cd <nuttx-directory>/tools
./Configure.sh sim/nx
./configure.sh sim/nx
Special simulated framebuffer configuration options:
@ -155,7 +155,7 @@ ostest
configuration may be selected as follows:
cd <nuttx-directory>/tools
./Configure.sh sim/ostest
./configure.sh sim/ostest
pashello
@ -163,4 +163,4 @@ pashello
by selected as follows:
cd <nuttx-directory>/tools
./Configure.sh sim/pashello
./configure.sh sim/pashello