Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs

how to update MDK to handle APPROTECT

Hi,

Update MDK to handle APPROTECT, MDK can be downloaded from MDK website, but no details on hot to update MDK to nRF5 SDK. Any guide lines to update the MDK with nRF5 SDK v17.0.2?

tried to update over the tools->package manager with Segger embedded studio, it could install the MDK package this way.  but after open the sample projects from nRF5 SDK, the source files still linked to the nRF5 SDK folder and not the latest version, and doesn't handle APPROTECT. 

As nRF5 SDK v17.1.0 can handle APPROTECT, tried copy a nRF5 SDK v17.0.2 based example project to SDK V17.1.0 which can't compile and complaining missing files.

Is it correct that MDK update has to be manually done by replacing the header/source files with each project (within the IDE). or ok to just replacing some files in the older nRF5 SDK and good for all sample projects.

Parents
  • Hi,

    Updating of the MDK for Segger Embedded Studio depends on which SDK version you are upgrading, and which OS you are using.

    When installing the updated MDK version for SES, it will by default be placed in these locations:

    • Windows: %APPDATA%\..\Local\SEGGER\SEGGER Embedded Studio\v3\packages\nRF
    • Mac: ~/Library/SEGGER/SEGGER Embedded Studio/v3/packages/nRF
    • Linux: ~/.segger/SEGGER Embedded Studio/v3/packages/nRF
    The SDK examples are setup to reference the MDK files local to the SDK. You either have to refer to the files in above mentioned paths from the project, or you can copy the files into the SDK.
    Copying the updated MDK files to the SDK should work for all projects in the SDK, while referencing the new location will have to be done for each project.
    For nRF5 SDK 15.0.0 and newer, the relevant MDK files can ble placed directly in <sdk root folder>/modules/nrfx/mdk/, replacing the existing files there. You need to copy files from multiple folders inside the nRF/Device/ folder.
    For nRF5 SDK 14.2.0 and older it's a bit more complicated, and you need to copy:
    • to <sdk root>\components\device:
      • various .h files found in the MDK install at nRF/Device/Include
    • to <sdk root>\components\toolchain:
      • system_nrf*.c files, found in the MDK install at nRF/Device/Source
      • system_nrf*.h files, found in the MDK install at nRF/Device/Include
    • to <sdk root>\svd:
      • *.svd files found in the MDK install at nRF/Device/Registers

    Another option is to copy the MDK directory from SDK 17.1.0 and replace it in SDK 17.0.2.

    Best regards,
    Jørgen

Reply
  • Hi,

    Updating of the MDK for Segger Embedded Studio depends on which SDK version you are upgrading, and which OS you are using.

    When installing the updated MDK version for SES, it will by default be placed in these locations:

    • Windows: %APPDATA%\..\Local\SEGGER\SEGGER Embedded Studio\v3\packages\nRF
    • Mac: ~/Library/SEGGER/SEGGER Embedded Studio/v3/packages/nRF
    • Linux: ~/.segger/SEGGER Embedded Studio/v3/packages/nRF
    The SDK examples are setup to reference the MDK files local to the SDK. You either have to refer to the files in above mentioned paths from the project, or you can copy the files into the SDK.
    Copying the updated MDK files to the SDK should work for all projects in the SDK, while referencing the new location will have to be done for each project.
    For nRF5 SDK 15.0.0 and newer, the relevant MDK files can ble placed directly in <sdk root folder>/modules/nrfx/mdk/, replacing the existing files there. You need to copy files from multiple folders inside the nRF/Device/ folder.
    For nRF5 SDK 14.2.0 and older it's a bit more complicated, and you need to copy:
    • to <sdk root>\components\device:
      • various .h files found in the MDK install at nRF/Device/Include
    • to <sdk root>\components\toolchain:
      • system_nrf*.c files, found in the MDK install at nRF/Device/Source
      • system_nrf*.h files, found in the MDK install at nRF/Device/Include
    • to <sdk root>\svd:
      • *.svd files found in the MDK install at nRF/Device/Registers

    Another option is to copy the MDK directory from SDK 17.1.0 and replace it in SDK 17.0.2.

    Best regards,
    Jørgen

Children
No Data
Related