- Forums
- Product Forums
- General Purpose MicrocontrollersGeneral Purpose Microcontrollers
- i.MX Forumsi.MX Forums
- QorIQ Processing PlatformsQorIQ Processing Platforms
- Identification and SecurityIdentification and Security
- Power ManagementPower Management
- Wireless ConnectivityWireless Connectivity
- RFID / NFCRFID / NFC
- Advanced AnalogAdvanced Analog
- Neural Processing UnitsNeural Processing Units
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- S12 / MagniV Microcontrollers
- Powertrain and Electrification Analog Drivers
- Sensors
- Vybrid Processors
- Digital Signal Controllers
- 8-bit Microcontrollers
- ColdFire/68K Microcontrollers and Processors
- PowerQUICC Processors
- OSBDM and TBDML
- S32M
- S32Z/E
-
- Solution Forums
- Software Forums
- MCUXpresso Software and ToolsMCUXpresso Software and Tools
- CodeWarriorCodeWarrior
- MQX Software SolutionsMQX Software Solutions
- Model-Based Design Toolbox (MBDT)Model-Based Design Toolbox (MBDT)
- FreeMASTER
- eIQ Machine Learning Software
- Embedded Software and Tools Clinic
- S32 SDK
- S32 Design Studio
- GUI Guider
- Zephyr Project
- Voice Technology
- Application Software Packs
- Secure Provisioning SDK (SPSDK)
- Processor Expert Software
- Generative AI & LLMs
-
- Topics
- Mobile Robotics - Drones and RoversMobile Robotics - Drones and Rovers
- NXP Training ContentNXP Training Content
- University ProgramsUniversity Programs
- Rapid IoT
- NXP Designs
- SafeAssure-Community
- OSS Security & Maintenance
- Using Our Community
-
- Cloud Lab Forums
-
- Knowledge Bases
- ARM Microcontrollers
- i.MX Processors
- Identification and Security
- Model-Based Design Toolbox (MBDT)
- QorIQ Processing Platforms
- S32 Automotive Processing Platform
- Wireless Connectivity
- CodeWarrior
- MCUXpresso Suite of Software and Tools
- MQX Software Solutions
- RFID / NFC
- Advanced Analog
- Neural Processing Units
-
- NXP Tech Blogs
- Home
- :
- Translated Content
- :
- Multi Source Translation Content
- :
- 2182893_en-US
2182893_en-US
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
2182893_en-US
2182893_en-US
Hi,
I'am still encountering this problem, if someone could help would be greatful.
I'm using MBDT 1.5 on Matlab 2022b
thanks,
Simon
Hi, @simon98,
We have recently released a new version of the toolbox (Model-Based Design Toolbox for S32K3 version 1.7.0). Would you be able to download and upgrade to this version of the toolbox, and then retry to determine whether the issue persists?
Please let us know about the progress.
Best regards,
Dragos
First of all, thank you very much @dragostoma for your prompt and helpful response—it was extremely useful.
I’m unable to find the CDD_Sbc_fs26 drivers in the S32 Configuration Tool. After some research, I learned that MBDT restricts installing new software into S32CT to prevent users from breaking the toolchain.
Before finding this, I attempted to install the FS26 package through S32 Design Studio using Help → Install New Software. However, after reopening Simulink and checking S32CT, the CDD drivers were still not available. It seems that S32 Design Studio and the Simulink S32 Configuration Tool operate independently and do not share installed components.
As a workaround, I copied the FS26 initialization blocks from the BMS example project. But when I try to build, deploy, and start the model, I encounter the following error: fatal error: CDD_Sbc_fs26.h: No such file or directory
I’m currently stuck at this point and need guidance on how to properly resolve this issue and integrate the required FS26 drivers or anyother way to move forward.
MBDT FS26
Hi,
SBC drivers have compatibility with RTD. Look into SBC release notes to find what RTD version support. You may need to install an appropriate SBC version if you want to use a certain RTD version, or viceversa.
For example with RTD 7.0.1 you need SBD drivers 6.0.0, if i remember right.
Greetings,
Simon
Hi @Naresh2000 ,
The message you are seeing is expected. The latest MBDT BMS Toolbox is currently validated only with MBDT S32K3xx 1.4.0. It is not yet compatible with MBDT S32K3xx 1.7.0, which is why Simulink prompts you to switch back to version 1.4.0.
So, depending on your use case:
- If you intend to use the BMS toolbox, please downgrade MBDT S32K3xx to version 1.4.0, which is the latest supported combination.
- If you do not need BMS functionality, you can continue using MBDT S32K3xx 1.8.0 without issues, which is actually the latest S32K3 toolbox released.
In short, the latest available BMS release currently works only with the S32K3xx 1.4.0 platform. Support for newer S32K3xx versions will come in a future BMS release.
Hope is clear now.
Best regards,
Dragos
I am using the newer version, MBDT S32K3xx 1.7.0, but Simulink shows a prompt saying that MBDT BMS 1.2.0 does not support version 1.7.0 and suggests switching to MBDT S32K3xx 1.4.0. What should I do in this situation?