Interrupts are not working when I jump to the application (STM32)

Question

I want to use the latest HAL library instead of Standard Peripheral Library.

And I want to read out the BMA250E G-sensor's chip_id, but it doesn't work.

The value of aRxBuffer always keep at 0x00. But it should be 0xF9!

What's wrong in my code?

‪#‎include‬ "stm32f4xx_hal.h"

#define I2Cx_SDA_GPIO_CLK_ENABLE() __HAL_RCC_GPIOB_CLK_ENABLE()
#define I2Cx_SDA_PIN GPIO_PIN_9
#define I2Cx_SDA_GPIO_PORT GPIOB
#define I2Cx_SDA_AF GPIO_AF4_I2C1

#define I2Cx_SCL_GPIO_CLK_ENABLE() __HAL_RCC_GPIOB_CLK_ENABLE()
#define I2Cx_SCL_PIN GPIO_PIN_6
#define I2Cx_SCL_GPIO_PORT GPIOB
#define I2Cx_SCL_AF GPIO_AF4_I2C1

#define I2Cx_CLK_ENABLE() __HAL_RCC_I2C1_CLK_ENABLE()
#define I2Cx_FORCE_RESET() __HAL_RCC_I2C1_FORCE_RESET()
#define I2Cx_RELEASE_RESET() __HAL_RCC_I2C1_RELEASE_RESET()

‪#‎define‬ I2C_ADDRESS 0x18

static void SystemClock_Config(void);

uint8_t aTxBuffer[2], aRxBuffer;

int main()
{
    HAL_Init();
    SystemClock_Config();
    I2C_HandleTypeDef I2cHandle;

    I2cHandle.Instance = I2C1;
    I2cHandle.Init.AddressingMode = I2C_ADDRESSINGMODE_7BIT;
    I2cHandle.Init.ClockSpeed = 400000;
    I2cHandle.Init.DualAddressMode = I2C_DUALADDRESS_DISABLE;
    I2cHandle.Init.DutyCycle = I2C_DUTYCYCLE_16_9;
    I2cHandle.Init.GeneralCallMode = I2C_GENERALCALL_DISABLE;
    I2cHandle.Init.NoStretchMode = I2C_NOSTRETCH_DISABLE;
    I2cHandle.Init.OwnAddress1 = 0;
    I2cHandle.Init.OwnAddress2 = 0;

    HAL_I2C_Init(&I2cHandle);

    aTxBuffer[0] = 0x00;
    HAL_I2C_Master_Transmit(&I2cHandle, I2C_ADDRESS, aTxBuffer, 1, 10000);
    HAL_I2C_Master_Receive(&I2cHandle, I2C_ADDRESS|0x01, &aRxBuffer, 1, 10000);
    HAL_Delay(1000);
}

 static void SystemClock_Config(void)
 {
    RCC_ClkInitTypeDef RCC_ClkInitStruct;
    RCC_OscInitTypeDef RCC_OscInitStruct;

    __HAL_PWR_VOLTAGESCALING_CONFIG(PWR_REGULATOR_VOLTAGE_SCALE1);
    RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSE;
    RCC_OscInitStruct.HSEState = RCC_HSE_ON;
    RCC_OscInitStruct.PLL.PLLState = RCC_PLL_ON;
    RCC_OscInitStruct.PLL.PLLSource = RCC_PLLSOURCE_HSE;
    RCC_OscInitStruct.PLL.PLLM = 8;
    RCC_OscInitStruct.PLL.PLLN = 360;
    RCC_OscInitStruct.PLL.PLLP = RCC_PLLP_DIV2;
    RCC_OscInitStruct.PLL.PLLQ = 7;
    HAL_RCC_OscConfig(&RCC_OscInitStruct);
    RCC_ClkInitStruct.ClockType =
        (RCC_CLOCKTYPE_SYSCLK | RCC_CLOCKTYPE_HCLK |
         RCC_CLOCKTYPE_PCLK1 | RCC_CLOCKTYPE_PCLK2);
    RCC_ClkInitStruct.SYSCLKSource = RCC_SYSCLKSOURCE_PLLCLK;
    RCC_ClkInitStruct.AHBCLKDivider = RCC_SYSCLK_DIV1;
    RCC_ClkInitStruct.APB1CLKDivider = RCC_HCLK_DIV4;
    RCC_ClkInitStruct.APB2CLKDivider = RCC_HCLK_DIV2;
    HAL_RCC_ClockConfig(&RCC_ClkInitStruct, FLASH_LATENCY_5);
}

