• Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 1526 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.

Using Putty not Hyperterminal with the EK-TM4C123GXL on an XP machine

Mitch Funk
Prodigy 40 points

I'm using an old PC with a fresh, updated XP installation.

I couldn't seem to get Hyperterminal to work in the exercises on step 33 of the TM4C123G_LaunchPad_Workshop_Workbook.

I downloaded putty.exe, and it ran steps 34 and 35 without a hitch.

FWIW

  • Guru 86755 points

    Mitch,

        Provide more details on this activity of launchpad workshop workbook or a link. Most people here probably are not familiar with launchpad workshop.

        Regarding your hyperterminal problem, have you configured it correctly?

    -kel

  • in reply to Markel Robregado
    Prodigy 40 points

    I've been working through this link. It is well written and up to date tutorial material:

    http://processors.wiki.ti.com/index.php/Getting_Started_with_the_TIVA%E2%84%A2_C-Series_TM4C123G_LaunchPad?DCMP=tivac&HQS=TM4C123G-Launchpad-Workshop

    The workbook is linked to that page. the link to the workbook:

    http://software-dl.ti.com/trainingTTO/trainingTTO_public_sw/GSW-TM4C123G-LaunchPad/TM4C123G_LaunchPad_Workshop_Workbook.pdf

    but for some reason the link to the workbook doesn't seem to be working just at this moment.

    I used hyperterm as stated in the workbook, and it came back with a 'can't connect' error message. putty seemed to work with xp, so I moved on, but I'm still interested in knowing how to use hyperterm. It usually opens on my machine wanting to set up a terminal session, but even when it defaults to running a serial comm session, it can't seem to connect.

  • in reply to Mitch Funk
    Guru 117855 points

    Mitch Funk said:
    it (Hyper-terminal) can't seem to connect.

    Usually - this results due to "mismatch" between Hyper-terminal's "default" communication settings and those w/in your interconnected MCU.

    Upon opening Hyper-Term click: File > Properties > Connect to > Configure... following should reveal:

    Those 2 highlights are not, "normally/customarily" good matches for your MCU.  "Hardware Flow Control" is the most likely cause for your failure to connect.  Replacing that selection w/ "None" & aligning the other selects -usually gets you, "On the Air."

    Bon chance, mon ami...