I have been trying to test support for the ARM926EJ-S added in recent versions.
I tried the Windows native r128 from yagarto, but this seemed to lock-up.
So I have now tried compiling r130 in cygwin, this seems to run but I cannot telnet in or access with GDB.
Am I doing something wrong or is there a bug in the ARM926EJ-S support?
My config is :-
#daemon configuration
telnet_port 4444
gdb_port 3333
#interface
interface ft2232
ft2232_device_desc "Amontec JTAGkey A"
ft2232_layout jtagkey
ft2232_vid_pid 0x0403 0xcff8
jtag_speed 5
#use combined on interfaces or targets that can't set TRST/SRST separately
reset_config trst_and_srst
#jtag scan chain
#format L IRC IRCM IDCODE (Length, IR Capture, IR Capture Mask, IDCODE)
jtag_device 4 0x1 0xf 0xe
jtag_nsrst_delay 100
jtag_ntrst_delay 100
#target configuration
daemon_startup reset
#target <type> <endianness> <startup mode> <chainpos> <variant>
target arm926ejs little run_and_halt 0 arm926ejs
run_and_halt_time 0 500
My target is a Hilscher netX 500, using a JtagKey to debug.
I haven’t posted my logfile as it is multi-megabyte in size, it looks okay near the start, getting as far as stopping the core, reading registers etc.
The last sensible log entry is :-
Debug: arm926ejs.c:422 arm926ejs_post_debug_entry(): D FSR: 0x00000040, D FAR: 0x00000000, I FSR: 0x00000000
This then repeats continuously with :-
Debug: ft2232.c:1182 ft2232_execute_queue(): DR scan, 48 bit, end in 8
Debug: jtag.c:1027 jtag_read_buffer(): fields[1].in_value: 0x01
Debug: jtag.c:996 jtag_build_buffer(): fields[0].out_value: 0x00000007
Debug: jtag.c:996 jtag_build_buffer(): fields[1].out_value: 0x01
Debug: jtag.c:996 jtag_build_buffer(): fields[2].out_value: 0x38f0
Debug: jtag.c:996 jtag_build_buffer(): fields[3].out_value: 0x01