<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title><![CDATA[EmBitz - Debugging and debug plugins]]></title>
		<link>https://www.embitz.org/forum/</link>
		<description><![CDATA[EmBitz - https://www.embitz.org/forum]]></description>
		<pubDate>Tue, 19 May 2026 06:38:29 +0000</pubDate>
		<generator>MyBB</generator>
		<item>
			<title><![CDATA[svd files for core specific registers]]></title>
			<link>https://www.embitz.org/forum/showthread.php?tid=235</link>
			<pubDate>Mon, 16 Feb 2026 18:21:26 +0100</pubDate>
			<dc:creator><![CDATA[<a href="https://www.embitz.org/forum/member.php?action=profile&uid=92">Misc01</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.embitz.org/forum/showthread.php?tid=235</guid>
			<description><![CDATA[I recently used STM32 CubeIDE. While this is annoying slow when using embitz before, i found one thing that i did not encounter before. There are system register definitions beyond the STM32 specific SFRs, that affect the ARM core itself, like SCB, which e.g. contains a register holding the last address when a crash occured. In the normal MCU .vcd files, these ARM specific registers seem to be missing. How to show these registers in embitz?<br />
<br />
Best regards<br />
   Michael]]></description>
			<content:encoded><![CDATA[I recently used STM32 CubeIDE. While this is annoying slow when using embitz before, i found one thing that i did not encounter before. There are system register definitions beyond the STM32 specific SFRs, that affect the ARM core itself, like SCB, which e.g. contains a register holding the last address when a crash occured. In the normal MCU .vcd files, these ARM specific registers seem to be missing. How to show these registers in embitz?<br />
<br />
Best regards<br />
   Michael]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[Watch static variables]]></title>
			<link>https://www.embitz.org/forum/showthread.php?tid=33</link>
			<pubDate>Tue, 19 Jan 2021 00:25:12 +0100</pubDate>
			<dc:creator><![CDATA[<a href="https://www.embitz.org/forum/member.php?action=profile&uid=166">Droid32</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.embitz.org/forum/showthread.php?tid=33</guid>
			<description><![CDATA[Hello,<br />
<br />
I'm using EB with EBlink on Win10x64.<br />
If i debug a program, the watch window can't display variables which are "static" (non-static work of course). Is there a way to display static variables in the watch window?<br />
<br />
mfg]]></description>
			<content:encoded><![CDATA[Hello,<br />
<br />
I'm using EB with EBlink on Win10x64.<br />
If i debug a program, the watch window can't display variables which are "static" (non-static work of course). Is there a way to display static variables in the watch window?<br />
<br />
mfg]]></content:encoded>
		</item>
		<item>
			<title><![CDATA[CMSIS-DAP/DAPLink debug probes]]></title>
			<link>https://www.embitz.org/forum/showthread.php?tid=11</link>
			<pubDate>Thu, 20 Aug 2020 00:02:16 +0200</pubDate>
			<dc:creator><![CDATA[<a href="https://www.embitz.org/forum/member.php?action=profile&uid=125">splin</a>]]></dc:creator>
			<guid isPermaLink="false">https://www.embitz.org/forum/showthread.php?tid=11</guid>
			<description><![CDATA[Are these natively supported or would these have to used with OpenOCD? It would seem to be preferable to be able to use an open, non-proprietry debug/programming probe rather than having to buy a new probe for different manufacturer's Cortex devices.<br />
<br />
For example, I have an LPC-Link2 which can be flashed with CMIS-DAP DAPLink firmware which presumably I should be able to use to program Nuvoton Mini51 serries devices rather than having to buy their nu-link product? ([EDIT] the Nu-link probe is probably not supported by EBlink so OPENOCD would be required losing EBlink's advantages).<br />
<br />
Are there significant performance differences between most debug probes (other than the expensive Segger products)?<br />
<br />
[EDIT] This CMIS-DAP probe is only 12.99 Euros and supports Jtag as weill as SWD though I'm not sure how big an advantage that is in practice:<br />
<br />
<a href="https://www.l-tek.com/web-shop/cmsis-dap-debug-probe/" target="_blank" rel="noopener" class="mycode_url">LTek debug probe</a><br />
<br />
Is Jtag faster than SWD? Are there any Cortex devices that don't support SWD?]]></description>
			<content:encoded><![CDATA[Are these natively supported or would these have to used with OpenOCD? It would seem to be preferable to be able to use an open, non-proprietry debug/programming probe rather than having to buy a new probe for different manufacturer's Cortex devices.<br />
<br />
For example, I have an LPC-Link2 which can be flashed with CMIS-DAP DAPLink firmware which presumably I should be able to use to program Nuvoton Mini51 serries devices rather than having to buy their nu-link product? ([EDIT] the Nu-link probe is probably not supported by EBlink so OPENOCD would be required losing EBlink's advantages).<br />
<br />
Are there significant performance differences between most debug probes (other than the expensive Segger products)?<br />
<br />
[EDIT] This CMIS-DAP probe is only 12.99 Euros and supports Jtag as weill as SWD though I'm not sure how big an advantage that is in practice:<br />
<br />
<a href="https://www.l-tek.com/web-shop/cmsis-dap-debug-probe/" target="_blank" rel="noopener" class="mycode_url">LTek debug probe</a><br />
<br />
Is Jtag faster than SWD? Are there any Cortex devices that don't support SWD?]]></content:encoded>
		</item>
	</channel>
</rss>