Provides the STM32Cube MCU Component "hal_driver" of the STM32F4 series.
active 2023-08-17 → 2024-10-18 (UTC)
Complete coverage26,787 / 26,787 hourly files (100%) · 2 absent upstream2023-08-15 → 2026-09-04 (UTC)
Events
143
Pushes
11
Pull requests
2
Issues
22
Stars
59
Forks
14
Activity over time
Daily event counts in the loaded window
Line chart, 429 days from 2023-08-17 to 2024-10-18. Pushes: 11 total, peak 1 in a day. Pull requests: 2 total, peak 1 in a day. Issues: 22 total, peak 2 in a day. Comments: 33 total, peak 5 in a day. Stars: 59 total, peak 3 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| KRASTM | 15 | 3 | 0 | 9 |
| TOUNSTM | 11 | 5 | 1 | 2 |
| ALABSTM | 10 | 0 | 0 | 8 |
| HYP96 | 9 | 0 | 0 | 5 |
| RJMSTM | 8 | 3 | 0 | 3 |
| FT9R | 3 | 0 | 0 | 2 |
| HBOSTM | 2 | 0 | 0 | 1 |
| lebakassemmerl | 2 | 0 | 0 | 1 |
| SimonTechv | 2 | 0 | 0 | 1 |
| Narukara | 1 | 0 | 1 | 0 |
| fre-ros | 1 | 0 | 0 | 0 |
| wylerAgy | 1 | 0 | 0 | 0 |
| litesky | 1 | 0 | 0 | 0 |
| user-redans | 1 | 0 | 0 | 0 |
| amir1387aht | 1 | 0 | 0 | 1 |
Recent activity
Latest issues, pull requests and releases
- Issue#35fre-ros2024-10-18 13:32CRYP_GCMCCM_SetHeaderPhase out bounds write in mask array
- Issue#34KRASTM2024-09-25 15:18an issue in using HAL_UARTEx_ReceiveToIdle_DMA
- Issue comment#29KRASTM2024-09-11 13:32Going beyond the address space of external QUAD SPI FLASH memory.
- Issue comment#29SimonTechv2024-09-11 08:11Going beyond the address space of external QUAD SPI FLASH memory.
- Issue comment#29KRASTM2024-09-09 10:12Going beyond the address space of external QUAD SPI FLASH memory.
- Issue comment#34KRASTM2024-08-27 15:05an issue in using HAL_UARTEx_ReceiveToIdle_DMA
- Issue comment#34KRASTM2024-08-27 14:47an issue in using HAL_UARTEx_ReceiveToIdle_DMA
- Issue comment#34amir1387aht2024-08-27 03:07an issue in using HAL_UARTEx_ReceiveToIdle_DMA
- Issue#34litesky2024-08-27 03:05an issue in using HAL_UARTEx_ReceiveToIdle_DMA
- Issue comment#33ALABSTM2024-08-23 17:06The TxE flag should never be cleared through the I2C's DR register at any time.
- Issue#33ALABSTM2024-08-23 17:06The TxE flag should never be cleared through the I2C's DR register at any time.
- Issue comment#31ALABSTM2024-08-19 16:47Update interrupt flag in TIMx->SR is not cleared upon Time Base configuration
- Issue comment#31ALABSTM2024-08-19 16:12Update interrupt flag in TIMx->SR is not cleared upon Time Base configuration
- Issue comment#33HYP962024-08-15 16:46The TxE flag should never be cleared through the I2C's DR register at any time.
- Issue#33HYP962024-08-15 16:42The TxE flag should never be cleared through the I2C's DR register at any time.
- Issue#32KRASTM2024-08-14 09:48The TxE flag should never be cleared through the I2C's DR register at any time.
- Issue comment#31FT9R2024-08-08 18:29Update interrupt flag in TIMx->SR is not cleared upon Time Base configuration
- Issue comment#32KRASTM2024-08-02 15:22The TxE flag should never be cleared through the I2C's DR register at any time.
- Issue comment#32HYP962024-08-02 06:34The TxE flag should never be cleared through the I2C's DR register at any time.
- Issue comment#32KRASTM2024-07-29 15:23The TxE flag should never be cleared through the I2C's DR register at any time.
- Issue#33HYP962024-07-26 14:00The TxE flag should never be cleared through the I2C's DR register at any time.
- Issue comment#33RJMSTM2024-07-25 12:01The TxE flag should never be cleared through the I2C's DR register at any time.
- Issue comment#31FT9R2024-07-25 05:47Update interrupt flag in TIMx->SR is not cleared upon Time Base configuration
- Issue#33HYP962024-07-25 02:06The TxE flag should never be cleared through the I2C's DR register at any time.
- Issue#32HYP962024-07-25 02:06The TxE flag should never be cleared through the I2C's DR register at any time.
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 59 stars here means stars gained during the window, not the repo's star count.