<?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: SWupdate procedure for imx8mp</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/SWupdate-procedure-for-imx8mp/m-p/1897252#M225720</link>
    <description>&lt;P&gt;The compiler (doing a bitbake -v core-image-base), would complain about u-boot-imx; seems that I should use the board configuration, for example in my case u-boot-congatec-sx8p&lt;/P&gt;</description>
    <pubDate>Tue, 02 Jul 2024 12:02:14 GMT</pubDate>
    <dc:creator>Marco_Savo</dc:creator>
    <dc:date>2024-07-02T12:02:14Z</dc:date>
    <item>
      <title>SWupdate procedure for imx8mp</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SWupdate-procedure-for-imx8mp/m-p/1895928#M225622</link>
      <description>&lt;P&gt;I am looking into a simple update solution for our custom OS for a custom board using a SMARC module based on imx8mp processor (SECO, congatec). I am already aware of AN13872 document, that is quite exaustive, but there is no mention of imx8mp, and seems overly complicated. I want to do a single image update procedure from an USB stick. Where can I find an exhaustive tutorial for that. I found many options and I could only break out the build in the process.&lt;/P&gt;&lt;P&gt;What I've done successfully, so far:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="python"&gt;repo init -u &amp;lt;...&amp;gt;
repo sync
cd sources/
git clone https://github.com/sbabic/meta-swupdate.git -b kirkstone
git clone https://github.com/nxp-imx-support/meta-swupdate-imx.git -b kirkstone_5.15.32_2.0.0
cd ../build_dir
echo "BBLAYERS += \"\${BSPDIR}/sources/meta-swupdate\"" &amp;gt;&amp;gt; conf/bblayers.conf
echo "BBLAYERS += \"\${BSPDIR}/sources/meta-swupdate-imx\"" &amp;gt;&amp;gt; conf/bblayers.conf

echo "IMAGE_INSTALL:append = \" lua swupdate swupdate-www swupdate-progress swupdate-client swupdate-tools-ipc u-boot-imx u-boot-fw-utils systemd-swusys json-c\"" &amp;gt;&amp;gt; conf/local.conf
echo "IMAGE_FSTYPES = \" ext4 ext4.gz wic.bmap wic.gz\"" &amp;gt;&amp;gt; conf/local.conf&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;At this point, the documentation is not clear.&lt;/P&gt;&lt;P&gt;&lt;EM&gt;bitbake swupdate-image, &lt;/EM&gt;what's for, exactly?&lt;/P&gt;&lt;P&gt;What's the next step? I see in the tutorial the use of swu_update_image_build.sh, but I could not find it in the repository&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 01 Jul 2024 13:40:41 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SWupdate-procedure-for-imx8mp/m-p/1895928#M225622</guid>
      <dc:creator>Marco_Savo</dc:creator>
      <dc:date>2024-07-01T13:40:41Z</dc:date>
    </item>
    <item>
      <title>Re: SWupdate procedure for imx8mp</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SWupdate-procedure-for-imx8mp/m-p/1897252#M225720</link>
      <description>&lt;P&gt;The compiler (doing a bitbake -v core-image-base), would complain about u-boot-imx; seems that I should use the board configuration, for example in my case u-boot-congatec-sx8p&lt;/P&gt;</description>
      <pubDate>Tue, 02 Jul 2024 12:02:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SWupdate-procedure-for-imx8mp/m-p/1897252#M225720</guid>
      <dc:creator>Marco_Savo</dc:creator>
      <dc:date>2024-07-02T12:02:14Z</dc:date>
    </item>
    <item>
      <title>Re: SWupdate procedure for imx8mp</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SWupdate-procedure-for-imx8mp/m-p/1897428#M225740</link>
      <description>&lt;P&gt;So I was able tu run:&lt;/P&gt;&lt;PRE&gt;bitbake swupdate&lt;/PRE&gt;&lt;P&gt;And:&lt;/P&gt;&lt;PRE&gt;bitbake swupdate-image&lt;/PRE&gt;&lt;P&gt;For this to run I had to comment:&lt;/P&gt;&lt;PRE&gt;#EXTRA_IMAGE_FEATURES += "tools-debug tools-profile tools-testapps ssh-server-openssh"&lt;/PRE&gt;&lt;P&gt;In local.conf&lt;/P&gt;&lt;P&gt;I can successfully configure swupdate in yocto with:&lt;/P&gt;&lt;PRE&gt;bitbake -c menuconfig swupdate&lt;/PRE&gt;&lt;P&gt;Now I have built:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;DIV&gt;swupdate-image-imx8mp-cgtsx8p.ext4.gz.u-boot&lt;/DIV&gt;&lt;DIV&gt;swupdate-image-imx8mp-cgtsx8p.ext4&lt;/DIV&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;But shouldn't I have a .swu file in order to use swupdate?&lt;/P&gt;</description>
      <pubDate>Tue, 02 Jul 2024 12:01:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SWupdate-procedure-for-imx8mp/m-p/1897428#M225740</guid>
      <dc:creator>Marco_Savo</dc:creator>
      <dc:date>2024-07-02T12:01:28Z</dc:date>
    </item>
    <item>
      <title>Re: SWupdate procedure for imx8mp</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SWupdate-procedure-for-imx8mp/m-p/1897608#M225758</link>
      <description>&lt;P&gt;So, now I have, built:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;DIV&gt;swupdate-image-imx8mp-cgtsx8p.ext4.gz.u-boot&lt;/DIV&gt;&lt;DIV&gt;swupdate-image-imx8mp-cgtsx8p.ext4&lt;/DIV&gt;&lt;DIV&gt;core-image-base-imx8mp-cgtsx8p.ext4.gz&lt;/DIV&gt;&lt;DIV&gt;bootcontainer__imx8mp-cgtsx8p__sd.bin&lt;/DIV&gt;&lt;DIV&gt;core-image-base-imx8mp-cgtsx8p.wic.bz2&lt;/DIV&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;So, I understand that I can use to create the .swu file:&lt;/P&gt;&lt;P&gt;pip install swugenerator&lt;/P&gt;&lt;P&gt;Can I use this as sw-description?&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;software =
{
	version = "0.1.0";

	imx8mp-dart = {
		hardware-compatibility: [ "1.0" ];

		files: (
			{
				filename = "core-image-base-imx8mp-cgtsx8p.ext4.gz";
				type = "archive";
				compressed = true;
				device = "/dev/update";
				filesystem = "ext4";
				path = "/";
			}
		);

		scripts: (
			{
				filename = "update.sh";
				type = "shellscript";
			}
		);
	};
}&lt;/LI-CODE&gt;&lt;P&gt;Is this correct?&lt;/P&gt;</description>
      <pubDate>Tue, 02 Jul 2024 15:22:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SWupdate-procedure-for-imx8mp/m-p/1897608#M225758</guid>
      <dc:creator>Marco_Savo</dc:creator>
      <dc:date>2024-07-02T15:22:58Z</dc:date>
    </item>
    <item>
      <title>Re: SWupdate procedure for imx8mp</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SWupdate-procedure-for-imx8mp/m-p/1898728#M225841</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/225253"&gt;@Marco_Savo&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;One can try to refer to chapter 6 in AN13872 (Creating a base image and an update image) and 6.1 (swupdate-script repository).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also it is useful to check the &lt;A href="https://sbabic.github.io/swupdate/sw-description.html" target="_self"&gt;SWUpdate syntax examples&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;--... ...--&lt;/P&gt;
