The overrun test needs to flush the fifo when it's done (it's a
deliberate error test).
Also remove access references to a peripheral that no longer exists
this allows us to build a simulation-focused xous image
this was previously called cramium-fpga but that precise
configuration is less accurate as the simulation environment
makes more shortcuts (and can include more peripherals)
than the fpga environment.
the backup flag can be left "hanging around" if a restore of PDDB
is aborted. This command allows a user to override that setting
in case this is necessary.
this all seems to work as expected now, next up: hooking the
interrupt handler for the IOX.
Probably should put the actual IRQ router in the HAL so that multiple
services can configure it, but have the handler actually invoke
a function in our address space.
programs should now use the usb-cramium crate for a USB
stack. It preserves the `lib` API, so you /should/ be able to
integrate it seamlessly by just renaming crates between
the two.
we're going to strip out the USB cramium support from this crate
eventually because it has migrated to a stand-alone crate
the hardware model is just too different to keep the two branches
in sync: one allows interrupts to be delegated to userspace, the other
requires the interrupts to happen all in the locked handler context
due to timing assumptions of the core.
the problem with the interrupt handler context is that panics
are really hard to debug - you can't actually send a panic message
from an interrupt context, because there is no IPC when the
handler is running. Normally we try to keep the handlers as
minimal as possible, but in this case we can't due to hardware
assumptions.
realizing a bunch of stuff like the stack expects you to enqueue
the OUT receiver with calls to read() that happen to block, fixing
max packet size that can be different for in and out end points,
and handling quirks of the core when sending setup packets longer than
64 bytes.
the UsbBus implementation is being totally rewritten for the
inside-out IRQ protected scheme.
we can now get past some preliminaries in the link protocol
(i.e., address setting and the first config descriptor), but
a long way to go still in debugging.