<?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>How to build the LINUX tools?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/18430/how-to-build-the-linux-tools</link><description>I develop with MDK.
Now, I want to create a bootloader with 12.1?
Follow the instruction of the document, I must install micro-ecc, and .... 
 
 
 
 
 
 But as last, we can not get the prebuilt native tools. 
 I want to know that why the SDK12</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 16 Dec 2016 10:11:30 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/18430/how-to-build-the-linux-tools" /><item><title>RE: How to build the LINUX tools?</title><link>https://devzone.nordicsemi.com/thread/71123?ContentTypeID=1</link><pubDate>Fri, 16 Dec 2016 10:11:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ba22cdf5-3714-4313-b605-085a2650362f</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Why build the toolchain from source? It comes with prebuilt binaries from launchpad. Building GCC from scratch is not something I would recommend for any embedded developer, as it&amp;#39;s a &lt;em&gt;very&lt;/em&gt; complex operation.
Grab the gcc-arm-none-eabi-*-linux.tar.bz2, unpack it to your desired directory and modify /components/toolchain/gcc/Makefile.posix to this path. If you get any weird errors running arm-none-eabi-gcc, it&amp;#39;s probably because you&amp;#39;re on 64-bit linux, and need to install &amp;quot;ia32-libs&amp;quot; for x86 compatibility.&lt;/p&gt;
&lt;p&gt;I agree with your last point here. We can always provide methods or tools to ease the development. For instance: provide scripts to pull and build the external library. I&amp;#39;ll bring this up internally.&lt;/p&gt;
&lt;p&gt;Cheers,
Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to build the LINUX tools?</title><link>https://devzone.nordicsemi.com/thread/71124?ContentTypeID=1</link><pubDate>Fri, 16 Dec 2016 09:12:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f4f1cb3f-9b0c-4665-9fe1-1aae2a5b464b</guid><dc:creator>J&amp;#248;rgen Holmefjord</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;It looks like you copied a dot (.) from the PDF file that was not supposed to be part of the link. Please follow the link to the correct page: &lt;a href="https://launchpad.net/gcc-arm-embedded-misc/native-build-tools/20150408"&gt;https://launchpad.net/gcc-arm-embedded-misc/native-build-tools/20150408&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The reason why micro-ecc is not included in the SDK, is that the license of the library does not allow us to distribute it. The user is therefore required to download and install the library manually. We are working on a better solution for this in the future.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Jørgen&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to build the LINUX tools?</title><link>https://devzone.nordicsemi.com/thread/71128?ContentTypeID=1</link><pubDate>Fri, 16 Dec 2016 03:22:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8c6ec619-ed6a-4488-a1f0-c207aa927c9a</guid><dc:creator>zhouyu</dc:creator><description>&lt;p&gt;No, You don&amp;#39;t have to. A newer version would be better. As long as It supports your gcc-arm. My distribution is Fedora 25. What kind of example would you like? The hex file of dfu? I used the example of SDK 12.2.
First, put the arm-gcc in a right place and compile the bootloader_secure example, then you may encounter &lt;a href="https://devzone.nordicsemi.com/question/103798/when-i-use-the-example-componentslibrariesecceccc25-error-5-cannot-open-source-input-file-uecch-no-such-file-or-directory/"&gt;the issue&lt;/a&gt;. I&amp;#39;m glad to share any detail here.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to build the LINUX tools?</title><link>https://devzone.nordicsemi.com/thread/71127?ContentTypeID=1</link><pubDate>Fri, 16 Dec 2016 02:31:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9698eae3-8bd1-4460-a408-0914d44a5d81</guid><dc:creator>ligang</dc:creator><description>&lt;p&gt;If possoble, can you send me some example? my mail is lglgang@126.com
I only use the bootloader DFU to download the new code to the board through bluetooth.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to build the LINUX tools?</title><link>https://devzone.nordicsemi.com/thread/71126?ContentTypeID=1</link><pubDate>Fri, 16 Dec 2016 02:28:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f9155187-b0ca-461b-951a-2be38e86e7a3</guid><dc:creator>ligang</dc:creator><description>&lt;p&gt;I must use the ubuntu 8.1 32bit ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to build the LINUX tools?</title><link>https://devzone.nordicsemi.com/thread/71125?ContentTypeID=1</link><pubDate>Fri, 16 Dec 2016 01:45:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:438835eb-9522-477d-993f-499eae8b607e</guid><dc:creator>zhouyu</dc:creator><description>&lt;p&gt;I&amp;#39;m using gcc to develop nrf52. I think you could put the gcc tools in /usr/local/.  Refer to &amp;quot;yoursdk/components/toolchain/gcc/Makefile.posix&amp;quot;. In my case, it is /usr/local/gcc-arm-none-eabi-4_9-2015q1. Then go to the folder where the makefile exists to compile.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>