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

Update files to Nordic sdk 9.0.0 #8

Merged
merged 7 commits into from
Dec 23, 2015
Merged

Update files to Nordic sdk 9.0.0 #8

merged 7 commits into from
Dec 23, 2015

Conversation

LiyouZhou
Copy link
Contributor

Tests:

clitest - all expected passes pass, all expected fails fail.
build - all ble-examples build successfully
pstorage - tested against https://github.com/andresag01/ble-examples-1/tree/eddystone_pstorage and works
dfu - tested to work

Highlight from sdk 9 release notes:

Changes

  • Flash access module has been refactored (pstorage).

Fixed issues:

  • Pstorage now supports updates of bond split across two pages.
  • Advertising module can be set to infinite time-out.
  • Serialization HCI transport layer: Receiving packet-buffer is not
    freed while sending ACK or NACK.

Known issues:

  • Device Manager is not supported in multi-role S130 operation.
    • Device Manager works in peripheral or central only operation on
      S130. This must be decided at compile time.
  • The DFU over BLE example has been tested to work with a minimum
    connection interval of 11.25 ms. The application cannot handle
    connection intervals lower than 11.25 ms and may undergo a system
    reset in the middle of a firmware update.
    Workaround: If you face unexpected disconnects during the firmware
    update process, consider increasing the connection interval used
    by the master.
  • App_pwm occasionally gives inverted signal.
  • The old manual procedure for testing buttonless DFU, as specified in
    the documentation, can lead to the DFU process hanging or returning
    an error when used with Master Control Panel 3.8 and newer.

@ARMmbed/ble-owners Please review.

@@ -39,7 +39,7 @@
#include <string.h>
#include "nordic_common.h"
#include "app_error.h"

#include "ble.h"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this the ble.h from Nordic-SDK as opposed to ble/BLE.h? is there a potential for misinterpretation?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rgrover In theory, all files including ble.h should only find ble.h as BLE.h is not exposed with extraIncludes. All files intending to use BLE.h would use ble/BLE.h. The problem only comes if a file, intending to use BLE.h, uses #include BLE.h, on mac os, this can find ble.h instead.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and on windows too right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jrobeson Yes it can be a problem on windows as well. So you should always use #include ble/BLE.h to use the BLE API.

@rgrover
Copy link
Contributor

rgrover commented Dec 14, 2015

@LiyouZhou please confirm that the bootloader is still able to build and work correctly with this new SDK. I have a feeling you'll find that the bootloader doesn't work any more unless you fix the constants in hci_mem_pool_internal.h (see comments above).
Jonny is currently attempting to build the bootloader for BBC. Please connect with him to align with his efforts.

Please also ensure that the memory consumption doesn't go up with this new SDK. Building any of our examples should show the heap sizes at the end. This is important.

@rgrover
Copy link
Contributor

rgrover commented Dec 14, 2015

I would like you to discuss your approach with others members of the team. Please document the affects of switching to the new SDK; we need to ensure that we don't affect existing functionality--such as use of pstorage, bootloader, etc. Could you also please highlight the important parts of the release notes for SDKv9?

@rgrover
Copy link
Contributor

rgrover commented Dec 14, 2015

@LiyouZhou please also be mindful that we need to hand-apply the changes from SDKv9 to the ble-nrf51822 repository on mbed.org. That repository will no longer automatically sync with the changes to the SDK.

@@ -68,8 +69,6 @@
#define BLE_UUID_RUNNING_SPEED_AND_CADENCE 0x1814 /**< Running Speed and Cadence service UUID. */
#define BLE_UUID_SCAN_PARAMETERS_SERVICE 0x1813 /**< Scan Parameters service UUID. */
#define BLE_UUID_TX_POWER_SERVICE 0x1804 /**< TX Power service UUID. */
#define BLE_UUID_IPSP_SERVICE 0x1820 /**< Internet Protocol Support service UUID. */

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting this UUID has been removed from the Nordic SDK. I wonder if that has something to do with their new IP strategy.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@LiyouZhou could you check if this UUID is still removed in v10?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rgrover @marcuschangarm It is reintroduced in v10

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

must be an oversight then.

@LiyouZhou
Copy link
Contributor Author

@rgrover
pstorage cmd queue size reduced to 2 in new commit.
Mem usage increased by 24bytes as a result of updating the sdk.
Bootloader continue to work.

@rgrover
Copy link
Contributor

rgrover commented Dec 14, 2015

@LiyouZhou you claim: Mem usage increased by 24bytes as a result of updating the sdk.
Can you account for this?

@LiyouZhou
Copy link
Contributor Author

@rgrover by looking at the obj-dump the major refactorying of pstorage.c caused this increase. There is a lot of change, hence it is difficult to tell exactly what cause memory increase.

@rgrover
Copy link
Contributor

rgrover commented Dec 14, 2015

@LiyouZhou ok. Thanks for this dive. 24bytes isn't too much to worry about.

@LiyouZhou
Copy link
Contributor Author

@rgrover hold off merging, need to talk to jonny and make a small change.

@ghost
Copy link

ghost commented Dec 22, 2015

sdk10 has a fix for "App_pwm occasionally gives inverted signal"

@LiyouZhou
Copy link
Contributor Author

@jrobeson I'm currently in the process of upgrading to v10. Should be up shortly.

LiyouZhou added a commit that referenced this pull request Dec 23, 2015
Update files to Nordic sdk 9.0.0 - Merging to prepare for v10 PR
@LiyouZhou LiyouZhou merged commit 164b319 into master Dec 23, 2015
@LiyouZhou LiyouZhou deleted the nordic_sdk_9.0.0 branch January 7, 2016 16:02
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.

3 participants