Segger Embedded Studio Code Size Limit?

RE: Segger Embedded Studio Code Size Limit?

Mike Marks — Tue, 13 Feb 2018 18:14:57 GMT

Thanks to those who suggested looking at the build configurations. Once I switched to use Internal instead of "internal and external", the code size issue seems to have vanished. Another issue has come up regarding link errors in the same project, but I'll close this and post that question in a new thread.

RE: Segger Embedded Studio Code Size Limit?

Mike Marks — Tue, 13 Feb 2018 14:10:24 GMT

I uploaded the project to the file sharing site Mega.nz and opened a private ticket. Thanks much for your help.

RE: Segger Embedded Studio Code Size Limit?

tesc — Tue, 13 Feb 2018 13:30:09 GMT

I would like to have a look at your SES project in order to reproduce and possibly figure out what the issue is.

If you want to keep it confidential then you can create a private ticket in order to send it there instead. If so, please reference this thread in that ticket.

Regards,
Terje

RE: Segger Embedded Studio Code Size Limit?

Mike Marks — Mon, 12 Feb 2018 22:03:14 GMT

I did import the project again and, as you suggested, made sure that only the Internal choice was selected and not the external one. When I first imported the project a few days ago, I may have had "both" chosen. Either way, thanks much for the help. I am not quite building yet, but trying to resolve a couple undefined references that I hope to solve tomorrow. At least there is no IAR reference...so far on my build.

RE: Segger Embedded Studio Code Size Limit?

RK — Mon, 12 Feb 2018 21:49:42 GMT

and running one myself I see SES creates configurations for both by default. So just select the 'internal' one instead of the 'external' one from the dropdown at the top left corner of your screen, or don't make an external one at all as it doesn't work.

RE: Segger Embedded Studio Code Size Limit?

RK — Mon, 12 Feb 2018 21:43:20 GMT

Not quite as much info in that build transcript as I'd hoped but the fact it has 'iar' startup in it and all the error message are IAR error messages says to me you're basically just running an external make and still using .. IAR.

If you read my message from a few days ago I asked "did you import the project as some kind of external make project?" and it seems you did. So go re-import it again and don't pick external anything, choose one of the SES nordic native project templates.

RE: Segger Embedded Studio Code Size Limit?

Mike Marks — Mon, 12 Feb 2018 21:37:37 GMT

I did see when checking Build -> Build Configurations that the first Private Configuration listed is "External IAR"? Could this have something to do with my problem? If so, what setting would I change to fix? Thanks, Mike

RE: Segger Embedded Studio Code Size Limit?

Mike Marks — Mon, 12 Feb 2018 21:15:45 GMT

Did a clean and then rebuilt the project - here is the output:

Building ‘hm_chair’ from solution ‘hm_chair’ in configuration ‘nrf52832_xxaa External’
Compiling ‘app_accel.c’
Warning[Pe177]: variable "m_twi" was declared but never referenced
Warning[Pe177]: variable "MagState" was declared but never referenced
Warning[Pe177]: function "TwiHandler" was declared but never referenced
Warning[Pe177]: function "TwiInit" was declared but never referenced
Compiling ‘chair_state.c’
Compiling ‘system_timer.c’
Compiling ‘main.c’
Warning[Pe177]: variable "loopCount" was declared but never referenced
Compiling ‘ctl_accel.c’
Warning[Pe550]: variable "iBfz" was set but never used
Compiling ‘ctl_adc.c’
Compiling ‘ctl_ANT.c’
Compiling ‘ctl_flash.c’
Assembling ‘iar_startup_nrf52.s’
Compiling ‘system_nrf52.c’
Compiling ‘ant_channel_config.c’
Compiling ‘hmi_i2c.c’
Compiling ‘nrf_drv_common.c’
Compiling ‘nrf_drv_gpiote.c’
Compiling ‘nrf_drv_saadc.c’
Compiling ‘nrf_drv_timer.c’
Compiling ‘nrf_drv_twi.c’
Compiling ‘nrf_drv_uart.c’
Compiling ‘nrf_saadc.c’
Compiling ‘app_error_weak.c’
Compiling ‘app_error.c’
Compiling ‘app_fifo.c’
Compiling ‘app_timer.c’
Compiling ‘app_uart_fifo.c’
Compiling ‘app_util_platform.c’
Compiling ‘nrf_assert.c’
Compiling ‘nrf_memobj.c’
Compiling ‘nrf_balloc.c’
Compiling ‘nrf_section_iter.c’
Compiling ‘nrf_strerror.c’
Compiling ‘retarget.c’
Compiling ‘nrf_sdh.c’
Compiling ‘nrf_sdh_ant.c’
Linking ‘hm_chair.out’
Error[Li016]: size limit exceeded. The application needs 0x864c (34 380) bytes, which is greater than the limit of 0x8000 (32 768) bytes.
Build failed

