TMS320F28388S: Registers in CM Core TI-TXT

Hi Ed,

Let me look into this and get back to you within the next few days.

Best Regards,

Aishwarya

Hi Aishwarya,

I tried that, and received the following error message.  Would a different syntax work?

error #10227-D: bad section property:  "NOLOAD"

Thank you,

Ed

If I remove the NOINIT part, it builds, and that area is no longer in the TI-TXT output.

Since this is not part of the normal RAM, will it be initialized before the program gets to main()?

Thank you,

Ed

Hi Aishwarya,

We don't want it to be initialized as we are doing it ourselves.  Is there a way to prevent it and still keep the NOLOAD?

Thank you,

Ed

Ed,

Can you confirm if you have the --ram_model or --rom_model currently invoked as well? You'll want this disabled

CM RAMs are initialized on POR to a zero value. Any initializations needing to be done for specific variables is typically done in the application code.

Is there a specific reason you want to initialize it in SW?

Best Regards,

Aishwarya

Hi Aishwarya,

We are using the rom_model option.

Now that I think about it, clearing the memory ourselves may not be helpful.  If we select NO_INIT, will the code which initializes is be removed?  Or will it be there regardless?

Thank you,

Ed

Ed,

BTW the rom_model allows for auto-initialization at boot time as follows.

The NOINIT attribute tells the compiler that a certain section should not be initialized and the linker needs to place the section in a special .noinit memory section. If you do not want to enable entire sections to be NOINIT, it's possible to use attributes with specific variables as shown here: 2.7.3. Variable Attributes — TI Arm Clang Compiler Tools User's Guide 

Best Regards,

Aishwarya

If I understand this correctly, marking them as NOINIT would not change the amount of flash being used?

For the memory which cannot be initialized from the CM side, should it still be marked as NOINIT?  Or will the linker automatically take care of that?

Thank you,

Ed

OK.  And what about the memory which the CM core cannot write, i.e. the C1 to CM RAM.  Obviously, that cannot, physically, be initialized by the CM core.  Should that be marked as NOINIT?

Thank you,

Ed

OK.  Thank you for your help Aishwarya,

Ed

Ed,

Glad to hear it, would you mind marking the previous answers as resolved as well, for anyone seeing this thread in the future? Thank you.

Best Regards,

Aishwarya

Didn't know I could mark two!  Good to know.

Thanks again,

Ed

Ed, 

Thank you!

Best Regards,

Aishwarya