lowRISC / lowRISC/opentitan

[spi_device] interrupts for unhandled flash commands

Open
#28,365 2 comments 0 reactions 0 assignees View on GitHub
IP:spi_device
Dominant language
SystemVerilog
Stars
3.6k
Forks
1.1k
Avg merge
2d 22h
Merged PRs (30d)
141

Description

When working on the QEMU SPI flash emulation I've noticed that our tests are receiving a lot of flash commands which we haven't configured slots for. Most commonly this will be the `WREN` and `EN4B`/`EX4B` commands.

QEMU has a helpful debug trace to warn about unhandled commands, but I was surprised the hardware doesn't have anything similar. I was expecting to find an interrupt or some kind of status register to tell Ibex when an unhandled flash command has arrived.

This would mostly be useful for logging warnings and finding bugs.

Contributor guide

Open the contributing guide

Research direction

The issue mentions QEMU SPI flash emulation, unhandled WREN and EN4B/EX4B commands, and Ibex. Start by tracing the existing SPI device command handling and checking how interrupts or status registers are represented. Done means the desired handling for unconfigured flash commands is designed and documented well enough to implement.

Written by the indexing model from the issue text.

Assessment

Domain
embedded-iot
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.