void HAL_I2C_MspInit(I2C_HandleTypeDef *hi2c)
{
    GPIO_InitTypeDef GPIO_InitStruct;

    I2Cx_SCL_GPIO_CLK_ENABLE();
    I2Cx_SDA_GPIO_CLK_ENABLE();

    GPIO_InitStruct.Pin = I2Cx_SCL_PIN;
    GPIO_InitStruct.Mode = GPIO_MODE_AF_OD;
    GPIO_InitStruct.Pull = GPIO_PULLUP;
    GPIO_InitStruct.Speed = GPIO_SPEED_FAST;
    GPIO_InitStruct.Alternate = I2Cx_SCL_AF;
    HAL_GPIO_Init(I2Cx_SCL_GPIO_PORT, &GPIO_InitStruct);

    GPIO_InitStruct.Pin = I2Cx_SDA_PIN;
    GPIO_InitStruct.Alternate = I2Cx_SDA_AF;
    HAL_GPIO_Init(I2Cx_SDA_GPIO_PORT, &GPIO_InitStruct);
}

void HAL_I2C_MspDeInit(I2C_HandleTypeDef *hi2c)
{
    I2Cx_FORCE_RESET();
    I2Cx_RELEASE_RESET();
    HAL_GPIO_DeInit(I2Cx_SCL_GPIO_PORT, I2Cx_SCL_PIN);
    HAL_GPIO_DeInit(I2Cx_SDA_GPIO_PORT, I2Cx_SDA_PIN);
}

Your "bootloader" code seems to disable all interrupts. Do your main "application" code enable interrupts again? — Some programmer dude
– Some programmer dude, Commented Mar 12, 2019 at 10:44
I added __enable_irq() as the first line in main in my blinky program. Now both LED's do not toggle. — mbards
– mbards, Commented Mar 12, 2019 at 12:44
FYI: arm KEIL: ARM: How to Write a Bootloader: keil.com/support/docs/3913.htm — Gabriel Staples
– Gabriel Staples, Commented Mar 14, 2019 at 7:42

followed Monica to Codidact · Accepted Answer · 2019-03-12 13:34:39Z

6

In projects generated by STM32CubeMX, the SystemInit() function in system_stm32f4xx.c, called by the startup code before main(), resets the vector table address register to the start of the FLASH.

/* #define VECT_TAB_SRAM */
#define VECT_TAB_OFFSET  0x00 /*!< Vector Table base offset field.
                                   This value must be a multiple of 0x200. */

/* -- snip -- */

#ifdef VECT_TAB_SRAM
  SCB->VTOR = SRAM_BASE | VECT_TAB_OFFSET; /* Vector Table Relocation in Internal SRAM */
#else
  SCB->VTOR = FLASH_BASE | VECT_TAB_OFFSET; /* Vector Table Relocation in Internal FLASH */
#endif

You can edit this file directly (and not run STM32CubeMX on the project again, because it appears to overwrite this file), or simply set the right value again in main(), before enabling interrupts.

answered Mar 12, 2019 at 13:34

followed Monica to Codidact

8,1591 gold badge27 silver badges40 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

mbards Over a year ago

I added SCB->VTOR = 0x8060000; to my application and it works! Thanks @berendi. Any idea why the debugger didn't update the VTOR register in my viewer after I jumped? I was watching for this.

AdvancedNewbie Over a year ago

Thank you for this. 'SCB->VTOR = ((uint32_t)FIRMWARE_START_ADDR);' also worked for me.

Collectives™ on Stack Overflow

Interrupts are not working when I jump to the application (STM32)

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related