- Jul 19, 2023
-
-
Tim Newsome authored
The main reason is to populate the cache, so that pull requests can benefit from a spike cache even the very first time. (Caches populated in one pull request are inaccessible to another one.) Change-Id: If894f2ccfaadc740bd52e34be3024153626b9fbd Signed-off-by:Tim Newsome <tim@sifive.com>
-
Tim Newsome authored
target/riscv: cleanup trigger setup
-
- Jul 18, 2023
-
-
Evgeniy Naydanov authored
* Add a warning when eq trigger is setup and it's behavior is different from other triggers. * Make eq trigger's behavior consistent with other triggers in case of length == 1. * Fix a bug in setting chained triggers (LT, GT case). * Improve logging. Change-Id: Id1ed0d11971b8ed875afbb979e6c8a8b51dd3818 Signed-off-by:Evgeniy Naydanov <evgeniy.naydanov@syntacore.com>
-
Tim Newsome authored
target/breakpoints: Clear software breakpoints from available targets
-
Tim Newsome authored
target/riscv: refactor read_memory_progbuf()
-
- Jul 15, 2023
-
-
Evgeniy Naydanov authored
There were a couple of problems with previous implementation: * Misalligned read would return ERROR_OK and print all zeroes. * CMDERR_BUSY for abstract access was improperly handled: According to the spec, no assumptions can be made about DM_DATA* contents in such a case, but these were considered valid values from memory. * A fallback to one element read was implemented when DMI_STATUS_BUSY occurred during batch reads, even though this can be accounted for. Change-Id: I09174c61c951b2bb97a529b7f0aa5afaa995179b Signed-off-by:Evgeniy Naydanov <evgeniy.naydanov@syntacore.com>
-
Tim Newsome authored
target/riscv: update some macro
-
- Jul 14, 2023
-
-
Mark Zhuang authored
Change-Id: Id2f1a2568a39eec0a9dd4fe0f155619b11f9d6ba Signed-off-by:Mark Zhuang <mark.zhuang@spacemit.com>
-
Mark Zhuang authored
1. update RISCV_MAX_HARTS to 2^20 according to SPEC 2. remove RISCV_MAX_REGISTERS, it's not used anywhere anymore 3. add parentheses Change-Id: Iadf0fa1ba3bbe5b9420b8430883e140db87f4f9e Signed-off-by:Mark Zhuang <mark.zhuang@spacemit.com>
-
- Jul 13, 2023
-
-
Tim Newsome authored
Change-Id: I3824e215a845ba7df3c7887ce1693378fde94b4b Signed-off-by:Tim Newsome <tim@sifive.com>
-
Tim Newsome authored
If a target where a software breakpoint was set is not currently available, but there are other targets in the same SMP group that are available, then we can use those to remove the software breakpoint. Change-Id: I9faa427c7b3aee31504e6e6599539e6f29b58d8f Signed-off-by:Tim Newsome <tim@sifive.com>
-
- Jul 07, 2023
-
-
Tim Newsome authored
Change-Id: If8806853d47779b5b208202803ed5da437f7b624 Signed-off-by:Tim Newsome <tim@sifive.com>
-
Tim Newsome authored
I think this was incorrectly removed in a merge. Change-Id: I49fce230f35ae7bd368d2ed780c6c1ffe5939fda
-
Tim Newsome authored
[target/riscv] support for smp group manipulation
-
Tim Newsome authored
target/riscv: Fix the trigger writing sequence
-
- Jul 04, 2023
-
-
Marek Vrbka authored
According to section 5.6 in the RISC-V debug specification, the previous way to set triggers was incorrect, as was discussed as part of https://github.com/riscv/riscv-openocd/issues/870 . This commit fixes the sequence to be in line with the specification as well as adds some comments to clarify for any future reader as to what is actually done. Change-Id: Iffc5cc0f866a466a7aaa72a4c53ee95c9080ac9d Signed-off-by:
Marek Vrbka <marek.vrbka@codasip.com>
-
- Jul 03, 2023
-
-
Parshintsev Anatoly authored
this functionality allows to query if a target belongs to some smp group and to dynamically turn on/off smp-specific behavior Change-Id: I469453d95e7c1640a91bc60d80c854404e508535 Signed-off-by:Parshintsev Anatoly <anatoly.parshintsev@syntacore.com>
-
- Jun 30, 2023
-
-
Tim Newsome authored
Add null pointer check before right shift for bscan tunneling.
-
- Jun 28, 2023
-
-
Tim Newsome authored
target/riscv: fix haltgroup_supported to info->haltgroup_supported
-
- Jun 27, 2023
-
-
Mark Zhuang authored
Change-Id: Id1276aecd3097d90e035bf3808e0c472188ba474 Signed-off-by:Mark Zhuang <mark.zhuang@spacemit.com>
-
- Jun 23, 2023
-
-
eolson authored
Change-Id: I5d4764c777f33d48705b3e5273eb840c13cfbfb7 Signed-off-by:eolson <erin.olson@seagate.com>
-
Chao Du authored
* rtos/FreeRTOS: solve some conflicting usage of thread id. 1. There are some RISCV-specific usage of thread_id, which has conflict with upstream. Some adaptions are made in this patch, to make sure OpenOCD is sending a clear thread list to gdb. 2. Use freertos_read_struct_value for xSchedulerRunning. Change-Id: I001a88a0c6d8eac98a389c0217b4897f28124840 Signed-off-by:
Chao Du <duchao@eswincomputing.com> * fix typo. Change-Id: Id6546cc74de44bbee7e44b7cb29b769a2f35ec4a * correct the data type. Change-Id: I28c7e111e569d94ba5f6e1ae21745ddb34d4dd12 * changes as per the review comment. Change-Id: Ica4c705a8f2657700dc27e24790287ca802480fd * another macro replacement. Change-Id: Ia9330fed32d917cf87804051ba1b8d6ac42cfb7b --------- Signed-off-by:
Chao Du <duchao@eswincomputing.com>
-
- Jun 22, 2023
-
-
Tim Newsome authored
target/riscv: resume only halted harts
-
Tim Newsome authored
When dcsr.ebreak* might be cleared, halt the target and set it again
-
- Jun 21, 2023
-
-
Evgeniy Naydanov authored
With this change, failures to resume a hart due to it not being halted are more explicitly logged or reported as an error. Change-Id: Ia55d8df85a908363d0f2140637ce1e47c1ab6251 Signed-off-by:Evgeniy Naydanov <evgeniy.naydanov@syntacore.com>
-
Tim Newsome authored
This involves halting the target, which might have unintended side effects, but when the debugger is connected software breakpoints must trap to the debugger. Anything else is a terrible user experience. Change-Id: I1f7bb610eeeb054cc3042dc6bcfc16589ce12a31 Signed-off-by:Tim Newsome <tim@sifive.com>
-
Tim Newsome authored
We need to know, so we can set it when necessary. Change-Id: I1f0d5107f1208f7b9316e15870f0804e51232dee Signed-off-by:Tim Newsome <tim@sifive.com>
-
Tim Newsome authored
Intended as a place where we can interact with the target without too much concern about preserving state and doing exactly the right thing while poll() is going on. Change-Id: Ic9bd441caae85901a131fd45e742599803df89b5 Signed-off-by:Tim Newsome <tim@sifive.com>
-
Tim Newsome authored
Specifically, call into the RISC-V version when target becomes halted, running, or unavailable. I'll be using unavailable shortly. Change-Id: I9ffffdccbf22e053fe6390d656b362bf9ab9559a Signed-off-by:Tim Newsome <tim@sifive.com>
-
Tim Newsome authored
Will be used later when we want to do a quick halt/resume. Change-Id: Ib80166234c4c277b7d9ce26b7566ac0f93017e64 Signed-off-by:Tim Newsome <tim@sifive.com>
-
Tim Newsome authored
* Only set ebreak bits that might be supported based on misa. * Don't write dcsr if its value wouldn't change. Change-Id: I7087af0b0df0fbdbf994373b5c887b9b389df872 Signed-off-by:Tim Newsome <tim@sifive.com>
-
Tim Newsome authored
Make it callable earlier, handle `supported` being NULL, and make enum names more clear. Change-Id: If4d286b54ccfc01eb5de5a57eb18f748c920e979 Signed-off-by:Tim Newsome <tim@sifive.com>
-
Tim Newsome authored
Makes it easier when reading debug logs. Change-Id: I3938437357e0d74e1cda680693f907a20c5579c7 Signed-off-by:Tim Newsome <tim@sifive.com>
-
Tim Newsome authored
The riscv013_on_halt function was being called but its implementation was empty, providing no additional functionality. Removed the function declaration, calls to it, and its implementation since it is not required. Change-Id: I425ea890deadeec945f0a47af247f3f99172e801 Signed-off-by:Tim Newsome <tim@sifive.com>
-
Tim Newsome authored
Otherwise I get a compiler warning, which fails the build. Change-Id: Ib7d4ab85160b537d07c74f8651ac42906fd661ed Signed-off-by:Tim Newsome <tim@sifive.com>
-
- Jun 17, 2023
-
-
Tim Newsome authored
target/riscv: Early exit magic sequence checks in riscv_semihosting
-
- Jun 16, 2023
-
-
Tim Newsome authored
When halted we don't need to read all 3 instructions before deciding the sequence doesn't match. Change-Id: I9f8345960ce27e859265af901a368166a70b9fde Signed-off-by:Tim Newsome <tim@sifive.com>
-
- Jun 15, 2023
-
-
Chao Du authored
* rtos/FreeRTOS: pxCurrentTCB should be used for judgment. The current TCB is stored in pxCurrentTCB, which is somehow RISC-V-specific, should not be overwritten from upstream (#816). * fix the code style check. Signed-off-by:
Chao Du <duchao@eswincomputing.com> Change-Id: I9ffa8947f0cb9e93c7d96866882a5a1e8e69afad * revert some over-changes in last commit. Change-Id: Ie88bd75b59190503db11ee4538281bd13b554e50 Signed-off-by:
Chao Du <duchao@eswincomputing.com> --------- Signed-off-by:
Chao Du <duchao@eswincomputing.com>
-
- Jun 13, 2023
-
-
Tim Newsome authored
target/riscv: Remove unnecessary prototypes.
-
- Jun 10, 2023
-
-
Tim Newsome authored
These functions used to exist but don't anymore. (Pointed out in #863) Change-Id: Iac6b5edd320bdff7628a788861e332f956dcd93d Signed-off-by:Tim Newsome <tim@sifive.com>
-