Hello Yuli and thank you for your response,

I should have included the bdinfo in my original post - my apologies.

Environment size: 311/262140 bytes => bdi memstart = 0x00000000 memsize = 0x01000000 flashstart = 0xFF800000 flashsize = 0x00800000 flashoffset = 0x00000000 sramstart = 0x00000000 sramsize = 0x00000000 immr_base = 0xF0000000 bootflags = 0x00000001 vco = 266.666 MHz sccfreq = 66.666 MHz brgfreq = 66.666 MHz intfreq = 199.999 MHz cpmfreq = 133.333 MHz busfreq = 66.666 MHz ethaddr = 4A:DC:16:9D:37:D8 IP addr = 47.129.82.129 baudrate = 57600 bps

=> flinfo

Bank # 1: Sharp 28F016SC (16 Mbit, 32 x 64K) Size: 8 MB in 32 Sectors Sector Start Addresses: FF800000 FF840000 FF880000 FF8C0000 FF900000 FF940000 FF980000 FF9C0000 FFA00000 FFA40000 FFA80000 FFAC0000 FFB00000 FFB40000 FFB80000 FFBC0000 FFC00000 FFC40000 FFC80000 FFCC0000 FFD00000 FFD40000 FFD80000 FFDC0000 FFE00000 FFE40000 FFE80000 FFEC0000 FFF00000 (RO) FFF40000 (RO) FFF80000 FFFC0000 => memcinfo BR0 = ff801801 OR0 = ff800836 BR1 = 04501801 OR1 = ffff8010 BR2 = 00000041 OR2 = ff000ca0 BR3 = 00000000 OR3 = fcffffff BR4 = 00000000 OR4 = edffffff BR5 = 00000000 OR5 = ffff7aff BR6 = 00000000 OR6 = bffbeffd BR7 = 00000000 OR7 = fdfff7ff BR8 = 00000000 OR8 = eeffffff BR9 = 00000000 OR9 = 7fffffff BR10 = 00000000 OR10 = ffffefff BR11 = 00000000 OR11 = f7ffffff MAR = ffb7ffff MAMR = 00000000 MBMR = 00000000 MCMR = 00000000 MPTPR = 1900 MDR = fe77aefe PSDMR = 416eb493 LSDMR = 00000000 PURT = ff PSRT = 10 LURT = df LSRT = ff IMMR = f0000062 => imi 100000

## Checking Image at 00100000 ... Image Name: Linux 2.4.21 - MPC8266ads Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size: 575596 Bytes = 562.1 kB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK

I am quite new to embedded systems, so please forgive me if I seem to miss the obvious. The reason that I went for the penguinppc kernel is that they had already done a lot of work towards supporting the MPC8266 board, including the PCI support, and as I don't really have the background to write my own drivers (someday, maybe ) I thought that this would be my best option - so far this hasn't been the case, unfortunately. I had suspected that I didn't need `clocks_in_mhz' as the kernel version that penguinppc provides is very new ( 2.4.21 ). The relationship of some of the addresses escapes me, I must admit - I thought that the load address and entry point of the kernel would be mapped to the loading point specified in u-boot by default ( 0x100000 ).

Any input that you have would be most welcome, and in the interim I will try configuring a kernel directly from kernel.org rather than rely on the penguinppc one. That seems to be my most immediate problem, judging from the successes that others have enjoyed using u-boot.

Thanks, Currie

ORIGINAL MESSAGE -

Hi,

I use Linux on older MPC8260ADS and the newest PQ2FADS (which is next generation of MPC8266ADS). I use modified Debian with home-made drivers and not penguinppc kernel. It looks like in you kernel there is either serial console (SCC) initialisation problem or memory mapping problem. These things are board specific and you don't write what your configuration is. `bdinfo' output and your memory mappings would be helpful (for example, check that internal RAM is mapped correctly, penguinppc startup code uses hard-coded address 0xF0000000 instead of checking bdinfo.) In new kernels you usually don't need to set `clocks_in_mhz', but again it depends on your time handling functions.