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

Upgrade Silicon Labs radio driver to v2.1.1 #5579

Merged
merged 4 commits into from Nov 30, 2017

Conversation

Projects
None yet
5 participants
@stevew817
Contributor

stevew817 commented Nov 24, 2017

Description

Upgrades the RAIL library (on which the Nanostack driver is based) from v1.5.x to v2.1.1. The upgrade from 1.x to 2.x includes a whole lot of API changes, but in the end, makes RAIL more efficiently run alongside an RTOS.

Additional improvements:

  • Stubs for all events
  • Binary should now be fully AAPCS-compliant (no more ambiguity on enum size), so should work across toolchains
  • Added EFR32_x flags to remove hard dependency on Mighty Gecko parts (should work on BG and FG parts too, even though they don't have mbed-enabled development kits).
  • Lays the foundation for potential BLE enablement on EFR32

Status

READY

Migrations

No behavioral change intended, no external API changes.

@0xc0170 0xc0170 requested a review from SeppoTakalo Nov 24, 2017

@stevew817

This comment has been minimized.

Contributor

stevew817 commented Nov 24, 2017

Also resolves #5382

@stevew817 stevew817 force-pushed the SiliconLabs:feature/rail-2.1 branch to 812e47c Nov 24, 2017

stevew817 added some commits Nov 24, 2017

Clear TX FIFO on every transmit
Need to avoid a TX packet error from messing up the TX FIFO. Since this API will return busy if a packet is in transmission anyways, this is acceptable.
@stevew817

This comment has been minimized.

Contributor

stevew817 commented Nov 24, 2017

@0xc0170 0xc0170 added needs: CI and removed needs: review labels Nov 29, 2017

@0xc0170

This comment has been minimized.

Member

0xc0170 commented Nov 29, 2017

/morph build

@mbed-ci

This comment has been minimized.

mbed-ci commented Nov 29, 2017

Build : SUCCESS

Build number : 618
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/5579/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build

@0xc0170

This comment has been minimized.

Member

0xc0170 commented Nov 29, 2017

@orenc17A Please review the failure for uvisor CI. Seems like target interface related

@mbed-ci

This comment has been minimized.

@mbed-ci

This comment has been minimized.

@stevew817

This comment has been minimized.

Contributor

stevew817 commented Nov 30, 2017

@0xc0170 Seems the failure is gone now?

@0xc0170 0xc0170 merged commit 118c1bb into ARMmbed:master Nov 30, 2017

6 checks passed

AWS-CI uVisor Build & Test Success
Details
ci-morph-build build completed
Details
ci-morph-exporter build completed
Details
ci-morph-test test completed
Details
continuous-integration/jenkins/pr-head This commit looks good
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
@ryankurte

This comment has been minimized.

Contributor

ryankurte commented Dec 18, 2017

@stevew817 is there a reason this doesn't include the ieee802154_subg_efr32xg12_configurator_out source/header files? (And are these generated from the default options in the configurator?)

-edit s\efr32xg1\efr32xg12\g-

@ryankurte

This comment has been minimized.

Contributor

ryankurte commented Dec 18, 2017

Follow up: this seems to need some modification to get it working.

With a quick-and-dirty copy of the configurator files the updated version results in a Thread 0x0 error -4: Parameter error which appears to originate somewhere in the depths of rf_device_register function. I can not however debug this because of the rail blob.

Shall I open another issue against this?

@stevew817

This comment has been minimized.

Contributor

stevew817 commented Dec 18, 2017

@ryankurte Yes, please log a separate issue. Not sure why they disappeared, but I'll look into it.

@SeppoTakalo

This comment has been minimized.

Contributor

SeppoTakalo commented Dec 18, 2017

This Thread error might be related to #5680 and #5587

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment