I have this eval board that I got used. It came with come linux preloaded on it that was booting from NAND.

Anyway, using sam-ba I erased nand, erased dataflash, loaded the stock at91bootstrap from at91.com and the stock u-boot(1.3.4) from at91.com.

The bootstrap starts up and runs and gets to the JUMP_ADDR at the end of main.c. However, u-boot doesn't seem to start.

I compiled my own versions of these programs and get the same results.

I'm 'assuming' the stock u-boot works but I don't have any way to verify that.

Any suggestions on what to try?

U-Boot should be at 0x20000 within the NAND

Before you do the jump, print out or inspect the 8 ARM vectors at 0x23F00000 in SDRAM

Compare this data against the nandflash_at91sam9g20ek.bin generated by AT91Bootstrap.

I'll also note you can put quite a lot of code within your AT91Bootstrap application, for example dump out memory, or add other diagnostics.

Bootstrap appears to be starting properly. And I should have noted, if it wasn't obvious, that I'm using dataflash, not nand. Instrumenting bootstrap probably won't be that helpful at this point, since I know it gets to the final JUMP.

Check the data at 0x23F00000 for ARM vectors.

If it's not the code from uboot, or valid ARM code, then you're SOL if you jump to it.

The word at 0x23F0003C should read back as 0xDEADBEEF for uboot ARM builds.

If all else fails, slap on a JTAG pod and step through it.

00000000 : 12 00 00 EA 14 F0 9F E5 - 14 F0 9F E5 14 F0 9F E5 ................
00000010 : 14 F0 9F E5 14 F0 9F E5 - 14 F0 9F E5 14 F0 9F E5 ................
00000020 : A0 00 F0 23 00 01 F0 23 - 60 01 F0 23 C0 01 F0 23 ...#...#`..#...#
00000030 : 20 02 F0 23 80 02 F0 23 - E0 02 F0 23 EF BE AD DE ..#...#...#....
00000040 : 00 00 F0 23 00 00 F0 23 - B0 70 F2 23 00 BF F3 23 ...#...#.p.#...#