STEVAL-25R3916B USB Mode not identified

[majidsurefow]

Hello,

I recently purchased the STEVAL-25R3916B board and it functions correctly with the out-of-the-box demo. However, I’ve been unable to get it working with any of the available software tools, such as the ST25R3916 Discovery GUI or ST25-PC.

I’ve confirmed that JP14 is correctly configured, the board is set to USB mode, and I’m using the correct USB port as per the documentation. Despite this, the software does not detect the board.

From what I’ve seen in the forums, this appears to be a recurring issue, but I haven’t come across any clear or official resolution.

Any assistance or guidance would be greatly appreciated.

[Brian TIDAL]

Hi,

please confirm that:

- the following message is displayed on the screen:

- the USB is connected on "MCU USB" (type B connector):

- JP14 and JP13 are in the position indicated as red on the picture

- your USB cable is not defective (please test the cable) 

- you can see USB input device with the following VID/PID in the device manager:

Rgds

BT

[majidsurefow]

Dear Brian,

For starters, I would like to extend my thanks for your prompt response. I can confirm that all of the specified requirements are met as:

1- USB connections and jumpers were done correctly:

2- USB Device is identified as you have shared, but none of the apps can use it.

3- I have tested using multiple cables, and the problem seems to persist. I have also tested the product on a different computer, but the state is the same.

What can be the issue?

On another note, I would like to also connect the NFC Reader separately to a different microcontroller, and I cannot seem to find any documentation that could help me setup the correct connections (for powering it up) and communicating through i2c or SPI.

To power it up if S100 is set to 5V or 3.3V:

assuming its set to 5V:

- should I connect 5V to VBUS on J102, and GND to the same GND on j102?

assuming the switch is set to 3.3V:

- should I connect 3.3V to 3V3 on J101?

your help is greatly appreciated. 

Thanks.

[Ulysses HERNIOSUS]

Hi, 

you checked already pretty much everything. Which leaves me puzzled. Last time such issue was resolved by moving from a power-only USB cable to a data USB cable. But the device is even enumerated in your case....

1. What is the Windows version you are using? Which architecture?
2. Can you keep the GUI open and observe output while resetting the board and putting back into USB mode? (AFAIK some log messages about device detected should appear)
3. I presume you were using a different PC with basically same company applied restrictions. Can you try this on a completely different PC (private one?) This should give us hints if the issue is with the board or somewhere else.

BR Ulysses

[Brian TIDAL · Accepted solution]

Hi,

regarding your questions about the connection another MCU:

• the schematics of the 2 boards are available in STEVAL-25R3916B SCHEMATIC
• the 3V3 is needed to
  • supply the VDD_IO (mandatory)
  • pull-up the I2C SCL and SDA in case of I2C
  • supply the LED101 (3V3 PWR_ok LED)
  • optionally provide the V_RF to supply the VDD and the VDD_TX in case S100 selects 3V3
• 3V3 must be connected on J101.8
• VBUS is optionally used to provide the V_RF to supply the VDD and the VDD_TX is case S100 selects 5V. 
• if S100 selects 5V, VBUS (5V) must be connected to J102.2
• The J101.3/7/11/14 and J102.4 pins are all connected to GND

Regarding the USB problem, can you check that the micro USB connector has not ben damaged?

Rgds

BT

[majidsurefow]

Dear Ulysses,

Thanks for your reply. After testing the module with a non-company PC, the USB mode functionality works as expected. It seems that the issue was a company group policy or something of similar nature.

Thanks for your timely help and support. 

[majidsurefow]

Dear Brian, 

Thanks for your reply.

The issue regarding the USB connection was fixed as it was due to some unexpected restrictions on the company's PCs. I will try to test the connection with a different MCU, and will likely seek your support in the near future.

Thanks for your time and efforts. 

[Ulysses HERNIOSUS]

Hi, 

thx for the feedback. I am actually surprised that I was right. To date I have not experienced USB HID input devices to be affected by group policies. 

If you happen to find out more about this together with your IT, then please provide hints what to watch out for in Windows settings/policies.

Thx, Ulysses