Error code DW_OP 159 from Simplicity Studio when code resets
09/267/2015 | 08:04 AM
We have a unit running a Giant Gecko processor, that has an intermittent reset.
Attaching an axf file to simplicity studio to allow us to debug, results in the Internal error DW_OP 159 occurring when the unit has reset, does anyone know what this error relates to?
Discussion Forums
32-bit MCUs
Answered
Answered
Hi Pete,
Is this on an STK, or your own board? I'm not familiar with the error DR_OP 159. Can you attach a debug log to this thread? You can create a debug log by going to help -> report bug in Simplicity Studio.
Regards,
Joe
Correct Answer
0
Its our own board, we think the error is actually an attempt to display a variable in Simplicity studio that is currently not in scope or hasn't been reset and it doesn't look like its related to the actual resetting issue on our board, which we have now found.
A case of the code doing exactly what it was told, and not what we thought it had been told!
0
159 is
2. DW_OP_stack_value
The DW_OP_stack_value operation specifies that the object does
not exist in memory but its value is nonetheless known and is
at the top of the DWARF expression stack. In this form of
location description, the DWARF expression represents the
actual value of the object, rather than its location. The
DW_OP_stack_value operation terminates the expression.
Error code DW_OP 159 from Simplicity Studio when code resets
We have a unit running a Giant Gecko processor, that has an intermittent reset.
Attaching an axf file to simplicity studio to allow us to debug, results in the Internal error DW_OP 159 occurring when the unit has reset, does anyone know what this error relates to?
Hi Pete,
Is this on an STK, or your own board? I'm not familiar with the error DR_OP 159. Can you attach a debug log to this thread? You can create a debug log by going to help -> report bug in Simplicity Studio.
Regards,
Joe
Its our own board, we think the error is actually an attempt to display a variable in Simplicity studio that is currently not in scope or hasn't been reset and it doesn't look like its related to the actual resetting issue on our board, which we have now found.
A case of the code doing exactly what it was told, and not what we thought it had been told!