RT-Thread / RT-Thread/rt-thread

🔨[bsp][nrf5x][driver][Improve the drivers within HAL_Driver]

Open
#6,058 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

good first issue
Dominant language
C
Stars
12.2k
Forks
5.4k
Avg merge
4d 12h
Merged PRs (30d)
40

Description

you can use the nrf5x board on your hand to finish this "good first issue"

[bsp/nrf5x]https://github.com/RT-Thread/rt-thread/tree/master/bsp/nrf5x

You can follow the document device introduce

可以用手上的nordic 开发板来进行PR
如果没有相关芯片开发板的BSP,可以尝试提交BSP, 参考文档 nRF5x系列BSP制作教程.md
如果有BSP,可以尝试验证一些功能,有些BSP并不完善,并且PR,比如UART, SPI, IIC等模块,验证成功,应该有需要PR和修复的地方。

提交BSP开发板
提交SPI IIC 模块修复和验证和完善

根据文档:
驱动接口
可验证模块,也可以添加utest测试项:

  • PIN
  • UARTV1
  • UARTV2
  • ADC
  • DAC
  • CAN
  • HWTIMER
  • IIC
  • PWM
  • RTC
  • SPI
  • WATCHDOG
  • HWCRYPTO
  • AUDIO IIS
  • USBD
  • USBH
  • PULSE ENCODER
  • WLAN
  • ON-CHIP FLASH

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the bsp/nrf5x directory and the nRF5x BSP tutorial, then read the device and driver-interface documentation. Select one listed module, such as SPI, IIC, or UART, and inspect its existing BSP support and any related utest coverage. Done means a specific driver improvement, validation result, or utest addition is submitted as a focused PR.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
embedded-iot
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.