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.

Stellaris Launchpad does not connect to IAR Embedded Workbench 6.4

Other Parts Discussed in Thread: SW-EK-LM4F120XL, EK-TM4C123GXL

Hi,

I am trying to run  my code on a Stellaris Launchpad (LX4F120H5QR) using IAR Embedded Workbench. I installed the IAR that came with the package (http://www.ti.com/tool/SW-EK-LM4F120XL).

I opened the workspace C:\StellarisWare\boards\ek-lm4f120xl\ek-lm4f120xl.eww

and tried to download the project blinky.ewp onto the device.

But I get the message: Fatal Error: ***ERROR***Unable to open device 0x00000002 Session aborted!

I have both the USB cables connected to my laptop when I download, and the green power LED is on. In the project settings, the device is chosen as LM4F120H5QR and in the Debugger Setup, the driver is TI Stellaris. 

Any help would be appreciated. Thanks,

Eakta

  • Hi Eakta,

    Have you installed the ICDI drivers? If not, you can find the latest version here: http://www.ti.com/tool/stellaris_icdi_drivers.

    You'll need to download and extract the zip file, then go to the Device Manager and update the drivers for the ICDI devices shown (there should be three in total). Point the driver update dialog to manually search in the folder containing the extracted driver files.

    Regards,

    Sam

  • Surely follow Sam's advice. 

    Beyond that - here are screen caps showing our paid IAR. 

    Note - we have/far prefer JLink probe - likely you direct connect via USB - and perhaps IAR has not caught up yet to new icdi on your board. 

    Compare yours against these - known good...  Note: our MCU differs from yours - general set-up should otherwise be of use...

    Doubt you have JLink - select appropriate for your need.

     

  • I have a similar but slightly different and more puzzling problem.

    1. I have an old Stellarise Launchpad (EK-LM4F120XL Kit with LX4F120H5QRFIGA3 chip) and a new Tiva Launchpad (EK-TM4C123GXL Kit with TM4C123GH6PMI chip)

    2. I use IAR Embedded Workbench for ARM, 32K Kickstart Edition 6.60 with standalone permanent license. (Thanks to cb1-mobile's pointer.)

    3. I did install the ICDI drivers (edit).

    4. I cannot use 2.+ 3. to download to neither chips in 1. No error msg is displayed, but Flash contents cannot be changed!

    5. However, I can use 2. to generate a bin file, and use LM Flasher to download that bin file to either chips in 1.

    6. What is more puzzling is, I can now use 2.+3. to debug. This include setting breakpoints, single stepping, etc.

    I can live with this situation. Actually, I kind of like it. But still, it is very puzzling.

  • Thank you Sam. That was the key.

  • @OCY:

    old_cow_yellow said:
    No error msg is displayed, but Flash contents cannot be changed!

    That's disturbing.  Is any form of message flashed/displayed - as this download fails?   And - if you review my screen cap (above) - might the IDE have ticked "suppress download?"  While you, "like the extra LM Flasher step" - does it not delay - and force extra (non-seamless) effort? 

    My sense is that your download should succeed w/your LX4F120 MCU - provided you've followed (above) screen caps - AND have selected (or have) the correct download file.

  • old_cow_yellow said:

    5. However, I can use 2. to generate a bin file, and use LM Flasher to download that bin file to either chips in 1.

    6. What is more puzzling is, I can now use 2.+3. to debug. This include setting breakpoints, single stepping, etc.

     Hi OCW, I fear this is inappropriate for you, I got caught a couple of time:

    debugger set to hardware or simulator? IAR default to simulator.

  • @OCY:

    Unclear if you have & use JLink or route USB cable directly from PC to target board.  Earlier caps - intended for op - covered JLink usage.

    Sure that you know - but (just in case) and to benefit others who may employ IAR w/out JLink - here my best guess of key: Project > Options - settings.

    Note: Below cap shows my switch away from (earlier) JLink to TI Stellaris.  (have not tried - this is my best sense...)  Note the .ddf file - mated to your MCU.  I do not operate the IDE w/that overide default box ticked - did so here to reveal that particular file...

    And following cap reveals that while our MCUs differ - same flashloader file is used.  Again - override default ticked so that filename reveals...

    Somewhere we have that LX4F120 board - although the crippled nature of that MCU discouraged our use.  If these caps don't fix your issue - kindly advise & I'll search/find and perform live test/verify...

  • cb1,

    Thanks. Indeed, I did not set up IAR correctly. I thought that not checking "Supress download" means allow download and "Use flash loader's" means I need something else. I was wrong. This works:

    -- OCY

  • @OCY,

    Good for you!   Sometimes too many options/choices confound.

    The acuteness of your, "issue description" led to this quick solution.

    I'd tick, "Verify Download" (just in case).  Note that you can, "Debug with and without Download." (adjacent,  top right icons)

    The many features of IAR really "bubble up" via a 2nd monitor - if mountain passes allow - that may blip your radar...

  • cb1,

    Yes. I did try "Verify Download" before I checked "Use Flash loader(s)". IAR did not send error or warning even though the Flash was clearly not programmed.

    I also tried "Verify Download" when I checked "Use Flash loader(s)".  IAR did not send error or warning either. In this case the Flash was programmed correctly. (Hence this does not proof that they did verify it!)

    -- OCY

  • That's not good - recall that our group use JLink - and always we receive an in-depth report & verification.

    Might it be the "placement" (w/in Debug Log - usually bottom screen window) which hides/masks this verify? 

    Here's ours...  (small portion)

  • Roberto,

    Thanks.

    I have the habit of using the simulator to inspect the object code to my satisfaction before I switch to use hardware. I am always aware of the simulator is not real. Thus I did not mistake the simulator as the real McCoy.

    -- OCY