&lt;P&gt;Salas.&lt;/P&gt;</description>
      <pubDate>Wed, 03 Jul 2024 19:41:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SWupdate-procedure-for-imx8mp/m-p/1898728#M225841</guid>
      <dc:creator>Manuel_Salas</dc:creator>
      <dc:date>2024-07-03T19:41:35Z</dc:date>
    </item>
    <item>
      <title>Re: SWupdate procedure for imx8mp</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SWupdate-procedure-for-imx8mp/m-p/1908460#M226161</link>
      <description>&lt;P&gt;OK, I am then able to create this .sdcard file that I can flash into the board with the uuu tool. For that, I had to modify the boards in the script repository, but also the swupdate-imx repository, to include imx8mp.&lt;/P&gt;&lt;P&gt;still, the result is:&lt;/P&gt;&lt;P&gt;Disk /dev/mmcblk2: 14.6 GiB, 15678308352 bytes, 30621696 sectors&lt;BR /&gt;Units: sectors of 1 * 512 = 512 bytes&lt;BR /&gt;Sector size (logical/physical): 512 bytes / 512 bytes&lt;BR /&gt;I/O size (minimum/optimal): 512 bytes / 512 bytes&lt;BR /&gt;Disklabel type: dos&lt;BR /&gt;Disk identifier: 0x2b59b9ca&lt;/P&gt;&lt;P&gt;Device Boot Start End Sectors Size Id Type&lt;BR /&gt;/dev/mmcblk2p1 204800 450559 245760 120M c W95 FAT32 (LBA)&lt;BR /&gt;/dev/mmcblk2p2 450560 6594559 6144000 2.9G 83 Linux&lt;BR /&gt;/dev/mmcblk2p3 6594560 6840319 245760 120M c W95 FAT32 (LBA)&lt;BR /&gt;/dev/mmcblk2p4 6840320 12984319 6144000 2.9G 83 Linux&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I want to do a singlecopy image with rescue image; the document explains it, but there is no script for doing it.&lt;/P&gt;&lt;P&gt;Plus, this is crating a filesystem with 4 partitions that uses 7.5 GB. So, why? what's going on with the additional 7.5 Gb not used?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 15 Jul 2024 07:47:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SWupdate-procedure-for-imx8mp/m-p/1908460#M226161</guid>
      <dc:creator>Marco_Savo</dc:creator>
      <dc:date>2024-07-15T07:47:35Z</dc:date>
    </item>
    <item>
      <title>Re: SWupdate procedure for imx8mp</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/SWupdate-procedure-for-imx8mp/m-p/1963482#M229010</link>
      <description>&lt;P&gt;Hi Marco,&lt;/P&gt;&lt;P&gt;I’m trying to implement the same SWUpdate feature on the i.MX8MPlus by referring to the AN13872 document. However, I’m encountering continuous errors while running the SW script to generate the swImage. I already added imx8mp configs files taking reference from imx8mm that it support by default .Could you share the patch you applied for the i.MX8MPlus target?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have attached the error logs below.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 27 Sep 2024 10:14:20 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/SWupdate-procedure-for-imx8mp/m-p/1963482#M229010</guid>
      <dc:creator>sanum19</dc:creator>
      <dc:date>2024-09-27T10:14:20Z</dc:date>
    </item>
  </channel>
</rss>

