Overview S32X-MB is a mother board of S32Z/E and S32K396, which is for extending the peripheral interfaces with multiple PHYs and pins. Users will face problems when using TJA1103 PHY on S32X-MB. This article is to notice the issues to users.                           Two hardware issues of TJA1103 PHY on MB 1. Pin strapping, TJA1103 can’t be configured as master mode when autonomous mode is enabled. 2. TJA1103 data unstable transmission, the clock signal has length 30 cm on the board but in the specification the maximum length of this signal is maximally 15 cm. Details of the two issues 1. Pin strapping: According to TJA1103 Datasheet, pin strapping should work as below. Actually, it is not exactly. Exceptions are, when CONFIG5 and CONFIG6 are set as both "H", TJA1103 works in master mode when not connecting slave board while TJA1103 works in slave mode when connecting slave board. If CONFIG5 and CONFIG6 are set both "O", TJA1103 works in slave mode regardless of whether slave board is connected or not.   2. TJA1103 data unstable transmission: There will be packet loss when transmit/receive packets with 100% line rate. There is possibility that packets drop with line rate less than 100%. workaround Current TJA1103 on the S32X-MB is a chip of old version with lower driving capability compared with new one. Pin strapping with “O” required CONFIG5 and CONFIG6 detecting voltage transition in a very short time window. Current TJA1103 on S32X-MB failed to drive signal at required voltage level in such a short time. Mode setting failure can be solved by 1. Replacing TJA1103 from S138X to S4070 version 2. Resetting PHY after power on Both steps need to be done. Picture below shows the original TJA1103 chip type(left) and a new version(right) that should be replaced.   J38-2 is the reset pin of TJA1103. Connect it with an extended pin which can trace to a GPIO pin of daughter board. Provide J38-2 with a low pulse to reset TJA1103. Other tips for usage - Before powering on, press the daughter board hard to make sure the connecters are tightly connected. - The MDIO and MDC pins are not traced from daughter board to S32X-MB. External transceiver can be used to monitor the master/slave mode of TJA1103. Conclusion Do not suggest customer using TJA1103 PHY on MB to test or develop project. Use the Realtek PHY on daughter board instead. If two switch ports are required, use S32E288-975 or S32Z280-400.

On this page, you will find the introduction to the TMU false measurement issue and a workaround example code. Additionally, a sample project is provided as a reference, to demonstrate one way to implement the workaround. Along with the sample project, an introduction to how the false measurement is detected and how to integrate it into the existing project will also be included. 1. TMU false measurement issue This issue will be included in the errata later release, errata numbers are ERR052243 and ERR052223. Below is the summary of this issue: 1.1 Description At random points in time, a false temperature measurement may be observed across the temperature range specified in the device datasheet. 1.2 Workaround Implement a software-based filter to detect if an invalid measurement is recorded by the TMU and respond accordingly.  2. Example description This example aims to provide a buildable project with the TMU workaround reference code on the S32Z2/E2 platform. 2.1 Dependency EB Tresos Studio, if the auto-generated code needs to be modified. RTD version: SW32ZE_RTD_R21-11_1.0.0_P09 Hardware: S32Z27x DC2 2.2 Guide Refer to the readme.txt file included in the project for how to build and run this example.  3. False measurement detecting flow This section is to show the false measurement detecting flow used in the example project. The diagram below shows the detecting flow for high temperature and fast temperature rising cases. The main idea about how to detect it can be described as follows: Time t2: Detect the high temperature and fast temperature rising and enter the TMU interrupt. Since there is a temperature jump at this time, it might be a false measurement and needs to be further verified in subsequent sample points. Time t3: Detect the fast temperature falling and enter the TMU interrupt again. In the TMU interrupt handler, needs to compare the actual difference (D1) and acceptable difference (D2). If D1 < D2, that indicates the temperature was measured incorrectly at time t2. As for low temperature and fast falling cases, the detecting flow is similar. 4. How to integrate The following steps demonstrate how to integrate this workaround code into an existing project, an EB-based project is used as an example to show the integration process.  1. Configure TMU a. Set the Average Low Pass Filter (ALPF) as 0 to disable the low pass filter for average temperature. b. Choose Temperature Monitoring Interval (TMI) as the continuous monitoring mode. 2. Configure timeout timer a. Enable a timer channel in the GPT module, any of the STM, PIT or Etimer can be used. RTU_STM timer is used in this example. b. Set the timer to one-shot mode. c. Set the Tmu_TimerIrqHandler as the notification of the timer. d. Calculate the channel frequency of the timer being used. The frequency is 1MHz in the example project, which will be used later to calculate the timeout value. 3. Build the workaround code into your project, as a less dependent software package, it is easy to compile. The structure of the workaround software is as below: 4. Install the TMU interrupt handler. 5. Change these parameters according to your own project setup.  6. Implement the related reactions for TMU real fault in Tmu_UserIrqNotifier Note: There are several ways to filter out the false temperature measured by TMU, the project shown here only serves as an example reference. If HSE is used, need to disable the TMU alert in HSE firmware, for more details, please look into the HSE-H&M Firmware Reference Manual.

