Hi,
On Wed, Dec 28, 2022 at 10:16:13PM +0530, Er.charmin Faldu wrote:
> Please find the bug report I am getting, your help is required to solve it.
I do not see any bug report, only the output of an OpenOCD process
that had no issues working at all, it's a normal regular run.
>
Dear Sir/mam,
Please find the bug report I am getting, your help is required to solve it.
Open On-Chip Debugger 0.12.0-rc1+dev-00061-g5e9b46d77 (2022-10-20-14:50) [
https://github.com/STMicroelectronics/OpenOCD]
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen
> But I couldn't find any code about `set_bscan_tunnel_ir` (I think `irscv
> set_bscan_tunner_ir ` you mentioned is probably wrong, should be
> `riscv set_bscan_tunnel_ir`, right?)
> I checked the master branch of openocd GitHub and SourceForge repo.
> Is it in another repository? please elaborat
Hi,
Aha, so it is in riscv-openocd repo, not merged into the main openocd repo
yet.
OK, good to know! And yes, this solves the bug I reported.
Thanks, Tommy!
BR,
Peng
Tommy Murphy 于2022年10月12日周三 22:20写道：
> > But I couldn't find any code about `set_bscan_tunnel_ir` (I think `irscv
> set_bscan_t
AM peng cheng
> wrote:
>
>> Registered in the mail list and repost this bug report again.
>>
>> peng cheng 于2022年10月12日周三 12:08写道：
>>
>>> Hi all,
>>>
>>> Hope everyone had a nice day!
>>>
>>> Don't know whether this is the
You can set the value you need for your hardware using `irscv
set_bscan_tunner_ir `. The code you pointed at is the default value.
Tim
On Wed, Oct 12, 2022 at 3:15 AM peng cheng wrote:
> Registered in the mail list and repost this bug report again.
>
> peng cheng 于2022年10月12日周
-- Forwarded message -
发件人： peng cheng
Date: 2022年10月12日周三 12:08
Subject: bug report: wrong user4 ir when using riscv user4 jtag tunnel
To:
Hi all,
Hope everyone had a nice day!
Don't know whether this is the correct place, but please forward it if I am
wrong.
Found
Registered in the mail list and repost this bug report again.
peng cheng 于2022年10月12日周三 12:08写道：
> Hi all,
>
> Hope everyone had a nice day!
>
> Don't know whether this is the correct place, but please forward it if I
> am wrong.
>
> Found this tricky issue whe
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 l
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
@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
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
On Mon, Nov 3, 2014 at 9:33 PM, Christian Bjørge Thoresen
wrote:
>>>Also so far I¹ve never seen the problem after reconnecting the USB cable
>>>to the interface board. My best guess would therefore be that depending
>>>on
>>>the termination of OpenOCD, there may still be a read transfer in the
>>>
Hi,
I hope Nathan (CC'd) can give us additional suggestions here as he is
involved in libusb darwin port.
For your convenience, the thread starts at
http://article.gmane.org/gmane.comp.debugging.openocd.devel/25696
TIA
On Mon, Nov 03, 2014 at 01:33:02PM +, Christian Bjørge Thoresen wrote:
>
On 30/10/14 15:02, "Christian Bjørge Thoresen"
wrote:
>
>On 30/10/14 14:20, "Christian Bjørge Thoresen"
>wrote:
>
>>
>>Also so far I¹ve never seen the problem after reconnecting the USB cable
>>to the interface board. My best guess would therefore be that depending
>>on
>>the termination of Ope
On 30/10/14 14:20, "Christian Bjørge Thoresen"
wrote:
>
>Also so far I¹ve never seen the problem after reconnecting the USB cable
>to the interface board. My best guess would therefore be that depending on
>the termination of OpenOCD, there may still be a read transfer in the
>system which will
On 30/10/14 06:41, "Xiaofan Chen" wrote:
>On Thu, Oct 30, 2014 at 12:21 PM, Paul Fertser
>wrote:
>> Hello,
>>
>> On Wed, Oct 29, 2014 at 09:09:13PM +, Christian Bjørge Thoresen
>>wrote:
>>> I don't think I tried to install the official drivers, but I'll
>>> still try to check if they might
On Thu, Oct 30, 2014 at 1:41 PM, Xiaofan Chen wrote:
> On Thu, Oct 30, 2014 at 12:21 PM, Paul Fertser wrote:
>> Hello,
>>
>> On Wed, Oct 29, 2014 at 09:09:13PM +, Christian Bjørge Thoresen wrote:
>>> I don't think I tried to install the official drivers, but I'll
>>> still try to check if the
On Thu, Oct 30, 2014 at 12:21 PM, Paul Fertser wrote:
> Hello,
>
> On Wed, Oct 29, 2014 at 09:09:13PM +, Christian Bjørge Thoresen wrote:
>> I don't think I tried to install the official drivers, but I'll
>> still try to check if they might have something to do with
>> this.
>
> AFAIK, OS X co
Hello,
On Wed, Oct 29, 2014 at 09:09:13PM +, Christian Bjørge Thoresen wrote:
> I don't think I tried to install the official drivers, but I'll
> still try to check if they might have something to do with
> this.
AFAIK, OS X comes with drivers for FTDI preinstalled, and you need to
manually k
Fra: andr...@fritiofson.net på vegne av Andreas
Fritiofson
Sendt: 29. oktober 2014 19:07
> On Wed, Oct 29, 2014 at 1:51 PM, Christian Bjørge Thoresen
> wrote:
>> Hi
>> I’m using OpenOCD 0.8.0 on OS X, with TAMPA TIAO FTDI interface and
>> STM32F103 target on a board by lc-soft. Also tested
On Wed, Oct 29, 2014 at 1:51 PM, Christian Bjørge Thoresen <
christian.thore...@hbv.no> wrote:
> Hi
>
> I’m using OpenOCD 0.8.0 on OS X, with TAMPA TIAO FTDI interface and
> STM32F103 target on a board by lc-soft. Also tested with a different
> STM32F103 target.
>
> Problem: OpenOCD fails to co
Hi
I'm using OpenOCD 0.8.0 on OS X, with TAMPA TIAO FTDI interface and STM32F103
target on a board by lc-soft. Also tested with a different STM32F103 target.
Problem: OpenOCD fails to connect to the target about 50 % of the time,
freezing after call to jtag_examine_chain().
Debugging done so f
On Jan 9, 2014, at 10:47 AM, Andreas Fritiofson wrote:
>
> On Thu, Jan 9, 2014 at 8:02 AM, Colin Howarth wrote:
> Hi,
>
> I'm trying to compile OpenOCD-0.7.0 to use the USBprog 4.0 interface on
> Mac-OS-X
>
> I've installed libusb-1.0 and compiling for a different interace (an
> FT2232-based
On Jan 9, 2014, at 8:10 AM, Paul Fertser wrote:
> On Thu, Jan 09, 2014 at 08:02:16AM +0100, Colin Howarth wrote:
>> I'm trying to compile OpenOCD-0.7.0 to use the USBprog 4.0 interface on
>> Mac-OS-X
>
> Please do not try to compile 0.7.0, try current code, and if that has
> any issues, report.
On Thu, Jan 9, 2014 at 8:02 AM, Colin Howarth wrote:
> Hi,
>
> I'm trying to compile OpenOCD-0.7.0 to use the USBprog 4.0 interface on
> Mac-OS-X
>
> I've installed libusb-1.0 and compiling for a different interace (an
> FT2232-based OpenOCD-USB) went OK (after fixing usb.h).
>
This problem is l
Hi!
What Paul said plus the following.
On Thu, Jan 9, 2014 at 7:42 AM, Colin Howarth wrote:
>
> sudo ln -sf /usr/local/include/libusb-1.0/libusb.h /usr/local/include/usb.h
>
This is not a good idea, usb.h is the header for libusb-0.1 which is an
entirely different API than libusb-1.0.
/Andrea
Hi,
On Thu, Jan 09, 2014 at 08:02:16AM +0100, Colin Howarth wrote:
> I'm trying to compile OpenOCD-0.7.0 to use the USBprog 4.0 interface on
> Mac-OS-X
Please do not try to compile 0.7.0, try current code, and if that has
any issues, report.
--
Be free, use free (http://www.gnu.org/philosophy/
Hi,
I'm trying to compile OpenOCD-0.7.0 to use the USBprog 4.0 interface on Mac-OS-X
I've installed libusb-1.0 and compiling for a different interace (an
FT2232-based OpenOCD-USB) went OK (after fixing usb.h).
However, if I try to compile after
./configure --enable-usbprog
compilation ends wi
Hi,
On Thu, Jan 09, 2014 at 07:42:33AM +0100, Colin Howarth wrote:
> I was trying to compile OpenOCD-0.7.0 on Mac-OS-X 10.6.8.
Please try current git HEAD instead, feel free to report if you have
any issues. And most likely you do not need the ft2232 driver, please
use "ftdi" OpenOCD interface dr
Hi,
I was trying to compile OpenOCD-0.7.0 on Mac-OS-X 10.6.8.
I had previously installed libusb-1.0 and libftd2xx.1.2.2.
Running ./configure halted with a message saying it couldn't find/use usb.h.
I created a symlink using
sudo ln -sf /usr/local/include/libusb-1.0/libusb.h /usr/local/include/
31 matches
Mail list logo
