nRF Connect SDK Intermediate Lesson 1 Exercise 1 Debugging Issues

RE: nRF Connect SDK Intermediate Lesson 1 Exercise 1 Debugging Issues

Edvin — Wed, 05 Jun 2024 07:24:10 GMT

Hello Tom,

Yes. We have seen some other reports on the same topic as well. We are still investigating. Make sure to regularly update all the extensions/plugins from Nordic, so that you will receive the fix if/when we find it.

BR,
Edvin

RE: nRF Connect SDK Intermediate Lesson 1 Exercise 1 Debugging Issues

TomSansome — Tue, 04 Jun 2024 21:17:09 GMT

Hi Edvin,

Sorry for the delay in replying.

Yeah i can run the debug session in VScode but just don't get anything in the thread viewer.

I have installed Ozone and if i debug with Ozone then i can view the threads and everything appears to work as expected which is good. It still does not answer the problem of it not working in VS code, do you know why one might work and the other not? Either way i can use Ozone for the time being and continue through the Intermediate Dev Academy course.

Best regards,

Tom

RE: nRF Connect SDK Intermediate Lesson 1 Exercise 1 Debugging Issues

Edvin — Tue, 28 May 2024 08:54:15 GMT

Hello Tom,

You should just power it like you usually do when you program the kit. Unfortunately, I am not sure what the issue is, then. But you are able to run a debug session, right? You just don't see the thread information?

How about debugging with Ozone? Did you try that? I do experience some bugs myself when debugging using VS Code, but most is solved after power cycling the DK, or even deleting the build folder and rebuilding the project.

BR,
Edvin

RE: nRF Connect SDK Intermediate Lesson 1 Exercise 1 Debugging Issues

TomSansome — Mon, 27 May 2024 13:34:09 GMT

Hi Edvin,

I have removed and reinstalled VS code, the command line tools and the jlink drivers you suggested. The only thing of note was that when reinstalling the command line tools it did not prompt me to install a jlink driver so i manually installed the versions you recommended. I also had to add the command line tools and the jlink software to the system Path variables in order for them to be found by VS Code.

Unfortunately there is no change in the behaviour and still no threads are displayed.

It should not matter how i am powering and connecting to the dev kit i assume? i am currently just connected and powered over USB.

Many thanks,

Tom

RE: nRF Connect SDK Intermediate Lesson 1 Exercise 1 Debugging Issues

Edvin — Fri, 24 May 2024 10:06:30 GMT

Hello Tom,

I don't know all the quirks with VS Code, but perhaps you can try some of the hints here:

https://stackoverflow.com/questions/47689536/how-to-completely-uninstall-vs-code-on-windows

Also, J-Link is a bit weird some times. I have v7.94e and v7.88j installed on this computer, so perhaps you can try that combination.

Best regards,

Edvin

RE: nRF Connect SDK Intermediate Lesson 1 Exercise 1 Debugging Issues

TomSansome — Wed, 22 May 2024 07:28:31 GMT

Hi Edvin,

No worries, thanks again for helping with this.

I have not tried on another computer as I unfortunately don't have access to one at the moment.

Would removing and then reinstalling everything be worth trying in the mean time? If so are there any specific steps i should take to ensure a fresh install (i.e. just re-install VS code or remove the command line tools and jlink drivers as well)?

I had previously setup VS code and nRF Connect around a year or two ago but at the time found out that ANT+ was not supported so had to use SES instead. When i set it up this time i wanted to start fresh and uninstalled VS code, the command line tools, jlink drivers etc. and then reinstalled them as per the instructions on the dev academy but found that VS code came back with all my previous extensions and settings for some reason. Do you know if there is a way to do a clean install of VS code?

Many thanks

Tom

RE: nRF Connect SDK Intermediate Lesson 1 Exercise 1 Debugging Issues

Edvin — Tue, 21 May 2024 20:55:44 GMT

Hello Tom,

Sorry for the late reply. We have had several public days off the last couple of weeks, and the backlog has grown proportionally with that.

Have you tried this on another computer? I ran this by the team that wrote the DevAcademy course that you refer to, and we didn't find anything that stood out as a mistake. Perhaps there is something wrong with the way that the toolchain is set up. Your project works as intended on my computer.

So for debugging (the debugging) purposes, can you please try to run the application on a different computer?

Best regards,

Edvin

RE: nRF Connect SDK Intermediate Lesson 1 Exercise 1 Debugging Issues

TomSansome — Mon, 13 May 2024 09:14:41 GMT

Hi Edvin,

Closing the other terminals and the opening a new nRF connect terminal does not make any difference, but it does appear to be named differently than the terminal in your screenshot. When i start a new debug session it creates a new terminal that does not start with "nRF Connect:" not sure if this matters?

here is the support information:

devzone.nordicsemi.com/.../nRF-Connect-support-information-13_2D00_5_2D00_2024.txt

[quote userid="26071" url="~/f/nordic-q-a/110752/nrf-connect-sdk-intermediate-lesson-1-exercise-1-debugging-issues/482969"]What does this say if you press the play button so that the breakpoint in main is hit? And after it is hit, does the NRF DEBUG terminal still doesn't show anything?[/quote]

