Re: [OpenOCD-devel] GNU ARM Eclipse OpenOCD: a new binary distribution for Windows, GNU/Linux, OS X

On 02/05/2015 07:44 AM, Pink Boy wrote: > I go to Freddie's site and see that the latest binary for windows is > OpenOCD 0.8.0 commit date: 27.04.2014 10:28:21 MD5: > 1d7ab70dbc0fe15c7bbc8e6cb7504c8c So 10 months out of date. Next time you wisit my site please take 10 seconds longer to look at i

Re: [OpenOCD-devel] GNU ARM Eclipse OpenOCD: a new binary distribution for Windows, GNU/Linux, OS X

On Wed, Feb 04, 2015 at 10:44:47PM -0800, Pink Boy wrote: > > Well, so far this is wishful thinking, currently the procedure is quite > > complicated, especially the libraries. > > That says not so nice things about the codebase and build system. MSYS2 is able to build OpenOCD just fine, without

Re: [OpenOCD-devel] GNU ARM Eclipse OpenOCD: a new binary distribution for Windows, GNU/Linux, OS X

Liviu Ionescu sez, > >> binary distribution of OpenOCD to the GNU ARM Eclipse plug-ins > >> project (http://gnuarmeclipse.livius.net/blog/openocd/). > > > > How a binary distribution helps end-users to build OpenOCD? > > The binary distribution obviously does not, but the public scripts used > t

Re: [OpenOCD-devel] GNU ARM Eclipse OpenOCD: a new binary distribution for Windows, GNU/Linux, OS X

On 1/02/2015 10:19 pm, Andreas Färber wrote: > Am 01.02.2015 um 09:52 schrieb Liviu Ionescu: >> Why do you think end users would want to build OpenOCD? > > * End users of OpenOCD are in fact developers. > * You've packaged 0.8.0, with broken support for J-Link, CMSIS-DAP, etc. > * OpenOCD ships onl

Re: [OpenOCD-devel] GNU ARM Eclipse OpenOCD: a new binary distribution for Windows, GNU/Linux, OS X

On 05 Feb 2015, at 02:06, Chris Johns wrote: > On 1/02/2015 10:19 pm, Andreas Färber wrote: >> Am 01.02.2015 um 09:52 schrieb Liviu Ionescu: >>> Why do you think end users would want to build OpenOCD? >> >> * End users of OpenOCD are in fact developers. >> * You've packaged 0.8.0, with broken s

Re: [OpenOCD-devel] GNU ARM Eclipse OpenOCD: a new binary distribution for Windows, GNU/Linux, OS X

On 05 Feb 2015, at 01:36, Peter Stuge wrote: > Liviu Ionescu wrote: >>> What is harmful and useless to me is a feature to someone else. :\ >> >> hmmm... harmful means "causing or likely to cause harm"; >> >>> I think you should remove --enable-legacy-ft2232_libftdi because the >>> ft2232 drive

Re: [OpenOCD-devel] GNU ARM Eclipse OpenOCD: a new binary distribution for Windows, GNU/Linux, OS X

Liviu Ionescu wrote: > > What is harmful and useless to me is a feature to someone else. :\ > > hmmm... harmful means "causing or likely to cause harm"; > > > I think you should remove --enable-legacy-ft2232_libftdi because the > > ft2232 driver really shouldn't be used anymore. > > is this harm

Re: [OpenOCD-devel] GNU ARM Eclipse OpenOCD: a new binary distribution for Windows, GNU/Linux, OS X

On 05 Feb 2015, at 01:15, Peter Stuge wrote: > Liviu Ionescu wrote: >> I appreciate that we finally agreed on something, but, in practical >> terms, what is the complete options list to be used, with harmful >> and useless options removed? > > I don't think there's a one-size-fits-all. all mea

Re: [OpenOCD-devel] GNU ARM Eclipse OpenOCD: a new binary distribution for Windows, GNU/Linux, OS X

On 05 Feb 2015, at 01:02, Peter Stuge wrote: > Liviu Ionescu wrote: >> - which options are harmful and should be removed? > > I think you should remove --enable-legacy-ft2232_libftdi because the > ft2232 driver really shouldn't be used anymore. ok >> - are there any other options that might b

Re: [OpenOCD-devel] GNU ARM Eclipse OpenOCD: a new binary distribution for Windows, GNU/Linux, OS X

Liviu Ionescu wrote: > I appreciate that we finally agreed on something, but, in practical > terms, what is the complete options list to be used, with harmful > and useless options removed? I don't think there's a one-size-fits-all. What is harmful and useless to me is a feature to someone else. :

Re: [OpenOCD-devel] GNU ARM Eclipse OpenOCD: a new binary distribution for Windows, GNU/Linux, OS X

Liviu Ionescu wrote: > - which options are harmful and should be removed? I think you should remove --enable-legacy-ft2232_libftdi because the ft2232 driver really shouldn't be used anymore. > - are there any other options that might be added? > (I would explicitly use all options available, even

Re: [OpenOCD-devel] GNU ARM Eclipse OpenOCD: a new binary distribution for Windows, GNU/Linux, OS X

On 05 Feb 2015, at 00:31, Freddie Chopin wrote: > And this is the exact reason why I use all these options even though 75% > of them could be left-out and auto-detected. fully agree. returning to the actual options, can we decide what options should be used for binary distribution builds (ev

Re: [OpenOCD-devel] GNU ARM Eclipse OpenOCD: a new binary distribution for Windows, GNU/Linux, OS X

On 04 Feb 2015, at 21:25, Peter Stuge wrote: >> (and I have a custom pkg-config to detect them), > > Why? Why not do as the manual describes and use PKG_CONFIG_LIBDIR? On 04 Feb 2015, at 23:58, Andreas Fritiofson wrote: > Please also see contrib/cross-build.sh that for the intricacies of cr

Re: [OpenOCD-devel] GNU ARM Eclipse OpenOCD: a new binary distribution for Windows, GNU/Linux, OS X

On 02/04/2015 11:11 PM, Andreas Fritiofson wrote: > Just wanted to further clarify that for automated builds such as > distro packaging scripts etc, it actually makes sense to be explicit > about the adapters that should be enabled, even if they are > auto-enabled. The reason is to cause configu

Re: [OpenOCD-devel] GNU ARM Eclipse OpenOCD: a new binary distribution for Windows, GNU/Linux, OS X

Andreas Fritiofson wrote: > perhaps it makes sense to add a --with-libusb1 etc, that requires > successful detection of the libraries Very much so. //Peter -- Dive into the World of Parallel Programming. The Go Parallel

Re: [OpenOCD-devel] GNU ARM Eclipse OpenOCD: a new binary distribution for Windows, GNU/Linux, OS X

On 04 Feb 2015, at 23:55, Peter Stuge wrote: >> except not knowing the best 'configure' options (and replicated the >> configuration used by Freddie Chopin, considered a 'classical'), I >> think the build scripts I used for all 3 platforms are quite elaborate. > > Elaborate doesn't mean correct

Re: [OpenOCD-devel] GNU ARM Eclipse OpenOCD: a new binary distribution for Windows, GNU/Linux, OS X

On Tue, Feb 3, 2015 at 5:55 PM, Paul Fertser wrote: > I recommend to build with these options (provided libusb-1.0, > libusb-1.0 and HIDAPI APIs are available via pkg-config in the host > OS): > > --enable-buspirate > --enable-amtjtagaccel > --enable-oocd_trace > --enable-arm-jtag-ew > --enable-s

Re: [OpenOCD-devel] GNU ARM Eclipse OpenOCD: a new binary distribution for Windows, GNU/Linux, OS X

On Wed, Feb 4, 2015 at 9:16 PM, Liviu Ionescu wrote: > > "PKG_CONFIG_LIBDIR > > Replaces the default pkg-config search directory. > > PKG_CONFIG_PATH > > A colon-separated (on Windows, semicolon-separated) list of directories to > search for .pc files. The default directory will always be searche

Re: [OpenOCD-devel] GNU ARM Eclipse OpenOCD: a new binary distribution for Windows, GNU/Linux, OS X

Liviu Ionescu wrote: > > libusb-win32 isn't really neccessary for you to build - it is only > > neccessary for the kernel driver. > > it was required by openocd, when using the configure options I > mentioned previously. Ah, all right. Normally, libusb-compat-0.1 would be preferable to libusb-win

Re: [OpenOCD-devel] GNU ARM Eclipse OpenOCD: a new binary distribution for Windows, GNU/Linux, OS X

On 04 Feb 2015, at 21:25, Peter Stuge wrote: > Liviu Ionescu wrote: >> my experience with windows drivers is close to null, > > Then study. thank you for this suggestion, I'll do it when really needed, but currently Windows has quite a low priority for me. >> my build procedures already comp

Re: [OpenOCD-devel] GNU ARM Eclipse OpenOCD: a new binary distribution for Windows, GNU/Linux, OS X

Liviu Ionescu wrote: > my experience with windows drivers is close to null, Then study. > and, after reading your links, my understanding is that now some of > the devices no longer work unless Zadig is installed. can you confirm this? Zadig is a tool which can be used to install drivers. It is

Re: [OpenOCD-devel] GNU ARM Eclipse OpenOCD: a new binary distribution for Windows, GNU/Linux, OS X

On 03 Feb 2015, at 18:55, Paul Fertser wrote: > Right, because the legacy ft2232 driver supports Olimex adapters. It > doesn't mean though that it's the most appropriate driver. > ... official manual has this note: "Note that this driver has several > flaws and the @command{ftdi} driver is recom

[OpenOCD-devel] ST-Link V2 read overshot?

Hi all, time to time I encounter an error reading a configuration register using ST-Link V2. I had to make a workaround in psoc4 driver for reading PSOC4_SPCIF_GEOMETRY @ 0x400E. Today I found that it looks like word access reads more than one word and triggers an exception when the next wor

Re: [OpenOCD-devel] Kinetis flash driver

On 4.2.2015 17:02, Jens Bauer wrote: > Hi Tomas. > > On Wed, 04 Feb 2015 16:37:51 +0100, Tomas Vanek wrote: >> There is not much problem in setting FCLKDIV - I assume every KExx >> sets FEI mode @48MHz at reset (busclk 24MHz). > Uhm, yes, if we can be sure it's always set to the same speed, that co

Re: [OpenOCD-devel] PSoC 4 PLD

On 3.2.2015 12:37, Paul Fertser wrote: > On Tue, Feb 03, 2015 at 08:22:00AM +0100, Tomas Vanek wrote: >> BTW: If you don't know what is PSoC4: It is not "yet another small >> ARM MCU", Cypress integrated Cotex M0 core with PLD-based >> programmable logic. I really enjoyed working with the chip and

Re: [OpenOCD-devel] Kinetis flash driver

Hi Tomas. On Wed, 04 Feb 2015 16:37:51 +0100, Tomas Vanek wrote: > There is not much problem in setting FCLKDIV - I assume every KExx > sets FEI mode @48MHz at reset (busclk 24MHz). Uhm, yes, if we can be sure it's always set to the same speed, that could simplify things. > KExx should have th

Re: [OpenOCD-devel] Kinetis flash driver

On 4.2.2015 13:16, Jens Bauer wrote: > Hi Tomas. > > On Wed, 04 Feb 2015 09:18:14 +0100, Tomas Vanek wrote: > >> I made a quick research and found these new families potentially >> unsupported: >> >> SF4: K11_M50 K12_M50 >> KL16_M48 KL26_M48 >> SF5: K21_M50 K21_M120 K22_M50 K22_M120 K24_M1

Re: [OpenOCD-devel] Any reason why successfull code-reviewed patches are not applied?

Le 02. 02. 15 08:55, Paul Fertser a écrit : > Hello, > > On Mon, Feb 02, 2015 at 12:27:18AM +0100, Andreas Fritiofson wrote: >> On Sun, Feb 1, 2015 at 8:28 PM, Jean-Christian de Rivaz <[1]j...@eclis.ch> >> wrote: >>I doubt that peoples that never contributed to OpenOCD are in good >>positi

Re: [OpenOCD-devel] Kinetis flash driver

Hi Tomas. On Wed, 04 Feb 2015 09:18:14 +0100, Tomas Vanek wrote: > I made a quick research and found these new families potentially > unsupported: > > SF4: K11_M50 K12_M50 > KL16_M48 KL26_M48 > SF5: K21_M50 K21_M120 K22_M50 K22_M120 K24_M120 K63 K64 > KL16_M48 KL26_M48 > SF6: KL

Re: [OpenOCD-devel] Kinetis flash driver

An idea for update of kinetis driver. Tell me if it is silly. SIM_FCFG1 and SIM_FCFG2 registers contain everything we need except sector sizes, program section limit (usually equals sector size) and info that device has 4 blocks. We can use a protection region size (flash size/32) instead of re

Re: [OpenOCD-devel] Any reason why successfull code-reviewed patches are not applied?

Le 02. 02. 15 00:27, Andreas Fritiofson a écrit : > > > On Sun, Feb 1, 2015 at 8:28 PM, Jean-Christian de Rivaz > wrote: > > Le 31. 01. 15 09:43, Paul Fertser a écrit : > > Most of us have coworkers or friends or fellow students who work in > > related field. So w

[OpenOCD-devel] [PATCH]: 5cd5b37 cfg: add toshiba tx03 target

This is an automated email from Gerrit. dmitry pervushin (dpervus...@gmail.com) just uploaded a new patch set to Gerrit, which you can find at http://openocd.zylin.com/2532 -- gerrit commit 5cd5b37e5e6ae2117e366631cfed52549e219b6d Author: dmitry pervushin Date: Wed Feb 4 11:34:05 2015 +0100

[OpenOCD-devel] [PATCH]: 287ae6d flash/nor: added sfctl (Toshiba) flash controller

This is an automated email from Gerrit. dmitry pervushin (dpervus...@gmail.com) just uploaded a new patch set to Gerrit, which you can find at http://openocd.zylin.com/2531 -- gerrit commit 287ae6d93450b3146c3a62502ace63c989d212c0 Author: dmitry pervushin Date: Wed Feb 4 11:27:36 2015 +0100

[OpenOCD-devel] [PATCH]: 07b861f flash/nor/spi: add GigaDevice SPI flash

This is an automated email from Gerrit. dmitry pervushin (dpervus...@gmail.com) just uploaded a new patch set to Gerrit, which you can find at http://openocd.zylin.com/2530 -- gerrit commit 07b861f11c91a61fe574f4c64238767fceda36c9 Author: dmitry pervushin Date: Wed Feb 4 11:26:14 2015 +0100

Re: [OpenOCD-devel] Kinetis flash driver

Hi Jens and Paul Paul wrote > The kinetis driver really need some love... and I feel exactly the same. The code is not so bad, I don't think it needs to be rewritten. Of course if you, Jens, want to do so, I'll be glad to help. The problem is autodetection and overwhelming number of Freescale MC