Can't send AT commands using TeraTerm

Home › Forums › mDot/xDot › Can't send AT commands using TeraTerm

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • September 9, 2016 at 7:37 am #14727
    Minh Nguyen
    Participant

    Hi everyone,

    I am following the mDot start guideline and trying sending some AT commands.
    I have already updated the firmware (the newest mdot-firmware-1.0.8.bin) flow the guideline at http://www.multitech.net/developer/software/mdot-software/mdot-firmware-upgrade/
    At step 9, I opened TeraTerm and set as the figure:
    TeraTerm setup

    At that time, nothing happend even I tried to enter some command from terminal. After I pressed the Reset button on the Developer board, the terminal screen display like this:
    and I still can not issue the commands.
    Do you have any idea for this problem?

    Thanks

    P/S: Sorry, I don’t know why my image not appear by using img tag. These are the links to images
    https://postimg.org/image/i3xjlz3bx/
    and
    https://postimg.org/image/3qnxif8el/

    • This topic was modified 8 years, 2 months ago by Minh Nguyen.
    • This topic was modified 8 years, 2 months ago by Minh Nguyen.
    • This topic was modified 8 years, 2 months ago by Minh Nguyen.
    • This topic was modified 8 years, 2 months ago by Minh Nguyen.
    September 9, 2016 at 8:59 am #14732
    Leon Lindenfelser
    Moderator

    Hi Minh,

    It looks like you are trying to issue commands on the debug port. Are you using a MultiTech developer card? Assuming you are, there are two ports that should enumerate. For AT commands, use the one that displays in teraterm as “COMxx: XR21V1410 USB UART”.

    Leon

    September 9, 2016 at 10:14 am #14734
    Leon Lindenfelser
    Moderator

    To clarify, what I stated above is true for the MDK board.
    http://www.multitech.com/brands/micro-mdot-devkit
    For the UDK 2.0 board…
    https://developer.mbed.org/teams/MultiTech/wiki/Using-MultiTech-UDK-for-mDot-Dev
    you will issue commands via the 9 pin serial connector.

    September 9, 2016 at 10:36 am #14737
    Minh Nguyen
    Participant

    Hi Leon,

    Thank you so much for your response.
    I am using UDK 2.0 board
    https://postimg.org/image/e23yfzaa3/

    When I start the TeraTerm, there are two ports of UDK are recognized: COM5 and COM9 (maybe, as you said, one for debugging and another for AT commands)
    https://postimg.org/image/5hhzar8tx/

    However, I have tried both these two ports, but I could not do with both of them
    https://postimg.org/image/xi2ha03h1/

    I set it up as the guideline at http://www.multitech.net/developer/software/mdot-software/mdot-firmware-upgrade/
    Did I miss any other needed setting?

    Thanks
    Minh

    September 9, 2016 at 10:51 am #14738
    Leon Lindenfelser
    Moderator

    My error… COM 9 is the AT command port. Looks like the issue is that your mdot is in serial data mode. You need to escape that mode to send AT commands. Press the reset button on the UDK board and immediately send it +++ upon reset. Timing is tight so it may take a few tries to get it out. You can send more than three +’s but it needs at least three.

    September 9, 2016 at 11:29 pm #14742
    Minh Nguyen
    Participant

    Hi Leon,
    Does “send it +++ upon reset” mean typing “+++ Enter” on terminal screen?
    I tried, but I could not even enter any character.

    Thanks,

    • This reply was modified 8 years, 2 months ago by Minh Nguyen.
    September 10, 2016 at 8:08 am #14745
    Jason Reiss
    Keymaster

    As Leon said the timing is tight.
    I usually just hold the ‘+’ key down and press the reset button on the device a few times when resetting manually.

    If it is automated I would reset, wait 0.2 sec, reset, wait 0.8 sec, and send +++

    March 16, 2018 at 3:47 pm #22864
    John Greene
    Participant

    After doing the above, I get:

    [ERROR] File from flash wrong size. Expected 256 – Actual 128
    [INFO] mDot Ready

    I am still unable to type anything into the tera term terminal, though. Any ideas?

    March 16, 2018 at 4:38 pm #22865
    John Greene
    Participant

    To add to my last post on this thread, the port that appears when I plug in the USB from the UDK is described as “STMicroelectronics STLink Virtual Com Port (COM5)” which we used to update mDots on a custom board via the 9-pin programming configuration. I have tried to disable and uninstall both the device and driver but for whatever reason the same description keeps appearing and am still unable to get tera term to respond.

    One other item of note: the device itself is being recognized in some fashion as a popup appears with “Multitech” described as the storage device on the D:\ drive.

    March 17, 2018 at 12:28 pm #22866
    John Greene
    Participant

    Please disregard above as I figured out that a second connection from the UDK’s DB9 connector was necessary to send the AT commands to the mDot.

  • Author
    Posts
Viewing 10 posts - 1 through 10 (of 10 total)
  • You must be logged in to reply to this topic.