Hey all,
This is a patch that adds some function block Doxygen comments for a
number of the functions in arm7_9_command.c. I'm trying to keep the
patches small so that those who know the functions well don't have a lot
to read all of the time. Besides, I have to learn what the functions do
Committed.
I've updated the copyright notice so that it is clear that Michael Bruck
is the first author(even if the copyright is held by someone else).
Let me know if it needs updating.
--
Øyvind Harboe
Embedded software and hardware consulting services
http://consulting.zylin.com
Committed in 1809
I missed the bugfix/typo until I reviewed your code :-)
Thanks!
--
Øyvind Harboe
Embedded software and hardware consulting services
http://consulting.zylin.com
___
Openocd-development mailing list
On Mon, May 18, 2009 at 6:36 AM, Rick Altherr kc8...@kc8apf.net wrote:
On May 17, 2009, at 9:03 PM, David Brownell wrote:
On Friday 15 May 2009, Øyvind Harboe wrote:
So apply this patch?
Can anyone test?
jtagpatch.txt
It failed for me on an ft2232 device.
Hmm. It looks like the
What could be going on is that the verify algorithm, which
runs on the target, crashed somehow.
Here is essentially what verify does:
1. uploads a small application to the target
2. this app runs a crc on the flash
3. OpenOCD checks that the crc is correct
Try a reset init before you run
-Oorspronkelijk bericht-
Van: openocd-development-boun...@lists.berlios.de
[mailto:openocd-development-boun...@lists.berlios.de] Namens Strontium
Verzonden: maandag 18 mei 2009 4:06
Aan: Xiaofan Chen
CC: openocd-development@lists.berlios.de
Onderwerp: Re: [Openocd-development]
On Mon, May 18, 2009 at 6:51 AM, Rick Altherr kc8...@kc8apf.net wrote:
On May 17, 2009, at 2:40 PM, Michael Bruck wrote:
- remove stale interdepencies between arm11 and arm7_9_common
- added comments
- fixed some indentation
Michael
On Mon, May 18, 2009 at 10:56 AM, Øyvind Harboe oyvind.har...@zylin.com wrote:
I agree. I'll get to reviewing the patches in depth tonight and hopefully
get them committed.
It would be great to have Magnus Lundin's changes committed too, just
to keep things in sync...
Which ones do you
On Mon, May 18, 2009 at 11:12 AM, Michael Bruck mbr...@digenius.de wrote:
On Mon, May 18, 2009 at 10:56 AM, Øyvind Harboe oyvind.har...@zylin.com
wrote:
I agree. I'll get to reviewing the patches in depth tonight and hopefully
get them committed.
It would be great to have Magnus Lundin's
Hello All:
Thanks a lot for the prompt answers, unlike this e-mail. I've been off from
the office since my post, so sorry for it.
I now notice I failed to provide sufficient details about the issue at
discussion. The flash uses is a 16bit data width, but it is connected using
just 8 bit
On Mon, May 18, 2009 at 11:25 AM, Øyvind Harboe oyvind.har...@zylin.com wrote:
On Mon, May 18, 2009 at 11:12 AM, Michael Bruck mbr...@digenius.de wrote:
On Mon, May 18, 2009 at 10:56 AM, Øyvind Harboe oyvind.har...@zylin.com
wrote:
I agree. I'll get to reviewing the patches in depth tonight
Do we have a time frame for that? Can't Magnus split these changes up
into small independent pieces and commit them to the trunk regularly?
This way he can update his working tree from the trunk and get my and
other's commits without everybody's work stalling until he has
finished the whole
On Mon, May 18, 2009 at 1:24 PM, Øyvind Harboe oyvind.har...@zylin.com wrote:
Do we have a time frame for that? Can't Magnus split these changes up
into small independent pieces and commit them to the trunk regularly?
This way he can update his working tree from the trunk and get my and
Then why not just copy the current trunk to something like
branches/merge-ftd2232-vs-r1809 and then commit the change there so
that it can be tested?
It's even easier than that :-)
jtag.c needs a few tweaks and a bit of testing and it can be committed
first without further ado. It just needs
If you post patches and vouch for them, then I, or another committer
who beats me to it, will commit them promptly.
Currently the problem is that there are patches posted, but nobody
has time to say anything as to whether they are ready for testing.
I think it would be *greatly* helpful if we
Xiaofan Chen wrote:
2008/12/25 Michel Catudal michelcatu...@gmail.com:
I could not get my older black j-link devices to work while the newer yellow
one works. I am curious as to what the basic difference would be between
the two. I tested them at work and they were working just as good on
On Mon, May 18, 2009 at 3:28 PM, Øyvind Harboe oyvind.har...@zylin.com wrote:
If you post patches and vouch for them, then I, or another committer
who beats me to it, will commit them promptly.
Currently the problem is that there are patches posted, but nobody
has time to say anything as to
I broke it down as small as possible. The change is trivial. I tested
it here as far as possible. I can't test *all* of the functions as my
target doesn't use them, but again, the rewrite is absolutely trivial.
Did Rick want something *else* or something *more*?
If he wanted something *more*
Committed.
Remove unecessary(and poptentially harmful?) around arguments
passed in to eval in command.c
### Eclipse Workspace Patch 1.0
#P openocd
Index: src/helper/command.c
===
--- src/helper/command.c(revision 1806)
On Mon, May 18, 2009 at 3:53 PM, Øyvind Harboe oyvind.har...@zylin.com wrote:
I broke it down as small as possible. The change is trivial. I tested
it here as far as possible. I can't test *all* of the functions as my
target doesn't use them, but again, the rewrite is absolutely trivial.
Did
On Mon, May 18, 2009 at 9:37 PM, Gene Smith g...@chartertn.net wrote:
I can't answer your questions but can only add another jlink question. I
know very little about the jlink. I have a yellow jlink that says jlink
ks, IAR Systems on the front (ks = kickstart?). On the back it says
On Mon, May 18, 2009 at 10:18 PM, Xiaofan Chen xiaof...@gmail.com wrote:
mc...@ubuntu904:~/Desktop/build/openocd/jlinknew$ openocd -f
openocd_lpc2148.cfg
Open On-Chip Debugger 0.2.0-in-development (2009-05-18-19:51) svn:1809
BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS
More tests on flash writing. I got the script from psas. Maybe it is too
old (for V1257). I will try later with new scripts.
http://www.linuxjournal.com/article/10421
With black J-link
script oocd_flash_lpc2148.script
J-Link command 0xdd failed (-2)
J-Link command 0xde failed (-2)
J-Link command
On Mon, May 18, 2009 at 3:36 PM, Nico Coesel ncoe...@dealogic.nl wrote:
Gentlemen,
AFAIK EJTAG is already implemented in OpenOCD (I'm using it for another
MIPS based SOC to program external flash). I just don't know how
complete it is in respect to debugging/single stepping. The flash
Xiaofan Chen wrote:
On Mon, May 18, 2009 at 9:37 PM, Gene Smith g...@chartertn.net wrote:
I can't answer your questions but can only add another jlink question. I
know very little about the jlink. I have a yellow jlink that says jlink
ks, IAR Systems on the front (ks = kickstart?). On the back
On May 17, 2009, at 1:51 AM, Michael Bruck wrote:
The code in jtag.c currently manipulates the command queue pointers
directly in every function. This increases potential for errors and
makes the code less readable by distracting the reader from the core
algorithm contained in every function.
Ø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 target
I merged in the updated version of Dick's changes as 4 separate patches:
- r1812 updates the state table but does not enable the short table
- r1825 has the FT2232 fixes for supporting the short table
- r1826 has the JLink fixes for supporting the short table
- r1827 enables the short table if
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.
--
Øyvind Harboe
Embedded software and hardware consulting services
http://consulting.zylin.com
Ø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
Raúl Sánchez Siles wrote:
Hello All:
Thanks a lot for the prompt answers, unlike this e-mail. I've been off from
the office since my post, so sorry for it.
I now notice I failed to provide sufficient details about the issue at
discussion. The flash uses is a 16bit data width, but it
On Mon, May 18, 2009 at 7:55 PM, Dirk Behme dirk.be...@googlemail.com 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
line, OpenOCD runs it before launching the telnet
server.
Ah, that explains a
Øyvind Harboe wrote:
On Mon, May 18, 2009 at 7:55 PM, Dirk Behme dirk.be...@googlemail.com 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
line, OpenOCD runs it before launching the telnet
server.
On Mon, 18 May 2009, Øyvind Harboe wrote:
[Oops - failed to copy the original to the list...]
On Mon, May 18, 2009 at 8:21 AM, Peter Denison open...@marshadder.org wrote:
On Sat, 16 May 2009, Øyvind Harboe wrote:
Could you post a GDB backtrace?
See:
$ gdb ../openocd --args openocd
... ends up running /usr/bin/openocd ...
Try
gdb --args openocd -f interface/xxx.cfg -f target/.cfg ...
--
Øyvind Harboe
Embedded software and hardware consulting services
http://consulting.zylin.com
___
On Monday 18 May 2009, Dean Glazeski wrote:
Do you mean the target_type_s and target_s structures? I think there may be
some others too like the arm7_9_common_s struct. I'm commenting up the
arm7_9_common_s struct as I go too.
Yes, those interfaces. Once those get properly documented,
their
On Mon, 2009-05-18 at 19:33 +0100, Peter Denison wrote:
On Mon, 18 May 2009, Øyvind Harboe wrote:
[Oops - failed to copy the original to the list...]
On Mon, May 18, 2009 at 8:21 AM, Peter Denison open...@marshadder.org
wrote:
On Sat, 16 May 2009, Øyvind Harboe wrote:
Could you post
Try using
libtool gdb ../openocd
or the more pedantic (but future-proof):
libtool --mode=execute gdb ../openocd
Once a solution has been identified, it would be nice to have the BUGS
file updated...
--
Øyvind Harboe
Embedded software and hardware consulting services
Does the LPC2148 (which I have) exhibit the same problem?
I can not test the attached patch here, but it is intended
to allow switching between the long(old) or new (short)
tms_sequence tables. The patch uses the short table
as default.
Try:
tms_sequence long
tms_sequence short
--
Øyvind
Minor NAND updates:
- Comment which IDs are museum IDs: obsolete first-gen parts,
some with IDs that are reused with newer parts, 256-byte pages.
Linux doesn't support these by default, and OpenOCD rejects
the 256-byte pages.
- Recognize Micron as a NAND manufacturer.
- For nand
On Mon, 2009-05-18 at 21:51 +0200, Øyvind Harboe wrote:
Try using
libtool gdb ../openocd
or the more pedantic (but future-proof):
libtool --mode=execute gdb ../openocd
Once a solution has been identified, it would be nice to have the BUGS
file updated...
On Mon, 18 May 2009, Øyvind Harboe wrote:
Try using
libtool gdb ../openocd
or the more pedantic (but future-proof):
libtool --mode=execute gdb ../openocd
Once a solution has been identified, it would be nice to have the BUGS
file updated...
Excellent! That (to be precise
Committed 1833
use tap_get_tms_path_len() instead of fix # of 7 for all interfaces.
Not tested if this builds, but at least we're looking at a build error
instead of a runtime error.
--
Øyvind Harboe
Embedded software and hardware consulting services
http://consulting.zylin.com
Hello,
I posted a similar patch several month ago.
I have a JLink version v3.0
To get it to work you have to change several little things.
This is just a very ugly hack that somewhat disables support for =V5 JLinks
I'd just be interested if any of you can also get it to work this way...
I
Try using
libtool gdb ../openocd
or the more pedantic (but future-proof):
libtool --mode=execute gdb ../openocd
Once a solution has been identified, it would be nice to have
the BUGS file updated...
--
for dev work it is often easier to configure with
Gentlemen,
AFAIK EJTAG is already implemented in OpenOCD (I'm using it for
another MIPS based SOC to program external flash). I just
don't know
how complete it is in respect to debugging/single stepping.
The flash
programming routines for PIC32 are also available in OpenOCD. So I
Benjamin Schmidt wrote:
There's this segger closed source linux gdm server tool...
http://www.segger.com/pub/jlink/JLink_Linux_090202.tar.gz
It can show the hardware version.
With patch still gets three EMU_CMD_GET_CAPS errors and don't worry.
Then LED goes off on jlink. Should it go
On Sat, May 16, 2009 at 6:38 AM, Dean Glazeski wrote:
On another note, I'm going to start working harder with Chitlesh Goorah,
CC'd, on packaging the RPM for Fedora for OpenOCD. Chitlesh has a desire to
get OpenOCD pushed into the Fedora Electronics Lab (FEL) distribution and I
really want
Does either rev 1833 or 1833 with my patch displaying something like this in
the beginning?
Info : J-Link compiled Feb 20 2006 18:20:20 -- Update --
Info : JLink caps 0x3
Info : JLink max mem block 32
Info : Vref = 3.283 TCK = 1 TDI = 0 TDO = 1 TMS = 0 SRST = 1 TRST = 255
The problem is that
Hello Benjamin,
Tuesday, May 19, 2009, 12:39:26 AM, you wrote:
BS There's this segger closed source linux gdm server tool...
BS http://www.segger.com/pub/jlink/JLink_Linux_090202.tar.gz
BS It can show the hardware version.
Is there a necessity to map missing JLink commands? I could find them
Hello Igor
I think this wouldn't hurt anyone and could be very useful for debugging like
this.
But it should definately check via EMU_CMD_GET_CAPS first if command is
available. At the moment the caps value is read from the device but for
example the call to EMU_CMD_GET_MAX_MEM_BLOCK is done
Hello Benjamin,
Tuesday, May 19, 2009, 2:48:30 AM, you wrote:
BS I think this wouldn't hurt anyone and could be very useful for debugging
like
BS this.
BS But it should definately check via EMU_CMD_GET_CAPS first if command is
BS available. At the moment the caps value is read from the device
Does OpenOCD supports J-Link under Windows?
From here it seems to be no. And the front page OpenOCD
only supports ftdi2232.
http://www.yagarto.de/howto/jlink/index.html
The drive is certainly an issue. libusb-win32 filter driver may
be an option but it is known to break things under Vista 32
and
On Sun, 17 May 2009, David Brownell wrote:
The following are some notes I put together about the nand
commands based on reading the source code.
I plan to turn them into documentation sometime later, maybe by this
time next week. I've seen no documentation on the NAND commands; that
seems
Xiaofan Chen a écrit :
As far as I know, the chip erase is not implemented/working
for flashing the PIC32 according to the mailing list archive. So
it might be barely working. I do not know the status of debugging.
The mips debugger should work with it but you need some way to flash the
2009/5/19 Michel Catudal michelcatu...@gmail.com:
The mips debugger should work with it but you need some way to flash the
program.
I am busy working on the programmer. When I get something working I will
submit it as well as my debugger and eclipse support.
That would be great. I have the
Hi all,
I have prepared the following e-mails to attempt to move the OpenOCD
release process into motion, breaking out some various policies for
managing our ongoing releases and milestones that should also give us
some degree of quality-assurance. These cover several related (but
separable)
Hi all,
I updated The List in r1828 (see the TODO file) to help prepare the
OpenOCD project for its forthcoming 0.2.0 release. Please review it to
make sure that it contains the features that you want OpenOCD to have
before it is done (not only for 0.2.0). Please reply to this thread
with
On Tue, May 19, 2009 at 1:33 PM, Rick Altherr kc8...@kc8apf.net wrote:
OpenOCD certainly supports more than just FT2232. At the moment, there is
support for FT2232, JLink, RLink, VSLLink, and usbprog. I don't know of any
reason why these won't work on Windows. All of the USB-based
Hi all,
This message tries to cover a proposal for a tactical release process
for the OpenOCD community to consider. If there seems to be agreement
that this will be acceptable, I will write start some the relevant bits
up in a document and add it to the reference manual.
At the moment, we are
Hi all,
In tandem to perpetual tactical quality-improvement release goals, the
OpenOCD community will be pursuing strategic development goals that lead
to special milestone releases. As this indicates, I think such
planning should be decoupled from the release process, in so far as we
should be
Hi all,
Since this weekend, I have spent some time working on a set of Perl
scripts to prototype the back-end system that will aggregate the data
and present it for review (pre-analysis).
I started on this to replace the static developer table that I was using
to augment The List. I think
62 matches
Mail list logo
