- 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
- :
- 2413554_en-US
2413554_en-US
2413554_en-US
2413554_en-US
In Simulink, when configuring the hardware, I am trying to change the directory for the reference configuration to a relative path.
Simulink -> HW-Settings -> Hardware Implementation -> Target hardware resources -> Referenced Configuration
Reference Configuration Path = '.\generated\referenced_config'
Unfortunately, it is not possible to enter a relative path here.
Nor have I so far been able to set the path via a MATLAB script.
Although the script appears to set the path in CoderTargetData, it is not actually applied.
Either the old path remains active, or an empty path is applied.
Is there a way to set a relative path for the reference configuration?
Hi, @AlexG124,
Thanks for the details. Could you please help us and let us know what are the MBDT toolbox version, as well as the MATLAB version that you are currently using?
In case you are using S32K3 toolbox, there is a model example showcasing the referenced configuration workflow, under model_ref/s32k3xx_refconfig_s32ct folder. Here you will find a MATLAB script called s32k3xx_refconfig_update_paths_callback.m that could help in achieving your goal.
It will be also helpful if you could let us know more details on your referenced configuration way of working, usage and application flow.
Best regards,
Dragos