e posting
this to another mailing list.
Also, rpmlint picked up that the FSF address in your COPYING file is
incorrect. Patch attached as well.
// Dean Glazeski
--- COPYING.orig 2011-12-14 21:41:38.679088677 -0600
+++ COPYING 2011-12-14 21:42:14.742637819 -0600
@@ -2,7 +2,7 @@
Version 2
Hey all,
Just got a bug report from the Red Hat bugzilla for the OpenOCD package.
I've directed the reporter to send more information here so you guys can
help him cause I'm pretty clueless about a lot of the source :).
https://bugzilla.redhat.com/show_bug.cgi?id=613343
// Dea
Well that's a strange one. Thanks for doing the comparison for me and
sharing the result and fix!
// Dean Glazeski
On Mon, May 3, 2010 at 12:01 PM, Gary Carlson wrote:
> Dean/Peter,
>
> Well I have some good news on this problem. I finally discovered on Friday
> what the is
able to test the
"bootability" of the flash stuff that gets written. I thought that if I
could write and then read the same data, then everything should be okay.
Something I'm thinking I should have done is try to write with SAM-BA and
then verified what was writ
Hey all,
OpenOCD 0.4.0 is now available in the Fedora repositories. Just run 'yum
install openocd' or 'yum update' to get it.
--
// Dean Glazeski
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
http
On Sat, Feb 13, 2010 at 8:00 PM, Dean Glazeski wrote:
> Hey all,
>
> I've posted the source RPM and builds for Fedora 11 and 12 for OpenOCD
> 0.4.0-RC2 on my Fedora people page. (http://dnglaze.fedoraproject.org).
> Give the RPMs a spin if you are running Fedora. I'
Hey all,
I've posted the source RPM and builds for Fedora 11 and 12 for OpenOCD
0.4.0-RC2 on my Fedora people page. (http://dnglaze.fedoraproject.org).
Give the RPMs a spin if you are running Fedora. I'll post my own results a
bit later this evening.
--
// Dea
ntually get the git
connector working, but for now it's a no go. You can build the plug-in in a
shell on sourceforge, but I have no idea how to make trac aware of the
plugin. Here's a ticket about it:
https://sourceforge.net/apps/trac/sourceforge/ticket/7674
Please, do consider using
On Thu, Jan 28, 2010 at 7:45 PM, David Brownell wrote:
> On Thursday 28 January 2010, Dean Glazeski wrote:
> > You know, I'm sort of in love with Trac. I love the way their code is
> > designed and I love their system. I've been using for quite some time.
>
> Hmm
quite some time. Do
you have this working with the OpenOCD git repository on SF? There is a
plug-in for git support in Trac, but I've never used it.
--
// Dean Glazeski
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
. I'd at least like to know the steps involved :). If it's
scriptable, I may put together a script we can put in the main tree that
will make everyone's life easier.
I don't have a 64-bit version of Windows installed right now, but I may in
the near future. You can keep me in the loop
dows C:\
type paths. There are also problems if there are spaces in the path. I'm
not sure how to correct for that in TCL, though I assume everything will be
alright if I surround the path with quotes. Course, that means the line
parsing needs to be changed too. There's sti
Lists available completions when a user presses tab from a telnet client. If
there is only one completion, it automatically does it. This supports commands,
sub-commands, files, and directories.
This also introduces a change to the command helpers that allows external files
to check if a command
telnet
branch, it's updated against the most current OpenOCD head. Any feedback will
be appreciated!
// Dean Glazeski
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Adds support for the control sequences for home and end on a keyboard to the
telnet server interface.
---
src/server/telnet_server.c | 20 +++-
1 files changed, 19 insertions(+), 1 deletions(-)
diff --git a/src/server/telnet_server.c b/src/server/telnet_server.c
index 92e7480..f
has the current
command set before passing the structure on.
--
// Dean Glazeski
From 0ae4eec403c52f8075172fcd10a0ce48ac9480b4 Mon Sep 17 00:00:00 2001
From: Dean Glazeski
Date: Fri, 1 Jan 2010 19:58:38 -0600
Subject: [PATCH] Add the current command to the command information
Adds the current
he
group type in helper/startup.tcl in ocd_bouncer is a reasonable idea. It
looks a heck of a lot better to not have all of that error output when some
one uses a group command without giving a subcommand.
--
// Dean Glazeski
From 433a11f257529f14c1fd0a412a1ec578d5eee288 Mon Sep 17 00:00:00 2001
#x27;
or 'init' but not anything like 'nand drivers'. This may not be the best
way to build the string from the command's arguments, but suggestions are
welcome :).
--
// Dean Glazeski
From e062290b5828ab5cb3e2ce5f9a0b5e6a8b8e6aa2 Mon Sep 17 00:00:00 2001
From: Dean Glazes
>
>
> Look at my mirror. I have a few patches for that. It's post 0.4 work.
>
> --Z
>
Sweet, that's what I was talking about. I guess I'll just leave it alone
and complain how you keep doing big changes on things I'm playing with :).
I'll
ent
device types and read from the common interface (I believe the pointer
locations have to also be the same here, so perhaps this is the same
thing?).
I'm not really sure if this is a worth while task, but it would reduce some
of the code redundancy.
uld I
return something other than ERROR_COMMAND_SYNTAX_ERROR?
--
// Dean Glazeski
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Hi All,
Thought I might throw this out there while I was working in Eclipse. If we
are ignore the random crap introduced by Eclipse IDE, we were missing some
things in the .gitignore file. This just adds those things. They were
annoying me :).
--
// Dean Glazeski
From
On Sat, Dec 19, 2009 at 10:19 PM, David Brownell wrote:
> On Saturday 19 December 2009, Dean Glazeski wrote:
> > > Could you reissue this without the gratuitous "add semicolon" changes?
> > > That way we'll be able to see if significant changed...
> &g
On Sat, Dec 19, 2009 at 3:47 PM, David Brownell wrote:
> On Thursday 17 December 2009, Dean Glazeski wrote:
> > - mww 0xfc20 0x4001 # CKGR_MOR : enable main oscillator,
> 512 slow clock startup
> > - sleep 20 # wait 20 ms (need 1
On Fri, Dec 18, 2009 at 2:48 PM, David Brownell wrote:
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
> Q: What is the most annoying thing in e-mail?
>
>
> On Friday 18 December 2009, Dean G
The increase happens because the NAND erase function was using 1000 for a
timeout so I just increased the general timeout to that amount. I don't
think it should be a big deal because the timeout shouldn't happen normally.
By the way, what is top-posting and how do I stop?
// Dean Gla
)
should be the return value. I've attached a new version of the patch to
address formatting and return value stuff.
// Dean Glazeski
On Fri, Dec 18, 2009 at 4:29 AM, David Brownell wrote:
> On Thursday 17 December 2009, Dean Glazeski wrote:
> > +...@deffn Command {at91sam9 cle} num a
Right now, I'm specifically calling get_nand_device_by_num or some such.
Can you suggest a better method or direct me to an example NAND flash? I'm
not really aware of any other method.
// Dean Glazeski
On Fri, Dec 18, 2009 at 4:13 AM, David Brownell wrote:
> On Thursday 17
That may be a bug, but that's how the original NAND code did the read and
write functions. It does make sense for them to either both do the swap or
not do the swap.
// Dean Glazeski
On Fri, Dec 18, 2009 at 1:43 AM, David Brownell wrote:
> On Thursday 17 December 2009, Dean Glazes
I'm fine with that. It probably is better to keep an eye on the actual read
data function as well. Feel free to make the same tweak to the NAND write
page data function as well (patch 2/2 in the series).
// Dean Glazeski
On Thu, Dec 17, 2009 at 11:51 PM, David Brownell wrote:
> On
Sorry, I took another look and saw what you were talking about and how to
correct for it. Here's another version that addresses that issue.
// Dean Glazeski
On Thu, Dec 17, 2009 at 10:56 PM, Dean Glazeski wrote:
> Oh, I didn't see that. This patch can be ignored then. It
Oh, I didn't see that. This patch can be ignored then. It just looks so
similar :).
// Dean Glazeski
On Thu, Dec 17, 2009 at 10:29 PM, David Brownell wrote:
> On Tuesday 15 December 2009, Dean Glazeski wrote:
> > I noticed the NAND erase function was doing page command stuff,
I forgot to mention, this builds on top of my NAND refactor work (read/write
page data function) that I posted in a previous patch series.
// Dean Glazeski
On Thu, Dec 17, 2009 at 9:10 PM, Dean Glazeski wrote:
> This patch series represents a NAND flash controller implementation
This updates the board configuration for the SAM9-L9260 board with the
configuration for the on-board NAND and dataflash. Included are commands
for configuring the AT91SAM9 NAND flash driver.
---
tcl/board/olimex_sam9_l9260.cfg | 94 ++-
1 files changed, 73 i
/nand/at91sam9.c
@@ -0,0 +1,746 @@
+/*
+ * Copyright (C) 2009 by Dean Glazeski
+ * dngl...@gmail.com
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License as published by
+ * the Free Software Foundation; either
This patch series represents a NAND flash controller implementation for AT91SAM9
devices and perhaps Atmel NAND in general. The first patch is the driver and
the necessary file updates to build it. The second patch is the driver applied
to the Olimex SAM9-L9260 board.
___
This series refactors some common code in the NAND core and makes them available
to NAND drivers.
- The first one refactors reading page data
- The second refactors the commond write page data
___
Openocd-development mailing list
Openocd-developme
Refactored the write page raw function into two new functions for writing data
to a NAND device and then another function to finish up a write to a NAND
device. This includes some new updates to introduce more error checking to
existing code.
---
src/flash/nand/core.c | 116 +
Added a new function to encapsulate reading a page of data from a NAND device
using either the read_block_data function of a NAND controller or to use direct
reading of data from the NAND device. This also adds some performance
enhancements and uses the read_data function if the read_block_data fu
this. It could later be extended to
manage resources, too.
// Dean Glazeski
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
--to="
openocd-development@lists.berlios.de" -2
// Dean Glazeski
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
iver doesn't have a better read
page function, we just sit there and call a read function on a controller
over and over again until we read enough. This could be bad if we also have
to look up the virtual table to get the right function. This might cause
issues for ZY1000, if I understand ho
suggested. I'd like to see the at91sam9-nand pieces make it into the
version 0.4.0 release, if it's still possible.
Let me know if there's anything I need to do to get it in. I can post a
giant patch for the AT91SAM9 NAND driver once the NAND refactor changes are
approved.
/
I noticed the NAND erase function was doing page command stuff, so I pulled
the redundant code out. Patch is attached
// Dean Glazeski
From 2bb284a568f936f47e2a638e80c1554f94f5e860 Mon Sep 17 00:00:00 2001
From: Dean Glazeski
Date: Tue, 15 Dec 2009 23:57:18 -0600
Subject: [PATCH 1/4] Use NAND
Merge the erase patch then. :)
> >
> > Not till I see that followup patch ... ;)
> >
> You won't till I see this one in git ... ;)
Then make your own repository on http://repo.or.cz, push the OpenOCD source
there with your patch and get on with it! Man you guys are an
> >> 0
>> src/helper/types.h: (in function h_u16_to_be)
>> src/helper/types.h:158:22: Left operand of >> may be negative (int): val
>> >> 8
>> src/helper/types.h:159:22: Left operand of >> may be negative (int): val
>> >> 0
>> src/helper/binaryb
27;t say I disagree with this position. Maybe as one of my tasks for the
next week, I'll start doing this kind of cleanup in my nand-refactor branch
at http://repo.or.cz/w/openocd/dnglaze.git. I still have some NAND tweaks
up there that aren't in mainline, but something like this migh
>function) {nand->function()} blocks for just about every read and
write command? Look at nand_read_page and nand_write_page. They have that
sort of logic.
// Dean Glazeski
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
htt
in the future OpenOCD can be configured with TCL
and LUA just for fun.
// Dean Glazeski
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Don't mind me when it comes to the NAND. I won't be active probably until
Christmas break when I no longer have persistent projects :). At that time
I welcome the challenge of forcing my stuff into the proper mold. I'll have
to make a list. Have fun!
// Dean Glazeski
On Fri,
Aargh, darn school! I can't keep up with these patches, but do it! This
leaves some room for work I want to do when I have time again :).
// Dean Glazeski
On Tue, Dec 1, 2009 at 5:30 PM, Zach Welch wrote:
> Hi all,
>
> I want to clean up our flash directory, moving
On Fri, Nov 27, 2009 at 7:13 PM, David Brownell wrote:
> On Friday 27 November 2009, Dean Glazeski wrote:
> > On Fri, Nov 27, 2009 at 2:12 AM, David Brownell
> wrote:
> >
> > > On Monday 23 November 2009, Dean Glazeski wrote:
> > > > point. The new p
On Fri, Nov 27, 2009 at 2:12 AM, David Brownell wrote:
> On Monday 23 November 2009, Dean Glazeski wrote:
> > point. The new play area is http://repo.or.cz/w/openocd/dnglaze.git.
> I've
>
> I merged a few of these. The page command refactoring:
>
> + if (
Oh, I got ya :). I just copy and pasted it from another file. I'll fix
that.
// Dean Glazeski
On Wed, Nov 25, 2009 at 5:53 PM, David Brownell wrote:
> On Wednesday 25 November 2009, Dean Glazeski wrote:
> > >
> > > - ARM NAND I/O interface update ... please
ch as
well and see what I can do with it for the code download. I'll post an
email when I get done. Thanks for the suggestions!
// Dean Glazeski
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
This patch shouldn't be necessary. I have the libftdi version working fine
with current head. I think this might be an issue with mixing libraries in
the configure command. I've responded to the next email with more
information.
// Dean Glazeski
On Wed, Nov 25, 2009 at 9:43
-with-ftd2xx
option.
// Dean Glazeski
On Wed, Nov 25, 2009 at 8:34 AM, loody wrote:
> dear all:
> I use configure --help, but I cannot see where I can tell openocd
> where the library of ft2232.
> I use following configure even I don't use cygwin and I use lib
> instead of de
r, and merge in my
three branches that have that at91sam9 driver and the core updates that it
depends on. I'm not sure on what the commands should be, so any direction
would be appreciated. :)
// Dean Glazeski
On Tue, Nov 24, 2009 at 4:02 PM, Zach Welch wrote:
> Hi all,
>
>
Actually, I ran into a possible other option:
git rebase -p master
which is supposed to preserve merges by not ignoring them. It seems to work
in the limited testing I've done. I'll wait for more commits on origin
before I confirm.
// Dean Glazeski
On Mon, Nov 23, 2009 at 6:2
an unemployed people?
I can't afford big name JTAG dongles! :) I would be very interested in
trying to work on a project like this in the time I have available.
// Dean Glazeski
___
Openocd-development mailing list
Openocd-development@lists.berlios
e a good way to rebase
two branches that merge to create another branch? With my current layout,
if I rebase each branch individually, the merge disappears.
// Dean Glazeski
On Mon, Nov 23, 2009 at 3:47 PM, Zach Welch wrote:
> On Mon, 2009-11-23 at 13:04 -0600, Dean Glazeski wrote:
> &
ch for the
SAM9 driver later anyways :).
// Dean Glazeski
On Mon, Nov 23, 2009 at 2:58 PM, Øyvind Harboe wrote:
> I took a super quick peek:
>
> 1. What's the order in which the branches should be applied?
>
> 2. The new .c file and modification of the Makefile.am belongs in th
ombine all the patches
for at91sam9-nand as a single patch and submit that. Does this sound like a
good plan? Once all of that is done, I'll submit some patches to fix
formatting if there are any issues. Thanks.
// Dean Glazeski
On Mon, Nov 23, 2009 at 1:53 PM, David Brownell wrote:
&
re very welcome.
// Dean Glazeski
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
I don't know if this patch actually works, but it does compile :). This is
how the davinci driver would change with the update as far as I can tell. I
don't have a board with this chip, so I'll leave it to you to try it out.
// Dean Glazeski
On Fri, Nov 20, 2009 at 2:03 PM,
tting.
// Dean Glazeski
From 0512447d983a6bf27db711148e30c3480683b5b0 Mon Sep 17 00:00:00 2001
From: Dean Glazeski
Date: Fri, 20 Nov 2009 00:19:39 -0600
Subject: [PATCH] NAND page command refactoring.
Created a new function that handles sending a command and the address
information for pages to a
I can verify that this patch makes the fake errors go away.
// Dean Glazeski
On Thu, Nov 19, 2009 at 8:16 PM, Zach Welch wrote:
> Another whoops. The changes to use '$_CHIPNAME.flash' were added after
> I wrote that code, and I didn't consider the consequences thoro
By '-c init' did you mean '-c openrd_init'?
// Dean Glazeski
On Thu, Nov 19, 2009 at 5:28 PM, :k wrote:
> i tried several versions of openocd, incl. latest from git. serveral
> machines (x86 & amd64), as well as different usb cables ..
>
> I am out o
ices, they
don't have an integer after the '.'. I'm not really sure why this is there
or how to fix it.
// Dean Glazeski
On Thu, Nov 19, 2009 at 5:00 PM, Zach Welch wrote:
> On Wed, 2009-11-18 at 02:56 -0800, Zachary T Welch wrote:
> > Hi all,
> >
> > T
spend some time with that
once I have the AT91SAM9 NAND working and get a start with the dataflash.
// Dean Glazeski
On Thu, Nov 19, 2009 at 5:12 PM, Zach Welch wrote:
> On Thu, 2009-11-19 at 15:08 -0800, Zach Welch wrote:
> > At the moment, I just want correctness. Thanks for doin
other note, would it be better to have a for loop iterate through data
as opposed to using memcmp? memcmp is faster, but you can provide more
information if things are in a for loop.
// Dean Glazeski
On Thu, Nov 19, 2009 at 4:58 PM, Dean Glazeski wrote:
> nand verify is not working. I
re.
As another curveball, it reads 0x1B when not verifying oob and 0x05 when I
tell it to at location 0. The correct value in the file is 0x1E for that
location and the NAND device does return this value when read.
// Dean Glazeski
On Thu, Nov 19, 2009 at 9:15 AM, Zach Welch wrote:
> On We
Glazeski
On Thu, Nov 19, 2009 at 2:40 AM, David Brownell wrote:
> On Wednesday 18 November 2009, Dean Glazeski wrote:
> > The thing is that the first time I tried to do this:
> >
> > nand erase 0 0 2048
> >
> > I got presented with command usage and had no idea
id parameter value.
// Dean Glazeski
On Thu, Nov 19, 2009 at 1:04 AM, David Brownell wrote:
> On Wednesday 18 November 2009, Dean Glazeski wrote:
> > Hi all,
> >
> > Is there a good way for me to determine the erase block size for a NAND
> > chip? Right now, the devic
one has
filled in the table? I know my Samsung chip gives out additional data bytes
in addition to manufacturer and device ID that specify block and page
sizes. Can this be leveraged to dynamically populate the NAND devices?
Thanks for any feedback.
// Dean Glazeski
Hi all,
Recent NAND file I/O changes are parsing the wrong argument for the size.
Should be third argument, not second.
// Dean Glazeski
From e569df94abf628bcec2652971fc825fc5e46193b Mon Sep 17 00:00:00 2001
From: Dean Glazeski
Date: Wed, 18 Nov 2009 23:22:25 -0600
Subject: [PATCH
move
instruction and added with 3. Now we are actually offsetting into an array.
Aren't C externs fun? Here's a site that explains it well. I know, it's
from microsoft, but it has pretty ASCII pictures :)
http://support.microsoft.com/kb/44463
// Dean Glazeski
On Wed, Nov 18, 2009 at
I can confirm that this fixes the seg fault on my end.
// Dean Glazeski
On Wed, Nov 18, 2009 at 1:42 PM, Zach Welch wrote:
> On Wed, 2009-11-18 at 11:34 -0800, Zach Welch wrote:
> > On Wed, 2009-11-18 at 11:23 -0700, David Brownell wrote:
> > > On Wednesday 18 November 2009
CC going on
the at91sam9 NAND driver, so I should (hopefully) start playing in about a
week. At that time I will be more able to let you know what can be done.
// Dean Glazeski
On Wed, Nov 18, 2009 at 9:10 AM, Zach Welch wrote:
> I have been considering another round of reorganization,
NAND working on my AT91SAM9, so there may be future patches for yet another
type of flash.
// Dean Glazeski
On Wed, Nov 18, 2009 at 4:56 AM, Zachary T Welch wrote:
> Hi all,
>
> This series improves on the patch sent previously to add bank names.
> It adds a 'name' field
cool EDA tools in FEL, but have Fedora installed already can just do
yum groupinstall 'Electronic Lab'
// Dean Glazeski
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listin
Hi all,
OpenOCD 0.3.1 is now available in the Fedora repositories. Just do
yum install openocd
or, if you already have it installed via yum,
yum update.
Enjoy.
// Dean Glazeski
___
Openocd-development mailing list
Openocd-development
9 ale 0 21 ;# address line 21 is the address latch enable line
at91sam9 rdy_busy 0 0xf800 13 ;# ready/~busy input comes from pin 13 of
PIOC
at91sam9 ce 0 0xf800 14 ;# chip enable output connected at pin 14 of
PIOC
Does this seem reasonable? Would this work for the majority of SAM9s out
there
Hi all,
This fixes minor typos in types.h that caused errors from doxygen. It just
changes params to param
// Dean Glazeski
From cb6a8383759147f607fef06ed2dd45ae5fcd47b5 Mon Sep 17 00:00:00 2001
From: Dean Glazeski
Date: Mon, 16 Nov 2009 12:38:20 -0600
Subject: [PATCH] Fix doxygen errors from
I'll post a
patch series for that soon. I'm not sure if I would be skilled enough at
finding where the code can be used elsewhere in the code base. I'll make an
attempt, but we'll see how bad/good that goes :).
I'm working
room for
refactoring between this function and the write version. I'm not sure how
to do that so I just posted this patch with the implementation.
// Dean Glazeski
From 91f54ef62fd9ab94260d941192fb1b7144501056 Mon Sep 17 00:00:00 2001
From: Dean Glazeski
Date: Sun, 15 Nov 2009 02:32:38 -06
w'. In addition, it
appears that the command name is now 'ocd_mww', so the index for the w, h,
or b character now needs to be 6 instead of 2. Patch is attached.
// Dean Glazeski
0001-Invalid-command-syntax-errors-with-MWW.patch
Description: Binary data
lled, so I don't know
where to go look for fixes. I'll leave it to some one who know better than
I. Is there a better way for me to handle this?
// Dean Glazeski
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
http
Another one that is still in the tree is command_context_s. Any reason that
still has the '_s'?
// Dean Glazeski
On Sat, Nov 14, 2009 at 9:09 AM, Zachary T Welch wrote:
> Hi all,
>
> I discovered that my series that upgraded types missed a few spots
> where scan_field_
ieve there was a discussion about having an installer for Windows but
there was some license issues that came up with distributing ftd2xx and for
some reason libftdi-win32 wasn't a good alternative.
// Dean Glazeski
___
Openocd-development mailing
I thought I might throw this in here, but the last time I tried to use the
CRC check, it didn't work. This was a long time ago, but I believe the
problem was due in part to interrupts being enabled on the chip. Is this
resolved, too?
// Dean Glazeski
On Tue, Nov 3, 2009 at 4:12 PM,
Hello,
There are two interface scripts that are essentially the same: luminary.cfg
and luminary-lm3s811.cfg. The only difference is the ft2232_device_desc.
Can anyone verify that we need both? If we do, any naming suggestions since
they seem to be for the same development board?
// Dean
send my a
link?
// Dean Glazeski
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
tal frequency. I was thinking it might be helpful to centralize some of
that type of logic to a TCL function that resides in a target file instead
of repeating the logic for each board that uses the target. This may show
up in the future as I play more with NAND on my SAM9-L9260 board.
se DLTK, to actually
recognize the files and give some coloring. I have to say, I'm sort of a
sucker for colors :)
// Dean Glazeski
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
On Fri, Oct 30, 2009 at 2:47 AM, David Brownell wrote:
> On Friday 30 October 2009, Dean Glazeski wrote:
> > --enable-ep93xx \
> > --enable-at91rm9200 \
>
> I'm amazed you can enable those on x86 builds. :)
> They're for different flavors of native AR
--enable-ft2232_libftdi \
--enable-ep93xx \
--enable-at91rm9200 \
--enable-usbprog \
--enable-presto_libftdi \
--enable-jlink \
--enable-vsllink \
--enable-rlink \
--enable-dummy \
--enable-gw16012 \
--enable-amtjtagaccel \
--enable-arm-jtag-ew
// Dea
it. It
may be wise to hammer down a standard and document it some where in the
source tree or in a developer document.
// Dean Glazeski
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
I'm not sure, but this might also be affecting general mww commands as
well. See this thread:
http://lists.berlios.de/pipermail/openocd-development/2009-October/011574.html
I don't have my development system on hand, so I can't test this right now.
// Dean Glazeski
On Sun, Oct
naging the database, that
sort of problem won't happen.
As another note, it wouldn't be that hard to leverage Sourceforge's
capabilities to track the bugs.
// Dean Glazeski
On Fri, Oct 23, 2009 at 2:13 AM, Holger Freyther wrote:
> On Friday 23 October 2009 08:56:04 Øyvind
1 - 100 of 158 matches
Mail list logo
