• State Verified Answer
  • Locked Locked
  • Replies 15 replies
  • Subscribers 25 subscribers
  • Views 400 views
  • Users 0 members are here
Attachments (4) Download All
Nordic Case Info
  • Case ID: 288757
Options
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

Issues with shell not echoing / buffering input characters

user111592

Greetings.

We are using the zigbee/shell sample in order to verify the connectivity of some other devices running the zigbee stack. While the shell sample had no issues in the past (circa tag v1.8.0) now we see a odd behavior in which the characters inputted in the terminal emulator (gtkterm) appear "delayed" by one character. We tried rolling back to v1.8.0 as were using the 1.9.1 tag in case that was the issue but the problem persisted. As such we do not fully know if the problem resides in the sdk, zephyr or our machine

As an example:


-checkout v1.8.0


-download shell sample


-open gtkterm and connnect to tty/ACM0


-press reset button on the board, board sends the opening message (*** Booting Zephyr OS build v2.7.99-ncs1-1  *** followed by  uart:~$ )


-press the "a" key, the character "a" appears on the screen


-press the "b" key, the character "a" appears on the screen


-press the "c" key, the character "b" appears on the screen


-press the "enter" key, the character "c" appears on the screen


-press the "d" key, the "enter" is parsed and the device replies with "aabc: command not found"

-press the "e" key, the character "d" appears on the screen

And so on and so forth, this makes it very difficult to employ the shell sample for verifying our devices.

  • 0 in reply to user92402

    Hi.

    We had not tried to program the DK with another computer.
    Furthermore, after updating nrfjprog, downgrading jlink and trying on the DK's USB with the project you've given us, the problem does not appear to present itself (although it took a couple presses of the reset button before gtkterm stopped appending garbage characters (like "[1;32m" and "^[") after uart:~$, characters that were intepreted by the shell as (obviously incorrect) commands)

    We will try with the updated nrfjprog / downgraded jlink to see if our normal build of the shell sample keeps manifesting such problems, as well with our normal build modified to route the shell output to USB

    Addendum/update: trying to use the shell sample in the nrf SDK with the updated nrfjprog/downgraded jlink still caused the same issue on gtkterm (to note: this is the same sample that originally displayed the problem, i suppose this excludes the possibility of nrfjprog/jlink being the source of the issue?)

    I am attaching a zip file with our shell sample, even though it should be the same as the one in the SDK

  • +1 in reply to user111592

    Hi,

    I have asked my colleagues, but besides the one I mentioned previously no one else has seen this error or are able to reproduce it. 

    Since the issue does not present itself when using nRF USB it might be an issue with the firmware on the interface MCU, so you can try uploading new firmware.

    1. Download the JLink interface MCU firmware from nRF52833 DK > Downloads.
    2. Unplug the DK from the computer.
    3. Hold in the IF BOOT/RESET button on the DK while plugging it in, and keep it pressed until LED5 starts to blink to make the device enter bootloader mode.
    4. The device should show up as BOOTLOADER.
    5. Drag and drop the firmware image into the DK.

    Best regards,

    Marte

  • 0 in reply to user92402

    Hi.

    Apologies for the late answer, we've just tried what you suggested. Now the DK prints to UART the following string when we press the reset button:
    *** Booting Zephyr OS build v2.7.99-ncs1-1 ***
    Though it doesn't print anything else. Where do we go from here exactly?

  • 0 in reply to user111592

    Hi,

    Make sure you have v7.58b of JLink, then try to flash the Zigbee shell sample to your DK again.

    Best regards,

    Marte

  • 0 in reply to user92402

    Hi.

    We did as told and all that happened is that now we cannot send commands via gtkterm. We only see uart:~$ and nothing more, pressing keys on the keyboard doesn't seem to send or echo anything


    EDIT: after flashing and then inserting the JLink interface MCU firmware it now behaves as expected.
    Thank you.

Related
Terms of service