Runtime Settings panel missing on Code Warrior DSC56800E v8.2.3

[jmv]

I am trying to download a .elf file without a project, which I have built using the command line tools. When I attempt to run I get a message saying:

'Couldn't find the application to launch to start the debug session. Choose the application to launch in the "Runtime settings" pref panel'. The problem is: I cannot find this panel anywhere. The help file suggests it should be under the Target settings group, but it isn't.

I have set the access paths to point to my source code, link files, etc., and the runtime library.

Code Warrior will download and run an elf file created within an IDE project, so I know the hardware and comms are working OK.

The installed Code Warrior version is DSC56800E v8.2.3.

Thanks

[J2MEJediMaster]

I assume that you're trying to launch the debugger from the command line? If so, what statement are you using to do that?

---Tom

[jmv]

Hi Tom

Thanks for the reply.

No - I am just using File Open menu in Code Warrior and navigating to the .elf file and loading it in. This is what the MC56F8xxx/DSP5685x Targeting Manual tells me, in section Debugging for DSP56800E, section 'Loading an .elf File Without a Project' (pg. 185). When I press the green arrow to start, I get this message. I have changed a number of options so that they look the same as those on a project that builds and downloads OK, but it still doesn't work.

One other question: I have noticed the Code Warrior and command line linkers behave differently with the OBJECT directive in the linker command file. It seems that the command line linker wants .obj, while Code Warrior linker wants .c, like this:

 OBJECT (F_EntryPoint, main.obj) # The function _EntryPoint have to be placed at the beginning of the code
                                       # section for proper functionality of the serial bootloader.


and


 OBJECT (F_EntryPoint, main.c) # The function _EntryPoint have to be placed at the beginning of the code
                                       # section for proper functionality of the serial bootloader.

So it will build without error only in one or the other. I guess Code Warrior used a different linker?


Thanks

[J2MEJediMaster]

I have dragged and dropped an .elf file onto the DSP IDE, and I get a dialog asking me to pick a debugger, and it gives me several choices in a dialog. I'm thinking that the command-line method you use doesn't provide enough information for the IDE to choose a debugger, but then you'd think that it would prompt you for one, like it did for me.

As this point, I'm stumped, and suggest you file a SR on this. Click here to do that.

---Tom