<?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: tftpboot ${loadaddr} uImage problem</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/tftpboot-loadaddr-uImage-problem/m-p/383441#M55452</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;what's your boot command? You can refer to below command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; U-Boot &amp;gt; setenv loadaddr 0x10800000&lt;BR /&gt;&amp;nbsp; U-Boot &amp;gt; setenv bootdelay 3&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; U-Boot &amp;gt; setenv serverip 10.192.241.222&lt;BR /&gt;&amp;nbsp; U-Boot &amp;gt; setenv tftpaddr 10.192.241.222&lt;BR /&gt;&amp;nbsp; U-Boot &amp;gt; setenv kernel uImage&lt;/P&gt;&lt;P&gt;&amp;nbsp; U-Boot &amp;gt; setenv bootcmd_net 'run bootargs_base bootargs_nfs;bootp ${loadaddr} ${tftpaddr}:${kernel};bootm'&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 11 Oct 2014 05:28:47 GMT</pubDate>
    <dc:creator>justin_jiang</dc:creator>
    <dc:date>2014-10-11T05:28:47Z</dc:date>
    <item>
      <title>tftpboot ${loadaddr} uImage problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/tftpboot-loadaddr-uImage-problem/m-p/383440#M55451</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;now i want to boot from SPI3:0,and i modify the code like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;void spi_io_init(struct imx_spi_dev_t *dev)&lt;BR /&gt;{&lt;BR /&gt; u32 reg;&lt;/P&gt;&lt;P&gt; switch (dev-&amp;gt;base) {&lt;BR /&gt; case ECSPI1_BASE_ADDR:&lt;BR /&gt;&amp;nbsp; /* Enable clock */&lt;BR /&gt;&amp;nbsp; reg = readl(CCM_BASE_ADDR + CLKCTL_CCGR1);&lt;BR /&gt;&amp;nbsp; reg |= 0x3;&lt;BR /&gt;&amp;nbsp; writel(reg, CCM_BASE_ADDR + CLKCTL_CCGR1);&lt;/P&gt;&lt;P&gt;#if defined CONFIG_MX6Q&lt;BR /&gt;&amp;nbsp; /* SCLK */&lt;BR /&gt;&amp;nbsp; mxc_iomux_v3_setup_pad(MX6Q_PAD_KEY_COL0__ECSPI1_SCLK);&lt;/P&gt;&lt;P&gt;&amp;nbsp; /* MISO */&lt;BR /&gt;&amp;nbsp; mxc_iomux_v3_setup_pad(MX6Q_PAD_KEY_COL1__ECSPI1_MISO);&lt;/P&gt;&lt;P&gt;&amp;nbsp; /* MOSI */&lt;BR /&gt;&amp;nbsp; mxc_iomux_v3_setup_pad(MX6Q_PAD_KEY_ROW0__ECSPI1_MOSI);&lt;/P&gt;&lt;P&gt;&amp;nbsp; mxc_iomux_v3_setup_pad(MX6Q_PAD_KEY_ROW1__ECSPI1_SS0);&lt;BR /&gt;#elif defined CONFIG_MX6DL&lt;BR /&gt;&amp;nbsp; /* SCLK */&lt;BR /&gt;&amp;nbsp; mxc_iomux_v3_setup_pad(MX6DL_PAD_KEY_COL0__ECSPI1_SCLK);&lt;/P&gt;&lt;P&gt;&amp;nbsp; /* MISO */&lt;BR /&gt;&amp;nbsp; mxc_iomux_v3_setup_pad(MX6DL_PAD_KEY_COL1__ECSPI1_MISO);&lt;/P&gt;&lt;P&gt;&amp;nbsp; /* MOSI */&lt;BR /&gt;&amp;nbsp; mxc_iomux_v3_setup_pad(MX6DL_PAD_KEY_ROW0__ECSPI1_MOSI);&lt;/P&gt;&lt;P&gt;&amp;nbsp; mxc_iomux_v3_setup_pad(MX6DL_PAD_KEY_ROW1__ECSPI1_SS0);&lt;BR /&gt;#endif&lt;BR /&gt;&amp;nbsp; break;&lt;BR /&gt; case ECSPI2_BASE_ADDR:&lt;BR /&gt; case ECSPI3_BASE_ADDR:&lt;BR /&gt;&amp;nbsp; /* ecspi2-3 fall through */&lt;BR /&gt;&amp;nbsp; break;&lt;BR /&gt; default:&lt;BR /&gt;&amp;nbsp; break;&lt;BR /&gt; }&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;s32 spi_get_cfg(struct imx_spi_dev_t *dev)&lt;BR /&gt;{&lt;BR /&gt; switch (dev-&amp;gt;slave.cs) {&lt;BR /&gt; case 0:&lt;BR /&gt;&amp;nbsp; /* SPI-NOR */&lt;BR /&gt;&amp;nbsp; dev-&amp;gt;base = ECSPI1_BASE_ADDR;&lt;BR /&gt;&amp;nbsp; dev-&amp;gt;freq = 25000000;&lt;BR /&gt;&amp;nbsp; dev-&amp;gt;ss_pol = IMX_SPI_ACTIVE_LOW;&lt;BR /&gt;&amp;nbsp; dev-&amp;gt;ss = 0;&lt;BR /&gt;&amp;nbsp; dev-&amp;gt;fifo_sz = 64 * 4;&lt;BR /&gt;&amp;nbsp; dev-&amp;gt;us_delay = 0;&lt;BR /&gt;&amp;nbsp; break;&lt;BR /&gt; case 1:&lt;BR /&gt;&amp;nbsp; /* SPI-NOR */&lt;BR /&gt;&amp;nbsp; dev-&amp;gt;base = ECSPI1_BASE_ADDR;&lt;BR /&gt;&amp;nbsp; dev-&amp;gt;freq = 25000000;&lt;BR /&gt;&amp;nbsp; dev-&amp;gt;ss_pol = IMX_SPI_ACTIVE_LOW;&lt;BR /&gt;&amp;nbsp; dev-&amp;gt;ss = 1;&lt;BR /&gt;&amp;nbsp; dev-&amp;gt;fifo_sz = 64 * 4;&lt;BR /&gt;&amp;nbsp; dev-&amp;gt;us_delay = 0;&lt;BR /&gt;&amp;nbsp; break;&lt;BR /&gt; default:&lt;BR /&gt;&amp;nbsp; printf("Invalid Bus ID!\n");&lt;BR /&gt; }&lt;/P&gt;&lt;P&gt; return 0;&lt;/P&gt;&lt;P&gt;}&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and under uboot, when i input:&lt;/P&gt;&lt;P&gt;MX6Q&amp;nbsp; U-Boot &amp;gt; sf probe 2:0&lt;/P&gt;&lt;P&gt;it display like this:&lt;/P&gt;&lt;P&gt;JEDEC ID: 0x20:0x20:0x16&lt;/P&gt;&lt;P&gt;4096 KiB M25P32 - 4MB at 2:0 is now current device&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;but when i use tftpboot cmd,errors occur:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MX6Q&amp;nbsp; U-Boot &amp;gt; tftpboot ${loadaddr} uImage&lt;/P&gt;&lt;P&gt;PHY indentify @ 0x0 = 0x0007c0f1&lt;/P&gt;&lt;P&gt;FEC: Link is Up 782d&lt;/P&gt;&lt;P&gt;Using FEC0 device&lt;/P&gt;&lt;P&gt;TFTP from server 192.168.3.153; our IP address is 192.168.3.221&lt;/P&gt;&lt;P&gt;Filename 'uImage'.&lt;/P&gt;&lt;P&gt;Load address: 0x10800000&lt;/P&gt;&lt;P&gt;Loading: TX timeout packet at 2786e2c0&lt;/P&gt;&lt;P&gt;TX timeout packet at 2786e2c0&lt;/P&gt;&lt;P&gt;TX not ready&lt;/P&gt;&lt;P&gt;TX timeout packet at 2786e2c0&lt;/P&gt;&lt;P&gt;T TX not ready&lt;/P&gt;&lt;P&gt;TX timeout packet at 2786e2c0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and when the image starts in linux,it can exchange data with my computer by net,so i don't why it can not transfer data with tftp?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 10 Oct 2014 09:57:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/tftpboot-loadaddr-uImage-problem/m-p/383440#M55451</guid>
      <dc:creator>caoping</dc:creator>
      <dc:date>2014-10-10T09:57:22Z</dc:date>
    </item>
    <item>
      <title>Re: tftpboot ${loadaddr} uImage problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/tftpboot-loadaddr-uImage-problem/m-p/383441#M55452</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;what's your boot command? You can refer to below command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; U-Boot &amp;gt; setenv loadaddr 0x10800000&lt;BR /&gt;&amp;nbsp; U-Boot &amp;gt; setenv bootdelay 3&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; U-Boot &amp;gt; setenv serverip 10.192.241.222&lt;BR /&gt;&amp;nbsp; U-Boot &amp;gt; setenv tftpaddr 10.192.241.222&lt;BR /&gt;&amp;nbsp; U-Boot &amp;gt; setenv kernel uImage&lt;/P&gt;&lt;P&gt;&amp;nbsp; U-Boot &amp;gt; setenv bootcmd_net 'run bootargs_base bootargs_nfs;bootp ${loadaddr} ${tftpaddr}:${kernel};bootm'&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 11 Oct 2014 05:28:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/tftpboot-loadaddr-uImage-problem/m-p/383441#M55452</guid>
      <dc:creator>justin_jiang</dc:creator>
      <dc:date>2014-10-11T05:28:47Z</dc:date>
    </item>
    <item>
      <title>Re: tftpboot ${loadaddr} uImage problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/tftpboot-loadaddr-uImage-problem/m-p/383442#M55453</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Have you tried to reproduce the problem in one of our boards?&lt;/P&gt;&lt;P&gt;Is it a custom hardware? If you use other SPI module you have the same error?&lt;/P&gt;&lt;P&gt;When you say you want to boot from SPI, do you mean fetching the rootfs or kernel from serial flash? or get U-boot Image from serial flash?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best Regards,&lt;/P&gt;&lt;P&gt;Alejandro&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Oct 2014 17:51:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/tftpboot-loadaddr-uImage-problem/m-p/383442#M55453</guid>
      <dc:creator>alejandrolozan1</dc:creator>
      <dc:date>2014-10-14T17:51:47Z</dc:date>
    </item>
    <item>
      <title>Re: tftpboot ${loadaddr} uImage problem</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/tftpboot-loadaddr-uImage-problem/m-p/383443#M55454</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;may be the ethernet communication problem,i use lan8720,&lt;/P&gt;&lt;P&gt;now i' ve coped uImage from mmc to spi, and i'm finding ways to use MFG tool to burn SPI3:0,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Oct 2014 06:05:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/tftpboot-loadaddr-uImage-problem/m-p/383443#M55454</guid>
      <dc:creator>caoping</dc:creator>
      <dc:date>2014-10-15T06:05:09Z</dc:date>
    </item>
  </channel>
</rss>

