Hello,
backtrace from current git repo source.
Regards,
Mathias
---
openocd: core.c:421: jtag_add_scan_check: Assertion `(field->check_value ==
((void *)0)) ||
(field->in_value != ((void *)0))' failed.
Program received signal SIGABRT, Aborted.
0xe424 in __kernel_vsyscall ()
(gdb) bt fu
Hello,
you can try to use the offset parameter (flash bank address):
flash write_image 0x0800
Regards,
Mathias
On 15.12.2011 01:31, Damjan Marion wrote:
>
> Hi,
>
> I tried to flash STM32 F2 in the same way like i do on F1 devices and hit
> some issues:
>
> My 1st try was with "stm32
Hello,
the commands doesn't work for me too. You can use flash erase_sector and flash
write_bank.
Regards,
Mathias
On 15.12.2011 01:31, Damjan Marion wrote:
>
> Hi,
>
> I tried to flash STM32 F2 in the same way like i do on F1 devices and hit
> some issues:
>
> My 1st try was with "stm32f
On 30.11.2011 01:46, Peter Stuge wrote:
> Mathias K. wrote:
>> If i try to push i can choose the review as target but it will
>> always pushed into the master and i got a error message.
>> The console command "git push review" works. Any hints?
>
> Can you ch
Hello,
i have a little problem with git gui to push the commits to the review server.
If i try to push i
can choose the review as target but it will always pushed into the master and i
got a error message.
The console command "git push review" works. Any hints?
Thanks & Regards,
Mathias
_
Hello,
> Em 28-10-2011 05:35, Jon Povey escreveu:
>> In fact I would get rid of [Openocd-development] too. There are headers
>> for sorting mail, other mailing lists I use don't have this, and are
>> more usable for that IMO.
>
> -1
> What about making it much shorter, like: [oocd-dev]
the subje
Hello,
Am 31.10.2011 06:10, schrieb Peter Stuge:
> Mathias K. wrote:
>>>> can you remove the magic incomplete number too?
>>>>
>>>> In this case the "1533d9d". This number is useless in the subject:
>>>
>>> I disagree. This is a
Hello,
Am 28.10.2011 20:15, schrieb Peter Stuge:
> Mathias K. wrote:
>> can you remove the magic incomplete number too?
>>
>> In this case the "1533d9d". This number is useless in the subject:
>
> I disagree. This is an abbreviated commit hash, which id
covered by
asserts
Regards,
Mathias
Am 28.10.2011 20:03, schrieb Mathias K.:
> Hello,
>
> can you remove the magic incomplete number too?
>
> In this case the "1533d9d". This number is useless in the subject:
>
> [Openocd-development] openocd patch: 1533d9d
Hello,
can you remove the magic incomplete number too?
In this case the "1533d9d". This number is useless in the subject:
[Openocd-development] openocd patch: 1533d9d cfi: unsupported code paths are
now covered by asserts
Now we have 2 times openocd as static text left. Do you think we need it
Hello,
is there any chance to reduce the gerrit subject line to a normal length with
more information at
the beginning? Currently the subject consist of 50% static text at the
beginning.
[Openocd-development] New patch to review for openocd: XXX bugfixes:
Thanks,
Mathias
Ups,
sorry, this is our guideline:
http://openocd.sourceforge.net/doc/doxygen/html/index.html
Regards,
Mathias
Am 25.10.2011 22:44, schrieb Mathias K.:
> Hello,
>
> you should update
> http://openocd.sourceforge.net/doc/doxygen/html/patchguide.html or remove this
> ugly &qu
Hello,
you should update
http://openocd.sourceforge.net/doc/doxygen/html/patchguide.html or remove this
ugly "Developer's Guide".
Regards,
Mathias
Am 25.10.2011 22:32, schrieb Peter Stuge:
> Mathias K. wrote:
>> 2.) create a ssl certificate
>> and set it in y
Hello Kyle,
the patch works with the TMS570 eval. board. You should use gerrit to submit
the patch.
"Short" instruction that works for me:
1.) register at http://openocd.zylin.com/ with a OPENID (you need a google or
yahoo account (or other))
2.) create a ssl certificate and set it in your pro
Hello,
this is a request to change the filename and (later) the internal names to
tif05.c/.h / tif05 or
something.
Background:
The TMS470R cpu from TI use the F05 Flash Module. The latest chips TMS470MF and
TMS570 use the new
F035 Flash Module. The Flash Modules are quite different and the cu
Hello,
i have append my experimental config files for the ti tms570 usb eval board.
Flash is not supported
by openocd yet. Maybe its useful for someone.
> flash info 0
device_ident_reg = 0x80206d0d
Could not identify part 0x21 as a member of the TMS470 family.
auto_probe failed
in procedure 'fl
Hello,
Am 08.10.2011 12:11, schrieb Øyvind Harboe:
sourceforge does not offer gerrit. Is there a hosting service that does?
gerrit is "only" a proxy before git. You can install it on any machine
and use the gerrit host instead of the git host to work with the repo.
Anyway you can check thi
Am 01.10.2011 09:02, schrieb Øyvind Harboe:
> No mailing list???
No.
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Patch appended.
>From e1fa97a81eba9901b3fa3af9169705d745406661 Mon Sep 17 00:00:00 2001
From: Mathias K.
Date: Wed, 21 Sep 2011 19:18:26 +0200
Subject: add target events, run algorithm and default r/w buffer api
Target events are added to get better gdb support. The run
algorithm functional
Hello,
i have checked the sources to find a way that works for this issue but this
would make a big api
change. Currently there is no way to tell the target write memory function the
kind of memory that
needs to be written. In my case the dsp563xx p,x,y memory.
Would it make sense to change th
Hello,
i prefer something like this (i don't want to start a goto discussion):
if ( tap->hasidcode && (dap_syssec_filter_data[i].idcode == tap->idcode) )
but we should be sure that idcode is initialized with an invalid value like
zero but independent of
the hasidcode flag.
Regards,
Mathias
> + }
> +
>
> 5. propagate (just return) the error code, do not change it:
>
> + if (kinetis_ftfl_command(bank, w0, w1, w2) != ERROR_OK) {
> + return ERROR_FLASH_OPERATION_FAILED;
> + }
> +
> +
>
>
>
>
>
>
>
>From ab35e7489fb125fac84049
Hello,
Am 13.09.2011 15:28, schrieb Oliver Döring:
> I'm having lots of problems with this Toradex board.
>
> I use a custom carrier board without JTAG buffers, so I connected my JTAG-USB
> directly to the
> Colibri FFC JTAG connector. My JTAG adapter is FT2232 based and uses the
> OOCDLink lay
No problem.
Am 12.09.2011 21:49, schrieb Øyvind Harboe:
> Please squash the patches together and repost if they do belong in
> the same patch.
>
> Thanks!
>
>From 1b17ccce801ff322ff5372207d82fb8827b4cbcf Mon Sep 17 00:00:00 2001
From: Mathias K.
Date: Mon, 12 Sep 2011 21:5
Hello,
yes you are right. Changes appended.
Regards,
Mathias
Am 12.09.2011 21:09, schrieb Eric Wetzel:
> On Mon, Sep 12, 2011 at 2:34 PM, Mathias K. wrote:
>> Hello,
>>
>> this patch add support for debug port access on a secured kinetis cpu with
>> mass eras
Hello,
this patch removes the test code used to verify the functionality.
Regards,
Mathias
Am 12.09.2011 16:17, schrieb Mathias K.:
> Hello,
>
> i have done some work on the kinetis cpu flash driver. Erase,write and read
> protection works.
>
>
> Regard
Hello,
this patch add support for debug port access on a secured kinetis cpu with mass
erase enabled.
Regards,
Mathias
>From 63c322864f50d9c3489f498e2f29a508ac9156d8 Mon Sep 17 00:00:00 2001
From: Mathias K.
Date: Mon, 12 Sep 2011 20:28:23 +0200
Subject: [PATCH] kinetis auto mass erase
Hello,
i have done some work on the kinetis cpu flash driver. Erase,write and read
protection works.
Regards,
Mathias
>From 09e1902067fac38e39564c538b6a125e3a0254b6 Mon Sep 17 00:00:00 2001
From: Mathias Kuester
Date: Mon, 12 Sep 2011 16:11:06 +0200
Subject: [PATCH] kinetis cpu flash driver
I get this issue because wrong target alignment. Flash commands works now.
Am 09.09.2011 20:43, schrieb Mathias K.:
> any progress with flash programming? I have tried to start a mass-erase but i
> only get a MSGSTAT0.
> There is no protection enabled, i don't know whats wr
Hello,
is there any way to configure the MDM-AP (AP 1) from the K40-CPU shortly after
ahbap_debugport_init
and before any memory is read from the cpu? The initialization should be called
if the IDCODE match,
like a "blacklist" filter. This is important if the security on this cpu is
enabled.
Hello,
Am 18.06.2011 15:21, schrieb j. m. norris:
> this is still work-in-progress and the writing of the on-chip flash does not
> work. I'm in the process of writing the code for that and I hope to submit
> that soon.
any progress with flash programming? I have tried to start a mass-erase but i
Hello,
the 563xx is already supported by openocd. Symphony Studio works from a win pc
connected to a linux
openocd with a ftdi jtag device connected to the dsp. Breakpoints still not
supported (ported) yet.
Regards,
Mathias
Am 31.08.2011 13:45, schrieb Sam Hawkens:
> Alex, Stefan,
>
> it w
Hello,
eclipse are also able to format to a desired coding style.
I think we should define an indent rule and use it as base. Personally i use
the Allman-Style.
Openocd mix more then two styles, i have seen Allman, K&R and GNU.
Regards,
Mathias
Am 28.08.2011 13:50, schrieb Michael Schwingen:
Hello Tom,
i have this stick too and it would be really nice if you can add flash support
for this cpu.
Regards,
Mathias
Am 23.08.2011 23:23, schrieb Tom Cauchois:
> Hi,
>
> I'm bringing up the TMS570 usb stick devkit (part# TMDX570LS20SUSB) with
> OpenOCD.
>
> I've gotten the target co
Hello,
Am 26.06.2011 14:30, schrieb Amit kumar:
> I am following "http://elinux.org/BeagleBoardOpenOCD";, I am new to Openocd
> and bank on the support
> of this list.
./configure --enable-ft2232_ftd2xx
--with-ftd2xx-linux-tardir=/libftd2xx0.4.16
--prefix=/home/user/bin/openOCD
is not
> Also,
Am 03.05.2011 22:12, schrieb Jie Zhang:
> I'm not familiar with ARM targets. So I'm not very sure. My guess is
> this can also improve performance on ARM targets but they needs be
> adapted to this lazy read usage.
Your blackfin is fast enough. This "read usage" only affect you if you rape the
st
I think gdb will get the register list and then, maybe depending on used debug
application, all
register values.
But we should remember that some/all functions in the current implementation,
that need a target
register to work, simple doesn't check if a register already stored or not.
They only
our reply!
>
> I'm adding a new target to OpenOCD. But I think all existing targets in
> OpenOCD have this issue.
> Maybe I missed something...
>
> Jie
>
> On Mon, May 2, 2011 at 12:13 PM, Mathias K. <mailto:kes...@freenet.de>> wrote:
>
> Hello,
Hello,
please tell us more about your target platform.
Regards,
Mathias
Am 02.05.2011 18:06, schrieb Jie Zhang:
> Hi,
>
> I encountered an issue when using OpenOCD with GDB. After GDB connects to
> OpenOCD and halt the
> target, "info reg" command returns all zeros for all registers. I took
Hello,
there are several mechanism to protect or unprotect the sectors
(factory/customer). If the "Secured
Silicon Sector" locked you need 12V at the reset pin to execute the "Temporary
Sector Group
Unprotect" command. If the "Secured Silicon Sector" not locked you are able to
unlock the secto
Hello,
i only have test it with this configuration, no more investigations. I think
the biggest problem is
the flash write functionality.
Regards,
Mathias
Am 13.04.2011 20:05, schrieb Ingo Hornberger:
> Mathias K. writes:
>>
>> [...]
>> Anyway, i was able to connect to
Hello,
sometimes i see this messages if my jtag cable (flat cable) not correct
connected to the target
board. But this is a cable issue.
Regards,
Mathias
Am 12.04.2011 14:44, schrieb Sergio:
> Info : JTAG tap: lm3s2776.cpu tap/device found: 0x3ba00477 (mfg:
> 0x23b, part: 0xba00, ver: 0x3)
Hello,
Am 06.04.2011 19:53, schrieb Martin Schmölzer:
> On Wed, 2011-04-06 at 17:45 +0200, Laurent Gauch wrote:
>
>> The EZ-USB gives access to USB but not to the ULINK interface. Right ?
>
> The ULINK consists of the EZ-USB microcontroller, an SRAM, an EEPROM and
> level shifters. There's even
Am 06.04.2011 18:58, schrieb Michael Schwingen:
> Am 04/06/2011 05:45 PM, schrieb Laurent Gauch:
> However, if the ULINK is basically an EZ-USB chip which downloads its
> code via USB, using the ULINK protocol would also mean we would have to
> use Keil's firmware, as it needs to be downloaded ever
I was able to link openocd against libjim. There is only a problem to link
jimsh against libjim.
Regards,
Mathias
Am 02.04.2011 03:10, schrieb Steve Bennett:
> On 10/03/2011, at 9:20 PM, Mathias K. wrote:
>
>> I have append it, it is only the linker output.
>>
>
Hello,
please tell us the version of the ftd2xx or read the ml.
Regards,
Mathias
Am 31.03.2011 19:14, schrieb Gwennaël Arbona:
> Hi,
>
>
> I am having a bug using OpenOCD 0.5.0-dev-00815-g8d338f3 (just compiled).
> I am working on Debian Squeeze 32 bits. I am using ftd2xx from FTDI.
> So I
Yes, but works with the latest windows d2xx.
Regards,
Mathias
Am 29.03.2011 16:21, schrieb Drasko DRASKOVIC:
> On Tue, Mar 29, 2011 at 4:03 PM, Mathias K. wrote:
>> Linux: d2xx 0.4.16-r1
>
> Yes, it works for me also with 0.4.16. Problem is in new D2XX 1.0.4.
&g
Am 29.03.2011 15:16, schrieb Drasko DRASKOVIC:
> Xiaofan,
> thanks for this confirmation.
>
> We can say that we identified the issue.
>
> However, it is still strange that the issue is not reproducible by Mathias...
>
> Mathias,
> are you sure that you used latest D2XX, version 1.0.4 ?
No, not
Hello,
i can't reproduce your errors. The libftdi and d2xx works like a charm here
(linux/windows). Error 4
means IO Error. I think you have carefully check your USB cables and your
hardware. If you work with
linux you can try "dmesg" to get some reports about hardware problems,
specially usb.
I think you should reduce your clock speed first.
Am 17.03.2011 16:27, schrieb Drasko DRASKOVIC:
> clock speed 6000 kHz
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-developme
Hello,
the send buffer looks okay. Maybe this is a timeout problem. Do you use the
d2xx or ftdi library?
Regards,
Mathias
Am 17.03.2011 13:14, schrieb Drasko DRASKOVIC:
> 3174056 Debug: 3174389 188209 ft2232.c:809 ft2232_send_and_recv():
> write buffer (size 18):
> 3174057 Debug: 3174390 1
Hello,
Am 17.03.2011 13:45, schrieb Drasko DRASKOVIC:
> 1) In openocd/src/target/mips_m4k.c we can see that target endianess
> is checked and treated only mips_m4k_bulk_write_memory() in and not
> mips_m4k_write_memory() and mips_m4k_read_memory(). Why is this so ?
> (It leads to wrong SDRAM setu
I don't know if this high value break any other flash driver. But this is okay
for me.
Am 17.03.2011 08:57, schrieb Øyvind Harboe:
> I hate options. Can't we just set the "right" value or figure it out?
>
>
> Crank it up real high? 128/256kBytes?
>
>
>
>
_
Hello,
for performance reason i would change the chunksize in src/flash/nor/tcl.c from
a hard coded value
to a option/parameter with a default value of the old hard coded value (1024).
Currently i use a
value of 32*1024.
Can anyone give me a suggestion to add this to the configuration file,
pre
Yes, thanks.
Am 15.03.2011 16:32, schrieb Øyvind Harboe:
> better?
>
>
>
>
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Hello,
Am 16.03.2011 20:19, schrieb Drasko DRASKOVIC:
> However, trying to load a bigger image function
> mips_m4k_bulk_write_memory() is called an fails in
> mips32_pracc_fastdata_xfer(). So, making mips_m4k_bulk_write_memory()
> to fall straight away to simple mips_m4k_write_memory(), like in
>
Hello,
the correct fix should be:
((uint32_t*)buffer)[i+1] = ((uint32_t*)buffer_x)[i1];
This function merge buffer_y and buffer_x into buffer.
Regards,
Mathias
Am 15.03.2011 15:08, schrieb Øyvind Harboe:
> found by inspection, not confirmed.
>
> Signed-off-by: Øyvind Harboe
> ---
> src/t
I have append it, it is only the linker output.
Am 10.03.2011 11:47, schrieb Peter Stuge:
> Mathias K. wrote:
>> Any hints to solve this problem?
>
> Please send exact copy of error messages, otherwise any diagnosis is
> impossible.
make all-recursive
make[1]: Entering dire
Hello,
the current git head failed to compile jimtcl. I use latest cygwin and
following configure options:
./configure --enable-maintainer-mode --disable-werror --disable-shared \
--enable-ft2232_ftd2xx \
--with-ftd2xx-win32-zipdir=/cygdrive/c/data/cdm/
Last compiler line:
gcc -g -O2 -o jim
Hello,
this patch add a target memory alignment option.
Regards,
Mathias
>From 7cafbb5b454fb79f36368e9b8c3a62b486f6c024 Mon Sep 17 00:00:00 2001
From: Mathias K.
Date: Thu, 3 Mar 2011 11:01:46 +0100
Subject: [PATCH] target: memory alignment option
Add a target option to enable/disa
Hello,
this patch fix the log message and change the log output to debug.
Regards,
Mathias
>From 1eea6ab88e31e912eea0f4b14c7317329fa6 Mon Sep 17 00:00:00 2001
From: Mathias K.
Date: Thu, 3 Mar 2011 10:28:21 +0100
Subject: [PATCH] ft2232: fix log message and change log output to de
Hello,
this message should be only visible if the debug output enabled. If you have
usb read/write problems
sometimes, this is the point you have to look.
Regards,
Mathias
Am 03.03.2011 10:19, schrieb Jon Povey:
> Since 6ddcee7d20ee873f1c214736c22f29d9781dded4
>
> When I try to read memory,
Hello,
read http://www.ftdichip.com/Support/Documents/DataSheets/ICs/DS_FT4232H.pdf
page 9. Looks like a
wrong hardware implementation. It is not possible to switch any jtag pin.
Regards,
Mathias
Am 02.03.2011 13:22, schrieb Jean-Christophe PLAGNIOL-VILLARD:
> Hi,
>
> I'm currently ad
Am 25.02.2011 17:54, schrieb Michael Schwingen:
> Mathias K. wrote:
>>
>> Am 25.02.2011 14:38, schrieb Michael Schwingen:
>>
>>> Mathias K. wrote:
>>>
>>>> I think you can't simple abstract this with 8/16/24/32bit access, because
&g
Hello,
Am 25.02.2011 14:38, schrieb Michael Schwingen:
> Mathias K. wrote:
>> I think you can't simple abstract this with 8/16/24/32bit access, because in
>> my case the data bus
>> has always a 24bit width and the address bus increment is always one (one
>>
Hello,
Am 24.02.2011 22:27, schrieb Michael Schwingen:
> Am 02/24/2011 09:36 AM, schrieb Mathias K.:
>> this patch add the risc (default) and harvard architecture to the target
>> structure. Currently
>> this patch only affect the memory read/write functions.
> I
Hello,
i have done more tests on this issue and i have create the patch bellow.
Regards,
Mathias
>From f2ecac695568717b953c0a323ac683e28108f11f Mon Sep 17 00:00:00 2001
From: Mathias K.
Date: Thu, 24 Feb 2011 12:53:52 +0100
Subject: [PATCH] ft2232: fix possible read buffer overflow
T
Hello,
this patch add the risc (default) and harvard architecture to the target
structure. Currently
this patch only affect the memory read/write functions.
Regards,
Mathias
From dbfc2e3b9473a9cfb48c3e6e651be7152f32748b Mon Sep 17 00:00:00 2001
From: Mathias K.
Date: Thu, 24 Feb 2011 09:31
Hello,
i see two possible solutions.
The first is to add a bit option to the target struct that define the supported
memory access like
8,16,32 bit (default 8/16/32) and target_write_buffer/target_read_buffer would
align in respect to
this value. I don't prefer this.
The second is to add a tar
Hello,
the target_write_buffer and target_read_buffer functions try to align the
memory read/write access.
This is wrong for the dsp563xx target, it is not possible to read a byte are
half word on a odd
address. On every memory address there are 3 bytes of data.
Is there any chance to add a co
Hello,
this patch add rudimentary gdb support to the dsp563xx target.
Regards,
Mathias
>From a0e603b114f4a7bcfab1ba1fd96693947d4d573a Mon Sep 17 00:00:00 2001
From: Mathias K.
Date: Sun, 20 Feb 2011 11:12:53 +0100
Subject: [PATCH 1/1] dsp563xx: rudimentary gdb support
This patch
This works, i need the global command context to access this variable from c:
/* from openocd.c */
extern struct command_context *global_cmd_ctx;
/* get the interpreter */
Jim_Interp *interp = global_cmd_ctx->interp;
Jim_Obj * memspace = Jim_GetGlobalVariableStr(interp,"memspace", JIM_NONE);
if
Am 18.02.2011 08:19, schrieb Øyvind Harboe:
> On Fri, Feb 18, 2011 at 8:12 AM, Mathias K. wrote:
>> Okay, i have found the issue. If i use the monitor command from gdb i
>> receive the string "qqset
>> memspace 0", with an extra "q" in the prefix. This
is then
"set memspace 0" and
the command "set" is called.
Is there any way to access the value "memspace" from c ?
Regards,
Mathias
Am 17.02.2011 20:00, schrieb Mathias K.:
> Looks like the tcl function is not called:
>
> Debug: 355
Looks like the tcl function is not called:
Debug: 355 26143 gdb_server.c:2183 gdb_input_inner(): received packet:
'qRcmd,736574206d656d73706163652030'
parameter for command_run_line() -> "qset memspace 0"
User : 356 26147 command.c:707 command_run_line(): 0
Debug: 357 26147 gdb_server.c:388 gdb_pu
Hello,
Am 17.02.2011 13:17, schrieb Edgar Grimberg:
> What does
>
> make --version
GNU Make 3.81
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPO
Hello,
i try to work with a propritary software and a openocd gdb connection to my
dsp563xx target. This
software sends a very important command "qset memspace 3". This command switch
between the different
target memory types (p,x,y,l) before a data upload/download.
I have tracked down the gdb
se edit for a commit, you
> can modify the changes for that commit or simply change the commit
> comment:
>
> git commit --amend
>
>
> The format of a commit comment is(by convention):
>
> topic: short descript
>
> longer description
From 9132f87664eeb9021d0
Hello,
i would inform you that make failed on my site with the make switch-jX and X
greater than 1.
Regards,
Mathias
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-develop
communication errors
- check the static pattern in jtag status to verify that the value is almost
correct, this check
fail if no target is present
Regards,
Mathias
>From 10c511d919ad5e9ea1c5c82ba4e845fd6357d945 Mon Sep 17 00:00:00 2001
From: Mathias K.
Date: Wed, 16 Feb 2011 15:00:06 +0
Changes:
- remove pipeline context, use once register instead
- fix wrong register write in resume and step function
- add more conditional branch handling
Regards,
Mathias
>From 996a0c10623ed05e5bb3187b9f2134e51d279887 Mon Sep 17 00:00:00 2001
From: Mathias K.
Date: Tue, 15 Feb 2011 20:17
:
> Should this fix be merged?
>
> Any objections?
>
> Could you write a patch with a better commit comment?
>
> Thanks!
>
From 684ffa06a3e18495d6653d6e89f2a058636bbd89 Mon Sep 17 00:00:00 2001
From: Mathias K.
Date: Tue, 15 Feb 2011 16:59:23 +0100
Subject: [PATCH 1/2]
Yes.
Am 14.02.2011 15:35, schrieb Øyvind Harboe:
> Should this patch be merged?
>
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Hello,
you can try configure with "--enable-verbose-jtag-io". All the jtag
input/output is done in interface.c.
Regards,
Mathias
Am 15.02.2011 02:28, schrieb Rodrigo Rosa:
> Hi,
>
> We've been trying to communicate via JTAG (through a signalyzer H2)
> with a freescale 568013.
> Modifying t
No, i need to change this. Anyway the overflow of the command read buffer size
in ft2232 should be
fixed (patched) first. I think in some circumstances this can happen again (i
have not seen this
yet) and this function need some more work to avoid this case in the future.
Am 14.02.2011 15:35, s
Hello,
the mpsse buffer preparation and send functionality is done in:
ft2232_set_data_bits_low_byte
ft2232_set_data_bits_high_byte
You only need to deliver the port value and direction to this functions. Thats
all.
Regards,
Mathias
Am 14.02.2011 10:36, schrieb Laurent Gauch:
> Why removin
rom b1cdc2056c85b9798d4f2ffe6a5b2f3f2f8fef05 Mon Sep 17 00:00:00 2001
From: Mathias K.
Date: Sun, 13 Feb 2011 13:21:42 +0100
Subject: [PATCH] - add functions for ft2232 set data bits high/low byte command
---
src/jtag/drivers/ft2232.c | 373 +++--
1 files changed,
Hello,
this patch add 2 functions to set data bits high/low byte.
Regards,
Mathias
>From b1cdc2056c85b9798d4f2ffe6a5b2f3f2f8fef05 Mon Sep 17 00:00:00 2001
From: Mathias K.
Date: Sun, 13 Feb 2011 13:21:42 +0100
Subject: [PATCH] - add functions for ft2232 set data bits high/low byte comm
Hello,
Am 11.02.2011 16:21, schrieb Mathias K.:
> On a memory read/write access the queue has always flushed at the end.
>
> But if i read some more data without a queue excecute in the middle and only
> at the end i get this
> error:
>
> Error: ftdi_write_data: usb bulk
On a memory read/write access the queue has always flushed at the end.
But if i read some more data without a queue excecute in the middle and only at
the end i get this
error:
Error: ftdi_write_data: usb bulk write failed
Error: couldn't write MPSSE commands to FT2232
I think there are to much
Hello,
Am 11.02.2011 10:17, schrieb Øyvind Harboe:
> How about rewriting clock_tms then?
>
Because the used time? This session was to short (some seconds) to get a
meaningful time statistic.
Regards,
Mathias
___
Openocd-development mailing list
Ope
Hello,
Am 11.02.2011 10:01, schrieb Øyvind Harboe:
> What kind of CPU are you running OpenOCD on?
It's a Intel T7200.
Regards,
Mathias
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinf
Hello,
i think this patch make sense because the functions are called very often
(column calls in the
profile data) and do a little bit more then nothing.
Am 11.02.2011 07:29, schrieb Øyvind Harboe:
> I don't have any objections to this particular patch, but if we
> have to start doing tweaks at
Changes:
- declare tap_set_state_impl, tap_get_state, tap_set_end_state,
tap_get_end_state as static inline,
this will decrease the calling overhead for this status getter and setter
functions
diff --git a/src/jtag/interface.c b/src/jtag/interface.c
index 1ed4512..8d5d514 100644
--- a/src/jtag/i
Changes:
- delay jtag queue excecution to decrease memory read/write times
- fix an early queue excecution in once interface
diff --git a/src/target/dsp563xx.c b/src/target/dsp563xx.c
index 4371d0a..9bfb9a1 100644
--- a/src/target/dsp563xx.c
+++ b/src/target/dsp563xx.c
@@ -29,8 +29,6 @@
#include
Hello,
in app. note AN1839 (dsp563xx) its 3 ;-). In DSP56300FM and AN2074 they use the
correct number 5.
Regards,
Mathias
Am 10.02.2011 20:25, schrieb Phil Fong:
> Hi,
> I've been working on Rodrigo on adding support to flash Freescale dsp56800e
> devices and have been looking at the ds
Hello,
is there any way to determine the current and maximum queue size before a
jtag_execute_queue() has
to be executed ?
Regards,
Mathias
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/lis
Hello,
On 08.02.2011 15:37, Tom Schouten wrote:
However, when restarting OpenOCD after USB replug it does work like normal. Is
there a way to make
this recover inside OpenOCD, or otherwise to simply exit the application so it
can be restarted
automatically?
Yes, you can exit openocd. Try the
Hello,
On 05.02.2011 10:43, Øyvind Harboe wrote:
What sort of CPU did you run the tests on?
Which test? The target cpu/mcu or my system cpu?
Let me know when the patch is ready to be committed. I suppose
it could need a bit of coolof .
I think its fine.
Regards,
Mathias
___
Hello,
On 07.02.2011 09:27, luca ellero wrote:
On 07/02/2011 3.54, Aaron Carroll wrote:
On 04/02/11 17:31, Mathias K. wrote:
Hello,
On 04.02.2011 01:38, Aaron Carroll wrote:
At a high level, I think it makes sense for functions to be explicit
about selecting an AP... I don't se
1 - 100 of 135 matches
Mail list logo
