[OpenOCD-devel] Problems using OpenOCD with Eclipse CDT on Stellaris Cortex-M3

2012-01-11 Thread Sergio
Hi list, >From las six months I'm trying to work with eclipse+cdt+openocd to debug a application. Googling, I can make some results but I don't know how continue. Please, help. I'm using openocd (try with devel version from hit repo and with las stable, the result is the same), debuging with gdb 7.

Re: [OpenOCD-devel] Problems using OpenOCD with Eclipse CDT on Stellaris Cortex-M3

2012-01-11 Thread Mathias K.
Do you use a gdb start script? Look like your code is not uploaded and you try to debug the "old" application. On 11.01.2012 11:19, Sergio wrote: > Hi list, >>From las six months I'm trying to work with eclipse+cdt+openocd to > debug a application. Googling, I can make some results but I don't >

Re: [OpenOCD-devel] TI DM8148, Cortex A8 not halting (OpenOCD 0.5.0 and 0.6.0-dev-00297-g115f538)

2012-01-11 Thread Delio Brignoli
On 10/01/2012, at 14:46, Kyle Manna wrote: > On 01/10/2012 03:38 AM, Delio Brignoli wrote: >> Hi Kyle, >> >> No I haven't tried the XDS100v2 yet because the issue does not seem to be >> related to the debugger HW. As you say, the issue appears to be lack of >> documentation. My immediate need fo

[OpenOCD-devel] gdb error: Remote 'g' packet reply is too long

2012-01-11 Thread Reinhard Biegel
Hi! I'm running openocd (svn) with a J-Link EDU interface to program and debug a STM32Lxxx. When connecting gdb to the openocd gdbserver I receive: "Remote 'g' packet reply is too long: ." Found that post on stackoverflow, where the author suggests a solution: http://stackoverflow.com/questi

Re: [OpenOCD-devel] gdb error: Remote 'g' packet reply is too long

2012-01-11 Thread Øyvind Harboe
Please create a commit and push your fix to Gerrit. Read HACKING for details. We can't submit the workaround, but at least we have a record of it and hopefully someone can rewrite your fix to include the necessary mechanics... -- Øyvind Harboe - Can Zylin Consulting help on your project? US t

Re: [OpenOCD-devel] gdb error: Remote 'g' packet reply is too long

2012-01-11 Thread Spencer Oliver
On 11 January 2012 12:50, Reinhard Biegel wrote: > Hi! > > I'm running openocd (svn) with a J-Link EDU interface to program and debug a > STM32Lxxx. When connecting gdb to the openocd gdbserver I receive: > "Remote 'g' packet reply is too long: ." > > Found that post on stackoverflow, where th

Re: [OpenOCD-devel] gdb error: Remote 'g' packet reply is too long

2012-01-11 Thread Reinhard Biegel
Sounds good. Sorry, I didn't notice the existence trac on sourceforge. Reinhard On Wednesday 11 January 2012 13:06:58 Spencer Oliver wrote: > This has been an issue for some time. > It also depends on whether you are using mainline gdb or one from > codesourcery. > > I have not looked into it fo

Re: [OpenOCD-devel] gdb error: Remote 'g' packet reply is too long

2012-01-11 Thread Sergio
I have this problem in the pass. Then I chage to 7.2 version... but I have other problems. What is the right version of gdb to work with openocd? (Not of the codesourcery, the standar version from the gdb standar source code) Thank's Sergio 2012/1/11 Spencer Oliver : > On 11 January 2012 12:50, Re

Re: [OpenOCD-devel] gdb error: Remote 'g' packet reply is too long

2012-01-11 Thread Sergio
Hi, I'm testing differents versions of gdb to use with openocd. With all versions tested I have problems (diferents) when using gdb + cdt + eclipse + openocd. The only version with all work is the binary version of the codesourcery. I try build gdb from source (version 7.2, the version used in code

Re: [OpenOCD-devel] gdb error: Remote 'g' packet reply is too long

2012-01-11 Thread Paul Fertser
On Wed, Jan 11, 2012 at 12:13:02PM -0300, Sergio wrote: > There are some patch or specific version for gdb to use with openocd? > I'm using openocd version 5.0 This is what i had to use in .gdbinit to get rid of the error: set tdesc filename OpenOCD/target.xml set architecture arm Where OpenOCD/

[OpenOCD-devel] [PATCH]: 3ad77e6 ignore - jenkins mingw fail test

2012-01-11 Thread gerrit
This is an automated email from Gerrit. Spencer Oliver (s...@spen-soft.co.uk) just uploaded a new patch set to Gerrit, which you can find at http://openocd.zylin.com/365 -- gerrit commit 3ad77e6c8799830770260a26d5dfe1e59b41d904 Author: Spencer Oliver Date: Wed Jan 11 20:56:10 2012 +

Re: [OpenOCD-devel] Swd on stlink

2012-01-11 Thread Jonathan Dumaresq
Hi, Spencer Oliver wrote: > On 10 January 2012 15:11, Jonathan Dumaresq > wrote: >> Hi all, >> >> Is there a way to use an stlink with swd right now with openocd ? I >> will use the stm32 M0 devices >> > > Only the stlink-v2 is supported at the moment - swd mode is used by > default. > With

Re: [OpenOCD-devel] Swd on stlink

2012-01-11 Thread Mathias K.
Hello, the function will abort because it's not implemented yet: if (size != 4) { LOG_DEBUG("%s %x %d %d", __func__, address, size, count); return ERROR_COMMAND_SYNTAX_ERROR; } The size is 2 (for 16bit) and the read aborts. There is a missing wrapp

Re: [OpenOCD-devel] Problems using OpenOCD with Eclipse CDT on Stellaris Cortex-M3

2012-01-11 Thread Andreas Fritiofson
On Wed, Jan 11, 2012 at 11:19 AM, Sergio wrote: > Hi list, > >From las six months I'm trying to work with eclipse+cdt+openocd to > debug a application. Googling, I can make some results but I don't > know how continue. Please, help. > I'm using openocd (try with devel version from hit repo and wi

Re: [OpenOCD-devel] gdb error: Remote 'g' packet reply is too long

2012-01-11 Thread Sergio
Thank's! Now work fine! Where can I read about this file and his function? Again, thank's very much thank's Sergio 2012/1/11 Paul Fertser : > On Wed, Jan 11, 2012 at 12:13:02PM -0300, Sergio wrote: >> There are some patch or specific version for gdb to use with openocd? >> I'm using openocd ve

Re: [OpenOCD-devel] gdb error: Remote 'g' packet reply is too long

2012-01-11 Thread Peter Stuge
Paul Fertser wrote: > > There are some patch or specific version for gdb to use with openocd? > > I'm using openocd version 5.0 > > This is what i had to use in .gdbinit to get rid of the error: > > set tdesc filename OpenOCD/target.xml > set architecture arm > > Where OpenOCD/target.xml is the