I'm porting u-boot 1.1.4 to my custom MPC8541 board, The resource on my board is like this: LCS0 Boot flash 0xFFF8_0000-0xFFFF_FFFF 512KB CCSR Default Value 0xFF70_0000-0xFF7F_FFFF 1MB LCS1 NvRAM 0xFF6E_0000-0xFF6F_FFFF 128KB CPLD 0xFF60_0000-0xFF67_FFFF 512KB LCS2 Image Flash1 0xF400_0000-0xF5FF_FFFF 32MB LCS3 Image Flash2 0xF600_0000-0xF7FF_FFFF 32MB CS1 discret DDR Bank1 0x0000_0000-0x07FF_FFFF 128MB CS0 discret DDR Bank0 0x0800_0000-0x0FFF_FFFF 128MB PCI memory space 0x8000_0000-0x9000_0000 512MB Because my board have no SPD_EEPROM for DDR config,so I choose MPC8560ads board as template. First I change the init.S file,rearrange the TLB entry according to my board, then I change include/configs/mpc8560ads.h according to my board, then compile and burn the u-boot.bin into boot flash. After power on,there have nothing dump from console. I have freescale codewarrior and USBTAP by my hand,so I debug the u-boot with CodeWarrior and I found that the program fly away from start.S->inflash:->bl cpu_init_f. Anybody who can help me to resolve this problem? And any suggestion should be appreciated. By the way,is there any other method to debug u-boot before console dump on mpc85xx,such as light led on GPIO pin? I think CodeWarrior is hard to use,could anybody use it successfully can share me some useful experience. I'm not familar with PPC assemble language,anyone can tell me what's the meaning ".long" in this sentence? .long TLB1_MAS0(0, 0, 0) Thanks.

dune

--------------------------------- All-new Yahoo! Mail - Fire up a more powerful email and get things done faster.