<?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>Thingy:91 stopped being responsive during activation</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/105094/thingy-91-stopped-being-responsive-during-activation</link><description>Hello, 
 The other day we received or batch of devices and started getting to know them. 
 For the Thingy:91 I followed the instructions in the video guide provided here . 
 One advice about this guide - it&amp;#39;s good to be mentioned that the MicroUSB cable</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 13 Jun 2023 14:49:14 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/105094/thingy-91-stopped-being-responsive-during-activation" /><item><title>RE: Thingy:91 stopped being responsive during activation</title><link>https://devzone.nordicsemi.com/thread/452530?ContentTypeID=1</link><pubDate>Tue, 13 Jun 2023 14:49:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:23cbfe07-1335-467a-a2cb-b2a71f561af3</guid><dc:creator>Ivan Popov</dc:creator><description>&lt;p&gt;Thanks for all of these resources! I&amp;#39;ll definitely make some time to check them.&lt;br /&gt;We are waiting for some more confirmations but it appear that finding a proper operator that supports at least one of the two protocols here will be problematic. I guess that freezes the usage of Thingy:91 for us for the moment. :/ Very sad.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;On the device level I watched the logs in the LTE Link Monitor - the missing network was confirmed there; and the RSSI Viewer only shows an empty diagram.&lt;/p&gt;
