mirror of
https://github.com/apache/nuttx.git
synced 2026-06-05 07:12:54 +08:00
Fix typos in comments and documentation.
This commit is contained in:
committed by
patacongo
parent
430a2178fb
commit
a5e643b0cd
@@ -32,7 +32,7 @@ Status
|
||||
for recovery from this condition at: https://community.nxp.com/thread/505593 .
|
||||
But none of those options are working for me.
|
||||
|
||||
Give the success running of of SRAM and the success of the same fixes
|
||||
Give the success running of SRAM and the success of the same fixes
|
||||
on the S32K118, I believe that the NSH configuration should now run out
|
||||
of FLASH. Unfortunately, I cannot demonstrate that.
|
||||
|
||||
|
||||
@@ -37,7 +37,7 @@ STATUS/ISSUES
|
||||
|
||||
2. Garbage appears on the display sometimes after a reset (maybe 20% of
|
||||
the time) or after a power cycle (less after a power cycle). I don't
|
||||
understand the cause of of this but most of this can be eliminated by
|
||||
understand the cause of this but most of this can be eliminated by
|
||||
simply holding the reset button longer and releasing it cleanly
|
||||
(then it fails maybe 5-10% of the time, maybe because of button
|
||||
chatter?) (2014-2-18).
|
||||
|
||||
@@ -336,7 +336,7 @@
|
||||
* CPU frequency = 120MHz / 1 = 120MHz
|
||||
*/
|
||||
|
||||
#define BOARD_MCLK_CPUDIV 1 /* MCLK divder to get CPU frequency */
|
||||
#define BOARD_MCLK_CPUDIV 1 /* MCLK divider to get CPU frequency */
|
||||
|
||||
/* Peripheral clocking */
|
||||
|
||||
|
||||
@@ -336,7 +336,7 @@
|
||||
* CPU frequency = 120MHz / 1 = 120MHz
|
||||
*/
|
||||
|
||||
#define BOARD_MCLK_CPUDIV 1 /* MCLK divder to get CPU frequency */
|
||||
#define BOARD_MCLK_CPUDIV 1 /* MCLK divider to get CPU frequency */
|
||||
|
||||
#define BOARD_MCK_FREQUENCY BOARD_GCLK0_FREQUENCY
|
||||
|
||||
|
||||
@@ -904,7 +904,7 @@ Click Shield
|
||||
click mikroBUSes. The above discusses on the UNO shield. I know that the
|
||||
serial ports, at least, differ on the two shields.
|
||||
|
||||
UPDATE: And it appears the that Mega shield is *not* compatible with the
|
||||
UPDATE: And it appears that the Mega shield is *not* compatible with the
|
||||
SAME70-Xplained. I am told that the SPI in mikroBUS slots does not connect
|
||||
to pins on the SAME70-Xplained that can support the SPI communications.
|
||||
Avoid this triple mikroBUS shield!
|
||||
|
||||
@@ -370,9 +370,9 @@ Common Configuration Notes
|
||||
b. Execute 'make menuconfig' in nuttx/ in order to start the
|
||||
reconfiguration process.
|
||||
|
||||
3. By default, all configurations assume the that you are building under
|
||||
under Linux (should work under Windows with Cygwin as well). This
|
||||
is easily reconfigured:
|
||||
3. By default, all configurations assume that you are building under
|
||||
Linux (should work under Windows with Cygwin as well). This is
|
||||
easily reconfigured:
|
||||
|
||||
CONFIG_HOST_LINUX=y
|
||||
|
||||
|
||||
@@ -477,9 +477,9 @@ Common Configuration Notes
|
||||
b. Execute 'make menuconfig' in nuttx/ in order to start the
|
||||
reconfiguration process.
|
||||
|
||||
3. By default, all configurations assume the that you are building under
|
||||
under Linux (should work under Windows with Cygwin as well). This
|
||||
is easily reconfigured:
|
||||
3. By default, all configurations assume that you are building under
|
||||
Linux (should work under Windows with Cygwin as well). This is
|
||||
easily reconfigured:
|
||||
|
||||
CONFIG_HOST_LINUX=y
|
||||
|
||||
|
||||
Reference in New Issue
Block a user