Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Limitation for multiple FMU instances #84

Merged
merged 1 commit into from
Jul 1, 2024
Merged

Limitation for multiple FMU instances #84

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/index.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -511,6 +511,8 @@ General limitations:
* If the FMU contains target-specific binaries _and_ target-specific source code for the same platform, the corresponding A2L files cannot be assigned uniquely.
Therefore, this constellation is not applicable to this layered standard and the FMU exporter must decide between source code and binary files for this platform.

* If the manifest attribute `supportsDirectMemoryAccessViaA2L` is set to `true` and an external XCP service is used, the importer must not instantiate the FMU more than once because a variable in the A2L file has only one associated memory address.

Limitations for binary FMUs:

* Normally only variables in the memory segments owned by the main FMU binary `<modelIdendifier>.{dll|so}` are accessible by the XCP service, i.e., variables defined in source code modules and in statically linked libraries.
Expand Down
Loading