Skip to content

[BUG]warnings when LARGE DATA MODEL used on MSP430 CCS port #671

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
Closed
dimitrovand opened this issue May 5, 2023 · 2 comments
Closed

[BUG]warnings when LARGE DATA MODEL used on MSP430 CCS port #671

dimitrovand opened this issue May 5, 2023 · 2 comments
Assignees
@moninom1
Labels
bug Something isn't working

Comments

@dimitrovand
Copy link

dimitrovand commented May 5, 2023 •
edited
Loading

Describe the bug
Warnings in portext.asm from portSAVE_CONTEXT and portRESTORE_CONTEXT dew to usage of mov.w in large data model. Using mov_x resolves all warnings.

Target

  • Development board: MSP-EXP430FR5994
  • IDE and version: Code Composer Studio 12.1.0.00007
  • Toolchain and version: Default for the IDE version

Host

  • Host OS: Windows
  • Version: 11

To Reproduce

  • Use any project containing the FreeRTOS port
  • In linker script select data and code to be moved to higher FRAM (FRAM2)
  • In project settings select Properties->Build->MSP430 Compiler->Processor Options and select large data/code models + --near_data = none
  • Add LARGE_DATA_MODEL in Properties->Build->MSP430 Compiler->Predefined Symbols

Expected behavior
No warnings

Screenshots
freertos
@dimitrovand dimitrovand added the bug Something isn't working label May 5, 2023
@dimitrovand dimitrovand changed the title [BUG]warnings when LARGE DATA MODEL used on MSP430 CSS port [BUG]warnings when LARGE DATA MODEL used on MSP430 CCS port May 9, 2023
@moninom1
Copy link
Member

moninom1 commented May 9, 2023

Hi @dimitrovand

Thank you for reporting the issue!
We are looking further into this issue. Will update in a while. Thank you for your patience!

@moninom1 moninom1 self-assigned this May 9, 2023
@aggarg aggarg mentioned this issue May 15, 2023
Merged
@aggarg
Copy link
Member

aggarg commented May 15, 2023

Fixed in this PR - #676

@aggarg aggarg closed this as completed May 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@moninom1 moninom1

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@aggarg @dimitrovand @moninom1