Committed.
Thanks!
--
Øyvind Harboe
Embedded software and hardware consulting services
http://consulting.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
The current macro uses a wrong value, and thus can generate
invalid MIPS instructions.
---
src/target/mips32.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/src/target/mips32.h b/src/target/mips32.h
index 7a4dd5e..e13707d 100644
--- a/src/target/mips32.h
+++ b/src/targe
Committed.
Thanks!
--
Øyvind Harboe
Embedded software and hardware consulting services
http://consulting.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Oleksandr Tymoshenko a écrit :
> Hi
>
> I'm trying to use openocd for debugging MIPS target but it seems
> that EJTAG support still lacks some features and has some bugs.
> I fixed several but it's still work in progress. Attached is the first
> (and very small) patch that fixes restoring CPU con
Hi,
due to a strange (unfixable) HW issue, I need to flash a few initial bytes
without any CPU support (ARM1176 in my case). After that, the code download
method with the working area can be used for the remaining process.
I can switch between both methods by dis/enabling the line
carm11.cpu conf
Hey guys,
does anyone know where can I find the ARM register context structure in
openocd code ? Where is it implemented ?
thanks!
Jesus
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinf
Hey guys,
I'm running OpenOCD here, trying to debug a LPC-2124, using a Wiggler's
compatible cable. I'm using the lpc2124.cfg (
http://svn.berlios.de/wsvn/openocd/trunk/src/target/target/lpc2124.cfg?rev=1602&sc=1
).
Well, I connect to the server with GDB, and can do some several commands:
- mon
Hi
I'm trying to use openocd for debugging MIPS target but it seems
that EJTAG support still lacks some features and has some bugs.
I fixed several but it's still work in progress. Attached is the first
(and very small) patch that fixes restoring CPU context for "resume"
command.
--
gonzo
dif
Dirk Behme wrote:
>
> Btw.: Is there an option or a possibility to run a script when I
> connect e.g. by telnet?
>
> I'm a little tired to always type the commands
>
> jtag tapenable omap3.cpu
> target create omap3.cpu cortex_a8 -endian little -chain-position
> omap3.cpu
> dap apsel 1
> omap3.cpu
Hi Magnus,
Magnus Lundin wrote:
> Hi Dirk
>
> Very good, I think we can commit this immediatleay as a place to collect
> the info about A8.
Wow, that was fast :)
> I now have a BeagleBoard :),
Great!
> so testing can be made more efficient,
> JTAG solution will be working at the end of t
On Mon, 2009-05-04 at 12:21 +0200, Uwe Hermann wrote:
> Hi,
>
> I uploaded a new Debian package of OpenOCD recently (based on r1583)
> which produced a number of build warnings (now errors because of
> -Werror). Haven't had the time to look into the issues, but the build
> logs could be useful for
On Mon, May 4, 2009 at 8:43 PM, Michael Schwingen
wrote:
> Øyvind Harboe wrote:
>> How old are these CPUs?
>>
>> What was the last release date of a CPU with a BDM protocol?
>>
> We used BDM on the MPC85x/MPC86x series, probably about 8-9 years ago now.
>
> I think the current Freescale PowerPC se
I've got a beagleboard too.
Looking forward to testing your upcoming
board/beagleboard.cfg script ;-)
--
Øyvind Harboe
Embedded software and hardware consulting services
http://consulting.zylin.com
___
Openocd-development mailing list
Openocd-developm
Øyvind Harboe wrote:
> How old are these CPUs?
>
> What was the last release date of a CPU with a BDM protocol?
>
We used BDM on the MPC85x/MPC86x series, probably about 8-9 years ago now.
I think the current Freescale PowerPC series use JTAG/COP instead of
BDM. Support for MPX82xx/MPC83xx woul
Committed.
Thanks!
--
Øyvind Harboe
Embedded software and hardware consulting services
http://consulting.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-developmen
Hi Dirk
Very good, I think we can commit this immediatleay as a place to collect
the info about A8.
I now have a BeagleBoard :), so testing can be made more efficient,
JTAG solution will be working at the end of the week, strange pinout and
low voltage.
The magic sequence for unlocking debug
Patch in attachment is a minimalist copy of Cortex M3 code to be able
to create a Cortex A8 target and use it for our OMAP3 investigation (*).
Idea is to extend this step by step with increasing knowledge.
Many thanks to Magnus for all the help with OMAP3!
Best regards
Dirk
(*) Commands th
Magnus Lundin wrote:
> tangray wrote:
>> Trying to access Debug Reister Interface with mdw I get
>>
>>> omap3.cpu mdw 0x54011d00
>>>
>>
>> 0x54011d00 411fc082...A
>>
>> Looking at Cortex-A8 TRM, it seems OK.
>>
>>> omap3.cpu mdw 0x54011088
>>>
>> AHBAP
tangray wrote:
> Trying to access Debug Reister Interface with mdw I get
>
>
>
>
>
>> omap3.cpu mdw 0x54011d00
>>
>
>
> 0x54011d00 411fc082...A
>
> Looking at Cortex-A8 TRM, it seems OK.
>
>
>
>
>> omap3.cpu mdw 0x54011088
>>
>
> AHBAP Cached values: d
On Mon, 4 May 2009, Øyvind Harboe wrote:
On Mon, May 4, 2009 at 3:03 PM, Alan Carvalho de Assis
wrote:
There is two types of BDM interfaces. The old interface is used on
some microcontrollers like Coldfire V2 (MCF5272, MCF5282, etc) and
other (with less wires) used on Coldfire V1 (MCF51JM, etc
On Mon, May 4, 2009 at 3:03 PM, Alan Carvalho de Assis
wrote:
> Hi Zach,
>
> On 5/1/09, Zach Welch wrote:
>> - Coldfire (suggested by NC)
>> - can we draw from the BDM project? http://bdm.sourceforge.net/
>>
>
> I think BDM support will be great!
>
> There is two types of BDM interfaces. T
Trying to access Debug Reister Interface with mdw I get
> omap3.cpu mdw 0x54011d00
0x54011d00 411fc082...A
Looking at Cortex-A8 TRM, it seems OK.
> omap3.cpu mdw 0x54011088
AHBAP Cached values: dp_select 0x0, ap_csw 0xc3800042, ap_tar 0x54011088
SWJ-DP ST
Hi Zach,
On 5/1/09, Zach Welch wrote:
> - Coldfire (suggested by NC)
> - can we draw from the BDM project? http://bdm.sourceforge.net/
>
I think BDM support will be great!
There is two types of BDM interfaces. The old interface is used on
some microcontrollers like Coldfire V2 (MCF5272,
Committed patches 1-4.
Thanks!
--
Øyvind Harboe
Embedded software and hardware consulting services
http://consulting.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-
Committed.
Thanks!
--
Øyvind Harboe
Embedded software and hardware consulting services
http://consulting.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
On Mon, May 04, 2009 at 12:21:53PM +0200, Uwe Hermann wrote:
> Hi,
>
> I uploaded a new Debian package of OpenOCD recently (based on r1583)
> which produced a number of build warnings (now errors because of
> -Werror). Haven't had the time to look into the issues, but the build
> logs could be use
Hi,
I uploaded a new Debian package of OpenOCD recently (based on r1583)
which produced a number of build warnings (now errors because of
-Werror). Haven't had the time to look into the issues, but the build
logs could be useful for others:
https://buildd.debian.org/pkg.cgi?pkg=openocd
Please fo
27 matches
Mail list logo