I had continued to the breakpoint in main() in the previous screenshot (the breakpoint was not right at the start of main() but it makes no difference where i place it in main(). The NRF DEBUG window still shows no threads available at this breakpoint.

Many thanks,

Tom

RE: nRF Connect SDK Intermediate Lesson 1 Exercise 1 Debugging Issues

Edvin — Mon, 13 May 2024 08:59:38 GMT

Hello Tom,

Ok, try opening a new nRF Connect terminal by pressing the little plus sign at the far right:

And kill all other terminals than the nRF Connect one. Then start the debug session all over. See if that helps. If not, can you please try to generate some support information:

Save that information to a file, and upload it here.

[quote user="TomSansome"]

Not sure if it is useful but here is the debug terminal output as well:

[/quote]

What does this say if you press the play button so that the breakpoint in main is hit? And after it is hit, does the NRF DEBUG terminal still doesn't show anything?

BR,
Edvin

RE: nRF Connect SDK Intermediate Lesson 1 Exercise 1 Debugging Issues

TomSansome — Fri, 10 May 2024 14:20:55 GMT

Here is the screenshot of the terminal window after starting debugging and having continued to the breakpoint in main():

I only have a single project open so i dont think that has been an issue but doing as you suggest seems not to make a difference, still not threads available for display.

Not sure if it is useful but here is the debug terminal output as well:

Cheers,

Tom

RE: nRF Connect SDK Intermediate Lesson 1 Exercise 1 Debugging Issues

Edvin — Fri, 10 May 2024 13:10:39 GMT

When you see the window that you are seeing, and says "No threads are available for display.", like it does in your previous screenshot. What does it say if you press "Terminal"? Can you share a screenshot of that aswell?

And please try to make sure you selected the correct project before clicking "Debug", and that you have opened the main.c file of that project before you click "Debug". (Opened properly, by double clicking the main.c tab at the top of the screen:

What does the terminal tab look like?

RE: nRF Connect SDK Intermediate Lesson 1 Exercise 1 Debugging Issues

TomSansome — Fri, 10 May 2024 12:27:21 GMT

Hi Edvin,

Thank you for your help, hopefully this is the correct way to upload the file, please let me know if you need anything else.

devzone.nordicsemi.com/.../inter_5F00_less1_5F00_exer1.zip

Best regards,

Tom

RE: nRF Connect SDK Intermediate Lesson 1 Exercise 1 Debugging Issues

Edvin — Fri, 10 May 2024 12:00:16 GMT

Can you please .zip and upload the application that you are using, so that I can give it a try?

RE: nRF Connect SDK Intermediate Lesson 1 Exercise 1 Debugging Issues

TomSansome — Wed, 08 May 2024 20:34:41 GMT

Hi Edvin,

I had added "CONFIG_DEBUG_THREAD_INFO=y", if i delete the build folder and rebuild it makes no difference, restarting also does not change anything, still no threads available for display. As i previously mentioned, i have also tried building the solution code for the exercise with the same result.

Many thanks

Tom

RE: nRF Connect SDK Intermediate Lesson 1 Exercise 1 Debugging Issues

Edvin — Wed, 08 May 2024 08:01:25 GMT

Make sure that you have added "CONFIG_DEBUG_THREAD_INFO=y" to your prj.conf, and then delete your build folder, and rebuild the application before trying once more. If it still doesn't show up, try to hit the restart button

Best regards,

Edvin

RE: nRF Connect SDK Intermediate Lesson 1 Exercise 1 Debugging Issues

TomSansome — Mon, 06 May 2024 08:58:48 GMT

Hi Edvin,

This is the example from the lesson in the DevAcademy when you start the debug session:

and this is what i see (when i use a breakpoint in main()):

As you can see my call stack on the left only has main() and the thread viewer is empty. Not sure why but today i cannot get the thread viewer to populate no matter where i add the breakpoint.

Cheers,

Tom

RE: nRF Connect SDK Intermediate Lesson 1 Exercise 1 Debugging Issues

Edvin — Mon, 06 May 2024 07:06:11 GMT

Hello Tom,

Can you please share som screenshots showing what you mean is missing/wrong, and point to the figures/parts of the DevAcademy where you mean the behavior differs?

Best regards,

Edvin

RE: nRF Connect SDK Intermediate Lesson 1 Exercise 1 Debugging Issues

TomSansome — Fri, 03 May 2024 08:02:06 GMT

Hi Edvin,

Thanks for getting back to me.

Yes it starts in reset.S, if i set a break point in main() and then continue it stops at the break point in main() but I don't get anything in the Thread Viewer and the call stack only contains main(). If i add a break point at the end of main() and continue to it then the tread viewer is populated but greyed out (cannot interact with anything unlike the description in exercise 1) and the call stack still only contains main(). Is this how it is supposed to function?

Best regards,

Tom

RE: nRF Connect SDK Intermediate Lesson 1 Exercise 1 Debugging Issues

Edvin — Thu, 02 May 2024 12:31:29 GMT

Hello,

Does it start in reset.S? Have you tried setting a breakpoint somewhere near the start of your main() function, and then hit the "play" button near the top of the VS Code window?

Does it jump into main() then?

Best regards,

Edvin