Re: [Openocd-development] [bisected] Re: arm920t regression cache support

2010-02-14 Thread Marc Pignat
Hi all! Here is a fix for my problem, at least. Problem : Clean and Invalidate DCache is not available in cp15 interpreted mode. workaround : Use the Invalidate only. The problem still remains for write back data cache, but at least it will work for write through. Marc diff --git a/src/target/

Re: [Openocd-development] Windows 64-bit version tests

2010-02-14 Thread karrbd
Hi Freddie, Thanks for the suggestion. At the time I don't have spare cycles for self-signing the drivers, but I decided to spend a bit of time troubleshooting the service section error in the INF file. I had success with WinXP 64 by changing libusb-win32_ft2232_driver.inf as follows. 1) in the

Re: [Openocd-development] [bisected] Re: arm920t regression cache support

2010-02-14 Thread David Brownell
On Sunday 14 February 2010, Marc Pignat wrote: > > I will look at this, it seems that interpreted accesses can only be used for > a restricted set of MCR/MRC instructions! Right. That's sort-of-explained in the ARM920t reference manual. I thought I had added comments identifying the relevant ta

Re: [Openocd-development] [bisected] Re: arm920t regression cache support

2010-02-14 Thread Marc Pignat
On Friday 12 February 2010 16:56:06 Øyvind Harboe wrote: > > I can't make it work, but if I read well int > > arm920t_write_cp15_interpreted, we should put > > the address in value... > > > > I mean we use MCR p15,0,r0,... and we put the VMA in r1, so it will be > > unused? > > I don't know and

Re: [Openocd-development] FreeBSD status of 0.4.0-RC2 (was: FreeBSD status of 0.4.0-RC1)

2010-02-14 Thread Xiaofan Chen
On Mon, Feb 15, 2010 at 9:36 AM, CeDeROM wrote: > Ah yes, OpenOCD's configure script can also assume using > "/usr/local/lib" and "/usr/local/include" to search for libraries and > header files - it would be nice, however if it don't the Port will > make it automatically :-) Actually I consider t

Re: [Openocd-development] FreeBSD status of 0.4.0-RC2 (was: FreeBSD status of 0.4.0-RC1)

2010-02-14 Thread CeDeROM
On Mon, Feb 15, 2010 at 1:21 AM, Xiaofan Chen wrote: > On Mon, Feb 15, 2010 at 9:13 AM, Xiaofan Chen wrote: >>> and there are some addtional libraries/includes passed to the compiler >>> in the Makefile: > (...) >> I think the above patches should be integrated into the main >> OpenOCD source tre

Re: [Openocd-development] FreeBSD status of 0.4.0-RC2 (was: FreeBSD status of 0.4.0-RC1)

2010-02-14 Thread CeDeROM
On Mon, Feb 15, 2010 at 12:53 AM, Xiaofan Chen wrote: > On Mon, Feb 15, 2010 at 8:35 AM, CeDeROM wrote: > >> If you want to test the latest 0.4.0-rc2 source code, please download >> this unapproved port package and uncompress it into /usr/ports/devel: >> http://files.tomek.cedro.info/stuff/openoc

Re: [Openocd-development] FreeBSD status of 0.4.0-RC2 (was: FreeBSD status of 0.4.0-RC1)

2010-02-14 Thread Xiaofan Chen
On Mon, Feb 15, 2010 at 9:13 AM, Xiaofan Chen wrote: >> and there are some addtional libraries/includes passed to the compiler >> in the Makefile: >> CFLAGS+=        -I${LOCALBASE}/include -L${LOCALBASE}/lib >> >> Wow, Ive just realised that using FreeBSD is somehow like programming >> in assembly

Re: [Openocd-development] FreeBSD status of 0.4.0-RC2 (was: FreeBSD status of 0.4.0-RC1)

2010-02-14 Thread Xiaofan Chen
On Mon, Feb 15, 2010 at 9:01 AM, CeDeROM wrote: > That is probably because port got requested dependencies: > ===>   openocd-0.4.0.r2 depends on executable: gmake - found > ===>   openocd-0.4.0.r2 depends on shared library: ftdi - found > > and there are some addtional libraries/includes passed t

Re: [Openocd-development] FreeBSD status of 0.4.0-RC2 (was: FreeBSD status of 0.4.0-RC1)

