fix(uart): force a reset edge and configure RX/TX pull state in hal_uart_init() #121
No reviewers
Labels
No labels
Category
App
Category
Documentation
Category
Firmware
Category
Hardware
Category
Qms
PR_Size
L
PR_Size
M
PR_Size
S
PR_Size
XL
PR_Size
XS
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Priority
Very Low Priority
Size
Epic
Size
Feature
Size
Task
Status
Blocked
Status
Draft
Status
Needs-review
Team
Board
Team
Dev
Team
Management
Type
Bug
Type
Capa
Type
Improvement
Type
New-feature
Type
Regulatory
Type
Usability
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
opendutchsolutions.public/hal_awr6843!121
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/120-uart-reset-pull"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #120.
Two gaps found diffing
hal_uart_init()against a hardware-confirmed sibling driver while debugging a real UART failure report on a downstream consumer project:SCIGCR0.RESET = 1written directly, no0first -- a no-op if the module was already out of reset (plausible here: the SBL/flash tool uses this same SCI instance to receive the flashed image before jumping to the app).SCIPIO7/SCIPIO8(RX/TX pull disable/select) never written -- their reset values are pin/pad default-dependent per this project's own register header comments, not guaranteed.Both fixed, matching the SDK reference driver (
UartSci_open()) and a hardware-confirmed sibling project's own port of it.Local verification:
ctest: 403/403 passing (clean full rebuild)tools/misra/run_misra.sh): 0 findingsclang-format --dry-run --Werror: cleanPR_Size/S