<?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>building error / Branch error.    git merge. git pull. west update</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/45904/building-error-branch-error-git-merge-git-pull-west-update</link><description>Everything worked on friday. 
 but after a git pull and west update on Master branch. but instead of Master branch is an unknown number, or a hash. this happens on everyone but not on nrf directory it stays in Master. 
 I found out that after west update</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 11 Apr 2019 08:57:15 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/45904/building-error-branch-error-git-merge-git-pull-west-update" /><item><title>RE: building error / Branch error.    git merge. git pull. west update</title><link>https://devzone.nordicsemi.com/thread/181500?ContentTypeID=1</link><pubDate>Thu, 11 Apr 2019 08:57:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:34b8d70a-1171-4478-a526-7d760f9ca24d</guid><dc:creator>henninglindseth</dc:creator><description>&lt;p&gt;Thank u for all your help, I managed to set back to last week and now it works with command line.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;-henning&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: building error / Branch error.    git merge. git pull. west update</title><link>https://devzone.nordicsemi.com/thread/181227?ContentTypeID=1</link><pubDate>Wed, 10 Apr 2019 07:19:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:67b2feaa-6cb4-4839-a71b-e456ee53df6a</guid><dc:creator>Martin Lesund</dc:creator><description>&lt;p&gt;Hi Henning,&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Currently there is a workaround to use SES&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;if you are using SES v4.16 you should be able to use the&amp;nbsp;&lt;em&gt;almost&lt;/em&gt; the latest updates from master branch, by rolling back to last week.&lt;/p&gt;
