Legacy FIRM PXI: Difference between revisions
No edit summary |
fun thing |
||
Line 37: | Line 37: | ||
| 0x0008.... | | 0x0008.... | ||
| [[1.0.0-0]] | | [[1.0.0-0]] | ||
| | | Stubbed, returns 0xE0C0EC03... | ||
|- | |- | ||
| 0x0009.... | | 0x0009.... | ||
| [[1.0.0-0]] | | [[1.0.0-0]] | ||
| | | Stubbed, returns 0xE0C0EC03... | ||
|- | |- | ||
| 0x000A.... | | 0x000A.... | ||
Line 55: | Line 55: | ||
| This writes the input 0x80-byte ASCII data to [[Flash_Filesystem|nand:/rw/sys/lgy.log]]. | | This writes the input 0x80-byte ASCII data to [[Flash_Filesystem|nand:/rw/sys/lgy.log]]. | ||
|} | |} | ||
This PXI service seems to be based on [[Development Services PXI]]. Commands 0x8 and 0x9 in both are stubbed with the same function (returns 0xE0C0EC03), commands that seem useless under NATIVE_FIRM have a purpose on legacy FIRMs (command 0xC does some "unnecessary copying to stack" on NATIVE_FIRM, but this same copy (0x80-bytes) is used to write to lgy.log on legacy FIRMs), and commands that are essential (and only useful) on legacy FIRMs (0x2 and 0x3) are stubbed completely on NATIVE_FIRM. | |||
=Command 0x2= | =Command 0x2= |