&lt;p&gt;The person who bought the device was actually convinced that we will be able to use it through WiFi but we&amp;#39;ve seen that this is not an option. The same goes for the other two Thing:53 units which we&amp;#39;ll have to access through a Blutooth Mesh or with a Zigbee Gateway.&lt;/p&gt;
&lt;p&gt;I guess at this point I&amp;#39;ll just close the ticket.&lt;/p&gt;
&lt;p&gt;Thank you for your support,&amp;nbsp;&lt;span&gt;Øyvind!&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Best regards,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Ivan&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Thingy:91 stopped being responsive during activation</title><link>https://devzone.nordicsemi.com/thread/452529?ContentTypeID=1</link><pubDate>Tue, 13 Jun 2023 12:19:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2aaed599-3abe-4e7b-a0c4-24bdd7984b41</guid><dc:creator>&amp;#216;yvind</dc:creator><description>[quote user="Ivan Popov"] elsewhere in the forum that it is possible to use another SIM provider with nrfCloud[/quote]
&lt;p&gt;nRF Cloud is only used to activate and manage the iBasis SIM provided with your DK or Thingy:91. There is no special SIM&amp;nbsp;provider&amp;nbsp;needed to use nRF Cloud.&lt;/p&gt;
[quote user="Ivan Popov"]Further on we are checking the possibilities to write our own software to receive and manage the data from the sensors. I guess your presentation &lt;a href="https://www.youtube.com/watch?v=KSivO9Cf1TE"&gt;here&lt;/a&gt; is good starting point?[/quote]
&lt;p&gt;Yes, you can start with that, but please note that the video is fairly outdated in regards to our latest version of the SDK.&amp;nbsp;You can follow that webinar, but there are changes introduced to later versions.&lt;/p&gt;
&lt;p&gt;You could have a look at our partner Golioth.io, they have upcoming trainings&lt;br /&gt;&lt;a href="https://blog.golioth.io/free-zephyr-training-hosted-by-golioth-june-7th-2023/"&gt;https://blog.golioth.io/free-zephyr-training-hosted-by-golioth-june-7th-2023/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Jared Wolff a.k.a. Circuit Dojo also has some good videos on YouTube&amp;nbsp;&lt;a href="https://www.youtube.com/c/circuitdojo"&gt;https://www.youtube.com/c/circuitdojo&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;These cover a lot of ground, and provide a lot of good insight in the Zephyr OS.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Thingy:91 stopped being responsive during activation</title><link>https://devzone.nordicsemi.com/thread/452528?ContentTypeID=1</link><pubDate>Tue, 13 Jun 2023 08:29:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:45280028-29e2-4508-8902-6d3a28023070</guid><dc:creator>Ivan Popov</dc:creator><description>&lt;p&gt;Hi&amp;nbsp;&lt;span&gt;Øyvind,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;We are just searching through our possible options for a local LTE-M provider (the NB-IoT connectivity doesn&amp;#39;t seem to be suitable for our case of sending frequent vibration data from the IMU) because I&amp;#39;ve seen elsewhere in the forum that it is possible to use another SIM provider with nrfCloud.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Further on we are checking the possibilities to write our own software to receive and manage the data from the sensors. I guess your presentation &lt;a href="https://www.youtube.com/watch?v=KSivO9Cf1TE"&gt;here&lt;/a&gt; is good starting point?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;There&amp;#39;s so much ground to cover but it&amp;#39;s quite exciting and interesting.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Cheers!&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Ivan&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Thingy:91 stopped being responsive during activation</title><link>https://devzone.nordicsemi.com/thread/452527?ContentTypeID=1</link><pubDate>Tue, 13 Jun 2023 08:18:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1b4ac8c9-75c7-4ffe-a827-f36ac6c1f1bf</guid><dc:creator>&amp;#216;yvind</dc:creator><description>[quote user="Ivan Popov"]Ahh! Now that&amp;#39;s more like it. Three simple steps of uploading the three correct files in the correct order. Now it&amp;#39;s blinking again.[/quote]
&lt;p&gt;That is very good to hear! &lt;span class="emoticon" data-url="https://devzone.nordicsemi.com/cfs-file/__key/system/emoji/1f642.svg" title="Slight smile"&gt;&amp;#x1f642;&lt;/span&gt;&lt;/p&gt;
[quote user="Ivan Popov"] I have a blinking (yellow-green) Thingy and it blinks forever. The eSIM is registered and marked active in the system[/quote]
&lt;p&gt;From the User Interface module of the Asset Tracker v2 application, we can see that yellow LED means it is searching for LTE. This could verify your assumption of not being in iBasis coverage. Note that it can take some time (up to 15 minutes) before being able to connect.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;From the 40412 error description we see that there are 5 scenarios which can report this error code.&amp;nbsp;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;You entered the device id and/or ownership code (PIN or HWID) incorrectly.&lt;/li&gt;
&lt;li&gt;Before attempting association, you did not wait for the LEDs to indicate the device was provisioned.&lt;/li&gt;
&lt;li&gt;Corrupt modem firmware.&lt;/li&gt;
&lt;li&gt;Corrupt, wrongly flashed, or illegitimate device certificates.&lt;/li&gt;
&lt;li&gt;Poor LTE connection&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Do you have access to another SIM, i.e. local SIM which has LTE-M/NB-IoT enabled to verify connection/iBasis issues?&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;br /&gt;Øyvind&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Thingy:91 stopped being responsive during activation</title><link>https://devzone.nordicsemi.com/thread/452526?ContentTypeID=1</link><pubDate>Mon, 12 Jun 2023 12:39:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c5d26b63-5482-4f60-963d-fb1af664bf27</guid><dc:creator>Ivan Popov</dc:creator><description>&lt;p&gt;Ahh! Now that&amp;#39;s more like it. Three simple steps of uploading the three correct files in the correct order. Now it&amp;#39;s blinking again.&lt;/p&gt;
&lt;p&gt;I guess the CONTENTS.txt file is not clear enough for beginners like me and the concept of bridge first, firmware next, and asset tracker application in the end somehow is a core knowledge that I missed.&lt;/p&gt;
&lt;p&gt;But now I&amp;#39;m again at the point where the problem started - I have a blinking (yellow-green) Thingy and it blinks forever. The eSIM is registered and marked active in the system. Now after waiting much more than three minutes for the light to become white what comes to my mind is:&lt;/p&gt;
&lt;p&gt;- I&amp;#39;m not in the iBASIS coverage ...despite the fact that &lt;a href="https://ibasis.com/solutions/iot-connectivity/coverage-usage-guidance/"&gt;according to their site&lt;/a&gt; Bulgaria is in the Zone 1 of their coverage ...&lt;/p&gt;
&lt;p&gt;- Or I missed some other step ...&lt;/p&gt;
&lt;p&gt;If at this point I go to the nrfCloud and try to register the Thingy as an LTE device it rightfully&amp;nbsp;responds with &lt;a href="https://api.nrfcloud.com/v1/#section/Error-Codes/40412"&gt;the 40412 error&lt;/a&gt;, even with correct values for Device ID and PIN.&lt;/p&gt;
&lt;p&gt;Any ideas here?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Ivan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Thingy:91 stopped being responsive during activation</title><link>https://devzone.nordicsemi.com/thread/452525?ContentTypeID=1</link><pubDate>Mon, 12 Jun 2023 09:45:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a9b8ef6d-080d-4996-8388-eb9b9af41ce1</guid><dc:creator>&amp;#216;yvind</dc:creator><description>&lt;p&gt;Ivan, I think I see the problem.&amp;nbsp;&lt;/p&gt;
[quote user="Ivan Popov"]The first step (updating the&amp;nbsp;nRF52840 SoC firmware) went fine:[/quote]
&lt;p&gt;Here it seems that you have programmed the wrong file. The nRF52840 is what provides the USB connection, but it needs the Connectivity Bridge (img_fota_dfu_hex\thingy91_nrf52_connectivity_bridge_2023-03-02_8f26142b.hex).&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Can you please reprogram the nRF52840 with that image, and then program the nRF9160 with the Asset Tracker v2?&lt;/p&gt;
&lt;p&gt;Thanks!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Thingy:91 stopped being responsive during activation</title><link>https://devzone.nordicsemi.com/thread/452524?ContentTypeID=1</link><pubDate>Mon, 12 Jun 2023 08:15:12 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7488a67d-24d4-4a99-a0e5-f8fd376f9a72</guid><dc:creator>Ivan Popov</dc:creator><description>&lt;p&gt;&lt;span&gt;Hello Øyvind,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Thanks for the informative reply!&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;I wen to the Getting Sarted guide in the documentation, as you suggested, and started the process all over.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;The first step (updating the&amp;nbsp;nRF52840 SoC firmware) went fine:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/Screenshot-from-2023_2D00_06_2D00_12-10_2D00_46_2D00_32.png" alt=" " /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;span&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/Screenshot-from-2023_2D00_06_2D00_12-10_2D00_47_2D00_00.png" alt=" " /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;span&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/Screenshot-from-2023_2D00_06_2D00_12-10_2D00_47_2D00_38.png" alt=" " /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;After that, on the second step (updating the firmware for the&amp;nbsp;nRF9160 SiP) thing started to diverge from the documentation instructions:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;At first the device doesn&amp;#39;t appear at all in the &amp;quot;Select Device&amp;quot; menu:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/Screenshot-from-2023_2D00_06_2D00_12-10_2D00_53_2D00_45.png" alt=" " /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;And then even despite the fact I try to write the firmware ZIP file, I can select it but the Programmer gives me the following warning and the Write button is not responsive:&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/Screenshot-from-2023_2D00_06_2D00_12-10_2D00_56_2D00_16.png" alt=" " /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/Screenshot-from-2023_2D00_06_2D00_12-10_2D00_57_2D00_04.png" alt=" " /&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Any ideas?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Regards,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Ivan&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Thingy:91 stopped being responsive during activation</title><link>https://devzone.nordicsemi.com/thread/452523?ContentTypeID=1</link><pubDate>Fri, 09 Jun 2023 10:05:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:add83770-8028-4324-891f-03195cc5baa0</guid><dc:creator>&amp;#216;yvind</dc:creator><description>&lt;p&gt;Hello Ivan,&amp;nbsp;&lt;br /&gt;&lt;br /&gt;When updating the modem FW over MCUBoot/USB, this will erase the whole flash including the application. This is why your device is no longer flashing, and you will need to reprogram the application as well.&lt;/p&gt;
&lt;p&gt;You should follow the&amp;nbsp;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.4.0/nrf/working_with_nrf/nrf91/thingy91_gsg.html#getting-started-with-thingy-91"&gt;Getting started with Thingy:91&lt;/a&gt;, which is more up to date than the video you are referring to.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;After updating the modem FW you should program the Asset Tracker v2 application, which is found &lt;a href="https://www.nordicsemi.com/Products/Development-hardware/Nordic-Thingy-91/Download?lang=en#infotabs"&gt;in our pre-compiled FW package&lt;/a&gt; (under the downloads tab on the Thingy:91 product page). Make sure to program the&amp;nbsp;&lt;span&gt;img_fota_dfu_hex/thingy91_asset_tracker_v2_2023-06-01_0677b099.hex if using MCUBoot. See more information in the Getting started guide.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;After doing so, you should be able to add the device to nRF Cloud as this application will provision your device. You can use the LTE Link Monitor to view the output from the application.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Let me know how that works.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Kind regards,&lt;br /&gt;Øyvind&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>