Hello,
I noticed the problem with both Eclipse and VisualGDB. Switching to SWD solved the problem in both cases.
I tried several recent versions of Jlink software and the result was the same - wrong endian instructions are displayed.
It's not a big problem (SWD works fine). I just thought I would mention it here to inform other ATSAMA5 users...
I have been playing around with a SAMA5D2 Xplained board.
It seems that if EDBG is re-programmed as Jlink, code disassembly is treated as *big* endian by mistake when using JTAG. This results in 'garbage' instructions.
SWD works fine (little endian instructions)
Also when using JTAG I have noticed writing to memory via JTAG is not reliable (sometimes top bit is not set). SWD looks OK.
P
