2.6.18 on mpc859t stuck in __delay

2.6.18 on mpc859t stuck in __delay

[Robin Gilks]

I'm sure this is a common one but I'm a bit stuck (like the target is 
really!!)

I'm real confused about what options to enable for a generic 866 series 
target - I'm got CONFIG_MPC86xADS and CONFIG_FADS enabled in the 
platform section but I'm not clear as to whether that will cause the 
startup code to look for an ADS EPROM chip or look for a bd_t struct of 
data from the bootloader.

I've checked the bdinfo at __res and it looks OK (booting from u-boot) 
with valid CPU, bus and console speeds but I get the impression that the 
decrementer isn't being started.

-- 
Robin Gilks
Senior Design Engineer          Phone: (+64)(3) 357 1569
Tait Electronics                Fax  :  (+64)(3) 359 4632
PO Box 1645 Christchurch        Email : robin.gilks@tait.co.nz
New Zealand

=======================================================================
This email, including any attachments, is only for the intended
addressee.  It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
 altered or corrupted during transmission.
=======================================================================

Re: 2.6.18 on mpc859t stuck in __delay

[Kalle Pokki]

On 11/2/06, Robin Gilks <robin.gilks@tait.co.nz> wrote:
> I'm sure this is a common one but I'm a bit stuck (like the target is
> really!!)
>
> I'm real confused about what options to enable for a generic 866 series
> target - I'm got CONFIG_MPC86xADS and CONFIG_FADS enabled in the
> platform section but I'm not clear as to whether that will cause the
> startup code to look for an ADS EPROM chip or look for a bd_t struct of
> data from the bootloader.

You should probably have just have CONFIG_8xx and
CONFIG_YOUR_OWN_BOARD defined. Don't enable these other boards, since
that just makes the code to access some board specific control
registers you don't have. This surely leads to machine check
exceptions or other erratic behavior. However, it may be useful to
grep all the CONFIG_MPC86xADS and CONFIG_FADS code sections, and check
if you should implement something similar to these code blocks that
applies to your own board.