Tutorial about USB HID Report Descriptors

最新推荐文章于 2023-05-23 09:40:23 发布
最新推荐文章于 2023-05-23 09:40:23 发布
阅读量420 收藏 1
点赞数
分类专栏： C/C++ 嵌入式 开发工具 文章标签： USB HID Descriptor
C/C++ 同时被 3 个专栏收录
23 篇文章 1 订阅
订阅专栏
嵌入式
23 篇文章 1 订阅
订阅专栏
开发工具
6 篇文章 0 订阅
订阅专栏

Forward Since: https://eleccelerator.com/tutorial-about-usb-hid-report-descriptors/

This page is from my old website, and it is sort of popular, so I’ve moved it here.

A USB HID report descriptor is one of the descriptors that a USB host can request from a USB device. HID devices send data to the host using reports, and the descriptor tells the host how to interpret the data. I will try to show you how to write one of these descriptors.

First, go to this page http://www.usb.org/developers/hidpage/ and find the document titled “Device Class Definition for HID”. What I will be talking about is essentially paraphrasing the important sections of that document.

Thanks for visiting! If you appreciate my content, please consider making a donation to a charity. Thank you ~ Frank

 

Second, go get the HID descriptor tool from the same page. You’ll want to play with it as you go through this tutorial. It is an absolute headache to write the HID report descriptors manually (converting between binary and hex and looking up the meanings of the numbers) so this tool is essential.

What is a USB HID report descriptor?

The HID protocol makes implementation of devices very simple. Devices define their data packets and then present a “HID descriptor” to the host. The HID descriptor is a hard coded array of bytes that describe the device’s data packets. This includes: how many packets the device supports, how large are the packets, and the purpose of each byte and bit in the packet. For example, a keyboard with a calculator program button can tell the host that the button’s pressed/released state is stored as the 2nd bit in the 6th byte in data packet number 4 (note: these locations are only illustrative and are device specific). The device typically stores the HID descriptor in ROM and does not need to intrinsically understand or parse the HID descriptor. Some mouse and keyboard hardware in the market today are implemented using only an 8-bit CPU.

– Wikipedia on Human Interface Device

I’m going to try teaching you about USB HID report descriptors by walking you through writing a few.

For a simple starting point, let us make a standard mouse. Just three buttons, and movement on the X and Y axis. So we want to send data regarding the buttons and movement. It takes one bit to represent each button, and one byte to represent the movement on one axis as a signed integer. So we can say that we want the data structure to look something like this

 Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
Byte 0UselessUselessUselessUselessUselessLeft ButtonMiddle ButtonRight Button
Byte 1X Axis Relative Movement as Signed Integer
Byte 2Y Axis Relative Movement as Signed Integer

And then we can say our data structure in C looks like

 

1

2

3

4

5

6

struct mouse_report_t

{

    uint8_t buttons;

    int8_t x;

    int8_t y;

}

So now in our descriptor, our first item must describe buttons, three of them

 

1

2

3

USAGE_PAGE (Button)

USAGE_MINIMUM (Button 1)

USAGE_MAXIMUM (Button 3)

each button status is represented by a bit, 0 or 1

 

1

2

LOGICAL_MINIMUM (0)

LOGICAL_MAXIMUM (1)

there are three of these bits

 

1

2

REPORT_COUNT (3)

REPORT_SIZE (1)

send this variable data to the computer

 

1

INPUT (Data,Var,Abs)

and the final result looks like

 

1

2

3

4

5

6

7

8

USAGE_PAGE (Button)

USAGE_MINIMUM (Button 1)

USAGE_MAXIMUM (Button 3)

LOGICAL_MINIMUM (0)

LOGICAL_MAXIMUM (1)

REPORT_COUNT (3)

REPORT_SIZE (1)

INPUT (Data,Var,Abs)

that will represent the buttons

but what about the five useless padding bits?

 

1

2

3

REPORT_COUNT (1)

REPORT_SIZE (5)

INPUT (Cnst,Var,Abs)

now we make the X axis movement

 

1

2

USAGE_PAGE (Generic Desktop)

USAGE (X)

we want it to be a signed integer that takes one byte, so it has a value between -127 and +127 (actually -128 and +127, but I want to keep things even)

 

