<?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>LayerscapeのトピックRe: LX2160 yocto implement problem?</title>
    <link>https://community.nxp.com/t5/Layerscape/LX2160-yocto-implement-problem/m-p/1367279#M9264</link>
    <description>&lt;P&gt;HI&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/52411"&gt;@yipingwang&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It seems Yocto image can be build by LSDK and Yocto release SDK,&lt;/P&gt;&lt;P&gt;In LSDK I saw a command as below can build yocto as below:&lt;/P&gt;&lt;P&gt;flex-builder -i mkrfs -r yocto:tiny&lt;/P&gt;&lt;P&gt;I am just confused about this, what is the different for Yocto build between LSDK and Yocto release SDK?&lt;/P&gt;&lt;P&gt;I know Yocto official build is using bitbike, how about LSDK with yocto build, is that just build a yocto rootfs?&lt;/P&gt;&lt;P&gt;This is because our product's emmc storage is not large, we need smaller size image and rootfs, now we use LSDK with ubuntu mate and customize rootfs size, but it still too large,&amp;nbsp;so we think yocto build maybe has chance to do that, &amp;nbsp;could you give us some advice, which one is suitable for our request? LSDK with yocto tiny build or Yocto SDK?&lt;/P&gt;&lt;P&gt;BR,&lt;/P&gt;&lt;P&gt;Jack&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 05 Nov 2021 09:53:03 GMT</pubDate>
    <dc:creator>jackho</dc:creator>
    <dc:date>2021-11-05T09:53:03Z</dc:date>
    <item>
      <title>LX2160 yocto implement problem?</title>
      <link>https://community.nxp.com/t5/Layerscape/LX2160-yocto-implement-problem/m-p/1364960#M9231</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I follow&amp;nbsp;&lt;SPAN&gt;Layerscape Software Development Kit User Guide for Yocto document&amp;nbsp;&lt;/SPAN&gt;implement sdk, after I generate image successfully, next I would like to burn image(bootloader, kernel and filesystem) into emmc, it seems not mentions in this document, is it can flash by flex-installer? any SOP we can follow?&lt;/P&gt;&lt;P&gt;I read&amp;nbsp;&lt;SPAN&gt;LSDK 20.04 user manual, it&amp;nbsp;&lt;/SPAN&gt;mentions can use flex-builder to build yocto, not using bitbike, it makes me a little confused, which way is correct method we can follow?&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;Jack&lt;/P&gt;</description>
      <pubDate>Tue, 02 Nov 2021 08:39:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LX2160-yocto-implement-problem/m-p/1364960#M9231</guid>
      <dc:creator>jackho</dc:creator>
      <dc:date>2021-11-02T08:39:36Z</dc:date>
    </item>
    <item>
      <title>Re: LX2160 yocto implement problem?</title>
      <link>https://community.nxp.com/t5/Layerscape/LX2160-yocto-implement-problem/m-p/1365042#M9233</link>
      <description>&lt;P&gt;Please refer to the following procedure.&lt;/P&gt;
