• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 31 subscribers
  • Views 152 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

MSPM0G3519: Fls_CheckAddressAlignmentWithMaxOperatableSize is failing when it called in Fls_Write

MSPM0G3519: Getting errors while using compiler option --no_slash_comment

Mubin Jakler
Prodigy 90 points

Part Number: MSPM0G3519

Hello Team,

We are working on MSPM0_MCAL_01.00.00.00_GHS package and one of our customer is asked for (--no_slash_comment) compiler option. when we used this option we are getting errors from MCAL side.

May i know any plan to qualify with this compiler option?

Compiler version : Green Hills, Multi v8.1.4 Comipler v2024.1.4 

BR,

Mubin Jakler

  • 0
    TI__Genius 13985 points

    Hi Mubin,

    Could I know if there any compiling issue when you compile MCAL package with Green Hills, Multi v8.1.4 Comipler v2024.1.4 compiler when (--no_slash_comment) compiler option is not used?

    As I checked, the (--no_slash_comment) compiler option is used to disable "//" comment grammar in code, which will cause compiling issue when there is "//' comment in package. Could I also know the use case why you need this option? Thanks.

  • 0 in reply to Pengfei Xie
    Prodigy 90 points

    Hi  

    If we are not use this compiler option we are able to compile all modules on Green Hills compiler.

    customer is want to use this compiler option on there platform. 

  • 0 in reply to Mubin Jakler
    TI__Genius 13985 points

    Hi Mubin,

    Thanks for your feedback.

    The --no-slash-comment option is used to disable the recognization of "//' by compiler, and ss I checked the “//” is used in MCAL as comment function, so customer will see compiling issue when they use this option.

    So my questions is why customer require to us "--no-slash-comment" option in their application, where is this requirement from (a preference of customer or a hard requirement due to some test requirement?). I need to understand the necessity before we could report it internally. Thanks.

  • 0 in reply to Pengfei Xie
    TI__Genius 13985 points

    Hi Mubin,

    The "--no-slash-comment" GHS compiler option is supported in the latest MCAL release to your team in early July. Let me close this thread, please let me know if any further questions, thanks.

  • 0 in reply to Pengfei Xie
    Prodigy 90 points

    Hi  ,

    Thank you so much, In this latest release i can see 10 modules are being qualified and verified at our end it's working fine but from Adc and Cdd_I2c modules  faced compile issue similar for // comment still is used.

    latest MCAL package : MCAL_MSPM0_01.00.00.00_GHS_071026

    Thanks for you feedback.

    BR,

    Mubin

  • 0 in reply to Mubin Jakler
    TI__Genius 13985 points

    Hi Mubin,

    Thanks for your feedback. 

    As I checked internally, this release is done specifically for 10 modules (MCU, PORT, DIO, FLS, FEE, GPT, ICU, SPI, CDD_DMA, CAN) as also shown in release notes. We haven’t addressed the compiler flag requests or testing for the remaining 6 modules. This is also aligned with AUMOVIO and Electrobit before our release. 

    Could you check with your team about whether this release meets your expectation or it is a new request for the compiler flag to support remaining 6 modules? Thanks.