I saw Michael Schwingen saying to use BDI2000 for Stellaris CPU
(http://lists.berlios.de/pipermail/openocd-development/2008-September/003107.html).
Can some one provide me such a file? I'm going to use LM3S6432
Processor, but configuration file for other Stellaris CPUs would also
help.
Thank you i
>> Then on the other hand if you are the copyright holder of a BDI
>> configuration
>> file and is willing to contribute that BDI configuration file to OpenOCD,
>> then
>> it would be much appreciated. That file could then be translated to
>> OpenOCD speak by "someone".
Unfortunately I don't have
>> I talked to Abatron and they said I have to buy a new firmware for
>> that CPU family (till now we had only ARM7/ARM9 CPUs). So I'll try
>> bundled software for Windows and then try to port my CPU to OpenOCD.
>>
>
> Ah - in that case, a config file will not help, you need the new BDI
> firmware
On Mon, Oct 26, 2009 at 11:02 PM, David Brownell wrote:
> On Monday 26 October 2009, Yegor Yefremov wrote:
>> What about making a common target file for the whole 6000 series?
>
> You could have a common target for all current Stellaris
> chips, for that matter... just make sur
On Tue, Oct 27, 2009 at 6:56 PM, David Brownell wrote:
> On Tuesday 27 October 2009, Yegor Yefremov wrote:
>> In the data sheets for all lm3s811 revisions only version 1 is
>> described. What to do with the stuff? Can revision number be made
>> "don't care" or
> The first issue comes up is how do I know the CPUTAPID for the new board?
> I went through the document of openocd, but could not find out
> comprehensive description
> talked about how to obtain CPUTAPID. What do I miss?
> Or what should I be familiar with first?
> Any suggestions would be great
I use LM3S6432 SoC that is controlled via LM3S881 board. When writing
to flash I frequently get such error message:
> halt
target state: halted
target halted due to debug-request, current mode: Thread
xPSR: 0x8100 pc: 0xbdf6 msp: 0x20007380
> flash write_image erase image.bin 0x1000 bin
au
David, I tried to apply all of the issues you pointed to. I've
increased -work-area-size to 16k otherwise openocd was complaining
about not enough working area
not enough working area available(requested 8192, free 8152)
I also found another CPUID 0x1ba00477. It was mentioned in the data
sheet of
Common target file for LM3S CPU family
Signed-off-by: Yegor Yefremov
Index: openocd/tcl/target/luminary.cfg
===
--- /dev/null 1970-01-01 00:00:00.0 +
+++ openocd/tcl/target/luminary.cfg 2009-11-09 09:57
Now, without line breaks
--
Common target file for LM3S CPU family
Signed-off-by: Yegor Yefremov
Index: openocd/tcl/target/luminary.cfg
===
--- /dev/null 1970-01-01 00:00:00.0 +
+++ openocd/tcl
I found some short description about TFTP support in OpenOCD but it
seems to be restricted to eCOS or ZY1000 debugger.
Are there any plans to implement such a feature? The usage were for
example following: I have my Linux development host where I compile
the firmware and I also run an TFTP daemon
On Wed, Dec 2, 2009 at 3:47 PM, Øyvind Harboe wrote:
> On Wed, Dec 2, 2009 at 3:42 PM, Yegor Yefremov
> wrote:
>> I found some short description about TFTP support in OpenOCD but it
>> seems to be restricted to eCOS or ZY1000 debugger.
>
> eCos has as tftp filing syste
On Tue, Dec 15, 2009 at 1:23 AM, David Brownell wrote:
> On Monday 09 November 2009, Yegor Yefremov wrote:
>> Common target file for LM3S CPU family
>
> I'm merging the modified version below ... your version
> still arrived mangled, among other things. Updates:
>
>
Hi all,
since the project moved to git, the ohloh.net
(http://www.ohloh.net/p/openocd) can only see the legacy svn
repository. I found a discussion about how to add new repository:
https://www.ohloh.net/forums/10/topics/3840. Can someone change the
repo?
Regards,
Yegor
___
On Thu, Dec 17, 2009 at 7:52 PM, Charles Vaughn wrote:
> I've recently purchased an LM3S811 evaluation board. I've tried to connect
> to it with OpenOCD, but I've met very little success even initiating a
> connection.
>
> When I use the version of OpenOCD available from Ubuntu repositories
> (r2
On Fri, Dec 18, 2009 at 3:58 PM, Charles Vaughn wrote:
> What revision is your board? The title is a bit out of sync with the issue,
> as in June it appears TI multiplexed SWO and JTAG. My board rev is LMWLV-C.
My board rev: LMWLV-B
Yegor
___
Openocd
On Fri, Dec 18, 2009 at 12:49 AM, David Brownell wrote:
> Much to my surprise, I observed a "flash erase_address ..."
> command erasing data which I didn't say should be erased.
>
> The issue turns out to be generic NOR flash code which was
> silently, and rather dangerously, morphing partial-sect
On Mon, Dec 28, 2009 at 2:45 AM, David Brownell wrote:
> On Monday 21 December 2009, Yegor Yefremov wrote:
>> My board rev: LMWLV-B
>
> Could you forward the USB IDs and device string of your
> board? I notice that tcl/interface/luminary-lm3s811.cfg
> doesn't inclu
I'm using LM3S6911 chip and would like to protect the firmware by
disabling debugging interface. I have found a discussion about this on
TI forum http://e2e.ti.com/f/471/p/45944/159065.aspx#159065%22
Unfortunately issuing these commands via openocd didn't disable JTAG:
mww 0x400fd004 0xFFFD (a
On Mon, Sep 6, 2010 at 5:21 PM, Yegor Yefremov
wrote:
> I'm using LM3S6911 chip and would like to protect the firmware by
> disabling debugging interface. I have found a discussion about this on
> TI forum http://e2e.ti.com/f/471/p/45944/159065.aspx#159065%22
> Unfortunat
Hello,
is anyone working on such a target? There are arm920 and arm926ejs
targets, but arm922 is not there. arm922 seems to be very similar with
arm920.
Regards,
Yegor
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lis
On Fri, Jun 3, 2011 at 8:11 PM, Drasko DRASKOVIC
wrote:
> On Wed, Jun 1, 2011 at 3:37 PM, Yegor Yefremov
> wrote:
>> Hello,
>>
>> is anyone working on such a target? There are arm920 and arm926ejs
>> targets, but arm922 is not there. arm922 seems to be very similar
Signed-off-by: Yegor Yefremov
---
tcl/interface/jtagkey2.cfg |7 ++-
tcl/interface/jtagkey2p.cfg |7 ++-
2 files changed, 4 insertions(+), 10 deletions(-)
Index: b/tcl/interface/jtagkey2.cfg
===
--- a/tcl
> Any objections?
Another option were to remove all jtagkey configuration files and
leave the jtagkey.cfg only.
Yegor
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
On Mon, Jun 6, 2011 at 9:27 AM, Øyvind Harboe wrote:
> On Mon, Jun 6, 2011 at 9:24 AM, Yegor Yefremov
> wrote:
>>> Any objections?
>>
>> Another option were to remove all jtagkey configuration files and
>> leave the jtagkey.cfg only.
>
> The d
On Mon, Jun 6, 2011 at 9:32 AM, Michael Schwingen
wrote:
> Am 06/06/2011 09:20 AM, schrieb Yegor Yefremov:
>> Signed-off-by: Yegor Yefremov
>>
>> ---
>> tcl/interface/jtagkey2.cfg | 7 ++-
>> tcl/interface/jtagkey2p.cfg | 7 ++-
>> 2 files
Hi Laurent,
> Do you have a Amontec JTAGkey-2 (High-speed USB 2.0) ?
>
> If yes, please do the same comparaison with libusb and d2xx on Linux and
> windows, and with the Amontec JTAGkey D2XX device driver package WHQL
> certified .
I would also like to have Amontec JTAGkey-2 and test the speed
co
On Sat, Oct 22, 2011 at 12:10 AM, Ananda Regmi wrote:
> Hello,
> Does anybody here know if Amontec - makers of JTAG Tiny - company went out
> of business or something?
> I know, this is an off topic question. But I have exhausted all my options
> before posting it here. Since, Amontec's SDK kit su
> I have create a change in one of my patch that i have already sent. I
> commited it, but I forget to add the signed-off by... Is it possible to edit
> a commit message ?
See here for more information about reworking patch series:
http://book.git-scm.com/4_interactive_rebasing.html
Yegor
__
29 matches
Mail list logo
