(once more, forgotten to cc the list)
Hi!
Ok I used git bisect for my first time and it seems that I have found something!
I haven't looked at the code yet, but the log seems very promising!
Here is what I've found:
f37c9b8d1560d0081e53c71c55113a3c9858011a is the first bad commit
commit f37c9b8d1560d0081e53c71c55113a3c9858011a
Author: Øyvind Harboe <oyvind.har...@zylin.com>
Date: Tue Nov 3 12:28:00 2009 +0100
arm920t: memory writes were broken when MMU was disabled
To support breakpoints, flush data cache line and invalidate
instruction cache when 4 and 2 byte words are written.
The previous code was trying to write directly to the physical
memory, which was buggy and had a number of other situations
that were not handled.
Signed-off-by: Øyvind Harboe <oyvind.har...@zylin.com>
:040000 040000 9929fd9afd9f244c2e094742465ebbd279b34354
8b9b3a9d6be11783a45c3edc7a98c35e6a6df4e8 M src
Regards
Marc
PS: here is how I found it:
git clone...
git bisect start
git bisect bad v0.3.1
git bisect good v0.1.0
[ba0f4a254c28ce0013e6dd2443f358316153610a] added pathmove command
git bisect good
[18d8ac5267a41d29417ea01213be5dc9c2bddf9c] David Brownell
<davi...@pacbell.net>Fix some command helptext:
git bisect good
Bisecting: 203 revisions left to test after this (roughly 8 steps)
[16a7ad5799ae488ad122648f2f74fe5d59e6c0c6] Minor cleanup to ARM926 debug entry:
**** 2010-02-11-13:54
git bisect good
Bisecting: 101 revisions left to test after this (roughly 7 steps)
[113679ff59e20530c621051d0aceb1876a49c45d] corrective fix for MinGW GNU C99
printf compliance
2010-02-11-13:57
git bisect good
Bisecting: 50 revisions left to test after this (roughly 6 steps)
[8f3b28ff4199a64d6f7aff1584a48f18661969ae] Fix incorrect line endings
2010-02-11-13:59
git bisect good
Bisecting: 25 revisions left to test after this (roughly 5 steps)
[517049dca50fa2af965b2ba9db43d50e65400c3f] Olimex FT2232H JTAG adapters
2010-02-11-14:01
git bisect good
Bisecting: 12 revisions left to test after this (roughly 4 steps)
[1b60ce8d5badb730739744323cb7cd4ac6c252af] target: 20 second timeout/megabyte
for CRC check
2010-02-11-14:03
git bisect bad
Bisecting: 6 revisions left to test after this (roughly 3 steps)
[c352c96f74bd5d5c3a498805856e4c2e6145eb0a] arm9tdmi: more correct fix for
vector_catch
2010-02-11-14:07
git bisect good
Bisecting: 3 revisions left to test after this (roughly 2 steps)
[72210fe3a3bcdecbabca5c37d23fa6d548daf2d2] User's Guide: more init info,
autoprobing, etc
2010-02-11-14:09
git bisect good
Bisecting: 1 revision left to test after this (roughly 1 step)
[b5ce7fe8125da3044a2b4f2d0ef57af4d9eef5e7] target: require working area for
physical/virtual addresses to be specified
2010-02-11-14:13
git bisect good
Bisecting: 0 revisions left to test after this (roughly 0 steps)
[f37c9b8d1560d0081e53c71c55113a3c9858011a] arm920t: memory writes were broken
when MMU was disabled
2010-02-11-14:16
git bisect bad
f37c9b8d1560d0081e53c71c55113a3c9858011a is the first bad commit
commit f37c9b8d1560d0081e53c71c55113a3c9858011a
Author: Øyvind Harboe <oyvind.har...@zylin.com>
Date: Tue Nov 3 12:28:00 2009 +0100
arm920t: memory writes were broken when MMU was disabled
To support breakpoints, flush data cache line and invalidate
instruction cache when 4 and 2 byte words are written.
The previous code was trying to write directly to the physical
memory, which was buggy and had a number of other situations
that were not handled.
Signed-off-by: Øyvind Harboe <oyvind.har...@zylin.com>
:040000 040000 9929fd9afd9f244c2e094742465ebbd279b34354
8b9b3a9d6be11783a45c3edc7a98c35e6a6df4e8 M src
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
