diff options
| author | patacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3> | 2012-08-07 23:51:47 +0000 |
|---|---|---|
| committer | patacongo <patacongo@42af7a65-404d-4744-a932-0658087f49c3> | 2012-08-07 23:51:47 +0000 |
| commit | f421a4b42eb88ce7ac1d121e2f01a27c1928031f (patch) | |
| tree | c97f4d8e7efed7d9a82beb4d04cb6fdfa804fd7c /nuttx/Documentation/NuttShell.html | |
| parent | 4017253a669e2647cdf54e27d1ae952d994361d3 (diff) | |
| download | px4-nuttx-f421a4b42eb88ce7ac1d121e2f01a27c1928031f.tar.gz px4-nuttx-f421a4b42eb88ce7ac1d121e2f01a27c1928031f.tar.bz2 px4-nuttx-f421a4b42eb88ce7ac1d121e2f01a27c1928031f.zip | |
Add a USB0 device header file for LPC43
git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@5016 42af7a65-404d-4744-a932-0658087f49c3
Diffstat (limited to 'nuttx/Documentation/NuttShell.html')
| -rw-r--r-- | nuttx/Documentation/NuttShell.html | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/nuttx/Documentation/NuttShell.html b/nuttx/Documentation/NuttShell.html index a92cbadd8..ca7e82627 100644 --- a/nuttx/Documentation/NuttShell.html +++ b/nuttx/Documentation/NuttShell.html @@ -8,7 +8,7 @@ <tr align="center" bgcolor="#e4e4e4"> <td> <h1><big><font color="#3c34ec"><i>NuttShell (NSH)</i></font></big></h1> - <p>Last Updated: August 3, 2012</p> + <p>Last Updated: August 7, 2012</p> </td> </tr> </table> @@ -1210,7 +1210,7 @@ losetup [-o <offset>] [-r] <dev-path> <file-path> <p> <b>Synopsis</b>. Setup the loop device at <dev-path> to access the file at <file-path> as a block device. - In the following example a 256Kb file is created (<code>dd</code>) and <code>losetup</code> is + In the following example a 256K file is created (<code>dd</code>) and <code>losetup</code> is used to make the file accessible as a block device. A FAT file system is created (<code>mkfatfs</code>) and mounted (<code>mount</code>). Files can then be managed on the loop-mounted file. @@ -3148,7 +3148,7 @@ endef </p> <li> <p> - The make file then defines the application name (<code>hello</code>), the task priority (default), and the stack size that will be allocated in the task runs (2Kb). + The make file then defines the application name (<code>hello</code>), the task priority (default), and the stack size that will be allocated in the task runs (2K). </p> <ul><pre> APPNAME = hello @@ -3160,7 +3160,7 @@ STACKSIZE = 2048 <p> And finally, the <code>Makefile</code> invokes the <code>REGISTER</code> macro to added the <code>hello_main()</code> named application. Then, when the system build completes, the <code>hello</code> command can be executed from the NSH command line. - When the <code>hello</code> command is executed, it will start the task with entry point <code>hello_main()</code> with the default priority and with a stack size of 2Kb. + When the <code>hello</code> command is executed, it will start the task with entry point <code>hello_main()</code> with the default priority and with a stack size of 2K. </p> <ul><pre> .context: |