Re: [Discuss OpenCPI] Container Issue

From: Neil Schafer <neil.schafer_at_nrl.navy.mil>
Date: Mon, 16 Jul 18 12:16:33 -0400

Running load gives me the line:
"No reserved DMA memory found on the linux boot command line
Driver loaded successfully"

Is there a verbose mode?

-----Original Message-----
From: discuss <discuss-bounces_at_lists.opencpi.org> On Behalf Of James Kulp
Sent: Monday, July 16, 2018 11:20 AM
To: discuss_at_lists.opencpi.org
Subject: Re: [Discuss OpenCPI] Container Issue

It looks like it is failing to recognize that the driver is loaded.
This usually indicates some sort of udev/mdev failure.
I.e. the /dev entries for OpenCPI are not getting created or not created
properly when the driver is loaded.
Did ocpidriver say anything about udev/mdev rules?


On 7/16/18 11:07 AM, Neil Schafer wrote:
> Hi,
>
>
>
> I'm working on a newish bsp, in an external project that has been
registered
> and built within my core ocpi framework. I have successfully flashed an
> opencpi-built assembly to the device (using vendor tools), but opencpi
sort
> of fails to recognize the container. I have loaded the ocpidriver, but
when
> I run ocpirun -C, I get:
>
> OCPI( 2:947.0314): When searching for PCI device '0000:02:00.0': Can't
open
> /dev/mem, forgot to load the driver? Sudo?
>
>
>
> The PCI address listed above is the correct address for the flashed
device.
>
>
>
> Running ocpirun -C -l10 reveals
>
> "Searching for local PCI-based HDL devices.
>
> When searching for PCI device '0000:02:00.0': Can't open /dev/mem.. Etc"
>
>
>
> Is there some other step I may have missed for providing permissions?
>
>
>
> Thanks,
>
> Neil
>
>


Received on Mon Jul 16 2018 - 16:16:33 CDT