Loading an additional ELF binary

[scottm]

In CodeWarrior it's possible to use the 'target tasks' function to load additional binaries through the flash programming interface.  Is there an equivalent in MCUX?

I'm aware of the 'additional ELF files' option in the debugger's main tab.  (Incidentally, making the user enter a '0' in a text field and click 'generate' is an awful way to implement removing a configuration option.)  The problem here is that I'm loading a bootloader that has memory regions that overlap the application.  The bootloader's ELF file can be loaded standalone, in which case the vector table is needed.  But with an application, it generates a CRC error.

At the moment I'm sidestepping the issue by loading the bootloader with an external tool and preserving the bootloader's memory area, but it's a cumbersome process when switching boards.

Thanks,

Scott

[lpcxpresso_supp]

The P&E probe discovery and connection is basically done by the P&E supplied plugin, rather than the IDE (the IDE simply merges the list of each of the supported types of probe that have been discovered for the user to select from).

We'll therefore need to discuss this with P&E but my suspicion is that this might be related to your use of a networked connection rather than USB.

Regards,

MCUXpresso IDE Support

[scottm]

I'm still looking for a solution to my original problem - I need to load a portion of a second ELF binary.  After the board has been updated using its bootloader (something that happens a lot at this stage in testing) the flash is locked and the programmer has to perform a mass erase, which means that every time I do that I have to fire up PROGACMP again to load the bootloader.

Scott

[lpcxpresso_supp]

So it sounds like you are manually trying to create launch configurations. We do not recommend doing this.

Delete any launch configs from within your project, then use the QuickStart Panel's Debug button to create a new launch configuration for the connected part (you can then modify that afterwards if necessary). For more details, please read the supplied User Guide.

Regards,

MCUXpresso IDE Support

[scottm]

I caught an example of that problem.  I created a new build configuration for a hardware variant and used the blue bug button to try to launch the debugger and got this.  I had to edit the debug configuration manually.

Scott

[scottm]

No, that's how I created the connection in the first place.  But I deleted it and started over for good measure.  (Incidentally, it's confusing to have the quickstart panel launch a welcome screen that's not part of the project - it means the debug launch button and most of the other options get immediately grayed out because the welcome screen is not part of the project.)

Here's what the blue debug button finds:

Now, I believe those two entries represent the two different launchers.  My question stands - what's the difference between the two?

I got the system stuck in a state where it wouldn't connect to the Cyclone the other day.  It kept giving me an error about not being able to auto-detect and to specify the settings on the command line.  I had to switch to a USB connection before it'd work again, and I think that's when I tried switching launchers.

Scott

[lpcxpresso_supp]

What debug probe are you using? The launch configuration settings and available options are specific to the probe.

Regards,

MCUXpresso IDE Support

[scottm]

P&E Cyclone ACP over Ethernet.

Can you explain the difference between the two launcher options?  I get "MCUXpresso IDE PEMicro Interface Hardware Debugging (DSF) Launcher" and "GDB PEMicro Interface Hardware Debugging (DSF) Launcher".  I'm using the GDB option now.  I had a lot of trouble getting it to connect initially.

Thanks,

Scott

[ZhangJennie]

Hi Scott,

I  wonder MCUXpresso doesn't have exact option as CW.

I suggest you refer answer of this thread which should help you.

https://community.nxp.com/message/917515 

Have a great day,
Jennie Zhang

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[scottm]

That only shows how to add symbols for an already-flashed bootloader.  I also don't have those options in my debugger window.

Scott