<?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>Problem about thread OTA</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/70319/problem-about-thread-ota</link><description>I need to implement using OTA to upgrade the thread.I followed Thread Tutorial: Practical guide for device upgrade OTA provided to complete the upgrade process,but it didn&amp;#39;t success. 
 I have 3 nRF52840 Development Kits. 1 DK will run a Client + Bootloader</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 14 Jan 2021 08:20:55 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/70319/problem-about-thread-ota" /><item><title>RE: Problem about thread OTA</title><link>https://devzone.nordicsemi.com/thread/289083?ContentTypeID=1</link><pubDate>Thu, 14 Jan 2021 08:20:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:90ea605d-94a3-4c10-84a8-c1a740dd5e32</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;What is NEC v1.4.99-dev1?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;If you are talking about NCS (nRF Connect SDK), then that is a different story. I am not too experienced with NCS yet, but there is something called&amp;nbsp;mcu_boot. Zephyr has it&amp;#39;s own implementation of bootloaders and DFU, and it is not related to the bootloader in the nRF5 SDK. If you are interested in that, I suggest you open a new ticket regarding the NCS bootloader and MCU boot, as it is a different topic than this.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&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><item><title>RE: Problem about thread OTA</title><link>https://devzone.nordicsemi.com/thread/289054?ContentTypeID=1</link><pubDate>Thu, 14 Jan 2021 03:33:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0e176252-209b-4824-bd42-9474b96a64ae</guid><dc:creator>taoyinzhou</dc:creator><description>&lt;p&gt;&lt;span&gt;Hi&amp;nbsp;Edvin,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;It worked successfully.Thanks.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;I have one more question. I actually want to implement DFU on&amp;nbsp; NEC v1.4.99-dev1, is there any example?&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;winik&lt;/p&gt;
&lt;p&gt;&lt;span&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Problem about thread OTA</title><link>https://devzone.nordicsemi.com/thread/288873?ContentTypeID=1</link><pubDate>Wed, 13 Jan 2021 10:14:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9f356422-3892-434d-ae83-87952522744c</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;So that means that it is working? Did the LED4 turn on on the client DK after a while? (NB: It takes a while). If not, can you open an RTT viewer to monitor the log from the client DK? Also, make sure that the Thread channel used on the client DK is 12. It should be set in sdk_config.h in the dfu2 folder I sent you, in the client\pca10056\blank\config\sdk_config:&lt;/p&gt;
&lt;p&gt;#define THREAD_CHANNEL 12&lt;/p&gt;
&lt;p&gt;I don&amp;#39;t know if it makes a difference, but please set this in the NCP example as well:&lt;/p&gt;
&lt;p&gt;sdk\examples\thread\ncp\ftd\uart\pca10056\blank\config\sdk_config.h.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;If it doesn&amp;#39;t work, please let me know what the RTT log of the client DK says.&lt;/p&gt;
&lt;p&gt;&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><item><title>RE: Problem about thread OTA</title><link>https://devzone.nordicsemi.com/thread/288805?ContentTypeID=1</link><pubDate>Wed, 13 Jan 2021 06:35:26 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a2946e78-438f-4351-bedf-8b45e13e40b3</guid><dc:creator>taoyinzhou</dc:creator><description>&lt;p&gt;I ran the dfu2 file you gave me, here is the output from the terminal, the output just keeps pausing at &amp;quot;Thread DFU server is running... Press &amp;lt;Ctrl + D&amp;gt; to stop. &amp;quot;this line.&lt;pre class="ui-code" data-mode="text"&gt;D:\widic\nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\examples\thread\dfu2&amp;gt;set DFU_SERVER_COM_PORT=COM6

D:\widic\nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\examples\thread\dfu2&amp;gt;set DFU_SERVER_DK=683193868

D:\widic\nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\examples\thread\dfu2&amp;gt;set CLIENT_DK_SNR=683571084

