On Wed, Dec 3, 2008 at 8:10 AM, Rick Altherr <[EMAIL PROTECTED]> wrote:
> Please feel free to provide commentary on any and all portions of this.
> I've written it in the format I expect to use for future status updates.
>
> Summary
> -
> The majority of the development work for 1.0 GM
Please feel free to provide commentary on any and all portions of
this. I've written it in the format I expect to use for future status
updates.
Summary
-
The majority of the development work for 1.0 GM has already been
committed to trunk but has yet to be integrated into the R
On Dec 2, 2008, at 8:35 PM, Duane Ellis wrote:
Hiroshi san,
What was the original complaint? If I understand correctly, the
problem
was this:
==
cmd_que_allocate() - returns an un-aligned pointer.
==
Is that correct? If so - the cause, and solution is utterly simple,
an
rick> This doesn't change the pointer returned by cmd_queue_alloc() at all.
the problem I believe is the *NEXT* allocation that is failing, after an
"odd-sized" request, you get an odd aligned pointer.
Two odd requests - should give you an even.. (sort of, not exactly, it
has to be 4 bytes her
Hiroshi san,
What was the original complaint? If I understand correctly, the problem
was this:
==
cmd_que_allocate() - returns an un-aligned pointer.
==
Is that correct? If so - the cause, and solution is utterly simple, and
is as follows:
The solution is to *ROUND*UP* all re
Duane> [paraphrased: Jtag CLOCK >= 8 to 9mhz does not do well on a 6
inch ribbon cable.]
Joern> That not correct. I currently have 20 Mhz TCK on a 6 inch ribbon
cable
What type of jtag dongle are you using that does 20mhz TCK?
Perhaps 20mhz works for you - but on my board - the scope says othe
Rahul Balani> I am new to this mailing list.
Welcome.
=
Rahul Balani> [i.MX21]
Hmm - I have an iMX27 - close but not exactly the same.
=
Rahul Balani> OpenOCD (rev: 1187)
Reasonably very new :-) FYI there is/was a big change to one of the
commands I
Hi everyone,
I am new to this mailing list. Since the past few days, I have been working
on an i.MX21 based Cogent CSB735 SBC on a CSB703 development board using
OpenOCD (rev: 1187) and gdb 6.8 with an Olimex ARM-USB-OCD. My configuration
and gdbinit script is given below:
---
On Tue, Dec 2, 2008 at 1:33 AM, Duane Ellis <[EMAIL PROTECTED]> wrote:
> Kees Jongenburger wrote:
>>
>> This patch provides an initial beaglebloard.cfg file up for
>> inclusion/review.
>>
>
> 1) Please review the new documentation.
>
> http://openocd.berlios.de/doc/Config-File-Guidelines.html
H
On Tue, Dec 2, 2008 at 8:01 AM, Rick Altherr <[EMAIL PROTECTED]> wrote:
> What config file are you using when this happens? What host OS/architecture
> are you using?
amd64 with the given configuration
greetings
btw performing 7 times
irscan 0 7
drscan 0 8 0X89
also makes it go BOOM
>
> Rick
Rick Altherr wrote:
> Ironically, my day job has been exclusively on non-x86 platforms for
> years and only recently started with x86.
>
> Pointers to data types should be aligned such that the data type is
> naturally aligned. That would mean that a 16-bit type should be
> 16-bit aligned. The qu
On Dec 2, 2008, at 10:03 AM, Michael Schwingen wrote:
Rick Altherr wrote:
I'm also not entirely sure that a structure must always be aligned.
I'm aware that some architectures will trap if an unaligned access is
encountered, but the OS should catch the trap and handle the
unaligned
access c
Rick Altherr wrote:
> I'm also not entirely sure that a structure must always be aligned.
> I'm aware that some architectures will trap if an unaligned access is
> encountered, but the OS should catch the trap and handle the unaligned
> access correctly.
No. AFAIK, C requires pointers to be ali
I think a combination of your two approaches might be more
appropriate. Let's introduce a new function
cmd_queue_allocate_aligned() that does the alignment as well as the
allocation. The benefit is that only cases where alignment is
necessary can use the new function, but they still only
> I'm also not entirely sure that a structure must always be aligned.
C language, one of what is required is,
member of structure should aligne to natively accessable.
# I think... but I'm not sure...
> I'm aware that some architectures will trap if an unaligned access is
> encountere
Rick Altherr> I read through this tonight. [paraphrased: suggestion
move all "removed" stuff to the appendix]
I'll see what I can do.
BTW - what about spelling/grammar/etc - that concerns me the most.
And - for the international types - who's English is *NOT* your first
and best language - i
> > How about this patch. this also works.
> >
> > Is it acceptable ?
>
> I change the code.
> this is more readable.
same, but revert unnecessary change.
Hiroshi Ito
Media Lab. Inc.,
URL http://www.mlb.co.jp ( Sorry, Japanese only. )
TEL +81-3-5294-7255 FAX +81-3-5294-7256
Index:
> How about this patch. this also works.
>
> Is it acceptable ?
I change the code.
this is more readable.
Hiroshi Ito
Media Lab. Inc.,
URL http://www.mlb.co.jp ( Sorry, Japanese only. )
TEL +81-3-5294-7255 FAX +81-3-5294-7256
Index: src/jtag/jtag.c
===
How about this patch. this also works.
Is it acceptable ?
> On Dec 2, 2008, at 12:46 PM, Hiroshi Ito wrote:
>
> > I'm running openocd on EP9307(arm925t) CPU, as a HOST.
> > and target is EP9307 and ARM926t with EP9307 GPIO.
> >
> > revision 1183 cause seg fault.
> > The problem is, cmd_queue_al
19 matches
Mail list logo
