https://becomwiki.live.md-websolutions.com/index.php?action=history&feed=atom&title=U-Boot_%28i.MX31%29 2026-05-13T14:12:41Z Versionsgeschichte dieser Seite in BECOM Systems Support MediaWiki 1.43.5 https://becomwiki.live.md-websolutions.com/index.php?title=U-Boot_(i.MX31)&diff=576&oldid=prev 2023-10-31T08:03:12Z

<p>1 Version importiert</p> <table style="background-color: #fff; color: #202122;" data-mw="interface"> <tr class="diff-title" lang="de-AT"> <td colspan="1" style="background-color: #fff; color: #202122; text-align: center;">← Nächstältere Version</td> <td colspan="1" style="background-color: #fff; color: #202122; text-align: center;">Version vom 31. Oktober 2023, 10:03 Uhr</td> </tr><tr><td colspan="2" class="diff-notice" lang="de-AT"><div class="mw-diff-empty">(kein Unterschied)</div> </td></tr></table>

Peter https://becomwiki.live.md-websolutions.com/index.php?title=U-Boot_(i.MX31)&diff=575&oldid=prev 2023-08-22T19:35:55Z

<p>1 Version importiert</p> <p><b>Neue Seite</b></p><div>=== Prerequisites ===<br /> You will need at least the following to successfully build and deploy a new bootloader:<br /> * A working ltib installation<br /> * A JTAG Programmer, such as PEEDI<br /> * A core module on the DevBoard<br /> <br /> You will need to take a note of the ethernet address which is shown just after the boot process has started.<br /> <br /> === Creating a new u-boot.bin ===<br /> Change to the directory where your ltib installation is. Then run the following command:<br /> &lt;pre&gt;<br /> ./ltib -m prep -p u-boot<br /> &lt;/pre&gt;<br /> This will unpack the u-boot files to ./rpm/BUILD/u-boot-$version$. You can now edit these files as desired.<br /> <br /> To finally create the bootloader image, run the following command:<br /> &lt;pre&gt;<br /> ./ltib -m scbuild -p u-boot<br /> &lt;/pre&gt;<br /> This will create the file u-boot.bin. You will need to copy it to an location, which is accessible via TFTP. In our example we shared the directory ltib5/rootfs/boot. To perform the copying, run the following command<br /> &lt;pre&gt;<br /> sudo cp ./rpm/BUILD/u-boot-1.2.0/u-boot.bin ./rootfs/boot/<br /> or<br /> ./ltib -m scdeploy -p u-boot<br /> &lt;/pre&gt;<br /> Using ls, make sure that the copy process finished successfully and that the filetime of the new image is the current time.<br /> <br /> === Flashing the bootloader image ===<br /> Now connect the JTAG to the devboard. Start the JTAG programmer. If you are using PEEDI, use the following commands flash the bootloader image.<br /> &lt;pre&gt;<br /> flash erase 0xa0000000 0x100000<br /> flash program tftp://192.168.0.75/u-boot.bin bin 0xa0000000<br /> &lt;/pre&gt;<br /> If the flashing does not succeed, you might want to check the FAQs section.<br /> <br /> === Changing the environment settings ===<br /> After flashing, all your environment settings will be gone and you will have to renew them. To do this, enter the bootloader prompt by pressing a key when asked to and perform the following commands. Keep in mind that the settings shown are only example settings and do not represent your setup.<br /> &lt;pre&gt;<br /> BTi.MX31$ setenv ethaddr 00:00:e2:a2:66:12<br /> BTi.MX31$ setenv ipaddr 192.168.0.51<br /> BTi.MX31$ setenv serverip 192.168.0.75<br /> BTi.MX31$ setenv bootfile uImage<br /> BTi.MX31$ run setup_bootargs_net<br /> BTi.MX31$ saveenv<br /> Saving Environment to Flash...<br /> Un-Protected 1 sectors<br /> Erasing Flash...<br /> . done<br /> Erased 1 sectors<br /> Writing to Flash... done<br /> Protected 1 sectors<br /> &lt;/pre&gt;<br /> <br /> [[Category:i.MX31]]</div>

en>Peter