Embedded House
  • Embedded Linux
    • Part 0: An small Introduction
    • Part 1: Board bring-up
    • Part 2: Bootloader configuration
    • Part 3: Kernel configuration
    • Part 4: Device drivers
    • Part 5: Device Tree
    • Part 6: Root filesystems
  • Docker for Embedded
    • Part 0: Prerequisites and tools
    • Part 1: Your first container build
    • Part 2: Containers for embedded
    • Part 3: Using more than one image
    • Part 4: Time to Docker Compose
    • Part 5: Docker Hub and docker registry
    • Part 6: Continuous Integration with docker
    • Part 7: Docker for VSCode Lovers
  • Aurix with iLLD
    • Part 00: Setting your environment
    • Part 01: The Infineon Low Level Drivers
    • Part 02: Ports and Digital Input Outputs
    • Part 03: System Timer
    • Part 04: Interrupt Router
    • Part 05: Multicore
    • Part 06: Clock System
  • FreeRTOS
    • Part 0: Setting your Tools
    • Part 1: Task
    • Part 2: Queues
    • Part 3: Timers
    • Part 4: Interrupts
    • Part 5: Mutexes
    • Part 6: Direct to task notifications
    • Part 7: Stream and messages buffer
    • Part 8: FreeRTOS Kernel Analisis
    • Part 9: FreeRTOS Command Line Interface (CLI)
  • Autosar MCAL with NXP S32K1xx
    • Part 0: Setup your Autosar Tools
    • Part I: Port and Dio drivers
    • Part II: Mcu Driver
    • Part III: Gpt Driver
    • Part IV: Platform and Base drivers
    • Part V: Adc Driver
    • Part VI: Pwm
    • Part VII: Spi Driver
    • Part VIII: Can Driver
    • Post IX: CanIf Driver
  • Unit testing with Ceedling
    • Part 0: Setting up the tools
    • Part I: Testing functions
    • Part II: Testing more complex data
    • Part III: Unit testing private things
    • Part IV: Unit Testing State Machines
    • Part IX: Unit Testing Registers
    • Part V: Code Coverage
    • Part VI: Integration Testing
    • Part VII: Testing with Mocks
    • Part VIII: Mocking the STM32 library
  • Algorithms
    • 000: Hash Tables, or sort of
    • 001: Concurrent processes
    • 002: Round Robin Scheduler
    • 003: Queue Buffers
    • 004: Managing Buttons
    • 005: Intro to State Machines
  • From scratch
    • Part I: Playing around with GCC (ARM flavor)
    • Part II: Playing around with multiple files
    • Part III: Compiler options and makefiles
    • Part IV: The Compiler and the Memory
    • Part IX: Linker Memory Regions
    • Part V: The Linker and the Memory
    • Part VI: Linker scripts to Map the memory
    • Part VII: Linker scripts to Map the memory
    • Part VIII: Linker scripts to map the memory
    • Part X: First program ever
    • Part XI: First program ever
    • Part XII: Enter OpenOCD
    • Part XIII: Init the .bss section
    • Part XIV: Init the .data section
    • Part XIX: Adding the Standard library
  • Application Notes
    • AN000: The way we work
    • AN001: The stm32 makefile
    • AN002: VSCode Intellisense
    • AN003: Debugging with VSCode
    • AN004: Semihosting
    • AN005: SocketCAN and can-utils
    • AN006: MISRA with Cppcheck
    • AN007: Documenting with Doxygen
    • AN008: Reading AUTOSAR Docs
    • AN009: YAML Notation for Tresos configuration
    • AN010: Tresos Tips and Tricks
    • AN011: SavvyCAN, CAN bus analyzer
    • AN012: Printf with Segger RTT
    • AN013: Setup WSL for Embedded Development
    • AN014: GDBGUI, a debugger in your web browser
  • Stm32g0 with HAL library
    • Part 00: Setting up your tools
    • Part 01: General Purpose Input Outputs
    • Part 02: Nested Vector Interrupt Controller
    • Part 03: Timers Module
    • Part 04: Universal Asynchronous Receiver Transmitter
    • Part 05: System Clocks
    • Part 06: Analog to Digital Converter
    • Part 07: Serial Peripheral Interface
    • Part 08: Pulse Width Modulation
    • Part 09: Controller Area Network
    • Part 10: Direct Memory Access
  • Home
  • Trainings
  • About
You've successfully subscribed to Embedded House
Great! Next, complete checkout for full access to Embedded House
Welcome back! You've successfully signed in.
Success! Your account is fully activated, you now have access to all content.
Success! Your billing info is updated.
Billing info update failed.

IR: Two Sw interrupt with the same vector

This post is for subscribers on the Expert tier only

Subscribe now

Already have an account? Sign in

Previous CAN: Transmission using two CAN controllers
Next IR: Software interrupts
Updated 3 months ago