This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ULink not working with uvision4

Working with ULINK2 in keil .After configuring all the settings in Debug .It is not displaying automatically the device id,no etc.JTAG Device chain is not blank .. what should be done?

Parents Reply Children
  • Hi,

    > i am using LM3S6918 Cortex M3

    hmmm ... the LMI (now: TI) LMxxxx devices like to lock themselves the debug port "for no reason" ... (I do not know, why, but I had this problems with the LM3S6/8x devices, and also with a LM... Ethernet MCU).

    If you have a LMI Demo Board, please go to the LMI website and download the LMI Flash Programming tool: (you must register to download the tool, but it does a great job)

    www.ti.com/.../lmflashprogrammer

    The Tool provides some TABs for various jobs to do. The last TAB provides the LMI unlocking. You will need the original FTDI JTAG connection for the Board.

    !!! ALL FIRMWARE ON THE LMI MCU WILL BE DELETED !!!

    Click on "Other Utilities" (last TAB) and select "Sandstorm Devices" (I guess LM3S6918 is Sandstorm, or probably Fury/DustDevil). Then click on "Unlock".

    This erases the device and makes the JTAG/SW Port avaiable again, if it was locked.

    ---
    Also please be very careful when setting up the clock tree for the Chip. With an invalid clock setting (i.e. Clock divider = 0) you can send the chip to silicon hell ... forever ...

    ---
    If this does not help, we must continue searching for a proper solution...

    .
    BR,
    /th.

  • thank you for your reply i will try in flash programming .But is there any other way in keil

  • Hi,

    > But is there any other way in keil

    The ULINK2 does various things trying to connect to the MCU. You can test the Connect Settings for the ULINK driver, play with
    Connect: Normal / under Reset / pre Reset
    Reset: Autodetect, HW, SYS and VECT

    The ULINK also tries internally to connect, but if the device decides to be locked our debugger has no chance.

    The LMI Flash Tool does some "crazy pin-toggling" sequences with the FTDI-JTAG to bring the MCU back to live. When I was working with the first unlock tools, there were several possibilities to go through - I think now they packed them all together and try them through...

    .
    Please try this tool if it solves your problem. And please write a note here even if you succeed.

    .
    BR,
    /th.

  • it is working.Now i want to program graphics LCD.Help needed