On 2010-01-16 14:03, Freddie Chopin wrote: > In 0.2.0 (mingw32 compilation, libftdi-0.16) it works fine. > In 0.3.0-rc0 (mingw32 compilation, libftdi-0.16) it doesn't. > In 0.3.1 (mingw32 compilation, libftdi-0.16) it doesn't. > In 0.4.0-rc1-dev (i686-w64-mingw32 crosscompilation, libftdi-0.17) it > doesn't. > In 0.4.0-rc1-dev (i686-w64-mingw32 crosscompilation, ftd2xx) it doesn't. > > Any ideas? I'll try bisecting that, but this can take me a lot of time );
Here is the bisection: > fred...@linux-e4gc:~/openocd> git bisect log > git bisect start > # good: [64d998e584e0140fff2ead4dfe09f2d14b43c89e] Remove '-in-development' > version tag: 0.2.0-in-development -> 0.2.0 > git bisect good 64d998e584e0140fff2ead4dfe09f2d14b43c89e > # bad: [70f735007d7b0f7ec9d269c4529d9f62c0eb779d] The openocd 0.3.0-rc0 > release. > git bisect bad 70f735007d7b0f7ec9d269c4529d9f62c0eb779d > # skip: [a2a3620d355de1016398576452c62436ccfe6793] - add missing svn props > from previous commit > git bisect skip a2a3620d355de1016398576452c62436ccfe6793 > # good: [6521b75ec2ae41d641910209f0c61b98d34a0c94] - fix build issue under > win32 (cygwin/msys) from svn r2746 > git bisect good 6521b75ec2ae41d641910209f0c61b98d34a0c94 > # bad: [9f6c23f47932eba99acd90949d0388e5ef1fbe35] more xscale cleanup (mostly > removing JTAG hooks) > git bisect bad 9f6c23f47932eba99acd90949d0388e5ef1fbe35 > # bad: [0d3632adff4e64d38650970002569b30bc71a52b] Merge branch 'master' of > ssh://dbrown...@openocd.git.sourceforge.net/gitroot/openocd/openocd > git bisect bad 0d3632adff4e64d38650970002569b30bc71a52b > # bad: [6d4cdddbe27d1b70528d9a70279a2a9b91c1f242] ARM11 command handling fixes > git bisect bad 6d4cdddbe27d1b70528d9a70279a2a9b91c1f242 > # bad: [fbbd3066ffb17b3a5a75b882c4b16aeaa6acad88] Don't provide invalid > OMAP5912 IR capture value/mask attributes > git bisect bad fbbd3066ffb17b3a5a75b882c4b16aeaa6acad88 > # bad: [1c262c8826067b0d240f6db1c4eebf5514ea7475] Try/catch scheme. Typed up > the functionality and regression tested. Ready for discussion and tiny > patches that tries out this scheme. > git bisect bad 1c262c8826067b0d240f6db1c4eebf5514ea7475 > # good: [22045fa6f28813f9e7b17c052f4c7a6c8355178d] When setting up an ETM, > cache its ETM_CONFIG register. Then only expose the registers which are > actually present. They could be missing for two basic reasons: > git bisect good 22045fa6f28813f9e7b17c052f4c7a6c8355178d > # good: [23e22b6ec42c137b48ef6359075a0fe819706f3c] Start handling the > (second) SRST stage of reset better: make sure that when there are two or > more targets, their various pre/post event reports are correctly ordered. > git bisect good 23e22b6ec42c137b48ef6359075a0fe819706f3c > # bad: [37755ffdb63164e768745369a98f06c5ec9d476d] When attaching GDB to > OpenOCD, the target state is no longer affected. Added gdb_sync feature that > allows GDB to sync up to target state. Issue "monitor gdb_sync" and the next > stepi, will return immediately with updated register values to GDB. > git bisect bad 37755ffdb63164e768745369a98f06c5ec9d476d The final message: > fred...@linux-e4gc:~/openocd> git bisect bad > 37755ffdb63164e768745369a98f06c5ec9d476d is the first bad commit > commit 37755ffdb63164e768745369a98f06c5ec9d476d > Author: oharboe <ohar...@b42882b7-edfa-0310-969c-e2dbd0fdcd60> > Date: Thu Sep 24 06:34:23 2009 +0000 > > When attaching GDB to OpenOCD, the target state is no longer affected. > Added gdb_sync feature that allows GDB to sync up to target state. > Issue "monitor gdb_sync" and the next stepi, will return immediately > with updated register values to GDB. > > > git-svn-id: svn://svn.berlios.de/openocd/tr...@2754 > b42882b7-edfa-0310-969c-e2dbd0fdcd60 > > :040000 040000 5b7d371625b7b3f2364f8f8f3880adf8dd190850 > b2a9b4a6e696e18461ae76ede31dc8691886c06a M src No idea how to fix that... 4\/3!! _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
