summaryrefslogtreecommitdiff
path: root/nuttx/configs
diff options
context:
space:
mode:
authorGregory Nutt <gnutt@nuttx.org>2015-03-27 10:47:03 -0600
committerGregory Nutt <gnutt@nuttx.org>2015-03-27 10:47:03 -0600
commit995317acc23b22d72562d72dadf2cee0a6aeba5e (patch)
tree885d7eb7fc487c2cb325ffb7f6587d4c4bafe22e /nuttx/configs
parent00d8ac3ba4966f96483d6d971aba88ffd97bb3d4 (diff)
downloadpx4-nuttx-995317acc23b22d72562d72dadf2cee0a6aeba5e.tar.gz
px4-nuttx-995317acc23b22d72562d72dadf2cee0a6aeba5e.tar.bz2
px4-nuttx-995317acc23b22d72562d72dadf2cee0a6aeba5e.zip
SAMV7 Ethernet+USB Updates
Diffstat (limited to 'nuttx/configs')
-rw-r--r--nuttx/configs/samv71-xult/README.txt26
1 files changed, 20 insertions, 6 deletions
diff --git a/nuttx/configs/samv71-xult/README.txt b/nuttx/configs/samv71-xult/README.txt
index a52fe1ee1..6870cbefa 100644
--- a/nuttx/configs/samv71-xult/README.txt
+++ b/nuttx/configs/samv71-xult/README.txt
@@ -83,15 +83,25 @@ The BASIC nsh configuration is fully function (as desribed below under
(of course with appropriate mounting and unmounting). I all not sure
of this and need to do more testing to characterize if the issue.
- 5. There is not yet any support for the following board features: QSPI, USB,
- EMAC, AT24, or WM8904 nor for any non-board features). Most of these
- drivers will port easily from either the SAM3/4 or from the SAMA5Dx.
+ 5. There is not yet any support for the following board features: QSPI or WM8904.
+ Many drivers will port easily from either the SAM3/4 or from the SAMA5Dx.
So there is still plenty to be done.
6. There has been a quick'n'dirty port of the SAMA5D4-EK Ethernet logic
- for the SAMV71-XULT. There are still some cache-related issues to
- be verified. No testing has yet been performed and so the driver should
- be considered non-functional.
+ for the SAMV71-XULT. It does not work properly. Data on the line
+ appears to be corrupted, probably at the level of the PHY.
+
+ 7. The USBHS device controller driver (DCD) is complete but non-functional.
+ At this point, work has stopped because I am stuck. The problem is that
+ bus events are not occurring: Nothing is detected by the USBHS when the
+ host is connected; no activity is seen on the bus by a USB analyzer when
+ the host is connected. Possibilities: (1) the pullups on DM and DP are
+ not working. This would prevent the host from detecting the presence of
+ the device. the DETACH bit is, however, being correctly cleared or (2)
+ some issue with clocking or configuration of the UTMI. I see nothing
+ wrong this this case. I have done extensive comparison of the Atmel
+ sample code and study of the data sheet, but I have not found the key to
+ solving this.
Serial Console
==============
@@ -926,3 +936,7 @@ Configuration sub-directories
# CONFIG_ARMV7M_ITCM is not set : Support not yet in place
# CONFIG_ARMV7M_DTCM is not set : Support not yet in place
+
+ Stack sizes are also large to simplify the bring-up and should be
+ tuned for better memory usages.
+