MBDT with non-AUTOSAR drivers

[AsierMaser]

Hi guys,

I was wondering if it is possible to use MBDT with the regular drivers on the S32 config tool. I have always used non-AUTOSAR drivers and all the code and config for our custom board is done this way.

Now we are using Simulink and when loading the custom .mex file the Simulink blocks do not seem to recognise the drivers. I loaded some MCAL peripherals and then the blocks showed several options, so I assume MBDT only works with MCAL?

If so, is there any tool to migrate from standard drivers to MCAL? I am doing it manually, but the S32 config tool is extremely slow (maybe my PC problem, would be great to clarify) and it could take days to migrate.

Thanks,

BR

[AsierMaser]

Hi @Irina_Costachescu

I have already configured the Tresos and generated a simple program to test de config. The problem is I am unable to load the code as I am getting some errors at Simulink. I am attaching the report, it seems like it is failing to access several include files even though they are located where they have to be.

Another thing I noticed is that Timers option shows 0 Hz on both solver and profiler timers. First I didn't have a Gpt configured on Tresos; now I do but it still shows 0 Hz. This is not related to the previous problem, but I am curious about it.

BR

[AsierMaser]

Hi @Irina_Costachescu

Thanks for your reply. Unfortunately I was afraid that it wouldn't be possible to use non-MCAL drivers. So, I started modifying the default config as you suggested. I also switched to EB Tresos since I found it to be much faster and more fluid than S32 configuration tool.

We are using two different microcontrollers for two different projects, S32K312 and S32K344 (both 172MQFP), but the one I am currently working on is the S32K312.

Please let me know if you need any other info.

BR

[Irina_Costachescu · Accepted solution]

Hello @AsierMaser 

MBDT is built on top of the RTD MCAL, so indeed the default configuration project we provide for the peripherals and processors we enable, as well as the APIs exposed inside our Simulink blocks, are based on this layer of the drivers package.

Unfortunately, I am not aware of any straightforward manner in which you could port the low level drivers configurations to MCAL components.

However, my suggestion would be to start from the default configuration project that MBDT provides for the processor your custom board is using, and try reconfiguring those settings to match your design particularities. Could you please share with us what hardware platform are you using, so that we could point you to the necessary documentation? We are describing the process of building specific configuration templates for custom hardware designs inside our toolboxes Release Notes documents.

Thank you,
Irina