1

2

LOGICAL_MINIMUM (-127)

LOGICAL_MAXIMUM (127)

we want it to take an entire byte which is 8 bits

 

1

2

REPORT_SIZE (8)

REPORT_COUNT (1)

and send it to the computer as a variable relative coordinate

 

1

INPUT (Data,Var,Rel)

you end up with something like this to represent the X axis movement

 

1

2

3

4

5

6

7

USAGE_PAGE (Generic Desktop)

USAGE (X)

LOGICAL_MINIMUM (-127)

LOGICAL_MAXIMUM (127)

REPORT_SIZE (8)

REPORT_COUNT (1)

INPUT (Data,Var,Rel)

How about Y axis? You can try

 

1

2

3

4

5

6

7

8

9

10

11

12

13

14

USAGE_PAGE (Generic Desktop)

USAGE (X)

LOGICAL_MINIMUM (-127)

LOGICAL_MAXIMUM (127)

REPORT_SIZE (8)

REPORT_COUNT (1)

INPUT (Data,Var,Rel)

USAGE_PAGE (Generic Desktop)

USAGE (Y)

LOGICAL_MINIMUM (-127)

LOGICAL_MAXIMUM (127)

REPORT_SIZE (8)

REPORT_COUNT (1)

INPUT (Data,Var,Rel)

Which will work, but to save memory, we can do this instead

 

1

2

3

4

5

6

7

8

USAGE_PAGE (Generic Desktop)

USAGE (X)

USAGE (Y)

LOGICAL_MINIMUM (-127)

LOGICAL_MAXIMUM (127)

REPORT_SIZE (8)

REPORT_COUNT (2)

INPUT (Data,Var,Rel)

So all your data will end up looking like

 

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

USAGE_PAGE (Button)

USAGE_MINIMUM (Button 1)

USAGE_MAXIMUM (Button 3)

LOGICAL_MINIMUM (0)

LOGICAL_MAXIMUM (1)

REPORT_COUNT (3)

REPORT_SIZE (1)

INPUT (Data,Var,Abs)

REPORT_COUNT (1)

REPORT_SIZE (5)

INPUT (Cnst,Var,Abs)

USAGE_PAGE (Generic Desktop)

USAGE (X)

USAGE (Y)

LOGICAL_MINIMUM (-127)

LOGICAL_MAXIMUM (127)

REPORT_SIZE (8)

REPORT_COUNT (2)

INPUT (Data,Var,Rel)

Ah but we are not done, in order to make the computer know that this is a mouse, we do

 

1

2

3

4

5

6

7

8

9

10

USAGE_PAGE (Generic Desktop)

USAGE (Mouse)

COLLECTION (Application)

    USAGE (Pointer)

    COLLECTION (Physical)

     

    ... What we wrote already goes here

     

    END COLLECTION

END COLLECTION

So in the end, this is the USB HID report descriptor for a standard mouse

 

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

0x05, 0x01,                    // USAGE_PAGE (Generic Desktop)

0x09, 0x02,                    // USAGE (Mouse)

0xa1, 0x01,                    // COLLECTION (Application)

0x09, 0x01,                    //   USAGE (Pointer)

0xa1, 0x00,                    //   COLLECTION (Physical)

0x05, 0x09,                    //     USAGE_PAGE (Button)

0x19, 0x01,                    //     USAGE_MINIMUM (Button 1)

0x29, 0x03,                    //     USAGE_MAXIMUM (Button 3)

0x15, 0x00,                    //     LOGICAL_MINIMUM (0)

0x25, 0x01,                    //     LOGICAL_MAXIMUM (1)

0x95, 0x03,                    //     REPORT_COUNT (3)

0x75, 0x01,                    //     REPORT_SIZE (1)

0x81, 0x02,                    //     INPUT (Data,Var,Abs)

0x95, 0x01,                    //     REPORT_COUNT (1)

0x75, 0x05,                    //     REPORT_SIZE (5)

0x81, 0x03,                    //     INPUT (Cnst,Var,Abs)

0x05, 0x01,                    //     USAGE_PAGE (Generic Desktop)

