Rutronik Development Kit 4 Programmable System-on-Chip CY8C4149AZE-S598 "System Basis Chip OBDII Example".
This application is intended to be used as a reference firmware example for the developers who need to quickly start with PSoC4100S Max and System Basis Chip TLE9262-3BQXV33 CANFD OBD-II protocol.
- ModusToolbox® software v3.7
- The latest hardware release RDK4 Rev2.
- GNU Arm® Embedded Compiler v14.2.1 (
GCC_ARM) - Default value ofTOOLCHAIN
Create the project and open it using one of the following:
In Eclipse IDE for ModusToolbox™ software
-
Click the New Application link in the Quick Panel (or, use File > New > ModusToolbox™ Application). This launches the Project Creator tool.
-
Pick a kit supported by the code example from the list shown in the Project Creator - Choose Board Support Package (BSP) dialogue.
When you select a supported kit, the example is reconfigured automatically to work with the kit. To work with a different supported kit later, use the Library Manager to choose the BSP for the supported kit. You can use the Library Manager to select or update the BSP and firmware libraries used in this application. To access the Library Manager, click the link from the Quick Panel.
You can also just start the application creation process again and select a different kit.
If you want to use the application for a kit not listed here, you may need to update the source files. If the kit does not have the required resources, the application may not work.
-
In the Project Creator - Select Application dialogue, choose the example by enabling the checkbox.
-
(Optional) Change the suggested New Application Name.
-
The Application(s) Root Path defaults to the Eclipse workspace which is usually the desired location for the application. If you want to store the application in a different location, you can change the Application(s) Root Path value. Applications that share libraries should be in the same root path.
-
Click Create to complete the application creation process.
For more details, see the Eclipse IDE for ModusToolbox™ software user guide (locally available at {ModusToolbox™ software install directory}/docs_{version}/mt_ide_user_guide.pdf).
The firmware example uses KitProg3 Debug UART for debug output. Some of the most common OBD-II PIDs are presented twice per second: Vehicle speed (0x0D), Engine speed (0x0C), Control module voltage (0x66), Intake air temperature (0x0F), Intake manifold absolute pressure (0x0B), Mass air flow sensor air flow rate (0x10).
The Green and Red USER LEDs indicate whether the device is connected to the CAN network using the standard OBD-II protocol. The result shown below was taken from a real vehicle while driving.
If you have successfully imported the example, the debug configurations are already prepared to use with the KitProg3 or MiniProg4. Open the ModusToolbox perspective and find the Quick Panel. Click the desired debug launch configuration, then wait for programming to complete and debugging to start.
A special mode, called SBC Development Mode, is available for software development or system debugging. The watchdog counter is stopped and does not need to be triggered. This mode can be accessed by setting the TEST [FO3] pin to GND during SBC Init Mode.
The OBD-II cable is not included in the RDK4 development kit; it is required to assemble the kit before the example can be fully tested with a vehicle. The cable part is provided by Rutronik and comes with RDK4's package. It is a cable for the Amphenol ICC Minitek MicroSpace™ header Part No.: 10142344-104KLF. The rest has to be done by the developers. Soldering skills are needed to assemble the OBD-II socket. Please pay attention to the pinouts shown below:
Once the cable is assembled, the RDK4 can be connected and powered from the vehicle's power system.
The evaluation board including the software is for testing purposes only and, because it has limited functions and limited resilience, is not suitable for permanent use under real conditions. If the evaluation board is nevertheless used under real conditions, this is done at one’s responsibility; any liability of Rutronik is insofar excluded.
