FEDEVEL
Platform forum

paul_aldana , 10-20-2016, 09:30 AM

Hello,

I'm fairly new to the iMX6 Rex and I've followed all the necessary steps from the development baseboard manual. After I've restarted the board after saving the u-boot parameters, I tried running the GUI with the "startx" command. The Rex just freezes up at "loading extension vivext".

Does anyone know how to work around this issue?

Thanks,

Paul

robertferanec , 10-20-2016, 11:18 AM

Did you try (http://www.imx6rex.com/software/imx6...-tests/#hdmi):

paul_aldana , 10-24-2016, 04:17 PM

Hello Robert,

Sorry took me a while to reply back to this. I was sidetracked by other projects. Anyways, I tried the steps from the "HDMI" part of the link you provided until "startx &".
Through the steps, the system could not find the "dfs.avi" file and could not play the video to the HDMI. I was able to display an image of 3 penguins to the HDMI display although the image is distorted by horizontal lines by using the "echo 0 ..." command. When I tried doing the "export DISPLAY=:0.0" and "startx &", it still gets stuck in the "Loading extension vivext".

Are the boards not updated before they get shipped out to customers?

robertferanec , 10-24-2016, 04:31 PM

Paul, I know, that VOIPAC tests all the boards before they ship them. However, I am not sure with what software your board was shipped with - if the command line only or with a GUI. I will double check with them. In the mean time, please describe all the steps what you have done, especially "After I've restarted the board after saving the u-boot parameters" - this seems to me very unusual, is it this (point 8)? http://www.imx6rex.com/software/getting-started/
Also, please attach the booting log. Thank you.

paul_aldana , 10-24-2016, 04:39 PM

I've followed everything in this link, http://www.imx6rex.com/software/getting-started/ , wherein we needed to update the network configuration of the board. I do not have the ethernet cable connected as it says it's optional anyways (I also do not have access to our network). After saving the u-bot parameters and restarting the board (as stated in step 8 of the "Getting Started" manual), that's when I first tried the "startx" which was my first issue in this post.

After you posted the link on how to access the peripherals of the rex, I tried to do the "HDMI" part of the guide, which resulted to the same issue of getting stuck at "Loading extension vivext" and also not being able to locate the "dfs.avi" file when trying to play video to the HDMI display.

robertferanec , 10-24-2016, 04:54 PM

The booting log may help. Please, contact VOIPAC directly and send them information about your board / order number.

If you like, you can try this file system, this will boot up to GUI: http://www.imx6rex.com/open-rex/soft...system/#copied

PS: I don't think VOIPAC is shipping the boards with our "dfs.avi" test video. You may need to find your own test video file.

paul_aldana , 10-24-2016, 04:58 PM

Here's the booting log.

robertferanec , 10-24-2016, 05:02 PM

I think, this is the correct file system which should boot up to GUI when you run the commands. Can you show me how it is stacked? When you run it with "&" and you press enter, you should be able to work with the console.

Also, do not forget. To support HDMI, you need to update the uBoot environmental variables according the steps here (especially the part with "video=mxcfb0:dev=hdmi,1280x720M@60,if=RGB666 vmalloc=400M fbmem=28M fbcon=28M" is important): http://www.imx6rex.com/software/imx6...on-tests/#hdmi

paul_aldana , 10-24-2016, 05:04 PM

Do you know what VOIPAC included inside the SD card?

paul_aldana , 10-24-2016, 05:06 PM

The system just freezes when I do the "startx &"

paul_aldana , 10-24-2016, 05:10 PM

But shouldn't it be showing the GUI already to my HDMI display by this time? I pressed enter and nothing is showing to the HDMI display.

robertferanec , 10-24-2016, 05:10 PM

I think, the problem is, because you used

"setenv bootargs_mmc 'setenv bootargs ${bootargs} ip=192.168.1.78:::255.255.255.0 root=/dev/mmcblk0p1 rootwait'" .. this will remove support for hdmi.

You need to put it back:

"setenv bootargs_mmc 'setenv bootargs ${bootargs} ip=192.168.10.86:::255.255.255.0 root=/dev/mmcblk0p1 rootwait video=mxcfb0:dev=hdmi,1280x720M@60,if=RGB666 vmalloc=400M fbmem=28M fbcon=28M'"

robertferanec , 10-24-2016, 05:12 PM

It will not show up if you do not have the "HDMI"in the bootargs.

paul_aldana , 10-24-2016, 05:31 PM

Aha! I got it to work! It is just that one part! Although I didn't change the "setenv bootargs_nfs" before "saveenv; reset" to get it to show up on my HDMI display.

One problem down and more to go!

Thank you so much for your help, Robert! You're the best!

robertferanec , 10-24-2016, 05:40 PM

Perfect