2010-02-14 Thread CeDeROM
On Mon, Feb 15, 2010 at 12:43 AM, Xiaofan Chen wrote: > On Mon, Feb 15, 2010 at 8:35 AM, CeDeROM wrote: >> Xiao, the port is a some kind of a program plug into a FreeBSD system >> - for a program to work on a FreeBSD it must have its own Port, also >> any change in the program code may be done on

Re: [Openocd-development] FreeBSD status of 0.4.0-RC2 (was: FreeBSD status of 0.4.0-RC1)

2010-02-14 Thread Xiaofan Chen
On Mon, Feb 15, 2010 at 8:35 AM, CeDeROM wrote: > If you want to test the latest 0.4.0-rc2 source code, please download > this unapproved port package and uncompress it into /usr/ports/devel: > http://files.tomek.cedro.info/stuff/openocd-040-rc2.tar.gz > > If you want to get the sources from a GI

Re: [Openocd-development] FreeBSD status of 0.4.0-RC2 (was: FreeBSD status of 0.4.0-RC1)

2010-02-14 Thread Xiaofan Chen
On Mon, Feb 15, 2010 at 8:35 AM, CeDeROM wrote: > Xiao, the port is a some kind of a program plug into a FreeBSD system > - for a program to work on a FreeBSD it must have its own Port, also > any change in the program code may be done only within its Port - what > you get from a binary is a resul

Re: [Openocd-development] FreeBSD status of 0.4.0-RC2 (was: FreeBSD status of 0.4.0-RC1)

2010-02-14 Thread CeDeROM
On Sun, Feb 14, 2010 at 3:26 PM, Xiaofan Chen wrote: > Do you need to run 8-CURRENT in order to get this latest port? > It seems 8.0-RELEASE ships with an old version of libftdi > and it does not work with OpenOCD. I also could not got > the latest git to build under FreeBSD. Xiao, the port is a

Re: [Openocd-development] FreeBSD status of 0.4.0-RC1

