Tuesday, April 24th 2018, 6:35pm UTC+2

You are not logged in.

  • Login
  • Register

MatthewKyeo

Beginner

Date of registration: Jul 19th 2017

Posts: 51

1

Monday, December 11th 2017, 7:59pm

[SOLVED] Additional Load File does not exist error

Hi, I'm Matthew. I use

- 64-bit SES 3.30 on 64-bit Windows 10 & MacOS (Nordic's free commercial license)

- J-Link Plus or onboard J-Link (Nordic's dev kits have a J-Link on the board itself)

- J-Link 6.22

- Nordic's PCA10040 v1.1.1 board (this board uses nRF52832-QFAA MCU)

If I configure the path of the "Additional Load File[0]" as an absolute path, SES loads the hex file nicely.




Whereas when it is configured as a relative path, it shows the above error.



I checked my directory several times using the "cd" command.

Since I push/pull codes from Windows 10 machines and MacOS machines, this relative path configuration is really important to me.

Can you help me with this error? That path configuration was the default configuration from Nordic, so I have no idea why this error shows up.

-Best Regards, Matthew

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 954

2

Tuesday, December 12th 2017, 9:56am

Hi Matthew,

Thank you for your inquiry.

To use the relative path to your hex please use the project directory macro as base.
e.g. $(ProjectDir)../../../test.hex

This is then relative to the .emProject file.

Does that work for you?

Best regards,
Nino
Please read the forum rules before posting: Forum Rules

Keep in mind, this is not a support forum. Its main purposes is user to user interaction.
Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
Should you be entitled to support contact us per e-mail.
The following contact form can be used for this: https://www.segger.com/about-us/contact-us/


MatthewKyeo

Beginner

Date of registration: Jul 19th 2017

Posts: 51

3

Tuesday, December 12th 2017, 11:36am

Wow, Nino! That was unexpected. Thanks for your answer, it works now. :thumbsup:




$(ProjectDir)/../../../../../../components/softdevice/s132/hex/s132_nrf52_5.0.0_softdevice.hex

was the answer. Problem solved! Appreciate your effort!

-Regards, Matthew

SEGGER - Nino

Super Moderator

Date of registration: Jan 2nd 2017

Posts: 954

4

Tuesday, December 12th 2017, 11:37am

Hi Matthew,

Great to hear that you are up and running again.
We will consider this case as solved now.

Best regards,
Nino
Please read the forum rules before posting: Forum Rules

Keep in mind, this is not a support forum. Its main purposes is user to user interaction.
Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
Should you be entitled to support contact us per e-mail.
The following contact form can be used for this: https://www.segger.com/about-us/contact-us/