Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for EMAC backhaul driver #85

Merged
merged 5 commits into from May 31, 2018
Merged

Add support for EMAC backhaul driver #85

merged 5 commits into from May 31, 2018

Conversation

kjbracey
Copy link
Contributor

@kjbracey kjbracey commented Jan 26, 2018

Add new EMAC backhaul driver option that uses new mbed OS 5.9 EMAC and default network interface APIs. This should work for any Ethernet EMAC driver, and can work with appropriately-engineered Wifi drivers - see README.md for more details.

@kjbracey
Copy link
Contributor Author

This requires ARMmbed/mbed-os#5944

@kjbracey
Copy link
Contributor Author

Reworked to use default network interface API.

Still not switched the default to EMAC. Guess we should?

@kjbracey
Copy link
Contributor Author

Note EMAC K64F driver still suffers from "cable disconnect start-up jam" so would be a functional regression from Nanostack version.

Add new EMAC backhaul driver option that uses new mbed OS 5.9 EMAC and
default network interface APIs. This should work for any Ethernet EMAC
driver, and can work with appropriately-engineered Wifi drivers - see
README.md for more details.
EMAC changes increase static allocation, meaning we don't quite fit in
an IAR K64F build any more.
No longer builds with mbed OS 5.9 due to collision with EMAC driver.
That EMAC driver is now usable, so no need for the Nanostack one
anyway.
Change JSON files to select EMAC driver, rather than native Nanostack.
This is currently a minor functional regression for K64F - the EMAC
driver doesn't start gracefully if the cable isn't connected.
@kjbracey kjbracey merged commit bbeea30 into master May 31, 2018
@kjbracey kjbracey deleted the emac_support branch May 31, 2018 12:28
@cmonr
Copy link
Contributor

cmonr commented Jun 4, 2018

FYI, it looks like this commit is causing the currently generated 5.8.6 patch release to not build, due to the new config options.

[mbed] Working path "/builds/ws/mbed-os-build-matrix/2235/K64F_ARM/sources/examples/mbed-os-example-filesystem" (directory)
[mbed] Exec "/usr/bin/python -u /builds/ws/mbed-os-build-matrix/2235/K64F_ARM/sources/examples/mbed-os-example-filesystem/mbed-os/tools/make.py -t ARM -m K64F --source . --build ./BUILD/K64F/ARM -v" in /builds/ws/mbed-os-build-matrix/2235/K64F_ARM/sources/examples/mbed-os-example-filesystem
Compiling nanostack-border-router for K64F, ARM
Building project nanostack-border-router (K64F, ARM)
Scan: .
Scan: env
Scan: mbed
Scan: FEATURE_COMMON_PAL
Scan: FEATURE_STORAGE
Scan: FEATURE_NANOSTACK
Traceback (most recent call last):
  File "/builds/ws/mbed-os-build-matrix/2235/K64F_ARM/sources/examples/nanostack-border-router/mbed-os/tools/make.py", line 298, in <module>
    stats_depth=options.stats_depth)
  File "/builds/ws/mbed-os-build-matrix/2235/K64F_ARM/sources/examples/nanostack-border-router/mbed-os/tools/build_api.py", line 583, in build_project
    resources = scan_resources(src_paths, toolchain, inc_dirs=inc_dirs)
  File "/builds/ws/mbed-os-build-matrix/2235/K64F_ARM/sources/examples/nanostack-border-router/mbed-os/tools/build_api.py", line 498, in scan_resources
    resources = toolchain.config.load_resources(resources)
  File "/builds/ws/mbed-os-build-matrix/2235/K64F_ARM/sources/examples/nanostack-border-router/mbed-os/tools/config/__init__.py", line 1028, in load_resources
    self.validate_config()
  File "/builds/ws/mbed-os-build-matrix/2235/K64F_ARM/sources/examples/nanostack-border-router/mbed-os/tools/config/__init__.py", line 992, in validate_config
    raise self.config_errors[0]
ConfigException: Attempt to override undefined parameter 'nsapi.default-stack' in 'application[*]'

Does this application still build in 5.8?

@adbridge
Copy link
Contributor

adbridge commented Jun 4, 2018

@kjbracey-arm Changes for 5.9 should not land on master until 5.9 is released as this breaks 5.8 compatibility. Instead these changes should have gone on the OOB branch. Can you please do that and restore master to 5.8 compatibility.

kjbracey added a commit that referenced this pull request Jun 5, 2018
Revert EMAC changes pending 5.9.0 release.

This reverts commits 8703cf7..935d777 (PRs #85 and #108).
kjbracey added a commit that referenced this pull request Jun 5, 2018
Revert EMAC changes pending 5.9.0 release.

This reverts commits 918feb6..935d777 (PRs #85 and #108).
kjbracey added a commit that referenced this pull request Jun 5, 2018
Revert EMAC changes pending 5.9.0 release.

This reverts commits 918feb6..935d777 (PRs #85 and #108).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants