Hi @nikolayyakovenk ,
Can you check if the mbdt_tja1153.c and mbdt_tja1153.h files exist in the src folder of the imported project?
If not, can you please try and copy them inside this folder from the path illustrated in the ToolboxSrc.png image I attached to the previous post? If not copied here, the S32DS won't be able to locate them, hence the error you encounter. Please try this out and let me know if it works.
Irina
Hi @nikolayyakovenk ,
To address the questions/issues you have encountered, I have structured my answer as it follows:
1. MBDT 1.0.0 and differences between Platform SDK versions
The RTD, used by MBDT for Simulink models deployment, is delivered with the toolbox, and all the files can be found inside the toolbox path/S32K3_RTD folder. Therefore, the Simulink ecosystem uses those files and does not depend on the RTD version installed in S32DS, thus making the deployment from Simulink work as expected. However, if you import a MBDT 1.0.0 project (which uses RTD version 2021_03) into S32DS, and from there you want to add components, integrate the application with other existing code, it is indeed recommended to have the same RTD version installed in S32DS (there are some API differences between the RTD 2021_03 and the 2021_10 versions).
2. MBDT 1.1.0
Now, since you have updated the MBDT version, the 1.1.0 supports both S32K312 and S32K344 hardware parts. Therefore, inside the toolbox you can find example applications for each of the components MBDT provides, for both processors, in the S32K3_Examples folder (I have attached the S32K3Examples.png with the exact path and the models existing there for the Gpt component, for example. Since these examples also use FreeMaster for real time application debugging, I used one of them for testing the issue you encountered).
Starting from this, I would suggest the following steps for trying to solve the issue you are facing:
1. From this examples folder, open and build directly a model designed for S32K344, in accordance to the processor you have.
- If the build fails, could you please provide more details related to the cause of failure? The Simulink Diagnostics Viewer window should contain all the information of the build process, including the cause of failure, so in case this happens, could you please attach that log to this thread? (If not opened automatically, the Diagnostic Viewer can be opened from the View diagnostics button in the bottom part of the model, please see attached DiagnosticViewer.png).
2. If the build is successful (executable files are created), open the Model Settings and select the Export option for the model.
- If the Export process still throws errors, could you please attach those in this thread?
3. If the process of Export has been completed successfully, the modelNameConfig folder should be ready to be imported in S32DS.
4. For importing the project into S32DS, after selecting File -> Import -> Existing Projects into Workspace option, make sure you use the modelNameConfig folder from the location where the project was exported (please see attached ImportProject1.png and ImportProject2.png).
- MBDT provides two options at Export: 'Simulink model folder' (in this case, the modelNameConfig folder next to the Simulink model should be imported) and 'To local file system' (the modelNameConfig folder from the location you chose for storing it should be imported).
5. And then, try and build the project from S32DS.
6. For flashing and debugging the project, you can create a new S32DS Debug Configuration, or start from an existing one, and use the .elf file generated by the S32DS build process inside the Debug_FLASH folder. Alternatively, you could use the default debug configuration MBDT provides (already contains the .elf file path), that can be accessed as illustrated in the DebugProject.png.
In the Example.png file I have attached the results provided by the Simulink build -> export -> S32DS import -> S32DS build process of one of the Gpt applications MBDT delivers, which uses Freemaster. The Freemaster files (both headers and sources) are present in the src folder of the modelNameConfig, and the S32DS build was successful. The Freemaster headers and sources are added to the src folder of the modelNameConfig during the Simulink build process, so they should also be present inside the Matlab folder. If the build of the Simulink model fails, the export process won't produce the desired behavior (maybe some files were not generated during the build process - this could be the cause for the missing Freemaster files). For testing this example, I have used MBDT 1.1.0 (using the integrated RTD 2021_10) and S32DS v3.4 Service Pack 2, where I have SW32K3_RTD_4.4_1.0.0_DS_updatesite_D2110 installed.
Could you please try following the steps from above and let me know if problems still pop, and in case they do, at which step?
Moreover, I would like to provide some additional information you might find useful:
In case you would like to build and export a MBDT Can model for S32K344, an additional action must be taken before moving to step 4 from the previous description, for obtaining the result of a successful S32DS build. Hence, please copy the mbd_tja1153.c and mbd_tja1153.h from the toolbox src folder (please see attached ToolboxSrc.png) to the modelNameConfig/src folder (please see attached modelNameConfigSrc.png). These files contain the initialization of the on board Can transceiver, and without having these files inside the modelNameConfig folder, the S32DS build process won't be able to locate them. We plan to automate this process in the next release.
Also, in case you would like to migrate one of the S32K312 examples to S32K344, after changing the Hardware Part in the Model Settings, make also sure that all the Simulink blocks in the model are updated with the new parameters (since the hardware differs, the options set for S32K312 - e.g. Can Controllers, Gpt channels, Adc hardware units, may not be valid for an application targeting S32K344).
Hope this helps,
Irina
Hi @yu123 ,
Based on the error message you have attached I would propose to follow the next steps, based on your current MBDT setup.
1. If you have EB Tresos installed and you are using it for configuring and initializing the hardware for your application, please check that EB Tresos has a valid license.
2. If this is not the case (you do not have EBT installed), I would recommend you to navigate to the place where this model is stored and remove all the generated folders. I have attached a screenshot of the model's folder on my end. Could you please try opening the model again under this setup?
If this works, please notice that after opening the model, two folders appear next to it. The first one will be modelName_TresosProject which contains the default configuration MBDT provides for hardware initializing all the components it provides support for. The MBDT blocks read the settings of the configuration project associated to the model and display in their masks the available options for implementing the logic of your design. The MBDT for S32K3 integrates the usage of configuration tools (S32 Config Tools and EB Tresos), specialized on setting and initializing the hardware used by an application.
In addition to that, a modelName_Config folder will also be brought next to the model. This one contains the drivers, linker files, basically all the necessary hardware aware sources for deploying Simulink applications on the MCU. In addition to these, it will also include the generate folder, containing the generated code corresponding to the TresosProject configuration.
Since this model will use the default configuration MBDT provides (and its generated code), you do not need to have EB Tresos installed for building this model. All the necessary sources can be found inside the two folders I was mentioning.
After these folders appear, I would recommend you to not remove the modelName_Config folder. If this happens, when closing the model and opening it again, the workflow will try regenerating the EB Tresos project configuration code, and since EB Tresos is not installed, this action will result in the error you have encountered.
I guess one of these things could have happened in your environment, triggering the attached error. However, if these are not the cases, please provide more details on your current setup.
Hope this helps,
Irina
Hi @nikolayyakovenk ,
Can you check if the mbdt_tja1153.c and mbdt_tja1153.h files exist in the src folder of the imported project?
If not, can you please try and copy them inside this folder from the path illustrated in the ToolboxSrc.png image I attached to the previous post? If not copied here, the S32DS won't be able to locate them, hence the error you encounter. Please try this out and let me know if it works.
Irina
hello
I succeeded in this way, but the blue light was always on , so I could not receive CAN communication. The following MBD was used.
