On Mon, 2008-10-06 at 18:58 -0400, Duane Ellis wrote: > John McCarthy wrote: > > Hi, > > > > has anyone got OpenOCD working with a Faraday FA526 processor (actually > > a Raritan Kira100 which uses a FA526 processor)? It appears to be an > > ARM926 variant but apparently not exactly. Does this require target > > specific support or am I just missing some configuration? > > > > I doubt it is an ARM926 - I think it is an ARM920. > > ARM926 = uses ARMv6 instruction set. > > This page: > > http://www.faraday-tech.com/html/products/IP/processor/fa5_series.html > > Says it is an "ARMV4T" instruction set which would imply - ARM920 ...
Unfortunately, the arm20t behaves even worse that the arm926 target: Debug: 515 12483 command.c:82 script_command(): script_command - halt Debug: 516 12483 command.c:99 script_command(): script_command - halt, argv[0]=ocd_halt Debug: 517 12483 target.c:1750 handle_halt_command(): - Debug: 518 12483 arm7_9_common.c:979 arm7_9_halt(): target->state: running Debug: 519 12483 embeddedice.c:403 embeddedice_write_reg(): 0: 0x00000007 Debug: 520 12485 target.c:1730 target_wait_state(): waiting for target halted... Debug: 524 14143 embeddedice.c:403 embeddedice_write_reg(): 0: 0x00000005 Debug: 525 14143 embeddedice.c:403 embeddedice_write_reg(): 0: 0x00000005 Debug: 526 14145 arm7_9_common.c:1075 arm7_9_debug_entry(): target entered debug from ARM state Error: 527 14153 armv4_5.h:117 armv4_5_mode_to_number(): invalid mode value encountered Error: 528 14153 arm7_9_common.c:1103 arm7_9_debug_entry(): cpsr contains invalid mode value - communication failure Debug: 529 14153 command.c:407 run_command(): Command failed with error code -305 User: 530 14153 command.c:607 openocd_jim_vfprintf(): Runtime error, file "command.c", line 436: User: 531 14153 command.c:607 openocd_jim_vfprintf(): Which apparently didn't halt. Another halt and I get a (large) loop of the same error: Error: 9619 409677 arm7_9_common.c:1103 arm7_9_debug_entry(): cpsr contains invalid mode value - communication failure Warning: 9620 409771 arm7_9_common.c:673 arm7_9_poll(): DBGACK set while target was in unknown state. Reset or initialize target. Debug: 9621 409771 embeddedice.c:403 embeddedice_write_reg(): 0: 0x00000005 Debug: 9622 409771 embeddedice.c:403 embeddedice_write_reg(): 0: 0x00000005 Debug: 9623 409773 arm7_9_common.c:1075 arm7_9_debug_entry(): target entered debug from ARM state Error: 9624 409781 armv4_5.h:117 armv4_5_mode_to_number(): invalid mode value encountered Error: 9625 409781 arm7_9_common.c:1103 arm7_9_debug_entry(): cpsr contains invalid mode value - communication failure Warning: 9626 409875 arm7_9_common.c:673 arm7_9_poll(): DBGACK set while target was in unknown state. Reset or initialize target. Debug: 9627 409875 embeddedice.c:403 embeddedice_write_reg(): 0: 0x00000005 Debug: 9628 409875 embeddedice.c:403 embeddedice_write_reg(): 0: 0x00000005 Debug: 9629 409877 arm7_9_common.c:1075 arm7_9_debug_entry(): target entered debug from ARM state Error: 9630 409885 armv4_5.h:117 armv4_5_mode_to_number(): invalid mode value encountered Error: 9631 409885 arm7_9_common.c:1103 arm7_9_debug_entry(): cpsr contains invalid mode value - communication failure Warning: 9632 409981 arm7_9_common.c:673 arm7_9_poll(): DBGACK set while target was in unknown state. Reset or initialize target. Debug: 9633 409981 embeddedice.c:403 embeddedice_write_reg(): 0: 0x00000005 Debug: 9634 409981 embeddedice.c:403 embeddedice_write_reg(): 0: 0x00000005 Debug: 9635 409983 arm7_9_common.c:1075 arm7_9_debug_entry(): target entered debug from ARM state Error: 9636 409991 armv4_5.h:117 armv4_5_mode_to_number(): invalid mode value encountered Error: 9637 409991 arm7_9_common.c:1103 arm7_9_debug_entry(): cpsr contains invalid mode value - communication failure Warning: 9638 410094 arm7_9_common.c:673 arm7_9_poll(): DBGACK set while target was in unknown state. Reset or initialize target. Debug: 9639 410094 embeddedice.c:403 embeddedice_write_reg(): 0: 0x00000005 Debug: 9640 410094 embeddedice.c:403 embeddedice_write_reg(): 0: 0x00000005 Debug: 9641 410096 arm7_9_common.c:1075 arm7_9_debug_entry(): target entered debug from ARM state Warning: 9642 410107 jtag.c:1217 jtag_check_value(): value captured during scan didn't pass the requested check: captured: 0x00 check_value: 0x01 check_mask: 0x0f Warning: 9643 410107 jtag.c:1177 jtag_read_buffer(): in_handler reported a failed check I'm sure I read somewhere (I think it was for the WinBond BMC which also uses a Faraday FA526) that it is an ARM926ejs but I'd need to recheck my facts to be sure. In either case, OpenOCD is currently not happy using either arm920t or arm926ejs with the Kira100. I'll see if the WinBond behaves any better (though I'm not too hopeful). Cheers, John McCarthy. _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
