[Qinheng RISC-V core CH582] 6 BLE_UART routine evaluation

kit7828

[Qinheng RISC-V core CH582] 6 BLE_UART routine evaluation [Copy link]

 

There is a BLE_UART routine in Qinheng's BLE routine, and it is rare to see the file

txt file in the folder

There are very few explanations of the routines in the entire Qinheng routines, so I also hope that Qinheng officials can add corresponding instructions to the demo routines to facilitate evaluation and learners.

BLE programming is relatively complicated due to the protocol. To be honest, if it weren't for the pressure of evaluation or product development, I probably wouldn't have bothered with it for a long time.

The BLE demo is compiled and downloaded to the development board. Unlike previous routines, the download and verification time is much longer.

After downloading, connect to the serial port

At this time, open the BLE debugging assistant on the mobile phone (refer to the previous evaluation routine, [Qinheng RISC-V core CH582] 5 Bluetooth routine initial evaluation and environment construction )

You can see ch583_ble_uart, after connecting

The serial port displays the above information, while the mobile app displays the following interface

This assistant tool can send and receive, but only the one at the bottom can be sent

The receiver can read the corresponding information by clicking the corresponding read button.

Device Information Here you can basically read the string information

There is only one person sending the message

After receiving the information, the serial port will prompt that the length information has been received

BLE RX DATA len:7

After a slight modification in the code, the received information can be displayed.

For testing convenience, only string information is processed

case BLE_UART_EVT_BLE_DATA_RECIEVED:
            PRINT("BLE RX DATA len:%d\r\n",p_evt->data.length);
            char * str = p_evt->data.p_data;
            str[p_evt->data.length] = 0x00;
            PRINT("BLE RX DATA:%s \n",p_evt->data.p_data);
            //for notify back test
            //to ble
            uint16_t to_write_length = p_evt->data.length;
            app_drv_fifo_write(&app_uart_rx_fifo,(uint8_t *)p_evt->data.p_data, &to_write_length );
            tmos_start_task( Peripheral_TaskID, UART_TO_BLE_SEND_EVT,2);
            //end of nofify back test

            //ble to uart
            app_uart_tx_data((uint8_t *)p_evt->data.p_data,p_evt->data.length);

            break;

In this way, the specific string received can be printed

It is also a more detailed test of the evaluation

After processing the received character information, Bluetooth control should be possible.

void app_uart_tx_data(uint8_t *data,uint16_t length)
{
    uint16_t write_length = length;
    if(strcmp(data,"LED1 ON"))  HAL_TURN_ON_LED1();
    if(strcmp(data,"LED1 OFF"))  HAL_TURN_OFF_LED1();
    app_drv_fifo_write(&app_uart_tx_fifo,data,&write_length);
}

In this way, Bluetooth can control more.

At least I will try GAPRole and GATT programming when I have a little more free time at work in the future.

Jacktang

Qinheng's official website does not explain much about the BLE_UART routines of CH582

lugl4313820

You are so proficient in mastering Bluetooth. Thanks for sharing. It’s been a pain. I look forward to more elegant works.

yaoquan5201314

After learning this, I think this idea is good. I will refer to it and learn to modify the code to control the transmission of sensor data in a couple of days.

WCH_Risc5

Thanks for the suggestion, we will consider adding more comments.

kit7828

lugl4313820 posted on 2022-4-9 18:43 You are so proficient in Bluetooth. Thank you for sharing. I look forward to more elegant works.

Thanks for the encouragement. I always feel that GATT is too difficult to learn.

kit7828

WCH_Risc5 posted on 2022-4-11 13:52 Thanks for your comments, we will consider adding more comments.

Thank you, I will definitely give it a good review