Read the check-in terminal: Chapters 25-27 - "RT-Thread Device Driver Development Guide"

EEWORLD社区

Read the check-in terminal: Chapters 25-27 - "RT-Thread Device Driver Development Guide" [Copy link]

Dear reading friends @nanruo @chrisrh @wakojosin @xiaolinen @damiaa

The reading check-in period ends on October 7th, and everyone can arrange their own progress.

The terminal was released in advance to celebrate the double holidays. The following questions are expected to be answered after reading Chapters 25-27 of the "RT-Thread Device Driver Development Guide".

1.USB device drivers are advanced drivers. Developing such device drivers requires developers to be familiar with the corresponding peripheral protocols. When developing USBD device drivers, it is not necessary to implement all the operation methods provided by the driver framework. Some operation methods may not be implemented. For example, which ones?
2.CAN interrupt functions do not return values. In the process of driver writing, according to different interrupt events, event
3.Which functions need to be called when entering and exiting interrupts?

damiaa

1.USB device drivers are advanced drivers. To develop such device drivers, developers must be familiar with the corresponding peripheral protocols. When developing USBD device drivers, it is not necessary to implement all the operation methods provided by the driver framework. Some operation methods may not be implemented. For example, which ones?

set_config

Suspended

wakeup

2. The CAN interrupt function does not have a return value. In the process of driver writing, according to different interrupt events, event

ＲＴ＿ＣＡＮ＿ＥＶＥＮＴ＿Ｒ︸＿ＩＮＤ 01

ＲＴ＿ＣＡＮ＿ＥＶＥＮＴ＿ＴＸ＿ＤＯＮＥ 02

ＲＴ＿ＣＡＮ＿ＥＶＥＮＴ＿ＴＸ＿ＦＡＩＬ 0３

ＲＴ＿ＣＡＮ＿ＥＶＥＮＴ＿ＲＸ＿ＴＩＭＥＯＵＴ 0５

ＲＴ＿ＣＡＮ＿ＥＶＥＮＴ＿ＲＸＯＦ＿ＩＮＤ 0６

　
3. Which functions need to be called when entering and exiting an interrupt?

Call interrupt entry rt_interrupt_enter();

and exit function rt_interrupt_leave();

wakojosin

1.USB device drivers are advanced drivers. To develop such device drivers, developers must be familiar with the corresponding peripheral protocols. When developing USBD device drivers, it is not necessary to implement all the operation methods provided by the driver framework. Some operation methods may not be implemented. For example, which ones?

set_config,suspend,wakeup
2.CAN interrupt function does not have a return value. In the process of driver writing, according to different interrupt events, event

Take RT_CAN_EVENT_RX_IND/TX_DONE/TX_FAIL/RX_TIMEOUT/RXOF_IND
3. Which functions need to be called when entering and exiting the interrupt?

Need to call rt_interrupt_enter and rt_interrupt_leave

xiaolinen

1. The three operations of set_config, suspend, and wakeup may not be implemented

2. RT_CAN_EVENT_RX_IND; RT_CAN_EVENT_TX_DONE; RT_CAN_EVENT_TX_FAIL; RT_CAN_EVENT_RX_TIMEOUT; RT_CAN_EVENT_RXOF_IND;

3. When entering and exiting an interrupt, you need to call rt_interrupt_enter() and rt_interrupt_leave()

chrisrh

1.USB device drivers are advanced drivers. To develop such device drivers, developers must be familiar with the corresponding peripheral protocols. When developing USBD device drivers, it is not necessary to implement all the operation methods provided by the driver framework. Some operation methods may not be implemented. For example, which ones?

set_config configures USBD device, suspend suspends USBD device, wakeup wakes up USBD device

2. The CAN interrupt function does not have a return value. In the process of driver writing, according to different interrupt events, event

The following values are possible: 0x01/*receive complete*/, 0x02/*send complete*/, 0x03/*send failed*/, 0x05/*receive timeout*/, 0x06/*receive overflow*/

3. Which functions need to be called when entering and exiting an interrupt?

When entering and exiting an interrupt, you need to call the interrupt entry function rt_interrupt_enter and the interrupt exit function rt_interrupt_leave.

2023.10.01, happy National Day holiday~

南若

1. Configure, suspend, and wake up

2. RT_CAN_EVENT_RX_IND(01); RT_CAN_EVENT_TX_DONE(02); RT_CAN_EVENT_TX_FAIL(03); RT_CAN_EVENT_RX_TIMEOUT(05)
;