Dear visitor, welcome to SEGGER Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.
Hello jcady92,I have the exact same problem! The UART communication through the virtual COM for the J-Link MCU on my NRF51-Dongle fails maybe about 20%. I can receive data from it just fine, but it cannot receive any data from me.
Any solutions?
Hi Yan,Hello jcady92,I have the exact same problem! The UART communication through the virtual COM for the J-Link MCU on my NRF51-Dongle fails maybe about 20%. I can receive data from it just fine, but it cannot receive any data from me.
Any solutions?
We are currently looking into this, we will post here as soon as we have any news.
Regards,
Yan
http://forum.segger.com/index.php?page=User&userID=5289
Hello jcady92,
We are having serious trouble reproducing this on our side.
Could you please provide a few details about your setup?
(GNU/Linux Distribution, J-Link version, firmware string (shown when you start the jlink commander), method of communicating with the UART from GNU/Linux.)
When exactly does the issue occur?
Regards,
Yan
Hi nikpe,Hello again,
I have today identified that my problem was solved when going from the kernel distribution 3.13.0-24-generic to 3.13.0-64-generic.
Your kernel version is printed by typing " uname -r" in a terminal.
I upgraded my kernel by:
sudo apt-get update; sudo apt-get dist-upgrade
I don't know what caused the issue but I can no longer re-produce it.
Does this mean that the issue only occurs right after booting the system?
Quoted
It occurs about 15-20% of the time when booting the system.
Hi Yan,Hi Jay,
Unfortunately we do not have a PCA1003, but we have a couple of PCA10000 dongles.
Would this also work?
Also we only have Raspberry Pi V1, but I assume the application would work on that as well.
A test program would be much appreciated.
There is only one thing which is not quite clear to me, you write:
Does this mean that the issue only occurs right after booting the system?
Quoted
It occurs about 15-20% of the time when booting the system.
Or does this mean that there are cases where the issue does not occur at all unless you re-boot?
This seems to be an entirely different issue from what Niklas experienced.As for the 15-20% question: The issue occurs right on boot of the system. For example, say you boot the system, communicate over serial, then power down the system and boot again. Repeating this say 10 times, serial communication should fail one or two of those times. It's not an exact science, but when the communication does fail, it will not work until the system is rebooted or the serial device is physically unplugged and plugged back in. Then it works properly.
This post has been edited 1 times, last edit by "jcady92" (Sep 11th 2015, 3:15am)
There are newer versions available for this firmware. Did you install the newest official package from https://www.segger.com/jlink-software.html ?
Quoted
PCA10000: SEGGER J-Link OB-SAM3U128 V1.00 (2014 Nov 28 10:24)
This post has been edited 1 times, last edit by "SEGGER - Yan" (Feb 8th 2016, 3:24pm)