- Timestamp:
-
06/28/23 13:51:40 (12 months ago)
- Author:
-
Utkarsh Verma
- Comment:
-
Add weekly update
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v49
|
v50
|
|
136 | 136 | * Blocker: Getting used to the RTEMS codebase and understanding the principles before implementing the driver. |
137 | 137 | * Next week: Start with the GPIO driver implementation around the GPIO2 interface. |
| 138 | * **June 21**: Coding Period Week !#4 |
| 139 | * Last week's work: |
| 140 | * Discussed with mentors how to proceed with the firmware development. Seems that UARTs will be an easier target. |
| 141 | * Looked into PL011 initialization routines through datasheets, other drivers and bare metal projects. |
| 142 | * Blocker: N/A |
| 143 | * Next week: Flesh out drivers for UARTs in bare metal. |
| 144 | * **June 28**: Coding Period Week !#5 |
| 145 | * Last week's work: |
| 146 | * Implemented GPIO support in bare metal. |
| 147 | * Implemented support for all five UARTs in bare metal. |
| 148 | * Read the RPi 4B BSP source code and explored how it utilizes RTEMS' APIs. |
| 149 | * Blocker: UART drivers depend on GPIO functionality, which is not present in the BSP. For implementing GPIO, the API has to be chosen. |
| 150 | * Next week: Discuss the GPIO API with the community and implement support for all five UARTs. |