Question about flashloader files

Hello Nawar

How are you downloading the Software? Are using CCS IDE, LMFlashProgrammer, Uniflash, etc?

Regards
Amit

I am using the IAR software and connecting the board via USB Debugger. Is that what you mean?
Thanks.

When setting up the project within IAR, the correct 'Flashloader' should automatically be selected.

If not, open the project options, select Debugger/Download, and enter the correct path for your MCU. Here an example for a project of mine, for another MCU from a different vendor (project name doesn't matter). Should be easy to grasp the concept ...

Hello Nawar,

OK. That is the first information that is usable. Have you selected TI Stellaris as the debugger?

Regards
Amit

Hello Amit,

Yes, I have selected TI Stellaris as a debugger.

Hello f. m.,

I did this step and here where the problem comes, I need to check the "override default .board file" box and choose the corresponding file! Right? But I couldn't find the file in the folder, I did find many different files but not the one corresponding to my device?

Some people suggest writing a new flash loader file or editing existing one, but not sure if this is the right way?

Thanks

Hello Nawar,

The board file should come with the IAR EWARM installtion. Check for updates to your IAR EWARM.

Regards
Amit

I saw some people on the net talking about writing their own version of the board files, or editing existing ones to match the wanted device. What do you think about that?

Thanks for the hint, I will check for an update too.

Hello Nawar,

I never had to write the board file. The default IAR EWARM when selected with Texas Instruments devices always has the correct set of files.

Regards
Amit

I think Amit is right, usually you don't have to change the preselection by IAR-WB.

For a project of mine, this was: $TOOLKIT_DIR$\config\flashloader\TexasInstruments\FlashLM4FxxxHxx.board

Notice that this is for an "old" LM4C Launchpad, not a new TM4C one.

And we did "override the default", because we had split our project in "safe" and "non-safe" code, placed in separate segments, and protected by the MPU.