Conflicts encountered during configuring CAN in tresos

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 

Conflicts encountered during configuring CAN in tresos

342 次查看
krupan
Contributor II

We are working on a new implementation using S32K118 coupled with an existing Tresos license (EB Tresos 24.0.1) and MCAL(S32K1XX_MCAL_4.3_RTM_1.0.4) but have encountered some difficulties :

a.) while trying to import a DBC file into the configuration. we don’t get to see the option to import DBC file here:

In addition to understanding the proper procedure for DBC file import—such as compatibility requirements, preprocessing steps, or known limitations within Tresos—we also have concerns regarding licensing constraints. Could there be a possibility that we are missing a required license or that certain features are restricted unless specific licensing conditions are met?

krupan_0-1750165543809.png

b.) Unable to configure CAN CPU Reference Clock

The peripheral clock selection for FLEXCAN0 appears to be EXT_CLK_OR_CLK_OFF, but when enabled this in MCU module, the reference node does not appear here to configure the CAN CPU reference clock.

Is this expected behavior, or is there a specific configuration or workaround to make the reference node available? Because the generation fails with errors when this is not configured.

krupan_1-1750165722562.png

 

0 项奖励
回复
1 回复

314 次查看
Julián_AragónM
NXP TechSupport
NXP TechSupport

Hi @krupan,

a)

You are correct. The evaluation license for Tresos that NXP provides does not contain the license for DBC import. If you need this feature, you will need to contact EB to purchase.

b)

The reference to the CPU clock configuration is set in the MCU driver configuration. MCU plugin needs to be added and then give the reference to it:

Julin_AragnM_1-1750184323565.png
Julin_AragnM_0-1750184310438.png

Best regards,
Julián

0 项奖励
回复