当前位置: 首页 > news >正文

ZYNQ AXI-UART学习

前言

记录一下在学习使用axi-uart官方example过程的一些问题和困惑

问题和困惑

RecvBuffer是一个数组,为什么可以直接用数组名和变量RecvCount相加,就可以给XUartLite_Recv第二个参数传递了?

点击查看代码
/******************************************************************************
*
* Copyright (C) 2002 - 2015 Xilinx, Inc.  All rights reserved.
*
* Permission is hereby granted, free of charge, to any person obtaining a copy
* of this software and associated documentation files (the "Software"), to deal
* in the Software without restriction, including without limitation the rights
* to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
* copies of the Software, and to permit persons to whom the Software is
* furnished to do so, subject to the following conditions:
*
* The above copyright notice and this permission notice shall be included in
* all copies or substantial portions of the Software.
*
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
* XILINX  BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
* WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
* OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
* SOFTWARE.
*
* Except as contained in this notice, the name of the Xilinx shall not be used
* in advertising or otherwise to promote the sale, use or other dealings in
* this Software without prior written authorization from Xilinx.
*
******************************************************************************/
/******************************************************************************/
/**
*
* @file xuartlite_polled_example.c
*
* This file contains a design example using the UartLite driver (XUartLite) and
* hardware device using the polled mode.
*
* @note
*
* The user must provide a physical loopback such that data which is
* transmitted will be received.
*
* MODIFICATION HISTORY:
* <pre>
* Ver   Who  Date	 Changes
* ----- ---- -------- -----------------------------------------------
* 1.00a jhl  02/13/02 First release
* 1.00a sv   06/13/05 Minor changes to comply to Doxygen and coding guidelines
* 2.00a ktn  10/20/09 Updated this example to wait for valid data in receive
*		      fifo instead of Tx fifo empty to update receive buffer
*		      and minor changes as per coding guidelines.
* 3.2   ms   01/23/17 Added xil_printf statement in main function to
*                     ensure that "Successfully ran" and "Failed" strings
*                     are available in all examples. This is a fix for
*                     CR-965028.
* </pre>
******************************************************************************//***************************** Include Files *********************************/#include "xparameters.h"
#include "xstatus.h"
#include "xuartlite.h"
#include "xil_printf.h"/************************** Constant Definitions *****************************//** The following constants map to the XPAR parameters created in the* xparameters.h file. They are defined here such that a user can easily* change all the needed parameters in one place.*/
#define UARTLITE_DEVICE_ID	XPAR_UARTLITE_0_DEVICE_ID/** The following constant controls the length of the buffers to be sent* and received with the UartLite, this constant must be 16 bytes or less since* this is a single threaded non-interrupt driven example such that the* entire buffer will fit into the transmit and receive FIFOs of the UartLite.*/
#define TEST_BUFFER_SIZE 16/**************************** Type Definitions *******************************//***************** Macros (Inline Functions) Definitions *********************//************************** Function Prototypes ******************************/int UartLitePolledExample(u16 DeviceId);/************************** Variable Definitions *****************************/XUartLite UartLite;		/* Instance of the UartLite Device *//** The following buffers are used in this example to send and receive data* with the UartLite.*/
u8 SendBuffer[TEST_BUFFER_SIZE];	/* Buffer for Transmitting Data */
u8 RecvBuffer[TEST_BUFFER_SIZE];	/* Buffer for Receiving Data *//*****************************************************************************/
/**
*
* Main function to call the Uartlite polled example.
*
* @param	None.
*
* @return	XST_SUCCESS if successful, otherwise XST_FAILURE.
*
* @note		None.
*
******************************************************************************/
int main(void)
{int Status;/** Run the UartLite polled example, specify the Device ID that is* generated in xparameters.h*/Status = UartLitePolledExample(UARTLITE_DEVICE_ID);if (Status != XST_SUCCESS) {xil_printf("Uartlite polled Example Failed\r\n");return XST_FAILURE;}xil_printf("Successfully ran Uartlite polled Example\r\n");return XST_SUCCESS;}/****************************************************************************/
/**
* This function does a minimal test on the UartLite device and driver as a
* design example. The purpose of this function is to illustrate
* how to use the XUartLite component.
*
* This function sends data and expects to receive the data thru the UartLite
* such that a  physical loopback must be done with the transmit and receive
* signals of the UartLite.
*
* This function polls the UartLite and does not require the use of interrupts.
*
* @param	DeviceId is the Device ID of the UartLite and is the
*		XPAR_<uartlite_instance>_DEVICE_ID value from xparameters.h.
*
* @return	XST_SUCCESS if successful, XST_FAILURE if unsuccessful.
*
*
* @note
*
* This function calls the UartLite driver functions in a blocking mode such that
* if the transmit data does not loopback to the receive, this function may
* not return.
*
****************************************************************************/
int UartLitePolledExample(u16 DeviceId)
{int Status;unsigned int SentCount;unsigned int ReceivedCount = 0;int Index;/** Initialize the UartLite driver so that it is ready to use.*/Status = XUartLite_Initialize(&UartLite, DeviceId);if (Status != XST_SUCCESS) {return XST_FAILURE;}/** Perform a self-test to ensure that the hardware was built correctly.*/Status = XUartLite_SelfTest(&UartLite);if (Status != XST_SUCCESS) {return XST_FAILURE;}/** Initialize the send buffer bytes with a pattern to send and the* the receive buffer bytes to zero.*/for (Index = 0; Index < TEST_BUFFER_SIZE; Index++) {SendBuffer[Index] = Index;RecvBuffer[Index] = 0;}/** Send the buffer through the UartLite waiting til the data can be sent* (block), if the specified number of bytes was not sent successfully,* then an error occurred.*/SentCount = XUartLite_Send(&UartLite, SendBuffer, TEST_BUFFER_SIZE);if (SentCount != TEST_BUFFER_SIZE) {return XST_FAILURE;}/** Receive the number of bytes which is transfered.* Data may be received in fifo with some delay hence we continuously* check the receive fifo for valid data and update the receive buffer* accordingly.*/while (1) {ReceivedCount += XUartLite_Recv(&UartLite,RecvBuffer + ReceivedCount,TEST_BUFFER_SIZE - ReceivedCount);if (ReceivedCount == TEST_BUFFER_SIZE) {break;}}/** Check the receive buffer data against the send buffer and verify the* data was correctly received.*/for (Index = 0; Index < TEST_BUFFER_SIZE; Index++) {if (SendBuffer[Index] != RecvBuffer[Index]) {return XST_FAILURE;}}return XST_SUCCESS;
}

