fix[STM32][I2C]: stabilize async completion and recovery flow for hard i2c

[wdfk-prog]

拉取/合并请求描述：(PR description)

[

为什么提交这份PR (why to submit this PR)

STM32 hard I2C 在使用 IRQ/DMA 异步传输时依赖 HAL 回调唤醒 rt_completion_wait()。当前错误中断未完整启用，且错误回调没有通知等待线程，可能导致 NACK、BERR 或异常状态下等待超时，后续恢复流程不稳定。

你的解决方案是什么 (what is your solution)

• 在配置 IRQ/DMA 异步传输时同时启用 I2C event IRQ 和 error IRQ。
• 为 receive/transmit start helper 增加 async_allowed 参数，避免在调度器不可用或全局中断关闭时进入 IRQ/DMA 等待路径。
• 在每次传输前重新初始化 completion，并将毫秒超时转换为 RT-Thread tick 后等待。
• 在异步完成后检查 HAL ErrorCode，在错误回调中唤醒等待线程。
• 对异步等待失败或 HAL 错误路径尝试启动 HAL_I2C_Master_Abort_IT()，并等待外设恢复到 READY 状态。

请提供验证的bsp和config (provide the config and bsp)

• BSP: F4。

• .config: 验证 BSP_I2C*_USING_INT、BSP_I2C*_TX_USING_DMA、BSP_I2C*_RX_USING_DMA 组合。

• action: 当前离线环境未提供 action 链接。

]

当前拉取/合并请求的状态 Intent for your PR

必须选择一项 Choose one (Mandatory):

• 本拉取/合并请求是一个草稿版本 This PR is for a code-review and is intended to get feedback
• 本拉取/合并请求是一个成熟版本 This PR is mature, and ready to be integrated into the repo

代码质量 Code Quality：

我在这个拉取/合并请求中已经考虑了 As part of this pull request, I've considered the following:

• 已经仔细查看过代码改动的对比 Already check the difference between PR and old code
• 代码风格正确，包括缩进空格，命名及其他风格 Style guide is adhered to, including spacing, naming and other styles
• 没有垃圾代码，代码尽量精简，不包含#if 0代码，不包含已经被注释了的代码 All redundant code is removed and cleaned up
• 所有变更均有原因及合理的，并且不会影响到其他软件组件代码或BSP All modifications are justified and not affect other components or BSP
• 对难懂代码均提供对应的注释 I've commented appropriately where code is tricky
• 代码是高质量的 Code in this PR is of high quality
• 已经使用formatting 等源码格式化工具确保格式符合RT-Thread代码规范 This PR complies with RT-Thread code specification
• 如果是新增bsp, 已经添加ci检查到.github/ALL_BSP_COMPILE.json 详细请参考链接BSP自查

[github-actions]

👋 感谢您对 RT-Thread 的贡献！Thank you for your contribution to RT-Thread!

为确保代码符合 RT-Thread 的编码规范，请在你的仓库中执行以下步骤运行代码格式化工作流（如果格式化CI运行失败）。
To ensure your code complies with RT-Thread's coding style, please run the code formatting workflow by following the steps below (If the formatting of CI fails to run).

---

🛠 操作步骤 | Steps

1. 前往 Actions 页面 | Go to the Actions page
   点击进入工作流 → | Click to open workflow →

2. 点击 Run workflow | Click Run workflow

• 设置需排除的文件/目录（目录请以"/"结尾）
  Set files/directories to exclude (directories should end with "/")
• 将目标分支设置为 \ Set the target branch to：05-stm32-i2c
• 设置PR number为 \ Set the PR number to：11366

3. 等待工作流完成 | Wait for the workflow to complete
   格式化后的代码将自动推送至你的分支。
   The formatted code will be automatically pushed to your branch.

完成后，提交将自动更新至 05-stm32-i2c 分支，关联的 Pull Request 也会同步更新。
Once completed, commits will be pushed to the 05-stm32-i2c branch automatically, and the related Pull Request will be updated.

如有问题欢迎联系我们，再次感谢您的贡献！💐
If you have any questions, feel free to reach out. Thanks again for your contribution!

