Debugger problem with Segger Embedded Studio 4.30c

RE: Debugger problem with Segger Embedded Studio 4.30c

Fabien Comte — Wed, 15 Jan 2020 09:31:04 GMT

Hello,

I am on master branch. I will try soon.

Thank you for your help.

RE: Debugger problem with Segger Embedded Studio 4.30c

Heidi — Tue, 14 Jan 2020 14:54:00 GMT

I was able to reproduce the error and I have reported this as a bug for the NCS team. However, when I switched to NCS v.1.1 as opposed to being on the master branch, the error disappeared.

Are you on NCS v.1.1 or master branch? If you're on the master, could you please switch to tag v.1.1 and confirm that this solves the issue for you too?

RE: Debugger problem with Segger Embedded Studio 4.30c

Fabien Comte — Mon, 13 Jan 2020 16:07:44 GMT

Ok as I said, please test the original aws_fota sample with SES. Without any change, debug is already broken.

RE: Debugger problem with Segger Embedded Studio 4.30c

Heidi — Mon, 13 Jan 2020 15:41:46 GMT

Hi, to clarify you shouldn't have to change anything but changing the paths to be relative like you suggested is a good idea, because then it doesn't matter where your application is located.

RE: Debugger problem with Segger Embedded Studio 4.30c

Fabien Comte — Mon, 13 Jan 2020 15:04:53 GMT

My mistake, I changed theses 2 lines because at first, samples had relative paths instead of ZEPHYR_BASE but it was fixed and now I have the same CMakeLists.txt as the sample.

RE: Debugger problem with Segger Embedded Studio 4.30c

Fabien Comte — Mon, 13 Jan 2020 15:02:41 GMT

Hello,

Just to be sure, I tried to debug aws_fota sample in SES without any modification in the same directory and it not works like the error reported.

RE: Debugger problem with Segger Embedded Studio 4.30c

Heidi — Mon, 13 Jan 2020 14:55:41 GMT

[quote user="facotl"]What settings / variables I have to change when I move a sample please ?[/quote]

It depends where your copied directory is located. If it's in the same place as aws_fota (ncs/nrf/samples/nrf9160) then you shouldn't change anything in the CMakeLists.txt file.

RE: Debugger problem with Segger Embedded Studio 4.30c

Fabien Comte — Mon, 13 Jan 2020 14:46:19 GMT

To work in SES I changed in CMakeLists.txt some paths

include($ENV{ZEPHYR_BASE}/../nrf/cmake/boilerplate.cmake NO_POLICY_SCOPE)
include($ENV{ZEPHYR_BASE}/cmake/app/boilerplate.cmake NO_POLICY_SCOPE)

What am I missing for west configuration ?

RE: Debugger problem with Segger Embedded Studio 4.30c

Fabien Comte — Mon, 13 Jan 2020 14:44:30 GMT

Hello Heidi,

This is strange, in aws_fota this command works but in my directory (a copy of aws_fota sample), it's not. What settings / variables I have to change when I move a sample please ?

RE: Debugger problem with Segger Embedded Studio 4.30c

Heidi — Fri, 10 Jan 2020 14:04:15 GMT

[quote user="facotl"]Please open project in SES and don't use command to build but SES (like the way used in getting started) and you will see.[/quote]

This is exactly what you did.

Again, if you are having trouble running the west build command in a terminal as well, SES is not your problem.

[quote user="facotl"]F:\Git\XXX\Projects\XXX\6_Sources\EmbeddedApplication>west build -b nrf9160_pca10090ns -d build -p[/quote]

Are you running the command inside your NCS directory? I can't tell. Please try to run the command inside the aws_fota directory.

RE: Debugger problem with Segger Embedded Studio 4.30c

Fabien Comte — Fri, 10 Jan 2020 09:08:26 GMT

C:\Users\Fabien>pip3 install west
Requirement already satisfied: west in c:\python38\lib\site-packages (0.6.3)
Requirement already satisfied: colorama in c:\python38\lib\site-packages (from west) (0.4.1)
Requirement already satisfied: PyYAML in c:\python38\lib\site-packages (from west) (5.1.2)
Requirement already satisfied: setuptools>=v40.1.0 in c:\python38\lib\site-packages (from west) (41.2.0)
Requirement already satisfied: configobj in c:\python38\lib\site-packages (from west) (5.0.6)
Requirement already satisfied: pykwalify in c:\python38\lib\site-packages (from west) (1.7.0)
Requirement already satisfied: six in c:\python38\lib\site-packages (from configobj->west) (1.13.0)
Requirement already satisfied: docopt>=0.6.2 in c:\python38\lib\site-packages (from pykwalify->west) (0.6.2)
Requirement already satisfied: python-dateutil>=2.4.2 in c:\python38\lib\site-packages (from pykwalify->west) (2.8.1)

F:\Git\XXX\Projects\XXX\6_Sources\EmbeddedApplication>west build -b nrf9160_pca10090ns -d build -p
usage: west [-h] [-z ZEPHYR_BASE] [-v] [-V] <command> ...
west: error: argument <command>: invalid choice: 'build' (choose from 'init', 'update', 'list', 'manifest', 'diff', 'status', 'forall', 'config', 'selfupdate', 'help')

RE: Debugger problem with Segger Embedded Studio 4.30c

Fabien Comte — Fri, 10 Jan 2020 09:06:48 GMT

Please open project in SES and don't use command to build but SES (like the way used in getting started) and you will see.

RE: Debugger problem with Segger Embedded Studio 4.30c

Heidi — Tue, 07 Jan 2020 13:49:18 GMT

Hi! Not sure what you mean by that. I wasn't able to reproduce your error, unfortunately.

[quote user="facotl"]I tried west build but I got an error that build is an invalid argument.[/quote]

However, if running west build -b nrf9160_pca10090ns -d build -p gives you that build is an invalid argument, you don't have west installed.

Did you go through the Getting Started Assistant in nRF Connect?

Specifically, in step 2 they ask you to run pip3 install west.

RE: Debugger problem with Segger Embedded Studio 4.30c

Fabien Comte — Fri, 03 Jan 2020 17:33:29 GMT

Does anyone can tell me how to change HEX target to ELF (I not found where it's done)

RE: Debugger problem with Segger Embedded Studio 4.30c

Fabien Comte — Mon, 30 Dec 2019 22:41:16 GMT

I found something. It expects an ELF file but it's a HEX file that is targeted. I am searching why.

RE: Debugger problem with Segger Embedded Studio 4.30c

Fabien Comte — Mon, 30 Dec 2019 21:52:22 GMT

Thank you for your help.

You can reproduce it with aws fota sample.

Steps are:
- import project
- build
- try to run debugger on it

I tried west build but I got an error that build is an invalid argument.

New NCS => no change.

RE: Debugger problem with Segger Embedded Studio 4.30c

Heidi — Mon, 30 Dec 2019 17:03:59 GMT

Hi!

Could you be more specific about what steps you're doing before you get this error?

Are you trying to run a sample or your own application?

Where is your NCS directory located, and where is the application you are running located in relation to the NCS directory?

Have you tried flashing using the command line (west build -b nrf9160_pca10090ns -d build -p) - do you get the same error here?

I think you should try deleting your whole NCS directory and installing it again.

Best regards,

Heidi