[Openocd-development] Fwd: [OpenOCD][PULL Request][MIPS32] CP0 coprocessor manipulation and cache synchronization routines
Hi Øyvind, do you have any update on this pull request ? Maybe some other maintainer can integrate it ? Sorry I am nagging, but you asked yourself ;). BR, Drasko -- Forwarded message -- From: Drasko DRASKOVIC drasko.drasko...@gmail.com Date: Thu, Jul 7, 2011 at 7:27 PM Subject: [OpenOCD][PULL Request][MIPS32] CP0 coprocessor manipulation and cache synchronization routines To: Openocd-Dev openocd-development@lists.berlios.de Hi all, I am happy to present you several exciting enhancements to the MIPS32 target. Most notably : 1) Implemented mips32_cp0_read() and mips32_cp0_write() routines that can affect CP0 copro regs. 2) Implemented command interfaces for these commands, so that they can be called from Telnet interface 3) Implemented cache synchronization, so that we can now support soft breaks on cached regions. Linux can be debugged fine now. All this has been discussed before on ML. I have split all in logically independent commits, so that it can be more easy integrated into the master (I tested each commit independently, and overall version). In the end, I rebased to souceforge's master, so all you have to do is to pull the changes from my github branch. BR, Drasko The following changes since commit ac43d7a69fca52df1ad287b51c44013653ad2f61: Drasko DRASKOVIC (1): mips_m4k and arm7_9 : Fix soft bkpt endianess for 16-bit instructions are available in the git repository at: git://github.com/drasko/openocd.git master Drasko DRASKOVIC (4): mips32: Removed Unnecessary JTAG Queue Flush mips_m4k: common_magic should be unsigned mips32: Added CP0 coprocessor R/W routines mips32: Sync Caches to Make Instr Writes Effective src/target/mips32.c | 106 ++ src/target/mips32.h | 117 --- src/target/mips32_pracc.c | 342 +++-- src/target/mips32_pracc.h | 41 +- src/target/mips_m4k.c | 108 ++- src/target/mips_m4k.h | 7 +- 6 files changed, 679 insertions(+), 42 deletions(-) ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Fwd: [OpenOCD][PULL Request][MIPS32] CP0 coprocessor manipulation and cache synchronization routines
Near as I can tell it's merged. if you check out the tip of your branch locally, then do a git rebase origin/master = do you see any residual commits? -- Øyvind Harboe - Can Zylin Consulting help on your project? US toll free 1-866-980-3434 / International +47 51 87 40 27 http://www.zylin.com/ ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Fwd: [OpenOCD][PULL Request][MIPS32] CP0 coprocessor manipulation and cache synchronization routines
On Fri, Aug 12, 2011 at 11:29 AM, Øyvind Harboe oyvind.har...@zylin.com wrote: Near as I can tell it's merged. if you check out the tip of your branch locally, then do a git rebase origin/master = do you see any residual commits? I checked and saw no residual commits - it seems to be perfect. Thanks a lot ! BR, Drasko ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Fwd: [OpenOCD][PULL Request][MIPS32] Fixed single byte memory write
On Fri, Aug 12, 2011 at 11:31 AM, Øyvind Harboe oyvind.har...@zylin.com wrote: It's merged already. Nice :). Thanks ! BR, Drasko ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] [PATCH] mips: fixing big endian host issues...
nag :-) BR, Stefan -Ursprüngliche Nachricht- Von: openocd-development-boun...@lists.berlios.de [mailto:openocd-development-boun...@lists.berlios.de] Im Auftrag von Mahr, Stefan Gesendet: Donnerstag, 11. August 2011 00:42 An: Drasko DRASKOVIC Cc: Openocd-Dev Betreff: Re: [Openocd-development] [OpenOCD][PULL Request][MIPS32] Fixed single byte memory write Hi Drasko Solution is more common, but the commit history is not clearer. You are fixing several bugs in one patch... Serveral? Just one and a half :-) However, I stripped the alignment fix to a seperate patch file. Please find the three new patches attached. Besides, I have an impression that you know what you are doing. Really? My previous patch breaks byte :-) access for mips_m4k_read_memory. Stefan 0002-mips-fix-reading-uint32-and-uint16-when-running-on-b.patch Description: 0002-mips-fix-reading-uint32-and-uint16-when-running-on-b.patch 0003-mips-fix-potential-alignment-error.patch Description: 0003-mips-fix-potential-alignment-error.patch 0001-target-add-helper-functions-to-get-set-u16-or-u32-ar.patch Description: 0001-target-add-helper-functions-to-get-set-u16-or-u32-ar.patch ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] [PATCH] mips: fixing big endian host issues...
Merged. Thanks! -- Øyvind Harboe - Can Zylin Consulting help on your project? US toll free 1-866-980-3434 / International +47 51 87 40 27 http://www.zylin.com/ ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 MinGW configure failure
On Wed, Aug 10, 2011 at 3:39 PM, Xiaofan Chen xiaof...@gmail.com wrote: On Wed, Aug 10, 2011 at 3:34 PM, Olivier Schonken olivier.schon...@gmail.com wrote: Hi Xiaofan In my case I struggled with the same problem for a day or two. That is why I need to know if it is the checkout of the version, or the updating of the mingw32 compiler that fixed the problem. After doing the ./bootstrap command, the head revision of JimTCL is cloned from its repository - afaik. Thus, to get version 0.63 checked out do the following cd jimtcl git tag -l (Gives you a list of the tags for the jimtcl repository) git checkout 0.63 The version of Jimtcl in the directory should now be 0.63. To view the tags of the openocd source, and checkout for instance 0.5.0-rc2 the same procedure is used. Hopefully this helps, cause I've been trying to replicate the problem without success for a while now. This is clear now. I will make sure that my MinGW/Cygwin setup are up to date and see if that helps. If not, I will follow your suggestion and downgrade jimtcl to see if that help. Thanks for the helps! For my Vista 32bit MinGW setup where the 0.5.0 release does not work, downgrading jimtcl to 0.63 does help -- now it works. There are lots of warnings about jimautoconf.h but in the end it works. ../../../jimtcl/jimautoconf.h:113:0: warning: PACKAGE_BUGREPORT redefined ../../../config.h:231:0: note: this is the location of the previous definition ../../../jimtcl/jimautoconf.h:116:0: warning: PACKAGE_NAME redefined ../../../config.h:234:0: note: this is the location of the previous definition ../../../jimtcl/jimautoconf.h:119:0: warning: PACKAGE_STRING redefined ../../../config.h:237:0: note: this is the location of the previous definition ../../../jimtcl/jimautoconf.h:122:0: warning: PACKAGE_TARNAME redefined ../../../config.h:240:0: note: this is the location of the previous definition ../../../jimtcl/jimautoconf.h:128:0: warning: PACKAGE_VERSION redefined ../../../config.h:246:0: note: this is the location of the previous definition For those who do not use git, you can download the jimtcl 0.63 zip file from github mirror. Replace the jimtcl with this version and then you should be able to build with MinGW. https://github.com/msteveb/jimtcl/zipball/0.63 But I think this is just a temp workaround. -- Xiaofan ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] JLink woes
On Fri, Aug 12, 2011 at 10:04 PM, Xiaofan Chen xiaof...@gmail.com wrote: Then I came across this one thread in Sparkfun. The change seems to make sense as well so I gave it a try. http://forum.sparkfun.com/viewtopic.php?f=18t=24946 It does not seem to help either. But then I find out actually my V8 J-Link works once in about 3 times for EK-LM3S1968 demo board. It works even though that there are still quite a bit of error message but it seems to work. With the on-board TI/Luminary interface, OpenOCD always works. Then I also check out V3/V6/V7 and they all work fine. D:\work\openocd\openocd_0.5.0_mingw\binopenocd.exe -f ek-lm3s1968_jlink.cfg Open On-Chip Debugger 0.5.0 (2011-08-11-13:48) Licensed under GNU GPL v2 For bug reports, read http://openocd.berlios.de/doc/doxygen/bugs.html Warn : Adapter driver 'jlink' did not declare which transports it allows; assumi ng legacy JTAG-only Info : only one transport option; autoselect 'jtag' 500 kHz Info : J-Link initialization started / target CPU reset initiated Info : J-Link compiled Feb 20 2006 18:20:20 -- Update -- Info : J-Link caps 0x3 Info : J-Link hw version 3 Info : J-Link hw type J-Link Info : Vref = 3.290 TCK = 1 TDI = 1 TDO = 1 TMS = 1 SRST = 0 TRST = 255 Info : J-Link JTAG Interface ready Info : clock speed 500 kHz Info : JTAG tap: lm3s1968.cpu tap/device found: 0x3ba00477 (mfg: 0x23b, part: 0x ba00, ver: 0x3) Info : lm3s1968.cpu: hardware has 6 breakpoints, 4 watchpoints D:\work\openocd\openocd_0.5.0_mingw\binopenocd.exe -f ek-lm3s1968_jlink.cfg Open On-Chip Debugger 0.5.0 (2011-08-11-13:48) Licensed under GNU GPL v2 For bug reports, read http://openocd.berlios.de/doc/doxygen/bugs.html Warn : Adapter driver 'jlink' did not declare which transports it allows; assumi ng legacy JTAG-only Info : only one transport option; autoselect 'jtag' 500 kHz Info : J-Link initialization started / target CPU reset initiated Info : J-Link ARM V6 compiled Feb 1 2011 14:28:14 Info : J-Link caps 0x99ff7bbf Info : J-Link hw version 6 Info : J-Link hw type J-Link Info : J-Link max mem block 8864 Info : J-Link configuration Info : USB-Address: 0xff Info : Kickstart power on JTAG-pin 19: 0xff01 Info : Vref = 3.209 TCK = 1 TDI = 0 TDO = 1 TMS = 0 SRST = 0 TRST = 0 Info : J-Link JTAG Interface ready Info : clock speed 500 kHz Info : JTAG tap: lm3s1968.cpu tap/device found: 0x3ba00477 (mfg: 0x23b, part: 0x ba00, ver: 0x3) Info : lm3s1968.cpu: hardware has 6 breakpoints, 4 watchpoints D:\work\openocd\openocd_0.5.0_mingw\binopenocd.exe -f ek-lm3s1968_jlink.cfg Open On-Chip Debugger 0.5.0 (2011-08-11-13:48) Licensed under GNU GPL v2 For bug reports, read http://openocd.berlios.de/doc/doxygen/bugs.html Warn : Adapter driver 'jlink' did not declare which transports it allows; assumi ng legacy JTAG-only Info : only one transport option; autoselect 'jtag' 500 kHz Info : J-Link initialization started / target CPU reset initiated Info : J-Link ARM V7 compiled Feb 15 2011 11:03:33 Info : J-Link caps 0xb9ff7bbf Info : J-Link hw version 7 Info : J-Link hw type J-Link Info : J-Link max mem block 9000 Info : J-Link configuration Info : USB-Address: 0xff Info : Kickstart power on JTAG-pin 19: 0x Info : Vref = 3.196 TCK = 1 TDI = 0 TDO = 1 TMS = 0 SRST = 0 TRST = 0 Info : J-Link JTAG Interface ready Info : clock speed 500 kHz Info : JTAG tap: lm3s1968.cpu tap/device found: 0x3ba00477 (mfg: 0x23b, part: 0x ba00, ver: 0x3) Info : lm3s1968.cpu: hardware has 6 breakpoints, 4 watchpoints -- Xiaofan ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] JLink woes
On Fri, Aug 12, 2011 at 10:10 AM, Xiaofan Chen xiaof...@gmail.com wrote: On Fri, Aug 12, 2011 at 10:04 PM, Xiaofan Chen xiaof...@gmail.com wrote: Then I came across this one thread in Sparkfun. The change seems to make sense as well so I gave it a try. http://forum.sparkfun.com/viewtopic.php?f=18t=24946 It does not seem to help either. But then I find out actually my V8 J-Link works once in about 3 times for EK-LM3S1968 demo board. It works even though that there are still quite a bit of error message but it seems to work. With the on-board TI/Luminary interface, OpenOCD always works. Then I also check out V3/V6/V7 and they all work fine. I have a V8 J-Link, and I can confirm Xiaofan's result that the code from Sparkfun that uses the EMU_CMD_SELECT_IF command does not solve the problem. The commands do execute successfully on initialization, but they report that interface 0 (JTAG) was already selected in the first place. I mentioned previously that I'm using the V8 J-Link on the TI/Logic PD EVM AM1808 board, but using the target/omapl138.cfg file. (They're the same ARM and JTAG route controller inside). When I try to run in this configuration, my J-Link becomes unresponsive. The LED on top of it turns off. Successive attempts to run openocd are met with earlier errors (inability to read HW version info or capabilities), and even the jlink.exe command line program from Segger cannot connect to it, complaining WARNING: Out of sync , resynchronising. After about 100 seconds, the device seems to reenumerate on USB (Windows makes the 'device connected' noise) and the LED comes back on. I'm going to try to use the Linux software from Segger with the kernel's usbmon to capture some commands and see what Segger's doing that we're not. (I've never done any of that before, so I don't expect good results). Best regards, ~Eric ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] JLink woes
On Sat, Aug 13, 2011 at 12:02 AM, Eric Wetzel thewet...@gmail.com wrote: I'm going to try to use the Linux software from Segger with the kernel's usbmon to capture some commands and see what Segger's doing that we're not. (I've never done any of that before, so I don't expect good results). I think this may be a good method for now -- reverse engineering. On the Segger J-Link Linux utility side, you can use usbmon. On the OpenOCD Linux side, you can use usbmon as well but you may want to use the --enable-verbose-usb-comms build option which enables verbose USB communication messages for USB communication debugging. Actually I think a easier way is now that you know 4.14g and lower firmware versions work whereas 4.14h and higher version firmware versions do not work. So a debug capture from OpenOCD may be already good enough to pinpoint the problem (with the --enable-verbose-usb-comms build option). An example from Spen last time. You can see that thread helped. http://lists.berlios.de/pipermail/openocd-development/2009-May/007464.html At that time, a lot of work were done to help bring J-Link to better working status. And it worked much better with Gary's patches including the patches in this thread. http://lists.berlios.de/pipermail/openocd-development/2009-July/009397.html So hopefully more people will jump in this time to fix this V8 issue. :-) -- Xiaofan ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Please welcome Andreas Fritiofson as a new OpenOCD maintainer!
Thank you all for the encouraging comments! I've been an OpenOCD user and followed the project several years now and watched it getting better and better. I'm excited to join the maintainer crew, taking a closer part in that positive progress. I'll start by getting acquainted with the procedures and then, as time permits, begin to review, comment and eventually merge your fine contributions. I do have both a day job and three kids so, while I check the mailing list more or less daily, there may be significant delays before I can respond, or find the time to dive deeper into matters. Best regards, Andreas ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] Build error with mingw32
The current HEAD cannot build with mingw32
libtool: link: i586-mingw32msvc-gcc -std=gnu99 -g -O2
-I/home/jie/installs/openocd/include -D__USE_MINGW_ANSI_STDIO -Wall
-Wstrict-prototypes -Wformat-security -Wshadow -Wextra
-Wno-unused-parameter -Wbad-function-cast -Wcast-align
-Wredundant-decls -Werror -o openocd.exe main.o
-L/home/jie/installs/openocd/lib ./.libs/libopenocd.a -lws2_32
../jimtcl/libjim.a
./.libs/libopenocd.a(libhelper_la-command.o): In function `process_jim_events':
/home/jie/sources/openocd/src/helper/command.c:1398: undefined
reference to `_Jim_ProcessEvents'
collect2: ld returned 1 exit status
make[4]: *** [openocd.exe] Error 1
make[4]: Leaving directory `/home/jie/sources/openocd/src'
Jim_ProcessEvents is defined in jimtcl/jim-eventloop.c.
set needs(eventloop) {expr {[have-feature select] || [have-feature usleep]}}
but
Checking for select...not found
Checking for usleep...not found
It build OK with mingw-w64 since
Checking for usleep...ok
Jie
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Build error with mingw32
On 13/08/2011, at 6:41 AM, Jie Zhang wrote:
The current HEAD cannot build with mingw32
libtool: link: i586-mingw32msvc-gcc -std=gnu99 -g -O2
-I/home/jie/installs/openocd/include -D__USE_MINGW_ANSI_STDIO -Wall
-Wstrict-prototypes -Wformat-security -Wshadow -Wextra
-Wno-unused-parameter -Wbad-function-cast -Wcast-align
-Wredundant-decls -Werror -o openocd.exe main.o
-L/home/jie/installs/openocd/lib ./.libs/libopenocd.a -lws2_32
../jimtcl/libjim.a
./.libs/libopenocd.a(libhelper_la-command.o): In function
`process_jim_events':
/home/jie/sources/openocd/src/helper/command.c:1398: undefined
reference to `_Jim_ProcessEvents'
collect2: ld returned 1 exit status
make[4]: *** [openocd.exe] Error 1
make[4]: Leaving directory `/home/jie/sources/openocd/src'
Jim_ProcessEvents is defined in jimtcl/jim-eventloop.c.
set needs(eventloop) {expr {[have-feature select] || [have-feature usleep]}}
but
Checking for select...not found
Checking for usleep...not found
Can you send me jimtcl/config.log
This is on Linux, right?
--
µWeb: Embedded Web Framework - http://uweb.workware.net.au/
WorkWare Systems Pty Ltd
W: www.workware.net.au P: +61 434 921 300
E: ste...@workware.net.au F: +61 7 3391 6002
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Build error with mingw32
On Fri, Aug 12, 2011 at 5:19 PM, Steve Bennett ste...@workware.net.au wrote:
On 13/08/2011, at 6:41 AM, Jie Zhang wrote:
The current HEAD cannot build with mingw32
libtool: link: i586-mingw32msvc-gcc -std=gnu99 -g -O2
-I/home/jie/installs/openocd/include -D__USE_MINGW_ANSI_STDIO -Wall
-Wstrict-prototypes -Wformat-security -Wshadow -Wextra
-Wno-unused-parameter -Wbad-function-cast -Wcast-align
-Wredundant-decls -Werror -o openocd.exe main.o
-L/home/jie/installs/openocd/lib ./.libs/libopenocd.a -lws2_32
../jimtcl/libjim.a
./.libs/libopenocd.a(libhelper_la-command.o): In function
`process_jim_events':
/home/jie/sources/openocd/src/helper/command.c:1398: undefined
reference to `_Jim_ProcessEvents'
collect2: ld returned 1 exit status
make[4]: *** [openocd.exe] Error 1
make[4]: Leaving directory `/home/jie/sources/openocd/src'
Jim_ProcessEvents is defined in jimtcl/jim-eventloop.c.
set needs(eventloop) {expr {[have-feature select] || [have-feature usleep]}}
but
Checking for select...not found
Checking for usleep...not found
Can you send me jimtcl/config.log
Attached.
This is on Linux, right?
Yes. Debian testing AMD64.
Jie
Invoked as: .././jimtcl/configure --with-jim-ext=nvp --disable-lineedit --disable-install-jim --disable-option-checking --prefix=/home/jie/installs/openocd --enable-maintainer-mode --host=i586-mingw32msvc host_alias=i586-mingw32msvc --cache-file=/dev/null --srcdir=.
Failed: ccache i586-mingw32msvc-cc -g -O2 -c conftest__.c -o conftest__.o
conftest__.c:1:24: error: sys/socket.h: No such file or directory
child process exited abnormally
The failed code was:
#include sys/socket.h
int main(void) {
return 0;
}
Failed: ccache i586-mingw32msvc-cc -g -O2 -c conftest__.c -o conftest__.o
conftest__.c:1:24: error: netinet/in.h: No such file or directory
child process exited abnormally
The failed code was:
#include netinet/in.h
int main(void) {
return 0;
}
Failed: ccache i586-mingw32msvc-cc -g -O2 -c conftest__.c -o conftest__.o
conftest__.c:1:23: error: arpa/inet.h: No such file or directory
child process exited abnormally
The failed code was:
#include arpa/inet.h
int main(void) {
return 0;
}
Failed: ccache i586-mingw32msvc-cc -g -O2 -c conftest__.c -o conftest__.o
conftest__.c:1:19: error: netdb.h: No such file or directory
child process exited abnormally
The failed code was:
#include netdb.h
int main(void) {
return 0;
}
Failed: ccache i586-mingw32msvc-cc -g -O2 -c conftest__.c -o conftest__.o
conftest__.c:1:20: error: sys/un.h: No such file or directory
child process exited abnormally
The failed code was:
#include sys/un.h
int main(void) {
return 0;
}
Failed: ccache i586-mingw32msvc-cc -g -O2 -c conftest__.c -o conftest__.o
conftest__.c:1:19: error: dlfcn.h: No such file or directory
child process exited abnormally
The failed code was:
#include dlfcn.h
int main(void) {
return 0;
}
Failed: ccache i586-mingw32msvc-cc -g -O2 -c conftest__.c -o conftest__.o
conftest__.c:1:25: error: crt_externs.h: No such file or directory
child process exited abnormally
The failed code was:
#include crt_externs.h
int main(void) {
return 0;
}
Failed: ccache i586-mingw32msvc-cc -g -O2 conftest__.c -o conftest__.o
/tmp/cca3kbgO.o: In function `main':
/home/jie/sources/openocd/jimtcl/conftest__.c:3: undefined reference to `_ualarm'
collect2: ld returned 1 exit status
child process exited abnormally
The failed code was:
extern void ualarm(void);
int main(void) {
ualarm();
return 0;
}
Failed: ccache i586-mingw32msvc-cc -g -O2 conftest__.c -o conftest__.o
/tmp/ccOSxm7T.o: In function `main':
/home/jie/sources/openocd/jimtcl/conftest__.c:3: undefined reference to `_sysinfo'
collect2: ld returned 1 exit status
child process exited abnormally
The failed code was:
extern void sysinfo(void);
int main(void) {
sysinfo();
return 0;
}
Failed: ccache i586-mingw32msvc-cc -g -O2 conftest__.c -o conftest__.o
/tmp/ccmzHPx4.o: In function `main':
/home/jie/sources/openocd/jimtcl/conftest__.c:3: undefined reference to `_lstat'
collect2: ld returned 1 exit status
child process exited abnormally
The failed code was:
extern void lstat(void);
int main(void) {
lstat();
return 0;
}
Failed: ccache i586-mingw32msvc-cc -g -O2 conftest__.c -o conftest__.o
conftest__.c:1: warning: conflicting types for built-in function 'fork'
/tmp/cckd557b.o: In function `main':
/home/jie/sources/openocd/jimtcl/conftest__.c:3: undefined reference to `_fork'
collect2: ld returned 1 exit status
child process exited abnormally
The failed code was:
extern void fork(void);
int main(void) {
fork();
return 0;
}
Failed: ccache i586-mingw32msvc-cc -g -O2 conftest__.c -o conftest__.o
/tmp/ccQGyG3k.o: In function `main':
Re: [Openocd-development] Build error with mingw32
On Fri, Aug 12, 2011 at 9:27 PM, Xiaofan Chen xiaof...@gmail.com wrote: On Sat, Aug 13, 2011 at 9:00 AM, Jie Zhang jzhang...@gmail.com wrote: Another option is to drop mingw32 and require mingw-w64. Do not do that. usleep is fine with later version of MinGW.org Win32API package. This is probably because you have a very old version of MinGW and MinGW Win32-API. Seems to be a problem with Debian. http://sourceforge.net/projects/mingw/files/MinGW/BaseSystem/RuntimeLibrary/Win32-API/ Debian seems to ship a 3-year old MinGW Win32-API. http://packages.debian.org/search?searchon=sourcenameskeywords=mingw32 Hmm, good point. I have written an email to the mingw32-runtime package maintainer of Debian to see if he has any plan to update it to the latest version. Regards, Jie ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Build error with mingw32
On Sat, Aug 13, 2011 at 9:38 AM, Jie Zhang jzhang...@gmail.com wrote: On Fri, Aug 12, 2011 at 9:27 PM, Xiaofan Chen xiaof...@gmail.com wrote: On Sat, Aug 13, 2011 at 9:00 AM, Jie Zhang jzhang...@gmail.com wrote: Another option is to drop mingw32 and require mingw-w64. Do not do that. usleep is fine with later version of MinGW.org Win32API package. This is probably because you have a very old version of MinGW and MinGW Win32-API. Seems to be a problem with Debian. http://sourceforge.net/projects/mingw/files/MinGW/BaseSystem/RuntimeLibrary/Win32-API/ Debian seems to ship a 3-year old MinGW Win32-API. http://packages.debian.org/search?searchon=sourcenameskeywords=mingw32 Hmm, good point. I have written an email to the mingw32-runtime package maintainer of Debian to see if he has any plan to update it to the latest version. BTW, there are other problems with the Linux MinGW packages in Debian/Ubuntu. This is one of them which does not affect C based programs like OpenOCD but it will affect C++ based programs. http://comments.gmane.org/gmane.comp.gnu.mingw.user/36693 Basically MinGW.org native compiler and the Cygwin i686-pc-ming32 cross compiler are built with --disable-sjlj-exceptions whereas many Linux MinGW cross compilers are built with a default option which is --enable-sjlj-exceptions. That is the case with MinGW package inside Ubuntu 11.04. On the other hand, MinGW-w64 packages inside Ubuntu is also not that usable since it is quite old (even for the upcoming 11.10). So I always use other versions. But Debian Sid seems to be better in this aspect. -- Xiaofan ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] [PATCH] fix cross compilation: host libsub was used before
On 19:35 Tue 09 Aug , Jean-Christophe PLAGNIOL-VILLARD wrote: tested in buildroot Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagn...@jcrosoft.com --- ok for everyone? if yes I'll prepare a 0.5.1 release as we can not cross compile openocd under buildroot without it Best Regards, J. ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] 0.5.0 release
On 18:56 Thu 11 Aug , Luca BRUNO wrote: Jean-Christophe PLAGNIOL-VILLARD scrisse: HI, I finally get the time to generate the release Sorry for the delay I was busy on the kernel and barebox merge window The tarbal are available at https://sourceforge.net/projects/openocd/files/openocd/0.5.0/ Thanks for your work! Package has been uploaded to Debian and built fine on every supported architectures: https://buildd.debian.org/status/package.php?p=openocd Hopefully it will hit testing in a bunch of weeks; I have to check if it's not to late to have it in Ubuntu, too. I'll push a 0.5.1 soon as it does not build under buildroot as we check the libusb the wrong way for cross compilation I've send a patch [PATCH] fix cross compilation: host libsub was used before Best Regards, J. ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Build error with mingw32
On Sat, Aug 13, 2011 at 11:56 AM, Jie Zhang jzhang...@gmail.com wrote: On Fri, Aug 12, 2011 at 10:15 PM, Xiaofan Chen xiaof...@gmail.com wrote: BTW, there are other problems with the Linux MinGW packages in Debian/Ubuntu. This is one of them which does not affect C based programs like OpenOCD but it will affect C++ based programs. http://comments.gmane.org/gmane.comp.gnu.mingw.user/36693 Basically MinGW.org native compiler and the Cygwin i686-pc-ming32 cross compiler are built with --disable-sjlj-exceptions whereas many Linux MinGW cross compilers are built with a default option which is --enable-sjlj-exceptions. That is the case with MinGW package inside Ubuntu 11.04. In GCC, the default is --disable-sjlj-exceptions. So I'm confused. Maybe the word default is too overloaded. But anyway, the thing is that Linux distros are not following the upstream recommendation of MinGW. In Debian testing, mingw32 is configured with --enable-sjlj-exceptions. mingw-w64 is configured without --enable-sjlj-exceptions. But if we compile all code, including libraries, with one compiler, it should be safe. Yes that is true. On the other hand, MinGW-w64 packages inside Ubuntu is also not that usable since it is quite old (even for the upcoming 11.10). So I always use other versions. But Debian Sid seems to be better in this aspect. I use Debian. That is better but I would still consider as not that good. MinGW-w64 Sourceforge website is a mess but the personal build of sezero is good if you want to use it under Linux (or Windows). http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/sezero_20110510/ http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/sezero_20110510/ If you use Windows, then TDM64 is also good. http://tdm-gcc.tdragon.net/download I use mainly TDM64 under Windows and the following build under Linux, http://code.google.com/p/mingw-w64-dgn/downloads/list -- Xiaofan ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
