Hi,
Does anybody have experience of running QNX on standalone Unity board (without SandPoint
motherboard).
As far as I understood changes should include:
1. Adjusted IPL
2. Startup code (remove south bridge init, add MPC107 init code)
3. PCI driver (use MPC107 instead of WinBond device)
4. Serial driver (use built-in UART instead of NatSemi 93k)
Am I missing something?
--
Regards,
Alex
PPC8245 in standalone mode (without Sandpoint)
Re: PPC8245 in standalone mode (without Sandpoint)
Alex Ivchenko <alexx@ueidaq.com> wrote:
the WinBond's interrupt controller (8259). You also need to configure
the debug device appropriately.
with the 107.
all vectors are handled (specifically the on-board devices). This is handled
by Startup's interrupt callouts.
Otherwise, the built-in uarts are 8250 compatible.
--
John
In startup, you'll need to remove the interrupt callouts that deal withHi,
Does anybody have experience of running QNX on standalone Unity board (without SandPoint
motherboard).
As far as I understood changes should include:
1. Adjusted IPL
2. Startup code (remove south bridge init, add MPC107 init code)
the WinBond's interrupt controller (8259). You also need to configure
the debug device appropriately.
We actually only configure a few things on the Winbond. We mainly deal3. PCI driver (use MPC107 instead of WinBond device)
with the 107.
This may require some changes to the EPIC interrupt controller. Im not sure4. Serial driver (use built-in UART instead of NatSemi 93k)
all vectors are handled (specifically the on-board devices). This is handled
by Startup's interrupt callouts.
Otherwise, the built-in uarts are 8250 compatible.
--
John