Automotive Gateway and CAN FD Solution

Application

Description

Automotive-grade gateway solution with CAN FD support, Ethernet connectivity, and secure boot for next-generation vehicle networks.

Core Advantages

300MHz Cortex-M7 provides 3x performance improvement over previous generation
Integrated CAN FD eliminates need for external CAN controllers
Hardware security module enables secure boot and encrypted communication
ASIL-B compliance with hardware safety features reduces certification effort

Recommended Bill of Materials (BOM)

Item Part Number Description Quantity Datasheet
1 Complete automotive gateway with 8 CAN FD channels 📄 Download

Applications

Central gateway controllers
Domain controllers (powertrain, chassis, body)
Zone controllers for zonal E/E architecture
Fleet management and telematics gateways
Diagnostic and programming tools
ADAS sensor fusion hubs

Technical Specifications

C A N F D Channels
8 (6 internal + 2 external)
C A N F D Data Rate
Up to 5 Mbps
Ethernet
Dual 10/100 Mbps with TSN
Processor
ARM Cortex-M7 @ 300MHz
Flash Memory
2MB with ECC
R A M
384KB with ECC
Operating Temperature
-40°C to +125°C
Safety Rating
ASIL-B

Customer Success Stories

AutoTech Systems GmbH

Automotive |

Challenge

Needed high-performance gateway for new domain-based E/E architecture with cybersecurity requirements

Solution

Implemented SAM E70-based gateway with 8 CAN FD channels and hardware security

Results

Achieved 5x bandwidth improvement, passed ISO/SAE 21434 cybersecurity audit, production volume 100K+ units/year

FAE Expert Insights

F

FAE Expert

Field Application Engineer

Professional Insights

Ready to Implement This Solution?

Contact our FAE team for design support and quotes

Contact Us Now

Frequently Asked Questions

What is the difference between CAN 2.0 and CAN FD?

CAN FD (Flexible Data-rate) is the next generation of CAN protocol with two key improvements: 1) Higher data rates - CAN FD supports up to 5 Mbps during the data phase (vs 1 Mbps max for CAN 2.0)

2) Larger payload - CAN FD supports up to 64 bytes per frame (vs 8 bytes for CAN 2.0). The arbitration phase remains at standard CAN speeds for compatibility. This means CAN FD can transfer 8x more data in the same time, or transfer the same data using less bus bandwidth. CAN FD is backward compatible at the physical layer but requires new controllers and transceivers.

Use CAN FD for new designs requiring high bandwidth; maintain CAN 2.0 compatibility during migration via gateway translation.

How do I implement secure boot on the SAM E70?

Secure boot implementation on SAM E70 involves: 1) Generate RSA key pair - private key kept secure, public key programmed into device OTP

2) Sign firmware image with private key using Microchip's signing tools

3) Configure boot ROM to verify signature before execution

4) Store signature and public key in dedicated secure memory

5) Enable tamper detection to prevent physical attacks. The ATECC608A can store keys and perform verification, offloading the main CPU. On boot, the ROM verifies firmware signature - if invalid, device enters safe mode. This prevents execution of unauthorized or corrupted firmware.

Use Microchip's secure boot tools; store keys in ATECC608A; enable tamper detection for production systems.

What is ASIL-B and why is it important?

ASIL (Automotive Safety Integrity Level) is a risk classification system defined in ISO 26262 for automotive functional safety. ASIL-B is the second-lowest level (B, A, C, D with D being highest). It applies to systems with moderate safety risk where failure could cause injury but not life-threatening. ASIL-B requires specific hardware and software safety mechanisms: ECC memory for data integrity, clock monitoring for timing integrity, watchdog timers for software monitoring, and safe state management. The SAM E70 includes hardware features that support ASIL-B compliance including dual-core lockstep, ECC, and safety monitor. Certification requires documentation of safety requirements, failure analysis (FMEDA), and testing.

ASIL-B suitable for body electronics and non-critical chassis systems; contact FAE for ASIL-C/D solutions.

Can this solution support AUTOSAR?

Yes, the SAM E70 is fully supported by AUTOSAR Classic Platform. Microchip provides MCAL (Microcontroller Driver Layer) drivers for all peripherals including CAN FD, Ethernet, ADC, and timers. The drivers are certified to AUTOSAR 4.4 standards and include: CAN driver with CAN FD support, Ethernet driver with TSN support, SPI and I2C drivers, ADC driver with DMA support, PWM and ICU drivers, Watchdog driver, and Flash driver for EEPROM emulation. The solution has been integrated with major AUTOSAR stacks including Vector, EB, and ETAS. BeiLuo can provide AUTOSAR integration support and training.

MCAL drivers available for AUTOSAR Classic; contact FAE for AUTOSAR Adaptive or specific stack integration.

How do I implement over-the-air firmware updates?

Over-the-air (OTA) firmware updates require a secure bootloader and update mechanism: 1) Implement dual-bank Flash with active and update partitions

2) Download encrypted firmware image to update partition

3) Verify image signature using ATECC608A before activation

4) Validate image integrity with CRC/SHA

5) Atomic switch to new firmware with rollback capability

6) Confirm successful boot before erasing old firmware. The SAM E70's 2MB Flash supports dual-bank operation. Use the secure element for signature verification and encryption. Implement UDS (Unified Diagnostic Services) over CAN or DoIP (Diagnostic over IP) for update communication. The reference design includes a complete OTA implementation.

Use dual-bank Flash for safe updates; implement signature verification with ATECC608A; use UDS or DoIP for communication.