• State Verified Answer
  • Replies 12 replies
  • Subscribers 62 subscribers
  • Views 9024 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 106143
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Configuring Software Pack Libraries in Keil

mst

I'm using the latest version of Keil with Software Packs. As I understood, copies of configurable files are stored in RTE folder. Non-configurable files are stored inside Keil folder structure and projects have only links to them.

For the bootloader example (dfu_dual_bank_ble_s110_pca10028) I want to change the DFU_APP_DATA_RESERVED. I do so by changing the parameter in dfu_types.h stored in the RTE folder. But this does not work, as the bootloader_settings_arm.c file from the software pack does not include the configurable file from the RTE folder, but the read-only, non-configurable, file from the Software Pack...

How to make the files from the Software Pack include the configurable files?

Configurable file:

image description

File used by bootloader:

image description

Parents
  • 0

    As I see you have already noticed, modifying library files or drivers is pretty troublesome when using packs. I have at this point no further recommendation other than already mentioned on this thread on how to tackle the problem when using packs. We have worked around this by simply using the conventional SDK folder structure instead, i.e. without packs, also available for all our SDKs on developer.nordicsemi.com. How to use the conventional SDK folder structure with the latest Keil 5 version is straightforward, described here, and that is what we currently recommend for customers that want to modify library files or drivers in the SDK.

    Update 27.3.2015 The bootloader_settings_arm.c file was made locked by mistake. It will be made configurable, hopefully in the next version of the SDK.

Reply
  • 0

    As I see you have already noticed, modifying library files or drivers is pretty troublesome when using packs. I have at this point no further recommendation other than already mentioned on this thread on how to tackle the problem when using packs. We have worked around this by simply using the conventional SDK folder structure instead, i.e. without packs, also available for all our SDKs on developer.nordicsemi.com. How to use the conventional SDK folder structure with the latest Keil 5 version is straightforward, described here, and that is what we currently recommend for customers that want to modify library files or drivers in the SDK.

    Update 27.3.2015 The bootloader_settings_arm.c file was made locked by mistake. It will be made configurable, hopefully in the next version of the SDK.

Children
Related