Difference between revisions of "83Plus:BCALLs:8072"
From WikiTI
(first packet) |
|||
| Line 9: | Line 9: | ||
=== Inputs === | === Inputs === | ||
* 5,(iy+1Bh): reset for I/O, set for USB | * 5,(iy+1Bh): reset for I/O, set for USB | ||
| + | * [[83Plus:RAM:867D|ioData]]: contents of first packet | ||
=== Outputs === | === Outputs === | ||
| Line 17: | Line 18: | ||
== Comments == | == Comments == | ||
| + | When receiving an OS over DBUS, the first packet (i.e., the "variable header" for the OS header) must have been received and its contents stored to (ioData). | ||
| + | |||
The OS MUST be marked invalid with [[83Plus:BCALLs:8093|MarkOSInvalid]] before BCALLing this entry point, which requires unlocking Flash. | The OS MUST be marked invalid with [[83Plus:BCALLs:8093|MarkOSInvalid]] before BCALLing this entry point, which requires unlocking Flash. | ||
Latest revision as of 10:17, 6 March 2007
Synopsis
Unofficial Name: ReceiveOS
BCALL Address: 8072
Receives an operating system from another device and then reboots.
Inputs
- 5,(iy+1Bh): reset for I/O, set for USB
- ioData: contents of first packet
Outputs
- None
Destroys
- All
Comments
When receiving an OS over DBUS, the first packet (i.e., the "variable header" for the OS header) must have been received and its contents stored to (ioData).
The OS MUST be marked invalid with MarkOSInvalid before BCALLing this entry point, which requires unlocking Flash.
It is likely that 80F6 receives the OS through direct USB on the 84+/SE.
This will not return for any reason; it can also display all kinds of error messages about low batteries, transfer errors, or manually interrupting it (pressing ON).
