<?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>nRF9160 custom modem updater: calculated SHA256 of modem firmware differs from digest.txt file</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/117893/nrf9160-custom-modem-updater-calculated-sha256-of-modem-firmware-differs-from-digest-txt-file</link><description>Hi, 
 I&amp;#39;m working on implementing a modem upload feature (using probe-rs) to be integrated into our production programming line. 
 Following the procedure described here ( docs.nordicsemi.com/.../device_setup.html) all seems to go well, but when calculating</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 09 Jan 2025 15:34:33 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/117893/nrf9160-custom-modem-updater-calculated-sha256-of-modem-firmware-differs-from-digest-txt-file" /><item><title>RE: nRF9160 custom modem updater: calculated SHA256 of modem firmware differs from digest.txt file</title><link>https://devzone.nordicsemi.com/thread/517763?ContentTypeID=1</link><pubDate>Thu, 09 Jan 2025 15:34:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4c1195f5-0d36-4c43-9784-6706475c7d11</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;There is&amp;nbsp;&lt;a href="https://docs.nordicsemi.com/bundle/nrfxlib-apis-latest/page/group_nrf_modem_bootloader_ga436e4efba426a6238a2120ab2a18a186.html#ga436e4efba426a6238a2120ab2a18a186"&gt;nrf_modem_bootloader_digest()&lt;/a&gt;&amp;nbsp;function (from&amp;nbsp;&lt;a href="https://docs.nordicsemi.com/bundle/nrfxlib-apis-latest/page/group_nrf_modem_bootloader.html"&gt;bootloader API&lt;/a&gt;) which should be used for reading digest hash data from the modem.&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF9160 custom modem updater: calculated SHA256 of modem firmware differs from digest.txt file</title><link>https://devzone.nordicsemi.com/thread/517679?ContentTypeID=1</link><pubDate>Thu, 09 Jan 2025 12:15:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:eeac267c-187c-4bb1-ab0a-a9330540dc3d</guid><dc:creator>rogierl</dc:creator><description>&lt;p&gt;Ok.. comment to self:&lt;/p&gt;
&lt;p&gt;What I suspect is going on is that the input hex files (from the zip archive) are encrypted and the given SHA256 hashes (in the digest.txt) are the digests of the non-encrypted data.. In other words, only the modem firmware itself can calculate the correct digest over the decoded/decrypted firmware image segments. Doh.&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;Does this&amp;nbsp;make sense..?&lt;/p&gt;
&lt;p&gt;In essence this comes down to just RTFM..&amp;nbsp;&lt;span class="emoticon" data-url="https://devzone.nordicsemi.com/cfs-file/__key/system/emoji/1f601.svg" title="Grin"&gt;&amp;#x1f601;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>