[U-Boot-Users] MBX with no NVRAM

[Ruurd Jan <ruurdjan@xs4all.nl>]

Hello,

I've got U-boot 0.2.0 up-and-running on my MBX860 board (a entry-level
50MHz version).
This board, hoever, does not have NVRAM (there is no battery).
Will this be a problem, even if I hard-code all variables I need into
U-boot?
I'm trying to boot a linux kernel, but after the kernel uncompresses,
the board reboots:
	=> tftpboot 200000 uImage
	ARP broadcast 1
	TFTP from server 10.0.0.150; our IP address is 10.0.0.200
Filename 'uImage'. Load address: 0x200000
	Loading:
#################################################################
	         ##################
	done
	Bytes transferred = 420568 (66ad8 hex)
	=> bootm
	## Booting image at 00200000 ...
	   Image Name:   Linux Kernel Image
	   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
	   Data Size:    420504 Bytes = 410.6 kB
	   Load Address: 00000000
	   Entry Point:  00000000
	   Verifying Checksum ... OK
	   Uncompressing Kernel Image ... OK


	U-Boot 0.2.0 (Feb 27 2003 - 21:10:18)

	CPU:   XPC860xxZPnnC1 at 50 MHz: 4 kB I-Cache 4 kB D-Cache
	Board: MBX860EN(01-W3425F01A)
	         *** Warning: Low Battery Status - On-Board Battery ***
	DRAM:  68 MB
	FLASH: 512 kB
	In:    serial
	Out:   serial
	Err:   serial
	Net:   SCC ETHERNET
	PCMCIA: 3.3V card found: SunDisk SDP 5/3 0.6
	            Fixed Disk Card
	            IDE interface
	            [silicon] [unique] [single] [sleep] [standby] [idle]
[low power] Bus 0: OK
	  Device 0: Model: SanDisk SDP3B-256 Firm: vdd 1.00. Ser#:
213008Q0410
	            Type: Removable Hard Disk
	            Capacity: 245.0 MB = 0.2 GB (501760 x 512)
	=>

Here's the environment I hard-coded into u-boot:
	bootcmd=bootm 20000
	baudrate=9600
	loads_echo=1
	bootargs=root=/dev/hda2 console=/dev/ttyS0,9600
	serverip=10.0.0.150
	ipaddr=10.0.0.200
	ethaddr=08:00:3e:2f:99:7e
	stdin=serial
	stdout=serial
	stderr=serial

I'm using a unmodified version of the MBX configs for the kernel, the
from the Denx site
(ftp://ftp.denx.de/pub/LinuxPPC/usr/src/linux-2.4.4-2002-10-06.tar.bz2)
with no patches.
If the NVRAM is not the issue, does anyone have a suggestion? I haven't
the time to build me a debugger :-((

thanks,

RJ