<?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>RTX failure - can you explain it?</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/24242/rtx-failure---can-you-explain-it</link><description> 
Hello, 
I have 2 identical projects. the exact same code, the exact same
project settings (except minor changes in the .uv2 file). the working
project starts all tasks correctly, while the bad one calls the sixth
task &amp;quot;_maybe_terminate_alloc&amp;quot;. that</description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: RTX failure - can you explain it?</title><link>https://community.arm.com/thread/114971?ContentTypeID=1</link><pubDate>Wed, 03 Jun 2009 12:07:45 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:57848890-1339-4837-a077-aeb0a32b1add</guid><dc:creator>Tamir Michael</dc:creator><description>&lt;p&gt;&lt;p&gt;
I colleague of time managed to cause RTX to hang in the function
&amp;#39;os_put_prio&amp;#39; while on a debugger (hence, no task got serviced
anymore). We have sent a report (including screen shots) to Keil
support. I hope to report soon about the causes. I built a new
version of the controller software using the sources of RTX (not the
binary; Keil confirm that the sources installed by RL-ARM 3.50
correspond with the library of MDK 3.50) and left the system running
for the night. This might allow more debug information.&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: RTX failure - can you explain it?</title><link>https://community.arm.com/thread/103155?ContentTypeID=1</link><pubDate>Fri, 29 May 2009 08:41:11 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:a0f572bf-875b-49a6-8849-88d26055ede8</guid><dc:creator>Tamir Michael</dc:creator><description>&lt;p&gt;&lt;p&gt;
Keil support response:&lt;/p&gt;

&lt;p&gt;
Hi Tamir,&lt;br /&gt;
I don&amp;acirc;&amp;euro;&amp;trade;t think it is a RTX issue. It is more likely
a debugger issue, looking up the wrong label.&lt;br /&gt;
Meanwhile I managed to get a plain RTK_Blinky example to show the
same behavior, where taskname is changed to _maybe_terminate_alloc.
Here my mapfile section of this:&lt;/p&gt;

&lt;pre&gt;
    os_switch_tasks_ret                      0x0000037d   Thumb Code     0  rt_hal.o(.emb_text)
    _maybe_terminate_alloc                   0x00000401   Thumb Code     0  maybetermalloc1.o(.emb_text)
    phaseA                                   0x00000401   Thumb Code    10  blinky.o(.text)
    phaseB                                   0x0000040b   Thumb Code    10  blinky.o(.text)
    phaseC                                   0x00000415   Thumb Code    10  blinky.o(.text)
    phaseD                                   0x0000041f   Thumb Code    10  blinky.o(.text)
&lt;/pre&gt;

&lt;p&gt;
Here it is same address. But the order of the labels as printed in
the mapfile seems relevant.&lt;br /&gt;
The reason why in your case _maybe_terminate_alloc has higher address
is probably, that this is &amp;acirc;&amp;euro;&amp;oelig;thumb code&amp;acirc;&amp;euro;
and your task is &amp;acirc;&amp;euro;&amp;oelig;ARM code&amp;acirc;&amp;euro;. Both have
actually the same address, but thumb code will show up at odd
address. I see this as well, when switching my project to ARM
mode:&lt;/p&gt;

&lt;pre&gt;
    os_switch_tasks_ret                      0x00000385   Thumb Code     0  rt_hal.o(.emb_text)
    _maybe_terminate_alloc                   0x00000409   Thumb Code     0  maybetermalloc1.o(.emb_text)
    phaseA                                   0x00000408   ARM Code      20  blinky.o(.text)
    phaseB                                   0x0000041c   ARM Code      20  blinky.o(.text)
    phaseC                                   0x00000430   ARM Code      20  blinky.o(.text)
    phaseD                                   0x00000444   ARM Code      20  blinky.o(.text)
&lt;/pre&gt;

&lt;p&gt;
&lt;br /&gt;
As I said, I will discuss this internally. If I have more news on
that, I will let you know.&lt;/p&gt;

&lt;p&gt;
Best Regards,&lt;br /&gt;
Andreas Barth&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: RTX failure - can you explain it?</title><link>https://community.arm.com/thread/89774?ContentTypeID=1</link><pubDate>Fri, 29 May 2009 03:25:57 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:9d77f5b6-ae36-47e0-afc3-f511021c6279</guid><dc:creator>Tamir Michael</dc:creator><description>&lt;p&gt;&lt;p&gt;
I have reported this issue to Keil support along with the projects
that cause this behavior. I will report when I know more. If this is
indeed a linker failure, you can expect an update...&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: RTX failure - can you explain it?</title><link>https://community.arm.com/thread/56171?ContentTypeID=1</link><pubDate>Thu, 28 May 2009 10:55:13 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:6fbe9110-2c3b-4995-97fa-2281b58fbb01</guid><dc:creator>Tamir Michael</dc:creator><description>&lt;p&gt;&lt;p&gt;
this looks like a linker failure - notice the location of&lt;br /&gt;
&amp;#39;_maybe_terminate_alloc&amp;#39; in the first code excerpt!&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>