cancel
Showing results for 
Search instead for 
Did you mean: 

CubeIDE - SCB.CCR address for 'F0 (Cortex-M0)

While trying to help with a problem on STM32F030, I've noticed this:

waclawekjan_0-1716643090171.png

the address of SCB.CCR is 0xE000ED14; and the displayed value is wrong, too, as it's a read-only register with fixed value of 0x0208 (see ARMv6M ARM p.B3-228 - characteristically, the reset value given there is incorrect, too...).

I don't use/have CubeIDE; can somebody please check and confirm/reject?

Thanks,

JW

 

4 REPLIES 4
Pavel A.
Evangelist III

If you don't have CubeIDE how you got this screenshot? If this is from the person you're helping, please ask them which version do they have? The registers file is part of the debugger bundled with the IDE.

 

> If you don't have CubeIDE how you got this screenshot?

From the stackexchange thread I've linked to above (to avoid misunderstanding: that thread is not about the SCB register; I just noticed the mismatch there).

> which version do they have?

It appears to be 1.15.1:

waclawekjan_0-1716676850528.png

JW

Pavel A.
Evangelist III

I don't have F030 with me but checked on a C031. CCR has correct address.

PavelA_0-1716679537685.png

Then found the svd file for F0 in the installed CubeIDE:

...CubeIDE1.15\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.productdb.debug_2.1.300.202404050853\resources\cmsis\STMicroelectronics_CMSIS_SVD\STM32F0x0.svd

and there the offset looks correct too. So I don't know... 

 

 

 <peripheral>
      <name>SCB</name>
      <description>System control block</description>
      <groupName>SCB</groupName>
      <baseAddress>0xE000ED00</baseAddress>
............
        <register>
          <name>CCR</name>
          <displayName>CCR</displayName>
          <description>Configuration and control
          register</description>
          <addressOffset>0x14</addressOffset>
          <size>0x20</size>
          <access>read-write</access>
          <resetValue>0x00000000</resetValue>
...............

 

 

 

I see. Thanks, @Pavel A. .

It's a mystery how that occured, then.

JW