2022-01-26 10:01 PM
2022-01-31 09:17 AM
Have a look at the build analyzer or the map-file for the build configuration producing the elf-file.
It will show you what is consuming data.
The supplied ioc-file only tells us which components that are enabled in MX. Not something we can use to make any conclusions. I see references to I-CUBE packages. Are these possibly contributing to the huge memory usage? Is it possible to disabled them?
2022-01-27 12:37 AM
2022-01-27 06:15 AM
230kB is a lot of data. You need to remove some of it in order to fit into the available space. No magic solution to that. What is taking up so much space in your flash?
2022-01-31 09:17 AM
Have a look at the build analyzer or the map-file for the build configuration producing the elf-file.
It will show you what is consuming data.
The supplied ioc-file only tells us which components that are enabled in MX. Not something we can use to make any conclusions. I see references to I-CUBE packages. Are these possibly contributing to the huge memory usage? Is it possible to disabled them?
2023-02-13 05:06 AM
Hello everybody!
I was facing the same on the present date and I managed to solve it as follows:
1) click on Run in the menu tab
2) click on Run Configurations
3) in the item "C/C++ Application:" go to Browser and insert the path where the .elf file is saved
4) click Apply and then Run
It is very likely that the program will compile and the error will no longer be displayed.
In my case this happened because the directory path where the .elf file is had been lost and when I re-entered the file location everything went back to normal.
Hope my tip helped.
2023-06-23 09:40 AM
Hi, i can't find the .elf file. Can you help me please?
2023-06-23 10:34 AM
Keil uses .AXF naming.
Executable objects might be missing if Linker doesn't complete properly.