Hello.
EDIT: When I connect to nRF52832, Windows are not creating bluetooth serial com port. And Bluetoth Services are not getting.
How Can I do this??
Thanks.
Hello.
EDIT: When I connect to nRF52832, Windows are not creating bluetooth serial com port. And Bluetoth Services are not getting.
How Can I do this??
Thanks.
Hello Gökhan,
I'm afraid it will be little bit complicated, because what you see on nRF5x DK COM port (part of mbed/SEGGER USB driver) is exactly the same as you see (over FTDI "TTL serial to USD" cable) on nRF5x UART PINs. The SEGGER J-Link MCU on the dev kit actually listens to the same PINs (on PCA10040 it is P0.05-08) and provides equivalent service as FTDI cable.
If you want to use one UART interface to transport data from PC (or other host) to nRF52 DK and another UART to transport it independently out (and connect it by e.g. FTDI cable to another host) then you need to write this secondary UART "instance" inside your application and assign different PINs to it. And because nRF52832 has only 1 HW UARTE peripheral (see more details here) then you will most probably need to use some SW implementation with bit-banged GPIO lines. This can work until you will have only these two UARTs in the project btu you can experience problems if you would use it with BLE stack and ongoing connection...
Cheers Jan
What do you mean by "my SDK" ? You meant DK ? My understanding is that you want to simply forward UART packet from one comport to another comport on the same computer (no BLE involved here) ? The easiest is to cross connect TX and RX, then you have it, you don't even need the nRF52.
If you want to have the nRF52 so you can process the data, you have to write your own code to switch between UART pins, and it may not be full duplex as only one UART can run at a time.
What do you mean by "my SDK" ? You meant DK ? My understanding is that you want to simply forward UART packet from one comport to another comport on the same computer (no BLE involved here) ? The easiest is to cross connect TX and RX, then you have it, you don't even need the nRF52.
If you want to have the nRF52 so you can process the data, you have to write your own code to switch between UART pins, and it may not be full duplex as only one UART can run at a time.