Forums

Hi Steve,

Can you share the exact build command you used?

Hope you are following the build, execution instructions & matching your output to the one mentioned in below link -

http://processors.wiki.ti.com/index.php/Graphics_SDK_Quick_installation_and_user_guide#Build_steps

http://processors.wiki.ti.com/index.php/Graphics_SDK_Quick_installation_and_user_guide#Execution_instructions

Can you ensure the below steps in sequence -

1) Build the kernel(PSP release) first (make uImage modules)

2)Build the graphics SDK release against this built kernel (built in step 1) (make BUILD=release OMAPES=6.x all_km)

3)Install the graphics SDK to the target file system (sudo make BUILD=release OMAPES=6.x install)

Follow the procedures as mentioned in user guide.

Ensure that the .kos getting inserted are the ones that got built in step 2 & not older .kos getting inserted with new kernel built or vice versa.

Also if you are not aware, we made a graphics SDK release 04.06.00.01 last week. Its available for download at -

http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/gfxsdk/latest/index_FDS.html

Thanks,

Prathap.

Hi Prathap,

I believe I am following the instructions exactly.

First of all I am running makeall.sh (Z3) which builds and installs everything (Linux kernel, all EZSDK components).

Next, I build and install the Graphics SDK using the following commands:

make BUILD=release OMAPES=6.x FBDEV=yes INSTALL_XORG=0 all

make BUILD=release OMAPES=6.x install

Then, on the target system, I run 38xx-demo.sh and restart the target.

When I run rc.pvr start, things seems to be working but I notice that omaplfb.ko is not loaded.

If I try to manually load omaplfb.ko, I get the error mentioned in my first post. pvrsrvkm.ko loads with no problem. bufferclass_ti.ko loads with no problem.

I have tried both the 4.05 and 4.06 versions and the behaviour is exactly the same.

I wonder if omaplfb.ko is dependent on some other module or on some kernel setting that is different between the Z3 RDK and the TI RDK.

Thanks,

Steve

Hi Steve,

The error message that you had provided earlier - omaplfb.ko fails with message invalid argument.

This typically indicates some mismatch between the .ko & kernel built.  What command did you use to build the kernel?. Did you do make modules while building the kernel & then later build the graphics SDK against this kernel?

Can you ensure(by checksum, time stamp) that the .ko built in graphics SDK under folder gfx_rel_es6.x is same as the one you are trying to insmod on target & you are indeed booting up with the right/expected kernel image.

Also share your dmesg logs before & after .ko insertion.

The dependancy of graphics SDK kernel modules are-  you should have inserted the syslink module,slaveloader app running successfully along with HDVPSS kernel modules inserted successfully. 

Can you share the bootargs, step by step output of each step mentioned under sections - step 1 & step2 below-

http://processors.wiki.ti.com/index.php/Graphics_SDK_Quick_installation_and_user_guide#Execution_instructions

You may also try debug build (pass BUILD=debug while build & install of graphics SDK) which may provide more clues on what is going wrong with your setup.

Thanks,

Prathap.

Hi Steve,

Were you able to verify the dependencies mentioned in my last post. From a graphics SDK perspective these are the dependencies/requirements to be satisfied. I am listing them again below for reference-

Some checks to be done -

=========================

1)make modules was done first on the kernel & then graphics SDK was built against this kernel.

2)Ensuring the .kos built on host Linux PC (found under gfx_rel_es6.x folder of graphics SDK release) are the ones that are getting inserted.

3)dmesg logs before & after insertion of .kos.

Kernel Requirements/dependencies to be satisfied before building graphics SDK -

=================================================================

http://processors.wiki.ti.com/index.php/DM816X_AM389X_VPSS_Video_Driver_User_Guide#Build_Linux_VPSS.2C_Fbdev.2C_V4L2_Display_and_V4L2_Capture_Drivers

http://processors.wiki.ti.com/index.php/RN_4_06_00_01#Pre-requisites

Now before executing 38xx-demo script, ensure below bootargs, HDVPSS requirements are satisfied -

http://processors.wiki.ti.com/index.php/DM816X_AM389X_VPSS_Video_Driver_User_Guide#Read_This_First

Bootargs -

http://processors.wiki.ti.com/index.php/Graphics_SDK_Quick_installation_and_user_guide#Execution_instructions

HDVPSS Requirements -

=====================

http://processors.wiki.ti.com/index.php/DM816X_AM389X_VPSS_Video_Driver_User_Guide#Load_VPSS.2C_Fbdev.2C_and_V4L2_Display_Driver_Modules

Essentially ensure the below steps have been executed successfully(without any errors or failures) before loading graphics drivers or running 38xx-demo script -

insmod syslink.ko

./slaveloader startup VPSS-M3 ti816x_hdvpss.xem3

insmod vpss.ko

insmod ti81xxhdmi.ko

insmod ti81xxfb.ko vram=0:24M,1:8M

Thanks,

Prathap.

Hi Prathap,

I have had to switch to other tasks at the moment. I will try and get back to this asap.

Thanks for your detailed posts.

Steve

Hi Steve,

Welcome. No problem. You can update about this whenever you try this.

Also please click on the verified answer if the suggestions provided helps to resolve the issue.

Thanks,

Prathap.

Hi Steve,

Were you able to try/verify the suggestions provided? Any updates on the same? 

Thanks,

Prathap.

Steve did you manage to get this to work?