<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Peripheral Register view broken in VS Code</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/106273/peripheral-register-view-broken-in-vs-code</link><description>This morning, the peripheral registers view stopped working in VS Code. This is part of the Cortex-Debug extension used when debugging through the nRF Connect extension. The Cortex-Debug extension seems to be attempting to parse a JSON svd file that is</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 05 Dec 2023 14:44:44 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/106273/peripheral-register-view-broken-in-vs-code" /><item><title>RE: Peripheral Register view broken in VS Code</title><link>https://devzone.nordicsemi.com/thread/459017?ContentTypeID=1</link><pubDate>Tue, 05 Dec 2023 14:44:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d14583eb-1320-4a5c-aa35-7343448a7afb</guid><dc:creator>Aaron F</dc:creator><description>&lt;p&gt;Ah, thank you Vidar! This is much better. It seems I just need the right Kconfigs.&lt;/p&gt;
&lt;p&gt;I suspect what happened was that I had been using a lot of the Cortex Debug views and the nRF Connect extension got upgraded dropping support for them. The new Thread Viewer view is really nice.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Peripheral Register view broken in VS Code</title><link>https://devzone.nordicsemi.com/thread/458930?ContentTypeID=1</link><pubDate>Tue, 05 Dec 2023 10:30:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d68b2bdf-de78-493a-8f3b-2397bedccac2</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;You&amp;#39;re right, I now see that we removed the Cortex debug integration in this release:&amp;nbsp;&lt;a href="https://nrfconnect.github.io/vscode-nrf-connect/release_notes/connect/2023.6.345.html?h=cortex+debug#removed-dependency-on-cortex-debug"&gt;https://nrfconnect.github.io/vscode-nrf-connect/release_notes/connect/2023.6.345.html?h=cortex+debug#removed-dependency-on-cortex-debug&lt;/a&gt;.&amp;nbsp;&amp;nbsp;However, I&amp;#39;m not sure why you are not seeing the threads in your call stack view or in the Thread viewer.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;When building a project with CONFIG_DEBUG_OPTIMIZATIONS=y and CONFIG_THREAD_NAME=y, I observe that the threads are displayed in both windows.&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1701772193178v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;Are we looking at the same windows?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Peripheral Register view broken in VS Code</title><link>https://devzone.nordicsemi.com/thread/458768?ContentTypeID=1</link><pubDate>Mon, 04 Dec 2023 14:42:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cb11500c-3ae4-4921-be6a-e5e45fec1593</guid><dc:creator>Aaron F</dc:creator><description>&lt;p&gt;Hi Vidar,&lt;/p&gt;
&lt;p&gt;Thank you for pointing this out. I was not aware of the different backend. I think my setup was using the nRF Debug backend already. I checked for the &lt;span style="font-family:courier new, courier;"&gt;nrf-connect.debugger.backend&lt;/span&gt; setting described in the article, but it seems to no longer exist? I am on version 2023.11.301 of the nRF Connect extension and that article is written for 2022.9.179. When I attempt to add &lt;span style="font-family:courier new, courier;"&gt;nrf-connect.debugger.backend&lt;/span&gt; into the &lt;span style="font-family:courier new, courier;"&gt;settings.json&lt;/span&gt; directly, the IntelliSense says &amp;quot;Unknown Configuration Setting&amp;quot;.&lt;/p&gt;
&lt;p&gt;Anyway, I went with the assumption that the nRF Debug backend is the one actually being used. This means I might have the wrong peripheral registers view open. Sure enough, I was able to open the correct view using the command palette and this one works properly.&lt;/p&gt;
&lt;p&gt;I do have a different issue now, though. I am not seeing any of the threads in the Thread Viewer or the Call Stack window. Normally (and maybe this was a Cortex Debug thing), the Call Stack view shows the call stacks for all threads. Now it shows only the active call stack. The Thread Viewer view is empty and says &amp;quot;No threads are available to display&amp;quot; even though I&amp;#39;m halted in a thread created using &lt;span style="font-family:courier new, courier;"&gt;K_THREAD_DEFINE&lt;/span&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Peripheral Register view broken in VS Code</title><link>https://devzone.nordicsemi.com/thread/458721?ContentTypeID=1</link><pubDate>Mon, 04 Dec 2023 12:17:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:3b76c1d4-bda8-4cd6-a0c6-13cbacb9946c</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I&amp;#39;m not sure what changed since the cortex-debug extension stopped working, but is it an option to use our recommended nRF Debug extension instead (&lt;a href="https://nrfconnect.github.io/vscode-nrf-connect/release_notes/connect/2022.9.179.html?h=cortex+debug#new-default-debugger-nrf-debug"&gt;https://nrfconnect.github.io/vscode-nrf-connect/release_notes/connect/2022.9.179.html?h=cortex+debug#new-default-debugger-nrf-debug&lt;/a&gt;)?&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Vidar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>