Re: [OpenOCD-devel] Bug report: RISC-V sba, incomplete recovery after sbbusyerror

2020-10-14 Thread Joe Stoy
Hi Jan That looks fine to me (though I haven't yet tested it). I guess strictly speaking the "| DM_SBCS_SBBUSYERROR" is unnecessary, as we know that bit is already set, but no matter. Thanks for making the fix. Regards joe ___ OpenOCD-devel mailing

Re: [OpenOCD-devel] Bug report: RISC-V sba, incomplete recovery after sbbusyerror

2020-10-14 Thread Jan Matyáš
fully upstreamed to the > main openocd project/repo? > -- > *From:* Joe Stoy > *Sent:* Tuesday, October 13, 2020 11:21:42 PM > *To:* openocd-devel@lists.sourceforge.net < > openocd-devel@lists.sourceforge.net> > *Subject:* [OpenOCD-devel] Bug report

Re: [OpenOCD-devel] Bug report: RISC-V sba, incomplete recovery after sbbusyerror

2020-10-13 Thread Tommy Murphy
@lists.sourceforge.net Subject: [OpenOCD-devel] Bug report: RISC-V sba, incomplete recovery after sbbusyerror This refers to "Open On-Chip Debugger 0.10.0+dev-g27c0fd7a (2020-01-04-05:57)". When controlling a RISC-V debug module, using system bus access with autoincrementing bursts, if sbbusyer

[OpenOCD-devel] Bug report: RISC-V sba, incomplete recovery after sbbusyerror

2020-10-13 Thread Joe Stoy
This refers to "Open On-Chip Debugger 0.10.0+dev-g27c0fd7a (2020-01-04-05:57)". When controlling a RISC-V debug module, using system bus access with autoincrementing bursts, if sbbusyerror is set, openocd currently clears the error bit by writing 0x0040 to the sbcs register. This also clears