Dmesg output a lot of weird info

[bonkbonk]

[ 312.127336] zocl-drm axi:zyxclmm_drm: zocl_destroy_client: client exits pid(831)
[ 312.127932] zocl-drm axi:zyxclmm_drm: zocl_create_client: created KDS client for pid(831), ret: 0

After the system starts, these messages keep being displayed.

The call to Pynq in Jupyter is normal.

Are these strange messages normal? What adjustments do I need to make?

pynq version:3.0.1

[joshgoldsmith]

Hi @bonkbonk, welcome to the PYNQ forum!

I would need to know a bit more information about your setup.

• What board are you using?
• Are these message showing up in the serial console (e.g. PuTTY, Minicom)?
• Are these messages showing on every boot, or just sometimes?
• Have you tried a different SD card, or burning the image again?
• Can you try the latest v3.1.1 image instead?

[bonkbonk]

hello @joshgoldsmith ！

1.I make the board by my self,and use pynq sdbuild workflow make the image.

2.this message showing up in serial console.

3.ervery boot.

4.yes ,i tried,but nothing different.

5.that’s a little hard, you know,set up env is a hard work .But I will take this as the final plan.

Could you give me some ideas or a direction for debugging?

[bonkbonk]

#my bsp.cfg
#CONFIG_DRM_DIGILENT_DRIVER=y 
#CONFIG_COMMON_CLK_DGLNT_DYNCLK=y

CONFIG_I2C_XILINX=y 
#CONFIG_MEDIA_USB_SUPPORT=y

#CONFIG_DRM_XLNX_BRIDGE=y 
#CONFIG_DRM_XLNX_PL_DISP=y 
#CONFIG_DRM_XLNX_BRIDGE_VTC=y
#CONFIG_VT_HW_CONSOLE_BINDING=y

#CONFIG_DRM_FBDEV_EMULATION=y
#CONFIG_APERTURE_HELPERS=y
#CONFIG_DRM_GEM_SHMEM_HELPER=y
#CONFIG_DRM_SIMPLEDRM=y

CONFIG_FB=y
#CONFIG_FB_XILINX=y 
#CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FB_SIMPLE=y
#CONFIG_FIRMWARE_EDID=y 
CONFIG_FB_DEVICE=y

#my system-user.dtsi
/include/ "system-conf.dtsi"

/{
	usb_phy0: phy0@e0002000 {
		compatible = "ulpi-phy";
		#phy-cells = <0>;
		reg = <0xe0002000 0x1000>;
		view-port = <0x0170>;
		drv-vbus;
	};

	reserved-memory {
		#address-cells = <1>;
		#size-cells = <1>;
		ranges;
		framebuffer_resv: framebuffer@36000000 {
		    reg = <0x36000000 0x1c2000>;
		    no-map; 
		};
	    };
        

        framebuffer@36000000 {
                compatible = "simple-framebuffer";
                reg = <0x36000000 (1024*600*3)>;
                width = <1024>;
                height = <600>;
                stride = <(1024*3)>;
                format = "r8g8b8";
                status = "okay";
        };
};

&usb0 {
    dr_mode = "host";
    usb-phy = <&usb_phy0>;
};

&i2c0 {
    clock-frequency = <100000>;
    status = "okay";
};

More information about my setup.

I’m trying to make a function for HDMI display. here are my board setting for sdbuild workflow.

Do you think this info’s got something to do with the display driver? I’m new to this, so I’m not really sure what’s causing the problem.

[bonkbonk]

from pynq import Overlay
from pynq import PL
from pynq.lib.video import VideoMode
import matplotlib.pyplot as plt
import numpy as np

PL.reset()
ol = Overlay('/home/xilinx/zynq.bit')
print(ol.ip_dict.keys())

frameBufferRead = ol.v_frmbuf_rd_0
frameBufferRead.write(0x10, 1024)
frameBufferRead.write(0x18, 600)
frameBufferRead.write(0x20, 0xc00)
frameBufferRead.write(0x28, 0x14)
frameBufferRead.write(0x30, 0x36000000)

frameBufferRead.write(0x00, 0x81)

here my python code ,i get a full white display on my screen. something wrong,but maybe not relate to this topic

[joshgoldsmith]

This message isn’t an error, it’s just an information message from zocl. It’s triggered by some interaction with XRT, which PYNQ uses for memory allocation and buffer read/writing. So it shouldn’t have anything to do with your hardware design, only with code running on the PS (that may be interacting with hardware on the PL).

One important thing is to understand if this message keeps triggering over and over by itself, or when you are running PYNQ code.

If it’s happening when using PYNQ, what code causes the message to occur?

[bonkbonk]

Thanks for your explanation. I’ll break down my code and find out what’s causing the problem.