summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGregory Nutt <gnutt@nuttx.org>2014-11-21 14:05:20 -0600
committerGregory Nutt <gnutt@nuttx.org>2014-11-21 14:05:20 -0600
commitb386491accf6bb557a98c26324a40702c76f52b1 (patch)
tree4aa98bcfc290faa42fb1de28600892da9e179ecf
parentbd2bbbd424a653830e8dc43ce8c8de63a35311ed (diff)
downloadnuttx-b386491accf6bb557a98c26324a40702c76f52b1.tar.gz
nuttx-b386491accf6bb557a98c26324a40702c76f52b1.tar.bz2
nuttx-b386491accf6bb557a98c26324a40702c76f52b1.zip
Update READMEs
-rw-r--r--nuttx/configs/efm32gg-stk3700/README.txt5
-rw-r--r--nuttx/configs/sama5d3-xplained/README.txt14
2 files changed, 19 insertions, 0 deletions
diff --git a/nuttx/configs/efm32gg-stk3700/README.txt b/nuttx/configs/efm32gg-stk3700/README.txt
index 0f236edd9..15bc1b549 100644
--- a/nuttx/configs/efm32gg-stk3700/README.txt
+++ b/nuttx/configs/efm32gg-stk3700/README.txt
@@ -32,6 +32,11 @@ STATUS
on LEUART0.
2014-11-14: LEUART0 BAUD increased from 2400 to 9600. Calibrated delay
loop.
+ 2014-11-18: Added basic drivers for USB device and host. The initial port
+ is a simple leverage from the STM32 which appears to use the same IP.
+ The current state is just the STM32 USB drivers with the appropriate.
+ The USB drivers still lack EFM32 initialization logic and are, of course,
+ completely untested.
LEDs and Buttons
================
diff --git a/nuttx/configs/sama5d3-xplained/README.txt b/nuttx/configs/sama5d3-xplained/README.txt
index 50c65eb2b..d3baba574 100644
--- a/nuttx/configs/sama5d3-xplained/README.txt
+++ b/nuttx/configs/sama5d3-xplained/README.txt
@@ -2907,12 +2907,26 @@ Configurations
the warning in the section "Information Common to All Configurations"
for further information.
+ 3. You will almost certainly need to adapt this configuration to
+ work in your network environment. I did all testing with a
+ single 10.0.0.xx network and a 4+1 port switch:
+
+ - Host PC IP 10.0.0.1
+ - Target GMAC IP: 10.0.0.2
+ - Target EMAC IP: 10.0.0.3
+
+ Host, EMAC, and GMAC were all connected using a switch.
+
STATUS:
2014-11-20: Configuration created. Partially verified. Both the
EMAC and GMAC appear to be function; both respond to pings from
the host PC. But I cannot perform the full bridge test yet
because there still is no host-side test driver in apps/examples/bridge.
+ 2014-11-21: Added the host-side test driver and correct a number
+ of errors in the test logic. The testing is working (according
+ to WireShark), but I an having some procedural issues related to
+ the Windows firewall.
nsh: