How amosproj/amos2024ss07-updating-flash-boot-loader works
Project type and purpose
• This is an embedded-plus-host application. On the embedded side you have a Flash Boot Loader (FBL) running on an Infineon AURIX™ TC375 microcontroller. On the host side you have a Windows GUI tool (built with Qt, CMake, Vector’s VXLAPI) that uses ISO-15765-2/CAN and UDS (ISO-14229) to update the firmware.
File structure
• Top-level:
• Deliverables, Documentation – static docs, design artifacts
• MCU_Aurix – embedded project (Eclipse/.cproject, .ads scripts)
– bootloader (src/inc)
– driver (CAN, flash, LED, reset)
– main (Cpu0_Main.c, Cpu1_Main.c, Cpu2_Main.c)
– Libraries: Infineon iLLD, SFR, Service, pinmapper, linker scripts
• WINDOWS_GUI – production GUI (C++/Qt)
– Communication (CAN wrapper, virtual driver)
– Communication_Layer (abstracted CommInterface)
– UDS_Layer, UDS_Spec
– UI (mainwindow.ui, controllers, flashmanager, validatemanager)
• TESTING_WINDOWS_GUI – unit/integration tests for the GUI and communication
README for additional insights
• Confirms embedded FBL goal and Windows PC GUI
• Mentions protocols: CAN, ISO-15765-2, UDS
• Lists key features: MCU reset, log window, firmware transfer
Elements
• Clear labels: e.g., “CAN Wrapper (VXLAPI)”, “UDS Layer”, “Bootloader Session Manager”
• From GUI button → FlashManager → UDS → CAN
• From MCU Bootloader → UDS → CAN → GUI log
• Network line style for CAN bus