• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 101 subscribers
  • Views 1934 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM335x Starter Kit - Linux - Disable LED D4, turn off screen and remove Tux/Penguin splash image?

Michael Skinner
Prodigy 50 points


Hi Everyone,

I have setup a minimal Linux installation based upon base-rootfs-am335x-evm.tar.gz within the 05.05 SDK. No bluetooth or wifi drivers, just NFS and Samba servers running.

I am currently using: 'echo "4" > /sys/class/graphics/fb0/blank' to blank the screen however I was wondering if there was a way to actually turn the screen off (as blanking still has the screen on - just displaying a black image).

The LED D4 also blinks twice a second, every second. Does anyone know what it indicates? It doesn't look like ethernet activity - is there a way to disable it? Even if I have to recompile a kernel module or the kernel itself?

Lastly, is there a way to remove the Tux/Penguin splash? It stays on screen even after Linux has finished booting. Is it by using opkg to remove psplash-support and psplash-ti or do kernel parameters need to be added (analogous to nosplash in GRUB)?

Thanks for any tips! I'm loving this board!

Mike 

  • 0
    TI__Expert 5450 points

    Mike,

    many of these answers can be found in the PSP User's Guide at http://processors.wiki.ti.com/index.php/AM335x_PSP_User%27s_Guide

    1. Turning off the LCD: Disable the LCD in the kernel (http://processors.wiki.ti.com/index.php/AM335x_LCD_Controller_Driver%27s_Guide)

    2. The LED blinking is the heartbeat LED to let you know the board is alive.  You can disable this in sysfs by doing "echo none > /sys/devices/platform/leds-gpio/leds/am335x:EVM_SK:heartbeat/trigger".  You can also cat that file to see what other options are available.

    3. See answer 1 above.  This is done by the kernel.

    Chase

  • 0
    Prodigy 220 points

    Hi Michael,

    To turn-off the Tux splash, you will need to recompile the kernel.

    Edit the file: /home/<user>/<ti-sdk>/board-support/board-port-labs/sitara-board-port-linux/arch/arm/configs/tisdk_am335x-evm_defconfig

    and find CONFIG_LOGO=y. Change it for CONFIG_LOGO=n (you may do it for next CONFIG_LOGO_LINUX defs)

    Then, follow the wiki http://processors.wiki.ti.com/index.php/Sitara_Linux_Training:_Linux_Board_Port, to recompile kernel.

    Regards,

    Mauricio O. Costa

  • 0 in reply to Mauricio Costa
    Prodigy 50 points

    Thanks Mauricio and Chase.

    The heartbeat sysfs command works well.

    I was hoping to avoid a kernel recompile, but it looks like I'm going to need to do it (to disable the LCD and the boot splash).  Maybe I will make the LCD driver a kernel module that I can blacklist (to avoid recompiling if I ever want the screen on for some reason).

    Thanks again :-) 

  • 0 in reply to Michael Skinner
    Intellectual 825 points

    Hey, I know this post is quite old. I was wondering if you could tell me as to how you managed to remove the tux image? I followed the steps mentioned above and for recompiling the kernel -

     I recompiled the kernel using make linux in the /opt/<ti-sdk>/

    Is this the correct way to recompile the kernel? If, so the image still appears. Any other way around it?

     i also tried going to /opt/ti-sdk-am335x-evm/board-support/board-port-labs/sitara-board-port-linux$ 

    and typing  - make ARCH=arm CROSS_COMPILE=/opt/ti-sdk-am335x-evm-06.00.00.00/linux-devkit/sysroots/i686-arago-linux/usr/bin/arm-linux-gnueabihf- tisdk_am335x-evm_defconfig

  • 0 in reply to Siddharth Sharma2
    Prodigy 50 points

    Hi Siddharth Sharma2,

    I'm sorry I'm not going to be much help - I don't recall recompiling the kernel (or successfully removing the Tux image).

    I haven't used the TI device for a long time (I now have Raspberry Pis).

    After reading your post, the only thing I can add is that "make"ing a kernel is not enough (at least on x86/x64 architectures). You may need to run other commands to actually install the kernel you have manually compiled, and ensure that the boot loader (if one exists) is configured to boot the new kernel (as opposed to the older one).

    Good luck, and sorry I cannot be more helpful to you.