cfg_lock

cfg_lock

[Eric Heim]

[-- Attachment #1: Type: text/plain, Size: 955 bytes --]

Anybody know how the cfg_lock bit is manipulated on the MPC8349EMDS board?  I know the bit is in the internal configuration registers but how is this bit flipped on boot?  We are trying to boot the board as an agent in a PC.  We can only do this using the hard coded option.  We would like to boot the board with the reset config word in the I2C but we can't boot the board with the 'core disabled' as we would like(it only works if the core enable bit is set, otherwise the PC hangs and won't boot).  We are hoping to use a pre-load command in the boot sequencer,  but there is little information on how this can be done or if it can be done.  We can flip the bit from u-boot or using our driver when the PC has booted up but we need some way to flip the bit during boot to allow our PC to get its proper configuration cycles.  Any ideas?

		
---------------------------------
How low will we go? Check out Yahoo! Messenger’s low  PC-to-Phone call rates.

[-- Attachment #2: Type: text/html, Size: 1094 bytes --]

Re: cfg_lock

[Kumar Gala]

On May 2, 2006, at 5:02 PM, Eric Heim wrote:

> Anybody know how the cfg_lock bit is manipulated on the MPC8349EMDS  
> board?  I know the bit is in the internal configuration registers  
> but how is this bit flipped on boot?  We are trying to boot the  
> board as an agent in a PC.  We can only do this using the hard  
> coded option.  We would like to boot the board with the reset  
> config word in the I2C but we can't boot the board with the 'core  
> disabled' as we would like(it only works if the core enable bit is  
> set, otherwise the PC hangs and won't boot).  We are hoping to use  
> a pre-load command in the boot sequencer,  but there is little  
> information on how this can be done or if it can be done.  We can  
> flip the bit from u-boot or using our driver when the PC has booted  
> up but we need some way to flip the bit during boot to allow our PC  
> to get its proper configuration cycles.  Any ideas?

You have the right idea about using the I2C to handle various  
register and config writes.  However, the UM details how to setup  
your EEPROM so that I2C boot sequencer can process it.

See section 4.4.3 in the UM.

- k