0x09, 0x30,                    //     USAGE (X)

0x09, 0x31,                    //     USAGE (Y)

0x15, 0x81,                    //     LOGICAL_MINIMUM (-127)

0x25, 0x7f,                    //     LOGICAL_MAXIMUM (127)

0x75, 0x08,                    //     REPORT_SIZE (8)

0x95, 0x02,                    //     REPORT_COUNT (2)

0x81, 0x06,                    //     INPUT (Data,Var,Rel)

0xc0,                          //   END_COLLECTION

0xc0                           // END_COLLECTION

This is actually the example descriptor provided with the USB HID documentation, and you can also find this as an example provided with the HID tool.

Cool, at this point, you will have encountered some concepts that you may have questions about, you should research the following:

Usage Pages

There’s one thing that I think isn’t explained well in the documentation, USAGE, USAGE_PAGE, USAGE_MINIMUM and USAGE_MAXIMUM. In a descriptor, you first set a USAGE_PAGE, and certain USAGEs are available. In the mouse example, USAGE_PAGE (Generic Desktop) allowed you to use USAGE (Mouse), and when the usage page was changed to USAGE_PAGE (Button), then the USAGE_MINIMUM and USAGE_MAXIMUM allowed you to specify the buttons, and before you can use USAGE (X) and USAGE (Y), the usage page was changed back to USAGE_PAGE (Generic Desktop). The usage page is like a namespace, changing the usage page affects what “usages” are available. Read the documentation called ” HID Usage Tables” for more info.

Collections

Read the documentation about the official proper use of collections. In my own words, collections can be used to organize your data, for example, a keyboard may have a built-in touchpad, then the data for the keyboard should be kept in one application collection while the touchpad data is kept in another. We can assign an “Report ID” to each collection, which I will show you later.

Hey here’s something you can do, by turning “USAGE (Mouse)” into “USAGE (Gamepad)”, you make the computer think that it’s a game pad with one joystick and 3 buttons. How about converting a Playstation 2 controller into a USB gamepad? The controller has 16 buttons and two thumb sticks, so we want the data to look like

 

 Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
Byte 0ButtonButtonButtonButtonButtonButtonButtonButton
Byte 1ButtonButtonButtonButtonButtonButtonButtonButton
Byte 2Left X Axis as Signed Integer
Byte 3Left Y Axis as Signed Integer
Byte 4Right X Axis as Signed Integer
Byte 5Right Y Axis as Signed Integer

So our data structure looks like

 

1

2

3

4

5

6

7

8

struct gamepad_report_t

{

    uint16_t buttons;

    int8_t left_x;

    int8_t left_y;

    int8_t right_x;

    int8_t right_y;

}

We make the computer understand that it’s a game pad

 

1

2

3

4

5

6

7

8

9

USAGE_PAGE (Generic Desktop)

USAGE (Game Pad)

COLLECTION (Application)

    COLLECTION (Physical)

 

    ...

 

    END COLLECTION

END COLLECTION

for the buttons

 

1

2

3

4

5

6

7

8

USAGE_PAGE (Button)

USAGE_MINIMUM (Button 1)

USAGE_MAXIMUM (Button 16)

LOGICAL_MINIMUM (0)

LOGICAL_MAXIMUM (1)

REPORT_COUNT (16)

REPORT_SIZE (1)

INPUT (Data,Var,Abs)

for the four thumb stick axis

 

1

2

3

4

5

6

7

8

9

10

USAGE_PAGE (Generic Desktop)

USAGE (X)

USAGE (Y)

USAGE (Z)

USAGE (Rx)

LOGICAL_MINIMUM (-127)

LOGICAL_MAXIMUM (127)

REPORT_SIZE (8)

REPORT_COUNT (4)

INPUT (Data,Var,Abs)

NOTE: Z is used to represent the right stick’s X axis, Rx is used to represent the right stick’s Y axis. This doesn’t make sense but this is how most existing USB game pads work. I have tested this using Battlefield Bad Company 2, it works.

NOTE: Use “absolute” for something like joysticks, but “relative” for things like mouse.

So now you end up with

 

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

USAGE_PAGE (Generic Desktop)

USAGE (Game Pad)

