LV2 Handling: Difference between revisions
Jump to navigation
Jump to search
(Created page with "* This only works on DECR-1000 ! <pre> In short: QA Flag needs to have the sys debug flag set. You need to be on a compatible FW (0.92-3.50 DECR with some exclusions). Run th...") |
mNo edit summary |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
* This only works on DECR-1000 ! | * This only works on DECR-1000 ! | ||
* https://workupload.com/file/cDetGwXjCc2 | |||
* 018c25f01f520e598b12b8a5ff2a7324 md5sum | |||
<pre> | <pre> | ||
| Line 10: | Line 12: | ||
Higher firmwares have more restrictions, like you can't read the memory etc. | Higher firmwares have more restrictions, like you can't read the memory etc. | ||
</pre> | </pre> | ||
{{Development}}<noinclude>[[Category:Main]]</noinclude> | |||
Latest revision as of 22:24, 10 November 2020
- This only works on DECR-1000 !
- https://workupload.com/file/cDetGwXjCc2
- 018c25f01f520e598b12b8a5ff2a7324 md5sum
In short: QA Flag needs to have the sys debug flag set. You need to be on a compatible FW (0.92-3.50 DECR with some exclusions). Run this program on the CP. Use an internal license for the ProDG tools. Connect with the TM and as soon as LV2 crashes you can use the Debugger. It only allows you to communicate with the error handler, it's meant for analyzing errors, not for actual source debugging. But you can still do debugging. It's missing in some lv2s. Higher firmwares have more restrictions, like you can't read the memory etc.
