I've been trying to install the Graphics SDK (4.05.00.01) on a Z3 DM8168 board.
After installing to the target file system I run "rc.pvr start" and the response is "Loaded PowerVR consumer services" which seems correct.
However, if I run lsmod, the omaplfb module has not been loaded. Here is the output ...
root@arago:/etc/init.d# lsmodModule Size Used by Not taintedpvrsrvkm 155098 0ti81xxhdmi 14478 0ti81xxfb 21771 0vpss 72346 2 ti81xxhdmi,ti81xxfbipv6 209855 10syslink 1108763 0
If I then try and manually load omaplfb, I get the following output ...
root@arago:/etc/init.d# insmod /lib/modules/2.6.37/kernel/drivers/char/omaplfb.koinsmod: can't insert '/lib/modules/2.6.37/kernel/drivers/char/omaplfb.ko': Invalid argument
I built the Graphics SDK according the instructions and everything seemed to build correctly.
I wonder if anyone has seen the problem and knows what is the solution?
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 -
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 -
If my reply answers your question then please click on the "Verify Answer" button.
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.
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-
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.
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 -
Now before executing 38xx-demo script, ensure below bootargs, HDVPSS requirements are satisfied -
HDVPSS Requirements -
Essentially ensure the below steps have been executed successfully(without any errors or failures) before loading graphics drivers or running 38xx-demo script -
./slaveloader startup VPSS-M3 ti816x_hdvpss.xem3
insmod ti81xxfb.ko vram=0:24M,1:8M
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.
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.
Were you able to try/verify the suggestions provided? Any updates on the same?
Steve did you manage to get this to work?
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.