COLLECTION (Application)

    COLLECTION (Physical)

        USAGE_PAGE (Button)

        USAGE_MINIMUM (Button 1)

        USAGE_MAXIMUM (Button 16)

        LOGICAL_MINIMUM (0)

        LOGICAL_MAXIMUM (1)

        REPORT_COUNT (16)

        REPORT_SIZE (1)

        INPUT (Data,Var,Abs)

        USAGE_PAGE (Generic Desktop)

        USAGE (X)

        USAGE (Y)

        USAGE (Z)

        USAGE (Rx)

        LOGICAL_MINIMUM (-127)

        LOGICAL_MAXIMUM (127)

        REPORT_SIZE (8)

        REPORT_COUNT (4)

        INPUT (Data,Var,Abs)

    END COLLECTION

END COLLECTION

Hey how about two players? Here’s where collections get handy

 

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

USAGE_PAGE (Generic Desktop)

USAGE (Game Pad)

COLLECTION (Application)

    COLLECTION (Physical)

        REPORT_ID (1)

        ...

    END COLLECTION

END COLLECTION

USAGE_PAGE (Generic Desktop)

USAGE (Game Pad)

COLLECTION (Application)

    COLLECTION (Physical)

        REPORT_ID (2)

        ...

    END COLLECTION

END COLLECTION

fill in the data areas and you end up with

 

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

USAGE_PAGE (Generic Desktop)

USAGE (Game Pad)

COLLECTION (Application)

    COLLECTION (Physical)

        REPORT_ID (1)

        USAGE_PAGE (Button)

        USAGE_MINIMUM (Button 1)

        USAGE_MAXIMUM (Button 16)

        LOGICAL_MINIMUM (0)

        LOGICAL_MAXIMUM (1)

        REPORT_COUNT (16)

        REPORT_SIZE (1)

        INPUT (Data,Var,Abs)

        USAGE_PAGE (Generic Desktop)

        USAGE (X)

        USAGE (Y)

        USAGE (Z)

        USAGE (Rx)

        LOGICAL_MINIMUM (-127)

        LOGICAL_MAXIMUM (127)

        REPORT_SIZE (8)

        REPORT_COUNT (4)

        INPUT (Data,Var,Abs)

    END COLLECTION

END COLLECTION

USAGE_PAGE (Generic Desktop)

USAGE (Game Pad)

COLLECTION (Application)

    COLLECTION (Physical)

        REPORT_ID (2)

        USAGE_PAGE (Button)

        USAGE_MINIMUM (Button 1)

        USAGE_MAXIMUM (Button 16)

        LOGICAL_MINIMUM (0)

        LOGICAL_MAXIMUM (1)

        REPORT_COUNT (16)

        REPORT_SIZE (1)

        INPUT (Data,Var,Abs)

        USAGE_PAGE (Generic Desktop)

        USAGE (X)

        USAGE (Y)

        USAGE (Z)

        USAGE (Rx)

        LOGICAL_MINIMUM (-127)

        LOGICAL_MAXIMUM (127)

        REPORT_SIZE (8)

        REPORT_COUNT (4)

        INPUT (Data,Var,Abs)

    END COLLECTION

END COLLECTION

This is really important: You must change your data structure to include the report ID

 Bit 7Bit 6Bit 5Bit 4Bit 3Bit 2Bit 1Bit 0
Byte 0Report ID
Byte 1ButtonButtonButtonButtonButtonButtonButtonButton
Byte 2ButtonButtonButtonButtonButtonButtonButtonButton
Byte 3Left X Axis as Signed Integer
Byte 4Left Y Axis as Signed Integer
Byte 5Right X Axis as Signed Integer
Byte 6Right Y Axis as Signed Integer

 

1

2

3

4

5

6

7

8

9

struct multiplayer_gamepad_report_t

{

    uint8_t report_id;

    uint16_t buttons;

    int8_t left_x;

    int8_t left_y;

    int8_t right_x;

    int8_t right_y;

}

You must manually set the report ID before you send the data to the computer in order for the computer to understand which player the data belongs to.

 

1

2

3

4

multiplayer_gamepad_report_t player1_report;

multiplayer_gamepad_report_t player2_report;

