Apalis TK1 video player

Technical Support
, , ,
1

Hello!

Tell me please, How I can install any gui video player?

I need to media player to be able to play *.wmv files.

I’ve tried to install vcl mplayer smplayer and other.

gst player don’t work too.

root@apalis-tk1-mainline:~# gst-play-1.0 test.wmv 
Press 'k' to see a list of keyboard shortcuts.
Now playing /home/root/test.wmv
WARNING No decoder available for type 'audio/mpeg, mpegversion=(int)1, mpegaudioversion=(int)1, layer=(int)3, rate=(int)48000, channels=(int)2, parsed=(boolean)true'.
WARNING debug information: ../../../gst-plugins-base-1.8.3/gst/playback/gsturidecodebin.c(939): unknown_type_cb (): /GstPlayBin:playbin/GstURIDecodeBin:uridecodebin0
ERROR Your GStreamer installation is missing a plug-in. for file:///home/root/test.wmv
ERROR debug information: ../../../gst-plugins-base-1.8.3/gst/playback/gsturidecodebin.c(1006): no_more_pads_full (): /GstPlayBin:playbin/GstURIDecodeBin:uridecodebin0:
no suitable plugins found:
../../../gst-plugins-base-1.8.3/gst/playback/gstdecodebin2.c(4565): gst_decode_bin_expose (): /GstPlayBin:playbin/GstURIDecodeBin:uridecodebin0/GstDecodeBin:decodebin0:
no suitable plugins found:
Missing decoder: MPEG-1 Layer 3 (MP3) (audio/mpeg, mpegversion=(int)1, mpegaudioversion=(int)1, layer=(int)3, rate=(int)48000, channels=(int)2, parsed=(boolean)true)

Reached end of play list.

Help me)

Thank you!

2

Unfortunately our mainline BSP does not support any video playback as of yet. Please use our regular BSP which should support video playback through gstreamer. If you prefer a graphical player UI have a look at our JetPack article.

3

Thank you for your answer!

It’s helpfull article, but i got some problems.

I boot my apalis by nfs. But i can’t do this because after kernel booting my /sys and /proc directoies is empty.

And kernel show message that /sys/fs/selinux is not found. I tried find mistakes in init or systemd deamons but I couldn’t.

Can you help me?

4

I assume you consulted the following article already. Which exact BSP flavor are you now using? Attaching a complete boot log may be useful as well.

5

Yes, I saw this this article.

I’m using Toradex Apalis TK1 Embedded Linux BSP V2.7 Beta 1.

/bin/bash starts without init that mean nfs works. But if I run linux with init I have got this log

6

Yes, I saw this article.

I’m using Toradex Apalis TK1 Embedded Linux BSP V2.7 Beta 1.

To me it rather looks like you are not only using a custom U-Boot e.g.:

U-Boot 2015.04-00038-g1c0a0a2-dirty (Mar 16 2017 - 13:56:41)

And a custom Linux kernel e.g.:

Linux version 3.10.40-gb7874e0-dirty (artem@artem-PC) (gcc version 5.4.0 20160609 (Ubuntu/Linaro 5.4.0-6ubuntu1~16.04.4) ) #5 SMP PREEMPT Tue Mar 21 14:51:38 MSK 2017

But also a custom root file system.

Could you elaborate some more what exactly that customisation comprises?

Have you ever tried the same using our regular binary Apalis TK1 Embedded Linux BSP V2.7 beta 1 demo image package?

/bin/bash starts without init that mean nfs works. But if I run linux with init I have got this log

I do know that using our regular BSP demo images booting via TFTP/NFS works just fine but to understand what exactly may go wrong in your case I would have to understand more clearly what exactly you are doing.

7

So, Yes I have tried using your Apalis TK1 Embedded Linux BSP V2.7 beta 1. But I crafted my uboot because kernel was not run with standard uboot.

My kernel have this number commit b7874e0bdcaf97c808c1504cd61d2fa500ce250e.
My uboot have this number commit 1c0a0a22eb107fe75f87eae6263027734fa62c5d.

But linux have been runing when I use standard rootfs BSP. But when I use rootfs jetson tk1 I have had problem.

Thanks for you answer.

8

So, Yes I have tried using your Apalis TK1 Embedded Linux BSP V2.7 beta 1. But I crafted my uboot because kernel was not run with standard uboot.

Would be interesting to know what exactly it was that did not work for you.

My kernel have this number commit b7874e0bdcaf97c808c1504cd61d2fa500ce250e.

OK, so you are using latest -next stuff.

My uboot have this number commit 1c0a0a22eb107fe75f87eae6263027734fa62c5d.

That probably was a previous -next version. You have to understand that the -next stuff is really work in progress and may change at any time and is therefore not quite intended for regular development.

But linux have been runing when I use standard rootfs BSP. But when I use rootfs jetson tk1 I have had problem.

I have to admit I don’t think I ever run the Jetson stuff via NFS, so maybe Ubuntu ARM has some limitation in that respect. I’m also not that much into Ubuntu to be honest.

Thanks for you answer.

You are very welcome.

9

Would be interesting to know what exactly it was that did not work for you.

Rootfs jetson tk1 doesn’t work for me not via NFS and not via MMC.
Actually, daemon init doesn’t start to the end.