Posts by rdohmhardt

    In fsimx6-V3 / (Armstone A9) the backlight brightness is set as shown below:

    cat /sys/devices/soc0/backlight_ldb//backlight/backlight_ldb/max_brightness /* gives -> 15 */
    echo 15 > /sys/devices/soc0/backlight_ldb//backlight/backlight_ldb/brightness /* sets it to maximum */


    • What are possible values/strings for /sys/devices/soc0/backlight_ldb/backlight/backlight_ldb/power/control ? The default is "auto"!
    • How do I access Pin-24 of the LCD FI-S25S connector in order to manually switch off/on the backlight ?

    As said above I could fix the orientation issue by changing .orient in the file board-mx6_armstonea9.c
    from MXT_ROTATED_90 to MXT_VERTICAL_FLIP, i.e.

    1. .orient = MXT_VERTICAL_FLIP

    Now, the mouse pointer (MP) follows my fingers movement. Still, I have a large offset of

    1. X: 50(of 154)mm and
    2. Y: 30(of 90)mm

    I.e. in both axes the MP position is 1/3rd (related to screen size) too high and 1/3rd too much left.
    I "played" with .x_size and .y_size. Exchanging them did not make a noticeable difference.
    Any other ideas?

    I did a retest and found the same result: When powering off date/time are gone.
    I use adapter…r/armstone-power-adapter/
    with a cell 2032 (3V).
    I just measured the off-load cell voltage (Vybrid module is disconnected) at J4 Pin 1/2 and 5/6: 2.6V
    When connecting the Vybrid module it drops down to 1.7V.
    The table below shows the figures completed by the voltage measured directly at the inserted CR2032.

    1. Connection state
    2. Power Adapter /
    3. Vybrid module J4 CR2032
    4. ----------------------------------------
    5. unplugged 2,6V 2,7V
    6. plugged 1,7V 2,65V

    To repeat: I measure a voltage drop at J4 from 2.6 down to 1.7V. I did this with another cell with similar results.
    The voltage drop of 0.9V might be to high and the 1.7V are insufficient to maintain date/time.

    Below are the lines from the boot log related to Vybrid Revision.
    Uncompressing Linux... done, booting the kernel.
    Linux version 3.0.15-F+S (keller@VBFedora14) (gcc version 4.7.2 (crosstool-NG 1.18.0 - for F+S boards and modul4
    CPU: ARMv7 Processor [410fc051] revision 1 (ARMv7), cr=10c53c7d
    CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache

    [Edit fs-support_HK: Fixed the Table]

    Dear RSchubert,

    how did you set the brightness to a value of 255?
    Is there an ioctl()?

    I use the display from…ts/tft-kapazitiver-touch/
    which is an CHI MEI TFT-LCD G070Y2-L01 supporting both 6 or 8 bits/color.
    Pin 4 of the iMX6 LVDS connector sets it fixed to 6 bit.
    The instruction
    # setenv extra video=mxcfb0:dev=ldb,LDB-WVGA,if=RGB666
    sets the display properly to work(colors are correct). Everything is visible. However, it could be brighter!
    The signals to control "on/off" and "Backlight PWM" are on Pin 24 and 25, respectively. How do I access them?

    A hint by F&S could bring a bit light into this issue!
    The correct rtc to use for the Vybrid (my PCB from 2013) is /dev/rtc1 and not /dev/rtc0!

    Thus you can set the HW Clock with, e.g.,
    #date "2016-07-04 22:37"
    #hwclock --systohc --rtc=/dev/rtc1 /* set HW clock to current system time */
    #hwclock -r --rtc=/dev/rtc1 /* read HW clock */

    Now date/time "survives" a reboot.

    However, when unplugging from power the Vybrid-A5 looses date/time.
    According to F&S this hardware issue is resolved with recent Vybrid-A5.

    I'm using the kit from…ts/tft-kapazitiver-touch/
    consisting of the TFT-LCD G070Y2-L01 and the Atmel capacitive touch.

    When touching the screen I can prompt the mouse pointer to move, i.e. X11 does see touch events.
    However, there is an offset of more than 50mm. Frequently also the movement direction deviates to the one of my finger,
    i.e. finger moves to the right -> mouse pointer moves down.

    During boot the serial log contains the following Atmel related lines:
    atmel_mxt_ts 2-004a: Family ID: 128 Variant ID: 1 Major.Minor.Build: 2.0.AA
    atmel_mxt_ts 2-004a: Matrix X Size: 16 Matrix Y Size: 14 Object Num: 17
    input: Atmel maXTouch Touchscreen as /devices/platform/imx-i2c.2/i2c-2/2-004a/input/input1

    For a capacitive touch a calibration should not be necessary. Thus how to get this issue resolved?

    The HW-clock on my Vybrid Armstone A5 PCB does not accept a date.

    I set the date with
    # date "2016-07-03 18:54"
    -> Sun Jul 3 18:54:00 UTC 2016
    and then setting the HW clock fails with
    # hwclock --systohc
    -> rtc-pcf8563 3-0051: pcf8563_set_datetime: err=-5 addr=02, data=06
    -> hwclock: RTC_SET_TIME: Input/output error

    In the past this forum mentions issues like
    -RTC not working at all or
    -high power consumption, thus using an external HW clock chip instead of the internal one.
    However, I do not know how to resolve this issue.

    Below the boot messages:

    Linux version 3.0.15-F+S (keller@VBFedora14) (gcc version 4.7.2 (crosstool-NG 1.18.0 - for F+S boards and modules) ) #1 Fr4
    CPU: ARMv7 Processor [410fc051] revision 1 (ARMv7), cr=10c53c7d
    CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
    Machine: F+S Elektronik Systeme GmbH, armStoneA5

    armStoneA5 Board Rev. 1.10

    rtc-pcf8563 3-0051: chip found, driver version 0.4.3
    rtc-pcf8563 3-0051: pcf8563_get_datetime: read error
    rtc-pcf8563 3-0051: rtc core: registered rtc-pcf8563 as rtc0
    snvs_rtc snvs_rtc.0: rtc core: registered snvs_rtc as rtc1

    Welcome to F+S-Vybrid
    fsvybrid login: root
    # uname -a
    ->Linux fsvybrid 3.0.15-F+S #1 Fri Aug 22 09:50:12 CEST 2014 armv7l GNU/Linux