Commit ec6ffd8
psram: diagnostic -- read HyperBus device ID + CR0 back (bounded) to see if it responds + if CR0 write landed
Research (datasheet + GitHub forks) reframed the wall: the Winbond HyperBus bring-up is UNIMPLEMENTED everywhere (stub in 7 repos; PebbleOS powers PSRAM off; PR coredevices#1602 QEMU-only). HAL_HYPER_PSRAM_Init has 3 defects: cal runs before DCR.HYPER is set (OPI framing), CR0 latency written after cal, no HyperBus reset. -75 showed re-cal after HYPER+CR0 still fails, so before rewriting the init, read ID0/ID1/CR0/CR1 back over HyperBus (HAL_HYPER_PSRAM_ReadID/ReadCR, bounded TCF spin so no hang) to learn: does the device respond in HyperBus framing, and did the CR0 write (expect 0x178f @144mhz) land? Diagnostic only.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>1 parent af74c2a commit ec6ffd8
1 file changed
Lines changed: 14 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
475 | 475 | | |
476 | 476 | | |
477 | 477 | | |
| 478 | + | |
| 479 | + | |
| 480 | + | |
| 481 | + | |
| 482 | + | |
| 483 | + | |
| 484 | + | |
| 485 | + | |
| 486 | + | |
| 487 | + | |
| 488 | + | |
| 489 | + | |
| 490 | + | |
| 491 | + | |
478 | 492 | | |
479 | 493 | | |
480 | 494 | | |
| |||
0 commit comments