Re: [OpenOCD-devel] Cortex A/M - DAP crazyness

On Wed, May 7, 2014 at 5:10 PM, Duane Ellis wrote: > [quoting out of order ..] > > andreas>> I have thought about this a great deal over the past years and > wandered quite far off from where OpenOCD is today. So my ideas are maybe > not very realistic in the short term. But it hardly hurts to ha

Re: [OpenOCD-devel] Source Level Debug using OpenOCD/GDB/Eclipse on Intel® Quark SoC X1000 Application Note

Hi all, thanks for the feedback. Most of your concerns have been already addressed in the update. As I wrote below the version you currently get on the website is outdated. And I've added what I could for the items which you reported and were not there yet. Let me clarify a couple of things tho

Re: [OpenOCD-devel] Cortex A & M - issue = assumed DAP access ports

duane>> [ suggest: means to specify the DEBUG and MEM ap ports for a core, without using ROM tables and hard coding] Paul.Fertser>> [ Lots of back and forth with duane about this ] My ask right now is: I believe this idea is good to move forward on - asking for confirmation. Note: Paul

Re: [OpenOCD-devel] Cortex A/M - DAP crazyness

[quoting out of order ..] andreas>> I have thought about this a great deal over the past years and wandered quite far off from where OpenOCD is today. So my ideas are maybe not very realistic in the short term. But it hardly hurts to have a common vision before starting to take the baby steps t

Re: [OpenOCD-devel] Cortex-M3 - Issue: BKPT_TYPE_BY_ADDRESS()

duane>> [[ started this: about creating a memory range to determine breakpoints, because CortexM macro is wrong headed ]] Freddie>> [[ points out using the flash memory area … ]] duane>> [ That means the target has to be probed - cannot always probe ] duane>> [ Not all targets have a “flash driv

Re: [OpenOCD-devel] Option to hold reset for mass erase?

Hi, On Wed, May 07, 2014 at 10:26:24AM +0100, Chris Fryer wrote: > I've just run across this Kinetis issue > whereby, with brand new > parts, you have to hold them in reset and perform a mass erase before > openocd can connect to them properly.

[OpenOCD-devel] Option to hold reset for mass erase?

Hi, I've just run across this Kinetis issue whereby, with brand new parts, you have to hold them in reset and perform a mass erase before openocd can connect to them properly. I'm putting together an ATE rig around openocd (CMSIS-DAP) so would l

[OpenOCD-devel] [PATCH]: 695f44c tcl/target: added support for TI OMAP/AM 3505 and 3517

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/2127 -- gerrit commit 695f44c361b01d0f60bddb47e2f6b3dbe7500dd4 Author: Andrey Skvortsov Date: Wed May 7 12:59:21 2014