AMMCLIB for S32K3xx (RTD dependent) fails to update S32DS 3.5

[rdrosescu]

Hi,

 I'm trying to update AMMCLIB for S32K3xx (RTD dependent) 1.1.29 in S32 Design Studio for S32 Platform 3.5 as recommended in S32DS Extensions and Updates. I receve the following error message: 

Could not be installed. Reason: Operation details Software being installed: com.nxp.AMMCLIB_S32K3xx.S32K3.root.1.1.29.feature.feature.group 1.1.29.202207251215 Missing requirement: com.nxp.AMMCLIB_S32K3xx.S32K3.root.1.1.29.feature.feature.group 1.1.29.202207251215 requires 'org.eclipse.equinox.p2.iu; com.nxp.RTD.S32K3XX.1.0.0.feature.feature.group [1.0.0,1.99.99)' but it could not be found.

Can you help me?

Thanks!

Radu

[Daniel_AGSO]

Hello,

as this thread is a bit older, im facting the same issue with the newest version. Can you maybe tell me, which versions of the different packages i need for installing version 1.1.37 of AMMCLIB for S32Kxx? Its a bit confusing and i cant find any documentation what version needs to be installed. 

My current installation:

Package: GDB Client for Arm Embedded Processors 12.1 Build 1702; Version: 1702; Build id: 202309251304
Package: S32 Design Studio Platform package; Version: 3.5.12; Build id: 202405290207
Package: S32K3.P01 RTD AUTOSAR R21-11 Version 3.0.0; Version: 3.0.0; Build id: 202304031555
Package: NXP GCC for Arm Embedded Processors v9.2 build 1649; Version: 1649; Build id: 202307190917
Package: GNU ARM PEMicro Interface Debugging Support; Version: 5.8.7; Build id: 202407171925
Package: S32K3xx development package; Version: 3.5.8; Build id: 202311290134
Package: NXP GCC for Arm Embedded Processors v10.2 build 1728; Version: 1728; Build id: 202307190908
Package: S32 Design Studio Platform Tools package; Version: 3.5.12; Build id: 202405290207
Package: NXP GCC for Arm Embedded Processors Build 1620; Version: 1620; Build id: 202005201521
Package: S32K3XX.P01 RTD AUTOSAR R21-11 Version 3.0.0; Version: 3.0.0; Build id: 202304031555
Package: S32 Design Studio Debugger Core; Version: 3.5.12; Build id: 202405281839

Thanks for t

[rdrosescu]

Hello Daniel,

In my opinion you should not be concerned about AMMCLIB because it is installed in Design Studio anyway. It's more important to tailor your DS installation to the program that you're looking to develop and the controller you're using. For now, only S32K344(BMS+Motor Control), S32K324, S32K358(BMS), S32k376(BMS), S32K396(Motor Control and Inverter) are available. Leaving aside the "learning" programs in the SDK that do not use AMMCLIB, it is enough to install the drivers and configurations specified for that application (ex.. the BMS application for S32K358 install strictly those specified in Design Files-Software -Automotive Software Package Manager) . Don't try to set up a  Design Studio good for the whole S32K3xx family with successive driver updates able to run all the applications on.  Also, I would advise that when you change your controller by ex.  from 358 to 396)  do a fresh install of Design Studio from zero, with the 396 drivers only. Or you keep them (358 and 396) on different computers. 

I think AMMCLIB only needs to be updated for motor control  and inverter applications and depend on the RTD version you have installed (and of course the microcontroller). And for MBD Toolbox for Simulink.

Following these rules, all applications I tried ran successfully without having to update AMMCLIB.

I wish you all the best,

Radu

[rdrosescu · Accepted solution]

Hello Mike,

I am interested in S32K344 and I work with S32K3X4EVB-Q257 and 172. I receive all updates on the associated account and email. I initially looked for information about the S32K396 and actually found nothing (no microcontroller, no evaluation kit) so I assumed that under this name was an upgrade for the S32k3xx series programs and later hardware developments. Even though I had some suspicions about the existence of a new member in the K3xx family I thought that the drivers do not influence each other, automatically selecting themselves according to the controller detected. It's a pity that the explanations as clear and to the point as those given by you are not included neither in the pdf documents associated with the drivers nor in those release notes.txt.
Thank you very much!

Radu

[rdrosescu]

Hi,

