Micro2440 won't when used out of the SDK board

Hi all,

 I have a micro2440 stamp module loaded with u-boot, a linux kernel and a
yaffs2 flash filesystem. When the stamp module is on the SDK board,
everything works fine, but when I try to boot it up connecting just power
and TX and RX for the console it hangs just before printing the "Hit any
key to stop autoboot" line. If i put the module back into the SDK board, it
boots fine again. 

¿Can anyone point me to what am I missing here? Thank you very much.

This is what u-boot prints just before hanging:

U-Boot 1.3.2-mini2440 (Feb 24 2010 - 13:04:49)
I2C:   ready
DRAM:  64 MB
Flash:  2 MB

NAND:  Bad block table not found for chip 0
Bad block table not found for chip 0

256 MiB

Found Environment offset in OOB..

USB:   S3C2410 USB Deviced

In:    serial

Out:   serial

Err:   serial

MAC: 08:08:11:18:12:27

Hi Issac.

On the Micro you will see two pins for a jumper. This replaces the NAND/NOR
switch on the SDK. If there is a jumper, remove it. If not, put one on.

-- Charlie

Hi Charlie, 

I'm afraid that the jumper is not the problem, as I'm booting from NAND
both when the board is in the SDK and when it's not (I have the jumper on
in both configurations).

I'm starting to think that it's either some kind of bug with u-boot, or
that I'm missing something at the hardware level.

Does anybody know which are the absolute minimum connections needed to boot
up a micro2440 module?

I'm applying 5VDC and ground on one of the connectors and I'm connecting
TXD0 and RXD0 to an 3V3 Serial to USB cable to read the console, but may be
I need to do something with RTS0 or CTS0...

Is there any other pin that must be connected somewhere to allow this
module to boot?

Thank you and best regards,
    Isaac

Well... I finally sorted this one out. 

It was so obvious that it's embarrasing :-)

U-boot was hanging just after printing the MAC address line because it was
trying to initialize the ethernet card to that MAC. As there is no ethernet
on the micro2440 module, u-boot just hanged for ever.

The solution was to just clear the ethraddr enviroment variable with

MINI2440# setenv ethaddr
MINI2440# saveenv

And now it boots each and every time.

I hope that this may help someone out there.

Best regards,
       Isaac