D:\widic\nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\examples\thread\dfu2&amp;gt;make -j9 -C bootloader\pca10056\blank\armgcc
make: Entering directory &amp;#39;D:/widic/nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8/examples/thread/dfu2/bootloader/pca10056/blank/armgcc&amp;#39;
make: *** No rule to make target &amp;#39;c\:\arm-gcc\lib\gcc\arm-none-eabi\10.2.1\include\stdint.h&amp;#39;, needed by &amp;#39;_build/nrf52840_xxaa_mbr/bsp.c.o&amp;#39;.  Stop.
make: Leaving directory &amp;#39;D:/widic/nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8/examples/thread/dfu2/bootloader/pca10056/blank/armgcc&amp;#39;

D:\widic\nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\examples\thread\dfu2&amp;gt;make -j9 -C client\pca10056\blank\armgcc
make: Entering directory &amp;#39;D:/widic/nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8/examples/thread/dfu2/client/pca10056/blank/armgcc&amp;#39;
make: *** No rule to make target &amp;#39;c\:\arm-gcc\lib\gcc\arm-none-eabi\10.2.1\include\stdint.h&amp;#39;, needed by &amp;#39;_build/nrf52840_xxaa/bsp.c.o&amp;#39;.  Stop.
make: Leaving directory &amp;#39;D:/widic/nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8/examples/thread/dfu2/client/pca10056/blank/armgcc&amp;#39;

D:\widic\nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\examples\thread\dfu2&amp;gt;make -j9 -C ..\ncp\ftd\uart\pca10056\blank\armgcc\
make: Entering directory &amp;#39;D:/widic/nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8/examples/thread/ncp/ftd/uart/pca10056/blank/armgcc&amp;#39;
make: *** No rule to make target &amp;#39;c\:\arm-gcc\lib\gcc\arm-none-eabi\10.2.1\include\stdint.h&amp;#39;, needed by &amp;#39;_build/nrf52840_xxaa/boards.c.o&amp;#39;.  Stop.
make: Leaving directory &amp;#39;D:/widic/nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8/examples/thread/ncp/ftd/uart/pca10056/blank/armgcc&amp;#39;

D:\widic\nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\examples\thread\dfu2&amp;gt;del files\settings.hex

D:\widic\nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\examples\thread\dfu2&amp;gt;nrfutil settings generate --family NRF52840 --application client\pca10056\blank\armgcc\_build\nrf52840_xxaa.hex --application-version 1 --bootloader-version 1 --bl-settings-version 2 files\settings.hex

Note: Generating a DFU settings page with backup page included.
This is only required for bootloaders from nRF5 SDK 15.1 and newer.
If you want to skip backup page generation, use --no-backup option.

Generated Bootloader DFU settings .hex file and stored it in: files\settings.hex

Bootloader DFU Settings:
* File:                     files\settings.hex
* Family:                   NRF52840
* Start Address:            0x000FF000
* CRC:                      0x8736CF1A
* Settings Version:         0x00000002 (2)
* App Version:              0x00000001 (1)
* Bootloader Version:       0x00000001 (1)
* Bank Layout:              0x00000000
* Current Bank:             0x00000000
* Application Size:         0x000642E0 (410336 bytes)
* Application CRC:          0xDA4F70D9
* Bank0 Bank Code:          0x00000001
* Softdevice Size:          0x00000000 (0 bytes)
* Boot Validation CRC:      0xAFFD6110
* SD Boot Validation Type:  0x00000000 (0)
* App Boot Validation Type: 0x00000001 (1)


D:\widic\nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\examples\thread\dfu2&amp;gt;del files\dfu_client.hex

D:\widic\nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\examples\thread\dfu2&amp;gt;mergehex -m client\pca10056\blank\armgcc\_build\nrf52840_xxaa.hex files\settings.hex -o files\dfu_client.hex
Parsing input files.
Merging file &amp;quot;nrf52840_xxaa.hex&amp;quot; into output.
Merging file &amp;quot;settings.hex&amp;quot; into output.
Storing merged file.

