Hello @mariuslucianand
I went through the topic How to use C code in our Tool box
I have Successfully built the code which you have mentioned above and Establish communication using C Code rather than using the Tool box. But, if I import the xml file of the Project to design Studio I encounter various Errors which are unable to include the Files present in bcc.
Secondly, I am trying to use Custom Code in order to transmit string value as a parameter using coder.ref but it pops out with an error.
Is there any possible way to Solve the above mentioned issues.
Regards
Nisha
Hello @nishalemos,
You have to import the files from the bcc folder as well in the S32DS project.
Right click on the project name, select Import. Look after General -> File System and select the bcc folder that contains the bcc_*.h/.c files
Hope this helps,
Marius
Hello @nishalemos,
To read the fault registers, you can use the "Fault Get Status Block" directly from our toolbox. This will return the 11 registers described below. This block uses the "BCC_Fault_GetStatus" function.
If you are interested in a register value that is not returned by this block, then you can read directly that register by using the "Reg Read Block", feeding it with the address mentioned by the Reference Manual. This block uses the "BCC_Reg_Read" C function to do the job.
Hope this helps,
Marius
Hello @rathi_tg.,
It looks like we are using different compiler versions and the lib that the S32DS complains about is from the GCC version 6.3 and not 4.9 the one that you have.
Now, the toolbox comes directly with the compiler, so the way in which you select which one to be used is by setting the system path variable that points to the compiler.
By default, the Model-Based Design Toolbox comes directly with the compiler and adds the path in the Matlab if the variable is not found declared in the Windows path variable. So in order to check which variable you have set, please type the following command in the Matlab environment.
My result points to the compiler from the toolbox.
Now, if your result is the following,
| C:\NXP\S32DS_ARM_v2.2\S32DS\build_tools\gcc_v4.9\gcc-arm-none-eabi-4_9\ |
you have two options:
1. Either go to the Windows' System properties, Environment variables and update the GCC_S32K_TOOL variable value to the:
| C:\NXP\S32DS_ARM_v2.2\S32DS\build_tools\gcc_v6.3\gcc-6.3-arm32-eabi |
2. Either go to the Windows' System properties, Environment variables and delete the GCC_S32K_TOOL variable. And Matlab will use the compiler provided with our toolbox which is the same as the one from the S32DS_ARM_v2.2.
In both cases, you have to restart Matlab after changing the already defined GCC_S32K_TOOL variable path.
Hope this helps,
Marius
Hello @mariuslucianand
I have Followed the above Steps I get build option but it generates few errors.
What are these specific to and how i could solve them.
Thanks and Regards
Gopal Rathi
