pc-ble-driver not working with my BT832X

[MOHAMED AHMED ALI MAHMOUD ELSABAGH]

I have been working on this for very long time but I can't figure it out, I am trying to use pc-ble-driver to connect my Ubuntu/Raspberry pi to by BT832X module over UART

I tried flashing the pre-compiled hex file version, from the github repo, and I connected my FTDI USB to UART from my Ubuntu machine to BT832X and I can see the data being sent from my PC on the logic analyzer, the problem is I can't see any response from the nrf52832.

I then tried to debug the connectivity firmware line by line on Keil, and I found that the nrf52832 really get the right characters on the UART line but I am not sure why it doesn't send back any response, this is very urgent matter for me so any help would be appreciated

[Stian Røed Hafskjold]

Which github repo are you referring to?

Can you try out Jørgen's answer in this thread? https://devzone.nordicsemi.com/f/nordic-q-a/18984/pc-ble-driver-py---sd_ble_gap_sec_params_reply-fails/73378#73378

Can you also check flow control settings? I know we had some issues with this using the JLink USB bridge we have on our developments kits in Linux. The CTS/RTS line was floating. Can you try to pull these lines low manually?

[MOHAMED AHMED ALI MAHMOUD ELSABAGH]

I am referring to this repo https://github.com/NordicSemiconductor/pc-ble-driver I am not using Jlink in connection I am just using a normal USB to UART FTDI chip to connect my Ubuntu and BT832X (nrf52832), and I am not getting error (0x03), when using the python wrappers I am getting (0x13) which means I am not getting any response but I am able to connect to the USB to UART

in ser_config.h I already changed those line

```

/** UART transmission parameters */
#define SER_PHY_UART_FLOW_CTRL NRF_UART_HWFC_DISABLED
#define SER_PHY_UART_PARITY NRF_UART_PARITY_EXCLUDED
#define SER_PHY_UART_BAUDRATE UART_BAUDRATE_BAUDRATE_Baud1M

```

so I the hardware flow control should be disabled, I am using the UART connectivity example not the HCI, and from the C example I am running at 1M baudrate which should be same as the nordic according to above settings

I also tried to pull CTS/RTS to ground manually but with no luck

[MOHAMED AHMED ALI MAHMOUD ELSABAGH]

I notice something strange according to this page here https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v12.0.0%2Fser_phy_uart_page.html&cp=4_0_0_3_2_2_2

and https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.sdk5.v12.0.0%2Fser_phy_uart_hci_page.html&cp=4_0_0_3_2_2_3

the first 2 bytes are the header and they contains the length of the payload bytes, and from my logic analyzer this is the sequence of bytes sent from the python script on UART

0xC0 0x00 0x05 0x00 0xFB 0xC0, ...

so does this means that the upcoming bytes for the first command is 192 bytes, because the python library is definitely not sending 192 bytes but is sending 4 bytes in the payload, so maybe that's why the nrf52 is not responding