Stalled Pipe

[DazzaNL]

Hi,

I am using the nRF51 Dongle and every time I send a command the pipeline goes into "Stall" condition. Using USBlyzer I can see that the command is sent but straight away the pipe enters the stall state and I am then unable to read the reply from the device. In order to remove this condition I have to restart the whole laptop, not just simply remove the dongle.

After doing some reading I found that this is often caused by incorrect settings for the start and endpoints of the pipes. Are the start and endpoints set in the Dongle firmware/hardware or can they be set in a driver/config file?

Also, when I go to Device manager I see 3 J-Link devices each with a different MI_0X value, is this normal?

I have loaded the S210 softdevice to the dongle, does this affect any of these settings?

Cheers,

Darren.

[Hung Bui]

@DazzaNL: You have accepted the answer on the case that Kenneth handles. Do you still have any confusion regarding this case ? As Kenneth mentioned the S210 and ANTUSB-m are different and they don't have the same interface.

[DazzaNL]

The original questions I asked here haven't been answered, I still don't know why the pipe stalls and why there are 3 J-link devices identified by windows. If I were to develop my own application, how do I know which device to use out of the 3? How do I know that the stalling pipe isn't a bug in the firmware or that my hardware isn't faulty? I would be trying to solve these issues with my code whereas they may be more fundamental.

Regards,

Darren.

[Hung Bui]

@Darren: Could you take a screen shot of what you have in Device Manager ? Usually you should see only one device (COM port) for each dongle.
(You may need to update the image in your Question since it's not possible to post comment with image).