Setting Audio output to Jack instead of HDMI

Someone else mentioned audio problems yesterday toward the end of the ask-the-expert thread, so I'm investigating at the moment.  line out did work at one point as I'd tested it at the time, but something has changed somewhere between then and now, so I'll have to backtrack to see if I can find it.

HDMI audio isn't going to work at this point either I'm afraid. While some patches for this do exist, they're still in a state of flux and it's not clear what version if any will make the cut.

As I've said before, mainline kernel isn't for everyone - things will be missing or get broken along the way.  It is important to work towards getting mainline functional though as it benefits everyone in the long term.  So your testing and letting us know of any problems is appreciated !

Hi,

Thanks for your insight.

I will try to flash to stock Ubuntu and check it once.

The problem with the stock ubuntu is that its resolution requires me to connect the serial debug and change the boot parameters.

If any one can help me with these U-boot parameters it would be really a big relief. As I still far behind my project in terms of making a Audio Video to work from this board.

Thanks in advance.

Warm Regards,

Abhijit

Take a look at http://www.element14.com/community/docs/DOC-68087/l/riotboard-updating-os-images-in-linux-environment which details how to get ubuntu onto an SD card. This should avoid needing to change anything apart from the boot switches.

Hi,

I am flashing it the way as per the user manual.

I just need help in getting the uboot configuration to change the hdmi video resolution.

Please help me do that.

Warm Regards,

Abhijit

hi abhijit,

plz try the below

MX6Solo RIOT U-Boot > setenv bootargs console=ttymxc1,115200 init=/init nosmp video=mxcfb0:dev=hdmi,1280x720M@60,bpp=32

video=mxcfb1:off fbmem=10M vmalloc=400M androidboot.console=ttymxc1 androidboot.hardware=freescale

 

MX6Solo RIOT U-Boot > saveenv

Thanks

Tushar

Hello,

I have tried this with two alternate forms.

setenv bootargs console=ttymxc1,115200 init=/init nosmp video=mxcfb0:dev=hdmi,1280x720M@60,bpp=32video=mxcfb1:off fbmem=10M vmalloc=400M androidboot.console=ttymxc1 androidboot.hardware=freescale

Also:

setenv bootargs console=ttymxc1,115200 init=/init nosmp video=mxcfb0:dev=hdmi,1366x768M@60,bpp=32video=mxcfb1:off fbmem=10M vmalloc=400M androidboot.console=ttymxc1 androidboot.hardware=freescale

In both cases the stock linux doesn't change the resolution.

Please let me know on this. It would be really helpful for all the other people who would like to use the stock linux than compiling their own.

Warm Regards,

Abhijit

setenv bootargs console=ttymxc1,115200 init=/init nosmp video=mxcfb0:dev=hdmi,1366x768M@60,bpp=32video=mxcfb1:off fbmem=10M

vmalloc=400M androidboot.console=ttymxc1 androidboot.hardware=freescale 

this one won't work, check here  Limitation 1366*768.

we used this one "1280x720M" and it works fine.

replace

bpp=32video=mxcfb1

with 

bpp=32 video=mxcfb1

there is space missing between bpp=32  and video=mxcfb1

Hello,

I am not sure whats the problem.

The debian build from agrahambell works perfectly fine. I install LXDE, there is no problem with that.

No need to calibrate the screen resolution in uboot.

I have tried both options and both don't work.

Warm Regards,

Abhijit

Hi,

Yes now I notice.

I will try this and post.

Warm Regards,

Abhijit

bose wrote:

The debian build from selsinork works perfectly fine. I install LXDE, there is no problem with that.

No need to calibrate the screen resolution in uboot.

The mainline kernel uses a different driver - or if not completely different then at least one that's had an extra 2-3 years of ongoing development and fixes. As such it's not really possible to directly compare the two of them, and probably isn't a good idea to use the same command line settings for both either.

I've said it before, and will in all likelyhood repeat it often, mainline isn't for everyone. There are both upsides and downsides. Some things work better on mainline, some on 3.0.35.

Hopefully sometime soon there may be a supported BSP for RIoT using the newer Freescale 3.10.x baseline BSP which would help to bridge some gaps..

bose wrote:

The debian build from selsinork works perfectly fine. I install LXDE, there is no problem with that.

No need to calibrate the screen resolution in uboot.

The mainline kernel uses a different driver - or if not completely different then at least one that's had an extra 2-3 years of ongoing development and fixes. As such it's not really possible to directly compare the two of them, and probably isn't a good idea to use the same command line settings for both either.

I've said it before, and will in all likelyhood repeat it often, mainline isn't for everyone. There are both upsides and downsides. Some things work better on mainline, some on 3.0.35.

Hopefully sometime soon there may be a supported BSP for RIoT using the newer Freescale 3.10.x baseline BSP which would help to bridge some gaps..