Tool/software:
The old image that came with the eval has a working boot screen, touch screen and program that load a screen. New image does not, was that removed or is there something wrong I need to look at?
Robert,
Can you please be more explicit with the SDK versions you are referring to?
-Josue
AM572X eval module
new image///onboard display does not come up – downloaded from TI
root@am57xx-evm:~# hostnamectl
Static hostname: am57xx-evm
Icon name: computer
Machine ID: 07b5f4e2274549fbae6cbbb850b465ca
Boot ID: 50ffa3086023472cb79f6b08c75de27b
Operating System: Arago 2023.10
Kernel: Linux 6.1.119-ti-ge4e8b16e66f5
Architecture: arm
/////////////////////////////////////
image that came with AM752X evm board/// onboard display come up
Linux version 4.1.13-g8dc6617
(gtbldadm@ubuntu-12)
(gcc version 4.9.3 20150413
(prerelease) (Linaro GCC 4.9-2015.05
Hello Robert,
I am out of the office until 1/22. Please expect delays in reply.
-Josue
Robert,
On the new image, do you see at least a grey screen?
Can you let me know what dtb you are using?
I do not think the LCD is enabled by default in the newer images.. I am double-checking with our dev team.
For sure the Matrix application is no longer supported.
Please see the release notes here: https://software-dl.ti.com/processor-sdk-linux/esd/AM57X/09_03_06_05/exports/docs/devices/AM57X/linux/Release_Specific_Release_Notes.html#release-09-03-00
-Josue
yes it is a light grey background.. I will review the release notes to see what was remove, but I would thing the boot screen would show but maybe that was removed.
U-Boot SPL 2023.04-ti-g2bedcd265ca6 (Dec 07 2024 - 07:04:35 +0000)
DRA752-GP ES2.0
no pinctrl state for default mode
Firmware loading failed for ipu2
Trying to boot from MMC1
Loading Environment from FAT... no pinctrl state for default mode
*** Error - No Valid Environment Area found
*** Warning - bad env area, using default environment
Loading Environment from MMC... *** Warning - bad CRC, using default environment
U-Boot 2023.04-ti-g2bedcd265ca6 (Dec 07 2024 - 07:04:35 +0000)
CPU : DRA752-GP ES2.0
Model: TI AM5728 BeagleBoard-X15
Board: AM572x EVM REV A.3A
DRAM: 2 GiB
ti_emmc_boardid_get failed -5
Core: 70 devices, 24 uclasses, devicetree: separate
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Loading Environment from FAT... *** Error - No Valid Environment Area found
*** Warning - bad env area, using default environment
Loading Environment from MMC... *** Warning - bad CRC, using default environment
Net: eth2: ethernet@48484000
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
This will not be a case any time
This will not be a case any time
7930368 bytes read in 373 ms (20.3 MiB/s)
This will not be a case any time
This will not be a case any time
216953 bytes read in 39 ms (5.3 MiB/s)
Working FDT set to 88000000
This will not be a case any time
This will not be a case any time
Kernel image @ 0x82000000 [ 0x000000 - 0x790200 ]
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Working FDT set to 88000000
Loading Device Tree to 8fec8000, end 8fffffff ... OK
Working FDT set to 8fec8000
ft_fixup_clocks failed for DSP voltage domain: <valid offset/length>
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 6.1.119-ti-ge4e8b16e66f5 (oe-user@oe-host) (arm-oe-linux-gnueabi-gcc (GCC) 11.5.0, GNU ld (GNU Binutils) 2.38.20220708) #1 SMP PREEMPT Sat Dec 7 07:14:10 UTC 2024
[ 0.000000] CPU: ARMv7 Processor [412fc0f2] revision 2 (ARMv7), cr=30c5387d
[ 0.000000] CPU: div instructions available: patching division code
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[ 0.000000] OF: fdt: Machine model: TI AM5728 BeagleBoard-X15
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] efi: UEFI not found.
Here is the start of the boot seems like there is an issues with some warning/errors. Reimage a couple time same results. Note the model shows Beagleboard, seem wrong. the UENV.txt file has no defined variables in it - should it?
Thanks for any help
Rob
Robert,
If your screen looks like this one:
This is the weston desktop and that's the expected behavior now that the GUI Matrix has been removed.
If this is the case then your LCD is in working order.
Yes, there are some kinks in the u-boot initialization that have not been taken care of and we can hopefully look into.
Josue
ok, thanks, questions: it looks just like it does when power is just turned on, not the grey you are showing?
I can stop/start weston but I see this in the restarting - [13:36:10.000] BUG: layer list is not empty after shutdown. Calls to weston_layer_fini() are missing somwhere.
below is the Weston /start after stop then restarting - seems fine except the above bug
I do see weston task in the list of task though
[13:42:37.-1225405176] weston 10.0.2 https://wayland.freedesktop.org Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/ Build: 10.0.2 [13:42:37.-1096150020] Command line: weston /start [13:42:37.-1226533029] OS: Linux, 6.1.119-ti-ge4e8b16e66f5, #1 SMP PREEMPT Sat Dec 7 07:14:10 UTC 2024, armv7l [13:42:37.139272] Flight recorder: enabled [13:42:37.1679848297] Using config file '/etc/xdg/weston/weston.ini' [13:42:37.002] Output repaint window is 7 ms maximum. [13:42:37.-1225405176] Loading module '/usr/lib/libweston-10/wayland-backend.so' [13:42:37.-1225405176] Loading module '/usr/lib/libweston-10/gl-renderer.so' [13:42:37.000] EGL client extensions: EGL_EXT_client_extensions EGL_EXT_device_base EGL_EXT_device_enumeration EGL_EXT_device_query EGL_EXT_platform_base EGL_KHR_client_get_all_proc_addresses EGL_KHR_debug EGL_EXT_platform_device EGL_EXT_platform_wayland EGL_KHR_platform_wayland EGL_MESA_platform_gbm EGL_KHR_platform_gbm EGL_MESA_platform_surfaceless MESA: info: Loaded libpvr_dri_support.so [13:42:37.004] EGL device extensions: EGL_EXT_device_drm EGL_EXT_device_drm_render_node [13:42:37.-1226615869] EGL version: 1.4 [13:42:37.139272] EGL vendor: Mesa Project [13:42:37.139272] EGL client APIs: OpenGL_ES [13:42:37.-1225740340] EGL extensions: EGL_EXT_buffer_age EGL_EXT_create_context_robustness EGL_EXT_present_opaque EGL_EXT_swap_buffers_with_damage EGL_EXT_yuv_surface EGL_KHR_config_attribs EGL_KHR_create_context EGL_KHR_fence_sync EGL_KHR_get_all_proc_addresses EGL_KHR_gl_renderbuffer_image EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_image_base EGL_KHR_no_config_context EGL_KHR_reusable_sync EGL_KHR_surfaceless_context EGL_KHR_swap_buffers_with_damage EGL_EXT_pixel_format_float EGL_KHR_wait_sync EGL_MESA_configless_context EGL_MESA_drm_image EGL_MESA_query_driver EGL_WL_bind_wayland_display EGL_WL_create_wayland_buffer_from_image [13:42:37.000] warning: Disabling render GPU timeline and explicit synchronization due to missing EGL_ANDROID_native_fence_sync extension [13:42:37.146904] EGL_KHR_surfaceless_context available [13:42:37.000] GL version: OpenGL ES 2.0 build 1.17@4948957 [13:42:37.-1226533029] GLSL version: OpenGL ES GLSL ES 1.00 build 1.17@4948957 [13:42:37.-1226533029] GL vendor: Imagination Technologies [13:42:37.-1226533029] GL renderer: PowerVR SGX 544MP [13:42:37.-1226536055] GL extensions: GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth24 GL_OES_depth_texture GL_OES_egl_sync GL_OES_element_index_uint GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_fbo_render_mipmap GL_OES_fragment_precision_high GL_OES_get_program_binary GL_OES_mapbuffer GL_OES_packed_depth_stencil GL_OES_required_internalformat GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_surfaceless_context GL_OES_texture_float GL_OES_texture_half_float GL_OES_texture_npot GL_OES_vertex_array_object GL_OES_vertex_half_float GL_EXT_blend_minmax GL_EXT_discard_framebuffer GL_EXT_draw_buffers GL_EXT_multi_draw_arrays GL_EXT_multisampled_render_to_texture GL_EXT_occlusion_query_boolean GL_EXT_shader_framebuffer_fetch GL_EXT_shader_texture_lod GL_EXT_texture_format_BGRA8888 GL_EXT_texture_rg GL_IMG_multisampled_render_to_texture GL_IMG_program_binary GL_IMG_read_format GL_IMG_shader_binary GL_IMG_texture_compression_pvrtc GL_IMG_texture_compression_pvrtc2 GL_IMG_texture_format_BGRA8888 GL_IMG_texture_npot GL_IMG_uniform_buffer_object GL_KHR_debug GL_EXT_texture_storage [13:42:37.-1226533919] GL ES 2.0 - renderer features: read-back format: RGBA wl_shm sub-image to texture: no EGL Wayland extension: yes [13:42:37.243948] Registered plugin API 'weston_windowed_output_api_v1' of size 8 [13:42:37.-1225848064] Color manager: no-op [13:42:37.-1889785611] Output 'wayland0' using color profile: built-in default sRGB SDR profile [13:42:37.428008] Creating 1024x640 wayland output at (0, 0) [13:42:37.000] wayland-backend: Using xdg_wm_base [13:42:37.-1226533919] Chosen EGL config details: id: 1 rgba: 8 8 8 8 buf: 32 dep: 0 stcl: 0 int: 0-1 type: win|pbf vis_id: 0 [13:42:37.000] Output 'wayland0' enabled with head(s) wayland0 [13:42:37.000] Compositor capabilities: arbitrary surface rotation: yes screen capture uses y-flip: yes cursor planes: no arbitrary resolutions: no view mask clipping: yes explicit sync: no color operations: no presentation clock: CLOCK_MONOTONIC_RAW, id 4 presentation clock resolution: 0.000000001 s [13:42:37.-1225405176] Loading module '/usr/lib/weston/desktop-shell.so' [13:42:37.-1096149808] launching '/usr/libexec/weston-keyboard' [13:42:37.-1225401440] Note: support for the deprecated wl_shell interface is disabled. If a legacy client still needs it, it can be re-enabled by passing -Ddeprecated-wl-shell=true to Meson when building Weston. [13:42:37.-1096150092] fatal: unhandled option: /start Failed to process Wayland connection: Broken pipe failed to create display: Broken pipe MESA: info: Unloaded libpvr_dri_support.so [13:42:37.000] BUG: layer_list is not empty after shutdown. Calls to weston_layer_fini() are missing somwhere.
is there something that I can run to see something on the display or driver code to use in the image to verify things (display)?
Robert,
it looks just like it does when power is just turned on, not the grey you are showing?
Can you clarify the above statement? you see the same screen or not? Do you see the date and the weston shell symbol?
Can you see a mouse when you connect one via USB?
Can you share the overlay you are using?
you could run the GPU examples under /usr/share/qt5/examples/gui:
root@am57xx-evm:~# cd /usr/share/qt5/examples/gui root@am57xx-evm:/usr/share/qt5/examples/gui# ./openglwindow/openglwindow MESA: info: Loaded libpvr_dri_support.so
and you should see the following:
-Josue
Screen is not the same as yours.
Not sure overlay question means
Ran program as stated and no display (see below)
root@am57xx-evm:/usr/share/qt5/examples/gui/openglwindow# ./openglwindow
qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
MESA: info: Loaded libpvr_dri_support.so
mouse does show up that it was loaded in the termal (Putty) nothing on screen
fyi..am57xx-evm-linux-rt-06.03.00.106.img.zip this image which was create in 2019 works fine
Seems like the latest version has big issues around this area?
Robert,
2019 image should be fine. I believe the default image for the newest SDK does not have the correct DTS loaded for enabling the LCD screen on the EVM.
So my question is essentially what DT source is being used?
You might have to use a different DT source file in order to see the screen enabled, and I believe this is an overlay file or .dtbo file
Should be this one: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/arch/arm/boot/dts/am57xx-evm.dtso?h=ti-linux-6.1.y
I myself do not have the bandwidth to test right now but I can probably get around the end of next week or the week after.
-Josue
Hi! thanks for the input I'll look at it, but traveling last couple of days should be back on it later today or tomorrow
Thanks, I trying to fine all the link for to get the file to build.. Seems more complicated then I would hope - any help with location image source files?
Robert,
You can download the SDKs at https://www.ti.com/tool/download/PROCESSOR-SDK-LINUX-AM57X/09.03.06.05
Or clone the Linux source https://git.ti.com/git/ti-linux-kernel/ti-linux-kernel.git. You could also do something to the extent of https://stackoverflow.com/questions/61587133/cloning-single-file-from-git-repository.
The LCD overlays are already present in your root image.
-Josue
Thanks, I need to get my Linux box up and look at it. From what I read it need to be built with Ubuntu 14, that really old?
Yes, SDK 6.3-8.2 is tested using Ubuntu 18.04 and the newer SDKs are all tested in Ubuntu 22.04.
-Josue