Hi,
I want to rectify my last e-mail. It seemed to be a weird bug in the tool
suite that we are using, since it would be impossible that all the read-only
registers also had that same strange value, it did not happen again
either. I do have another question, however.
Has the driver ever been
Bastiaan Nijkamp wrote:
Has the driver ever been tested/used without a switch attached? Because when
the host (which has ID 0x0) enumerates the other board it also assigns ID 0x0
to the agent, it seems that the agent should have been assigned 0x1 as ID.
How the host ID is set on your host
Bastiaan Nijkamp bastiaan.nijk...@gmail.com wrote:
How the host ID is set on your host board?
Normally rio_enum_host() should increment next_destid in your case.
The hostID is set to 0x0 with the riohdid parameter as boot argument.
In this case I would expect to see ID=1 assigned to the
How the host ID is set on your host board?
Normally rio_enum_host() should increment next_destid in your case.
The hostID is set to 0x0 with the riohdid parameter as boot argument.
Make sure that you have the MASTER bit is set in agent's GCCSR register
(0xC_013C).
If your board uses HW config
Hi,
We have found a poorly documented jumper on our boards that force pci-mode
to 32bit instead of 64bit. It seems to have an effect on RapidIO aswell
since the host now completes the enumeration process including finding the
other board. However, as soon as the agent starts the peer discovery
Hi Bastian,
Bastiaan Nijkamp wrote:
It seems i forgot to include the relevant TLB entries in U-Boot and the
Device Tree in the e-mail, so here they are:
The TLB entries in U-Boot:
The kernel maintains the TLB, you must not set those in U-boot. It might
cause conflicts when the kernel
Subject: Re: Serial RapidIO Maintaintance read causes lock up
Hi John,
1. Yes, they are both running the exact same kernel and both are configured in
the same way. With the exception that one is set as host and the other as a
agent.
2. Accept All is set for both boards.
3. As i understand
Hi Alex,
Thanks for your advice. We are trying to make a board-to-board connection
without any additional hardware (eg. a switch). The boards use a 50-pin,
right-angle MEC8-125-02-L-D-RA1 connector from SAMTEC and are connected
trough a EEDP-016-12.00-RA1-RA2-2 cross cable from SAMTEC. I hope
Hi Bastiaan,
Bastiaan Nijkamp bastiaan.nijk...@gmail.com wrote:
fsl-of-rio e00c.rapidio: LAW start 0xc000, RIO
Maintainance Window Size 0x40,New Main Start: 0xd108
RIO: enumerate master port 0, RIO0 mport
fsl_rio_config_read: index 0 destid 255 hopcount 0 offset
Bastiaan,
On 05/10/10 15:28, Bastiaan Nijkamp wrote:
Hi John,
1. Yes, they are both running the exact same kernel and both are
configured in the same way. With the exception that one is set as host
and the other as a agent.
2. Accept All is set for both boards.
3. As i understand, the agent
Bastiaan Nijkamp bastiaan.nijk...@gmail.com wrote:
A interesting thing that i found out is that when the agent is reset while the
host is locked up (eg. it cannot be stopped nor can i read the registers and
memory trough a JTAG Interface), the host comes back online and just
continues
Hi Alex,
Yes, Sorry, that was a typo. The correct address that is printed is
0xd1080068.
And i did not disable the error handler, CONFIG_E500 is set at compile time.
Regards,
Bastiaan
2010/10/5 Bounine, Alexandre alexandre.boun...@idt.com
Hi Bastiaan,
Bastiaan Nijkamp
Hi,
It seems i forgot to include the relevant TLB entries in U-Boot and the
Device Tree in the e-mail, so here they are:
The TLB entries in U-Boot:
/*
* TLB 3: 256M Non-cacheable, guarded
* 0xc000 256M Rapid IO MEM First half
*/
SET_TLB_ENTRY(1, CONFIG_SYS_RIO_MEM_VIRT,
13 matches
Mail list logo
