On Mon, 11 Jul 2011 21:26:48 +0200
Øyvind Harboe wrote:
"minIni" from CompuPhase might be an option to parse
ini-files. It's a
reather small code written in C, open-source and has a
GPL-compatible
license.
The Apache License is not GPL compatible.
Hmm, I'm not a license-expert but I did a
Problem: CFI flashes can be quite slow. 200kBytes erase + 100kBytes write
are not uncommon limitations => maximum theoretical performance
of 66kBytes/s erase+write speed.
With a 16mByte flash, this means 4 minutes best case.
Alternative approach: upload an application to RAM that contains
the ent
Very thank's, in the last hour I can configure eclipse (googling), but
I'm interesting in a more lightweight application, like Code::Blocks or
something like that.
Again, very thank's
Sergio
El 11/07/2011 07:15 p.m., Andrew Leech escribió:
On 11/07/2011 9:08 PM, Hard Maker wrote:
Hi List,
I'm
On 11/07/2011 9:08 PM, Hard Maker wrote:
Hi List,
I'm starting with OpenOCD and have a questions about wath hi level
application can use with openOCD. Basically I need/want run
aplications and know the var values. Using OpenOCD I can flash, view
registry state, run, etc. But there are some apl
> "minIni" from CompuPhase might be an option to parse ini-files. It's a
> reather small code written in C, open-source and has a GPL-compatible
> license.
The Apache License is not GPL compatible.
--
Øyvind Harboe - Can Zylin Consulting help on your project?
US toll free 1-866-980-3434 / In
Tarballs available for 0.4.0-rcs allowed me to build executables which
would show correct version on startup as well as PDF User's Guide with
correct tag. Now all people can see is "0.5.0-dev". "Real" release
tarballs would be really appreciated...
4\/3!!
__
...
I think it's an windows ini file format or a close
dialect... Here is
a Java library
to parse ini file that I googled up. I'm sure there are
ini file parsers for
any language on the planet...
http://ini4j.sourceforge.net/
"minIni" from CompuPhase might be an option to parse
ini-files.
Has anyone written a tool to convert BDI to OpenOCD speak?
http://www.denx.de/wiki/view/DULG/WhereCanIFindBDI2000ConfigurationFiles
The syntax is very simple and almost all of it has trivial
translations when there
is a translation...
I think it's an windows ini file format or a close dialect..
On Mon, Jul 11, 2011 at 8:14 PM, Steve Bennett wrote:
> On 11/07/2011, at 10:03 PM, Xiaofan Chen wrote:
>
>> On Tue, Jun 28, 2011 at 1:48 PM, Xiaofan Chen wrote:
>>> On Sun, Jun 26, 2011 at 10:14 PM, Øyvind Harboe
>>> wrote:
Can someone review this?
>>>
>>> Maybe it is good to fix for
On 11/07/2011, at 10:03 PM, Xiaofan Chen wrote:
> On Tue, Jun 28, 2011 at 1:48 PM, Xiaofan Chen wrote:
>> On Sun, Jun 26, 2011 at 10:14 PM, Øyvind Harboe
>> wrote:
>>> Can someone review this?
>>>
>>
>> Maybe it is good to fix for 64bit as well, similar to the case of
>> --with-ftd2xx-win32-z
On Tue, Jun 28, 2011 at 1:48 PM, Xiaofan Chen wrote:
> On Sun, Jun 26, 2011 at 10:14 PM, Øyvind Harboe
> wrote:
>> Can someone review this?
>>
>
> Maybe it is good to fix for 64bit as well, similar to the case of
> --with-ftd2xx-win32-zipdir where $host_cpu is checked to decide
> which library t
>>> Yes, if BE target shifts out an 32 bit value from address 0, it will
>>> begin with bit0:7, that is byte address 0x03 at targets memory.
>>
>> And host will do the same. When it shifts out 32-bit value , it will
>> put contents of it's address 0x3 to output buffer[0] and send this
>> first.
> I
On Mon, Jul 11, 2011 at 1:43 PM, Drasko DRASKOVIC
wrote:
>> Yes, if BE target shifts out an 32 bit value from address 0, it will
>> begin with bit0:7, that is byte address 0x03 at targets memory.
>
> And host will do the same. When it shifts out 32-bit value , it will
> put contents of it's addres
On Mon, Jul 11, 2011 at 1:41 PM, Mahr, Stefan wrote:
>> When you start shifting out LSB (bit) from the BE host, will you start
>> shifting out contents of address 0x3, or the address 0x0 ? In my
>> opinion, it will be content of the addr 0x3 that will be shifted out
>> first (as it holds bits 0:7
> When you start shifting out LSB (bit) from the BE host, will you start
> shifting out contents of address 0x3, or the address 0x0 ? In my
> opinion, it will be content of the addr 0x3 that will be shifted out
> first (as it holds bits 0:7 for on the BE host).
Yes, if BE target shifts out an 32 b
On Mon, Jul 11, 2011 at 1:30 PM, Øyvind Harboe wrote:
> On Mon, Jul 11, 2011 at 1:10 PM, Drasko DRASKOVIC
> wrote:
>> On Mon, Jul 11, 2011 at 12:52 PM, Øyvind Harboe
>> wrote:
>>> On Mon, Jul 11, 2011 at 12:45 PM, Drasko DRASKOVIC
>>> wrote:
On Mon, Jul 11, 2011 at 11:53 AM, Øyvind Harboe
Øyvind Harboe wrote:
> Really OpenOCD could have stored the bits as a series of
> words larger than bytes in the host representation to be more
> efficient.
This would probably be a source of much more confusion :-)
___
Openocd-development mailing list
On Mon, Jul 11, 2011 at 1:10 PM, Drasko DRASKOVIC
wrote:
> On Mon, Jul 11, 2011 at 12:52 PM, Øyvind Harboe
> wrote:
>> On Mon, Jul 11, 2011 at 12:45 PM, Drasko DRASKOVIC
>> wrote:
>>> On Mon, Jul 11, 2011 at 11:53 AM, Øyvind Harboe
>>> wrote:
I think there is a fundamental misunderstandi
On Mon, Jul 11, 2011 at 12:52 PM, Øyvind Harboe wrote:
> On Mon, Jul 11, 2011 at 12:45 PM, Drasko DRASKOVIC
> wrote:
>> On Mon, Jul 11, 2011 at 11:53 AM, Øyvind Harboe
>> wrote:
>>> I think there is a fundamental misunderstanding about JTAG
>>> and OpenOCD.
>>>
>>> Let me try to clarify:
>>>
>>
Hi List,
I'm starting with OpenOCD and have a questions about wath hi level
application can use with openOCD. Basically I need/want run aplications
and know the var values. Using OpenOCD I can flash, view registry state,
run, etc. But there are some aplication to do a trace more easy?
I'm try w
On Mon, Jul 11, 2011 at 12:45 PM, Drasko DRASKOVIC
wrote:
> On Mon, Jul 11, 2011 at 11:53 AM, Øyvind Harboe
> wrote:
>> I think there is a fundamental misunderstanding about JTAG
>> and OpenOCD.
>>
>> Let me try to clarify:
>>
>> JTAG clocks in and out bits, not bytes, so the concept of
>> "big/
Sorry, little mistake:
wrong:
>> LE host: result = (uint32_t)buffer[0]; // result = 0x78563412 (memory
>> 0x12 0x34 0x56 0x78)
>> BE host: result = (uint32_t)buffer[0]; // result = 0x12345678 (memory
>> 0x12 0x34 0x56 0x78)
corrected:
LE host: result = *(uint32_t*)&buffer[0];//
On Mon, Jul 11, 2011 at 11:53 AM, Øyvind Harboe wrote:
> I think there is a fundamental misunderstanding about JTAG
> and OpenOCD.
>
> Let me try to clarify:
>
> JTAG clocks in and out bits, not bytes, so the concept of
> "big/small-endian" does not enter the picture at the JTAG level.
Sat that w
On Mon, Jul 11, 2011 at 12:31 PM, Øyvind Harboe wrote:
> On Mon, Jul 11, 2011 at 12:17 PM, Drasko DRASKOVIC
> wrote:
>> On Mon, Jul 11, 2011 at 7:31 AM, Øyvind Harboe
>> wrote:
>>> Now a sequence of 8 bit words happens to be identical to
>>> little endian representation
>> In what way ? 8 bits
On Mon, Jul 11, 2011 at 12:17 PM, Drasko DRASKOVIC
wrote:
> On Mon, Jul 11, 2011 at 7:31 AM, Øyvind Harboe
> wrote:
>> Now a sequence of 8 bit words happens to be identical to
>> little endian representation
> In what way ? 8 bits is 8 bits - one byte, bits 7:0. I do not see BE
> or LE represent
Hi Thomas (and list),
I have just been trying to use OpenOCD on a TI DM365 EVM.
It doesn't work very well, sounds a bit like the problems you
were having last year, starting with this:
http://lists.berlios.de/pipermail/openocd-development/2010-April/015436.html
Did you ever manage to get things
On Mon, Jul 11, 2011 at 7:31 AM, Øyvind Harboe wrote:
> Now a sequence of 8 bit words happens to be identical to
> little endian representation
In what way ? 8 bits is 8 bits - one byte, bits 7:0. I do not see BE
or LE representation here...
BR,
Drasko
I think there is a fundamental misunderstanding about JTAG
and OpenOCD.
Let me try to clarify:
JTAG clocks in and out bits, not bytes, so the concept of
"big/small-endian" does not enter the picture at the JTAG level.
OpenOCD stores the bits clocked in/out as a series of words
which happen to be
On Mon, Jul 11, 2011 at 11:10 AM, Mahr, Stefan wrote:
>>> buf_get_u32:
>>> return (((uint32_t)buffer[3]) << 24) |
>>> (((uint32_t)buffer[2]) << 16) |
>>> (((uint32_t)buffer[1]) << 8) |
>>> (((uint32_t)buffer[0]) <<
>> buf_get_u32:
>> return (((uint32_t)buffer[3]) << 24) |
>> (((uint32_t)buffer[2]) << 16) |
>> (((uint32_t)buffer[1]) << 8) |
>> (((uint32_t)buffer[0]) << 0);
>>
>
> I do not get this function at all... What I see
On 11 July 2011 07:31, Jean-Christophe PLAGNIOL-VILLARD
wrote:
>> Totally agree on this - FreeBSD ports use automatic package download
>> and extraction mechanism, so having tarball for RC2 would be great!
>> Please let me know then its available :-)
> for RC we have us gitweb to generate the tar.
On 19:43 Sun 10 Jul , li...@neuronenwerk.de wrote:
> On Sun, 10 14:38 , Jean-Christophe PLAGNIOL-VILLARD wrote:
> > On 09:30 Sun 10 Jul , Xiaofan Chen wrote:
> > > On Sun, Jul 10, 2011 at 9:11 AM, wrote:
> > > > Hi list,
> > > >
> ... snip ...
>
> > > > The results as of now are that cu
On Mon, Jul 11, 2011 at 6:31 AM, Jean-Christophe PLAGNIOL-VILLARD
wrote:
>> Totally agree on this - FreeBSD ports use automatic package download
>> and extraction mechanism, so having tarball for RC2 would be great!
>> Please let me know then its available :-)
> for RC we have us gitweb to generat
33 matches
Mail list logo
