DeliveryTestReport_CBD1400346
The content of this delivery and the tested configuration is described in DeliveryDescription_CBD1400346.html
Delivery Information
License Information
| License Information: | Nexteer Automotive Corporation Package: GMLAN 3.1 - CANbedded License for GM; MultiChannel Micro: R7F701311 Compiler: GHS 2015.1.7 |
|---|---|
| License Number: | CBD1400346 |
| OEM: | Gm |
| SLP: | GMLAN 3.1 |
| Controller: | Rh850 |
| CanCell: | Rscan |
| Compiler: | GreenHills |
Delivery Information
| Delivery Number: | 01 |
|---|---|
| SIP Version: | 01.01.35 |
| Delivery ID: | 01.01.35.01.40.03.46.01.00.00 |
| Release Type: | Serial production release (complete functionality, fully tested , full process, incl. serial production release) |
| Delivery Type: | Initial delivery (based on explicit purchase order) |
| Delivery Reason: | 5015512 |
Test Verdict
| Test Verdict | Passed |
| Test Report Date | 2016-05-06 |
Test Activities
According to Vector’s embedded software development and delivery process, the test activities are assigned to the development phases of the software. The most important development phases for a delivery like this are the Component Test and the Delivery Test.
Component Tests
Each component listed in the section "Detailed Version Information" within the delivery description has been tested during the component development phase before component release independently of this specific delivery. The test activities on component level include:
- Code inspection and inspection of all work products, e.g. technical references
- Static and dynamic tests according to the component-specific test specification and test plan
- MISRA-C:2004 analysis and justification of deviations
- Code coverage analysis (target: high code coverage of dynamic tests, additional inspection of uncovered code areas)
Delivery Tests
Testing the ordered program ("SLP") on the real hardware with the target compiler and the requested configuration is performed for each delivery ("SIP") in order to detect any delivery specific issues. The test activities on delivery level include:
- Compile and link test on the real hardware with customer-specific compiler-, assembler- and linker-options (as specified in the questionnaire)
- Dynamic tests according to the program related delivery test suite
- Dynamic tests according to the ordered configuration or use-case (depending on the questionnaire or SLP defaults)
- Optional: manual tests to cover special use-cases
If there are no delivery specific tests documented below this is a redelivery without test relevant changes. The delivery tests from the former delivery are still valid.
The results of the delivery specific tests are documented on a summary level within this report. The result of the component specific test is not documented here as it is a prerequisite that the component has passed its release test before being delivered to customers. Vector does not distribute all the detailed test results to you. If you are interested in a review of the detailed delivery test results and those of the component specific tests, please contact Vector for more information.
Delivery Tests Results
Use Case Standard
| Diag: Basic Tests | Passed |
| Diag: Sleep related Test | Passed |
| Diag: Partial Offline | Passed |
| Diag: Reinitialization | Passed |
| Diag: Periodic Messages | Passed |
| Diag: Periodic Messages | Passed |
| Diag: Timing | Passed |
| Diag: DynDef Messages | Passed |
| Diag: TP-Error | Passed |
| Bus Load Test with heavy bus load | Passed |
| Remote Frames Test Remote Frames | Passed |
| Cancel Transmit Test Cancel Transmit | Passed |
| Lock CAN interrupts Test functionality of CanCanInterruptDisable and CanCanInterruptRestore. | Passed |
| General tests These tests validate generic aspects of the GGDA | Passed |
| Modes required for flash programming These tests check basic diagnostic modes | Passed |
| Modes required for fault memory These tests checks the fault memory diagnostic modes | Passed |
| GmCal Tests Tests GmCal: set different configurations, reset, check if messages are send according to configuration | Passed |
| Application Verify that optional application APIs work as expected. | Passed |
| Multiple Identity Module Verify that the ECU switches message sets properly when configured as a multiple identity module. | Passed |
| Bus Off Verify that the ECU enters and exits busoff at the appropriate times, the ECU does not transmit during busoff, and that all related APIs work as expected. | Passed |
| State Verify that the ECU enters and exits special diagnostic modes properly and that all related APIs work as expected. | Passed |
| Bus Off Verify that the ECU enters and exits busoff at the appropriate times, the ECU does not transmit during busoff, and that all related APIs work as expected. | Passed |
| Sleep Wakeup Verify that the ECU enters and exits sleep mode at the appropriate times and that all related APIs work as expected. | Passed |
| State Verify that the ECU enters and exits special diagnostic modes properly and that all related APIs work as expected. | Passed |
| VN Activation Verify that the ECU activates and deactivates VNs at the appropriate times, the appropriate messages are sent and received, and that all related APIs work as expected. | Passed |
| TP Transmission Tests Test TP data transmission and TP data reception with variable data length | Passed |
| VStdMemCopy Tests VStdMemCopy Tests | Passed |
| VStdMemSet Tests VStdMemSet Tests | Passed |
| VStdMemClr Tests VStdMemClr Tests | Passed |
| Download/Upload Data Test Upload from RAM and ROM and Download to RAM | Passed |
| Individual Polling_Tx Test Individual Polling | Passed |
| Remote Frames Test Remote Frames | Passed |
| Acceptance Filter Test Acceptance Filter | Passed |
| Extended Status Test Extended Status | Passed |
| Cancel Transmit Test Cancel Transmit | Passed |
| Application Messages Test Rx / Tx ApplMsg, RDS macros, Pretransmit / Precopy | Passed |
| Individual Polling_Rx Test Individual Polling | Passed |