vFlash

• Interactive flashing via the user interface (Desktop Editions) and automated flashing via a programming interface (Test Bench Editions – with C API and C# API) for process integration and integration into an existing software environment.
• Flexible referencing of flashware during the development phase for quick testing of code changes or easy replacement of preconfigured flash projects in a single package, also protected against unwanted changes.
• Software update using “native” data in Intel Hex, Motorola S, and binary formats or, alternatively, based on container formats such as ODX-F and manufacturer-specific formats.
• vFlash Standard Variant for updating ECUs via a single channel – also for consistent updating of multiple ECUs with vFlash Desktop Edition and the “System Update” feature.
• vFlash Station Variant for parallel flashing of up to 10 ECUs via their own channel – can be used directly for just-in-time updates via the GUI (vFlash Station Desktop Edition) or integrated via an automation interface (vFlash Station Test Bench Edition), for example in a production application.
• Flexible extension of OEM flash sequences through so-called “Custom Actions” that are executed before and/or after flashing.

• Encoding or data backup with data recovery using Custom Actions.
• Documentation and quality assurance of flash actions in flash reports using Custom Actions or the built-in short report.
• Flashing of compressed and encrypted data.
• Validation of the flash bootloader in the ECU in combination with CANoe.DiVa (via CAN, FlexRay, DoIP, LIN) – for CAN (FD) and Ethernet also in a virtual environment using the “SIL Kit.”
• Use of vFlash in the context of HIL testing – CANoe uses vFlash, for example, to load test software onto the SUT in order to then perform specific tests.
• Authentication based on the “Security Manager” Add-Ons from OEMs and suppliers.
• Tracing of CAN(FD) and Ethernet communication for more detailed analysis in the event of a fault.
• Network management: Cyclical and event-based sending of static CAN (FD) messages
• Securing DoIP communication using TLS (ISO13400-3), even via a Windows-managed Ethernet adapter.
• Ethernet functions: IPv4 and IPv6 via 100/1000BASE-T1, 100/1000BASE-TX, 10BASE-T1s; support for VLAN, DHCP, and SLACK; waking up ECUs – via the DoIP Activation Line or via Open Alliance TC10.

• A new Python API makes it easier than ever to integrate vFlash into user applications, CI/CD pipelines and automated toolchains.
• User applications can now control vFlash on the Vector VN8900 and VT6000 hardware platforms via the new SOVD API – opening the door to more flexible, service-oriented workflows and future-ready diagnostic environments.

• For system-level update scenarios, vFlash System Update now supports parallel and synchronized updates of multiple ECUs in a subsystem or vehicle via a single connection. This makes coordinated and consistent updates more efficient.

• vFlash 12 extends the support for OEMs and Tier-1 suppliers. vFlash now also supports Bosch’s proprietary interpretation of HEX flashware formats containing multiple datablocks and multiple segments, efficiently and conveniently controlled through a single Memory Description File.
• With support for more than 100 OEMs and over 250 OEM and Tier-1 bootloaders, vFlash 12 provides a powerful foundation for standardized, reliable, and future-ready ECU update processes.
• Support of the JLR ODX-F Flashware file format (ODX-F files that reference JLR VBF files)

• The vFlash Station GUI has also been enhanced with a new user interface for getting more detailed information about the currently active just-in-time parallel ECU software update, each operated on a separate connection. This is especially valuable in pre-production environments where throughput optimization, time savings and cost efficiency are key success factors. The solution can be used interactively and can also be integrated into an existing production application.

• vFlash 12 also simplifies software updates for lightweight MICROSAR IO ECUs. These ECUs can now be updated even when the companion ECU is not yet available, enabling earlier validation.

Vector Tool Platform

VN8900

^{*After updating to Windows 10}

VT6000