player1_report.report_id = 1;

player2_report.report_id = 2;

You can also use collections and report IDs to make composite devices. So far I’ve shown you the keyboard, mouse, and gamepad. Here’s something that describes a composite device that is a keyboard, mouse, and two player game pad.

 

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

USAGE_PAGE (Generic Desktop)

USAGE (Keyboard)

COLLECTION (Application)

    REPORT_ID (1)

    ...

END COLLECTION

USAGE_PAGE (Generic Desktop)

USAGE (Mouse)

COLLECTION (Application)

    USAGE (Pointer)

    COLLECTION (Physical)

        REPORT_ID (2)

        ...

    END COLLECTION

END COLLECTION

USAGE_PAGE (Generic Desktop)

USAGE (Game Pad)

COLLECTION (Application)

    COLLECTION (Physical)

        REPORT_ID (3)

        ...

    END COLLECTION

END COLLECTION

USAGE_PAGE (Generic Desktop)

USAGE (Game Pad)

COLLECTION (Application)

    COLLECTION (Physical)

        REPORT_ID (4)

        ...

    END COLLECTION

END COLLECTION

and of course, your data structures with the added report ID.

 

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

struct keyboard_report_t

{

    uint8_t report_id;

    uint8_t modifier;

    uint8_t reserved;

    uint8_t keycode[6];

}

 

struct mouse_report_t

{

    uint8_t report_id;

    uint8_t buttons;

    int8_t x;

    int8_t y;

}

 

struct gamepad_report_t

{

    uint8_t report_id;

    uint16_t buttons;

    int8_t left_x;

    int8_t left_y;

    int8_t right_x;

    int8_t right_y;

}

But since we changed the data structure, your device no-longer supports boot protocol, and hence you will not need to define a protocol. So make sure you change usbconfig.h accordingly.

Want to see this in action? Load up this example project into USnooBie and let Windows’s “Devices and Printers” show you!

Example Project Files

hid_tutorial_1_ss[1]

