Some Question About the MBDT of S32k3 pher SDK

[brat_zhang]

Dear Sir , here I have some S32K3 SDK question need your help and confirm , please help , thanks!

Question1  The MBDT toolbox of NXP, currently does not support DMA, I2C and other functions, will be increased in the future?

Figure 1 Features currently supported by the MBDT

Question2  Currently, the file formats generated by demo program are bin and a2l. Can upgrade files hex, bin, and S19 be supported?

Figure 2 The current file format generated by the MBDT

Question3  As for UDS, watchdog, CCP/XCP, FS26, 33771 functions, we don't see these functional modules in MBDT at present, do we need to write them by ourselves? Are there any development routines to refer to? Or develop your own tutorials for these libraries?

Figure 3. Current MBDT library browser

Question4  MBDT toolkit comes with the demo routine, you can compile, but cannot download to the development board, the message cannot connect to the board. The driver has been installed on the PE official website. Viewing through FreeMASTER, the Device Name is not recognized。

Figure 4 Failure to download to the development board

Figure 5. Computer that can be downloaded to the development board normally

Question5  Reconfigure EB project in demo. EB can be successfully compiled in EB, but when it is loaded into simulink project, EB error will be reported during compilation. At least the following methods have been tested:

• Complete 344 EB project;
• EB in demo contains 344 EB of the same functional module project;
• Using the EB project of demo as a template, modify the EB configuration of 344 on this template；
• Based on the EB project of demo as the template, modify the ADC configuration of 344 on this template, and leave the rest unchanged。

Figure 6 Error in simulink compilation after EB reconfiguration

[georgevictor]

Hi, @brat_zhang,

Thank you for using MBDT for your projects.

I am going to respond to your questions in the order in which they were addressed:

1. The MBDT for S32K3xx generates code based on RTD (Real Time Drivers) MCAL components. The configuration of these components is done using an external configuration tool (S32 Configuration Tool integrated in our toolbox or the EB tresos tool that needs to be downloaded). Our S32K3xx toolbox includes support for the following RTD components:

• LIN
• UART
• ADC
• PWM
• DIO
• MCL
• CAN
• SPI
• GPT

Currently, the MBDT for S32K3xx does not support I2C and DMA, we will take these into consideration for our future planning, however, we cannot commit to a roadmap yet.

Nevertheless, taking into consideration that we include the entire RTD drivers package, you can use a component even though it is not enabled in our toolbox. You need to add and configure it first in the external configuration tool. Now that the configuration of the component is completed, to call its API functions for implementing your application, you could start by using the custom code block provided by Simulink. Please note that you will also need to include the header files for the component to be able to use specific functions. Also, you will need to call the initialization function for the added component. A good example for your use is the s32k3xx_isr_custom_code_ebt, where the ICU component is used with a similar approach.

2. For now, the formats of the executable files generated by our toolbox are elf and bin.
3. The UDS, watchdog, CCP/XCP, FS26, MC33771 modules are not currently included in MBDT for S32K3. Please note that the watchdog functionality is supported by RTD, so a similar approach like the one for I2C and DMA could be adopted for including it in your application. As for UDS, CCP/XCP you could check with the RTD team on how this support could be enabled. Moreover, please note that FS26 is a package of external drivers that can be installed from the following link : https://www.nxp.com/products/power-management/pmics-and-sbcs/safety-sbcs/safety-system-basis-chip-wi.... It is not included inside the MBDT package, so some integration steps must be performed on your side to have these work together.

As for the MC33771, I would mention that the BMS drivers included in our toolbox support the MC33775A and the MC33772C HVBMS. These BMS drivers are Custom Device Drivers implemented  to work together with the RTD drivers on which our S32K3xx toolbox is based.

For more details on compatibilities and supported parts, please check the information in the following threads:

https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/How-do-I-use-MC33771C-with-the-S32K3XX-...

https://community.nxp.com/t5/Model-Based-Design-Toolbox-MBDT/MCAL-of-S32-Configulation-Tool-inside-M...

4. Regarding the download issue, there are a few things that need to be taken into consideration:
   • Most of our examples delivered with the toolbox are configured for the S32K344-Q257 processor, but, as mentioned in the readme file of each example, they can easily be used for multiple hardware parts. Therefore, when you build an application, make sure the Hardware Part is set for your specific processor or/and package.
   • I will need further information about your board. If you are using a custom board with an external or internal debugger, or if you are using an evaluation board provided by NXP, could you share with us the board that you use?

To use the FreeMASTER utilitary, indeed, you need to install the PE-micro drivers to have access to the Serial Port of the board's OpenSDA chip, in case you have an EVB. If you have a custom board, it depends on the chip used for serial communication.

5. As I understand it, you have modified the ADC settings in the configuration tool. If you have successfully modified the EB tresos project without getting any errors, we should check if these updates are causing the compilation error. In order to have a starting point for solving this issue, a screenshot with the error would be helpful.

Unfortunately, I can't see any of your mentioned figures; maybe they need to be uploaded again.

Cheers,

Victor