Problems using BMS GEN1 SDK 4.4 and R21-11 Version 1.0.3

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

Problems using BMS GEN1 SDK 4.4 and R21-11 Version 1.0.3

200 次查看
PhilippH
Contributor I

Dear Sir or Madam,

we have troubles using the driver „S32K3 BMS GEN1 SDK 4.4 and R21-11 Version 1.0.3“ in S32 Design Studio with S32K358.

In the Release Notes of the BMS SDK, in section 2.2.2 Installation Design Studio, the following steps are written:

  1. Install S32 Design Studio IDE v3.5 Service Pack 1 EAR4 Build 23030
  2. Install the Update Site for S32K3 Real Time Drivers AUTOSAR 4.4 and R21-11 Version 3.0.0: SW32K3_RTD_4.4_R21-11_3.0.0_D2303_DS_updatesite.zip
  3. Install this BMS GEN1 SDK SW package using the Update site installer: SW32K3_BMS_GEN1_SDK_4.4_R21-11_1.0.3_updatesite_D2407.zip

Until now, we worked with S32 DS v3.6.3 and SW32K3_S32M27x_RTD_R21-11_6.0.0_D2506_DesignStudio_updatesite.zip.

Installing SW32K3_BMS_GEN1_SDK_4.4_R21-11_1.0.3_updatesite_D2407.zip with RTD 6.0.0 in S32 DS v3.6.3 fails with an error message [1].

A downgrade from RTD 6.0.0 to 3.0.0 leads to error messages upon opening our project file that we created using RTD 6.0.0 [2].

I created a blank project using S32 DS v3.5 (I could not find the exact Service Pack 1 EAR4 Build 2030). I could install RTD 3.0.0 and the BMS SDK according to the release notes above. However, the generated code did not compile because standardTypes.h was not found.

My questions:

  • Is there a way to import, configure and compile the BMS Drivers using the BMS SDK, RTD 6.0.0 and S32 DS v3.6.3?
  • If not, do all developers that use S32 DS need to downgrade their installation and RTD to comply with the steps from the release notes? We all work on a common configuration of which the BMS driver is part of.
  • How do we generate code that compiles?

 

Best regards,

Philipp

 

[1]:

S32DS v3.6.3

Installation of BMS-SDK mit RTD 6.0.0:

Operation details Software being installed:
com.nxp.BMS_GEN1_SDK.S32K3XX.root.1.0.3.feature.feature.group 1.0.3.202408021227 Missing requirement:
com.nxp.BMS_GEN1_SDK.S32K3XX.root.1.0.3.feature.feature.group 1.0.3.202408021227 requires
'org.eclipse.equinox.p2.iu; com.nxp.RTD.S32K3.root.feature.feature.group 3.0.0' but it could not be found

 

[2]:

S32DS v3.6.3

Loading our S32DS Project with RTD 3.0.0:

An error has occurred. See error log for more details.

PeripheralExpressionException[
Description: Feature FEATURE_PORT_PINSWITHIF not defined for the part number S32K358, core M7_0_0 and peripheral null
Function: getFeature(valid)
Contexts:
ExpressionContext[ child_context = ChildContext[
 $this = Siul2_Port.PortConfigSet.PortContainer.0.PortPin.0.PortPinIfe
 component = Siul2_Port
 $instance = Siul2_Port
 $group = BOARD_InitPeripherals]]

ExpressionContext[ child_context = ChildContext[
 $this = Siul2_Port.PortConfigSet.PortContainer.0.PortPin.0.PortPinIfe
 component = Siul2_Port
 $instance = Siul2_Port
 $group = BOARD_InitPeripherals]]

ExpressionContext[ child_context = ChildContext[
 $this = Siul2_Port.PortConfigSet.PortContainer.0.PortPin.0.PortPinIfe
 component = Siul2_Port
 $instance = Siul2_Port
 $group = BOARD_InitPeripherals]]
]

 

0 项奖励
回复
1 回复

121 次查看
Robin_Shen
NXP TechSupport
NXP TechSupport

Hi Philipp,

Sorry, I checked the latest HVBMS for the S32K358 and it still uses S32DS v3.5 and RTD 3.0.0.
At this stage, I'm afraid you'll have to refer to section 4 BMS Software installation procedure in the BMS_SWInstalationGuide_Bring-up_2024.10.pdf to install these software.

BMS_SWInstalationGuide_Bring-up_2024.10.png

It is not recommended to install these software in S32DS v3.6.3. Unless the HVBMS team releases a new version of the software package, those examples will not work in S32DS v3.6.3 + RTD 6.0.0 environment.


Best Regards,
Robin
-------------------------------------------------------------------------------
Note:
- If this post answers your question, please click the "ACCEPT AS SOLUTION" button. Thank you!

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------