<?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>Low Power Test Locks out Debugger</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/33472/low-power-test-locks-out-debugger</link><description> 
I was running The Low Power FreeRTOS example on a STM32F446 Eval
board. The operation of the 
example is to (Cortex M4) : 

 
This example creates two threads. 

 
+ A Rx thread that blocks on a queue to wait for data, blinking
LED each time data is</description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: Low Power Test Locks out Debugger</title><link>https://community.arm.com/thread/120637?ContentTypeID=1</link><pubDate>Wed, 19 Aug 2015 15:40:28 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:46350cd7-bd25-4b6d-a3b1-376a9fc1c84e</guid><dc:creator>Gary Olson</dc:creator><description>&lt;p&gt;&lt;p&gt;
Thanks for all of the help.&lt;/p&gt;

&lt;p&gt;
There is no debug.ini file that comes with the project. But the
Debug Settings :&lt;/p&gt;

&lt;p&gt;
Connect: Under Reset&lt;/p&gt;

&lt;p&gt;
Reset: Autodetect&lt;/p&gt;

&lt;p&gt;
Checked Reset after connect&lt;/p&gt;

&lt;p&gt;
did work without any problem.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Low Power Test Locks out Debugger</title><link>https://community.arm.com/thread/108387?ContentTypeID=1</link><pubDate>Wed, 19 Aug 2015 12:13:30 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:8953c14e-8dd0-4a98-9ca3-1510c990d981</guid><dc:creator>Kevin</dc:creator><description>&lt;p&gt;&lt;p&gt;
on the Options for Target-&amp;gt; debug tab, are you including a
debug initialization file? a *.ini.&lt;/p&gt;

&lt;p&gt;
the ini file configures the debug control register of the
device.&lt;/p&gt;

&lt;p&gt;
one of the options is to keep the debug circuitry powered in low
power mode.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Low Power Test Locks out Debugger</title><link>https://community.arm.com/thread/93518?ContentTypeID=1</link><pubDate>Wed, 19 Aug 2015 09:34:51 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:c9385c69-b220-4cc2-8b65-fcca1d25abd8</guid><dc:creator>Gary Olson</dc:creator><description>&lt;p&gt;&lt;p&gt;
Thanks for the information. I was methodically trying out the
examples that ST Microelectronics provide for the Eval Board.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Low Power Test Locks out Debugger</title><link>https://community.arm.com/thread/64012?ContentTypeID=1</link><pubDate>Wed, 19 Aug 2015 08:55:40 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:f3f7c537-0ea5-40ec-99b0-192581ac2d84</guid><dc:creator>&amp;#178;erik malund</dc:creator><description>&lt;p&gt;&lt;p&gt;
I do not know of your situation, but, for some, low power setting
&amp;#39;kills&amp;#39; the debugger&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Low Power Test Locks out Debugger</title><link>https://community.arm.com/thread/69321?ContentTypeID=1</link><pubDate>Wed, 19 Aug 2015 07:20:34 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:55a18d90-1b22-418b-bea1-4d88b77d074b</guid><dc:creator>edPer Westermark</dc:creator><description>&lt;p&gt;&lt;p&gt;
It&amp;#39;s expected to get communications failure when running
power-save functionality. So traditional routes are to make the code
better behaving during the development phase.&lt;/p&gt;

&lt;p&gt;
- maybe check a GPIO and not activate low-power features unless
the pin says &amp;quot;ok&amp;quot;.&lt;/p&gt;

&lt;p&gt;
- add a couple of seconds of delay at program startup, to give
time to connect and stop the program before it disconnects.&lt;/p&gt;

&lt;p&gt;
- maybe check the supply voltage and avoid low-power if the device
has &amp;quot;charger connected&amp;quot;.&lt;/p&gt;

&lt;p&gt;
The above methods applies to all kinds of code that will play
around with oscillators or power modes.&lt;/p&gt;

&lt;p&gt;
If a device has already been programmed with a problematic
software, then it&amp;#39;s time to check what potential options the specific
processor might have for trigging internal boot loaders, booting from
alternative memory, connecting while in reset or similar. In short -
if the chip manufacturer have implemented some ways to &amp;quot;unbrick&amp;quot; the
processor.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Low Power Test Locks out Debugger</title><link>https://community.arm.com/thread/64013?ContentTypeID=1</link><pubDate>Wed, 19 Aug 2015 05:51:15 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:a0035b0a-9930-496a-a1e8-477b6b2d1341</guid><dc:creator>Gary Olson</dc:creator><description>&lt;p&gt;&lt;p&gt;
I will try to connect under reset after working today.&lt;/p&gt;

&lt;p&gt;
&lt;a href="http://www.keil.com/support/man/docs/ulink2/ulink2_ctx_debug.htm"&gt;http://www.keil.com/support/man/docs/ulink2/ulink2_ctx_debug.htm&lt;/a&gt;&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>