When i try to debug some demo-code from ATMELs AT91SAM3U-EK via arm-none-eabi-gdb, then the j-link gdb-server first donwload something, but stuck then for ever in a loop. Hers the log:
...
T0F34 1828:368 JLINK_ReadMemHW(0x400E0A08, 0x0004 Bytes, ...) - Data: 00 00 00 01
T0F34 1828:369 JLINK_ReadMemHW(0x400E0A08, 0x0004 Bytes, ...) - Data: 00 00 00 01
T0F34 1828:370 JLINK_ReadMemHW(0x400E0A08, 0x0004 Bytes, ...) - Data: 00 00 00 01
T0F34 1828:371 JLINK_ReadMemHW(0x400E0A08, 0x0004 Bytes, ...)

The address 0x400E0A08 is the EEFC Flash Status Register of the bank1. And the state says: "The Enhanced Embedded Flash Controller (EEFC) is ready to start a new command."

But the j-link gdb-server dont belive this in some way and asks again and again... Hier are some gdb-commands i tryed:

target remote localhost:2331
monitor reset
monitor speed auto
monitor flash device = AT91SAM3U4E
monitor flash breakpoints = 1
monitor flash download = 1
load bin/usb-device-massstorage-project-at91sam3u-ek-at91sam3u4-flash.elf

Any hint?

The "monitor endian little" was missing...