2010-02-14 Thread CeDeROM
On Sun, Feb 14, 2010 at 12:11 AM, David Brownell wrote: >> -It is better to name package openocd-0.4.0rc1.tar.gz than >> openocd-0.4.0-rc1.tar.gz, as there are some other system conventions >> that forbids using "-" and "_" mark after the program number (ie. >> "-devel" or "_n" for revision number

Re: [Openocd-development] dsp56371 crash

2010-02-14 Thread David Brownell
On Sunday 14 February 2010, Mathias K. wrote: > here the patch to fix the crash and create the reg list. Merged, thanks. > Now another Problem with gdb: > > User : 340 52745 gdb_server.c:106 gdb_last_signal(): undefined debug reason 6 > - target needs reset I think we've seen that before in o

Re: [Openocd-development] OpenOCD 0.4.0-RC2 Fedora RPM

2010-02-14 Thread Dean Glazeski
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'll post my own results a > bit

Re: [Openocd-development] FreeBSD status of 0.4.0-RC1

2010-02-14 Thread Øyvind Harboe
> -I cannot build the ZY1000 minidriver: Try the --enable-dummy-minidriver. It tests 90% of buildability of that driver model and it can be built without any funky setup, ditto for the --enable-dummy(but it doesn't exercise the minidriver model). -- Øyvind Harboe Visit us at Embedded World, Marc

Re: [Openocd-development] SVF player - fail to run command

2010-02-14 Thread simon qian
Try adding '-d3' option, and post the log info. 2010/2/14 Vaclav Peroutka > Hello all, > > I compiled git HEAD revision of openocd today and try to program XC9572 > with SVF generated by Xilinx ISE 10.1. I use following openocd.cfg: > telnet_port > gdb_port > interface ft2232 > ft2232_

Re: [Openocd-development] FreeBSD status of 0.4.0-RC2 (was: FreeBSD status of 0.4.0-RC1)

2010-02-14 Thread CeDeROM
On Sun, Feb 14, 2010 at 4:37 PM, Xiaofan Chen wrote: > Yeah I think openocd-devel port is the way to go. I do not really > like the port system very much due to the fact that many > mirrors are dead. The binaries are also not often updated. > Many ports are actually quite outdated. Almost all por

Re: [Openocd-development] [PATCH 1/2] arm11: allow minidrivers to implement inner loop of memory writes

2010-02-14 Thread Øyvind Harboe
On Sat, Feb 13, 2010 at 10:29 PM, David Brownell wrote: > On Tuesday 09 February 2010, Ųyvind Harboe wrote: >> This allows minidrivers to e.g. hardware accelerate memory >> writes. >> >> Same trick as is used for arm7/9 dcc writes. >> >> Added error propagation for memory transfer failures in >> c

Re: [Openocd-development] at91sam7 broken with v0.4.0-rc2

2010-02-14 Thread Timo Boettcher
Hi! * Freddie Chopin wrote: > > Info : 155 2398 core.c:1350 jtag_interface_init(): clock speed 6000 kHz > > Are you sure about the 6MHz JTAG clock? It worked with the SAME configfiles with openocd from 20091229. > Is the core frequency above 40MHz after reset? it is set in a procedure in the con

[Openocd-development] IEEE Standard 1149.7

2010-02-14 Thread David Brownell
Ratified in December http://grouper.ieee.org/groups/1149/7/ And evidently published last week. If anyone finds a good technical summary of what this covers, in particular details of how its JTAG router functionality works -- I've seen suggestions that it's changed since the summaries I f

Re: [Openocd-development] at91sam7 broken with v0.4.0-rc2

2010-02-14 Thread David Brownell
I'm suspecting your config files are set up wrong. On Sunday 14 February 2010, Timo Boettcher wrote: > Info : 155 2398 core.c:1350 jtag_interface_init(): clock speed 6000 kHz That's fishy. Atmel chips are pretty consistent about always running at "slow clock" -- 32 KiHz -- after reset. Which me

Re: [Openocd-development] GPL violations (ftd2xx)

2010-02-14 Thread Freddie Chopin
On 2010-02-14 18:28, Freddie Chopin wrote: > ... the third is ancient (r200-something) ... Sorry - multiply that by 7.5 (r1500-something). There are other versions in the same place too. 4\/3!! ___ Openocd-development mailing list Openocd-development@l

[Openocd-development] GPL violations (ftd2xx)

2010-02-14 Thread Freddie Chopin
Hi [; You do remember the ftd2xx case? I clearly remember some of OpenOCD leaders stating that any violation of GPL (distributing OpenOCD linked to ftd2xx) will be legally fought, courts and various organizations would be informed, etc.. Yet today I've found a fourth case of violating this "ru

Re: [Openocd-development] at91sam7 broken with v0.4.0-rc2

2010-02-14 Thread Freddie Chopin
> Info : 155 2398 core.c:1350 jtag_interface_init(): clock speed 6000 kHz Are you sure about the 6MHz JTAG clock? Is the core frequency above 40MHz after reset? Why don't you use standard cfg files? BTW - LPC2103 works perfectly fine with rc2, but at 1MHz, not 6. 4\/3!!

Re: [Openocd-development] FreeBSD status of 0.4.0-RC1

2010-02-14 Thread Xiaofan Chen
On Mon, Feb 15, 2010 at 12:26 AM, CeDeROM wrote: > Well, in FreeBSD you don't build the packages yourself from scratch - > this is the reason that Ports exists - to be able to build the package > from source with some options enabled/disabled, but the OS specific > quirks are done by the maintaine

Re: [Openocd-development] FreeBSD status of 0.4.0-RC1

2010-02-14 Thread Xiaofan Chen
On Mon, Feb 15, 2010 at 12:26 AM, CeDeROM wrote: > If you have installed the GDM package, then the only thing to place in > /etc.rc.conf is to enable the gdm and it will take care of everything > else (HAL/DBUS): > gnome_enable="YES" > Yes that is the key here. Thanks for the hint. Now I am typin

[Openocd-development] OpenOCD v0.4.0-rc2 RPM for Mandriva 2010.0 and Fedora 12

2010-02-14 Thread Michel Catudal
For those interested I have some RPM for the OpenOCD RC2 on my web site. I have Mandriva 2010.0 and Fedora 12 RPM files, both source and binaries. If you want to test openocd with setedit I also have new binaries for setedit. I haven't updated sourceforge with those yet. The setedit and turbo vis

Re: [Openocd-development] FreeBSD status of 0.4.0-RC1

2010-02-14 Thread CeDeROM
On Sun, Feb 14, 2010 at 4:11 PM, Xiaofan Chen wrote: > On Sun, Feb 14, 2010 at 11:49 PM, CeDeROM wrote: > >> Xorg will autoconfigure though HAL and DBUS so you should have these >> installed. If you install gnome2 (pkg_add -r gnome2 xorg) it will >> download and install via network full working X

Re: [Openocd-development] FreeBSD status of 0.4.0-RC1

2010-02-14 Thread Xiaofan Chen
On Sun, Feb 14, 2010 at 11:49 PM, CeDeROM wrote: > Xorg will autoconfigure though HAL and DBUS so you should have these > installed. If you install gnome2 (pkg_add -r gnome2 xorg) it will > download and install via network full working X environment for you > with just one command :-) Just did t

[Openocd-development] at91sam7 broken with v0.4.0-rc2

2010-02-14 Thread Timo Boettcher
Hi! I just tried openocd-0.4.0-rc2 with my olimex-arm-usb-ocd on at91sam7, but it doesn't work anymore. Log is attached below. I will git bisect it if necessary (if so, please tell me), known working (but not necessarily last working) version was from 20091229. Current head (a2ce3a51dfbc9760e

Re: [Openocd-development] FreeBSD status of 0.4.0-RC1

2010-02-14 Thread CeDeROM
Hello Xiao! :-) On Sun, Feb 14, 2010 at 3:26 PM, Xiaofan Chen wrote: > On Sun, Feb 14, 2010 at 7:38 AM, CeDeROM wrote: > > I have now a working 8.0-Release system, only console though. X > is kind of working, but no keyboard and mouse, so not really > useful, tried the vesa driver and the nvidia

Re: [Openocd-development] FreeBSD status of 0.4.0-RC1

2010-02-14 Thread Xiaofan Chen
On Sun, Feb 14, 2010 at 7:38 AM, CeDeROM wrote: I have now a working 8.0-Release system, only console though. X is kind of working, but no keyboard and mouse, so not really useful, tried the vesa driver and the nvidia driver port. But never mind, I will solve this later. > -The issue with FT2232

Re: [Openocd-development] Windows 64-bit version tests

2010-02-14 Thread Freddie Chopin
On 2010-02-12 21:21, karrbd wrote: > I tried a few Windows OSes with this 64-bit build: > > When installing the driver on Win7 x64, Vista x64, and WinXP x64 it fails > with "A service section in this INF is invalid." > > I tried this with JTAGkey2 and Olimex ARM-USB-TINY. > > Let me know what other

[Openocd-development] OpenOCD-0.4.0-rc2 for Windows

2010-02-14 Thread Freddie Chopin
I've just posted the packages with 0.4.0-rc2 for Windows on my website www.freddiechopin.info > Download > Software > OpenOCD dev I've also posted the original 0.4.0-rc1 for reference if someone wishes to try that too. Happy testing! 4\/3!! ___ Openo

Re: [Openocd-development] dsp56371 crash

2010-02-14 Thread Mathias K.
Hello, here the patch to fix the crash and create the reg list. Now another Problem with gdb: User : 340 52745 gdb_server.c:106 gdb_last_signal(): undefined debug reason 6 - target needs reset Regards, Mathias Am 14.02.2010 07:33, schrieb David Brownell: > On Saturday 13 February 2010, Aust

Re: [Openocd-development] FreeBSD status of 0.4.0-RC1

2010-02-14 Thread Xiaofan Chen
On Sun, Feb 14, 2010 at 7:22 PM, CeDeROM wrote: >> Still the same result, Release 8.0 failed to boot for my PC. I just >> tried the USB image and it immediately failed (dumping some >> resister contents) after I hit enter on the boot menu. This is >> similar to what I have tried before (including

Re: [Openocd-development] FreeBSD status of 0.4.0-RC1

2010-02-14 Thread CeDeROM
Hello Xiao! On Sun, Feb 14, 2010 at 4:34 AM, Xiaofan Chen wrote: >> Probably I will try it later, maybe with a Live CD first to see if it boots. >> Last time I spent sometime to get USB things working under FreeBSD. >> http://mcuee.blogspot.com/search/label/FreeBSD > > Still the same result, Rele