Hello community,
we developed our own toolchain for an Intel Cyclone V FPGA (MitySOM-5CSX) using this tutorial (https://de.mathworks.com/help/ecoder/target-sdk.html), to generate code from Simulink models using the Embedded Coder Support Package for ARM Cortex-A Processors. In the 5th step of this tutorial (Activate the Application Deployment Feature) the IP address of the target board is specified, which then also appears correct under Configuration Parameters -> Hardware Implementation -> External Mode.
Now, if you want to change this IP address at this point (Configuration Parameters -> Hardware Implementation -> External Mode), the embedded coder will not use this new IP address, but only the one that was specified when the target was created. That means, no matter which IP address the user later sets under Configuration Parameters -> Hardware Implementation -> External Mode, only the one specified when creating the target will be used for code generation, which is unsuitable.

Is this a bug or a feature? Where can the user later set the IP address of his target board, which then will be used by the embedded coder?

Thank you guys and with best wishes,
Lars LindnerHello community,
we developed our own toolchain for an Intel Cyclone V FPGA (MitySOM-5CSX) using this tutorial (https://de.mathworks.com/help/ecoder/target-sdk.html), to generate code from Simulink models using the Embedded Coder Support Package for ARM Cortex-A Processors. In the 5th step of this tutorial (Activate the Application Deployment Feature) the IP address of the target board is specified, which then also appears correct under Configuration Parameters -> Hardware Implementation -> External Mode.
Now, if you want to change this IP address at this point (Configuration Parameters -> Hardware Implementation -> External Mode), the embedded coder will not use this new IP address, but only the one that was specified when the target was created. That means, no matter which IP address the user later sets under Configuration Parameters -> Hardware Implementation -> External Mode, only the one specified when creating the target will be used for code generation, which is unsuitable.

Is this a bug or a feature? Where can the user later set the IP address of his target board, which then will be used by the embedded coder?

Thank you guys and with best wishes,
Lars Lindner Hello community,
we developed our own toolchain for an Intel Cyclone V FPGA (MitySOM-5CSX) using this tutorial (https://de.mathworks.com/help/ecoder/target-sdk.html), to generate code from Simulink models using the Embedded Coder Support Package for ARM Cortex-A Processors. In the 5th step of this tutorial (Activate the Application Deployment Feature) the IP address of the target board is specified, which then also appears correct under Configuration Parameters -> Hardware Implementation -> External Mode.
Now, if you want to change this IP address at this point (Configuration Parameters -> Hardware Implementation -> External Mode), the embedded coder will not use this new IP address, but only the one that was specified when the target was created. That means, no matter which IP address the user later sets under Configuration Parameters -> Hardware Implementation -> External Mode, only the one specified when creating the target will be used for code generation, which is unsuitable.

Is this a bug or a feature? Where can the user later set the IP address of his target board, which then will be used by the embedded coder?

Thank you guys and with best wishes,
Lars Lindner embedded coder, code gerneration, external mode, ip adress, arm cortex-a processors MATLAB Answers — New Questions

​