<?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>trace settings for SAME70</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/36284/trace-settings-for-same70</link><description> 
Dear all, 

 
I use the SAME70 that is a 300MHz Cortex M7 device with a JLINK
Debugger. I tried to use the trace facility with no success. As soon
as I switch on the trace facility the startup &amp;#39;hangs&amp;#39; in the function
dbg_task_switch(). 
I assume it</description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>RE: trace settings for SAME70</title><link>https://community.arm.com/thread/109407?ContentTypeID=1</link><pubDate>Tue, 23 Jan 2018 13:00:18 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:dc9de2b9-186b-4b2b-ad88-8377ed411f7b</guid><dc:creator>Markus Krug</dc:creator><description>&lt;p&gt;&lt;p&gt;
It ends up in the function dbg_task_switch() that is located in
the HAL_CM.c file and part of the CMSIS RTX.&lt;br /&gt;
Any idea where this comes from?&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: trace settings for SAME70</title><link>https://community.arm.com/thread/94309?ContentTypeID=1</link><pubDate>Tue, 23 Jan 2018 12:41:50 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:7f13f104-d1f1-423f-8b6d-db147bb32d2c</guid><dc:creator>Westonsupermare Pier</dc:creator><description>&lt;p&gt;&lt;p&gt;
Ends up in the Hard Fault Handler?&lt;/p&gt;

&lt;p&gt;
__main initializes the statics in RAM, assumes all memory
described to the linker is up and functional, typically achieved by
code in SystemInit()&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: trace settings for SAME70</title><link>https://community.arm.com/thread/70517?ContentTypeID=1</link><pubDate>Tue, 23 Jan 2018 10:13:47 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:b1e81062-ce7a-4f15-a6af-930d5d16e4a6</guid><dc:creator>Markus Krug</dc:creator><description>&lt;p&gt;&lt;p&gt;
I dig into the problem a little bit further.&lt;br /&gt;
It seems to me it is somehow related to what happens in __main (not
main() ). The startup code jumps into __main but never comes back. If
I stop the execution I always hang at the line while (ITM_PORT31_U32
== 0U) in the above mentioned function. So for some reasons the debug
task switch is called even before the operating system is
started.&lt;br /&gt;
If I use the prepared RTOS examples I don&amp;#39;t have the problem - but
also no output in the EventViewer.&lt;/p&gt;

&lt;p&gt;
Best Regards&lt;br /&gt;
Markus&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>