<?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>Install micro-ecc with SEGGER</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/63481/install-micro-ecc-with-segger</link><description>Hi 
 I&amp;#39;m trying to use Crypto but can&amp;#39;t get started because micro-ecc isn&amp;#39;t installed 
 The install instructions say: 
 Enter the subdirectory for the SoC and the toolchain that you are using to build your application: 
 
 InstallFolder \external\micro</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 25 Jan 2021 18:51:12 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/63481/install-micro-ecc-with-segger" /><item><title>RE: Install micro-ecc with SEGGER</title><link>https://devzone.nordicsemi.com/thread/291134?ContentTypeID=1</link><pubDate>Mon, 25 Jan 2021 18:51:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:57877e00-eb4a-4211-bf2c-7b1f469b221d</guid><dc:creator>RVM</dc:creator><description>&lt;p&gt;I have a follow up question.&lt;/p&gt;
&lt;p&gt;I want to use the ECDSA256 with the micro-ecc but for the life of me I cannot get a fully linked build.&lt;/p&gt;
&lt;p&gt;I keep getting this error in the bootloader:&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; nrf_dfu_validation.c:(.text.nrf_dfu_validation_signature_check+0x3e): undefined reference to `nrf_crypto_hash_calculate&amp;#39;&lt;/p&gt;
&lt;p&gt;I have raised this issue in another ticket but wanted to see if you have any suggestions.&lt;br /&gt;What kind of backend can I use to support ECDSA256 on nRF52832 (no 310), SDK 16.0.0 and S132 v7.0.2&lt;/p&gt;
&lt;p&gt;Cheers&lt;/p&gt;
&lt;p&gt;RMV&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Install micro-ecc with SEGGER</title><link>https://devzone.nordicsemi.com/thread/259125?ContentTypeID=1</link><pubDate>Thu, 09 Jul 2020 09:27:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c368bf78-2675-4f5d-8321-9b1aa0c575aa</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Sorry for misunderstanding your question. SES uses GCC as the compiler internally. The libraries built by GCC can be used with SES.&lt;/p&gt;
&lt;p&gt;You can see the backends supporting AES in the &lt;a href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.0.0/lib_crypto.html#lib_crypto_intro_family_aes"&gt;nrf_crypto library documentation&lt;/a&gt;. For nRF52832, only mbedTLS is available, as it does not have the CC310 HW Cryptocell module in the chip. For MD5, this is not supported by the nrf_crypto library at all. I believe this was decided to not implement because it is simple to do in SW and not that much used in small embedded systems. I see that mbedTLS has functions for calculating MD5 (external\mbedtls\library\md5.c), they are included in the nRF_Crypto examples and I think you should be able to call the API without any modifications.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Jørgen&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Install micro-ecc with SEGGER</title><link>https://devzone.nordicsemi.com/thread/259086?ContentTypeID=1</link><pubDate>Thu, 09 Jul 2020 07:18:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e6bdb23c-5a5f-4a90-8c94-8bcc10537129</guid><dc:creator>Nick_RA</dc:creator><description>&lt;p&gt;Hi. Yes I understand the licencing issue, and I was referring to the page you linked to which doesn&amp;#39;t help because step 4 (which I quoted in my question) doesn&amp;#39;t make any reference to SES. &amp;quot;Enter the subdirectory for the SoC and the toolchain that you are using to build your application&amp;quot; - there isn&amp;#39;t a subdirectory for Segger.&lt;/p&gt;
&lt;p&gt;Anyway, I probably asked the wrong question because I was just trying to compile the SDK examples to start with which maybe isn&amp;#39;t the best approach here.&lt;/p&gt;
&lt;p&gt;I need 2 crypto functions. AES&amp;nbsp; encrypt/decrypt, and MD5 for file checking. What libraries do I need to include?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Install micro-ecc with SEGGER</title><link>https://devzone.nordicsemi.com/thread/258832?ContentTypeID=1</link><pubDate>Tue, 07 Jul 2020 14:31:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:24117354-1582-4039-80c6-a5e8d7ade347</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;We are not allowed to provide micro-ecc with the SDK due to limitations in the license of the library. If you want to use the micro-ecc backend, you need to build it yourself using GCC. See the instructions &lt;a href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.0.0/lib_crypto_backend_micro_ecc.html#lib_crypto_backend_micro_ecc_install"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;By default, the micro-ecc backend is not used in the crypto examples, the nRF_Oberon backend is used (&lt;a href="https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.0.0/group__nrf__crypto__config.html#ga22ba157a40ce2742fb86f3e527754a91"&gt;NRF_CRYPTO_BACKEND_OBERON_ENABLED&lt;/a&gt;=1). You can exclude/remove the micro-ecc library file (micro_ecc_lib_nrf52.a) from the project if you do not intend to use it. That way you should be able to build the examples in SES without any need for additional tools.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;Jørgen&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>