[Openocd-development] [PATCH] add missing initializers in nand.c

Hi all, The attached patch fixes a missing initializer warning with -Wextra. Cheers, Zach diff -u src/flash/nand.c src/flash/nand.c --- src/flash/nand.c (working copy) +++ src/flash/nand.c (working copy) @@ -165,7 +165,7 @@ {"NAND 2GiB 1,8V 16-bit", 0xB5, 0, 2048, 0, LP_OPTIONS16}, {"NAND 2

[Openocd-development] [PATCH] trim logic in tms470.c

Hi all, The attached patch removes two comparisons that are always true and generate warnings with -Wextra. Cheers, Zach Index: src/flash/tms470.c === --- src/flash/tms470.c (revision 1462) +++ src/flash/tms470.c (working copy) @@

[Openocd-development] [PATCH] fix signed/unsigned comparisons

Hi all, The attached patch fixes a number of signed/unsigned comparison warnings that appear with -Wextra. This handles the flash directory first. I will submit more patches to fix the remaining warnings. This patch serves as a temporary measure. Many structures use 'int' instead of unsigned t

Re: [Openocd-development] [PATCH] fix warnings in usbprog

Well, I checked around in the code, and it seems that function is only called with a type produced by jtag_scan_type. That function returns a value that is covered by the three cases; moreover, those three values are the only ones defined for enum scan_type. It really should never hit the default

Re: [Openocd-development] [PATCH] fix warnings in usbprog

Hi >From what I read in the patch no default test means possible crash, that was not possible with previous code My 2cts Fab On Sun, Apr 19, 2009 at 12:35 AM, Zach Welch wrote: > Hi all, > > The attached patch fixes pointer-sign warnings in the usbprog module. > In the process, I could not he

Re: [Openocd-development] [PATCH] fix warnings in usbprog

On Sat, 2009-04-18 at 15:35 -0700, Zach Welch wrote: > Hi all, > > The attached patch fixes pointer-sign warnings in the usbprog module. > In the process, I could not help but simplify the code to be a little > more compact/readable (maintaining functional equivalence). Oops. I made a last second

[Openocd-development] [PATCH] fix warnings in usbprog

Hi all, The attached patch fixes pointer-sign warnings in the usbprog module. In the process, I could not help but simplify the code to be a little more compact/readable (maintaining functional equivalence). Cheers, Zach Index: src/jtag/usbprog.c =

[Openocd-development] [PATCH] use tap_state_t

Hi all, The attached patch fixes a few instances where the tap_state_t type should be used. Cheers, Zach Index: src/jtag/gw16012.c === --- src/jtag/gw16012.c (revision 1462) +++ src/jtag/gw16012.c (working copy) @@ -194,7 +194,7 @@

[Openocd-development] [PATCH] automake maintainer mode

Hi all, The attached patch adds the AM_MAINTAINER_MODE macro to configure.ac, which provides the --enable-maintainer-mode option. When provided, the autotools generate additional Makefile rules that allow the build system (configure, Makefile.in and Makefile outputs) to be rebuilt when their rele

Re: [Openocd-development] [STi7109]Is there any config files ?

Hello, STi71xx has SuperH (SH4) architecture and is not supported by OpenOCD Best regards, Ivan On Sat, 18 Apr 2009 13:18:46 +0200, Jean-Christophe PLAGNIOL-VILLARD wrote: > On 13:25 Sat 18 Apr , Jean-Michel Hautbois wrote: >> Hi everybody, >> >> I am new to this mailing list, and new with

Re: [Openocd-development] [STi7109]Is there any config files ?

2009/4/18 Jean-Christophe PLAGNIOL-VILLARD : > On 13:25 Sat 18 Apr     , Jean-Michel Hautbois wrote: >> My main goal is to write a new u-boot inside the flash memory (the >> chip is a Spansion S29GL128N), because the last one has been erased. > u-boot can do it itself I can't do anything today, be

Re: [Openocd-development] [STi7109]Is there any config files ?

On 13:25 Sat 18 Apr , Jean-Michel Hautbois wrote: > Hi everybody, > > I am new to this mailing list, and new with using openOCD. > I have a Tribbox (STi7109 based board), and I wish to use a JTAGkey > from amontec. > I can't find any file relative to this board in the source code. Is > there a

Re: [Openocd-development] JTAG/TAP changes?

Zach Welch wrote: > Hi guys, > > What is the status of the out-of-tree TAP work? Can I talk you into > posting the patches in their current state for review, along with a > description of what is done and the list of tasks still in progress? > > Thanks, > > Zach > I have no modified code yet.

[Openocd-development] [STi7109]Is there any config files ?

Hi everybody, I am new to this mailing list, and new with using openOCD. I have a Tribbox (STi7109 based board), and I wish to use a JTAGkey from amontec. I can't find any file relative to this board in the source code. Is there any way to use it ? How can I do that ? My main goal is to write a n

[Openocd-development] Patches applied, new version r1462

Hello, the following patches was applied: - openocd-flash-static-keyword-v3.patch - openocd-lpc2000-fix-erase-obo.patch - openocd-jlink-fix-sign-ptr-warn.patch - openocd-wextra-etm.patch - openocd-wextra-jtag.patch - openocd-add-new-tap-symbols-v6.patch Many thanks to Zach Welch. Regards, Mich