S32E2 Propulsion Domain Controller Solution 0.8.0 has been released in FlexNet. This solution demonstrates the integration abilities of S32E2 by simultaneously holding System Manager, PIL, Safety Manager, Aws IoT, BMS, AE motor control, GTM motor control, CAN-CAN/Eth gateway, Bootloader, FOTA, and EL2M applications. Owing to powerful Cortex-R52 cores, abundant flexible peripherals, and well-designed isolation/virtualization, various applications can function well without interference. This solution offers customers technical details in the multi-core system, peripheral usage, and useful libraries. The user guide elaborates on bringing up all applications from scratch.    Key features: Compatible with RTD 0.9.0 P01 (with patch files made by the Apps team). EB Tresos MCAL projects S32 DS IP layer projects Compatible with S32E2 DC4 hardware RevB and GreenBox3 Rev B Multicore system implementation, including bringing up SMU/RTU/FlexLLCE cores, R52 cores on/off in run time, inter-core communication, and isolation. Propulsion domain control applications System manager (SMU): System-level configuration, core management. Bootloader (SMU): Load multiple images at full speed and boot cores. Support FOTA too. PIL with MBDT (R0_C0): Simulink & MBDT (Ported from PILPlayback code. Appreciate the help from Austin Apps team) Safety manager (R0_C1): Monitor critical BMS and AE motor application data. React as per safety requirements. Aws IoT (R1_C0): Publish vehicle data to the MQTT broker server via AWS IoT services. Stacks used: FreeRTOS, LWIP, mbedTLS, AWS IoT. FOTA (R1_C0): Work with the bootloader. BMS (R1_C1): Monitor battery parameters Motor control by AE die (R1_C2): Use motor control peripherals in the AE die. Motor control by GTM (R1_C3): Use motor control peripherals in the S250 die. CAN-Eth gateway (FlexLLCE): PDU router between CAN and Ethernet ports(Ported from PDU Tunnel on Zone Control POC platform. Appreciate the help from Zonal Control team) EL2M (RTU1): Manage GIC and MPU in Exception Level 2 Bootloader and FOTA to update images for up to 8 cores. Safety and security software/hardware enablement Leveraging the latest libraries (LWIP, FreeRTOS, AMMCLIB). Coworking with eco-system partners (Elektrobit, Amazon, Mathworks) Release packages: Doc: User guide Sw:  pdc_ds pdc_ebt pdc sw_pkg Hardware dependencies: This solution is verified on S32E2 DC4 RevB and GreenBox3 RevB hardware. Please refer to the User Guide for more hardware versions. Note: This reference design is with demo software quality, users are expected to be responsible for the quality when integrating it into a real application.