apps/-related update

git-svn-id: svn://svn.code.sf.net/p/nuttx/code/trunk@3377 42af7a65-404d-4744-a932-0658087f49c3
This commit is contained in:
patacongo 2011-03-13 19:04:32 +00:00
parent d146196b72
commit 969158ca0f
3 changed files with 56 additions and 2 deletions

17
TODO
View File

@ -8,7 +8,7 @@ NuttX TODO List (Last updated March 8, 2011)
(1) pthreads (sched/)
(1) C++ Support
(5) Binary loaders (binfmt/)
(16) Network (net/, drivers/net)
(17) Network (net/, drivers/net)
(5) Network Utilities (netutils/)
(2) USB (drivers/usbdev, drivers/usbhost)
(5) Libraries (lib/)
@ -30,6 +30,7 @@ NuttX TODO List (Last updated March 8, 2011)
(3) ARM/STR71x (arch/arm/src/str71x/)
(4) ARM/LM3S6918 (arch/arm/src/lm3s/)
(4) ARM/STM32 (arch/arm/src/stm32/)
(1) Intel x86 (arch/x86)
(4) 8051 / MCS51 (arch/8051/)
(2) Hitachi/Renesas SH-1 (arch/sh/src/sh1)
(4) Renesas M16C/26 (arch/sh/src/m16c)
@ -307,6 +308,13 @@ o Network (net/, drivers/net)
the mechanism for leaving and joining groups is hidden behind a wrapper
function so that little of this incompatibilities need be exposed.
Description: The SLIP driver (drivers/net/slip.c) has had only the most superficial
testing. The main issue is the I haven't yet gotten a dual UART Linux
configuration that supports SLIP (I need one UART for SLIP and one for
the serial debug console).
Status: Open
Priority: Medium
o Network Utilities (netutils/)
Description: One critical part of netutils/ apps is untested: The uIP
@ -922,6 +930,13 @@ o ARM/STM32 (arch/arm/src/stm32/)
Priority: Low until someone needs DMA1, Channel 5 (ADC3, UART4_TX, TIM5_CH1, or
TIM8_CH2).
o Intel x86 (arch/x86)
^^^^^^^^^^^^^^^^^^^^
Description: No timer interrupts in the QEMU configuration.
Status: Open
Priorty: Medium-High
o 8051 / MCS51 (arch/8051/)
^^^^^^^^^^^^^^^^^^^^^^^^^

View File

@ -806,6 +806,32 @@ Where <subdir> is one of the following:
Ethernet data link layer. The Ethernet driver is disabled; SLIP IP
packets are exchanged on UART1; UART0 is still the serial console.
1. Configure and build the slip-httpd configuration.
2. Connect to a Linux box (assuming /dev/ttyS0)
3. Reset on the target side / attach SLIP on the Linux side:
$ slattach -p slip -s 57600 /dev/ttyS0 &
This should create an interface with a name like sl0. Add -d to
get debug output. In the naming, slN, the N corresponds to the
tty device number as in /dev/ttySN.
4. After turning over the line to the SLIP driver, you must configure
the network interface. Again, you do this using the standard
ifconfig and route commands. Assume that we have connected to a
host PC with address 192.168.0.101 from your target with address
10.0.0.2. On the Linux PC you would execute the following as root:
$ ifconfig sl0 192.168.0.101 pointopoint 10.0.0.2 up -OR?-
$ ifconfig sl0 10.0.0.2 pointopoint 192.168.0.101 up
$ route add 10.0.0.2 dev sl0
Assuming the SLIP is attached to device sl0.
[ NOTE: As of this writing, I actually have not yet successfully ]
[ configured SLIP on Linux. The above are really just my working notes. ]
[ I suspect that I may have the IP address backward for one thing. ]
thttpd:
This builds the THTTPD web server example using the THTTPD and
the examples/thttpd application.

View File

@ -88,13 +88,26 @@
int nsh_execapp(FAR struct nsh_vtbl_s *vtbl, const char *cmd, char *argv[])
{
int ret = OK;
const char * name;
/* Try to find command within pre-built application list. */
ret = exec_nuttapp(cmd, argv);
if (ret < 0)
{
return -errno;
int err = -errno;
int i;
/* On failure, list the set of available built-in commands */
nsh_output(vtbl, "Builtin Apps: ");
for (i = 0; name = nuttapp_getname(i); i++)
{
nsh_output(vtbl, "%s ", name);
}
nsh_output(vtbl, "\nand type 'help' for more NSH commands.\n\n");
return err;
}
#ifdef CONFIG_SCHED_WAITPID