On Thu, Aug 27, 2009 at 1:35 PM, Rohit Chandel wrote:
> Please suggest any straight forward tutorial on how to use OpenOCD with old
> FTDI drivers.
>
Depending on how straight-forward is straight-forward, here is the building
instruction for OpenOCD under Windows.
http://forum.sparkfun.com/viewto
On Thu, Aug 27, 2009 at 12:45 AM, Freddie Chopin wrote:
> Rohit Chandel pisze:
> > A new window opens up after that saying "openocd.exe" has stopped
> > working and the usual option to check online for solution, close the
> > program or debug the program.
>
> >something must be seriously broken in
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 and we have fixed the root
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
On Wed, Aug 26, 2009 at 9:20 PM, David Brownell wrote:
> On Wednesday 26 August 2009, Ųyvind Harboe wrote:
>> > Does i.MX31 have one of the cores which extends Thumb
>> > with new instructions? I'm not sure they're all fully
>> > supported for use by the simulator. Worth looking at
>> > once you
Committed.
Thanks!
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
On Wednesday 26 August 2009, Øyvind Harboe wrote:
> > Does i.MX31 have one of the cores which extends Thumb
> > with new instructions? I'm not sure they're all fully
> > supported for use by the simulator. Worth looking at
> > once you have the ARM instructions behaving. :)
>
> openocd arm11 ta
Rohit Chandel pisze:
> A new window opens up after that saying "openocd.exe" has stopped
> working and the usual option to check online for solution, close the
> program or debug the program.
something must be seriously broken in that case... sorry, but I have no
idea what that could be. what O
On Wed, Aug 26, 2009 at 9:06 PM, David Brownell wrote:
> On Wednesday 26 August 2009, Ųyvind Harboe wrote:
>> > If anything, they should be *more* separate.
>> >
>> > The whole simulator bears some thought though. Is the whole
>> > point of it just to enable one type of single stepping? I
>> > do
Committed.
Thanks!
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
On Wednesday 26 August 2009, Øyvind Harboe wrote:
> > If anything, they should be *more* separate.
> >
> > The whole simulator bears some thought though. Is the whole
> > point of it just to enable one type of single stepping? I
> > don't recall seeing comments about when/why the simulator
> > wo
On Wed, Aug 26, 2009 at 5:58 PM, David Brownell wrote:
> On Wednesday 26 August 2009, Igor Skochinsky wrote:
>> As for ARM, I think arm_simulator.c and arm_disassembler.c should be
>> merged since they share a lot of functionality.
>
> They seem kind of separate to me. I can disassemble without
>
On Wed, Aug 26, 2009 at 7:36 PM, Zach Welch wrote:
> I think that these two blocks of code need to be put in a static helper
> that eliminates their duplicated functionality.
Actually, the LOG_ERROR() should be pushed up into the
failing site according to error handling rules in OpenOCD(which
are
On Wed, Aug 26, 2009 at 8:23 PM, Freddie Chopin wrote:
> Rohit Chandel pisze:
> > But the problem comes when I give "openocd" at cmd line.
> > Michael informed me that on this I should get connected to the Target
> > through OpenOCD. But I get an error message in a new window saying
> > "openocd.e
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
I think that these two blocks of code need to be put in a static helper
that eliminates their duplicated functionality.
On Wed, 2009-08-26 at 12:03 +0200, Øyvind Harboe wrote:
> If the PC is pointing to an invalid instruction, then simulation will
> fail. This is
> expected.
>
> ### Eclipse Works
Hi,
On Wed, Aug 26, 2009 at 17:58, David Brownell wrote:
> On Wednesday 26 August 2009, Igor Skochinsky wrote:
>> As for ARM, I think arm_simulator.c and arm_disassembler.c should be
>> merged since they share a lot of functionality.
>
> They seem kind of separate to me. I can disassemble without
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 for us.
Cool! Could you m
On Wednesday 26 August 2009, Igor Skochinsky wrote:
> As for ARM, I think arm_simulator.c and arm_disassembler.c should be
> merged since they share a lot of functionality.
They seem kind of separate to me. I can disassemble without
wanting to simulate. And vice versa.
If anything, they should
Fix segv in jtag_examine_chain(): exit loop on no-tap. Keep
"next iteration" step with the rest of the loop overhead.
Cleanup: remove spurious whitespace, and an overlong line;
only assign "tap->hasidcode" once.
---
src/jtag/core.c | 14 --
1 file changed, 8 insertions(+), 6 delet
Øyvind Harboe wrote:
> Add INSTALL.Win32 file?
>
That would be OK with me - for me, it is important that the information
is bundled in one place, and not separate for each distribution.
(even if I don't use OpenOCD on Windows).
cu
Michael
___
Openo
On Wed, Aug 26, 2009 at 4:50 PM, Igor Skochinsky wrote:
> On Wed, Aug 26, 2009 at 16:29, Øyvind Harboe wrote:
>> I've worked on refactoring the arm simulation code
>> to be able to support non-armv4_5 targets. The
>> approach is to define an interface that the caller
>> has to support. See below fo
Rohit Chandel pisze:
> But the problem comes when I give "openocd" at cmd line.
> Michael informed me that on this I should get connected to the Target
> through OpenOCD. But I get an error message in a new window saying
> "openocd.exe has stopped working" and the usual message whether to
> clo
On Wed, Aug 26, 2009 at 16:29, Øyvind Harboe wrote:
> I've worked on refactoring the arm simulation code
> to be able to support non-armv4_5 targets. The
> approach is to define an interface that the caller
> has to support. See below for example.
>
> Thoughts? Objections?
I think there is no need
I've worked on refactoring the arm simulation code
to be able to support non-armv4_5 targets. The
approach is to define an interface that the caller
has to support. See below for example.
Thoughts? Objections?
int arm_simulate_step(target_t *target, uint32_t *dry_run_pc)
{
armv4_5_c
Great work!
I'll commit it sooner rather than later if I don't hear any protests.
(I'm not following the Cortex A8 development or testing anything, I just
try to commit things readily to keep the Cortex A8 development moving
forward)
--
Øyvind Harboe
Embedded software and hardware consulting se
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_u32 only returned 0x0 for the registers,
Sorry I forgot to attach the files in last mail.
-- Forwarded message --
From: Rohit Chandel
Date: Wed, Aug 26, 2009 at 5:53 PM
Subject: Re: [Openocd-development] OpenOCD 0.2.0 : Olimex ARM-USB-TINY ->
unable to find driver software
To: openocd-development
I tried to use OpenOC
I tried to use OpenOCD with the very basic test setup for my board (thanks
to Michael Fischer).
Inside the SAM7S256Test folder you will find a file openocd.cfg. This
contains all the "settings" to connect
to my target(i.e. Olimex AT91SAM7s256 Board with ARM-USB-TINY(olimex)).
Yagarto toolchain is
Add INSTALL.Win32 file?
-
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
David Brownell wrote:
> On Tuesday 25 August 2009, Michael Schwingen wrote:
>
>>> Yep; though I think such "builder docs" should not be
>>> part of the "user's guide" (openocd.texi) or of the
>>> "developer's manual" (doxygen stuff).
>>>
>> Why not?
>>
>
> Because users are not norma
Any thoughts on how to solve the arm11 single stepping
support?
If the hardware does not support single stepping, then the
instruction must be emulated and a breakpoint must
be set on the next instruction.
This code has been written for arm7/9, but it
relies on the armv4_5 structure which the ARM
On Tuesday 25 August 2009, Michael Schwingen wrote:
>
> > Yep; though I think such "builder docs" should not be
> > part of the "user's guide" (openocd.texi) or of the
> > "developer's manual" (doxygen stuff).
>
> Why not?
Because users are not normally builders ... and should not be.
And even i
If the PC is pointing to an invalid instruction, then simulation will
fail. This is
expected.
### Eclipse Workspace Patch 1.0
#P openocd
Index: src/target/arm7_9_common.c
===
--- src/target/arm7_9_common.c (revision 2625)
+++ src/tar
The attached patch reduces ARM11 output noise(bogus errors & warnings)
when there is no IDCODE upon JTAG chain examine + evaluation.
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
### Eclipse Workspace Patch 1.0
#P openocd
Index: src/jtag/jtag.h
=
David Brownell wrote:
> Various updates to 0.3.0 NEWS
>
Good idea. One more from me ...
cu
Michael
Index: NEWS
===
--- NEWS (revision 2626)
+++ NEWS (working copy)
@@ -12,6 +12,7 @@
"cortex_m3 vector_catch" ... traps certain har
David Brownell wrote:
> On Tuesday 25 August 2009, Michael Schwingen wrote:
>
>> Luca Ottaviano wrote:
>>
>>> 2 - No documentation whatsoever to start using Openocd: when using a
>>> jtag interface you need to learn about libusb-win32 drivers, the
>>> difference between libusb versions (l
37 matches
Mail list logo
