I got brand new apalis imx6 module with brand new ixora v 1.1 board. I have connected mouse keyboard a hdmi monitor. When I boot up I can see a lit blank screen. I tried 3 different working monitors.
I bought second pair of apalis and ixora and same issue. What is wrong ?
Is toradex shipping boards out without testing them
Our production test does certainly test HDMI output capability.
May I ask what BSP version you are running?
There were some known issues with certain HDMI screens in older BSPs. We therefore recommend installing the latest stable or alternatively beta BSP according to the following article on our developer website.
Please note that in the future all our modules will ship with our new Toradex Easy Installer pre-installed which will greatly simplify this process and improve on the out-of-the-box experience.
marcel.tx, how can I know BSP version, it was shipped from toradex and does not work out of the box… I cannot see anything…Serial port needs a special cable/connector which I do not have.
I have 2 v1.0A IXORA boards and they all work fine with the same setup, these 2 brand new IXORAs have issue (right out of the box).
It looks like screen lits up but is just BLANK. Sounds like some SW issue to me. What do you folks think ?
I was able to make serial port connector and hook it up with the Probalematic boards and attached is 1 sample.
Sounds like TOradex is shipping boards out with a very OLD BSP (sometime from 2015), Please double check my observation from the attached log file.
Here is the log file: link text
The Angstrom Distribution apalis-imx6 ttymxc0
Angstrom v2014.12 - Kernel 3.10.17
Apalis_iMX6_LinuxImageV2.4_20150518
Yes, but as mentioned before the pre-installed software is about to change.
Please give the Toradex Easy Installer a try.
Hi
Please note that the following page gives information on how to configure the display interface to be used and how to setup its resolution on the kernel command line.
The following is not a valid setting for i.MX 6 and will result in mxcfb0 not being assigned to HDMI and thus HDMI will have no output signal.
video=mxcfb0:1280x1080-24@60
As a first measure you could set back on the U-Boot console the U-Boot environment variable vidargs to its default:
env default vidargs
saveenv
Max
Please see my log file above, my serial console is asking me for login what do I enter there ? Some username and password is needed
Username is “root” and password is blank.
This is what I am getting:
root@apalis-imx6:~# env default vidargs
env: can’t execute ‘default’: No such file or directory
AND this is what I get after following the above mentioned link:
root@apalis-imx6:~# setenv vidargs 'mxc_hdmi.only_cea=1 video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24
video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off fbmem=32M’
-sh: setenv: command not found
I am trying but where is :
Windows: recovery-windows.bat ?
Tell me how to RMA boards back to you, this is a GIANT MESS>
Customer should NOT have to jump through hoops, to make just a very basic functionality work.
Please update my Boards SW and make HDMI work. I have spent 20 hours on this and I am very very upset at the way things are managed.
I can grantee you nobody at TORADEX has validated these boards for HDMI, they have used 1280*1080 resolution, I can see that from command history.
Please tell me how to RMA these boards, I am very tired and irritated
@Max mentioned to update the variables in U-Boot not via Linux terminal.
Please enter into U-Boot console via debug serial console and run the commands mentioned. If to update the U-Boot env variables via Linux terminal use fw_printenv/fw_setenv commands.
I represent Esperanza Consulting and ATIAK solutions (http://www.atiak.com/).
Message me your FAEs contact, I will try and reach him. I am based in Eastern USA.
A very very nice gentleman name Stefan from Toradex helped me reset the Toradex shipped Software by using the following command:
setenv vidargs 'mxc_hdmi.only_cea=1 video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24 video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off fbmem=32M'
not post boot, BUT after holding device in boot using serial console. And now the boards are working.
Thank you Toradex and Very special thanks to Stefan