&lt;P&gt;Please connect SD card to your host PC&lt;/P&gt;
&lt;P&gt;1. Please create two partitions with Linux command "fdisk", one 1G FAT16 and 2G one ext2/ext3 or with remainder of the available disk size.&lt;BR /&gt;# mkfs.vfat /dev/sdb1&lt;BR /&gt;# mkfs.ext2 /dev/sdb2&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;2. Please deployed RCW + PBI + BL2(bl2_&amp;lt;boot_mode&amp;gt;.pbl)image to SD card as the following.&lt;BR /&gt;dd if=&lt;SPAN&gt;bl2_sd.pbl&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;of=/dev/sdb bs=512 seek=8&lt;/P&gt;
&lt;P&gt;note:/dev/sdb is SD device name.&lt;/P&gt;
&lt;P&gt;Please deploy&amp;nbsp;TF-A FIP image at 0x00800 in SD card.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;dd if=fip_uboot.bin of=/dev/sdb bs=512 seek=2048&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Please deploy DPAA2-MC at 0x05000 in SD card.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;dd if=&amp;lt;MC image&amp;gt; of=/dev/sdb bs=512 seek=20480&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Please deploy DPAA2 DPL at 0x06800 in SD card.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;dd if=&amp;lt;DPL image&amp;gt; of=/dev/sdb bs=512 seek=26624&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Please deploy DPAA2 DPC at 0x07000 in SD card.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;dd if=&amp;lt;DPC image&amp;gt; of=/dev/sdb bs=512 seek=28672&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;3. Please deploy rootfs filesystem to SD card in the host PC as the following.&lt;BR /&gt;# mkdir&amp;nbsp; /temp&lt;BR /&gt;# mount&amp;nbsp; /dev/sdb2&amp;nbsp; /temp&lt;BR /&gt;# cd /temp&lt;BR /&gt;# cp&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;fsl-image-networking-lx2160ardb.tar.gz&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;.&lt;BR /&gt;# tar -xzvf&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;fsl-image-networking-lx2160ardb.tar.gz&lt;/SPAN&gt;&lt;BR /&gt;# rm&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;fsl-image-networking-lx2160ardb.tar.gz&lt;/SPAN&gt;&lt;BR /&gt;Please deploy Kernel Image and the dtb to the /boot folder.&lt;BR /&gt;# cp&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;Image&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;boot&lt;BR /&gt;# cp&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;fsl-lx2160-rdb-sdk.dtb&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;boot&lt;BR /&gt;&lt;BR /&gt;Configure the switch setting boot from SD card&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Plug in the SD card to the target board and power on.&lt;BR /&gt;Set the environment in uboot for SD boot.&lt;/P&gt;
&lt;P&gt;=&amp;gt;&lt;BR /&gt;=&amp;gt; setenv bootcmd 'setenv bootargs root=/dev/mmcblk0p2 rw rootdelay=5 console=ttyAMA0,115200 earlycon=pl011,mmio32,0x21c0000;mmcinfo;mmc read 0x80d00000 0x6800 0x800;&amp;nbsp;fsl_mc lazyapply dpl 0x80d00000;ext2load mmc 0:2 0xa0000000 /boot/&lt;SPAN&gt;Image&lt;/SPAN&gt;;ext2load mmc 0:2 0xb0000000 /boot/&lt;SPAN&gt;fsl-lx2160a-rdb-sdk.dtb&lt;/SPAN&gt;;booti 0xa0000000 - 0xb0000000'&lt;BR /&gt;=&amp;gt; saveenv&lt;BR /&gt;&lt;BR /&gt;Boot up Linux&lt;BR /&gt;=&amp;gt; boot&lt;/P&gt;</description>
      <pubDate>Tue, 02 Nov 2021 09:54:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LX2160-yocto-implement-problem/m-p/1365042#M9233</guid>
      <dc:creator>yipingwang</dc:creator>
      <dc:date>2021-11-02T09:54:22Z</dc:date>
    </item>
    <item>
      <title>Re: LX2160 yocto implement problem?</title>
      <link>https://community.nxp.com/t5/Layerscape/LX2160-yocto-implement-problem/m-p/1365593#M9239</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/52411"&gt;@yipingwang&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your reply, it seems your reply is for SD card upgrade, I will try it.&lt;/P&gt;&lt;P&gt;How about yocto emmc upgrade procedure, normally in OTA upgrade, it will upgrade kernel and rootfs in running system, not in uboot commad line, can we use flex-installer do this?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Jack&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 03 Nov 2021 08:44:56 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LX2160-yocto-implement-problem/m-p/1365593#M9239</guid>
      <dc:creator>jackho</dc:creator>
      <dc:date>2021-11-03T08:44:56Z</dc:date>
    </item>
    <item>
      <title>Re: LX2160 yocto implement problem?</title>
      <link>https://community.nxp.com/t5/Layerscape/LX2160-yocto-implement-problem/m-p/1366383#M9252</link>
      <description>&lt;P&gt;&lt;SPAN&gt;flex-installer is only used in flex-builder released LSDK. For Yocto released SDK, please use the method which I provided previously.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 04 Nov 2021 05:33:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LX2160-yocto-implement-problem/m-p/1366383#M9252</guid>
      <dc:creator>yipingwang</dc:creator>
      <dc:date>2021-11-04T05:33:35Z</dc:date>
    </item>
    <item>
      <title>Re: LX2160 yocto implement problem?</title>
      <link>https://community.nxp.com/t5/Layerscape/LX2160-yocto-implement-problem/m-p/1366596#M9255</link>
      <description>&lt;P&gt;HI&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/52411"&gt;@yipingwang&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;below command need to confirm with you:&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;1.Please deploy DPAA2-MC at 0x05000 in SD card.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;sudo dd if=./mc_app/mc_10.20.4_lx2160a.itb of=/dev/sdc bs=512 seek=20480&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;2.Please deploy DPAA2 DPL at 0x06800 in SD card.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;=&amp;gt;It seems DPL image has 2 image:&amp;nbsp;dpl-2dpni.dtb and&amp;nbsp;dpl-eth.19.dtb, which one I should use to flash?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;sudo dd if=mc-utils/dpl-2dpni.dtb of=/dev/sdc bs=512 seek=26624&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;3.Please deploy DPAA2 DPC at 0x07000 in SD card.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;=&amp;gt;It seems DPC image has 2 image: dpc-usxgmii.dtb&amp;nbsp;and dpc-warn.dtb, which one I should use to flash?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;sudo dd if=./mc-utils/dpc-usxgmii.dtb of=/dev/sdc bs=512 seek=28672&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Jack&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 04 Nov 2021 09:44:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LX2160-yocto-implement-problem/m-p/1366596#M9255</guid>
      <dc:creator>jackho</dc:creator>
      <dc:date>2021-11-04T09:44:37Z</dc:date>
    </item>
    <item>
      <title>Re: LX2160 yocto implement problem?</title>
      <link>https://community.nxp.com/t5/Layerscape/LX2160-yocto-implement-problem/m-p/1367043#M9257</link>
      <description>&lt;P&gt;You could use DPC&amp;nbsp;dpc-usxgmii.dtb and DPL&amp;nbsp;dpl-eth.19.dtb.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Nov 2021 03:20:24 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LX2160-yocto-implement-problem/m-p/1367043#M9257</guid>
      <dc:creator>yipingwang</dc:creator>
      <dc:date>2021-11-05T03:20:24Z</dc:date>
    </item>
    <item>
      <title>Re: LX2160 yocto implement problem?</title>
      <link>https://community.nxp.com/t5/Layerscape/LX2160-yocto-implement-problem/m-p/1367177#M9261</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/52411"&gt;@yipingwang&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1. I follow your command to flash image to sd card, plug in sd card to EVB board, but cannot boot successful as below:&lt;/P&gt;&lt;P&gt;NOTICE:&amp;nbsp; BL2: v1.5(release):nsc1.1_nsa.004_2021071201_NSC-NSA-9-gaa4e338ee-dirty&lt;/P&gt;&lt;P&gt;NOTICE:&amp;nbsp; BL2: Built : 04:26:56, Sep&amp;nbsp; 8 2021&lt;/P&gt;&lt;P&gt;NOTICE:&amp;nbsp; INITIALIZING SEC&lt;/P&gt;&lt;P&gt;NOTICE:&amp;nbsp; UDIMM 18ADF2G72AZ-3G2E1&amp;nbsp;&lt;/P&gt;&lt;P&gt;NOTICE:&amp;nbsp; Verifying RSA&lt;/P&gt;&lt;P&gt;NOTICE:&amp;nbsp; Verifying hash&lt;/P&gt;&lt;P&gt;NOTICE:&amp;nbsp; Verifying RSA&lt;/P&gt;&lt;P&gt;NOTICE:&amp;nbsp; Verifying hash&lt;/P&gt;&lt;P&gt;NOTICE:&amp;nbsp; Verifying RSA&lt;/P&gt;&lt;P&gt;NOTICE:&amp;nbsp; Verifying hash&lt;/P&gt;&lt;P&gt;NOTICE:&amp;nbsp; Verifying RSA&lt;/P&gt;&lt;P&gt;NOTICE:&amp;nbsp; Verifying hash&lt;/P&gt;&lt;P&gt;NOTICE:&amp;nbsp; DDR4 UDIMM with 2-rank 64-bit bus (x8)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;NOTICE:&amp;nbsp; 32 GB DDR4, 64-bit, CL=22, ECC on, 256B, CS0+CS1&lt;/P&gt;&lt;P&gt;NOTICE:&amp;nbsp; Verifying RSA&lt;/P&gt;&lt;P&gt;NOTICE:&amp;nbsp; Verifying hash&lt;/P&gt;&lt;P&gt;NOTICE:&amp;nbsp; Verifying RSA&lt;/P&gt;&lt;P&gt;NOTICE:&amp;nbsp; Verifying hash&lt;/P&gt;&lt;P&gt;NOTICE:&amp;nbsp; Verifying RSA&lt;/P&gt;&lt;P&gt;NOTICE:&amp;nbsp; Verifying hash&lt;/P&gt;&lt;P&gt;ERROR: &amp;nbsp; BL2: Failed to load image (-80)&lt;/P&gt;&lt;P&gt;Authentication failure&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2. The SD card partition I use fdisk format as below:&lt;/P&gt;&lt;P&gt;Disk /dev/sdc: 29.1 GiB, 31293702144 bytes, 61120512 sectors&lt;/P&gt;&lt;P&gt;Units: sectors of 1 * 512 = 512 bytes&lt;/P&gt;&lt;P&gt;Sector size (logical/physical): 512 bytes / 512 bytes&lt;/P&gt;&lt;P&gt;I/O size (minimum/optimal): 512 bytes / 512 bytes&lt;/P&gt;&lt;P&gt;Disklabel type: dos&lt;/P&gt;&lt;P&gt;Disk identifier: 0xbf896a7d&lt;/P&gt;&lt;P&gt;Device &amp;nbsp; &amp;nbsp; Boot &amp;nbsp; Start &amp;nbsp; &amp;nbsp; End Sectors Size Id Type&lt;/P&gt;&lt;P&gt;/dev/sdc1&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; 2048 2099199 2097152 &amp;nbsp; 1G&amp;nbsp; 6 FAT16&lt;/P&gt;&lt;P&gt;/dev/sdc2 &amp;nbsp; &amp;nbsp; &amp;nbsp; 2099200 6293503 4194304 &amp;nbsp; 2G 83 Linux&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;3.And I run below command:&lt;/P&gt;&lt;P&gt;$ sudo mkfs.vfat /dev/sdc1&lt;/P&gt;&lt;P&gt;$ sudo mkfs.ext2 /dev/sdc2&lt;/P&gt;&lt;P&gt;$ sudo dd if=./atf/bl2_sd.pbl of=/dev/sdc bs=512 seek=8&lt;/P&gt;&lt;P&gt;209+1 records in&lt;/P&gt;&lt;P&gt;209+1 records out&lt;/P&gt;&lt;P&gt;107265 bytes (107 kB, 105 KiB) copied, 0.0712491 s, 1.5 MB/s&lt;/P&gt;&lt;P&gt;$ sudo dd if=./atf/fip_uboot.bin of=/dev/sdc bs=512 seek=2048&lt;/P&gt;&lt;P&gt;1598+1 records in&lt;/P&gt;&lt;P&gt;1598+1 records out&lt;/P&gt;&lt;P&gt;818391 bytes (818 kB, 799 KiB) copied, 0.19099 s, 4.3 MB/s&lt;/P&gt;&lt;P&gt;$ sudo dd if=./mc_app/mc_10.20.4_lx2160a.itb of=/dev/sdc bs=512 seek=20480&lt;/P&gt;&lt;P&gt;2133+1 records in&lt;/P&gt;&lt;P&gt;2133+1 records out&lt;/P&gt;&lt;P&gt;1092272 bytes (1.1 MB, 1.0 MiB) copied, 0.350616 s, 3.1 MB/s&lt;/P&gt;&lt;P&gt;$ sudo dd if=mc-utils/dpl-eth.19.dtb of=/dev/sdc bs=512 seek=26624&lt;/P&gt;&lt;P&gt;8+1 records in&lt;/P&gt;&lt;P&gt;8+1 records out&lt;/P&gt;&lt;P&gt;4583 bytes (4.6 kB, 4.5 KiB) copied, 0.00849373 s, 540 kB/s&lt;/P&gt;&lt;P&gt;$ sudo dd if=./mc-utils/dpc-usxgmii.dtb of=/dev/sdc bs=512 seek=28672&lt;/P&gt;&lt;P&gt;1+1 records in&lt;/P&gt;&lt;P&gt;1+1 records out&lt;/P&gt;&lt;P&gt;736 bytes copied, 0.00504512 s, 146 kB/s&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;# mkdir&amp;nbsp; /temp&lt;/P&gt;&lt;P&gt;# mount&amp;nbsp; /dev/sdc2&amp;nbsp; /temp&lt;/P&gt;&lt;P&gt;# cd /temp&lt;/P&gt;&lt;P&gt;# cp&amp;nbsp; fsl-image-networking-lx2160ardb.tar.gz .&lt;/P&gt;&lt;P&gt;# tar -xzvf&amp;nbsp; fsl-image-networking-lx2160ardb.tar.gz&lt;/P&gt;&lt;P&gt;# rm&amp;nbsp; fsl-image-networking-lx2160ardb.tar.gz&lt;/P&gt;&lt;P&gt;# cp Image boot&lt;/P&gt;&lt;P&gt;# cp fsl-lx2160a-rdb-lx2160ardb-rev2.dtb boot&lt;/P&gt;&lt;P&gt;Any step I miss to run?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;Jack&lt;/P&gt;</description>
      <pubDate>Fri, 05 Nov 2021 07:54:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LX2160-yocto-implement-problem/m-p/1367177#M9261</guid>
      <dc:creator>jackho</dc:creator>
      <dc:date>2021-11-05T07:54:59Z</dc:date>
    </item>
    <item>
      <title>Re: LX2160 yocto implement problem?</title>
      <link>https://community.nxp.com/t5/Layerscape/LX2160-yocto-implement-problem/m-p/1367186#M9262</link>
      <description>&lt;P&gt;Did you build secure boot images with Yocto?&lt;/P&gt;&lt;P&gt;Or did you blow ITS bit to enable secure boot on your target board?&lt;/P&gt;</description>
      <pubDate>Fri, 05 Nov 2021 08:03:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LX2160-yocto-implement-problem/m-p/1367186#M9262</guid>
      <dc:creator>yipingwang</dc:creator>
      <dc:date>2021-11-05T08:03:27Z</dc:date>
    </item>
    <item>
      <title>Re: LX2160 yocto implement problem?</title>
      <link>https://community.nxp.com/t5/Layerscape/LX2160-yocto-implement-problem/m-p/1367256#M9263</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/52411"&gt;@yipingwang&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for your reply,&lt;/P&gt;&lt;P&gt;Sorry, it seems EVB board jumper switch to emmc boot, I switch it to SD card, it can boot successful.&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;Jack&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Nov 2021 09:23:27 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LX2160-yocto-implement-problem/m-p/1367256#M9263</guid>
      <dc:creator>jackho</dc:creator>
      <dc:date>2021-11-05T09:23:27Z</dc:date>
    </item>
    <item>
      <title>Re: LX2160 yocto implement problem?</title>
      <link>https://community.nxp.com/t5/Layerscape/LX2160-yocto-implement-problem/m-p/1367279#M9264</link>
      <description>&lt;P&gt;HI&amp;nbsp;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/52411"&gt;@yipingwang&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It seems Yocto image can be build by LSDK and Yocto release SDK,&lt;/P&gt;&lt;P&gt;In LSDK I saw a command as below can build yocto as below:&lt;/P&gt;&lt;P&gt;flex-builder -i mkrfs -r yocto:tiny&lt;/P&gt;&lt;P&gt;I am just confused about this, what is the different for Yocto build between LSDK and Yocto release SDK?&lt;/P&gt;&lt;P&gt;I know Yocto official build is using bitbike, how about LSDK with yocto build, is that just build a yocto rootfs?&lt;/P&gt;&lt;P&gt;This is because our product's emmc storage is not large, we need smaller size image and rootfs, now we use LSDK with ubuntu mate and customize rootfs size, but it still too large,&amp;nbsp;so we think yocto build maybe has chance to do that, &amp;nbsp;could you give us some advice, which one is suitable for our request? LSDK with yocto tiny build or Yocto SDK?&lt;/P&gt;&lt;P&gt;BR,&lt;/P&gt;&lt;P&gt;Jack&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 05 Nov 2021 09:53:03 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LX2160-yocto-implement-problem/m-p/1367279#M9264</guid>
      <dc:creator>jackho</dc:creator>
      <dc:date>2021-11-05T09:53:03Z</dc:date>
    </item>
    <item>
      <title>Re: LX2160 yocto implement problem?</title>
      <link>https://community.nxp.com/t5/Layerscape/LX2160-yocto-implement-problem/m-p/1367714#M9279</link>
      <description>&lt;P&gt;LSDK only can be used to generate Yocto based rootfs filesystem, please refer to the following.&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="yipingwang_0-1636354324662.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/161484i886B20DE627BAA3E/image-size/medium?v=v2&amp;amp;px=400" role="button" title="yipingwang_0-1636354324662.png" alt="yipingwang_0-1636354324662.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;According to your requirement, probably Yocto released SDK is a good choice.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Nov 2021 07:05:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/LX2160-yocto-implement-problem/m-p/1367714#M9279</guid>
      <dc:creator>yipingwang</dc:creator>
      <dc:date>2021-11-08T07:05:15Z</dc:date>
    </item>
  </channel>
</rss>

