Its defined differently on these boards (and all our future board
ports) since after relocation and such we have the FLASH @
0xe800_. And thus the u-boot image is at @ 0xeff8_.
- k
On Aug 23, 2009, at 4:44 AM, Felix Radensky wrote:
Hi, Kumar
I don't see any immediate problem
Hi, Kumar
Kumar Gala wrote:
Its defined differently on these boards (and all our future board
ports) since after relocation and such we have the FLASH @
0xe800_. And thus the u-boot image is at @ 0xeff8_.
Thanks for the explanation. Out of curiosity, I've tried to set FLASH
On Aug 24, 2009, at 10:10 AM, Felix Radensky wrote:
Thanks for the explanation. Out of curiosity, I've tried to set
FLASH physical address on MPC8536DS
to 0xf800_ and modify TEXT_BASE to 0xfff8_. But that
resulted in non-bootable system
(no u-boot messages at all).
What did I
Kumar Gala wrote:
On Aug 24, 2009, at 10:10 AM, Felix Radensky wrote:
Thanks for the explanation. Out of curiosity, I've tried to set FLASH
physical address on MPC8536DS
to 0xf800_ and modify TEXT_BASE to 0xfff8_. But that resulted
in non-bootable system
(no u-boot messages at
Hi, Kumar
I don't see any immediate problem with current FSL definitions
except they are confusing.
I think my proposal will not work on platforms like MPC8572,
MPC8536, and P2020DS where TEXT_BASE is defined as
0xeff8 instead of 0xfff8. Can you please explain the
reason why TEXT_BASE
Hi,
All FSL MPC85xx boards define CONFIG_SYS_MONITOR_LEN as 256K
although actual size of u-boot binary is 512K. XES Xpedite boards seem to do
the right thing.
I was wandering whether CONFIG_SYS_MONITOR_LEN for 85xx boards
can be defined in terms of CONFIG_SYS_MONITOR_BASE, similar to AMCC
boards
6 matches
Mail list logo
