[U-Boot] [HELP]PCIX problem on MPC8547 in uboot

I have a self-designed board which is based on MPC8548PC demo board, but CPU is MPC8547E. I configured PCI to PCI-X 64bits asynchrous mode, 100MHz, and there were two SATA controllers connected directly to BUS #0. U-boot version is 1.1.4 which is previouly for MPC8548PC demo board, I have modified

[U-Boot] [HELP]uboot 1.3.4 can't work on my MPC8548 board

Hi: I downloaded uboot 1.3.4 and build it successfully, but it can't work on my MPC8548 board. There is no output message after power on. I use USB TAB to trace where the problem is and find that cpu died during relocation of CCSRBAR in cpu_init_early_f function. Is there anyone who also finds this

[U-Boot] Two confusing questions about relocation of code on MPC8548CDS board

After code is relocated, cpu jumped from flash to RAM, I have two questions I can't understand. Any help will be appreciated greatly. 1. Because TEXT_BASE=0xfff8 which points to flash space, after code is copied from flash to RAM and start to run from RAM, how can u-boot make sure code is plac

Re: [U-Boot] how compilor know where .text section starts from?

2008/12/3 Wolfgang Denk <[EMAIL PROTECTED]>: > Dear hank.peng <[EMAIL PROTECTED]>, > > repl: bad addresses: >hank.peng <[EMAIL PROTECTED]> -- no at-sign after local-part (<) > > Please fix the mail address you provide in your headers as return > address. Either get rid of the dot, or add qu

[U-Boot] how compilor know where .text section starts from?

Hi, everybody: I am new to uboot and reading source code, I have a question: how does compilor know where .text section starts from? For example, I am using MPC8548CDS, document says .text section begins from 0xfff8000, but I haven't find this value in u-boot.lds? So it must be specified in some ot