This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Dialog box that shows "Get Alternative File" when running Blinky in debug mode

Other Parts Discussed in Thread: UNIFLASH

Hi all,

I am new to the launchpad but not really new to the Cortex M family since i have done a couple of projects in STM32F4 using Keil. So please bear with me..

I find using the SFLASH a bit weird since i was used to having an in built Flash in the uControllers and having an external flashing tool to save into the SFLASH mem was kinda new. And i had no idea what the SOP jumpers were for. I was lost for 1 full day(yes, 24 hours) but this forum saved me. This forum really provides a wealth of info.

I seem to encounter this problem only during debugging mode. IAR flashes a dialog box as such. The thing is i have no idea why the path points to the mentioned directory.. Ignoring the messsage allows me to step through but sometimes somewhere down there will be another pop up with a path pointing tp cpu.c file.

I am able to download to SFLASH using UNIFLASH(SOP jumper on and then removed) and run in SRAM(exiting debug w/o pressing the reset button) with no problem. The 3 LEDs blink.

However this massage annoys me when i debug. I can skip it but that's not the point... Any help is appreciated..

  

 

  • I figured out what the problem is.. Might be useful for those who might encounter this in the future..

    You will need to open up the driverlib.ewp project clean and recompile the driverlib.a archive library. Then from the IAR linker, readd the freshly compiled driverlib.a That should refresh the path. You can then reference the driverlib.a file from the original driverlib.ewp Release\Exe folder or simply copy it to your present Blinky directory..

    Open Options and go to the Linker Tab.. as shown below..

    All should be fine..no more weird pop-ups not finding smth while debugging...

     

  • Hi Fadleen,

    Thanks for the Update.

    As you have noticed these are notification messages are related to source path resolution when the static library is compiled on the different system/path. Recompiling the library resolves this.

    Regards,

    Ankur