Skip to content
TheChatArchiveThe Chat Archive
Qwenqwen3-235b-a22b· Alibaba (Qwen)Hugging Face LMArena Human Preference 140K

Write me code in LL to unit GPDMA on channel 0 for battery communciation

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Claudeclaude-opus-4-20250514’s answer.
  1. User

    Write me code in LL to unit GPDMA on channel 0 for battery communciation

  2. Qwen Assistant

    Here's an example of how to configure GPDMA Channel 0 for battery communication (assuming UART-based communication) using STM32 Low Layer (LL) APIs:

    #include "stm32h5xx_ll_gpdma.h"
    #include "stm32h5xx_ll_uart.h"
    #include "stm32h5xx_rcc.h"
    
    // Define your UART instance and buffer
    #define BATTERY_UART USART1
    #define BATTERY_BUFFER_SIZE 64
    uint8_t battery_tx_buffer[BATTERY_BUFFER_SIZE] = "BATT_DATA";
    
    void GPDMA_Battery_Init(void)
    {
        // 1. Enable GPDMA clock
        RCC->AHB1ENR |= RCC_AHB1ENR_GPDMA1EN;
        
        // 2. Deinitialize channel 0 to default state
        LL_GPDMA_DeactivateChannel(GPDMA1, LL_GPDMA_CHANNEL_0);
        
        // 3. Configure GPDMA Channel 0
        LL_GPDMA_SetPeriphRequest(GPDMA1, LL_GPDMA_CHANNEL_0, LL_GPDMA1_REQUEST_USART1_TX);
        
        // Configure channel parameters
        LL_GPDMA_ConfigChannel(GPDMA1, LL_GPDMA_CHANNEL_0,
            LL_GPDMA_DIRECTION_MEMORY_TO_PERIPH |
            LL_GPDMA_MODE_NORMAL |
            LL_GPDMA_SCR_UB1 |
            LL_GPDMA_SINC_INCREMENT |
            LL_GPDMA_DINC_NOINCREMENT |
            LL_GPDMA_SDATAALIGN_BYTE |
            LL_GPDMA_DDATAALIGN_BYTE |
            LL_GPDMA_PRIORITY_HIGH);
        
        // 4. Set data addresses
        LL_GPDMA_SetPeriphAddress(GPDMA1, LL_GPDMA_CHANNEL_0, (uint32_t)&BATTERY_UART->TDR);
        LL_GPDMA_SetMemoryAddress(GPDMA1, LL_GPDMA_CHANNEL_0, (uint32_t)battery_tx_buffer);
        
        // 5. Set number of data units
        LL_GPDMA_SetDataLength(GPDMA1, LL_GPDMA_CHANNEL_0, BATTERY_BUFFER_SIZE);
        
        // 6. Enable UART TX DMA request
        LL_USART_EnableDMAReq_TX(BATTERY_UART);
        
        // 7. Enable GPDMA channel
        LL_GPDMA_EnableChannel(GPDMA1, LL_GPDMA_CHANNEL_0);
        
        // 8. Start transfer
        LL_GPDMA_StartTransfer(GPDMA1, LL_GPDMA_CHANNEL_0);
    }
    
    // Example usage
    int main(void)
    {
        GPDMA_Battery_Init();
        
        // Wait for transfer complete
        while (!LL_GPDMA_IsActiveFlag_TC0(GPDMA1));
        
        // Clear flag
        LL_GPDMA_ClearFlag_TC0(GPDMA1);
        
        // Continue with other operations...
    }
    

    Key considerations:

    1. Hardware Requirements:

      • Ensure your UART peripheral supports DMA
      • Verify the correct DMAMUX request mapping
      • Confirm UART GPIOs are configured for alternate function
    2. Buffer Management:

      • Make sure the buffer remains in scope during transfer
      • Consider using volatile or memory barriers if buffer is modified elsewhere
      • For continuous transfers, implement double buffering
    3. Interrupt Handling:

      void DMA1_Channel0_IRQHandler(void)
      {
          if (LL_GPDMA_IsActiveFlag_TC0(GPDMA1)) {
              LL_GPDMA_ClearFlag_TC0(GPDMA1);
              // Handle transfer complete
          }
          
          if (LL_GPDMA_IsActiveFlag_TE0(GPDMA1)) {
              LL_GPDMA_ClearFlag_TE0(GPDMA1);
              // Handle transfer error
          }
      }
      
    4. Configuration Notes:

      • Change LL_GPDMA1_REQUEST_USART1_TX according to your UART instance
      • Adjust data width (BYTE/HALFWORD/WORD) based on your UART configuration
      • Modify priority and mode (normal/circular) as needed
      • For reception, reverse direction and use RDR register

    To use this code:

    1. Replace USART1 with your actual UART instance
    2. Adjust buffer size and content
    3. Enable NVIC interrupts if using interrupt-driven transfers
    4. Add error handling for production code

    This example demonstrates memory-to-peripheral transfer for UART transmission. For battery communication, you might need to adapt it for specific protocols (Modbus, SMBus, etc.) and add appropriate timing/parsing logic.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.