OpenCores
URL https://opencores.org/ocsvn/or1k/or1k/trunk

Subversion Repositories or1k

[/] [or1k/] [trunk/] [insight/] [gdb/] [remote-or1k.c] - Rev 1765

Rev

Details | Compare with Previous | Blame

Filtering Options

Clear current filter

Rev Log message Author Age Path
1765 root 5547d 15h /or1k/trunk/insight/gdb/remote-or1k.c
1124 Initialize or1k_implementation with reasonable defaults for the number
of implementation registers. This doesn't affect the jtag or sim
targets at all because those values are always overwritten when
or1k_implementation is initialized. However, it is necessary when
connecting to remote gdb stubs through a serial port or socket, since
or1k_implementation is not yet initialized for those targets.
sfurman 7743d 10h /or1k/trunk/insight/gdb/remote-or1k.c
613 init: trap exception occurs always; initialization of sr not needed anymore markom 8150d 03h /or1k/trunk/insight/gdb/remote-or1k.c
607 single step steps just one instruction ^c bug fixed markom 8152d 02h /or1k/trunk/insight/gdb/remote-or1k.c
593 ctrl-c handling fixed markom 8156d 01h /or1k/trunk/insight/gdb/remote-or1k.c
405 Stepping trough l.jal and l.jalr fixed. simons 8201d 04h /or1k/trunk/insight/gdb/remote-or1k.c
379 bug fixed. markom 8208d 05h /or1k/trunk/insight/gdb/remote-or1k.c
375 Support for breakpoints changed. simons 8208d 16h /or1k/trunk/insight/gdb/remote-or1k.c
374 *** empty log message *** simons 8208d 22h /or1k/trunk/insight/gdb/remote-or1k.c
373 update after links markom 8209d 02h /or1k/trunk/insight/gdb/remote-or1k.c
372 steps toward joining or32.c and opcode/or32.h of or1ksim and gdb; added opcodes/or32.c; more detailed gdb l.trap handling markom 8209d 04h /or1k/trunk/insight/gdb/remote-or1k.c
363 program can be stepped and continued before running it, supporting low level debugging markom 8214d 00h /or1k/trunk/insight/gdb/remote-or1k.c
362 some changes based on current modifications to or1k; cleaner register naming; ctrl-c causes stepi; write&read pc work on next instruction markom 8214d 05h /or1k/trunk/insight/gdb/remote-or1k.c
207 Several major changes to allow gdb to work with an Or1k implementation
that does not need a writeable PC. This version will use the breakpoint
vector and install a new vector into the EPC register, and then single
step out of the breakpoint exception. The breakpoint exception vector
must include only 2 commands: l.rfe and l.nop. Anything else and this
gdb version will fail w/ or1ksim.
chris 8269d 06h /or1k/trunk/insight/gdb/remote-or1k.c
151 Typo in the previous commit. Sorry. chris 8361d 07h /or1k/trunk/insight/gdb/remote-or1k.c
150 Fixed some single stepping issues chris 8361d 07h /or1k/trunk/insight/gdb/remote-or1k.c
143 Modifications necessary to work with JTAG or1ksim simulator chris 8363d 02h /or1k/trunk/insight/gdb/remote-or1k.c
135 Fixed a couple of bugs related to updating registers over JTAG
during debugging.
chris 8367d 04h /or1k/trunk/insight/gdb/remote-or1k.c
125 Fixed a bug involving failure to reset chain after or1k_flush_pipeline() chris 8370d 03h /or1k/trunk/insight/gdb/remote-or1k.c
122 or1k target init call fixed.
long long type converted to LONGEST.
markom 8377d 07h /or1k/trunk/insight/gdb/remote-or1k.c

1 2 Next >

Show All

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.