Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
NuttX RTOS
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Container Registry
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
f4grx
NuttX RTOS
Commits
7fa3362a
Commit
7fa3362a
authored
10 years ago
by
Gregory Nutt
Browse files
Options
Downloads
Patches
Plain Diff
Update READMEs
parent
690d9fc2
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
configs/efm32gg-stk3700/README.txt
+5
-0
5 additions, 0 deletions
configs/efm32gg-stk3700/README.txt
configs/sama5d3-xplained/README.txt
+14
-0
14 additions, 0 deletions
configs/sama5d3-xplained/README.txt
with
19 additions
and
0 deletions
configs/efm32gg-stk3700/README.txt
+
5
−
0
View file @
7fa3362a
...
...
@@ -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
================
...
...
This diff is collapsed.
Click to expand it.
configs/sama5d3-xplained/README.txt
+
14
−
0
View file @
7fa3362a
...
...
@@ -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:
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment