“Offline” backtraces decoding is indeed not possible neither with DS 1.2.0, nor with DS 2.0.0
It’s planned to reintroduce this feature in the next release.
Meanwhile, you can do it with TMT, even if the “workaround” is not easy. Actually, from 1.2.0 DS don’t generate anymore the debug axf file required by TMT for backtraces decoding.
Anyway, it’s still possible to do it manually.
Here is the procedure:
Locate the AXFShrinker tool in a former DS 1.1.2 install (or older). This tool is indeed not integrated anymore from DS 1.2.0. It should be located in the plugins/com.wavecom.openat.ide.ebs.build.core.win32_XXX/os/win32 sub-directory of your old DS install;
Please just tell if you can’t grab it, I will post an archive here containing the file.[/]
Run “AXFShrinker yourapp.axf backtraces_app.axf” to produce the backtraces_app.axf debug file[/]
Locate the Firmware package corresponding to the Firmware running on the target[/]
In this package, look for the backtraces64k.axf file[/]
You now have to concatenate these two axf files (FW package’s one, and your app one;
A python script is integrated to do this under Windows (cat.py, integrated in com.wavecom.openat.ide.ebs.build.core_xxx/scripts plug-in), or if you have a Linux shell (or even maybe just a MinGW or Cygwin shell), just use “cat” utility (“cat backtraces64k.axf backtraces_app.axf > backtraces.axf”);
Let’s call the concatenation result “backtraces.axf”[/]
Now back to TMT, you need to provide, in the settings dialog, two files: the backtraces.axf file you’ve just generated, and the xxx.symbols files generated by DS in the output folder of your application project.[/]
From there, you should be able to decode offline backtrace files (retrieved from the ADL API) with TMT.
But please note that:
- backtraces.axf file has to be regenerated each time the application is rebuilt (application AXF has changed…)
- Backtraces decoding algorithm in TMT is sometimes just unable to decode backtraces
Hope this will help…