Search Results

Hi guys, thank you for your support. Actually I asked my colleagues and they told me that the tool they use also accepts .elf files. That is why they were able to see the paths... Ok so we will search for a tool that accepts .hex and see how it goes. Thank you again!

My colleagues need to pass the code to a fuzzing tool. That tool accepts only .bin files. So, as you said I converted the .elf to hex file and then to .bin file but the library paths can still be seen through the tool. So I was thinking maybe if I could somehow remove them from the beginning (?)

Hi, when I build my project with Segger embedded studio the produced .elf file also includes the SDK library paths. I want the paths not to be visible/ written in the .elf file. I want to be used (obviously) but not displayed in .elf file after building the project because I want to share my .elf file with other people. So, I was wondering if there is some configuration in Segger Embedded studio that does that Any ideas? Thank you