Some more information on details/usage in [1]. Target use TAP for JTAG
and DAP for SWD, so we need to create union containing both inside
with common API, or initialize only one of them at time and null other
to let know which one is in use, or create null pointer and cast it
based on transport typ
On Fri, Aug 19, 2011 at 1:09 AM, Carlson Gary
wrote:
> (...)
> Debug: 35 45 command.c:151 script_debug(): command - ocd_transport
> ocd_transport select swd
> Error: 36 45 target.c:435 get_current_target(): BUG: current_target out
> of bounds
Hello Gary, did you try the openocd-libswd fork or
I have an Energy Micro EFM32 Gecko board in my hands at the moment that
provides a SWD debug interface (no JTAG). With some level of SWD support
now available in OpenOCD, I was a little curious how much effort it would
take to bridge this over to the EFM32 evaluator with its onboard jlink.
To tha
On Fri, Aug 19, 2011 at 3:17 AM, SEGGER - Support J-Link (AG)
wrote:
>
> Hi Eric,
>
> We have built a new beta version (V4.33h) which comes with a new firmware for
> J-Link
> in which the problem regarding OpenOCD has been fixed.
>
> Could you please give the new version a try and provide some fe
On Thu, Aug 18, 2011 at 4:33 PM, Øyvind Harboe wrote:
>> But if we treat each target as a thread, we will need something as
>> thread id. target_number is good for this purpose. Does keeping
>> target_number hurt?
>
> I'm not sure that the current target number scheme is suitable
> for this purpos
> But if we treat each target as a thread, we will need something as
> thread id. target_number is good for this purpose. Does keeping
> target_number hurt?
I'm not sure that the current target number scheme is suitable
for this purpose.
Perhaps retire target number from tcl usage and clean it up
On Thu, Aug 18, 2011 at 4:18 PM, Øyvind Harboe wrote:
> target_number should be retired. Patches gladly accepted.
>
> The only slight hickup is to get rid of current_target, near as I can tell.
>
> Targets are identified only by strings from tcl.
>
But if we treat each target as a thread, we will
target_number should be retired. Patches gladly accepted.
The only slight hickup is to get rid of current_target, near as I can tell.
Targets are identified only by strings from tcl.
--
Øyvind Harboe - Can Zylin Consulting help on your project?
US toll free 1-866-980-3434 / International +47 51
Hi,
I saw this
int target_number; /* DO NOT USE! field to be removed in 2010 */
in the definition of "struct target". I don't know the reason to
remove it. Maybe it's just useless? I I need a way to identify each
target. I think target_number is good for this purpose.
Regards,
Jie
On 18 August 2011 09:02, Gunnar Henne wrote:
> Hello,
>
> here is a patch to support EN29LV800BB flash devices via CFI. I have
> successfully tested ist in openocd 0.5.0 with the hardware described here:
> http://www.bettyhacks.com
>
> It was posted by telek...@gmx.de in the bettyhacks forum for o
Hello,
here is a patch to support EN29LV800BB flash devices via CFI. I have
successfully tested ist in openocd 0.5.0 with the hardware described here:
http://www.bettyhacks.com
It was posted by telek...@gmx.de in the bettyhacks forum for openocd
0.4.0 and integrated into 0.5.0 by me.
Kind regard
11 matches
Mail list logo
