[Manuel Malagon]

Mine behaved the exact same way you describe and I got it like a month ago. I plugged it in and nothing happened.

I didn’t worry much and I just created the eMMC image with the instructions from the OSD32MP1 Debian SDK and flashed it with STM32CubeProgrammer and now it works like a charm.

[Manuel Malagon]

Just in case anyone lands here…

Do not use STM32CubeProgrammer v2.6.0!! It will corrupt the flash and you will not have HDMI output, (and maybe something else will be wrong). The resulting eMMC image seemed to work correctly for me and the only apparent issue was no HDMI output. But I’m not sure if it had another hidden issue.

I used STM32CubeProgrammer v2.5.0, it doesn’t crash and it will correctly flash the eMMC.

[Manuel Malagon]

Neeraj,

Well, something must have gone wrong with the image I created. I created the image using the STM32CubeProgrammer v2.6.0 which was crashing at the very end of the process (I posted a question in this forum about that) but the board worked fine, apparently, just the HDMI had issues. Everything else seemed to be working well. I switched to the STM32CubeProgrammer v2.5.0, created the image again, and flashed it to the eMMC. This time the flashing was successful without the programmer crashing at the end and now I have video coming out of the board.

So I don’t know what was wrong the first time but now it is working fine. I’ll keep using the STM32CubeProgrammer v2.5.0 to avoid future issues. I don’t know what’s wrong with 2.6.0.

[Manuel Malagon]

Neeraj

The board is configured properly and that is verified by the fact that I get video if I use the openstlinux image. Due to your suggestion, I tried the pre-built image in the link you give and it is working correctly! I get video with this image.

The problem is that I used the eMMC image generated following the OSD32MP1 Debian SDK steps here: https://github.com/octavosystems/osd32mp1-debian to flash the on-board eMMC.

Maybe you need to check out that image and see if there are any problems with it because that is the one that doesn’t work and that I need. Please let me know your thoughts on this. I followed the steps exactly as outlined in that website.

[Manuel Malagon]

Neeraj,

I forgot to mention, nothing happens if I restart the Weston service.

I have tried with an HDMI 720p monitor and it didn’t work either.

I get – connected – when I execute – sudo cat /sys/class/drm/card0/card0-HDMI-A-1/status – and the following with – sudo cat /sys/class/drm/card0/card0-HDMI-A-1/modes –

1280x720 800x600

1 2	1280x720 800x600

But I get – disabled – when executing – sudo cat /sys/class/drm/card0/card0-HDMI-A-1/enabled –

I also get this when executing sudo get-edid | parse-edid

This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface No EDID on bus 0 No EDID on bus 2 No EDID on bus 3 2 potential busses found: 1 4 Will scan through until the first EDID is found. Pass a bus number as an option to this program to go only for that one. 128-byte EDID successfully retrieved from i2c bus 1 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "2269W" ModelName "2269W" VendorName "AOC" # Monitor Manufactured week 36 of 2015 # EDID version 1.3 # Digital Display DisplaySize 480 270 Gamma 2.20 Option "DPMS" "true" Horizsync 30-83 VertRefresh 50-76 # Maximum pixel clock is 170MHz #Not giving standard mode: 1920x1080, 60Hz #Not giving standard mode: 1680x1050, 60Hz #Not giving standard mode: 1440x900, 60Hz #Not giving standard mode: 1280x1024, 60Hz #Not giving standard mode: 1280x960, 60Hz #Not giving standard mode: 1280x720, 60Hz Modeline "Mode 0" +hsync +vsync EndSection

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33

This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface No EDID on bus 0 No EDID on bus 2 No EDID on bus 3 2 potential busses found: 1 4 Will scan through until the first EDID is found. Pass a bus number as an option to this program to go only for that one. 128-byte EDID successfully retrieved from i2c bus 1 Looks like i2c was successful. Have a good day. Checksum Correct   Section "Monitor" Identifier "2269W" ModelName "2269W" VendorName "AOC" # Monitor Manufactured week 36 of 2015 # EDID version 1.3 # Digital Display DisplaySize 480 270 Gamma 2.20 Option "DPMS" "true" Horizsync 30-83 VertRefresh 50-76 # Maximum pixel clock is 170MHz #Not giving standard mode: 1920x1080, 60Hz #Not giving standard mode: 1680x1050, 60Hz #Not giving standard mode: 1440x900, 60Hz #Not giving standard mode: 1280x1024, 60Hz #Not giving standard mode: 1280x960, 60Hz #Not giving standard mode: 1280x720, 60Hz Modeline "Mode 0" +hsync +vsync EndSection

I hope this helps.

• This reply was modified 3 years, 5 months ago by Manuel Malagon.
• This reply was modified 3 years, 5 months ago by Manuel Malagon.

[Manuel Malagon]

Neeraj

Thanks for helping. That is the status of Weston service when I boot the board with the monitor plugged in. If I boot the board without the monitor then the service works just fine, but then if I plug in the monitor after the board has booted nothing happens. If I restart the Weston service after plugging in the monitor then Weston fails again.

I’m using a 1080p monitor that doesn’t have an HDMI input so I’m using an HDMI-to-DVI cable. Maybe that is the problem. I didn’t know that could have an adverse effect. I’ll try to test with another monitor and see what happens.

I’ll let you know what happens when using an HDMI monitor.

[Manuel Malagon]

Upon further investigation, I found this:

? weston.service - Weston Wayland Compositor Loaded: loaded (/lib/systemd/system/weston.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2021-07-02 03:03:56 UTC; 11min ago Main PID: 1939 (code=exited, status=1/FAILURE) Jul 02 03:03:55 insight-server systemd[1]: Starting Weston Wayland Compositor... Jul 02 03:03:55 insight-server systemd[1]: Started Weston Wayland Compositor. Jul 02 03:03:55 insight-server weston-start[1939]: openvt: Using VT /dev/tty3 Jul 02 03:03:56 insight-server systemd[1]: weston.service: Main process exited, code=exited, status=1/FAILURE Jul 02 03:03:56 insight-server systemd[1]: weston.service: Failed with result 'exit-code'.

1 2 3 4 5 6 7 8 9 10

? weston.service - Weston Wayland Compositor    Loaded: loaded (/lib/systemd/system/weston.service; enabled; vendor preset: enabled)    Active: failed (Result: exit-code) since Fri 2021-07-02 03:03:56 UTC; 11min ago Main PID: 1939 (code=exited, status=1/FAILURE)   Jul 02 03:03:55 insight-server systemd[1]: Starting Weston Wayland Compositor... Jul 02 03:03:55 insight-server systemd[1]: Started Weston Wayland Compositor. Jul 02 03:03:55 insight-server weston-start[1939]: openvt: Using VT /dev/tty3 Jul 02 03:03:56 insight-server systemd[1]: weston.service: Main process exited, code=exited, status=1/FAILURE Jul 02 03:03:56 insight-server systemd[1]: weston.service: Failed with result 'exit-code'.

Why could this be happening?

[Manuel Malagon]

Neeraj,

You are right, I just moved the boot switches to boot from flash and it is working. I don’t know why it crashes at the end and I guess it doesn’t matter as long as it flashes the eMMC correctly.

I haven’t tried with 2.5 or 2.4 yet.

[Manuel Malagon]

Neeraj,

Awesome! Thank you so much for helping!

It turns out it was the udev rules! I followed the instructions in the community post you mentioned and now it is working!

Regards,

Manuel Malagon

[Author]

Posts