RapidIO: MC Exception when enumerating peer to peer connection
Bounine, Alexandre
Alexandre.Bounine at idt.com
Tue Nov 2 02:58:08 EST 2010
Thomas Taranowski wrote:
> Yes, I tried pretty much all combinations of boot order, but I believe
> the preferred approach is to boot the agents first, then the host
> according to my freescale documentation. My problem was that all
> three devices had the same device id. Once I programmed them with
> different device id's via the alternate device id register I could
> finally get doorbell messages across with the jtag.
In the current fsl_rio implementation initialization enables ACCEPT_ALL
mode for the port therefore you should not have problems caused by
initial destID value. Based on your post about multiport support I think
you are close to find a source of the problem.
Are you using any switches in your setup or this is pure board-to-board
configuration?
Alex.
More information about the Linuxppc-dev
mailing list