• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 31 subscribers
  • Views 635 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

UARTStdioInitExpClk not working in EKS_LM4F232 hello example

John Osen
Genius 3585 points

UARTStdioInitExpClk do not work.

I am using the hello example as a starting point in learning CCS.  Is the virtual com port limited to 115200?  I do not see any limitation in the EKS documentation.

(Is there an easy way to paste from CCS to this window?  This applet brings up a window that takes about fifteen seconds to paste into it then insert into this window.  Messiest interface I have ever seen.)

My first change was to set the 115200 baud to 57600.  It did not work.  I stepped into UARTStdioInitExpClk (I will call it 'that function' from now on to avoid pasting or typing it out).  The arguements initially were set into R0 and R1.  The first lines of that function call another function that clobbers R0 and R1.  After changing some compiler setting, I get the arguements of that function to be saved in probably the stack.  So when I finally do get to MAP_UARTConfigSetExpClk (which I will call 'that other function'), things get screwed up.

Should I not be able to change the baud rate in this example?

  • 0
    TI__Mastermind 18905 points

    John,

    The virtual com port is facilitated by the ICDI portion of the board that is primarily for JTAG emulator.  I believe the firmware in the LM3S3601 for the IDCI expects 115200 baud rate.  I will verify this with the software engineer that wrote the firmware, and follow up.

    Lela 

  • 0 in reply to Lela Garofolo
    TI__Mastermind 18905 points

    John,

    I have verified with the software engineer that the ICDI is hard coded to 115200 baud and this is most likely your issue.  An update has been done to the firmware that is in the ICDI and is available on the web. 

    Download the latest version of LM Flash Programmer at www.ti.com/lmflashprogrammer version 1381.  On the "other configurations" tab there is a (new) button, ICDI update.  If you click this button it will automatically load the latest version of the firmware for the Stellaris ICDI.

    Please let me know if you any issues.

    Lela

  • 0 in reply to Lela Garofolo
    Genius 3585 points

    Actually, that did not work out so well.

    I downloaded the new app and then started it up.  At about the time I started the app, I got a "tried and failed to load new HW" dialog.  I should have grabbed a screen shot.  I then tried to load the new FW, but the load failed.  Restarting my computer did not help.  Now the Texas Instruments XDS560 PCI JTAG Emulator cannot start (Code 10) and CCS will not connect to the EKS.   I removed the XDS560 HW.

    The EKS is running the last program loaded.

    I looked like the update bricked the JTAG emulator.  Fortunately power cycling the EKS fixed the bricked issue and I am back working.

    There is no evidence that anything happend toward updating the ICDI.  It appears that the XDS560 PCI JTAG Emulator HW driver is unnecessary.  I do not know when it was installed.

  • 0 in reply to John Osen
    TI__Mastermind 18905 points

    John,

    You should not have gotten that message.   Whatever has gone awry, don't worry.... I doubt you have rendered your ICID or JTAG useless.  Most likely the issue is due to a windows driver either not installed/not properly installed or there is a power issue. 

    One quick note, the XDS560 does not support Stellaris Cortex-M devices, so this is why your XDS560 is not working.  Only XDS100 supports stellaris.

    Couple questions to figure out what the issue is:

    How are you powering the EKS?  ICDI or OTG?  Either method of powering the board will work for updating the firmware, just make sure you have the J6 jumper in the proper place  and the POWER led is on. 

    Have you looked at the hardware device manager?  What OS do you have?  Windows 7?  I've seen issues with installing the Stellaris DFU and JTAG window drivers on windows 7.  Typically a reinstall fixes it.  Look at your device manager to see if the drivers are there and if there are issues reported for the device status.

    Lela

  • 0 in reply to Lela Garofolo
    TI__Genius 10190 points

    Hi Lela,

    According to the post XDS560 is not supported on LM4F.  Yet the Wiki indicates compatibility:
    http://processors.wiki.ti.com/index.php/Stellaris_Emulator_Compatibility

    Which is correct?  I've been using the JLink which works great.

    Thanks,
    Mark

  • 0 in reply to Mark Ackerson
    TI__Mastermind 18905 points

    Mark,

    The wiki page is incorrect.  I do not know who created the wiki; it was not done by the Stellaris group. I am in the process of having it taken down, as most of the information is incorrect. 

    Please note that you may also find a third-party tool vendor to claim to "support" Stellaris devices.  However, there is a difference in how a third party tool vendor and a MCU group defines "support."  I have no doubt that if the right engineering efforts were put in place that a XDS560 would work with a Stellaris device, however, that has not been done.  To my knowledge, there are no future plans to do so for the XDS560. 

    XDS100v2, J-Link, U-Link, and Stellaris ICDI are all supported and verified to work by the Stellaris group.

    Lela