• State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 19 subscribers
  • Views 1413 views
  • Users 0 members are here
Options
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Dbg_STM32F2xx.ini

Fuchs Leonhard

Hello,

I am busy on a new project with a STM32F207. On our last projects we used STM32F10x-Devices and for debugging purposes I used the corresponding debug.ini file.

/******************************************************************************/
/* Dbg_STM32F2xx.ini: STM32F2xx Debugger Initialization File                  */
/******************************************************************************/
/* This file is part of the uVision/ARM development tools.                    */
/* Copyright (c) 2005-2013 Keil Software. All rights reserved.                */
/* This software may only be used under the terms of a valid, current,        */
/* end user licence from KEIL for a compatible version of KEIL software       */
/* development tools. Nothing else gives you the right to use this software.  */
/******************************************************************************/

 _WDWORD(0xE0042004, 0x00000027);                       // Set DBGMCU_CR

The old ini file was much more verbose and meaningful. And the content of the DBGMCU_CR register is not compatible between F1 and F2 devices.

Do I have to setup the freeze registers BGMCU_APB1_FZ and DBGMCU_APB2_FZ)? Can this be done here in the ini file?

Is there any example ini file available where I can choose the peripherals (timer, can, etc.) which should stop when core is halted?

Thank you
Leo

0