<?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>IoT DFU on Contiki using CoAP Blocktransfer</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/23490/iot-dfu-on-contiki-using-coap-blocktransfer</link><description>[Aim]
I am working on a project where I aimed to Integrate/Develop firmware management system using Contiki running over Nordic NRF52. 
 [Components]
Contiki running over Nordic NRF52 + LwM2M (Management server) + CoAP block transfer (Transport Medium</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sat, 15 Jul 2017 12:27:04 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/23490/iot-dfu-on-contiki-using-coap-blocktransfer" /><item><title>RE: IoT DFU on Contiki using CoAP Blocktransfer</title><link>https://devzone.nordicsemi.com/thread/92270?ContentTypeID=1</link><pubDate>Sat, 15 Jul 2017 12:27:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b0523614-331f-4e7f-b91f-2592c11adfb3</guid><dc:creator>Manas</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I figured out the cause and writing it down.&lt;/p&gt;
&lt;p&gt;In NRF port of contiki there is no sys evt handler (in addition to the ble evt handler that is already registered) in cpu/nrf52832/ble/ble-core.c.&lt;/p&gt;
&lt;p&gt;Registering a sys evt handler and calling &amp;quot;pstorage_sys_event_handler(event)&amp;quot; from the handler would solve the purpose.&lt;/p&gt;
&lt;p&gt;PS: Seems like attachments is having some issue as I can&amp;#39;t attach the patch with this post.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>