I've got an i.MX31 in my office.
The ARM11 code is missing important code...
/* architecture specific status reply */
int arm11_arch_state(struct target_s *target)
{
FNC_INFO_NOTIMPLEMENTED;
return ERROR_OK;
}
/* target request support */
int arm11_target_request_data(struct t
Renato> Anybody has ever connected to an ARM 1136 with J-Link?
Renato> [specifically: Freescale IMX31 - PDK board]
I do not know about JLINK - but - that is a separate issue.
But - Several Freescale FAE types lurk on this mailing list and answer
questions when they can.
https://lists.berl
On Wed, Dec 17, 2008 at 11:10:53PM +0100, Michael Schwingen wrote:
> lou.openocd...@fixit.nospammail.net wrote:
> >
> >> or speed_table.c should be compiled separately and linked
> >> in.
> >>
> >
> > It could be. Would I need to do anything other than add rlink_speed_table.o
> > to RLINKFIL
Hello All,
I'm new to OpenOCD, just got v1220 and trying to use a JLink (IAR) probe on
Freescale's i.MX31PDK board, [http://www.freescale.com/imx31pdk]. i.MX31 has
an ARM1136 CPU, I'm receiving some errors when starting OpenOCD, perhaps you
could point me a direction here.
I'm issuing the followi
various> [whats up with beagle board]
All - FYI - I received a beagle today
I have to find a few cables (hdmi to vga), power supply (I have) - etc
to hook it up etc.
An early toy for Xmas vacation play time. I am amazed at how small this
thing is!
-Duane.
_
lou.openocd...@fixit.nospammail.net wrote:
>
>> or speed_table.c should be compiled separately and linked
>> in.
>>
>
> It could be. Would I need to do anything other than add rlink_speed_table.o
> to RLINKFILES in src/jtag/Makefile.am, rename rlink/speed_table.c to
> rlink_speed_table.c, ch
On Dec 17, 2008, at 1:36 PM, lou.openocd...@fixit.nospammail.net wrote:
I saw this thread in the archives, but wasn't subscribed at the
time, so
I cannot reply directly.
https://lists.berlios.de/pipermail/openocd-development/2008-November/003742.html
It has come to my attention that the STM3
I saw this thread in the archives, but wasn't subscribed at the time, so
I cannot reply directly.
https://lists.berlios.de/pipermail/openocd-development/2008-November/003742.html
It has come to my attention that the STM32 Primer2, while it uses the
same RLink chip that the STM32 Primer does, doesn
On Dec 17, 2008, at 10:03 AM, lou.openocd...@fixit.nospammail.net wrote:
On Wed, Dec 17, 2008 at 08:57:14AM -0800, Rick Altherr wrote:
On Dec 17, 2008, at 3:01 AM, Øyvind Harboe wrote:
We've got lots of other examples, e.g. the at91fr40162 flash driver
contains
a .elf file that is compiled
On Wed, Dec 17, 2008 at 08:57:14AM -0800, Rick Altherr wrote:
>
> On Dec 17, 2008, at 3:01 AM, Øyvind Harboe wrote:
>
>> We've got lots of other examples, e.g. the at91fr40162 flash driver
>> contains
>> a .elf file that is compiled with an arm-elf toolchain using eCos
>> source.
>> We're *NOT*
On Dec 17, 2008, at 9:06 AM, Dirk Behme wrote:
Before I can think about further testing or help, I'd like to be on
a confirmed status level.
I believe the best status anyone has encountered is: the BeagleBoard
boots and OpenOCD sees the Flyswatter. There is no success in setting
up the
> --enable-ft2232_ftd2xx
> --with-ftd2xx
>
> and
>
> --enable-ft2232_libftdi
> --with-libftdi
First time I tried to build on BSD, I read the docs, did some
searching on configure, and assumed this would work, which it did not,
of course. My alternative was to hack the makefiles and/or hack
CFLAGS
Rick Altherr wrote:
> I haven't tried getting OpenOCD to validate the JTAG chain. The config
> file seems appropriate, but the error messages indicate a JTAG
> problem. The EMU0 and EMU1 jumpers shouldn't matter as the default
> configuration is the JRC is the only enabled tap. I'm trying
Rick Altherr wrote:
>
> On Dec 16, 2008, at 11:45 PM, Dirk Behme wrote:
>
>> 1. Path given with --with-ftd2xx is ignored at openocd's link time. I
>> think we need something like adding "-L" to build
>> tooling for linking. I already had a look to this, but was lost in
>> Makefile generation :(
>
I haven't tried getting OpenOCD to validate the JTAG chain. The
config file seems appropriate, but the error messages indicate a JTAG
problem. The EMU0 and EMU1 jumpers shouldn't matter as the default
configuration is the JRC is the only enabled tap. I'm trying to find
some time to work
On Dec 17, 2008, at 3:01 AM, Øyvind Harboe wrote:
*) The xscale target does something similar with its debug binary,
which
tells me it's acceptable if not preferable.
I vote for keeping it simple & robust. The procedure should be
described and committed
to SVN, but it can be done manually f
On Dec 16, 2008, at 11:45 PM, Dirk Behme wrote:
1. Path given with --with-ftd2xx is ignored at openocd's link time. I
think we need something like adding "-L" to build
tooling for linking. I already had a look to this, but was lost in
Makefile generation :(
Should be relatively simple in Mak
On Dec 16, 2008, at 10:45 PM, SimonQian wrote:
Hi,
It's not problem with OpenOCD, but with arm-none-eabi-gdb.exe.
Reference to the discussed topic "Problem with GDB 6.8".
My log is similar with Ramon's.
I cut some information from his log:
Debug: 700 10078 gdb_server.c:1997 gdb_input_inner()
I'd like to reproduce recent OpenOCD status with Beagleboard (and then
maybe help/test?):
I use OpenOCD svn version 1245 from yesterday with openocd.cfg and
beagleboard.cfg in attachment (mainly from [1]). I use libFTDI and
Flyswatter with TinCanTools Beagleboard adapter kit. BeagleBoard run
Spencer Oliver wrote:
> I am looking into a few various methods.
> using the ejtag fastarea + stub should give the greatest speed increase for
> non-dma targets - its finding time.
I thought about this way: A special load_internal_image cmd executed
with a flash-address reads the elf image header
On Wed, Dec 17, 2008 at 12:01:05PM +0100, Øyvind Harboe wrote:
> > *) The xscale target does something similar with its debug binary, which
> > tells me it's acceptable if not preferable.
>
> I vote for keeping it simple & robust. The procedure should be
> described and committed
> to SVN, but it
On Tue, Dec 16, 2008 at 09:16:43PM -, Spencer Oliver wrote:
> >
> > Attached, is a patch against the svn trunk that adds support
> > for the Raisonance RLink JTAG adapter.
...
>
> It would be good to include the rlink (i have a few lying around) but am
> unsure we could without
> permission
Øyvind Harboe wrote:
>> *) The xscale target does something similar with its debug binary, which
>> tells me it's acceptable if not preferable.
>>
>
> I vote for keeping it simple & robust. The procedure should be
> described and committed
> to SVN, but it can be done manually for files which
duane> [declare 1.0]
dirk> For 1.0 I'd like to have proper handling of --with-ftd2xx path:
Agreed.
dirk> I think we need something like adding "-L" to
build tooling for linking. I already had a look to this, but was lost in
Makefile generation
I solved it another way - by passing CFLAGS throu
> *) The xscale target does something similar with its debug binary, which
> tells me it's acceptable if not preferable.
I vote for keeping it simple & robust. The procedure should be
described and committed
to SVN, but it can be done manually for files which are updated once in a
blue moon. I'd s
Bearing in mind that any changes are moot until we know whether the
patch will even be acceptable with them (Spencer Oliver's concern, for
instance)...
On Tue, Dec 16, 2008 at 07:30:59PM -0800, Rick Altherr wrote:
>
> On Dec 16, 2008, at 9:25 AM, lou.openocd...@fixit.nospammail.net wrote:
>
>> At
26 matches
Mail list logo
