<?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/"><channel><title>Anvi's Activities</title><link>https://community.arm.com/members/anvi</link><description>Anvi's recent activity</description><dc:language>en-US</dc:language><generator>Telligent Community 10</generator><item><title>Let me Help You</title><link>https://community.arm.com/achievements/687f4b6d-e18a-4e55-836c-49926ca2c9d9</link><pubDate>Sun, 20 Dec 2020 03:19:08 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:29e0018a-d0ad-459f-90b7-61ee14a04987</guid><dc:creator /><description>Answer a question that is verified as helpful or correct.</description></item><item><title>Errors L6366E &amp;amp; L62242E</title><link>https://community.arm.com/developer/tools-software/tools/f/keil-forum/48301/errors-l6366e-l62242e</link><pubDate>Thu, 17 Dec 2020 01:30:38 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:40709047-fb9d-4ed5-914b-1b81e90f9ab7</guid><dc:creator>Anvi</dc:creator><description>&lt;p&gt;I created a static library for&amp;nbsp;the &lt;a href="https://github.com/kmackay/micro-ecc"&gt;micro-ecc&lt;/a&gt;&amp;nbsp;project using&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm" rel="nofollow"&gt;GNU Arm Embedded Toolchain&lt;/a&gt;:&lt;br /&gt;arm-none-eabi-gcc -Wall -c uECC.c&lt;br /&gt;and&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;a href="https://developer.arm.com/documentation/dui0476/latest/" rel="nofollow"&gt;armar&lt;/a&gt;:&lt;br /&gt;armar -rcs libuECC.a uECC.o&lt;/p&gt;
&lt;p&gt;I added the library file to my Keil Project and I get this error:&lt;/p&gt;
&lt;p&gt;Build started: Project: xxx&lt;br /&gt;*** Using Compiler &amp;#39;V5.05 update 1 (build 106)&amp;#39;, folder: &amp;#39;C:\Keil_v5\ARM\ARMCC\Bin&amp;#39;&lt;br /&gt;Build Project &amp;#39;app_main&amp;#39; - Target &amp;#39;xxx&amp;#39;&lt;br /&gt;linking...&lt;br /&gt;.\release\xxx.axf:&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;strong&gt;Error: L6366E: uECC.o attributes are not compatible with the provided cpu and fpu attributes .&lt;br /&gt;Object uECC.o contains Build Attributes that are incompatible with the CPU attributes.&lt;br /&gt;Tag_CPU_arch = ARM v4T (=2)&lt;br /&gt;Tag_THUMB_ISA_use = Thumb instructions were permitted to be used (=1)&lt;br /&gt;Tag_ARM_ISA_use = ARM instructions were permitted to be used (=1)&lt;/strong&gt;&lt;br /&gt;.\release\xxx.axf:&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;strong&gt;Error: L6242E: Cannot link object uECC.o as its attributes are incompatible with the image attributes.&lt;/strong&gt;&lt;br /&gt;... &lt;strong&gt;wchart-16 clashes with wchart-32.&lt;/strong&gt;&lt;br /&gt;... &lt;strong&gt;arm-isa clashes with m-profile.&lt;/strong&gt;&lt;br /&gt;Not enough information to list image symbols.&lt;br /&gt;Not enough information to list load addresses in the image map.&lt;br /&gt;Finished: 8 information, 0 warning and 2 error messages.&lt;br /&gt;&amp;quot;.\release\xxx.axf&amp;quot; - 2 Error(s), 0 Warning(s).&lt;br /&gt;Target not created.&lt;br /&gt;Build Time Elapsed: 00:00:02&lt;/p&gt;
&lt;p&gt;If I try to link just the object file on its own (not a static library), I get the same error.&lt;/p&gt;
&lt;p&gt;I realize that I&amp;#39;m using an&amp;nbsp;old version of the ARM compiler and upgrading might fix these issues; but I just wanted to know if there is a workaround that I could try first.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Ask A Question I</title><link>https://community.arm.com/achievements/460ac7df-7ccc-4c42-a204-9e05eef3be09</link><pubDate>Thu, 17 Dec 2020 01:30:39 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:c5eeaa3e-cf53-4ac5-91e4-cb9738f60c81</guid><dc:creator /><description>Ask a question in a forum.</description></item><item><title>Understanding Flash Operations</title><link>https://community.arm.com/developer/tools-software/oss-platforms/f/android-forum/48003/understanding-flash-operations</link><pubDate>Sat, 07 Nov 2020 23:28:14 GMT</pubDate><guid isPermaLink="false">dd9e70c8-6d3c-4c71-b136-2456382a7b5c:47817835-e2dd-464b-89ba-8c5c257a4449</guid><dc:creator>Anvi</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I&amp;#39;m&amp;nbsp;developing on an&amp;nbsp;STM32F207 (&lt;a href="https://www.st.com/resource/en/datasheet/stm32f205rb.pdf"&gt;datasheet&lt;/a&gt;). I am attempting to modify a&amp;nbsp;couple&amp;nbsp;of the internal Flash sectors (the 128kB sectors 10 &amp;amp; 11 to be specific). I&amp;#39;m trying to figure out how to do this in a way that will not block the CPU. Let&amp;#39;s say I&amp;#39;m trying to write an entire 128 KB sector.&lt;/p&gt;
&lt;p&gt;The F207&amp;#39;s Flash is a single bank; my understanding is that means the CPU is blocked during Flash write operations and the Flash cannot be read until the write operation is complete.&lt;/p&gt;
&lt;p&gt;The most common solution I&amp;#39;ve seen expressed is to place and execute the Flash operations in RAM; but won&amp;#39;t this cause the same issue? The flash is still being written to. Won&amp;#39;t this also prevent it from being read by the CPU?&lt;/p&gt;
&lt;p&gt;Also, would it be possible to divert these operations to the DMA unit? If not, why?&lt;/p&gt;
&lt;p&gt;Thank you&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>