&lt;p&gt;That means.&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;cd ncs/nrf
git checkout 08b3d50860633bfc56107f7f9b61106c6087e70b
git checkout -b &amp;lt;choose_branch_name&amp;gt;
west update
&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;Then you should be able to run SES&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: building error / Branch error.    git merge. git pull. west update</title><link>https://devzone.nordicsemi.com/thread/180932?ContentTypeID=1</link><pubDate>Tue, 09 Apr 2019 08:11:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cb2c13a1-e636-4183-b522-8286465fd703</guid><dc:creator>Martin Lesund</dc:creator><description>&lt;p&gt;Hi Henning,&lt;/p&gt;
&lt;p&gt;&lt;em&gt;We are aware that SES does not work with the master-branch, and we are working on the fix so a new version should be released soon.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;In the meantime I would recommend you to build via &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/44879/build-nrf-connect-sdk-project-via-command-line" rel="noopener noreferrer" target="_blank"&gt;the command line as instructed here.&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="text-decoration:underline;"&gt;Note you need to add the &amp;quot;non-secure&amp;quot; for the application:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;cmake -GNinja -DBOARD=nrf9160_pca10090&lt;strong&gt;ns&lt;/strong&gt; ..&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: building error / Branch error.    git merge. git pull. west update</title><link>https://devzone.nordicsemi.com/thread/180908?ContentTypeID=1</link><pubDate>Tue, 09 Apr 2019 06:45:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1d6fce04-3162-4252-869a-058d5152a16a</guid><dc:creator>henninglindseth</dc:creator><description>&lt;p&gt;Yes, now Ive done everything on the list, I worked so far, however when I set up samples to build in SES 4.14 and 4.16 I get the error that the EMproject is not valid. and when I tried to build in command prompter is says Configuring incomplete. &lt;br /&gt;The samples worked on friday to build on the prompter.&amp;nbsp; It worked fine on friday, I had a ticket about mqtt_simple sample error, but now its closed, cause it got fixed. but after west update on saturday, nothing is working on the new repo, only v0.3.0 to upload.&lt;/p&gt;
&lt;p&gt;even done&lt;/p&gt;
&lt;pre class="highlight literal-block"&gt;set ZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb&lt;/pre&gt;
&lt;pre class="highlight literal-block"&gt;set GNUARMEMB_TOOLCHAIN_PATH=c:\gnuarmemb&lt;br /&gt;&lt;br /&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/414.PNG" /&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/416.PNG" /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/mqqterror.PNG" /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;/pre&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: building error / Branch error.    git merge. git pull. west update</title><link>https://devzone.nordicsemi.com/thread/180894?ContentTypeID=1</link><pubDate>Tue, 09 Apr 2019 06:08:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:823d3057-df8d-45e1-b456-0b25642d65f8</guid><dc:creator>Martin Lesund</dc:creator><description>&lt;p&gt;Hi Henning,&lt;/p&gt;
&lt;p&gt;Please do follow the steps shown in the Documentation referenced in my first post.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Let&amp;#39;s start from a clean slate.&lt;/li&gt;
&lt;/ul&gt;
&lt;ol&gt;
&lt;li&gt;make a folder called &amp;quot;ncs&amp;quot;&lt;/li&gt;
&lt;li&gt;inside that folder, use the command:&amp;nbsp; (&lt;em&gt;to clone the manifest repo &amp;quot;&lt;span style="text-decoration:underline;"&gt;nrf&amp;quot;&lt;/span&gt;)&lt;/em&gt;
&lt;pre&gt;west init -m &lt;a href="https://github.com/NordicPlayground/fw-nrfconnect-nrf"&gt;https://github.com/NordicPlayground/fw-nrfconnect-nrf &lt;/a&gt;&lt;/pre&gt;
&lt;/li&gt;
&lt;li&gt;Then enter the following command:&amp;nbsp; (&lt;em&gt;to clone the project repositories)&lt;/em&gt;
&lt;pre&gt;&lt;span&gt;west&lt;/span&gt; &lt;span&gt;update&lt;/span&gt;&lt;/pre&gt;
&lt;/li&gt;
&lt;li&gt;&lt;span&gt;&lt;span&gt;Then you are &lt;span style="text-decoration:underline;"&gt;done&lt;/span&gt;, and the structure should look like this:&lt;/span&gt;&lt;/span&gt;
&lt;pre&gt;&lt;span&gt;ncs&lt;/span&gt;
 &lt;span&gt;|&lt;/span&gt;&lt;span&gt;___&lt;/span&gt; &lt;span&gt;.&lt;/span&gt;&lt;span&gt;west&lt;/span&gt;
 &lt;span&gt;|&lt;/span&gt;&lt;span&gt;___&lt;/span&gt; &lt;span&gt;mcuboot&lt;/span&gt;
 &lt;span&gt;|&lt;/span&gt;&lt;span&gt;___&lt;/span&gt; &lt;span&gt;nrf&lt;/span&gt;
 &lt;span&gt;|&lt;/span&gt;&lt;span&gt;___&lt;/span&gt; &lt;span&gt;nrfxlib&lt;/span&gt;
 &lt;span&gt;|&lt;/span&gt;&lt;span&gt;___&lt;/span&gt; &lt;span&gt;zephyr&lt;/span&gt;&lt;/pre&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;/p&gt;
