aboutsummaryrefslogtreecommitdiff
path: root/debug/targets/RISC-V/spike32-2.py
AgeCommit message (Collapse)AuthorFilesLines
2017-12-27Test FPRs that aren't XLEN in size.Tim Newsome1-1/+1
Cover all combinations of 32,64 bit XLEN with F and FD extensions. Finishes Issue https://github.com/riscv/riscv-openocd/issues/110
2017-09-29Fix tests to work in multi-gdb mode.Tim Newsome1-1/+1
The Gdb class now can handle connecting to more than one gdb. It enumerates the harts across all connections, and when asked to select a hart, it transparently sends future gdb commands to the correct instance. Multicore tests still have to be aware of some differences. The main one is that when executing 'c' in RTOS mode, all harts resume, while in multi-gdb mode only the current one resumes. Additionally, gdb doesn't set breakpoints until 'c' is issued, so the hart where breakpoints are set needs to be resumed before other harts might see them.
2017-09-21Add coverage for single-core non-rtos OpenOCD.Tim Newsome1-1/+1
2017-08-28Increase remotetimeout for spike targets.Tim Newsome1-0/+1
On overloaded systems, when executing compare-sections, otherwise gdb might hit a timeout and the compare-sections code doesn't deal with it. (You get an error message complaining that 130 is not a valid hex digit.)
2017-08-28Make pylint happy.Tim Newsome1-1/+1
2017-08-28Make the debug tests aware of multicore.Tim Newsome1-0/+11
Targets now contain an array of harts. When running a regular test, one hart is selected to run the test on while the remaining harts are parked in a safe infinite loop. There's currently only one test that tests multicore behavior, but there could be more. The infrastructure should be able to support heterogeneous multicore, but I don't have a target like that to test with.