topic Re: viable alternative at input 'ASSERT' in MCUXpresso General

viable alternative at input 'ASSERT'

tbiberdorf — Fri, 04 Jun 2021 17:28:19 GMT

I have been getting the following linker error being posted by a host of .ld files that included in my workspace but not used by my project settings and I'm not sure how to have MCUXpresso ignore them.

I am using version v11.2.1 of MCUXpresso:

I modified my project settings as per the following forum entry but this has made no effect on the ASSERT issue.

https://community.nxp.com/t5/MCUXpresso-IDE/How-can-we-disable-the-syntax-checking-of-linker-files/m-p/943064

This does not prevent my project from building and I am still able to load and debug my project with no issues. It's just that I don't know why MCUXpresso is indicating that they are there

Does anyone have any other suggestions to follow?

Thanks

Re: viable alternative at input 'ASSERT'

ErichStyger — Fri, 04 Jun 2021 18:14:19 GMT

Hi @tbiberdorf ,

if you could post your linker file(s) here then the NXP IDE engineering team could have a look and fix the problem in linker file parser (I hope).

Otherwise: if you open the file with the text editor, the errors still remain in the Problems view.

To get them removed, go to the view and delete them:

I hope this helps,

Erich

Re: viable alternative at input 'ASSERT'

tbiberdorf — Fri, 04 Jun 2021 19:29:32 GMT

attached is one of the linker files.

The interesting thing is that my project does not even use any of these .ld files, so all these error messages really confuse finding and fixing errors when they do happen.

The error message is associated with lines 117 and 154.

. = ASSERT((__data_load_start__ + SIZEOF(.data)) >= __FLASH_segment_start__ && (__data_load_start__ + SIZEOF(.data)) <= (__FLASH_segment_end__) , "error: .data is too large to fit in FLASH memory segment");

. = ASSERT(__heap_end__ >= __SRAM_segment_start__ && __heap_end__ <= (__SRAM_segment_end__) , "error: .heap is too large to fit in SRAM memory segment");

Re: viable alternative at input 'ASSERT'

ErichStyger — Sat, 05 Jun 2021 04:56:22 GMT

Hi @tbiberdorf ,

>>The interesting thing is that my project does not even use any of these .ld files,

The IDE parses the file when you open it, flagging errors that time. The messages are not coming from the linker but from the IDE.

Looking closer to your ASSERTs I think they are indeed wrong, see https://sourceware.org/binutils/docs/ld/Miscellaneous-Commands.html : you cannot use them as expressions and assign it to the current location: you need to remove the .= in front of them.

I hope this helps,

Erich