<?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>Other NXP ProductsのトピックMsc8156 ethernet boot</title>
    <link>https://community.nxp.com/t5/Other-NXP-Products/Msc8156-ethernet-boot/m-p/184604#M1435</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have generate a srec file using the ELF2xx and SREC2xx utility.&lt;/P&gt;&lt;P&gt;AndI have configurate my pc ipadress (10.0.0.1), the dhcp server and the tftpserver using the Ethernet Boot Test pdf.&lt;/P&gt;&lt;P&gt;But when try the boot the board, everything is ok until the first data block is sending by the tftp server, that produced a checksum error (code : 003FEFFD).&lt;/P&gt;&lt;P&gt;I think it's because the tftp server cut a reccord in two parts.&lt;/P&gt;&lt;P&gt;I am using Codewarrior 10.1.8, DHCPTurbo (dhcp server), TFTPTurbo (tftp server) and Ethereal (ethernet sniffer).&lt;/P&gt;&lt;P&gt;Do someone know a solution to avoid this ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 19 Feb 2011 00:20:18 GMT</pubDate>
    <dc:creator>Jim95</dc:creator>
    <dc:date>2011-02-19T00:20:18Z</dc:date>
    <item>
      <title>Msc8156 ethernet boot</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/Msc8156-ethernet-boot/m-p/184604#M1435</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have generate a srec file using the ELF2xx and SREC2xx utility.&lt;/P&gt;&lt;P&gt;AndI have configurate my pc ipadress (10.0.0.1), the dhcp server and the tftpserver using the Ethernet Boot Test pdf.&lt;/P&gt;&lt;P&gt;But when try the boot the board, everything is ok until the first data block is sending by the tftp server, that produced a checksum error (code : 003FEFFD).&lt;/P&gt;&lt;P&gt;I think it's because the tftp server cut a reccord in two parts.&lt;/P&gt;&lt;P&gt;I am using Codewarrior 10.1.8, DHCPTurbo (dhcp server), TFTPTurbo (tftp server) and Ethereal (ethernet sniffer).&lt;/P&gt;&lt;P&gt;Do someone know a solution to avoid this ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 19 Feb 2011 00:20:18 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/Msc8156-ethernet-boot/m-p/184604#M1435</guid>
      <dc:creator>Jim95</dc:creator>
      <dc:date>2011-02-19T00:20:18Z</dc:date>
    </item>
    <item>
      <title>Re: Msc8156 ethernet boot</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/Msc8156-ethernet-boot/m-p/184605#M1436</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Jim95,&lt;/P&gt;&lt;P&gt;Have you ensured that your srec file is only on 1 file?&lt;/P&gt;&lt;P&gt;It is perfectly fine and normal to send an SREC over multiple packets, the big issue is that you must remove all carriage returns from the file.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Otherwise, from the pcap capture, it appears that things are running fine up to that point, so the boot process was correctly initiated.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;-Andrew&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 19 Feb 2011 02:12:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/Msc8156-ethernet-boot/m-p/184605#M1436</guid>
      <dc:creator>AndrewinApps</dc:creator>
      <dc:date>2011-02-19T02:12:39Z</dc:date>
    </item>
    <item>
      <title>Re: Msc8156 ethernet boot</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/Msc8156-ethernet-boot/m-p/184606#M1437</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Andrew,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for your response.&lt;/P&gt;&lt;P&gt;I removed the carriage returns, it&amp;nbsp;&amp;nbsp;works well when&amp;nbsp;I only use sc100-elf2xx.&lt;/P&gt;&lt;P&gt;But when&amp;nbsp;I use sc100-elf2xx and sc100-srec2xx&amp;nbsp;some reccords need to be written in the DDR1, that is not initialized, and the boot-loader stop.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Jimmy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Feb 2011 17:35:58 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/Msc8156-ethernet-boot/m-p/184606#M1437</guid>
      <dc:creator>Jim95</dc:creator>
      <dc:date>2011-02-21T17:35:58Z</dc:date>
    </item>
    <item>
      <title>Re: Msc8156 ethernet boot</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/Msc8156-ethernet-boot/m-p/184607#M1438</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Jimmy,&lt;/P&gt;&lt;P&gt;Using DDR requires running a boot patch. If you need this, please create an SR via the Freescale support page.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Regards,&lt;/P&gt;&lt;P&gt;-Andrew&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Feb 2011 05:27:48 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/Msc8156-ethernet-boot/m-p/184607#M1438</guid>
      <dc:creator>AndrewinApps</dc:creator>
      <dc:date>2011-02-22T05:27:48Z</dc:date>
    </item>
    <item>
      <title>Re: Msc8156 ethernet boot</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/Msc8156-ethernet-boot/m-p/184608#M1439</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is a two-stage process like this possible?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1) Simple Ethernet Boot loads a small stub of DDR initialization code&lt;/P&gt;&lt;P&gt;2) stub initializes DDR and re-enters the boot ROM&lt;/P&gt;&lt;P&gt;3) boot ROM resumes Simple Ethernet Boot and loads main image into DDR&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In theory this is simple but hinges on the re-entrancy of the boot ROM in Simple Ethernet Boot mode. If this isn't possible, what prevents it?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Mar 2011 18:09:14 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/Msc8156-ethernet-boot/m-p/184608#M1439</guid>
      <dc:creator>ldg</dc:creator>
      <dc:date>2011-03-22T18:09:14Z</dc:date>
    </item>
    <item>
      <title>Re: Msc8156 ethernet boot</title>
      <link>https://community.nxp.com/t5/Other-NXP-Products/Msc8156-ethernet-boot/m-p/184609#M1440</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This would require doing a DDR initialization boot patch running out of EEPROM.&lt;/P&gt;&lt;P&gt;Simple ethernet boot jumping back into the BootROM is not something we support.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Mar 2011 01:30:37 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Other-NXP-Products/Msc8156-ethernet-boot/m-p/184609#M1440</guid>
      <dc:creator>AndrewinApps</dc:creator>
      <dc:date>2011-03-25T01:30:37Z</dc:date>
    </item>
  </channel>
</rss>

