UART communication using nRH52840

[sravich1]

1. I am a newbee to nrf 52840..I saw lot of documents and got confused on where to start ..indly guide me on this
2. we are trying nrf52840 dev kit as we are using nrf52840 in our custom board
3. Let me know how can start for UART communciation using this dev Kit
4. Kindly let me know the procedures
5. Also if I plan to use custom board for this..let me know how we can program for incoming BLE msg to be sent via UART..

Kindly let me know

Thanks and regards

Ravi chandran

[Jared]

Hi there,

I'll be handling this case from now. 

This case has been going back and forth between different problems. Could you now specify exactly what your problem is, and what you need help with? 

regards

Jared 

[sravich1]

Hi jared,

currently I am using nRF52840 development board connected through UART to our custom board .

I used nRF connect APP to test the Bluetooth and was successful in sending data.

1.My question was can we use the same to test using 3rd party App such as Bluetooth terminal??,

I also used nRF2.0 but was not able to connect..let me know on this.

2. Also cuurently I am using SEGGER embedded studio where I am running Baremetal code to run the hex file.

Is there any other flash tool which we can use ??

3. How do I change the UART speed from 115200 to 9600 ..there is #define should I just use this??

4. The development board UART was connected to my USB and this worked fine, to connect to our custom board..Do I need to connect to pin number 6 and 8 to UART of the custom board.??also to change pins should I change in pCA10056.h file ???

Let me know 

Thanks 

Ravi

[sravich1]

Hi jared,

Looks like according to your Guide there is something called as dynamic HWFC handling..so your pin 5 and 7 needs to be disabled I think.Am I correct??..If so how do you do this in hardware kit??

Any suggestion would be good...also the Tx is coming from STM32 for this also to work we need to disable HWFC.Kindly let me know.

regards

Ravi

[sravich1]

Hi jared,

Also I tried with making HWFC false in pca10056.h but connected to pin number 6 and 8.

Then I changed in header file pin numbers to 3 and 4 for GPIO but still did not workpca10056.h

Kindly let me know

regards

Ravi

[sravich1]

HI jared,

Any update on my previous message would help..Kindly let me know.

thanks

Ravi

[Jared]

sravich1 said:

first and second instance same pins..do we need different pins??

Yes, only one peripheral can drive any GPIO at a time. You need to debug your application, and see if the data is received correctly from the STM32 and if that data is sent with ble_nus_data_send() correctly. 

regards

Jared

[sravich1]

Hi jared,

This is the example code under ble_peripheral/ble_uart...I hope this does both sending as well as receiving..we have not changed any code...let me know where do we need to change for seeing this..

also we want ble to be on once it is powered on..currently it is on for few seconds and ble goes off...any flag or any code where we need to enable to run ble all the time...kindly let me know.

regards

Ravi

[Jared]

sravich1 said:

This is the example code under ble_peripheral/ble_uart...I hope this does both sending as well as receiving..we have not changed any code...let me know where do we need to change for seeing this..

also we want ble to be on once it is powered on..currently it is on for few seconds and ble goes off...any flag or any code where we need to enable to run ble all the time...kindly let me know.

The ble_app_uart peripheral example in the SDK acts as a "bridge" between a serial device and a wireless device, in that it receives data over serial and transports it wireless over BLE to the wireless device, and vice versa. It does not supports having two devices connected over serial without modifications. 

The example starts advertising after the initialization routine at the start of main.c. It does not turn it off.

regards

Jared 

[sravich1]

Hi Jared,

we were able to change advertising value which is default set at 18000 to 0 ,then you will have the BLE connected as long it is on...also we were abel to get the Tx and Rx using the App...we will ping you if you further need any help from your side.

regards

Ravi

[Jared]

Good,

I'll close this case then, since it seems that the orginal issue has been resolved. Please create a new ticket for any future issues.

regards

Jared