Wednesday, March 28, 2007
Tips for March 2007
Q: I'm using Optima Tools (Eclipse) to debug an Interrupt Service Routine (ISR). I can step up close to the ISR but when I try to step into or run a breakpoint into it, my system crashes. What is wrong?
A: Unfortunately, stepping through ISRs is not supported with our toolset. You can try it without Eclipse and see if that works, but it might depend on the target. The powerpc-ose-gdb can be used on the command line to accomplish this - tedious, but works.
Q: Okay... I tried using powerpc-ose-gdb on the cygwin command line with the latest Optima Tools release of 1.3 (gdb 6.3 for OSE), and got this error:
$ cd OSETOOLS1.3/gdb_win32_powerpc_6.3/bin
$ ./powerpc-ose-gdb
241 [main] ? (2472) c:\OSE\OSETOOLS1.3\gdb_win32_powerpc_6.3\bin\powerpc-ose
-gdb.exe: *** fatal error - proc magic mismatch detected - 0x8B3C/0xC87757A7.
This problem is probably due to using incompatible versions of the cygwin DLL.
Search for cygwin1.dll using the Windows Start->Find/Search facility
and delete all but the most recent version. The most recent version *should*
reside in x:\cygwin\bin, where 'x' is the drive on which you have
installed the cygwin distribution. Rebooting is also suggested if you
are unable to find another cygwin DLL.
A: Oops, you are using Tools 1.3 version of gdb with the older version of cygwin. We shipped cygwin 1.3 with OSE5.1 and OSE5.1.1, but upgraded to cygwin 1.5 with OSE5.2 . So match your cygwin version to your OSE release before attempting this. Otherwise nothing works, including builds under refsys.
Q: Right, I'm running Tools 1.2 release of powerpc-ose-gdb. What's the command sequence to find out if the connection to the target is okay and to connect to it?
A: cd OSETOOLS1.2/gdb_win32_powerpc_5.2.1/bin
./powerpc-ose-gdb
GNU gdb 5.2.1
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "--host=i686-pc-cygwin --target=powerpc-ose".
(gdb) info ose targets
Hostname Port Id
192.168.3.201 1024 0
Above indicates you're good to go. After first starting gdb, you might have to wait 10-20 secs for this - hit return every 10-20 secs until you see the target info appear. Then you can "target ose 192.168.3.201:1024" followed by "info ose processes" to verify everything is cool with the target.
Q: Wait a minute, I'm running Tools 1.3 version of gdb instead and that doesn't work! I get:
Undefined info ose command: "targets". Try "help info ose".
A: For reasons unknown, this command changed in this tools release. Try "info ose gates" instead, then rinse, cycle, repeat as above. Sorry this isn't better documented.
Q: I was able to see my OSE4.6 target with the Tools 1.2 gdb version, but my Tools 1.3 version doesn't see it. Why?
A: Appears to be a known problem with the newer Tools release. Stick with OSE5 when using Tools 1.3 release version of powerpc-ose-gdb.
A: Unfortunately, stepping through ISRs is not supported with our toolset. You can try it without Eclipse and see if that works, but it might depend on the target. The powerpc-ose-gdb can be used on the command line to accomplish this - tedious, but works.
Q: Okay... I tried using powerpc-ose-gdb on the cygwin command line with the latest Optima Tools release of 1.3 (gdb 6.3 for OSE), and got this error:
$ cd OSETOOLS1.3/gdb_win32_powerpc_6.3/bin
$ ./powerpc-ose-gdb
241 [main] ? (2472) c:\OSE\OSETOOLS1.3\gdb_win32_powerpc_6.3\bin\powerpc-ose
-gdb.exe: *** fatal error - proc magic mismatch detected - 0x8B3C/0xC87757A7.
This problem is probably due to using incompatible versions of the cygwin DLL.
Search for cygwin1.dll using the Windows Start->Find/Search facility
and delete all but the most recent version. The most recent version *should*
reside in x:\cygwin\bin, where 'x' is the drive on which you have
installed the cygwin distribution. Rebooting is also suggested if you
are unable to find another cygwin DLL.
A: Oops, you are using Tools 1.3 version of gdb with the older version of cygwin. We shipped cygwin 1.3 with OSE5.1 and OSE5.1.1, but upgraded to cygwin 1.5 with OSE5.2 . So match your cygwin version to your OSE release before attempting this. Otherwise nothing works, including builds under refsys.
Q: Right, I'm running Tools 1.2 release of powerpc-ose-gdb. What's the command sequence to find out if the connection to the target is okay and to connect to it?
A: cd OSETOOLS1.2/gdb_win32_powerpc_5.2.1/bin
./powerpc-ose-gdb
GNU gdb 5.2.1
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "--host=i686-pc-cygwin --target=powerpc-ose".
(gdb) info ose targets
Hostname Port Id
192.168.3.201 1024 0
Above indicates you're good to go. After first starting gdb, you might have to wait 10-20 secs for this - hit return every 10-20 secs until you see the target info appear. Then you can "target ose 192.168.3.201:1024" followed by "info ose processes" to verify everything is cool with the target.
Q: Wait a minute, I'm running Tools 1.3 version of gdb instead and that doesn't work! I get:
Undefined info ose command: "targets". Try "help info ose".
A: For reasons unknown, this command changed in this tools release. Try "info ose gates" instead, then rinse, cycle, repeat as above. Sorry this isn't better documented.
Q: I was able to see my OSE4.6 target with the Tools 1.2 gdb version, but my Tools 1.3 version doesn't see it. Why?
A: Appears to be a known problem with the newer Tools release. Stick with OSE5 when using Tools 1.3 release version of powerpc-ose-gdb.
free invisible web counter
