<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>i.MX ProcessorsのトピックRe: uboot for MX8MM can't authenticate kernel</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/uboot-for-MX8MM-can-t-authenticate-kernel/m-p/1201927#M166739</link>
    <description>&lt;P&gt;It turns out the the kernel was being loaded at a non-standard location, so the signing script needed changed.&lt;/P&gt;</description>
    <pubDate>Fri, 18 Dec 2020 19:36:12 GMT</pubDate>
    <dc:creator>adam_m</dc:creator>
    <dc:date>2020-12-18T19:36:12Z</dc:date>
    <item>
      <title>uboot for MX8MM can't authenticate kernel</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/uboot-for-MX8MM-can-t-authenticate-kernel/m-p/1196982#M166207</link>
      <description>&lt;P&gt;I am working on getting uboot to load a secure kernel on a Boundary Devices Nitrogen8MM. I have already worked through the instructions at &lt;A href="https://boundarydevices.com/high-assurance-boot-hab-i-mx8m-edition/" target="_blank"&gt;https://boundarydevices.com/high-assurance-boot-hab-i-mx8m-edition/&lt;/A&gt; and eveything is working with a sigend uboot.&lt;/P&gt;&lt;P&gt;According to BoundaryDevices, they have been told by NXP that the next step is to get booi to auth the kernel by using this patch: &lt;A href="https://github.com/boundarydevices/u-boot-imx6/commit/a20a5ee3c0" target="_blank"&gt;https://github.com/boundarydevices/u-boot-imx6/commit/a20a5ee3c0&lt;/A&gt; However, it's not working.&lt;/P&gt;&lt;P&gt;When I auth the kernel by hand using hab_auth_img, it appears to work just fine:&lt;/P&gt;&lt;PRE&gt;=&amp;gt; load mmc 1 ${loadaddr} Image&lt;BR /&gt;30009696 bytes read in 679 ms (42.1 MiB/s)&lt;BR /&gt;=&amp;gt; hab_auth_img ${loadaddr} ${filesize} 0x01c9d000&lt;BR /&gt;&lt;BR /&gt;Authenticate image from DDR location 0x40480000...&lt;BR /&gt;&lt;BR /&gt;Secure boot enabled&lt;BR /&gt;&lt;BR /&gt;HAB Configuration: 0xcc, HAB State: 0x99&lt;BR /&gt;No HAB Events Found!&lt;BR /&gt;&lt;BR /&gt;=&amp;gt;&lt;/PRE&gt;&lt;P&gt;&lt;BR /&gt;But when just booting I get this:&lt;/P&gt;&lt;PRE&gt;Authenticating Image...&lt;BR /&gt;&lt;BR /&gt;Authenticate image from DDR location 0x40800000...&lt;BR /&gt;Error: Invalid IVT structure&lt;BR /&gt;&lt;BR /&gt;Allowed IVT structure:&lt;BR /&gt;IVT HDR = 0x4X2000D1&lt;BR /&gt;IVT ENTRY = 0xXXXXXXXX&lt;BR /&gt;IVT RSV1 = 0x0&lt;BR /&gt;IVT DCD = 0x0&lt;BR /&gt;IVT BOOT_DATA = 0xXXXXXXXX&lt;BR /&gt;IVT SELF = 0xXXXXXXXX&lt;BR /&gt;IVT CSF = 0xXXXXXXXX&lt;BR /&gt;IVT RSV2 = 0x0&lt;BR /&gt;Authenticate Image Fail, Please check&lt;BR /&gt;Error loading kernel image&lt;/PRE&gt;&lt;P&gt;&lt;BR /&gt;And, of course, if I don't use the patch then it boots just fine, but I need to auth the kernel before leading.&lt;/P&gt;&lt;P&gt;What am I missing?&lt;/P&gt;</description>
      <pubDate>Thu, 10 Dec 2020 00:19:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/uboot-for-MX8MM-can-t-authenticate-kernel/m-p/1196982#M166207</guid>
      <dc:creator>adam_m</dc:creator>
      <dc:date>2020-12-10T00:19:54Z</dc:date>
    </item>
    <item>
      <title>Re: uboot for MX8MM can't authenticate kernel</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/uboot-for-MX8MM-can-t-authenticate-kernel/m-p/1199311#M166466</link>
      <description>&lt;P&gt;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/181279"&gt;@adam_m&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;Hello,&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;P&gt;1.&amp;nbsp; Please check if parameters "&lt;SPAN class="blob-code-inner blob-code-marker" data-code-marker="+"&gt;ld", "image_size"&lt;/SPAN&gt; in patch function&amp;nbsp; &lt;SPAN class="blob-code-inner blob-code-marker" data-code-marker="+"&gt;&lt;SPAN class="pl-c1"&gt;authenticate_image&lt;/SPAN&gt;(ld, image_size)&lt;BR /&gt;are the same as in case of manual verification -&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;PRE&gt;hab_auth_img ${loadaddr} ${filesize}&lt;/PRE&gt;
&lt;P&gt;&lt;SPAN class="blob-code-inner blob-code-marker" data-code-marker="+"&gt;&lt;BR /&gt;2. Is IVT added to the kernel before signing?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;BR /&gt;Yuri.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Dec 2020 04:09:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/uboot-for-MX8MM-can-t-authenticate-kernel/m-p/1199311#M166466</guid>
      <dc:creator>Yuri</dc:creator>
      <dc:date>2020-12-15T04:09:56Z</dc:date>
    </item>
    <item>
      <title>Re: uboot for MX8MM can't authenticate kernel</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/uboot-for-MX8MM-can-t-authenticate-kernel/m-p/1201927#M166739</link>
      <description>&lt;P&gt;It turns out the the kernel was being loaded at a non-standard location, so the signing script needed changed.&lt;/P&gt;</description>
      <pubDate>Fri, 18 Dec 2020 19:36:12 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/uboot-for-MX8MM-can-t-authenticate-kernel/m-p/1201927#M166739</guid>
      <dc:creator>adam_m</dc:creator>
      <dc:date>2020-12-18T19:36:12Z</dc:date>
    </item>
  </channel>
</rss>

