This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

updated U-Boot for DM365 (evm or otherwise) -- what am I missing?

I have a custom board based on the UDWORKS hardware and the DM365 EVK, and I'm trying to update u-boot on it.  Using the source from TI, a modified version 1.3.4 of U-Boot and Constantine's SD card flashing utility, I can get a serial console on my board.  I hope that this shows that there are no hardware problems in getting this far.

However, attempting to use the u-boot from the 4.02 DVSDK does not work.  I noticed that the maximum U-Boot image size there was 160K and that my u-boot image was larger, so I modified the sd card flash utility to permit larger u-boot images, and tested this with the 1.3.4 image to make sure that it still worked.

When trying to use my image (built for davinci_dm365_evm U-Boot target), I see the following: 

DM36x initialization passed!
TI UBL Version: 1.50
Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000019.
DONE
Jumping to entry point at 0x81080000.

I've tried official u-boot sources, the arago u-boot-davinci tree, and the DVSDK 4.02 sources.  None of them appear to work and I'm unsure how to even begin debugging without jtag.

This is the boot log from the 1.3.4 image I built: 

DM36x initialization passed!
TI UBL Version: 1.50
Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000019.
DONE
Jumping to entry point at 0x81080000.


U-Boot 2009.03-dirty (Nov 13 2012 - 14:16:34)

I2C: ready
DRAM: 128 MB
NAND: NAND device: Manufacturer ID: 0x2c, Chip ID: 0xf1 (Micron NAND 128MiB 3,3V 8-bit)
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xf1 (Micron NAND 128MiB 3,3V 8-bit)
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
256 MiB
*** Warning - bad CRC or NAND, using default environment

In: serial
Out: serial
Err: serial

EEPROM @ 0x50 read FAILED!!!
Ethernet PHY: GENERIC @ 0x00
Hit any key to stop autoboot: 0
DM365 EVM >

Any thoughts on what I need to do to get this working?  Surely it must be something simple, but I've gone through the u-boot config many times and nothing looks incorrect to me.