I am using HC-05 bluetooth module and STM32F407. I have to enter AT Command Mode and send some AT Commands. Normally, i do it pressing button on the module. But i have to enter AT Command Mode using only software. I can enter AT Command Mode, but i can't send any AT Commands to module. I tried to change the name of the module but it didn't work.
Here is my try. Where is my mistake?
/* USER CODE BEGIN PV */
/* USER CODE END PV */
static void MX_USART3_UART_Init(void)
HAL_UART_Transmit(&huart3, (uint8_t *)data, strlen(data), 2000);
>>Where is my mistake?
Perhaps some place else..
There is a lot of other code involved in getting the interface and peripheral set up, and some expectations about baud rates, connectivity and responses.
Not good with embedded? Try connecting to a PC terminal via a USB-to-CMOS Serial adapter and walk through the sequences and interactions so you understand them properly.
Does the HC05 expect <CR> <LF> or just <CR>, have you even got the order correct in your string? Remember also sprintf() returns the length.
HAL_UART_Transmit(&huart3, (uint8_t *)data, sprintf(data,"AT+NAME=charles\r\n"), 2000);
What response do you get from the radio? If you leave the output side connected to the USB-to-CMOS Serial adapter you could watch on the PC.
How do other people approach debugging these things? Using scopes or logic analyzers? Understanding what the expectations of the hardware are, and meeting them.
Westonsupermare Pier said:If you leave the output side connected to the USB-to-CMOS Serial adapter you could watch on the PC.
If you have two USB-to-CMOS Serial adapters (or a double adaptor) you could monitor both what the microcontroller sends and what the radio replies:
View all questions in Keil forum