<br><font size=2 face="sans-serif">Hello,</font>
<br>
<br><font size=2 face="sans-serif">The board is not exactly MPC8260ADS.
It is similar to this and the RAM version of the u-Boot tree is abailable.
Does this mean that we need to burn the flash with the image (u-boot.bin
OR u-boot.srec ?) we obtained by the compiling the RAM version of the u-Boot
source tree? </font>
<br>
<br><font size=2 face="sans-serif">The flash attached to our board is mapped
from 0x0 address. The u-boot document says that the SDRAM should be mapped
to 0x0 to make it work. So, in my case as the flash is mapped to 0x0, then
how shall I proceed? Does the memory mapping is determined by the
h/w design of the board? </font>
<br>
<br><font size=2 face="sans-serif">As I know that HRCW of our board is
stored from adress 0x0 to address 0xFF. Does this mean we need to burn
the image (u-boot.bin OR u-boot.srec ?) from the adress 0x100?</font>
<br>
<br><font size=2 face="sans-serif">Thanks,</font>
<br><font size=2 face="sans-serif"><br>
Batsayan Das<br>
Tata Consultancy Services Limited<br>
Mailto: batsayan.das@tcs.com<br>
Website: http://www.tcs.com</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Wolfgang Denk <wd@denx.de></b>
</font>
<br><font size=1 face="sans-serif">Sent by: u-boot-users-admin@lists.sourceforge.net</font>
<p><font size=1 face="sans-serif">10/26/2005 03:29 PM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">To</font></div>
<td><font size=1 face="sans-serif">batsayan.das@tcs.com</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif">u-boot-users@lists.sourceforge.net</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">Subject</font></div>
<td><font size=1 face="sans-serif">Re: [U-Boot-Users] Help on mpc8260ads
flash u-boot</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><font size=2><tt>In message <OF277F660B.19F369DD-ON652570A6.0020CA43-652570A6.0024E9CA@tcs.com>
you wrote:<br>
> <br>
> We have a working RAM version of U-Boot for MPC8260ADS type customs
board. <br>
<br>
What a waste of effort. The MPC8260ADS board is
supposed to be<br>
working out of the box. Why are you
wasting your time on some<br>
unsupported mode of operation? You *did* read the FAQ, didn't you?<br>
http://www.denx.de/wiki/view/DULG/CanUBootBeConfiguredSuchThatItCanBeStartedInRAM<br>
<br>
> What the places we need to look into to convert this RAM version of
U-Boot <br>
> to ROM/Flash version of U-boot. The objective is when power on the
u-boot <br>
<br>
Nothing needs to be changed. This is the standard mode of operation<br>
which works with the original U-Boot source tree.<br>
<br>
> binary, so some part of the RAM version u-boot need to be modified
to do <br>
> this. Is there any specific place in the u-boot tree where we need
to make <br>
<br>
Just dump your RAM version. You just wasted your time on it.<br>
<br>
Best regards,<br>
<br>
Wolfgang Denk<br>
<br>
-- <br>
Software Engineering: Embedded and Realtime Systems, Embedded
Linux<br>
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de<br>
At the source of every error which is blamed on the computer you will<br>
find at least two human errors, including the error of blaming it on<br>
the computer.<br>
<br>
<br>
-------------------------------------------------------<br>
This SF.Net email is sponsored by the JBoss Inc.<br>
Get Certified Today * Register for a JBoss Training Course<br>
Free Certification Exam for All Training Attendees Through End of 2005<br>
Visit http://www.jboss.com/services/certification for more information<br>
_______________________________________________<br>
U-Boot-Users mailing list<br>
U-Boot-Users@lists.sourceforge.net<br>
https://lists.sourceforge.net/lists/listinfo/u-boot-users<br>
</tt></font>
<br><font size=1 color=white face="sans-serif">ForwardSourceID:NT00006476
</font>
<br>
<table><tr><td bgcolor=#ffffff><font color=#000000>Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you<br>
</font></td></tr></table>