Installing an older version of RTD (S32K3 Real Time Drivers Version 1.0.0 HotFix 01) solves the problem and the error no longer occurs . So AMMCLIB for S32K3xx (RTD dependent) is supported. But a new reinstall of the latest RTD driver - S32K396_GD3162_RTD_4.4_0.8.0_CD01_D2208_DS_updatesite.zip is no longer supported ((Cannot complete the install because one or more required items could not be found.
Software being installed: GD3162 S32K3 0.8.0.202208310747 (com.nxp.GD3162.S32K3.root.0.8.0.feature.feature.group 0.8.0.202208310747)
Missing requirement: GD3162 S32K3 0.8.0.202208310747 (com.nxp.GD3162.S32K3.root.0.8.0.feature.feature.group 0.8.0.202208310747) requires 'org.eclipse.equinox.p2.iu; com.nxp.s32ds.s32k396.dev.feature.feature.group 1.0.0' but it could not be found)). I'm a bit confused as to which of the two RTD drivers is used by the S32 SD in this case.

[rdrosescu]

I forgot to mention that I have already installed  S32K396_GD3162_RTD_4.4_0.8.0_CD01_D2208.exe and S32K396_GD3162_RTD_4.4_0.8.0_CD01_D2208_DS_updatesite.zip

[mikedoidge]

Hello,

Let me clarify a bit. It can be somewhat confusing.

The S32Kxx name is referring to a family of devices (S32K312, S32K314, S32K322, S32K324, S32K341, S32K342, and S32K344). The S32K396 is a specific device, that is not supported by the packages using the S32Kxx name. For the S32K396, you must use the packages that contain the S32K396 name in the name of the package.

In addition, when you are using S32 Design Studio, the packages you need to install all end with ...DS_updatesite.zip. You indicated you installed both of the following packages: S32K396_GD3162_RTD_4.4_0.8.0_CD01_D2208.exe and S32K396_GD3162_RTD_4.4_0.8.0_CD01_D2208_DS_updatesite.zip. What you did is install the S32 Design Studio integration package of the Real-Time Drivers for S32K396 AND you installed the standalone version of the Real-Time Drivers for S32K396. The standalone version is for use with any integrated development environment you have. It contains no integration for any specific IDE. This is the one that is packaged as a .EXE file. They are providing the same Real-Time Drivers package.

So what I see from the error messages is that you probably are confused on what packages you need to install to enable the AMMCLIB package to be installed. There are dependencies between the various packages, but you need to install the correct package for the device you are intending to develop your application on. If you are looking to install the AMMCLIB for S32K3xx (RTD dependent) package to S32 Design Studio, you must first install the S32K3xx RTD package. However, the S32K3xx RTD package requires the S32K3xx Development Package. So you really need 3 packages, installed in this order:

1. S32K3xx development package

2. S32K3 Real-Time Drivers

3. AMMCLIB for S32K3xx (RTD dependent)

The S32DS Extensions and Updates installer should handle the precedence of these packages properly if you select them all at the same time, but if you should by chance receive some error, this is the order to install them individually.

In addition to this order of install, the correct versions should be used. S32K3xx_AMMCLib 1.1.29 depends on S32K3 RTD v1.0.0 and cannot be installed on top of any other version of RTD. We will add support for S32K3 RTD v2.0.1 in AMMCLib release 1.1.30 (the release is planned for end of September).

The current latest available version of the S32K3 RTD is: S32K3 RTD AUTOSAR 4.4 Version 2.0.0; Version: 2.0.0; Build id: 202203311410. This is what I have installed, but as you can see from my previous statement, it is not compatible with the AMMCLib 1.1.29 and you would therefore need to install the older version of the RTD. Please also note, this is for S32DS 3.4. It seems there is not yet a release of the S32K3 RTD for S32DS 3.5 (as mentioned earlier, the S32K396 RTD package for S32DS 3.5 is specific to the S32K396 device, does not support the other S32K3xx devices and there is currently no AMMCLib available for it yet), so you would need to wait for this to be released to use the S32K3xx AMMCLib on S32DS 3.5.

In summary, install S32DS 3.4, then install the packages listed above using the versions identified above. In case of any doubts, there exists release notes for each package which contain details of dependencies and supported versions.

Best Regards,

Mike

[hoppach]

Hello,

I am facing the same problem, and followed the installation as denoted by Mike:

1. S32DS 3.5
2. SW32K3_RTD_4.4_2.0.1
3. EBtresosStudio

Unfortunately, I end up with the RTD not available in S32DS Extensions and Updates, so AMMCLIB cannot be installed. How can I force S32DS to read in RTD?

Kind regards, Elmar

[mikedoidge]

Hello Elmar,

The best way is by downgrading to S32DS 3.4 until such time that a version of S32K3 RTD 4.4 is published in support of S32DS 3.5.

If needed, please also follow the steps detailed in the following article:

Troubleshooting: Can't See AMMCLib for S32K3 in S32DS 3.4, S32DS Extensions and Updates

Best Regards,

Mike

[GM767]

I am still experiencing this problem and I am using S32DS 3.5

Should I downgrade to S32DS 3.4?

[mikedoidge]

Hello @GM767,

Yes.

Best Regards,

Mike