<?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>Unable to install SDK requirements</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/50264/unable-to-install-sdk-requirements</link><description>when I try to run: pip3 install -r mcuboot\scripts\requirements.txt, it fails with the following; 
 Collecting cryptography (from -r mcuboot\scripts\requirements.txt (line 1)) Using cached files.pythonhosted.org/.../cryptography-2.7.tar.gz Installing</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 26 Jul 2019 13:52:36 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/50264/unable-to-install-sdk-requirements" /><item><title>RE: Unable to install SDK requirements</title><link>https://devzone.nordicsemi.com/thread/200788?ContentTypeID=1</link><pubDate>Fri, 26 Jul 2019 13:52:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:49650fc9-9a89-44d8-b45d-15caa145eaee</guid><dc:creator>Randall</dc:creator><description>&lt;p&gt;OK.&amp;nbsp; That finally worked.&amp;nbsp; I ended up having to re-clone the SDK repository (I think all my previous distortions screwed everything up).&amp;nbsp; I&amp;#39;m not sure how python38 got installed.&amp;nbsp; It seems like if one choco install python you will get 3.8, but based on a listing of choco packages, I uinstalled python, then did a choco install python3.&amp;nbsp; That gave me 3.7.4.&amp;nbsp; That allowed the requirements.txt to work, but I still had to manually install pyelftools.&amp;nbsp; Not sure why.&amp;nbsp; After all that I was able to successfully build and flash at_client.&amp;nbsp; Still working on command line.&amp;nbsp; It is my understanding from other posts that the most recent version is having some problems with the SEGGER IDE so I&amp;#39;m leaving that for future study.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks for the help Edvin,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Randall&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to install SDK requirements</title><link>https://devzone.nordicsemi.com/thread/200763?ContentTypeID=1</link><pubDate>Fri, 26 Jul 2019 12:16:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5e596a8c-7cf6-433e-b6da-f563b60bf2f6</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I see that you use python38 in your paths. Can you please try to downgrade to Python 3.7.&lt;/p&gt;
&lt;p&gt;If that doesn&amp;#39;t help:&lt;/p&gt;
&lt;p&gt;Have you followed the Getting Started Assistant from nRF Connect for Desktop? Did all the checkpoints before pip3 install -r mcuboot\scripts\requirements.txt work? Are they green?&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Edvin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>