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]

Hi Darren,

Could you let me know more about the set-up you trying to make ?

Which application did you flash on the chip besides the S210 softdevice dongle ?

How do you want to control the dongle from the PC via USB ?

[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.

[Hung Bui]

Hi DazzaNL,

The nRF51 Dongle is quite different from the ANTUSB.m dongle.

The S210 won't handle any command from the USB port. The S210 provides an ANT stack that the application programmed on the chip can use to set up to transmit and receive ANT package.

The USB interface on the dongle mainly works as an USB-COM port. And if you want to control the dongle from PC you would need to develop your own application that receive command from UART and then process that command to transmit or receive ANT packet.

I would suggest you to follow the quick start section here. You can try the broadcast example that you can use ANTUSB-m to verify that the nRF51 dongle broadcasts something.

[DazzaNL]

Hi,

Thank you for your reply, although I must admit to being a little confused. The documentation for the S210 is almost exactly the same as the one for the ANTUSB-m, leading me to think that it was effectively the same thing.

I have worked through the examples in the past but none of them allow me to do what I need. If I have the Bike S&C example on the DK board what do I need to have on the Dongle to receive the data?

Ultimately I need to be able to configure 8 channels (from LabVIEW) that will connect to 8 different DK boards that will be running the same software, except for the channel numbers. If this is easier to implement on the ANTUSB-m then I will use that but surely it is also possible on the dongle without significant coding?

Thanks again for your help.

Darren.

[DazzaNL]

Also, I asked this question some days ago. When I did the first project I used HEX codes to communicate with the ANTUSB-m, so for example to assign a channel would be something like "A4 04 42 00 00 00 00 E2" and this worked really well. These HEX commands are all listed on the documentation for the ANT Stack under the S210 documentation. This is the cause of some of my confusion as to why it doesn't work.