I'm getting some odd behaviour on an AT91RM3400-based board that I was hoping people could help with.

The JTAG/ICE connection (via a wiggler-alike) fails to connect at anything faster than the lowest OcdRemote speed (4kHz) unless I let it sit in a loop trying to connect, which causes it to succeed after about forty attempts. This is apparently to expected behaviour, since it only has the slow clock at this point.

But ignoring the JTAG cable, if I just turn the board on or reset it and watch the DBGU output, it usually gives nothing, and occasionally (about once in 10-100 attempts) gives:
" *** ATMEL AT91 UPLOADER ***
Copyright (C) 2001 ATMEL Corporations Version: 1.0"
and then stops. (Sometimes it starts "MEL AT91" and misses the " *** AT".)

Either way, it never gets to the point where it offers me a menu.

Any suggestions or ideas what might be happening?

It turns out that it's starting up at 115200, printing out the splash message and then switching to 38400, printing the message again, and then switching to XMODEM mode (i.e. emitting "C" repeatedly).

This is clearly quite a different version to the RomBoot source on the Atmel CD and which is described in the documentation. Possibly it's because I'm using an old sample chip? This one has these identifying messages on it:

Atmel
AT91RM3400
AI-002
58A06S 0423
4P1818 ARM

Having worked out what it's doing, I now need to know:
- Is this an old version of the software?
- Can I get the source/binary (with symbol table if possible)?
- If not, if I send it a file over XMODEM, what will it do with it?
- Will recent versions of the chip have different software?
- If so, where can I get the source/binary for that?
- Where does the program sit in memory (so I don't accidentally overwrite it)?

I'm basically just after a way to get my code into DataFlash. There's also the question of how much working space in RAM the XMODEM program uses and where it is, so that I can know the maximum file size that's safe to send.