Re: [OpenOCD-devel] multiple cores on a single TAP

2016-05-25 Thread Tim Newsome
Thanks. That looks promising. I'll play with it for real once I have a target that has more than one core. I'm happy that this infrastructure exists. Tim On Wed, May 25, 2016 at 1:41 PM, Andreas Färber wrote: > Am 25.05.2016 um 01:34 schrieb Tim Newsome: > > RISC-V supports accessing more than

Re: [OpenOCD-devel] 64-bit addresses

2016-05-25 Thread Tim Newsome
On Wed, May 25, 2016 at 1:44 PM, Andreas Färber wrote: > Am 25.05.2016 um 02:17 schrieb Tim Newsome: > > I notice that eg. read_memory() takes address as a uint32_t. Does > > OpenOCD support 64-bit address spaces? Are there plans to support it? > > See for example: http://openocd.zylin.com/#/c/12

Re: [OpenOCD-devel] 64-bit addresses

2016-05-25 Thread Andreas Färber
Am 25.05.2016 um 02:17 schrieb Tim Newsome: > I notice that eg. read_memory() takes address as a uint32_t. Does > OpenOCD support 64-bit address spaces? Are there plans to support it? See for example: http://openocd.zylin.com/#/c/1200/ Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 N

Re: [OpenOCD-devel] multiple cores on a single TAP

2016-05-25 Thread Andreas Färber
Am 25.05.2016 um 01:34 schrieb Tim Newsome: > RISC-V supports accessing more than one core through a single JTAG TAP. > Is there an existing example in OpenOCD of a target that does the same > thing? http://openocd.org/doc/html/Config-File-Guidelines.html -> 6.3.4 HTH, Andreas -- SUSE Linux Gmb

Re: [OpenOCD-devel] openocd/GDB issue with STM32L151

2016-05-25 Thread Andreas Fritiofson
On Wed, May 25, 2016 at 2:32 PM, Paul Fertser wrote: > > On Wed, May 25, 2016 at 02:19:02PM +0200, Daniel Kowalski wrote: > > Debugging works correctly when I remove last script line (program). > > I don't know why debugger is stuck in half-working state after flashing > > chip. > > I'm still con

Re: [OpenOCD-devel] openocd/GDB issue with STM32L151

2016-05-25 Thread Paul Fertser
Hello, I'm glad you found it out finally! Please see few commits inline. On Wed, May 25, 2016 at 02:19:02PM +0200, Daniel Kowalski wrote: > Debugging works correctly when I remove last script line (program). > I don't know why debugger is stuck in half-working state after flashing > chip. "prog

Re: [OpenOCD-devel] openocd/GDB issue with STM32L151

2016-05-25 Thread Daniel Kowalski
On Wed, 25 May 2016 03:44:52 +0200 Daniel Kowalski wrote: > I downgraded openocd to v0.8.0 (compiled from sources) and it works > correctly (catches breakpoint). I had to change probe to jlink and > transport to jtag (I was using Jtag Lock-pick tiny 2 with SWD - FTDI > based), but it makes no dif

[OpenOCD-devel] [PATCH]: 7259d34 flash: nor: mdr: fix verification problem with 1986VE1T or 1986VE3T

2016-05-25 Thread gerrit
This is an automated email from Gerrit. Andrey Skvortsov (andrej.skvort...@gmail.com) just uploaded a new patch set to Gerrit, which you can find at http://openocd.zylin.com/3509 -- gerrit commit 7259d34b14d00fe7724fa3ee2154eab03e3d4094 Author: Andrey Skvortsov Date: Wed May 25 13:11:18 2016