RE: Segger Embedded Studio Code Size Limit?

RK — Mon, 12 Feb 2018 20:59:04 GMT

how about clean it - build it - paste the actual transcript from the build especially the last step. If there's a build error one stage must be generating it.

RE: Segger Embedded Studio Code Size Limit?

Mike Marks — Mon, 12 Feb 2018 15:54:14 GMT

I assume the converted project file is either the <name>.emProject or <name>.emSession? Checking both of those files does not show the error message. The Compiler Options -> Linker shows no additional input files or linker scripts. If the compiler is set to gcc, does that mean that the IAR compiler is not being used?

RE: Segger Embedded Studio Code Size Limit?

Mike Marks — Mon, 12 Feb 2018 15:47:21 GMT

The command that generates the error is "Linking <project name>.out". Prior to that the commands are "Compiling <filename>". Attempting to search through the project files (<name>.emProject" and <name>.emSession" does not show the size limit error message. From earlier messages, it sounds like I could somehow be using the IAR compiler? Could one of the linker options be wrong?

RE: Segger Embedded Studio Code Size Limit?

RK — Mon, 12 Feb 2018 14:13:26 GMT

don't see anything wrong with those assembler options. Sure they wouldn't be causing GCC to emit an IAR error message.

RE: Segger Embedded Studio Code Size Limit?

Mike Marks — Mon, 12 Feb 2018 14:11:59 GMT

I also noticed that the Additional Assembler Options shows the following: "--cpu;$(CoreType);--fpu;$(FPU3);-S" from solution in External IAR configuration

RE: Segger Embedded Studio Code Size Limit?

RK — Mon, 12 Feb 2018 14:11:38 GMT

This is making no sense at all. When you build the project in SES you should get a build transcript, can you see it actually running the GCC compile and link commands? What command does it run at the point it emits the error message? GCC just doesn't emit that error message, it's entirely an IAR thing. The import project makes an entirely native project from the original one so .. there should be nowhere to put such an error.

The only other possibility I can think of, not that I've EVER seen it, is that the export of the project exported a linker file with that error message in it. You could look at (grep) the converted project source to see if that happened.

RE: Segger Embedded Studio Code Size Limit?

Mike Marks — Mon, 12 Feb 2018 14:04:28 GMT

Compiler settings shows gcc as the compiler. The only choices listed are gcc and clang if I chooise the pull-down under Compiler. The project was imported using File -> Import IAR EWARM / Keil MDK Project... and then selecting the .eww file from the project directory.

RE: Segger Embedded Studio Code Size Limit?

tesc — Mon, 12 Feb 2018 09:29:20 GMT

Can you check compiler settings for the project? ("Project" menu -> "Edit options...", then select the "Code" -> "Compiler" item.)

RE: Segger Embedded Studio Code Size Limit?

RK — Fri, 09 Feb 2018 22:39:08 GMT

ok that is an IAR error which would indicate you're still actually compiling with IAR. Did you import the project as some kind of external made project? A native SES built one has no limits and it doesn't produce IAR error messages.

RE: Segger Embedded Studio Code Size Limit?

Mike Marks — Fri, 09 Feb 2018 13:52:16 GMT

Exact error is "Error [Li016]: size limit exceeded. The application needs 0x864c (34380) bytes, which is greater than the limit of 0x8000 (32768) bytes." When I check the Tools -> License Manager and choose Manage Activations, I see that the product is licensed to Mike Marks - Avid Technologies.

RE: Segger Embedded Studio Code Size Limit?

RK — Fri, 09 Feb 2018 08:24:51 GMT

No the size limit didn't come over from IAR. What's the ACTUAL error message? Have you registered your copy of SES to get the free Nordic license which allows full access and even commercial use, even though I believe that SES has no size limit either.