<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/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/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Algorithm development: from Matlab to Segger Embedded Studio</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/48675/algorithm-development-from-matlab-to-segger-embedded-studio</link><description>Hi, I am currently working in Matlab to develop my DSP algorithms and will use the Matlab coder and Embedded coder to convert them to C code. Afterwards I will import the .c and .h files into Segger Embedded Studio. Has anyone experience with this process</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 18 Jun 2019 20:43:37 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/48675/algorithm-development-from-matlab-to-segger-embedded-studio" /><item><title>RE: Algorithm development: from Matlab to Segger Embedded Studio</title><link>https://devzone.nordicsemi.com/thread/193501?ContentTypeID=1</link><pubDate>Tue, 18 Jun 2019 20:43:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:167955d8-3cbb-46dd-842d-739a08dfd738</guid><dc:creator>hmolesworth</dc:creator><description>&lt;p&gt;Perhaps I wasn&amp;#39;t clear; the usual course is to load the appropriate library and not the source tree, in this case for IAR; SES would probably use the GCC library, but I haven&amp;#39;t yet tried that.&lt;/p&gt;
&lt;p&gt;Options-&amp;gt;Linker-&amp;gt;Library: Additional runtime Libraries selection:&lt;/p&gt;
&lt;p&gt;$PROJ_DIR$\..\..\..\..\components\toolchain\cmsis\dsp\ARM\arm_cortexM4lf_math.lib&lt;/p&gt;
&lt;p&gt;The libraries on Github are located here for CMSIS v4:&amp;nbsp;&lt;a href="https://github.com/ARM-software/CMSIS/tree/master/CMSIS/Lib/ARM"&gt;CMSIS/Lib/ARM&lt;/a&gt;&amp;nbsp;and here for CMSIS v5:&amp;nbsp;&lt;a href="https://github.com/ARM-software/CMSIS_5/tree/develop/CMSIS/DSP/Lib/ARM"&gt;CMSIS/DSP/Lib/ARM&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Algorithm development: from Matlab to Segger Embedded Studio</title><link>https://devzone.nordicsemi.com/thread/193351?ContentTypeID=1</link><pubDate>Tue, 18 Jun 2019 09:13:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0e9ce8f7-37af-49b0-9dcc-8e3982d26009</guid><dc:creator>awneil</dc:creator><description>&lt;p&gt;CMSIS should be standard &amp;#39;C&amp;#39; code - so shouldn&amp;#39;t be any issues using it with SES or any other IDE ...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Algorithm development: from Matlab to Segger Embedded Studio</title><link>https://devzone.nordicsemi.com/thread/193242?ContentTypeID=1</link><pubDate>Mon, 17 Jun 2019 15:56:45 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a0f8cf53-6bea-4ea0-9f8b-3eeea0bbd373</guid><dc:creator>hmolesworth</dc:creator><description>&lt;p&gt;I would suggest leveraging off the existing DSP code and libraries; I have used them with both Keil and IAR with good results, though not yet looked into the libraries on SES though I think they are compatible. Some of the libraries are optimised for DSP code on the Cortex-M4 and therefore should be much faster than vanilla C code&lt;/p&gt;
&lt;p&gt;&lt;a href="https://github.com/ARM-software/CMSIS_5/tree/develop/CMSIS/DSP"&gt;CMSIS_5/tree/develop/CMSIS/DSP&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Algorithm development: from Matlab to Segger Embedded Studio</title><link>https://devzone.nordicsemi.com/thread/193235?ContentTypeID=1</link><pubDate>Mon, 17 Jun 2019 15:00:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:532b4183-32cf-4f2b-b032-83e525797053</guid><dc:creator>awneil</dc:creator><description>&lt;p&gt;So long as it generates compliant &amp;#39;C&amp;#39; code, and all the dependencies are available, there should be no problem.&lt;/p&gt;
&lt;p&gt;Neither SES nor its underlying GCC toolchain can tell whether your code was hand-written or machine-generated.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>