??? 10/07/08 18:05 Modified: 10/07/08 18:09 Read: times |
#158911 - Versa Debugger and Nooverlay Responding to: ???'s previous message |
Simply, if you select Nooverlay linker directive, Versa Debugger won't start, complaining about missing or corrupt files.
Actually, it takes linker M51 file (yes, it does not support LX51 too as the linker listing file looks differently) and .LST files produced by compiler and extract required info from there. The most probable reason is that Keil's OMF51 extensions are not public so they can't use linker object output file instead. As a result, you have a horrible mess with variable watch window showing all defined variables, local or global, you can't see structure members, etc. etc. It's a pity they are not interested in writing a driver for Keil's uVision, as that's the only reasonable way. I offered to write it myself free of charge, as I REALLY hate their debugger, but as usual, got no response. And to spice it up a little bit more - a link on their page to the latest debugger release points to the corrupt file (ca.640K instead of 3.6M)... - Dejan |
Topic | Author | Date |
Ramtron Versa Debugger problems | 01/01/70 00:00 | |
What stuff | 01/01/70 00:00 | |
Pressed send too fast | 01/01/70 00:00 | |
links | 01/01/70 00:00 | |
Thx | 01/01/70 00:00 | |
I used it with SDCC only... | 01/01/70 00:00 | |
Project Configuration? | 01/01/70 00:00 | |
Solved... | 01/01/70 00:00 | |
throw it at their head | 01/01/70 00:00 | |
Ramtron, Ramtron... | 01/01/70 00:00 | |
Could you be a bit more specific? | 01/01/70 00:00 | |
oddly enough | 01/01/70 00:00 | |
Versa Debugger and Nooverlay | 01/01/70 00:00 | |
OUCH | 01/01/70 00:00 | |
re: OUCH![]() | 01/01/70 00:00 |