STM32 disabling interrupts global in GCC how

I'd go for this one (should already be defined in the CMSIS header 
files):

1

/*disable all interrupts*/

2

static inline __attribute__((always_inline)) void __DISABLE_IRQ(void)

3

{__asm volatile("CPSID i");}

4

5

/*enable all interrupts*/

6

static inline __attribute__((always_inline)) void __ENABLE_IRQ(void)

7

{__asm volatile("CPSIE i");}

See also the ARM documentation in CPSIE:

http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dai0321a/BIHBFEIB.html

Note that "CPSID i" is called "disable interrupts", and the SysTick is 
an exception, not an interrupt. However, "CPSID i" turns also off the 
SysTick exception.

You can also use "CPSID f" instead of "CPSID i", to include fault 
handlers:

http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0497a/BABHBAAB.html

mehmet karakaya schrieb:
> I have a critical code where I want this code not be interrupted by any
> interupt

At first (very first!) try to avoid such kind of code. There is always a 
option to solve a problem in a different way.

Then consider to use the Keil compiler, because the Keil is capable to 
use SVC's (supervisor calls) - but the GCC is not capable to do so. If 
you insist to use the GCC, then you need to write a wrapper for SVC's in 
assembler.

The purpose of the SVC is, that the SVC can be done in Software and the 
called code runs not in user mode, but instead in supervisor mode. This 
may be priorized properly, so you have exactly what you want - without 
using such "disable_int" and so on.

W.S.

W.S. schrieb:
> If you insist to use the GCC, then you need to write a wrapper for
> SVC's in assembler.
It's surprising to see you recommending to avoid Assembly code ?

W.S. schrieb:
> The purpose of the SVC is, that the SVC can be done in Software and the
> called code runs not in user mode, but instead in supervisor mode.

Which makes sense if you are using an RTOS. But if there is an RTOS 
anyway, it should provide easy means for code parts that must not be 
interrupted. However, when going bare metal, I think there is no user 
mode because all code runs as privileged.

There are a number of occasions where disabling interrupts makes sense. 
When fumbling around with the core clock, for example. Or when writing 
to the flash. Ok, it is ill-advised for synchronising data between 
application and interrupts, that has a design smell.

In general, GCC has some advantages over Keil. No code size limit, and 
GCC exists cross-platform so that you can develop, debug and test the 
code e.g. on a host PC. When developing free software, Keil is out of 
the game anyway because it would be self-defeating to require a non-free 
tool to build free software.

Nop schrieb:
> However, when going bare metal, I think there is no user
> mode because all code runs as privileged.

This is rather not the case. But I think, we do not need to have 
arguments. Simply spoken the SVC rises the privilege to the programmed 
level and when all other interrupt levels are tuned accordingly, then 
our TO mehmet karakaya has the final solution. But he seems to be 
absent...

W.S.