D:\widic\nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\examples\thread\dfu2&amp;gt;nrfjprog -e --snr 683571084
Erasing user available code and UICR flash areas.
Applying system reset.

D:\widic\nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\examples\thread\dfu2&amp;gt;nrfjprog -e --snr 683193868
Erasing user available code and UICR flash areas.
Applying system reset.

D:\widic\nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\examples\thread\dfu2&amp;gt;nrfjprog --program ..\..\..\components\softdevice\mbr\hex\mbr_nrf52_2.4.1_mbr.hex --verify --snr 683571084
Parsing image file.
Reading flash area to program to guarantee it is erased.
Checking that the area to write is not protected.
Programming device.
Verifying programming.
Verified OK.

D:\widic\nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\examples\thread\dfu2&amp;gt;nrfjprog --program bootloader\pca10056\blank\armgcc\_build\nrf52840_xxaa_mbr.hex --verify --snr 683571084
Parsing image file.
Reading flash area to program to guarantee it is erased.
Checking that the area to write is not protected.
Programming device.
Verifying programming.
Verified OK.

D:\widic\nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\examples\thread\dfu2&amp;gt;nrfjprog --program files\dfu_client.hex --verify --snr 683571084
Parsing image file.
Reading flash area to program to guarantee it is erased.
Checking that the area to write is not protected.
Programming device.
Verifying programming.
Verified OK.

D:\widic\nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\examples\thread\dfu2&amp;gt;nrfjprog --reset --snr 683571084
Applying system reset.
Run.

D:\widic\nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\examples\thread\dfu2&amp;gt;del files\app_dfu_package.zip

D:\widic\nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\examples\thread\dfu2&amp;gt;nrfutil pkg generate --hw-version 52 --sd-req 0x00 --application-version 2 --application files\app_3.hex --key-file ..\..\dfu\private.pem files\app_dfu_package.zip
Zip created at files\app_dfu_package.zip

D:\widic\nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\examples\thread\dfu2&amp;gt;nrfjprog --program ..\ncp\ftd\uart\pca10056\blank\armgcc\_build\nrf52840_xxaa.hex --verify --snr 683193868
Parsing image file.
Reading flash area to program to guarantee it is erased.
Checking that the area to write is not protected.
Programming device.
Verifying programming.
Verified OK.

D:\widic\nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\examples\thread\dfu2&amp;gt;nrfjprog --reset --snr 683193868
Applying system reset.
Run.

D:\widic\nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\examples\thread\dfu2&amp;gt;TIMEOUT 5

等待 0 秒，按一个键继续 ...

D:\widic\nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\examples\thread\dfu2&amp;gt;nrfutil dfu thread -pkg files\app_dfu_package.zip -p COM6 --channel 12 --panid 43981
Address not specified. Using ff03::1 (all Thread nodes)
Using connectivity board at serial port: COM6
Waiting for NCP to promote to a router...
Thread DFU server is running... Press &amp;lt;Ctrl + D&amp;gt; to stop.



&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Problem about thread OTA</title><link>https://devzone.nordicsemi.com/thread/288593?ContentTypeID=1</link><pubDate>Tue, 12 Jan 2021 10:13:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c4bf4a0a-6a7a-4d06-a776-a6eba3e458fa</guid><dc:creator>Edvin</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;I have not tested the guide that you linked to before, but perhaps you can try out the following test guide:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://infocenter.nordicsemi.com/topic/sdk_tz_v4.1.0/thread_example_dfu.html?cp=7_3_2_10_4_0_2#thread_example_dfu_test"&gt;https://infocenter.nordicsemi.com/topic/sdk_tz_v4.1.0/thread_example_dfu.html?cp=7_3_2_10_4_0_2#thread_example_dfu_test&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;If you try to run unzip and the dfu folder attached here in SDK\examples\dfu2, and run the test.bat script (change the serial numbers and COM port near the top of test.bat), does that work in your case? If not, what does the terminal output say?&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/dfu2.zip"&gt;devzone.nordicsemi.com/.../dfu2.zip&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&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>