On 26.12.2010 19:41, David Brownell wrote:
via Google search, I found the following, which, in conjunction with the
Cortex-A9 reference manuals from ARM, may be of interest to folk looking
at OMAP4 and other recent TI chips for OpenOCD; it looked to answer some
of the questions I've heard on this
On 04.12.2010 07:12, Austin, Alex wrote:
I imagine the problem is voltage, actually. The OMAP3530 and other similar
devices run their JTAG ports at 1.8V, and the ARM-USB-OCD doesn't like working
below 3V.
Therefore the Flyswatter
http://www.tincantools.com/product.php?productid=16134&cat=0&p
Hi Anton,
On 03.04.2010 09:16, Øyvind Harboe wrote:
Hi Anton,
I can't look until after easter, but it is great to see some work
done in this area!
Yes, great! :)
Hopefully you'll get some good feedback before then and it will
be ready to merge soon, so we can get it tested more widely!
It
On 02.04.2010 01:01, Maximilian Odendahl wrote:
It is still related to OMAP though, and I guess I'll might need JTAG as
well, so I'll at least get the wiki up to date once I'm at that point.
I just tried recent version of OpenOCD with Beagle (OMAP3).
Using recent git
Open On-Chip Debugger 0.5
On 17.12.2009 19:39, David Brownell wrote:
> On Thursday 17 December 2009, Dirk Behme wrote:
>
>> Ok, after board reset I get
>>
>> -- cut --
>> > scan_chain
>> TapName Enabled I
Thomas Kindler wrote:
> Hi!
>
> Now that the reset problem is solved for me, I'm trying to optimize my
> eclipse setup for my STM32 target.
>
> Basically, I'm using gnuarmeclipse.sf.net for project settings and
> makefile generation, CodeSourcery Lite as the toolchain, and the
> "Eclipse C/C++
Piet Delaney wrote:
> Dirk Behme wrote:
>> Piet Delaney wrote:
>>> Dirk Behme wrote:
>>>> David Brownell wrote:
>>>>> On Friday 21 August 2009, Dirk Behme wrote:
>>>>>> While reading in the git thread the keyword "branch":
Piet Delaney wrote:
> Dirk Behme wrote:
>> David Brownell wrote:
>>> On Friday 21 August 2009, Dirk Behme wrote:
>>>> While reading in the git thread the keyword "branch":
>>>>
>>>> What's about a "beagle-testing" or
Dean Glazeski wrote:
> Hi list,
>
> I've been sort of bothered by the lack of a GUI for OpenOCD. I've seen this
> project: http://openocd-gui.sourceforge.net/, but I'm not entirely certain
> if I like their direction. My main concern is the lack of activity and the
> goal of using C++ or TCL/Tk.
Øyvind Harboe wrote:
> "Migrate away from Berlios" committe wants an alternative
> to Berlios mailing lists.
>
> Some alternatives so far:
>
> - Set up seperate openocd.org server => not going to happen. We
> don't have the resources and dedication to run it.
> - sourceforge mailing lists apparen
Øyvind Harboe wrote:
>> My vote is for a server that supports http for read-only access :-)
>
> We need and want a git mirror. That git mirror will support http.
>
> We haven't decided which mirror yet though.
Thanks for testing to Rolf!
At least we now know that for http://gitorious.org and
h
Øyvind Harboe wrote:
> Zach, David and I as maintainers constitute the committee
> to move OpenOCD to sourceforge and make some choices
> about how things will be moved on behalf of the community.
>
> We want input from the community, but we also need a bit
> of leadership to execute the steps.
>
David Brownell wrote:
...
>> Has anyone solved the problem of git access from behind a
>> strict HTTP proxy?
...
> Lacking that, we might want a git mirror at a site which
> does have easier HTTP access.
Rolf, could you try if
git clone http://git.gitorious.org/u-boot-omap3/mainline.git
works fo
Øyvind Harboe wrote:
>> I'm not sure if we really want SourceForge, though. Especially for mailing
>> lists. U-Boot moved away from it because of pain:
>>
>> http://lists.denx.de/pipermail/u-boot/2008-August/038001.html
>>
>> (not mentioned there: Spam handling)
>
> What other free viable options
David Brownell wrote:
> On Monday 05 October 2009, Dirk Behme wrote:
>> What's about staying with all we have at Berlios (mailing list, home
>> page etc) and just switching the source code to git, e.g. at gitorious?
>
> We already have a GIT tree at SourceForge, it
Øyvind Harboe wrote:
> Berlios has been down for several days.
>
> There has previously been some talk about switching to git
> as a source control for all sorts of other reasons, but there
> never was a reason to do the work.
>
> While we are thankful for the hosting service Berlios has provided
Matt Hsu wrote:
>> On my BeagleBoard I can now do "reset halt" and end up somwhere
> Hi Magnus,
>
> Nice work!
> It seems that all the low-level logic for A8 are ready for debugging.
> The reset is get gdb hook up with openOCD.
What's about applying this and
https://lists.berlio
Magnus Lundin wrote:
David Brownell wrote:
I think that's not quite following the model which the code in
the src/helper/startup.tcl file is expecting ... a closer match
would use reset-assert-pre (or maybe "post") not reset-start.
I have done some more testing and trying to understand the re
Øyvind Harboe wrote:
> Remove these, they probably *slow down* if anything...
>
> # Increase the packet size to improve download speed.
> set remote memory-write-packet-size 1024
> set remote memory-write-packet-size fixed
Thanks for the hint, done:
http://elinux.org/BeagleBoardOpenOCD#LED_blink
Magnus Lundin wrote:
We can, and sometimes we want to, write to memory while the CortexA8
core is running,
but for gbd to load a program and the i-caches to be cleared to core
must be halted.
Yes, thanks!
Attachment now gives me:
-- cut --
> arm-none-linux-gnueabi-gdb
GNU gdb 6.8
Copyright
Magnus Lundin wrote:
>
>>> At the end of the reset handling we reinitialise the tap and the
>>> debug interface with omap3_dbginit
>>> omap3_reset is really reset+reinit+halt and you call it if you want
>>> to debug the loading of u-boot by the X-Loader
>>
>> Do you mean omap3_reset shou
Magnus Lundin wrote:
> Well, some days our work is a bit more confused then other days.
>
> Dirk Behme wrote:
>> Magnus Lundin wrote:
>>> For testing and comments:
>>>
>>> Uses the OMAP3530 global software reset and defines corresponding
&g
Magnus Lundin wrote:
Dirk Behme wrote:
David Brownell wrote:
Update the DaVinci target configs so they have JTAG post-reset
event handlers which:
- run the 100 JTAG clocks ICEpick wants
- ensure the ARM (and ETB) taps are enabled
---
The OMAP3 post-reset handlers should probably do
David Brownell wrote:
> Update the DaVinci target configs so they have JTAG post-reset
> event handlers which:
>
> - run the 100 JTAG clocks ICEpick wants
> - ensure the ARM (and ETB) taps are enabled
> ---
> The OMAP3 post-reset handlers should probably do something
> similar, doing the (update
David Brownell wrote:
> Reorder the two JTAG reset events (C/internal, Tcl/external) so
> they can be used properly to enable TAPs with ICEpick. Make them
> kick in the same way on *both* paths (TCK/TMS or TRST).
>
> Tweak TCL reset script ... mostly improving comments about what
> the steps do,
functional changes.
Tested-by: Dirk Behme
Used LEDblink test code for this.
Best regards
Dirk
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
opap3_dbginit
has setup all core registers correctly.
Signed-off-by: Magnus Lundin
Tested-by: Dirk Behme
---
tcl/target/omap3530.cfg |2 ++
1 file changed, 2 insertions(+)
Index: trunk/tcl/target/omap3530.cfg
===
--- trunk.orig/tcl
Magnus Lundin wrote:
> For testing and comments.
This makes software breakpoints in LEDBlink work:
-- cut --
(gdb) b main
Breakpoint 1 at 0x823c: file LEDblink.c, line 22.
(gdb) cont
Continuing.
Breakpoint 1, main () at LEDblink.c:22
22 LEDbrightness++;
Current language:
Behme
Add documention for new post reset event.
Signed-off-by: Dirk Behme
---
doc/openocd.texi | 17 +
1 file changed, 13 insertions(+), 4 deletions(-)
Index: trunk/doc/openocd.texi
===
--- trunk.orig/doc
Øyvind Harboe wrote:
Take #3...
I committed a fix for a bug where running jtag configure twice would
cause an infinite loop upon event nofitication, but it still bothers me that
jtag configure was invoked twice...
Seems to work for me (configuration patch in attachment):
> openocd -s lib/open
ould
> go first.
Acked-by: Dirk Behme
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Matt Hsu wrote:
> Magnus Lundin wrote:
>> Hello list.
>>
>> For those of you who has not yet had the time to read all the TRM's
>> covering Cortex-A8 and ARM ADIv5, I have started to write up an easy
>> introduction to the debug components in a Cortex-A8 system.
>>
> It's great. The first
David Brownell wrote:
> On Saturday 05 September 2009, David Brownell wrote:
>> ... see the appended patch, which
>> is yours plus (a) "quilt" removed spurious end-of-line
>> whitespace, and (b) the icepic.cfg update is there
>
> Doesn't behave quite right ...
I got
...
RCLK - adaptive
extra clo
Holger Freyther wrote:
> On Friday 04 September 2009 21:39:08 Øyvind Harboe wrote:
>>> Shouldn't it do that when TRST is released instead of when
>>> it's asserted?
>> Fixed in take #2.
>>
>> Testing anyone?
>
> Yes, can you tell me how the expected result looks like?
It's my understanding that O
David Brownell wrote:
> On Saturday 05 September 2009, Øyvind Harboe wrote:
>> Add "jtag_extra_clocks 100" to your config file
>
> to icepick.cfg in fact ... see the appended patch, which
> is yours plus (a) "quilt" removed spurious end-of-line
> whitespace, and (b) the icepic.cfg update is there
Øyvind Harboe wrote:
> Before I commit the change, could you also test a non-beagleboard
> target for regressions?
Unfortunately, I have only BeagleBoard where I can attach Flyswatter :(
Anybody else?
> I won't be able to run tests until next week, but I can test that
> it builds + commit the ch
Øyvind Harboe wrote:
On Sat, Sep 5, 2009 at 9:32 AM, Dirk Behme wrote:
Øyvind Harboe wrote:
Did you specify the extraclocks via the command?
Uuups ;) Where should I put the extraclocks command with witch exact
syntax?
Add "jtag_extra_clocks 100" to your config file
Ahh :)
Øyvind Harboe wrote:
> Did you specify the extraclocks via the command?
Uuups ;) Where should I put the extraclocks command with witch exact
syntax?
> Take #3 of this patch should probably define a post-tap-reset
> event where beagleboard config file could do whatever it
> needed...
This would
Øyvind Harboe wrote:
>> Shouldn't it do that when TRST is released instead of when
>> it's asserted?
>
> Fixed in take #2.
>
> Testing anyone?
>
> a) the patch should do no harm to other targets
> b) it should fix the extraclocks problem with Beagleboard...
Hmm, I'm not really happy with this p
Magnus Lundin wrote:
> Hello all Cortex_A8 fans !
>
> Please test the following patch that hopefully corrects some insane
> errors in Thumb state handling.
> (Yes I wrote it myself, but it seems UBoot for BeagleBoard does not use
> Thumb Mode)
I have this patch applied since some time, and it d
Matt Hsu wrote:
>The following is my log of setting up a breakpoint:
>
> Telnet session
Did you already try to attach and control all this with gdb? Or
anybody else?
Best regards
Dirk
___
Openocd-development mailing list
Openocd-development@lists
Use jtag_rclk instead of jtag_speed. This fixes message
OLD SYNTAX: DEPRECATED - use jtag_khz, not jtag_speed
for BeagleBoard.
Subject: [PATCH v3] Use jtag_rclk instead of jtag_speed for BeagleBoard
From: Dirk Behme
Use jtag_rclk instead of jtag_speed. This fixes message
OLD SYNTAX
Jonas Horberg wrote:
> Dirk Behme wrote on 2009-09-03 20:17:39:
>
>> David Brownell wrote:
>>> On Monday 31 August 2009, Dirk Behme wrote:
>>>> David Brownell wrote:
>>>>> On Monday 31 August 2009, Dirk Behme wrote:
>>>>>>
Matt Hsu wrote:
>>> Also, the programming breakpoints works as well.
>>
>> Could you give some examples how you use this? Giving some logs of how
>> you are testing would help other to reproduce this ;)
>The following is my log of setting up a breakpoint:
Thanks, this helps a lot!
Tried it a
Hi Magnus!
Magnus Lundin wrote:
> Hello all Cortex_A8 fans !
>
> Please test the following patch that hopefully corrects some insane
> errors in Thumb state handling.
> (Yes I wrote it myself, but it seems UBoot for BeagleBoard does not use
> Thumb Mode)
Same as already mentioned with Matt's p
Matt Hsu wrote:
> David Brownell wrote:
>> Re #1 and #3: I'd combine the "add #defines" and "use #defines"
>> into one patch myself... minor point.
>>
> Hi David,
>It sounds fine to me and makes the description clear.
>I will make v2 patches and submit later.
Please note th
David Brownell wrote:
> On Monday 31 August 2009, Dirk Behme wrote:
>> David Brownell wrote:
>>> On Monday 31 August 2009, Dirk Behme wrote:
>>>> +jtag_rclk
>>>> +
>>> needs digits ..
>> Hmm, really? Then, jtag_rclk seems to be broken:
:
Tested-by: Dirk Behme
Please apply.
> Also, the programming breakpoints works as well.
Could you give some examples how you use this? Giving some logs of how
you are testing would help other to reproduce this ;)
Many thanks
Dirk
___
Openocd-deve
Øyvind, Dave,
Øyvind Harboe wrote:
> On Tue, Aug 25, 2009 at 4:33 PM, Dirk Behme wrote:
>> Øyvind Harboe wrote:
>>> I have committed all but 01_openocd_beagle.patch to hopefully get things
>>> moving along
>>>
>>> 01_openocd_beagle.patch is problem
David Brownell wrote:
> On Monday 31 August 2009, Dirk Behme wrote:
>> +jtag_rclk
>> +
>
> needs digits ..
Hmm, really? Then, jtag_rclk seems to be broken:
jtag_rclk:
-- cut --
RCLK - adaptive
...
Info : clock speed 6000 kHz
-- cut --
jtag_rclk 3000:
-- cut --
RCL
Use jtag_rclk instead of jtag_speed. This fixes message
OLD SYNTAX: DEPRECATED - use jtag_khz, not jtag_speed
for BeagleBoard.
Subject: [PATCH v2] Use jtag_rclk instead of jtag_speed for BeagleBoard
From: Dirk Behme
Use jtag_rclk instead of jtag_speed. This fixes message
OLD SYNTAX
David Brownell wrote:
> On Sunday 30 August 2009, Dirk Behme wrote:
>> --- trunk_r2643.orig/tcl/interface/flyswatter.cfg
>> +++ trunk_r2643/tcl/interface/flyswatter.cfg
>> @@ -8,5 +8,5 @@ interface ft2232
>> ft2232_device_desc "Flyswatter"
>> ft2232_la
Fix typo in help text. It has to be 'production_test' instead of
'production' here.
Signed-off-by: Dirk Behme
Fix typo in help text. It has to be 'production_test' instead of
'production'.
Signed-off-by: Dirk Behme
---
src/helper/startup.tcl |
Use jtag_khz instead of jtag_speed. This fixes message
OLD SYNTAX: DEPRECATED - use jtag_khz, not jtag_speed
while using Flyswatter with BeagleBoard.
3000kHz is the default speed choosen if jtag_speed 1 was used.
Signed-off-by: Dirk Behme
Use jtag_khz instead of jtag_speed. This fixes
Dirk Behme wrote:
> ... the further steps could be:
> - Update eLinux OpenOCD Beagle page
I have updated
http://elinux.org/BeagleBoardOpenOCD
a little. Please add or correct anything I missed ;)
Best regards
Dirk
___
Openocd-development m
Holger Freyther wrote:
> On Thursday 27 August 2009 07:04:22 Dirk Behme wrote:
>> Holger Freyther wrote:
>>> Hey,
>>>
>>> today Matt Hsu and me sat together to look into why OpenOCD does not work
>>> on the beagle board. We have found and fixed some iss
Holger Freyther wrote:
> On Thursday 27 August 2009 07:04:22 you wrote:
>> Holger Freyther wrote:
>>> Hey,
>>>
>>> today Matt Hsu and me sat together to look into why OpenOCD does not work
>>> on the beagle board. We have found and fixed some issues with the code,
>>> it should make it more robust
Holger Freyther wrote:
> Hey,
>
> today Matt Hsu and me sat together to look into why OpenOCD does not work on
> the beagle board. We have found and fixed some issues with the code, it
> should
> make it more robust and we have fixed the root cause for us.
>
> cortex_a8_dap_read_coreregister_u
David Brownell wrote:
> On Wednesday 26 August 2009, Holger Freyther wrote:
>> today Matt Hsu and me sat together to look into why OpenOCD does not work on
>> the beagle board. We have found and fixed some issues with the code, it
>> should
>> make it more robust and we have fixed the root cause
David Brownell wrote:
> On Tuesday 25 August 2009, Magnus Lundin wrote:
>> * Eclipse must be installed with correct scripts and addons to relibly
>> make gdb talk to OpenOCD
>
> I'd like to see a writeup of what's involved with
> that for current Eclipse versions become part of
> the User's Guide
David Brownell wrote:
> On Friday 21 August 2009, Dirk Behme wrote:
>> While reading in the git thread the keyword "branch":
>>
>> What's about a "beagle-testing" or similar branch with the patches
>> mentioned above?
>
> Feel fre
Øyvind Harboe wrote:
> I have committed all but 01_openocd_beagle.patch to hopefully get things
> moving along
>
> 01_openocd_beagle.patch is problematic because it modifies the behavior
> for *all* targets.
>
> Thoughts?
You might have noticed that I'm not really an expert of OpenOCD's code
Let's try to organize this a little and summarize the status:
1. Last time I tried was *r2604*:
https://lists.berlios.de/pipermail/openocd-development/2009-August/010035.html
To reproduce this, you have to apply the four patches in attachment of
that mail to r2604.
Fred and Matt: Please try
Øyvind Harboe wrote:
> Should these patches be committed as-is?
From user point of view, I would say yes. Additional fixes/clean up
can go on top of these, then.
But we should let Dave decide, as all patches are from him or at least
cleaned up by him.
Best regards
Dirk
___
Øyvind Harboe wrote:
> What is the status on Beagleboard?
https://lists.berlios.de/pipermail/openocd-development/2009-August/010035.html
> It would be nice to have some solid progress on that long standing
> item
Yes!
I'd vote to apply the four patches mentioned in the link above.
While we
David Brownell wrote:
> On Wednesday 19 August 2009, James Lin wrote:
>
>> Then I tried to apply the patch described in
>>
>> http://lists.berlios.de/pipermail/openocd-development/2009-June/008256.html
>>
>> I don't know if this additional step was necessary but it seemed
>> to get correct mfg, p
Magnus Lundin wrote:
> Hi list,
>
> I know there is a lot of fixing to get a stable 0.2.0 so this is
> clearly for next release.
> But I also know that some folks wants to get going with CortexA8, so
> here it comes.
Great! Many thanks!
Dave, Sergey: This does look like a really *good* starti
Sergey Lapin wrote:
> Hi, all!
>
> Is there any news regarding support of BeagleBoard in OpenOCD?
> Last time I checked, there was none, I'm interested to help, so I
> want to know the status and what can I do.
Recent status of trunk (at least the last time I checked):
https://lists.berlios.de/p
David Brownell wrote:
> On Friday 19 June 2009, Dirk Behme wrote:
>> Seems to work :) THANKS!!
>
> Good. I look forward to seeing more things start to work
> there ... and the next release after 0.2.0 having some
> support for Cortex-A8! :)
Don't hesitate to send
David Brownell wrote:
Update the Beagle setup:
- OMAP3530 updates:
* split ICEpick TAP enable support to its own file, for
reuse and eventually for storing other utility code
like emulation reset
* clean up, including labeling the tap as for DAP not
for the Cortex-A8 a
David Brownell wrote:
> Update the Beagle setup:
>
> - OMAP3530 updates:
> * split ICEpick TAP enable support to its own file, for
> reuse and eventually for storing other utility code
> like emulation reset
> * clean up, including labeling the tap as for DAP not
> for t
Øyvind Harboe wrote:
> On Wed, Jun 10, 2009 at 5:30 PM, Dirk Behme wrote:
>> Ųyvind Harboe wrote:
>>> Committed.
>>>
>>> Does OMAP/BeagleBoard need this?
>>>
>>> This "pathmove" command is ready for testing & feedback.
>>
Øyvind Harboe wrote:
> Committed.
>
> Does OMAP/BeagleBoard need this?
>
> This "pathmove" command is ready for testing & feedback.
If someone with more OpenOCD and recent changes knowledge than me
likes to convert
http://svn.berlios.de/svnroot/repos/openocd/trunk/tcl/board/ti_beagleboard.cfg
Øyvind Harboe wrote:
>> Which information do you need to get an idea what the beagle script is
>> expected to do?
>
> I can't dive into the OMAP stuff with the time I have for OpenOCD,
While this is fine (it's not different with me, else I would help more
;) ), I think we could try to improve de
Øyvind Harboe wrote:
> Committed.
> Retired endstate(and updated docs). Background polling would
> overwrite any changes to the endstate. From the command
> line point of with the recent changes to ir/drscan the "endstate" command
> wasn't used anyway.
>
> The best I can do for the beagleboard con
Zach Welch wrote:
> On Fri, 2009-05-22 at 10:57 +0200, Øyvind Harboe wrote:
>> Trying again...
>>
>> My editor is screwing things up with whitespace, hence all those irrelevant
>> changes...
>
> The second attempt was no better. Here it is done right.
First, thanks for helping with this patch!
Øyvind Harboe wrote:
> I'm going to be out of the office for the next week, so I'm turning into
> a pumpkin RSN.
>
> omap3_dbginit should be made part of the reset sequence.
>
> OpenOCD supports hot-plugging of targets. Feel free to scream, but this
> is something that developers do since it save
Øyvind Harboe wrote:
> Looking at your configuration scripts, they should *not* call init
> once they are implemented correctly.
Do you like to give any hints how to implement them correctly and what
do you think is wrong with them?
We talk about
http://svn.berlios.de/svnroot/repos/openocd/trun
Øyvind Harboe wrote:
> This assert happens because a drscan is executed on a disabled TAP.
> i.e. it is not in OpenOCD's list of enabled TAP's, the physical device
> might very well be enabled.
>
> How would you like OpenOCD to tell you this?
Øyvind: I'm not sure if this question is for me or Mic
Michael Bruck wrote:
> On Thu, May 21, 2009 at 1:39 PM, Dirk Behme wrote:
>> Michael Bruck wrote:
>>> Dirk, did this happen when you used the drscan/irscan commands?
>> Not sure, but possible. Have a look to tap-enable event of
>>
>> http://svn.berlios.de/sv
9 at 8:15 AM, Rick Altherr wrote:
>> On May 20, 2009, at 11:03 PM, Dirk Behme wrote:
>>
>>> Just want to let you know that with recent svn head r1870 I get
>>>
>>> trying to validate configured JTAG chain anyway...
>>> openocd: jtag.c:889: interfac
to Magnus for all the help!
Signed-off-by: Dirk Behme
---
src/target/board/ti_beagleboard.cfg |3 +++
src/target/target/omap3530.cfg | 17 +
2 files changed, 20 insertions(+)
Index: trunk/src/target/board/ti_beagleboard.cfg
Just want to let you know that with recent svn head r1870 I get
trying to validate configured JTAG chain anyway...
openocd: jtag.c:889: interface_jtag_add_dr_scan: Assertion `field ==
out_fields + scan->num_fields' failed.
while at least r1865 seems to work. Found while playing with OMAP3
scri
Øyvind Harboe wrote:
> On Mon, May 18, 2009 at 7:55 PM, Dirk Behme wrote:
>> Ųyvind Harboe wrote:
>>> You can't use "target create" on the telnet command line
>>> because it is after "init". If "init" is not on the command
>>&
Øyvind Harboe wrote:
> You can't use "target create" on the telnet command line
> because it is after "init". If "init" is not on the command
> line, OpenOCD runs it before launching the telnet
> server.
Ah, that explains a lot! ;) Will try it.
Thanks
Dirk
_
Øyvind Harboe wrote:
> You have to create the target before the init command.
>
> One could talk about allowing targets to be created/deleted
> on the fly, but OpenOCD isn't at that stage today.
>
>
> This works:
>
> openocd -s lib/openocd/ -f interface/dummy.cfg -f target/omap3530.cfg
> -c "ta
Øyvind Harboe wrote:
>> So this *does* work :)
>>
>> Looks like a Cortex configuration/environment issue then.
>
> Strange indeed.
>
> Can you reproduce it w/your target and the dummy driver?
openocd -s lib/openocd/ -f interface/dummy.cfg -f board/ti_beagleboard.cfg
> version
Open On-Chip Debu
Øyvind Harboe wrote:
> On Sun, May 17, 2009 at 8:02 PM, Dirk Behme wrote:
>> Ųyvind Harboe wrote:
>>> Strange indeed. Parsing works here...
>> Yes, I believe this ;)
>>
>> The big question is what might be different for me.
>>
>> From your last ma
Øyvind Harboe wrote:
> Strange indeed. Parsing works here...
Yes, I believe this ;)
The big question is what might be different for me.
From your last mail, you use 'at91eb40a' CPU configuration? Maybe the
init scripts for this do some magic which is missing for me? What
scripts do you source
Øyvind Harboe wrote:
>> -- cut --
>> > version
>> Open On-Chip Debugger 0.2.0-in-development (2009-05-17-07:51) svn:1800
>> > omap3.cpu mem2array dataval 32 [expr "0x54011000 + 0 * 4"] 1
>> > ocd_mem2array dataval 32 [expr "0x54011000 + 0 * 4"] 1
>> invalid command name "ocd_mem2array_dataval"
>
Zach Welch wrote:
> On Sun, 2009-05-10 at 22:31 +0200, Magnus Lundin wrote:
>>> So some progress, but nothing more ;)
>>>
>>> (all: Above error is from TCL script containing "ocd_mem2array
>>> romtable_cid 32 [expr ($debugbase&0xF000) + 0xFF0] 4")
>>>
>>> Do you have any special patches or do
Strontium wrote:
> Magnus Lundin wrote:
>> Magnus Lundin wrote:
>>
>>> When I do this for the Beagle i just use
>>>
>>> # set the current target, should not be nexessary with only one target
>>> configured
>>> targets omap3.cpu
>>> # call tcl functions without the extra target name
>>> mem2arr
Øyvind Harboe wrote:
> Please test this patch to see if it fixes mem2array/array2mem.
This seems to fix Strontium's issue.
Unpatched r1800 gives me:
-- cut --
> version
Open On-Chip Debugger 0.2.0-in-development (2009-05-17-07:51) svn:1800
> omap3.cpu mem2array dataval 32 [expr "0x54011000 + 0
Rick Altherr wrote:
>
> On May 10, 2009, at 11:43 PM, Laurent Gauch wrote:
>
>> Hi all BeagleBoard + OpenOCD users,
>>
>> What is the setup for Emu0 Emu1 pin :
>> - need both left open
>> - need both EMU0 EMU1 pull-down resistors
>> - need EMU0 pull-down resistors ...
...
> My recollection of thi
Magnus Lundin wrote:
> Dirk Behme wrote:
>> Magnus Lundin wrote:
>>> Hi
>>> Rev 1547, Added two commands that just returns values in hex, good for
>>> scripting.
>>>
>>> >dap baseaddr
>>> >dap apid
>>>
>>&
Magnus Lundin wrote:
> Hi
> Rev 1547, Added two commands that just returns values in hex, good for
> scripting.
>
> >dap baseaddr
> >dap apid
>
> Next I started playing with Tcl scripts that scans the ROM table and
> installed components. This is my first shot at JimTcl in OpenOCD but it
>
first time it is called.
any ideas?
Attached are my config script and tcl script for reference
Strontium
Magnus Lundin wrote:
Dirk Behme wrote:
Btw.: Is there an option or a possibility to run a script when I
connect e.g. by telnet?
I'm a little tired to always type the commands
jt
Magnus Lundin wrote:
> tangray wrote:
>> Hi all,
>>
>> I could not enter debug state when I set DRCR[0] to "b1", And I get the
>> DSCR[1:0] value is "b10"
>> any idea?
>>
>>
>> DRCR:Debug Run Control Register
>>
>> DSCR:Debug Status and Control Register
>>
>> these registers is on page 12.4.12 of
c:108 script_command(): script_command -
>> apsel, argv[0]=ocd_dap_apsel
>> Debug: 179 2143 command.c:108 script_command(): script_command -
>> apsel, argv[1]=1
>> User : 180 2150 command.c:383 command_print(): ap 1 selected,
>> identification register 0x04770002
>&
n (always?) fails, too. I then simply did it a
second time and didn't care about it :( Hopefully with your good
description one of the experts will have an idea ;)
> Attached are my config script and tcl script for reference
Great, thanks! I will test them if I have some minutes.
Best
1 - 100 of 182 matches
Mail list logo
