Posts by petersen

    Hello F&S Community,


    we are facing an issue during the update/install mechanism. On certain USB memory devices the update (update.scr) process will fail.

    Recent appearance of the problem showed that u-boot didn't seem to see the USB memory at all.


    We use FAT32 only at the moment.


    Are there any restrictions in case of quality of the storage devices? Is this problem known or are we rather alone with this behavior during the update mechanism?



    Best Regards,

    Arne Petersen

    Hello and thank you for your post!


    I am in direct contact with one of your developers at the moment and will get a starter kit soon to try the software on the baseboard. I did not mention that we use a custom board from F&S.


    Quote

    How did you get the EDID specificiations that you listed above? Was this some output of a Linux command on our board?

    I used a program called EDIDViewer on my windows desktop.


    The full dmsg :

    dmesg_boot.txt


    The complete serial output while booting :

    serial_boot_output.txt


    Best regards.



    Edit 1:

    Quote

    So my guess would point to a problem when reading the EDID data.


    I read the EDID data in /sys/devices/soc0/soc/20e0000.hdmi_video/edid (on the board):


    Those raw data is the same as the output of the EDID Viewer (windows desktop) when compared with a web based EDID viewer.


    Output of the EDID Viewer (windows desktop):

    Code
    1. 0x00 00 FF FF FF FF FF FF 00 10 AC DB A0 42 36 47 30
    2. 0x10 20 1B 01 04 A5 35 1E 78 3A 05 65 A7 56 52 9C 27
    3. 0x20 0F 50 54 A5 4B 00 71 4F 81 80 A9 C0 D1 C0 01 01
    4. 0x30 01 01 01 01 01 01 02 3A 80 18 71 38 2D 40 58 2C
    5. 0x40 45 00 0F 28 21 00 00 1E 00 00 00 FF 00 43 57 36
    6. 0x50 59 37 37 38 42 30 47 36 42 0A 00 00 00 FC 00 44
    7. 0x60 45 4C 4C 20 50 32 34 31 37 48 0A 20 00 00 00 FD
    8. 0x70 00 38 4C 1E 53 11 01 0A 20 20 20 20 20 20 00 47


    Edit 2:

    After further investigation i could not reproduce the correct EDID data in /sys/devices/soc0/soc/20e0000.hdmi_video/edid, it stayed empty (0x00).


    Additionally i checked the status of /sys/devices/soc0/soc/20e0000.hdmi_video/cable_state and to my surprise it contains plugin, when no hdmi is connected and plugout, when hdmi is connected. That should probably not happen.


    I build the kernel with debug enabled and the following output comes up when i connect the hdmi monitor to my board:

    Code
    1. mxc_hdmi 20e0000.hdmi_video: Hotplug interrupt received
    2. mxc_hdmi 20e0000.hdmi_video: phy_int_stat=0x3d, phy_int_pol=0x0
    3. mxc_hdmi 20e0000.hdmi_video: EVENT=plugout
    4. mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_cable_disconnected
    5. mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_phy_disable
    6. hdmi_disable_overflow_interrupts
    7. mxc_hdmi 20e0000.hdmi_video: mxc_hdmi_phy_disable - exit
    8. hdmi_disable_overflow_interrupts

    If i unplug hdmi:

    Thank you for the fast reply,


    I managed to rebuild the device tree with these changes, but the display does not get recognized.

    Hopefully I can get some suggestions to understand what I am missing here.


    Here is my fb0 --info :


    The xrandr outcome :

    The kernel messages (grep mxc) :

    The kernel :

    Code
    1. root@econo206:~# uname -a
    2. Linux econo206 4.1.15-rt18-F+S #2 SMP PREEMPT RT Mon Aug 17 06:29:55 UTC 2020 armv7l GNU/Linux


    I use a DELL P2417H connected via HDMI.


    EDID Data :


    Any kind of help is highly appreciated!

    Best regards.



    Edit:

    If i unplug the monitor the following output comes up :

    Code
    1. mxc_hdmi 20e0000.hdmi_video: Read EDID again
    2. mxc_hdmi 20e0000.hdmi_video: create default modelist

    Hello,


    I know this Topic is a little old, but it fits my problem and I do not think things changed.


    The solution is given for Buildroot, is it possible to list the changes between Buildroot and Yocto?


    Thank you in andvance!