&lt;hr /&gt;
&lt;ul&gt;
&lt;li&gt;&lt;span style="text-decoration:underline;"&gt;&lt;strong&gt;If you want to update the repositories&lt;/strong&gt;&lt;/span&gt;, then you just do a:&lt;/li&gt;
&lt;/ul&gt;
&lt;pre&gt;&lt;span&gt;git pull&lt;/span&gt;&lt;/pre&gt;
&lt;p&gt;In the &amp;quot;&lt;strong&gt;nrf&lt;/strong&gt;&amp;quot; repo. (&lt;em&gt;&lt;span style="text-decoration:underline;"&gt;not&lt;/span&gt; nrfxlib repo as shown in your screenshot)&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;and follow that up with a:&lt;/p&gt;
&lt;pre&gt;&lt;span&gt;west&lt;/span&gt; &lt;span&gt;update &lt;/span&gt;&lt;/pre&gt;
&lt;p&gt;&lt;span&gt;To update&amp;nbsp;&lt;span style="text-decoration:underline;"&gt;all&lt;/span&gt;&lt;strong&gt;&amp;nbsp;&lt;/strong&gt;the repoes. That&amp;#39;s kind of the neat thing with &lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/guides/west/index.html" rel="noopener noreferrer" target="_blank"&gt;the west tool&lt;/a&gt;.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;So it should look like this:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;img src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/support-attachments/beef5d1b77644c448dabff31668f3a47-0a5620353574400fa373e12676d7d2b8/pastedimage1554789873605v1.png" alt=" " /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;hr /&gt;
&lt;p&gt;That the other repoes stays in a HEAD detached state is expected behavior and you do not need to change those.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/support-attachments/beef5d1b77644c448dabff31668f3a47-0a5620353574400fa373e12676d7d2b8/pastedimage1554790035584v2.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best Regards,&lt;/p&gt;
&lt;p&gt;Martin L.&lt;/p&gt;
&lt;pre&gt;&lt;/pre&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: building error / Branch error.    git merge. git pull. west update</title><link>https://devzone.nordicsemi.com/thread/180798?ContentTypeID=1</link><pubDate>Mon, 08 Apr 2019 13:52:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:75fa3a79-a2b7-44c4-8806-e99467b0413a</guid><dc:creator>henninglindseth</dc:creator><description>&lt;p&gt;&lt;img alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/gitbash.PNG" /&gt; as u see the manifest-rev and HEAD detached shows up agian after west update.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: building error / Branch error.    git merge. git pull. west update</title><link>https://devzone.nordicsemi.com/thread/180791?ContentTypeID=1</link><pubDate>Mon, 08 Apr 2019 13:44:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b1d3a183-6ab4-43a4-8564-7f4c77d5692a</guid><dc:creator>henninglindseth</dc:creator><description>&lt;p&gt;I&amp;#39;ve done west update. but it comes back with a hash instead of MASTER. didn&amp;#39;t you read the issue above? sorry a bit crancky cause I&amp;#39;va been sitting thw whole day with this thing.&lt;/p&gt;
&lt;p&gt;to check if ive done something wrong.&lt;/p&gt;
&lt;p&gt;1.&amp;nbsp; I&amp;#39;ve deleted the local repos.&lt;/p&gt;
&lt;p&gt;2. Clone them agian. and cloned the scripts etc.&lt;/p&gt;
&lt;p&gt;3. then i&amp;#39;ve initiate west whit.&amp;nbsp; west init -l (small L) nrf in the ncs directory.&lt;/p&gt;
&lt;p&gt;4. Then west update. but instead of MASTER, it comes back with a hash.&lt;/p&gt;
&lt;p&gt;5. to check what that hash is, I wrote &amp;quot; git branch &amp;quot;&amp;nbsp; there i get * (HEAD detached at refs/heads/manifest-rev)&lt;br /&gt; &amp;nbsp; and a extra branch called &amp;quot;manifest-rev&amp;quot; &lt;/p&gt;
&lt;p&gt;6. I tried to fixe the HEAD by reattche it and then merge the manifest-rev with master. even tried to delete it, but it reappare afte west update.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: building error / Branch error.    git merge. git pull. west update</title><link>https://devzone.nordicsemi.com/thread/180784?ContentTypeID=1</link><pubDate>Mon, 08 Apr 2019 13:18:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a0084e00-d5f7-4aaa-aba6-d2dfce5658ff</guid><dc:creator>Martin Lesund</dc:creator><description>&lt;p&gt;Hi Henning,&lt;/p&gt;
&lt;p&gt;Please note that when updating repositories, you should only need to pull the latest update in the &lt;strong&gt;nrf&lt;/strong&gt; repo and then just do a: west update&lt;/p&gt;
&lt;p&gt;&lt;span style="text-decoration:underline;"&gt;This is to bring the project repositories to a&amp;nbsp;&lt;strong&gt;matching&lt;/strong&gt; revision defined by the manifest file.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/gs_ins_windows.html#updating-the-repositories" rel="noopener noreferrer" target="_blank"&gt;Documentation for updating the repositories.&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>