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.

[DazzaNL]

Hi,

I am trying to communicate with the Dongle as a USB RAW device from LabVIEW. I have previously done the same thing with an ANTUSB-m device but now I want to expand my application further. For testing purposes I am using the Bike S&C application on the nRF51 DK board to test the setup.

I have only placed the S210 onto the dongle, my understanding is that this will allow me to send my own HEX commands the same as for the ANTUSB-m. Is this true?

Cheers,

Darren.