<?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>topic Secure boot enabling on A core [Linux] in S32G</title>
    <link>https://community.nxp.com/t5/S32G/Secure-boot-enabling-on-A-core-Linux/m-p/1960430#M10897</link>
    <description>&lt;P&gt;The bsp version that i am using is bsp 40.&lt;BR /&gt;I have included the below lines in local.conf :&lt;BR /&gt;DISTRO_FEATURES:append = " secboot"&lt;BR /&gt;NXP_FIRMWARE_LOCAL_DIR = "&lt;/P&gt;&lt;P&gt;/yocto-s32/sources/meta-alb/recipes-bsp/hse"&lt;BR /&gt;I have placed the firmware folder in this path :&lt;BR /&gt;I am not sure while building this by bitbake ros-image-core I am getting the following error and not sure why is it fetching for arm-trusted-firmware-tools :&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;Failed to fetch URL git://github.com/nxp-auto-linux/arm-trusted-firmware.git;protocol=https;branch=release/bsp40.0-2.10, attempting MIRRORS if available&lt;BR /&gt;ERROR: arm-trusted-firmware-tools-native-2.10-r0 do_fetch: Fetcher failure: Unable to find revision b6c0948400594e3cc4dbb5a4ef04b815d2675808 in branch release/bsp40.0-2.10 even from upstream&lt;/SPAN&gt;&lt;/SPAN&gt;.&lt;/P&gt;</description>
    <pubDate>Tue, 24 Sep 2024 06:01:57 GMT</pubDate>
    <dc:creator>ashwini2024</dc:creator>
    <dc:date>2024-09-24T06:01:57Z</dc:date>
    <item>
      <title>Secure boot enabling on A core [Linux]</title>
      <link>https://community.nxp.com/t5/S32G/Secure-boot-enabling-on-A-core-Linux/m-p/1960430#M10897</link>
      <description>&lt;P&gt;The bsp version that i am using is bsp 40.&lt;BR /&gt;I have included the below lines in local.conf :&lt;BR /&gt;DISTRO_FEATURES:append = " secboot"&lt;BR /&gt;NXP_FIRMWARE_LOCAL_DIR = "&lt;/P&gt;&lt;P&gt;/yocto-s32/sources/meta-alb/recipes-bsp/hse"&lt;BR /&gt;I have placed the firmware folder in this path :&lt;BR /&gt;I am not sure while building this by bitbake ros-image-core I am getting the following error and not sure why is it fetching for arm-trusted-firmware-tools :&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&lt;SPAN class=""&gt;Failed to fetch URL git://github.com/nxp-auto-linux/arm-trusted-firmware.git;protocol=https;branch=release/bsp40.0-2.10, attempting MIRRORS if available&lt;BR /&gt;ERROR: arm-trusted-firmware-tools-native-2.10-r0 do_fetch: Fetcher failure: Unable to find revision b6c0948400594e3cc4dbb5a4ef04b815d2675808 in branch release/bsp40.0-2.10 even from upstream&lt;/SPAN&gt;&lt;/SPAN&gt;.&lt;/P&gt;</description>
      <pubDate>Tue, 24 Sep 2024 06:01:57 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/Secure-boot-enabling-on-A-core-Linux/m-p/1960430#M10897</guid>
      <dc:creator>ashwini2024</dc:creator>
      <dc:date>2024-09-24T06:01:57Z</dc:date>
    </item>
    <item>
      <title>Re: Secure boot enabling on A core [Linux]</title>
      <link>https://community.nxp.com/t5/S32G/Secure-boot-enabling-on-A-core-Linux/m-p/1961355#M10928</link>
      <description>&lt;P&gt;Hello, &lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/234952"&gt;@ashwini2024&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for your post.&lt;/P&gt;
&lt;P&gt;From BSP UM, for supporting ROS, the &lt;SPAN class="fontstyle0"&gt;fsl-image-ubuntu-ros is supported, ros-image-core is not mentioned from BSP's perspective.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class="fontstyle0"&gt;Then I suggest trying the fsl-image-ubuntu-ros for a test.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class="fontstyle0"&gt;BR&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class="fontstyle0"&gt;Chenyin&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 25 Sep 2024 05:47:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/Secure-boot-enabling-on-A-core-Linux/m-p/1961355#M10928</guid>
      <dc:creator>chenyin_h</dc:creator>
      <dc:date>2024-09-25T05:47:50Z</dc:date>
    </item>
  </channel>
</rss>

