MemMap.h file does not contain content for Calprm and Var memory segments that were present in .c source code file

31 Ansichten (letzte 30 Tage)

Uday Subramaniam am 12 Jul. 2024 um 21:16

0
Verknüpfen

Direkter Link zu dieser Frage

https://de.mathworks.com/matlabcentral/answers/2136963-memmap-h-file-does-not-contain-content-for-calprm-and-var-memory-segments-that-were-present-in-c-so

Kommentiert: Uday Subramaniam vor etwa 4 Stunden

Hello,

I am using Matlab R2023b. I have created a Simulink model and generated AUTOSAR compliant C code. In my Simulink model, I created SwAddrMethods named CAL, CODE and VAR. The CAL method is for Calprm memory section, CODE is for Code memory section and VAR is for Var memory section.

In my generated .c source code and .h header files, I see the #defines for each SwAddrMethod. Some excerpts from my .c code below:

/* Please see snapshots for source code and MemMap header file for reference. */

Same case is true for the .h header file. I can see instances of #defines for all 3 SwAddrMethods.

But, in the generated MemMap.h header file, I can only see reference to #ifdef PwrSteerOutPrcs_START_SEC_CODE

#undef PwrSteerOutPrcs_START_SEC_CODE and #ifdef PwrSteerOutPrcs_STOP_SEC_CODE

#undef PwrSteerOutPrcs_STOP_SEC_CODE.

I do not notice the START_SEC_CAL, STOP_SEC_CAL and START_SEC_VAR, STOP_SEC_VAR are being generated.

/* Please see snapshots for source code and MemMap header file for reference. */

Q1. What can cause the #defines for CAL and VAR to not be defined in MemMap.h? Is this soem setting I can correct in Autosar Component Viewer app / Simulink Model Settings? Or is it a bug in Matlab R2023b release?

Attached are snapshot #1 of the 1 instrumented signal. Am I using the correct settings? I have noticed in some models that instead of 'From signal object: Global' , there is an 'Auto' option in the dropdown for 'Mapped to' (attached in snapshot #2). I do not get that option for 'Auto'.

Q2. Is there a setting I should change on my Model Settings / Autosar App to get the Auto dropdown option? Will that help resolve Q1? Or is this a bug in matlab R2023b. Please advise.

Any help is much appreciated! Thank you!