[U-Boot-Users] cpu_init.c: qe_config_ioports not being called?

[U-Boot-Users] cpu_init.c: qe_config_ioports not being called?

[Russell McGuire]

Anyone,

 

I was wondering if somebody could help me out to understand something.

 

Using the MPC8360E, I have configured up a custom header board and have used
the appropriate 

#define CONFIG_QE. However when I boot the board up the
'config_qe_ioports()' doesn't seem to get called.

Consequently the Ethernet doesn't work after U-boot completes.

 

I placed some printf()'s in the function to see if it was getting called,
and no printouts.

 

So my question is, why isn't the 'config_qe_ioports()' getting called inside
the mpc83xx/cpu_init_f.

Is perhaps cpu_init_f() not getting called? Stumped here. 

 

U-boot seems to work fine otherwise, it boots completely into RAM and
relocates, etc. I can use the md command and query the ioports and see the
settings are not taking effect.

 

 

-Russ

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20070110/952b310d/attachment.htm 

[U-Boot-Users] cpu_init.c: qe_config_ioports not being called?

[Timur Tabi]

Russell McGuire wrote:

> I placed some printf()?s in the function to see if it was getting 
> called, and no printouts.

That's because cpu_init_f() is called before the serial port is enabled.

> So my question is, why isn?t the ?config_qe_ioports()? getting called 
> inside the mpc83xx/cpu_init_f.
> 
> Is perhaps cpu_init_f() not getting called? Stumped here?

Just FYI, here's a trick to make sure the compiler is thinking the same thing 
you are:

Modify cpu_init_f() like this:

#ifdef CONFIG_QE
asdlfhasdfkjlhgasdfiuge
	/* Config QE ioports */
	config_qe_ioports();
#endif

The compiler will generate a syntax error on the garbage characters you insert, 
if it compiles that code.  If U-Boot builds fine, then you know that CONFIG_QE 
is not defined at that point in the code, or cpu_init.c is not being compiled at 
all.

> U-boot seems to work fine otherwise, it boots completely into RAM and 
> relocates, etc? I can use the md command and query the ioports and see 
> the settings are not taking effect.

cpu_init_r() has further QE initialization, and printfs work in that function. 
Check to see if it is being called.


-- 
Timur Tabi
Linux Kernel Developer @ Freescale