functional group issue

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

functional group issue

ソリューションへジャンプ
1,064件の閲覧回数
Ayaz
Contributor IV

I am facing an issue with port configurations. I have grouped my signals using the pin tool, and the names for the pin tools should be in the format (PortContainer + pin functional group). The issue is that (VS_0) has only one pin, while (VS_1) has two pins. When I add the second pin to (VS_1), a pin is also added to (VS_0). It seems like they must have the same number of pins. How can I fix this?

Skærmbillede 2024-10-28 104556.png

2: I can only select one group to be called by default, and it is routed to global settings. Can you explain what effect this has?Skærmbillede 2024-10-28 105150.png

Skærmbillede 2024-10-28 105855.png

I have attached my project for you to review.

S32K344

RTD 4.0

0 件の賞賛
返信
1 解決策
1,044件の閲覧回数
Julián_AragónM
NXP TechSupport
NXP TechSupport

Hi @Ayaz,

1. For pin configuration, you can simply create various functional groups from the Pins tab, and the configuration will be generated:

Julin_AragnM_0-1730152368662.png

Julin_AragnM_0-1730152202037.png

I believe you cannot have more than one PortContainerSet, since it is Port AUTOSAR specification, please refer to this community post: PORT configuration in MCAL - NXP Community.

I've attached a project where the three different RGB pins were configured in different groups, and blink depending on the configured group by calling Siul2_Port_Ip_Init() with the respective structure.

2. This limitation is by design. Only one functional group can contain the default initialization code, the others are intended as alternatives or to be called additionally later. 

For example also in the clocks tool, you need to have one default init configuration and the others are alternatives.

If you'd like to have the initialization split in multiple functions or controlled by some login in your code, you can omit calling default initialization completely and just call the functions that  you need in your application module directly. 

Wth this approach, you might also want to un-set the [B] icon  (boot init) checking in the Problems view:

Julin_AragnM_1-1730152462550.png

If the [B] icon is unset, the cross-dependencies from other tools will be checked to be fulfilled by any functional groups, not just by "default init" one.

Best regards,
Julián

元の投稿で解決策を見る

0 件の賞賛
返信
1 返信
1,045件の閲覧回数
Julián_AragónM
NXP TechSupport
NXP TechSupport

Hi @Ayaz,

1. For pin configuration, you can simply create various functional groups from the Pins tab, and the configuration will be generated:

Julin_AragnM_0-1730152368662.png

Julin_AragnM_0-1730152202037.png

I believe you cannot have more than one PortContainerSet, since it is Port AUTOSAR specification, please refer to this community post: PORT configuration in MCAL - NXP Community.

I've attached a project where the three different RGB pins were configured in different groups, and blink depending on the configured group by calling Siul2_Port_Ip_Init() with the respective structure.

2. This limitation is by design. Only one functional group can contain the default initialization code, the others are intended as alternatives or to be called additionally later. 

For example also in the clocks tool, you need to have one default init configuration and the others are alternatives.

If you'd like to have the initialization split in multiple functions or controlled by some login in your code, you can omit calling default initialization completely and just call the functions that  you need in your application module directly. 

Wth this approach, you might also want to un-set the [B] icon  (boot init) checking in the Problems view:

Julin_AragnM_1-1730152462550.png

If the [B] icon is unset, the cross-dependencies from other tools will be checked to be fulfilled by any functional groups, not just by "default init" one.

Best regards,
Julián

0 件の賞賛
返信