Roadmaps / BeagleBone / How the plan works
Read first
How the plan works
Time model. One study week is 8 hours: about 2 hours of reading, 5 at the bench and 1 for review. The core path is 16 weeks, 128 hours. Optional stretch work adds about 30 hours (5 items of about 5 hours), so the full path is 153 hours. Fresher pacing: plan 20 weeks (160 hours): six weeks each for Phases 3 and 4, with the extra weeks spent on debugging and the Checkpoint 3 and 4 reruns. At 5 hours a week, allow 26 weeks for the core path; at 4 hours, 32. Week 0 is an extra 12 hours and is optional. Practice projects are the bench time of their weeks, not extra hours.
Every phase has the same parts. A weekly table, up to three practice projects, up to five repositories to read, one milestone checkpoint, and five questions to check yourself. The checkpoint is the point of the phase. The weekly deliverables are steps toward it.
Scoring. Score each checkpoint yourself, then ask one other engineer to score it. Use six dimensions: specification and budgets; trade-offs and decisions; verification and correctness; measurement on real hardware; failure handling and safety; communication and influence. Use four levels: 1 Works on your desk; 2 Sound (specified, tested and repeatable: a stranger can rerun your captures); 3 Proven (trade-offs measured, holds at the limits, a seeded fault is caught); 4 Leading (a method other teams reuse, with a measured outcome). If you have no second engineer, post your hand-in on the Beagle forum, score it against these levels, and cap your self-score at 2. This roadmap judges the checkpoints like this:
| Checkpoint | Judged mainly on |
|---|---|
| 1 Baseline harness | Measurement; verification |
| 2 Hardware description | Specification; verification; failure handling |
| 3 PRU step engine | Measurement; trade-offs; failure handling |
| 4 Shippable image | Failure handling; communication; trade-offs |
Three rules of the bench. Read the manual and the errata before you blame your code. Measure first, and keep the capture that proves the number. Add power and wiring in small steps. Write your prediction before each measurement; the deliverables of Weeks 4, 8, 12 and 16 compare predicted and measured numbers.