hi ALL:
I am using a WIGGLER board to program flash by using boundary scan.
It's too slow as here are 734 CellNum on the chip MPC8247, and the TCK is only
about 100KHz to 200KHz.
I found JLink can works at 12MHz TCK.
So my question is:
Can we take full control of JLink by using OpenOCD and gener
Le 02/02/2010 20:43, Igor Skochinsky a écrit :
> So you mean the JTAG connector is for reprogramming the STM32, and not
> for connecting other boards? That does make it somewhat less
> attractive...
>
>I've looked at the schematics more closely, and it seems the pins we'd
> need to connected a
On Wed, Feb 3, 2010 at 8:18 AM, David Brownell wrote:
> On Tuesday 02 February 2010, Spencer Oliver wrote:
>> I have been given all the info for the ST-LINK from ST.
>> http://www.st.com/stonline/products/literature/um/15285.pdf
>>
>> It is accessed using vendor specific mass storage cmds.
>
> You
Hello Michel,
Wednesday, February 3, 2010, 1:57:49 AM, you wrote:
MC> Le 02/02/2010 05:35, Igor Skochinsky a écrit :
>> Very interesting! It seems it's also included in the STM8S-Discovery
>> board, which costs just $7 - one third to one fourth of the
>> stand-alone adapter. Do you know if JTAG o
Le 02/02/2010 05:35, Igor Skochinsky a écrit :
> Hi Spencer,
>
> On Tue, Feb 2, 2010 at 11:18, Spencer Oliver wrote:
>
>> I have been given all the info for the ST-LINK from ST.
>> http://www.st.com/stonline/products/literature/um/15285.pdf
>>
>> It is accessed using vendor specific mass stora
On Tuesday 02 February 2010, Spencer Oliver wrote:
> I have been given all the info for the ST-LINK from ST.
> http://www.st.com/stonline/products/literature/um/15285.pdf
>
> It is accessed using vendor specific mass storage cmds.
You mean, it enumerates like a mass storage device? Yeech.
Sigh.
This sets up a few of the core "struct arm" data structures so they
can be used with ARMv7-M cores. Specifically, it:
- defines new ARM core_modes to match the microcontroller modes
(e.g. HANDLER not IRQ, and two types of thread mode);
- Establishes a new microcontroller "core_type", which
On Tuesday 26 January 2010, Nicolas Pitre wrote:
> > > Also I don't like the fact that the introduced arm_semi_hosting structure
> > > (which could have been done in a patch of its own btw) is carrying fields
> > > that are valid only for one particular instance of a semihosting call and
> > > ther
Øyvind Harboe wrote:
> It's missing a LOG_ERROR() in this case
>
will do
Spen
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
It's missing a LOG_ERROR() in this case
--
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
___
Openocd-development mailing li
Øyvind Harboe wrote:
> On Tue, Feb 2, 2010 at 6:59 PM, David Brownell wrote:
>> On Tuesday 02 February 2010, Fredrik Hederstierna wrote:
>>> This is the patch that fix the timeout issue:
>> I think we'll hold this until the 0.5 merge window opens,
>> to make sure it gets enough testing.
>
> I'm l
>From ad9d10708d154f3a50b1b5c3465025a646ae54a5 Mon Sep 17 00:00:00 2001
From: Spencer Oliver
Date: Tue, 2 Feb 2010 21:15:03 +
Subject: [PATCH] JTAG: fix bug when no interface connected
- fix coredump when OpenOCD is started without a jtag interface connected,
Signed-off-by: Spencer Oliver
On Tue, Feb 2, 2010 at 6:59 PM, David Brownell wrote:
> On Tuesday 02 February 2010, Fredrik Hederstierna wrote:
>> This is the patch that fix the timeout issue:
>
> I think we'll hold this until the 0.5 merge window opens,
> to make sure it gets enough testing.
I'm loathe to add codepaths to par
David Brownell wrote:
> On Tuesday 02 February 2010, Spencer Oliver wrote:
>>> By the way ... if STR7 can't actually read the protect status from
>>> the hardware, why does that flash driver have a str7x_protect_check()
>>> method which pretends to do exactly that, instead of just printing
>>> a wa
Could you run openocd with highest verbose messages level? Also turn on the
usb comm and I/O debug options from the configure script invocation?
Regards,
Dimitar
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.ber
On Tuesday 02 February 2010 04:29:36 David Brownell wrote:
> On Monday 01 February 2010, Xiaofan Chen wrote:
> > I do not think libusb0.dll is the problem. It is said that arm-jtag-ew
> > emulates the J-Link in low level API. It takes quite some for
> > OpenOCD to get J-Link working properly. So I
On Tuesday 02 February 2010, Spencer Oliver wrote:
>
> > By the way ... if STR7 can't actually read the protect status from
> > the hardware, why does that flash driver have a str7x_protect_check()
> > method which pretends to do exactly that, instead of just printing
> > a warning that the status
Nicolas Pitre wrote:
> From: Spencer Oliver
>
>> @@ -480,6 +460,39 @@ int arm_semihosting(struct target *target, int
>> *retval)
>> return 0;
>> }
>>
>> -*retval = do_semihosting(target);
>> +lr = buf_get_u32(ARMV4_5_CORE_REG_MODE(arm->core_cache, ARM_MODE_SVC
David Brownell wrote:
> On Tuesday 02 February 2010, Edgar Grimberg wrote:
>>> What might make more sense is to have the 0.5 series dump that
>>> status only after "protect_check" ... like it only dumps erase
>>> status after "erase_check".
>> Or we can clone the functionality of at91sam7 flash dri
On Tuesday 02 February 2010, Harald Kipp wrote:
> Moved board specific settings from target/at91r40008.cfg to a new file
> board/ethernut3.cfg.
> Set correct CPUTAPID.
> Reset delay increased, see MIC2775 data sheet.
> Increased work area size from 16k to 128k.
Committed ... thanks!
Moved board specific settings from target/at91r40008.cfg to a new file
board/ethernut3.cfg.
Set correct CPUTAPID.
Reset delay increased, see MIC2775 data sheet.
Increased work area size from 16k to 128k.
Thanks,
Harald Kipp
diff -rupN openocd-0.4.0-rc1/tcl/board/ethernut3.cfg
openocd-0.4.0-rc1-
On Tue, Feb 2, 2010 at 7:12 PM, David Brownell wrote:
> On Friday 29 January 2010, Edgar Grimberg wrote:
>> Is there a way to make it send email notifications to this list, with
>> some tag in the subject line ([TRAC] or something similar)? This will
>> make the evolution of the tickets visible to
On Tuesday 02 February 2010, Edgar Grimberg wrote:
> > What might make more sense is to have the 0.5 series dump that
> > status only after "protect_check" ... like it only dumps erase
> > status after "erase_check".
>
> Or we can clone the functionality of at91sam7 flash driver. The last
> thing
On Monday 01 February 2010, Austin, Alex wrote:
>
> The only really viable option seems to be gitit, and I'm not sure we
> want something that complex. We're probably better off sticking with
> known-good and hosted wiki options.
My thoughts exactly. Using something like "gitit" would require a
On Sunday 31 January 2010, Øyvind Harboe wrote:
> I was kinda wondering if we could have the wiki stored in git as well.
> (14 days cooloff before pushing or somesuch?).
A two week push delay would indeed be a good way to essentially
prevent a wiki from attracting any users. ;)
What makes wikis w
> I committed this ... but I think you must mean "patch v2",
> not "patch 2/2". I can't find a "patch 1/2" ...
I'm still learning how to speak git. Thanks for committing and
pointing out the naming problem.
Regards,
Edgar
> Thanks for finding and fixing this bug!
>
> - Dave
>
> p.s. Also commit
From: Spencer Oliver
> @@ -480,6 +460,39 @@ int arm_semihosting(struct target *target, int
> *retval)
> return 0;
> }
>
> - *retval = do_semihosting(target);
> + lr = buf_get_u32(ARMV4_5_CORE_REG_MODE(arm->core_cache, ARM_MODE_SVC,
> 14).value, 0, 32);
> +
On Friday 29 January 2010, Edgar Grimberg wrote:
> Is there a way to make it send email notifications to this list, with
> some tag in the subject line ([TRAC] or something similar)? This will
> make the evolution of the tickets visible to the list, avoiding
> unnecessary duplication of information
On Tuesday 02 February 2010, Fredrik Hederstierna wrote:
> This is the patch that fix the timeout issue:
I think we'll hold this until the 0.5 merge window opens,
to make sure it gets enough testing.
- Dave
___
Openocd-development mailing list
Openocd-
On Tuesday 02 February 2010, Edgar Grimberg wrote:
> The default state of the flash after a reset init is unlocked.
> The information in the flash driver reflects this.
>
> The information about the lock status cannot be read from the
> flash chip, so the user is informed that flash info might not
>From ad4fa0bd982d954da81dd4311dc7ed1e53f0e4e7 Mon Sep 17 00:00:00 2001
From: Spencer Oliver
Date: Tue, 26 Jan 2010 15:08:38 +
Subject: [PATCH 3/3] ARM semihosting: document ARMv7M semihosting
Signed-off-by: Spencer Oliver
---
doc/openocd.texi | 11 +++
1 files changed, 11 insert
>From a9e610a28430bdc276bd14cb108c1d4ba20b2e05 Mon Sep 17 00:00:00 2001
From: Spencer Oliver
Date: Tue, 2 Feb 2010 13:07:28 +
Subject: [PATCH 2/3] ARM semihosting: add ARMv7M semihosting support
Add ARMv7M support to current arm semihosting implementation.
armv7m_arch_state will now show se
semihosting patch has been split up a little bit.
updated to latest git master.
Cheers
Spen
>From e94f8ef0802d7abf2798d9967dc14caf00bda4c5 Mon Sep 17 00:00:00 2001
From: Spencer Oliver
Date: Tue, 2 Feb 2010 13:01:50 +
Subject: [PATCH 1/3] ARM semihosting: split do_semihosting
Remove any tar
> Just for info the str73 and str75 cfg's would also need updating.
Right. Thanks for info! The patch is on its way.
Edgar
>
> Cheers
> Spen
>
--
Edgar Grimberg
System Developer
Zylin AS
ZY1000 JTAG Debugger http://www.zylin.com/zy1000.html
Phone: (+47) 51 63 25 00
__
For STR7x flash, the device cannot be queried for the protect status.
The solution is to remove the protection on reset init. The driver
also initialises the sector protect field to unprotected.
Signed-off-by: Edgar Grimberg
---
tcl/target/str730.cfg |9 -
tcl/target/str750.cfg | 1
Edgar Grimberg wrote:
> The default state of the flash after a reset init is unlocked.
> The information in the flash driver reflects this.
>
> The information about the lock status cannot be read from the
> flash chip, so the user is informed that flash info might not
> contain accurate informati
Hi
I did this optimization some time ago, and I'm sorry it contains a bug as
you discovered.
The problem is the timeout.
Thanks alot to Henrik Persson at Securitas Direct who spotted the bug in
the first place and patched it.
The timeout is currently set to 1000 eventhough the bank-erase takes
Igor Skochinsky wrote:
> Hi Spencer,
>
> On Tue, Feb 2, 2010 at 11:18, Spencer Oliver wrote:
>> I have been given all the info for the ST-LINK from ST.
>> http://www.st.com/stonline/products/literature/um/15285.pdf
>>
>> It is accessed using vendor specific mass storage cmds.
>>
>> Again this is
Hi Spencer,
On Tue, Feb 2, 2010 at 11:18, Spencer Oliver wrote:
> I have been given all the info for the ST-LINK from ST.
> http://www.st.com/stonline/products/literature/um/15285.pdf
>
> It is accessed using vendor specific mass storage cmds.
>
> Again this is a smart dongle, all the jtag/swi is
David Brownell wrote:
> Picking up, briefly, an old thread about how OpenOCD could
> learn to support "smart" dongles... where code running inside
> the JTAG adapter can offload some tasks from OpenOCD, like
> polling for status changes.
>
>
I have been given all the info for the ST-LINK from ST
On Mon, Feb 1, 2010 at 9:46 PM, David Brownell wrote:
> On Monday 01 February 2010, Edgar Grimberg wrote:
>> On the other hand, for other drivers, shouldn't flash info do a protection
>> check on the background? Otherwise the information presented by the
>> flash info command is *wrong*.
>
> So fa
The default state of the flash after a reset init is unlocked.
The information in the flash driver reflects this.
The information about the lock status cannot be read from the
flash chip, so the user is informed that flash info might not
contain accurate information.
Signed-off-by: Edgar Grimberg
42 matches
Mail list logo
