nibbly78 Community Member

In the Rowley guide for externally built application, the wizard points "exactly" to the .elf in question... Can't seem to do this in SES!

.

So, if I "modify" the project type from Externally Built Executable to >> Excutable, debug works which proves my paths etc to the elf file were correct all along. However, I lose the ability to call the make file to build etc. I then changed it back to…

This is the layout and settings that I have. $(ProjectDir)=C:/Firmware/MotorisedFaders/MyBranch/motor-firmware Inside of ProjectDir is another folder called MQ500MotorFader which is where the elf file MQ500MotorFader.elf is generated when the make file…

I already made the project name the same as the ProjectName.elf so the Debug->Debugger->Command Arguments >> $(ProjectName)$(EXE) is already correct. The linking that's done by the make file is too complicated for me to try to get SES to do the…

To highlight the problem better I did the following :- step 1) I used the project wizard to create a new Hello World program and tested that is ran with debugger. (worked just fine) step 2) I then created another project side by side but selected…

I have managed to instruct SES to build my elf file by calling a makefile (make all) Now, when I select debug/Go, I get a error saying No executable to debug. How do I instruct SES to point to my .elf file so that it can be debugged? I have attached a…

To fix the original problem I set the project name within the solution to match the filename of the .elf file

What project? Ozone just opens and uses the .elf file. I didn't change any settings, so I guess it uses default jlink settings. (I did have a look at settings but there is not not change) Anyway, I'm going to give up on Ozone and create another thread…

I'm not sure how this can be a mismatch between BL and application. Like I said, I can debug the .elf with Eclipse and the bootloader remains intact so there is no mismatch (unless I'm mistaken) I attempt to debug the same .elf file with SES and get a…

Hi Nino, Eclipse does not know about the bootloader either... Eclipse is settup to only call "make clean" and "make app_debug" (so no access to compiler/linker etc to my knowledge) the .elf that is generated by the make command is the EXACT .elf file…

I know I'm going a bit off topic with Ozone but I'm pretty sure that Ozone is doing a full chip erase when its flashing the .elf which is trampling the bootloader which resides at the default boot location in flash. I've noticed that if there is no code…

Ok, just gave Ozone a try and my target hit a hardfault immediately upon clicking the attach button. (the same .elf works through Ecplise <<< I shudder every time I type or say the E word) Ozone also complained I needed a valid licence but did allow me…

Thanks for that. I'll give that a try as well. In ozone, will I be able to debug the .elf and have it integrate back to the source code for single stepping/breakpoints etc?

I have a project that is built using a make file. This results in a .elf file being generated. This elf file runs and debugs using Eclipse/GDB (although its a horrible debug experience hence why I want to use SES) I'm trying to debug the .elf using SES…

It will take me a little while to strip out unnecessary/sensitive code. I'll get back to you.