Anti-brick Register: Difference between revisions
From SpecNext Wiki
m 5 revisions imported |
No edit summary |
||
| Line 5: | Line 5: | ||
|ShortDesc=Used within the [[Anti-brick system]]. | |ShortDesc=Used within the [[Anti-brick system]]. | ||
}} | }} | ||
'''Read''' bit mapped: | '''Read''' bit mapped: | ||
{| class="wikitable" | {| class="wikitable" | ||
Revision as of 23:16, 19 April 2019
| Number | TBRegisterNumber::$10 |
|---|---|
| Readable | TBRegisterReadable::Yes |
| Writable | TBRegisterWritable::Yes |
| Short Description | [[ShortDesc::Used within the Anti-brick system.]] |
Read bit mapped:
| Bit | Effect |
|---|---|
| 7-2 | Reserved, 0 |
| 1 | DivMMC button pressed |
| 0 | Multiface button pressed |
Write bit mapped (only in config mode):
| Bit | Effect |
|---|---|
| 7 | If 1 start selected core, if 0 FPGA loads the fixed anti-brick core |
| 6-5 | Reserved, must be 0 |
| 4-0 | Core ID 0-31 (default is 2) |
Note that in normal running pressing the DivMMC or Multiface button creates an NMI which halts any running program, and the reflashable core must be loaded before any user code is run. This means that unless you are rewriting the entire firmware from scratch this register is probably not useful.