Nrf51822 and STM32 uart bootloader problem

RE: Nrf51822 and STM32 uart bootloader problem

bjorn-spockeli — Tue, 26 Nov 2019 02:26:04 GMT

OK, the nRF51 is limited to the 1Mbit Phy of Bluetooth, so the throughput is limited to 149.2 kbps. However, the actual throughput will depend on the features supported by the ESP32 as it is the BLE master. I am afraid that we cannot provide a lot of support for issues on non-Nordic ICs.

RE: Nrf51822 and STM32 uart bootloader problem

Folny — Sun, 24 Nov 2019 13:44:54 GMT

I only use Rx Tx pins I tried to increase the bit rate to 115200 but that's not a big difference, I feel the problem is in the code for ESP32.

RE: Nrf51822 and STM32 uart bootloader problem

bjorn-spockeli — Fri, 22 Nov 2019 08:45:46 GMT

The nRF51 supports higher baudrates and I guess the STM32 does as well, so you can try to increase it to 115200? Are you only using TX/RX lines or are you using Hardware flow control (i.e. CTS/RTS) lines in addition?

Best regards

Bjørn

RE: Nrf51822 and STM32 uart bootloader problem

Folny — Thu, 21 Nov 2019 15:51:30 GMT

Yes today I just tried it and it worked, I used the character '\ r' in the code ble_app_uart and in the code for STM32 and I had to modify the application for Windows to work it speed uart I set to 57600. This time, but the problem at 16kb bin file uploads too long about 4 minutes.

RE: Nrf51822 and STM32 uart bootloader problem

bjorn-spockeli — Thu, 21 Nov 2019 15:24:32 GMT

Looking at the ble_app_uart code in SDK v8.0.0 you should be able to alter it to send a byte as soon as it is received over UART instead of waiting for the '\n' character. See comment below

void uart_event_handle(app_uart_evt_t * p_event)
{
    static uint8_t data_array[BLE_NUS_MAX_DATA_LEN];
    static uint8_t index = 0;
    uint32_t err_code;

    switch (p_event->evt_type)
    {
        case APP_UART_DATA_READY:
            UNUSED_VARIABLE(app_uart_get(&data_array[index]));
            index++;
            
            //Remove if statement and send a single byte each time the APP_UART_DATA_READY event is processed.
            if ((data_array[index - 1] == '\n') || (index >= (BLE_NUS_MAX_DATA_LEN))) 
            {
                err_code = ble_nus_string_send(&m_nus, data_array, index);
                if (err_code != NRF_ERROR_INVALID_STATE)
                {
                    APP_ERROR_CHECK(err_code);
                }
                
                index = 0;
            }
            break;

        case APP_UART_COMMUNICATION_ERROR:
            APP_ERROR_HANDLER(p_event->data.error_communication);
            break;

        case APP_UART_FIFO_ERROR:
            APP_ERROR_HANDLER(p_event->data.error_code);
            break;

        default:
            break;
            }
}

RE: Nrf51822 and STM32 uart bootloader problem

Folny — Thu, 21 Nov 2019 08:28:40 GMT

Yes, I use Keil for both Nrf51 and STM32, considering how to modify the code to send a string in ble_app_uart without having to use '\ n', and that the code can also be used for a standard STM32 Flash Loader ? this would solve many problems.

http://gechologic.com/how-to-use-stm32-flash-loader

RE: Nrf51822 and STM32 uart bootloader problem

bjorn-spockeli — Wed, 20 Nov 2019 18:36:49 GMT

If you're using Keil to develop the nRF51 Firmware, then it should be fairly simple to debug the nRF51, see http://www2.keil.com/mdk5/debug.

If you're using GCC with makefiles, then I would recommend using Segger Ozone, see Ozone The J-Link Debugger Introduction or GDB, see https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/using-gdb-with-nordic-devices.

RE: Nrf51822 and STM32 uart bootloader problem

Folny — Wed, 20 Nov 2019 16:29:21 GMT

I haven't tried the debug mode yet and I know very little about Nrf51 programming and I'm just learning and I'm hoping to come to this problem.

RE: Nrf51822 and STM32 uart bootloader problem

bjorn-spockeli — Wed, 20 Nov 2019 13:49:08 GMT

Ok, can you run the ble_app_uart in a debug session and check wether the two bytes are being received or not, i.e. that you enter the UART event handler? You can alternatively output the received data using RTT.

Best regards

Bjørn

RE: Nrf51822 and STM32 uart bootloader problem

Folny — Wed, 20 Nov 2019 12:21:43 GMT

Sorry I use Google translator :-) I think the error will definitely be on the Nrf51 wall because as I wrote through the cable everything works correctly I have already tried many options but the problem still persists.

RE: Nrf51822 and STM32 uart bootloader problem

bjorn-spockeli — Wed, 20 Nov 2019 11:19:35 GMT

I ran the first sentence through Google Translate, which returned " That's exactly what I tried to add '\ n' to the STM32 boot code, but I get an error".

Ok, do you get an error on the STM side or the nRF51 side? Please elaborate.

RE: Nrf51822 and STM32 uart bootloader problem

Folny — Wed, 20 Nov 2019 10:36:43 GMT

Exactly, I tried to add an '\ n' update to the STM32 boot code, but I get an error while updating. I Have tested this modified code with FTDI usb and the update will succeed.

static void Send_ACK(UART_HandleTypeDef *handle)
{
    uint8_t msg[2] = {ACK, '\n'};
    
    HAL_UART_Tx(handle, msg, 2);
}

/*! \brief Sends an NACKnowledge byte to the host.
 *  
 *  \param  *UartHandle The UART handle
 */
static void Send_NACK(UART_HandleTypeDef *handle)
{
    uint8_t msg[2] = {NACK, '\n'};
    
    HAL_UART_Tx(handle, msg, 2);
}

RE: Nrf51822 and STM32 uart bootloader problem

bjorn-spockeli — Wed, 20 Nov 2019 09:34:57 GMT

Just to calrify: You have a STM32F sends UART commands to the nRF51 running the ble_app_uart example, which in turn sends these over BLE to a ESP32?

I think that the ble_app_uart example expects the '\n' character to be received before sending the string received over UART on BLE.

Best regards

Bjørn