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
- 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
-Best Regards, Matthew