# Configure Wireshark SOME/IP dissector for your service
# Edit → Preferences → Protocols → SOME/IP
# Key settings:
# - SOME/IP port range: 30490 (SD) + 30501 (reliable) + 30502 (unreliable)
# - Service/Method mapping: add Service 0x1234, Method 0x0001 name "GetSpeed"
# - After config: filter on "someip" shows decoded messages
# Useful Wireshark filters:
# someip → all SOME/IP traffic
# someip.serviceid == 0x1234 → specific service
# someip.methodid == 0x8001 → specific event
# someip.messagetype == 0 → all REQUESTs
# someip.returncode != 0 → all errors
# someip.sessionid == 5 → trace specific call session
# someipsd → SD traffic only
# someipsd.type == 0x01 → OfferService entries onlyvsomeip Configuration and Wireshark Decode
CANoe .NET: Automated SOME/IP Method Test
/* CANoe CAPL: test SOME/IP method call roundtrip */
variables {
dword test_session_id = 1;
byte test_running = 0;
timer response_timeout;
}
void SendSomeIpRequest(word service_id, word method_id, byte* payload, int len)
{
byte msg[32];
/* Build SOME/IP header */
msg[0] = (service_id >> 8) & 0xFF;
msg[1] = service_id & 0xFF;
msg[2] = (method_id >> 8) & 0xFF;
msg[3] = method_id & 0xFF;
msg[4] = 0; msg[5] = 0; msg[6] = 0; msg[7] = len + 8; /* Length */
msg[8] = 0x00; msg[9] = 0x01; /* Client ID */
msg[10] = (test_session_id >> 8); msg[11] = test_session_id & 0xFF;
msg[12] = 0x01; /* Protocol Version */
msg[13] = 0x01; /* Interface Version */
msg[14] = 0x00; /* REQUEST */
msg[15] = 0x00; /* E_OK */
memcpy(msg + 16, payload, len);
EthSend(msg, 16 + len, "192.168.1.100", 30501); /* TCP send */
setTimer(response_timeout, 100); /* 100 ms timeout */
test_running = 1;
}
on timer response_timeout {
if (test_running) {
write("FAIL: No SOME/IP response within 100ms for session %d", test_session_id);
test_running = 0;
}
}
on EthReceive * {
if (test_running && this.byte(14) == 0x80) { /* RESPONSE */
word recv_session = (this.byte(10) << 8) | this.byte(11);
if (recv_session == test_session_id && this.byte(15) == 0x00) {
write("PASS: Session %d — Return Code E_OK", test_session_id);
}
test_running = 0;
cancelTimer(response_timeout);
}
}AUTOSAR Adaptive Proxy Generation
| Generation Step | Tool | Output |
|---|---|---|
| Define ServiceInterface in ARXML | DaVinci Developer / EB tresos | ServiceInterface with Methods, Events, Fields |
| Generate C++ proxy/skeleton | arxml2cpp (AUTOSAR toolchain) | SpeedServiceProxy.h, SpeedServiceSkeleton.h |
| Generate Service Instance Manifest | arxml2json | speed_service_manifest.json (vsomeip config) |
| Compile and link | arm-linux-gnueabihf-g++ | Executable linked against libvsomeip3.so, libara_com.so |
| Deploy | SSH to target QNX/Linux ECU | Run ./speed_service_server; verify SD OfferService in Wireshark |
SOME/IP Debugging Checklist
| Symptom | Cause | Fix |
|---|---|---|
| Wireshark: no SD OfferService | Server not started / vsomeip.json unicast IP mismatch | Check server process running; verify unicast IP matches ECU's actual IP |
| SubscribeEventgroupAck missing | Server ServiceInstance not deployed or wrong service/instance ID | Verify vsomeip.json service/instance IDs match client config |
| NOTIFICATION never arrives | EventGroup ID mismatch between client and server ARXML | Check EventGroup ID in both server skeleton and client proxy ARXML |
| Session ID not incrementing | TCP socket re-establishing each call | Use persistent TCP connection; check socket error handling in application |
| Return Code 0x22 (E_UNKNOWN_METHOD) | Method ID in request does not match server's registered methods | Verify Method ID in ARXML matches vsomeip.json method registration |
Summary
A production-quality SOME/IP implementation requires four verified components: vsomeip.json with correct unicast IP and service/instance IDs, ARXML-generated proxy/skeleton C++ code, Wireshark decode confirming SD and message exchange, and automated CANoe/CAPL tests verifying method roundtrip latency and return code. The debugging checklist covers 95% of SOME/IP integration failures — most trace back to ID mismatches between the client and server configurations.
🔬 Deep Dive — Core Concepts Expanded
This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.
Key principles to reinforce:
- Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
- Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
- Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.
🏭 How This Topic Appears in Production Projects
- Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
- Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
- Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.
⚠️ Common Mistakes and How to Avoid Them
- Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
- Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
- Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
- Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.
📊 Industry Note
Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.