解释

核心原理:C语言中数组名会退化成指针

  1. 数组名 → 指针
    当你把 RecvBuffer 用在表达式里(除了 sizeof 和 & 等少数场合),它会自动转换成一个指向首元素的指针,类型是 u8(即 unsigned char)。
    也就是说:
点击查看代码
RecvBuffer      // 等价于 &RecvBuffer[0],类型 u8*
  1. 指针 + 整数 = 偏移后的指针
    C语言允许指针进行加减整数运算,实际效果是:
点击查看代码
RecvBuffer + RecvCount    // 等价于 &RecvBuffer[RecvCount]

它给出的是数组中第 RecvCount 个元素的地址,类型仍然是 u8*。因为 u8 是1字节大小,所以这里的“偏移”刚好就是 RecvCount 个字节。

  1. 函数签名也对得上
    XUartLite_Recv 的第二个参数声明为 u8 DataBufferPtr,它需要的就是一个指向 u8 的指针。
    RecvBuffer + RecvCount 的类型正是 u8
    ,完美匹配。

一句话总结

RecvBuffer + RecvCount 就是 “数组首地址往后偏移 RecvCount 个字节的指针”,每次调用 Recv 时,新接收的数据就从这个位置开始存放,从而逐步填满整个接收缓冲区。

反思:结构体也能这样使用吗?

答案:不能,普通变量不会自动转换为指针(只有数组名会)。

http://www.jsqmd.com/news/730764/

相关文章:

  • 协议逆向工程实践:基于TEA加密算法的手机号与QQ号关联查询技术解析
  • 从Wi-Fi到5G:手把手教你用MATLAB仿真Alamouti编码性能(含QPSK调制)
  • Meshtastic终极指南:打造无界通信网络的完整教程
  • Phi-3.5-Mini-Instruct影视制作:人物小传生成+分场大纲+台词风格化润色
  • 客服售后响应太慢、沟通不清还不会整理?该如何优化客服售后服务
  • 英雄联盟智能助手Seraphine:3个颠覆性功能改变你的游戏体验
  • 5分钟快速上手QtScrcpy:电脑键鼠操控安卓手机的完整指南
  • 2026年一体式泵站生产厂家权威推荐榜单:一体化污水泵站/一体化预制泵站/雨水提升泵站源头厂家精选 - 泵站报价15613348888
  • simple-llm-finetuner性能优化:如何在有限GPU内存下获得最佳效果
  • 绝区零自动化工具终极指南:解放双手的全能游戏助手配置教程
  • RLHF-V:如何验证与改进大模型对齐中的奖励模型?
  • 2026年毕业论文AI率超50%攻略:高比例AIGC内容答辩前48小时处理完整方案
  • 《SRE:Google 运维解密》读书笔记25: 分布式周期性任务系统 - 当“定时任务”遇上“行星级规模”
  • 终极指南:3分钟解锁微信网页版完整功能的技术深度解析
  • nodejs基于Vue的电子办公签章系统_2122r
  • java武警警官学院训练信息管理系统论文
  • Phi-3.5-mini-instruct开源模型:可审计、可修改、可嵌入业务系统的LLM
  • Wan2.2-I2V-A14B部署案例:高校数字媒体实验室AI教学平台搭建
  • 电商设计师必看:如何用AI工具一键生成高点击率主图?
  • SiameseUniNLU部署教程:nohup后台运行+日志监控+端口管理全流程详解
  • 小米 MiMo 100 万亿 Token 保姆级免费申请教程
  • NVIDIA Profile Inspector完整指南:5步解锁显卡隐藏性能的终极方案
  • QQ音乐加密格式算法深度解析与逆向工程实现
  • 【Sickos1.1渗透测试手把手超详细教程】
  • 10分钟掌握RePKG:解锁Wallpaper Engine资源的终极钥匙
  • ComfyUI-Manager:如何用插件管理器轻松管理你的AI绘画工作流
  • 5步轻松为Unity游戏添加智能翻译功能
  • Wi-Fi 信号盲区和断连难题怎么破?6 种方法让家庭网络稳定升级!
  • TMSpeech:彻底改变Windows本地语音识别的三大突破
  • AntiMicroX:游戏手柄映射解决方案的技术实现与配置策略