Thread: Disable interrupt in ARM M0 program

How do i disable the interrupt in this ARM M0 univesity design start program?
The design is made for the M0 and echos an inputted char as an integer, it is part of a larger piece of code (which is ommitted for simplicity)
Can i do it in the main program(attached) or will i have to edit the assembler code(also attached)?






//--------------------------------------------------------------

Code:

----------------
    // Cortex-M0 DesignStart C program example
    //------------------------------------------------------------------------------
    
    #include <stdio.h>
    #include <time.h>
    #include <rt_misc.h>
    #include <stdlib.h>
    
    #define AHB_LED_BASE                0x50000000
    #define AHB_UART_BASE                0x51000000
    
    
    void UART_ISR(void)
    {
                int sample;
                char ch [16];
                sample = atoi (ch);
                printf("the value entered is %d\n", sample);
    }
    
    //////////////////////////////////////////////////////////////////
    // Main Function
    //////////////////////////////////////////////////////////////////
    
    int main() 
        {
        
            char ch [16];
            while(1==1)
            {
            fgets (ch, 16, stdin);
        //printf("String: %s\n\n",ch);
            }
    }

Assembly code

Code:

UART_Handler    PROC
                    EXPORT UART_Handler
                    IMPORT UART_ISR
                    PUSH    {R0,R1,R2,LR}
                    LDR     R1, =0x51000000               ;UART
                    LDR     R0, [R1]                      ;Get Data from UART
                    STR     R0, [R1]                      ;Write to UART
    
                    BL UART_ISR
    
                    POP     {R0,R1,R2,PC}
                    ENDP
    
                    
                    ALIGN 4

Check the compiler documentation - this should tell you how to disable interrupts using C. Reviewing the data sheet for the specific device would also be a good idea, as there might be more than a single interrupt configuration (i.e. global enable/disable versus individual).