On Wed, 2009-05-06 at 08:17 +0200, Øyvind Harboe wrote:
> Looks like more fun with the code below in jim.c...
>
> #if !defined(HAVE_UNISTD_H) || !defined(__GNU_LIBRARY__)
> extern char **environ;
> #endif
>
>
> ../../../openocd/src/helper/jim.c: In function `Jim_EnvCoreCommand':
> ../../
Looks like more fun with the code below in jim.c...
#if !defined(HAVE_UNISTD_H) || !defined(__GNU_LIBRARY__)
extern char **environ;
#endif
../../../openocd/src/helper/jim.c: In function `Jim_EnvCoreCommand':
../../../openocd/src/helper/jim.c:11988: warning: redundant
redeclaration of 'en
Hi Dick,
I'm sorry to hear that things turned out the way they did. I believe
that OpenOCD will be worse off without your efforts and you
have for sure left some big marks on OpenOCD in terms of
quantity and quality.
BTW, I'm struggling with applying the patches, I don't know why...
could you jus
* xsvf.patch:
This simplifies XSTATE handling, and protects against illegal state
transitions that might be in an SVF file. Previous code was vulnerable
to a bad path. They are now handled through a robust use of the
tms_seq[] table. With this patch and my xsvf_tools, I was able to work
w
Zach,
You are a quality guy and I want to go on record, with you being the
recipient, of why I am leaving the project.
>>> Yes, it could be separated. I could do it myself, but I have my own
>>> list of tasks.
If the patch was separated and only portions of it were ap
Hello List,
I had problems with the last openocd version, therefore
I decide to go back and check some older versions.
The problems with the new version was:
- could connect to str710, but if I change data with mww
only the first time I could display the data with mdw. The
second time I got only
I would like to remove in_check_mask.
There are a *few* places in the code where it is used,
but those are trivially modified.
This will result in lots of code deleted and more easily
understandable code.
--
Øyvind Harboe
Embedded software and hardware consulting services
http://consulting.zyli
I'd like to see the JTAG API tightend up a bit more.
in_handler is used in a few dozen places, but really
the code would be much clearer if this was handled
on the user side rather than inside the JTAG API.
Net this would result in a lot of deleted code and
easier to read code.
I've made some ma
I've gotten some information in email about BDM so I can
not claim credit for this analysis/research :-)
The PowerOPC BDM is not the same as the Coldfire BDM.
Some signals have the same name, but that is where the
similarities end.
The PowerPC relies of instructions serialized into the core
(DPI
Magnus Lundin wrote:
> Good observations,
>
> - The error reporting and handling for memory read/write errors is
> incomplete, this ia general problem, well know but it only occurs when
> things are broken anyway.
>
> - The cortex-a 8 code is incomplete, we know that, you have found the
> "
Hi Strontium,
Strontium wrote:
> Ok,
>
> I am trying to make the files described below. And have gotten along
> fine, but have found the following problem.
>
> The first time my script executes after a reset of the beagle:
>
> dap apsel 1
>
> openocd halts with an error, thus: (at -d 3)
>
Good observations,
- The error reporting and handling for memory read/write errors is
incomplete, this ia general problem, well know but it only occurs when
things are broken anyway.
- The cortex-a 8 code is incomplete, we know that, you have found the
"missing target_examine" function wher
Ok,
I am trying to make the files described below. And have gotten along
fine, but have found the following problem.
The first time my script executes after a reset of the beagle:
dap apsel 1
openocd halts with an error, thus: (at -d 3)
Fails:
Debug: 166 1139 arm_adi_v5.c:242 swjdp_trans
Single stepping does not work for arm1136 on the parport adapter.
Looking at ft2232 vs. bitbang, I see a big difference in how
these drivers exist the scan operation. (Hope I got this one right... :-)
The bitbang driver manually wiggles it's way to TAP_xRPAUSE,
then does a 7 clock transition to t
Removed extra line added before prompt. This is actually
fixing a regression that nobody has reacted to.
### Eclipse Workspace Patch 1.0
#P openocd
Index: src/helper/command.c
===
--- src/helper/command.c(revision 1600)
+++ sr
Hi all,
Can't enter debug state as setting cortex-a8 register of DRCR as below ,Any
idea?
> mww 0x54011090 1
setting DRCR halt request bit
> mdw 0x54011088
0x54011088 4b072002. .K
reading DSCR,but core still restarted
Best Regards,
Ray
___
Hi all,
we're trying to build up a small farm of target and interface hardware.
We're providing access to this farm to some of the OpenOCD developers
we talk to when there are issues, e.g. we're looking into ARM11
problems now.
In particular we should probably have an ft2232 in our farm.
Please
Jesus Sanchez-Palencia wrote:
> When I add a breakpoint I got the "success message" (breakpoint added
> at address 0xwhatever) but then I do a "monitor reset halt" and a
> "monitor resume". At this point I expected that I would stop at some
> breakpoint and then I could start stepping. I've adde
18 matches
Mail list logo
