the usage of the S32DS_config tools issue_FC

[Fidel]

Dears,

       my questions as below:

       1. the pin config tools is conflict with the perapheral tools? that is red label 1 and red label2, must choose one from between of them? and the red label 4 part is related with label 2 ,and red label 3 with label 2, that is right? and that why the board folder and generate folder in label 4 part are exclued from the project? if we want to reuse the board and generate folder and exclude the label 3 part, what should I do?

2 . no matter what manner we choose to config pins, the clock configuration are always done througn  the ''clocks'' which is between the ''pins'' and peritherals,  that is right? even we use MCAL and low level driver.

[mikedoidge]

Hello,

The SDK and the S32 Configuration Tools support both AUTOSAR and non-AUTOSAR configuration code generation. The Pins Tool supports ONLY NON-AUTOSAR configuration code generation.

If you are required to use the MCAL drivers, these are AUTOSAR drivers. In this case, you should not use the Pins Tool. I would recommend that you disable the Pins Tool for this project.

From the Peripherals perspective, select the Overview tab and turn the switch off for the Pins Tool:

Best Regards,

Mike

[Fidel]

and another question here then, if there is any information in the project indicates the project is created or configured for a autosar or non-autosar project? or I can only identify that by to check the peripherals configure part?

[mikedoidge]

Hi Fidel,

I think you are probably correct. The best method is likely to look to the Mode setting in the configuration panel for the driver within the Peripherals Tool:

I've also noticed that in some of the generated code, there are some clues, but it seems it is not as consistent as the Mode setting in the tool.

Best Regards,

Mike

[Fidel]

Hi Mike,

      got it , it is clear now , and then what should I do if I want to change the autosar project back to non-autosar project? when I deleted all the MCAL drivers  、low level drivers and reuse the pin tool, there always some problems. that means I must to creat a new non-autosar project? thanks a lot~

[mikedoidge]

Hello Fidel,

In theory, it should be possible to replace the AUTOSAR drivers with non-AUTOSAR drivers. However, if you are having some issues with this, then I think these tools may not be setup for easy transition. I'm certain this workflow is not a part of the validation testing. It is not expected to be a normal workflow. The type of drivers required is known at the start of a project so a transition should really be a very rare occurrence.

Best Regards,

Mike

[Fidel · Accepted solution]

Yes, thank you for your reply, it is all clear now~