Actions
Forum Thread Details
  • State Verified Answer
  • Replies 17 replies
  • Subscribers 356 subscribers
  • Views 1849 views
  • Users 0 members are here
Related

display port reference design

zjeng

Hi,

from the documentation I see that the reference design (and its pre-builts) are made for the engineering sample version AES-ZU3EGES-1-SK-G.

I want to run the DP reference design on the production version of the board.

Q1) Can I run the ES pre-builts on production version?

Q2) What changes do you expect to apply to the sources if I go and rebuild the sources for production version?

Thanks, Ric.

 

p.s.

Q3) The Out-Of-Box references provided are build for ES version as well. Same question here: Can I run it on production silicon version? Expecting NO, can you provide adapted version of these design examples please.

  • 0

    zheng,

    The published UltraZed EG DisplayPort Reference Design is for production silicon.  The SD card images that are provided in the archive with the document, as for production silicon.

    Can you point me to exactly where in the documentation you see a reference to ES1 silicon.  I will update it.

    Regards,

    Mario.

  • 0 in reply to albertabeef

    Mario

    This are good news! So we can use DP reference with production silicon.

    In the documentation see Hardware Requirements or search for "ZU3EGES".

    Same is true for the Out-of-Box documentation.

    Regards, Ric.

  • 0 in reply to albertabeef

    I can confirm that the DP reference design (prebuilt image) run on my production silicon board. However It run into an error while attempting to connect my 4k monitor (Unigraf UCD-323 DP reference sink). The relevant log lines may are as follows:

    [3395547.503] Module class: X.Org Video Driver
    [3395547.503] ABI class: X.Org Video Driver, version 20.0
    [3395547.503] (II) ARMSOC: Driver for ARM Mali compatible chipsets
    [3395547.503] (--) using VT number 2
    [3395547.503] (WW) Falling back to old probe method for armsoc
    [3395547.503] (II) No BusID or DriverName specified - opening /dev/dri/card0
    [3395547.503] (EE) ERROR: Cannot open a connection with the DRM - No such file or directory
    [3395547.503] (EE) No devices detected. [3395547.503] (EE) Fatal server error:
    [3395547.504] (EE) no screens found(EE)

    Any idea what to check?

    Thanks, Ric.

  • 0

    Hi, this is another DP reference design topic I start here in this thread. Hope it is not too confusing.

    The build script I start with ./make_uz3eg_iocc_dp_bsp.sh runs well except when it try to get access to Git via git:// github.com/...

    I can trace this back to a limitation of our company firewall (which may is true for others company IT infrastructure as well).

    Question: Can we change the access requests from git:// to https:// ? From a quick review of the script source I didn't find this reference.

    Thanks, Ric.
     

  • 0

    Hello Zjeng,

    We are currently looking into your questions. In the furture please post any new topics in new forum posts. Doing so will leave a better paper trail for others to follow if they encounter similar issues.

    Thanks,
    Josh

  • 0 in reply to zjeng

    Ric,

    I do not get anything ressembling your console output on my side ... do you get these messages after boot, when you connect your monitor ?

    Please share your complete linux console output for reference ...

    Here are some ideas:

    1) Can you execute the following commands ?

    With the monitor disconnected, here is what I get:

       # ls /sys/class/drm
       card0  card0-DP-1  controlD64  version

       # cat /sys/class/drm/card0-DP-1/status
       disconnected

       # cat /sys/class/drm/card0-DP-1/modes

    With a Samsung 4K DP (LU28E590DS) monitor connected, here is what I get:

       # ls /sys/class/drm
       card0  card0-DP-1  controlD64  version

       # cat /sys/class/drm/card0-DP-1/status
       connected

       # cat /sys/class/drm/card0-DP-1/modes
       3840x2160
       3840x2160
       2560x1440
       1920x1080
       1920x1080
       1680x1050
       1600x900
       1280x1024
       1280x1024
       1440x900
       1280x800
       1152x864
       1280x720
       1280x720
       1024x768
       1024x768
       1024x768
       832x624
       800x600
       800x600
       800x600
       800x600
       640x480
       640x480
       640x480
       640x480
       640x480
       720x400

     

    Regards,

    Mario.

  • 0 in reply to zjeng

    Ric,

    To my knowledge, all of the accesses to the Avnet git repository are done before launching the build.

    The other git repository accesses are probably occuring as part of the Xilnx petalinux build.  This would be a question for the Xilinx forum.

    For reference, can you share the message that is complaining about the access to git:// ?

     

    Also, I have encounterred issues with the "git://gitenterprise.xilinx.com/Graphics/mali400-xlnx-userspace.git" package,
    which points to a Xilinx internal repository.

    Xilinx have documented this issue, and proposed a solution

    I have applied the solution to this design as follows:

       petalinux-config
   ---> Yocto Settings  --->
      --->  YOCTO SOURCE MIRROR URL ( choose external path )
         --->  EXTERNAL PATH
            petalinux.xilinx.com/.../downloads

    Which adds the following content to the config file:

        CONFIG_YOCTO_SOURCE_MIRROR_URL_SELECT_EXTERNAL=y
        CONFIG_YOCTO_SOURCE_MIRROR_URL_SELECT_EXTERNAL_PATH="http://petalinux.xilinx.com/sswreleases/rel-v2017.2/downloads"
      
     
    Hope this helps !
     
    Regards,
     
    Mario.
     
     
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    
	
    
		
						
						
				
						
				
				
		
		
    
			
		
    
	
    

    

    • 

	

  • 
	
    



	
		
	
	





    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
												
						in reply to albertabeef
					
									
    
	
    

		
		
    
					
    Mario,
    the # ls /sys/class/drm answer is "version" only.
    I can provide the log file but can not past it here in the editor nor can I attache a file.
     Please provide an email address to send to.
     
     Just to ask, the only hw modifications I made to the boards are SW2 to boot from sd-card and JP1 closed with a jumper.
     Further, Ethernet is not connected.
     Anything wrong here?
    Thank you,
     Ric.
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    
	
    
		
						
						
				
						
				
				
		
		
    
			
		
    
	
    

    

    • 

	

  • 
	
    



	
		
	
	





    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
												
						in reply to albertabeef
					
									
    
	
    

		
		
    
					
    Mario,
    thanks! The error message is as follows:
    ERROR: linux-xlnx-4.9-xilinx-v2017.2+gitAUTOINC+d9c9ef8834-r0 do_fetch: Fetcher failure for URL: 'git://github.com/Xilinx/linux-xlnx.git;protocol=https;branch=2017.2_video_ea;nobranch=1'. Unable to fetch URL from any source.
    Regarding the Petalinux configuration: I made the changes in the (script generated) uz3eg_iocc_2017_2 directory. Then I rerun the script. Correct?
    Ric.
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    
	
    
		
						
						
				
						
				
				
		
		
    
			
		
    
	
    

    

    • 

	

  • 
	
    



	
		
	
	





    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
												
						in reply to zjeng
					
									
    
	
    

		
		
    
					
    Hello Ric,
    You should be able to paste in any comments you need to. Try using Firefox.
    --Josh
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    
	
    
		
						
						
				
						
				
				
		
		
    
			
		
    
	
    

    

    •