polarisyj86
关注
  • 0
    点赞
  • 踩
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
USB报告描述符自动生成工具 HID Descriptor tool
04-07
HID Descriptor tool USB报告描述符自动生成工具 SMT32编码自动生成工具 HID tool
USB HID介绍
热门推荐
08-26 4万+
HID是一种USB通信协议，无需安装驱动就能进行交互，在学习HID之前，先来复习一下USB协议的相关内容。   USB设备描述符－概述 当插入USB设备后，主机会向设备请求各种描述符来识别设备。那什么是设备描述符呢？ Descriptor即描述符，是一个完整的数据结构，可以通过C语言等编程实现，并存储在USB设备中，用于描述一个USB设备的所有属性，USB主机是通过一系列命令来要求设备发送
HID标准规定的Usage Pages
ydgd118的博客
05-23 852
HID（Human Interface Devices）设备的Usage用于向计算机传达设备的功能用途等。Usage（用法）提供了对HID设备的输入、输出和特性报告中的数据项的描述。HID规范已经定义的用法的存在，并不保证计算机系统或应用软件将识别或利用该数据项。
HID从设备连接电脑获取描述符分析
hexiechina2010的专栏
06-03 3771
Bus Hound 6.01 capture on Windows Vista (x64). Complements of www.perisoft.net   Device - Device ID (followed by the endpoint for USB devices)             (18) Generic USB Hub             (29)
STM32例程Tutorial 32 - USB HID.7z
07-22
在"STM32例程 Tutorial 32 - USB HID"中，你可能会找到关于如何设置STM32 USB控制器、编写HID报告处理代码、配置描述符创建以及如何与主机进行有效通信的具体示例和指南。通过学习和实践这个教程，你可以掌握在STM32...
oracle report builder Tutorial.pdf
10-23
oracle report builder Tutorial.pdf
EDEM Tutorial 1 - Conveyor
最新发布
01-03
《EDEM教程1 - 传送带》是一份官方的学习资料，专为仿真爱好者设计，旨在帮助他们理解和掌握EDEM软件的使用。EDEM（Eulerian Discrete Element Method）是一种基于离散元方法的颗粒流体动力学软件，广泛应用于各种...
USB-AUDIO-CLASS-TUTORIAL.rar_class_usb audio
09-23
- USB设备根据功能被划分为不同的类，如HID（人机交互设备）、Mass Storage（大容量存储设备）、Hub（集线器）等，而UAC属于多媒体设备类。 - 每个设备类都有特定的设备描述符和配置描述符，用于告诉主机设备的...
HID Descriptor Tool
03-07
此工具能生成HID report descriptor的工具，并且可以测试report descriptor。
USB-HID学习(1)
weixin_41080308的博客
03-15 2018
基本定义 USB是一种通用的串行总线，它支持一个主机与一个或多个外设之间通信。采用串行数据传输通信协议。 USBHID设备 定义：USBHID是USB设备中的一大类，即Human Interface Devices，人机接口设备。它主要用于人与计算机进行交互，并且是USB最早支持的一类设备。HID设备支持低速、全速、高速三种设备。由于HID设备要求用户输入能够得到及时响应，故其传输方式通常采用“中断方式”。 在USB协议中，HID设备的定义放置在接口描述符中，USB的设备描述符和配置描述符中.
罗技F710手柄描述符数据抓包 - 以及stm32读取usb-hid数据程序
少磊的博客
01-28 4810
硬件： 罗技F710游戏手柄、一台笔记本电脑 软件： USBlyzer分析仪 大家都知道，罗技F710上有D模式和X模式，D模式是普通模式，每帧数据传输8个字节。 D模式 Connection Status Device connected Current Configuration 1 Speed Full (12 Mbit/s) Device Address 14 ...
自制游戏手柄joystick stm32 hal usb协议
dawm的博客
04-27 8728
自制游戏手柄ps：开发环境初始配置代码编写推荐工具：参考文章： ps： 耗费了一天去了解怎么实现usb协议下的HID传输，因为各个文字没有说清楚，导致我数据的内容总时接收不到或者错位，所以特意下一篇文章来具体指出了各个步骤的坑 开发环境 windows stm32f103rct6 stm32cubemx keil joystick模块（5针）两轴 初始配置 开启时钟 USB时钟 一定 48M 打开USB 配置HID 配置完成 代码编写 打开usbd_hid.c 应为stm32cbemx 自动生成
STM32 HAL库学习（六）USB识别成Custom HID通信
yhl_sophia的博客
11-19 2万+
一、STM32F070 USB基础知识了解： STM32F070 USB采用USB 2.0规范，时钟频率为48MHZ，有一个专用的USB数据存储区，大小为1024字节；支持16个单向传输端点、8个双向传输端点 USB外设模块构成图： USB物理接口模块： USB_DM、USB_DP —— 数据正、负信号 Analog Transceiver —— 模拟收发器 Embedded pu...
几个错误的解决关键
我的世界我的梦
12-10 3万+
导读： 　　1、 　　org.springframework.orm.ObjectRetrievalFailureException: Object of class [com.xindeco.myregister.pojo.MyRegisterInfo] with identifier [14]: not found 　　MyRegisterInfo在数据库没有identifier [1
linux gadget 模拟鼠标,HID设备--开发板模拟鼠标
weixin_39611174的博客
05-16 1910
HIDHID鼠标裸数据驱动：1234567Symbol: HIDRAW [=y]Type : booleanPrompt: /dev/hidraw raw HID device supportLocation:-> Device Drivers-> HID support-> HID bus support (HID [=y])读取数据1read(uibc->hid_fd...
Android Open Accessory Protocol 2.0
weixin_33966095的博客
04-19 139
来自： http://source.android.com/devices/accessories/aoa2.html   Android Open Accessory Protocol 2.0   This document describes changes in the Android Open Accessory (AOA) protocol since its initial r...
USB HID报告描述符教程
Lonecheat的博客
08-19 412
https://zhuanlan.zhihu.com/p/27568561
tensorflow tutorial
10-30
TensorFlow Tutorial是TensorFlow官方提供的学习资源，旨在帮助新手快速入门。该教程详细介绍了TensorFlow的基本概念、常用操作和各种模型的构建方法。 在TensorFlow Tutorial中，首先会介绍TensorFlow的基本工作...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值