topic CW4.6: 9S12XDP512: debug break point problems with XGATE in CodeWarrior for MCU https://community.nxp.com/t5/CodeWarrior-for-MCU/CW4-6-9S12XDP512-debug-break-point-problems-with-XGATE/m-p/193295#M7024 <HTML><HEAD></HEAD><BODY><SPAN>We are using a 9S12XDP512, and have C code doing the initialization, transferring execution to old assembly code that is in the process of being converted. We are using the XGATE.</SPAN><BR /><BR /><SPAN>When we step through the code, the XGATE control register is left alone from it's initial value (0x0000).</SPAN><BR /><BR /><SPAN>When we set a break point, the debugger sets the XGDBG bit, setting the XGMCTL register to a minimum of 0x0020.</SPAN><BR /><BR /><SPAN>On resume of code execution, this debug bit is not cleared, and our old assembly code doesn't touch XGMCTL again after initialization. So the XGATE stays in debug mode, freezing it's execution.</SPAN><BR /><BR /><SPAN>Is there a way to have the debugger restore XGMCTL to it's previous state before the break point?</SPAN><BR /><BR /><SPAN>Thanks, Paul.</SPAN><BR /><DIV> </DIV></BODY></HTML> Tue, 14 Oct 2008 02:55:09 GMT paulcsf 2008-10-14T02:55:09Z CW4.6: 9S12XDP512: debug break point problems with XGATE https://community.nxp.com/t5/CodeWarrior-for-MCU/CW4-6-9S12XDP512-debug-break-point-problems-with-XGATE/m-p/193295#M7024 <HTML><HEAD></HEAD><BODY><SPAN>We are using a 9S12XDP512, and have C code doing the initialization, transferring execution to old assembly code that is in the process of being converted. We are using the XGATE.</SPAN><BR /><BR /><SPAN>When we step through the code, the XGATE control register is left alone from it's initial value (0x0000).</SPAN><BR /><BR /><SPAN>When we set a break point, the debugger sets the XGDBG bit, setting the XGMCTL register to a minimum of 0x0020.</SPAN><BR /><BR /><SPAN>On resume of code execution, this debug bit is not cleared, and our old assembly code doesn't touch XGMCTL again after initialization. So the XGATE stays in debug mode, freezing it's execution.</SPAN><BR /><BR /><SPAN>Is there a way to have the debugger restore XGMCTL to it's previous state before the break point?</SPAN><BR /><BR /><SPAN>Thanks, Paul.</SPAN><BR /><DIV> </DIV></BODY></HTML> Tue, 14 Oct 2008 02:55:09 GMT https://community.nxp.com/t5/CodeWarrior-for-MCU/CW4-6-9S12XDP512-debug-break-point-problems-with-XGATE/m-p/193295#M7024 paulcsf 2008-10-14T02:55:09Z Re: CW4.6: 9S12XDP512: debug break point problems with XGATE https://community.nxp.com/t5/CodeWarrior-for-MCU/CW4-6-9S12XDP512-debug-break-point-problems-with-XGATE/m-p/193296#M7025 <HTML><HEAD></HEAD><BODY>Well, we found it.<BR /><BR />We were initializing the XGATE with XGMCTL=0x8383, which has the wrong state for BDM freeze operation.<BR /><BR />The fix was to initialize the XGATE with XGMCTL=0xC3C3, causing the XGATE to freeze in DBM debug mode.<BR /><BR /><BR /><DIV></DIV></BODY></HTML> Tue, 14 Oct 2008 04:05:51 GMT https://community.nxp.com/t5/CodeWarrior-for-MCU/CW4-6-9S12XDP512-debug-break-point-problems-with-XGATE/m-p/193296#M7025 paulcsf 2008-10-14T04:05:51Z