<?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 Re: Kernel 5.4, imx.6q : sdma firmware not ready!, SPI transfer failed: -22 in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Kernel-5-4-imx-6q-sdma-firmware-not-ready-SPI-transfer-failed-22/m-p/1234304#M169812</link>
    <description>&lt;P&gt;Hi Christian,&lt;/P&gt;&lt;P&gt;Yes, I did study your previous advice, and tried it. But when I try to build the imx-sdma module as loadable, it is build but not installed in the rootfs image. How do I get it to be installed?&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Lars&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 22 Feb 2021 10:46:40 GMT</pubDate>
    <dc:creator>lmhdoms</dc:creator>
    <dc:date>2021-02-22T10:46:40Z</dc:date>
    <item>
      <title>Kernel 5.4, imx.6q : sdma firmware not ready!, SPI transfer failed: -22</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Kernel-5-4-imx-6q-sdma-firmware-not-ready-SPI-transfer-failed-22/m-p/1233650#M169744</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Porting our yocto based kernel from 4.9.67 to 5.4.81 (linux-fslc-imx), I face issues when accessing the spi flash device.&lt;/P&gt;&lt;P&gt;The kernel is configured with:&lt;/P&gt;&lt;P&gt;CONFIG_IMX_SDMA=y&lt;/P&gt;&lt;P&gt;CONFIG_DMA_VIRTUAL_CHANNELS=y&lt;/P&gt;&lt;P&gt;I have added the sdma firmware like this:&lt;/P&gt;&lt;P&gt;IMAGE_INSTALL_append = " linux-firmware-imx-sdma-imx6q"&lt;/P&gt;&lt;P&gt;And it gets installed here:&lt;/P&gt;&lt;P&gt;root@cpb539:~# ls -al /lib/firmware/imx/sdma/&lt;BR /&gt;-rw-r--r-- 1 root root 2746 Mar 9 2018 sdma-imx6q.bin&lt;/P&gt;&lt;P&gt;The DTS looks like:&lt;/P&gt;&lt;P&gt;sdma: sdma@20ec000 {&lt;BR /&gt;compatible = "fsl,imx6q-sdma", "fsl,imx35-sdma";&lt;BR /&gt;reg = &amp;lt;0x020ec000 0x4000&amp;gt;;&lt;BR /&gt;interrupts = &amp;lt;0 2 4&amp;gt;;&lt;BR /&gt;clocks = &amp;lt;&amp;amp;clks 62&amp;gt;,&lt;BR /&gt;&amp;lt;&amp;amp;clks 155&amp;gt;;&lt;BR /&gt;clock-names = "ipg", "ahb";&lt;BR /&gt;#dma-cells = &amp;lt;3&amp;gt;;&lt;BR /&gt;fsl,sdma-ram-script-name = "imx/sdma/sdma-imx6q.bin";&lt;BR /&gt;};&lt;BR /&gt;};&lt;/P&gt;&lt;P&gt;During boot, the fw was not installed, but using ROM.. should be ok at this point?&lt;/P&gt;&lt;P&gt;[ 0.140059] imx-sdma 20ec000.sdma: Direct firmware load for imx/sdma/sdma-imx6q.bin failed with error -2&lt;BR /&gt;[ 0.140136] imx-sdma 20ec000.sdma: Direct firmware load for imx/sdma/sdma-imx6q.bin failed with error -2&lt;BR /&gt;[ 0.140152] imx-sdma 20ec000.sdma: external firmware not found, using ROM firmware&lt;/P&gt;&lt;P&gt;The SPI flash devices gets probed ok:&lt;/P&gt;&lt;P&gt;[ 1.031793] spi-nor spi0.0: m25p32 (4096 Kbytes)&lt;BR /&gt;[ 1.036466] 5 cmdlinepart partitions found on MTD device spi0.0&lt;BR /&gt;[ 1.042391] Creating 5 MTD partitions on "spi0.0":&lt;BR /&gt;[ 1.047218] 0x0000003f0000-0x000000400000 : "boardid"&lt;BR /&gt;[ 1.055693] 0x0000003e0000-0x0000003f0000 : "u-boot-env"&lt;BR /&gt;[ 1.062571] 0x0000003c0000-0x0000003e0000 : "uploadlog"&lt;BR /&gt;[ 1.075590] 0x0000003b0000-0x0000003c0000 : "u-boot-env2"&lt;BR /&gt;[ 1.085624] 0x000000000400-0x000000060400 : "u-boot"&lt;BR /&gt;[ 1.095754] spi_imx 2008000.spi: probed&lt;BR /&gt;[ 1.100815] spi-nor spi2.0: found m25p16, expected s25fl216k&lt;BR /&gt;[ 1.106523] spi-nor spi2.0: m25p16 (2048 Kbytes)&lt;BR /&gt;[ 1.115946] spi_imx 2010000.spi: probed&lt;BR /&gt;[ 1.120662] spi_imx 2018000.spi: probed&lt;/P&gt;&lt;P&gt;Now reading from the spi flash fails:&lt;/P&gt;&lt;P&gt;root@cpb539:~# dd if=/dev/mtd1 of=/tmp/env.bin bs=65535 count=1&lt;BR /&gt;[ 802.819901] imx-sdma 20ec000.sdma: sdma firmware not ready!&lt;BR /&gt;[ 802.825563] spi-nor spi0.0: SPI transfer failed: -22&lt;BR /&gt;[ 802.830673] spi_master spi0: failed to transfer one message from queue&lt;BR /&gt;dd: /dev/mtd1: Invalid argument&lt;/P&gt;&lt;P&gt;What am I missing in getting SPI access to work? how do I make the sdma firmware ready?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Lars&lt;/P&gt;</description>
      <pubDate>Fri, 19 Feb 2021 13:16:44 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Kernel-5-4-imx-6q-sdma-firmware-not-ready-SPI-transfer-failed-22/m-p/1233650#M169744</guid>
      <dc:creator>lmhdoms</dc:creator>
      <dc:date>2021-02-19T13:16:44Z</dc:date>
    </item>
    <item>
      <title>Re: Kernel 5.4, imx.6q : sdma firmware not ready!, SPI transfer failed: -22</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Kernel-5-4-imx-6q-sdma-firmware-not-ready-SPI-transfer-failed-22/m-p/1233717#M169749</link>
      <description>&lt;P&gt;Hi Lars,&lt;/P&gt;&lt;P&gt;I already answered this question several times in this forum. See here.&lt;BR /&gt;&lt;A href="https://community.nxp.com/t5/i-MX-Processors/imx6-linux-imx-sdma-firmware-load-failed-error/m-p/1193695#M165982" target="_blank"&gt;https://community.nxp.com/t5/i-MX-Processors/imx6-linux-imx-sdma-firmware-load-failed-error/m-p/1193695#M165982&lt;/A&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;BR /&gt;Christian&lt;/P&gt;</description>
      <pubDate>Fri, 19 Feb 2021 15:17:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Kernel-5-4-imx-6q-sdma-firmware-not-ready-SPI-transfer-failed-22/m-p/1233717#M169749</guid>
      <dc:creator>ceggers1</dc:creator>
      <dc:date>2021-02-19T15:17:49Z</dc:date>
    </item>
    <item>
      <title>Re: Kernel 5.4, imx.6q : sdma firmware not ready!, SPI transfer failed: -22</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Kernel-5-4-imx-6q-sdma-firmware-not-ready-SPI-transfer-failed-22/m-p/1234304#M169812</link>
      <description>&lt;P&gt;Hi Christian,&lt;/P&gt;&lt;P&gt;Yes, I did study your previous advice, and tried it. But when I try to build the imx-sdma module as loadable, it is build but not installed in the rootfs image. How do I get it to be installed?&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Lars&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Feb 2021 10:46:40 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Kernel-5-4-imx-6q-sdma-firmware-not-ready-SPI-transfer-failed-22/m-p/1234304#M169812</guid>
      <dc:creator>lmhdoms</dc:creator>
      <dc:date>2021-02-22T10:46:40Z</dc:date>
    </item>
    <item>
      <title>Re: Kernel 5.4, imx.6q : sdma firmware not ready!, SPI transfer failed: -22</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Kernel-5-4-imx-6q-sdma-firmware-not-ready-SPI-transfer-failed-22/m-p/1234346#M169817</link>
      <description>&lt;P&gt;With this added to local.conf, I get the loadable modules installed.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;CORE_IMAGE_EXTRA_INSTALL += " kernel-modules"&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Now on to the tests.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Feb 2021 12:03:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Kernel-5-4-imx-6q-sdma-firmware-not-ready-SPI-transfer-failed-22/m-p/1234346#M169817</guid>
      <dc:creator>lmhdoms</dc:creator>
      <dc:date>2021-02-22T12:03:37Z</dc:date>
    </item>
    <item>
      <title>Re: Kernel 5.4, imx.6q : sdma firmware not ready!, SPI transfer failed: -22</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Kernel-5-4-imx-6q-sdma-firmware-not-ready-SPI-transfer-failed-22/m-p/1234397#M169821</link>
      <description>&lt;P&gt;Success: adding the kernel-modules gets the imx-sdma.ko installed. Also the sdma fw 3.5 gets loaded successfully.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Lars&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 22 Feb 2021 14:10:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Kernel-5-4-imx-6q-sdma-firmware-not-ready-SPI-transfer-failed-22/m-p/1234397#M169821</guid>
      <dc:creator>lmhdoms</dc:creator>
      <dc:date>2021-02-22T14:10:38Z</dc:date>
    </item>
  </channel>
</rss>

