Skip to content

Move FEATURE_IPV6 from mbed-os to here. #2207

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

Closed
wants to merge 4 commits into from
Closed

Move FEATURE_IPV6 from mbed-os to here. #2207

wants to merge 4 commits into from

Conversation

SeppoTakalo
Copy link
Contributor

Contains same version of libraries as #453

Tagged versions

  • mbed-mesh-api mbed-os-5.0-rc1
  • mbed-trace mbed-os-5.0-rc1
  • nanostack-hal-cmsis-rtos mbed-os-5.0-rc1
  • nanostack-interface copied. no remote repository
  • nanostack-libservice mbed-os-5.0-rc1
  • sal-stack-nanostack mbed-os-5.0-rc1 Binaries generated from v5.0.5

@SeppoTakalo
Copy link
Contributor Author

@sg- @0xc0170 Please review

@sg-
Copy link
Contributor

sg- commented Jul 21, 2016

@SeppoTakalo I only see a M3 build. I thought there was going to be a M0 build as well.

@SeppoTakalo
Copy link
Contributor Author

@sg- Now Cortex-M0, M0+, M3 and M4 libraries are there.

I did not create symlinks, because I don't know if those work on Windows.

@0xc0170
Copy link
Contributor

0xc0170 commented Jul 22, 2016

+1

@sg-
Copy link
Contributor

sg- commented Jul 22, 2016

@SeppoTakalo Its failing to respond to ping with mesh-minimal example. Can you check this?

@geky
Copy link
Contributor

geky commented Jul 22, 2016

Hi @SeppoTakalo, I know this is a change, but would it be possible to move FEATURE_IPV6 into features/net to match the organization of network related features? features/net/FEATURE_IPV6

related prs #2231, #2216

@c1728p9
Copy link
Contributor

c1728p9 commented Jul 23, 2016

@SeppoTakalo, I tried out the m3/m4 and I can get thread to work, but not 6lowpan. It looks like 6lowpan didn't get fully compiled in. I also tried using the m0/m0+ library on a K64F (since the m3/m4 library was broken) but I get link errors like this:

libnanostack_arm-none-eabi-gcc_Cortex-M0.a(security_lib.o): In function `sec_ecc_state_free':
security_lib.c:(.text+0xec): undefined reference to `ecc_free_memory'

Contains same version of libraries as #453

Tagged versions
* mbed-mesh-api mbed-os-5.0-rc1
* mbed-trace mbed-os-5.0-rc1
* nanostack-hal-cmsis-rtos mbed-os-5.0-rc1
* nanostack-interface copied. no remote repository
* nanostack-libservice mbed-os-5.0-rc1
* sal-stack-nanostack mbed-os-5.0-rc1 Binaries generated from v5.0.5
@SeppoTakalo
Copy link
Contributor Author

SeppoTakalo commented Jul 25, 2016

Verified: GCC modules (at least) are broken. I think I have accidentally build them with some other than mbedOS configuration of stack.
I will do rebasing and updating immediately.
I will also study how to build the Cortex-A modules (in progress).

Thanks for reporting and testing this. Sorry for the trouble.

Seppo Takalo added 2 commits July 25, 2016 11:58
Use M0 build for both M0 and M0+
Use M3 build for both M3 and M3
Use Cortex-A5 build for all Cortex-A cores.
@SeppoTakalo
Copy link
Contributor Author

Wait.. why did Github closed this.. maybe because I updated my branch...

@SeppoTakalo SeppoTakalo reopened this Jul 25, 2016
@SeppoTakalo
Copy link
Contributor Author

OK. Now libraries updated.
6LoWPAN seems to work.
Thread tests pending... waiting for BR build.

@SeppoTakalo
Copy link
Contributor Author

Also added Cortex-A libraries.

@SeppoTakalo
Copy link
Contributor Author

Verified with these binaries:
mesh-minimal with 6LoWPAN: works
mesh-minimal with Thread: works
K64F border router with 6LoWPAN: works
K64F border router with Thread: works. (not public)

Problems with thread were in application side configuration on border router. PR's submitted to Thread testapps.

@geky
Copy link
Contributor

geky commented Jul 25, 2016

Thanks for moving this last minute 👍

@sg-
Copy link
Contributor

sg- commented Jul 26, 2016

landed by way of #2249

@sg- sg- closed this Jul 26, 2016
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.

5 participants