S32K144 MCAL GPT "undefined reference to `LPIT_BASE_ADDR32'"

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

S32K144 MCAL GPT "undefined reference to `LPIT_BASE_ADDR32'"

1,240件の閲覧回数
binZhang01
Contributor III

Use MCAL code generated by EB and run it on the IDE software of S32DS。

In GPT Demo,it is allways show up "undefined reference to `LPIT_BASE_ADDR32".

 

binZhang01_0-1732361536572.pngbinZhang01_1-1732361616260.pngbinZhang01_2-1732361754521.pngbinZhang01_3-1732361882938.png

binZhang01_0-1732363666407.png

 

0 件の賞賛
返信
3 返答(返信)

1,190件の閲覧回数
Julián_AragónM
NXP TechSupport
NXP TechSupport

Hi @binZhang01,

It seems that you are missing the MCL component for the base address definition:

Julin_AragnM_0-1732643906991.png

Please generate the configuration and include into the build the MCL folder: 

Julin_AragnM_1-1732643928707.png

You can see after I add it, the LPIT errors disappear, only the configuration files are missing, which you should generate:

Before:

Julin_AragnM_2-1732643971265.png

After:

Julin_AragnM_3-1732643974727.png

Also, you may find useful this guide to integrate AUTOSAR to S32DS: S32K344 MCAL Integrate with S32DS. It is based on S32K344, but the general procedures apply.

Best regards,
Julián

0 件の賞賛
返信

1,174件の閲覧回数
binZhang01
Contributor III

hi,I already have this document。I found that I have no problem using the S32K144_STD SDK file. In this routine, I am using S32K144_STM. What is the difference between RTM and RTD?

 

binZhang01_1-1732674874677.png

 

 

0 件の賞賛
返信

1,156件の閲覧回数
Julián_AragónM
NXP TechSupport
NXP TechSupport

Hi @binZhang01,

RTM simply refers to the maturity level of the drivers, in this case, ready to market/release to manufacturer. Meaning it is suitable for production use.

As for RTD, the picture below shows it very clear, RTD include SDK(NON-AUTOSAR), MCAL(AUTOSAR) and Enhanced Drivers:

Julin_AragnM_0-1732724483025.png

Best regards,
Julián

0 件の賞賛
返信