[github-actions]

📌 Code Review Assignment

🏷️ Tag: bsp_stm32

Reviewers: @Liang1795 @hamburger-os @wdfk-prog

Changed Files (Click to expand)

• bsp/stm32/libraries/HAL_Drivers/drivers/drv_hard_i2c.c

---

📊 Current Review Status (Last Updated: 2026-05-06 18:32 CST)

• ⌛ @Liang1795 Pending Review
• ⌛ @hamburger-os Pending Review
• ⌛ @wdfk-prog Pending Review

---

📝 Review Instructions

1. 维护者可以通过单击此处来刷新审查状态: 🔄 刷新状态
   Maintainers can refresh the review status by clicking here: 🔄 Refresh Status

2. 确认审核通过后评论 LGTM/lgtm
   Comment LGTM/lgtm after confirming approval

3. PR合并前需至少一位维护者确认
   PR must be confirmed by at least one maintainer before merging

ℹ️ 刷新CI状态操作需要具备仓库写入权限。
ℹ️ Refresh CI status operation requires repository Write permission.

[Copilot]

Pull request overview

This PR updates the STM32 hard I2C driver to make IRQ/DMA async transfers more robust by ensuring error interrupts can wake waiters and by adding a recovery/abort flow when async completion fails.

Changes / 变更：

• Enable both I2C event IRQ and error IRQ when using INT/DMA async paths; wake the waiting thread from HAL_I2C_ErrorCallback().
  启用 I2C event/error 中断并在错误回调中唤醒等待线程，避免等待超时卡死。
• Gate IRQ/DMA usage with async_allowed to avoid entering async wait paths when scheduler is unavailable or interrupts are disabled.
  增加 async_allowed 限制，避免在不允许调度/中断的上下文进入异步等待路径。
• Add an abort-and-wait-for-READY recovery path when async wait fails or HAL reports an error.
  在异步等待失败或 HAL 报错时尝试 Abort 并等待外设恢复到 READY。

Comments suppressed due to low confidence (2)

bsp/stm32/libraries/HAL_Drivers/drivers/drv_hard_i2c.c:229

• [maintainability/类别]: Misleading RT_UNUSED on used parameters / 对已使用参数的 RT_UNUSED 误用

English: In stm32_i2c_master_receive_start(), RT_UNUSED(i2c_obj), RT_UNUSED(mode), and RT_UNUSED(timeout) are declared, but these parameters are later dereferenced/used in the function. This is misleading for readers and may hide real unused-parameter issues in the future. Please remove RT_UNUSED(...) for parameters that are actually used.
中文：在 stm32_i2c_master_receive_start() 中声明了 RT_UNUSED(i2c_obj) / RT_UNUSED(mode) / RT_UNUSED(timeout)，但后续又实际解引用/使用了这些参数。这样会误导阅读者，也可能掩盖未来真正的未使用参数问题。建议删除对已使用参数的 RT_UNUSED(...)。

    RT_UNUSED(i2c_obj);
    RT_UNUSED(mode);
    RT_UNUSED(timeout);
    RT_ASSERT(i2c_obj != RT_NULL);

bsp/stm32/libraries/HAL_Drivers/drivers/drv_hard_i2c.c:283

• [maintainability/类别]: Misleading RT_UNUSED on used parameters / 对已使用参数的 RT_UNUSED 误用

English: In stm32_i2c_master_transmit_start(), RT_UNUSED(i2c_obj), RT_UNUSED(mode), and RT_UNUSED(timeout) are marked unused but later used. Please remove these RT_UNUSED(...) lines for the parameters that are actually referenced.
中文：在 stm32_i2c_master_transmit_start() 中把 i2c_obj/mode/timeout 标记为 RT_UNUSED，但后续又实际使用了它们。建议删除这些对已使用参数的 RT_UNUSED(...)，避免误导。

    RT_UNUSED(i2c_obj);
    RT_UNUSED(mode);
    RT_UNUSED(timeout);
    RT_ASSERT(i2c_obj != RT_NULL);