<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.arm.com/utility/feedstylesheets/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/"><channel><title>STM32 JTAG debugging with ULINK-ME acts weird</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/38198/stm32-jtag-debugging-with-ulink-me-acts-weird</link><description> 
I&amp;#39;ve been using MicroVision IDE and debugging STM32 successfully,
until recently. 

 
When starting the debugging, after loading the software the
debugger gives the following: 

 
Cannot access Memory 
*** error 57: illegal address (0x08000000) 

 </description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: STM32 JTAG debugging with ULINK-ME acts weird</title><link>https://community.arm.com/thread/125223?ContentTypeID=1</link><pubDate>Thu, 29 Jan 2009 04:55:58 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:9c68ed94-8377-4a3c-bc92-2db95155d12a</guid><dc:creator>Jani Laaksonen</dc:creator><description>&lt;p&gt;&lt;p&gt;
Problem seems to be solved.&lt;/p&gt;

&lt;p&gt;
Upgrading to latest ARM developement package did not help,
but..&lt;/p&gt;

&lt;p&gt;
I disabled three flags from the debugger settings:&lt;br /&gt;
-caching of code memory&lt;br /&gt;
-caching of data memory&lt;br /&gt;
-download code to flash&lt;/p&gt;

&lt;p&gt;
I don&amp;#39;t know how the flags turned on anyway.&lt;/p&gt;

&lt;p&gt;
It seems it still downloads code to flash, as the code cannot
possibly fit into sram, but it works.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: STM32 JTAG debugging with ULINK-ME acts weird</title><link>https://community.arm.com/thread/114646?ContentTypeID=1</link><pubDate>Thu, 29 Jan 2009 01:56:19 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:f388e067-a5df-44d8-bf4f-f36e3efa9697</guid><dc:creator>Jani Laaksonen</dc:creator><description>&lt;p&gt;&lt;p&gt;
STM32 like the topic says, STM32F101RBT6 to be exact. Do you need
any other info?&lt;/p&gt;

&lt;p&gt;
The core starts with internal oscillator, because no user or
startup library code has a chance to run before the error.&lt;/p&gt;

&lt;p&gt;
JTAG clock is at 500kHz at the moment. It has been working
correctly before at 1MHz, and I&amp;#39;ve tried as slow as 5kHz - slow as a
snail but the problem still persists.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: STM32 JTAG debugging with ULINK-ME acts weird</title><link>https://community.arm.com/thread/101588?ContentTypeID=1</link><pubDate>Thu, 29 Jan 2009 01:41:55 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:0effa46e-cb4d-4807-9258-3010ec733fb7</guid><dc:creator>Tamir Michael</dc:creator><description>&lt;p&gt;&lt;p&gt;
without any knowledge of your processor, I would suggest lowering
the speed of your JTAG?&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: STM32 JTAG debugging with ULINK-ME acts weird</title><link>https://community.arm.com/thread/77116?ContentTypeID=1</link><pubDate>Thu, 29 Jan 2009 01:21:35 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:e82cbe1d-e4b7-44b7-a99c-bc59b4c843dd</guid><dc:creator>Jani Laaksonen</dc:creator><description>&lt;p&gt;&lt;p&gt;
But it fails immediately, without running any code.&lt;/p&gt;

&lt;p&gt;
The reset vector at 0x08000004 points to 0x08000165, which is not
on word or doubleword boundary.&lt;/p&gt;

&lt;p&gt;
The program counter however sets to 0x08000164 on reset.&lt;/p&gt;

&lt;p&gt;
Should it be on word or doubleword boundary?&lt;/p&gt;

&lt;p&gt;
The code runs perfectly on target system though.&lt;/p&gt;

&lt;p&gt;
So what is wrong here, as I don&amp;#39;t believe this has anything to do
with my code, just some settings maybe.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: STM32 JTAG debugging with ULINK-ME acts weird</title><link>https://community.arm.com/thread/55294?ContentTypeID=1</link><pubDate>Thu, 29 Jan 2009 00:52:03 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:812c6df2-be68-4c19-9988-5747ee2f0c20</guid><dc:creator>Andy Neil</dc:creator><description>&lt;p&gt;&lt;p&gt;
&lt;i&gt;&amp;quot;The address is the starting address of on-chip flash, so it is
valid.&amp;quot;&lt;/i&gt;&lt;/p&gt;

&lt;p&gt;
Not necessarily: that just indicates that memory physically exists
at the address - it does not confirm that the specific access attempt
(Read/Write/Execute) was valid for that address...&lt;/p&gt;

&lt;p&gt;
Check your pointers...&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>