RADIO / GW / Programming guide

INFOTAINMENT & GATEWAY MODULES

Routes network traffic and controls audio, displays, telematics, cameras and connected features.

MODULE GUIDE08/38

01Software package update

02Replacement-module provisioning

03Vehicle-option coding

04Component protection / account activation

PROGRAMMING DECISION GATES

Identify, protect and recover the operation

Do not treat every service event as a simple flash. Determine what must be transferred, authorized, calibrated and verified before writing software.

01 / IDENTIFY

Define the operation

  • Separate a software update from replacement setup, coding, security pairing and calibration.
  • Record the current software, part number, VIN and configuration before changing anything.
02 / COMPATIBILITY

Pass the compatibility gate

  • Confirm part number, hardware level, supersession, region, options and new-versus-used restrictions.
  • Verify the OEM tool, subscription, interface and required security credentials.
03 / PRESERVE

Protect data and sequence

  • Save the pre-scan, identification, as-built data and learned values the procedure permits you to restore.
  • Follow the OEM module order, ignition states and CAN FD or DoIP transport requirements exactly.
04 / RECOVER

Respond to interruption

  • Do not cycle the ignition or disconnect power unless the OEM recovery prompt directs it.
  • Preserve the error, verify support voltage and communication, then use the approved recovery or bootloader routine.

NETWORK & PROGRAMMING ACCESS

Likely architecture paths

These are common implementations, not a vehicle-specific pinout. Confirm the exact topology, protocol and gateway route in current OEM service information before connecting or programming.

VEHICLE COMMUNICATION

Possible networks

Automotive Ethernet, CAN/CAN FD and MOST are common; LIN may serve local controls. USB, LVDS, APIX/GMSL or similar display links are point-to-point media interfaces and should not be diagnosed like CAN.

DIAGNOSTIC TRANSPORT

Programming access

Large packages commonly use DoIP/Ethernet, USB or OEM media; configuration may still travel over CAN. Gateways can require secure diagnostic authorization and certificate provisioning.

PROGRAMMING TOPOLOGY

Critical online dependencies

Display, amplifier, telematics, cameras, cluster, USB hubs and gateway routing tables may all be package dependencies. Preserve customer settings and feature entitlements where permitted.

BEFORE CONNECTING

✓ All network branches and termination checked✓ Correct region, option and hardware identifiers✓ Reliable wired network connection for online programming✓ Support supply sized for extended sessions✓ OEM account and security authorization where required

COMPLETE TEST SEQUENCE

  1. Save the topology scan, module IDs, option coding and customer settings.
  2. Confirm the problem is not a display, amplifier, antenna, Ethernet or MOST link fault.
  3. Connect stable vehicle and computer power; prevent sleep and automatic restarts.
  4. Install software packages in the OEM-specified order, including dependent modules.
  5. Apply coding, component protection and feature provisioning through approved services.
  6. Verify camera, audio, navigation, USB, Bluetooth and gateway routing functions.
  7. Rescan, confirm every expected module is present and document subscription-dependent features.

POST-PROGRAMMING VERIFICATION

  • No gateway topology or coding mismatches
  • Audio and displays recover after sleep/wake
  • Ethernet/MOST/CAN dependent modules communicate
  • Customer data and connected-service status are handled appropriately
VEHICLE-SPECIFIC DATA WINS

Software, subscriptions, security access, voltage targets and ignition sequences vary by manufacturer and model.

NEXT MODULE / BECM / HPCMBattery & Hybrid Control Modules→