• 0
Blake

How to launch Digilent hdmi FMC with zc702 board

Question

Hi all,

I want to verify Digilent HDMI FMC on zc702 board, but the Zynq base TRD 15.04 was used Avnet HDMI FMC with IP - "avnet_hdmi_in" in the path "rdf0286-zc702-zvik-base-trd-2015-4\hardware\vivado\srcs\ip".

If I use the original SD image to boot up zc702 board with Digilent FMC on FMC2 slot.
The board could detect i2c@1 (FMC), but crashed by i2c fatal error.
If I modify the constraint file only - pin_zc702.xdc to match Digilent FMC I/O setting, then repacked the BOOT.BIN with modified bitstream.
The board could boot up successfully, but couldn't seem detect i2c@1 (FMC).

Could I replace the corresponding IP to launch the Digilent FMC only?
If yes, where could I get the right IP?

If not, could someone tell me what I missed? Thanks.

BR
Blake

Share this post


Link to post
Share on other sites

22 answers to this question

Recommended Posts

  • 0

Hi @Blake,

Does the project work if it is not booted from the SD Card? Here is a tutorial using the zc702 and the FMC-HDMI that should be helpful. Here is a demo that uses the Zedboard and the FMC-HDMI.

thank you,

Jon

 

 

 

Share this post


Link to post
Share on other sites
  • 0

Hi Jon,

Thanks for your reply.

1.,
I tried the LK tutorial on zc702 + digilent hdmi-fmc also, but I meet an error message from following code flow without any modification :
Status = fmc_digilent_hdmii_init(&zc702_IicPs_1); 
=> 2. iic_writex2( IicPs, iic_hdmi_in_reset, IIC_HDMI_IN_RESET_LEN );
=> 3. iic_write2(IicPs, Config.Addr, Config.Reg, Config.Init);
=> 4. Status = XIicPs_MasterSendPolled(IicPs, WriteBuffer, 2, Address);
=> 5. while ((IntrStatusReg & XIICPS_IXR_COMP_MASK) != XIICPS_IXR_COMP_MASK){
            if ((IntrStatusReg & Intrs) != 0U) {
                 return (s32)XST_FAILURE;
            }
2.
I got a zed board too, although the sample was based on vivado 17.1; but I still used current version 17.4 to open the project to save time. (any side effect?)
It shows the project out of date, I can synthesis the project successfully; but I got an error when I executed implement flow.
The error message as below :
(Error) [Project 1-682] Sub-design 'design_1.bd' is not generated for Synthesis target. Please open this sub-design and generate with synth_checkpoint_mode as 'Singular' in original project before adding it to current project.

(critical warning) [Vivado 12-1464] The source file 'D:/zed_fmc/Zed_FMC_HDMI.xpr/Zed_FMC_HDMI/Zed_FMC_HDMI.srcs/sources_1/bd/design_1/design_1.bd' cannot be added to the fileset 'sources_1'.

After I   installed the corresponding version 17.1, there were no more error message.
Btw, how to verify zedboard + hdmi-fmc?
My test environment as below :
Input source : Notebook display port -> hdmi-fmc hdmi1
output : zedboard hdmi port -> monitor

There are no signal on monitor, the uart log as below :
control 9 status F00 Error 7F00000 Int Status 0 H and V Size 1E00280 Detector Timing Status 7 Video Mode = 5
Thanks.

# new update 2018/10/15
I added the debug message and found following error message :

    /*
     * Check for completion of transfer.
     */
    while ((IntrStatusReg & XIICPS_IXR_COMP_MASK) != XIICPS_IXR_COMP_MASK){

        IntrStatusReg = XIicPs_ReadReg(BaseAddr, XIICPS_ISR_OFFSET);
        /*
         * If there is an error, tell the caller.
         */
        if ((IntrStatusReg & Intrs) != 0U) {
            printf("~~~ XST_FAILURE"); <---------------- It will return FAILURE.
            return (s32)XST_FAILURE;
        }
    }

It will return FAILURE when it tried to write (0xff, 0x80)
static u8 iic_IO_hdmi_config[][2] = {
    { 0xff, 0x80 }, // i2c reset
    ...
This symptom seems like the issue that I meet on LK tutorial.


BR
Blake

Edited by Blake

Share this post


Link to post
Share on other sites
  • 0

Hello @Blake,

If you take a look into the errata section of the device reference manual, https://reference.digilentinc.com/fmc_hdmi/refmanual you will find out that, the  FMC EEPROM contents do not conform to the VITA 57.1 FPGA Mezzanine Card (FMC) Standard. We have an workaround for this issue. Please check this link:  https://github.com/Digilent/FMC-HDMI-frufix. Please try to reprogram the eeprom, and after that check again the solutions given by @jpeyron. Thank you.

Best Regards,

Bogdan Vanca

 

Share this post


Link to post
Share on other sites
  • 0

Hi Bogdan Vanca,

I already tried the frufix, the log as below:
----------------------------------------------------------
FMC-HDMI IPMI FRU programmer
This app checks the FRU data in the EEPROM on the FMC-HDMI and upgrades it, if necessary.
----------------------------------------------------------
FRU ID in EEPROM 0x02
FRU_ID in programmer 0x02
No upgrade needed. Force upgrade? [y/n]
Starting the FMC EEprom program...
Generating IPMI...
Writing IPMI data to EEprom address 0...
Reading back IPMI data from EEprom address 0...
Verifying data...
Writing IPMI data to EEprom address 16...
Reading back IPMI data from EEprom address 16...
Verifying data...
Writing IPMI data to EEprom address 32...
Reading back IPMI data from EEprom address 32...
Verifying data...
Writing IPMI data to EEprom address 48...
Reading back IPMI data from EEprom address 48...
Verifying data...
Writing IPMI data to EEprom address 64...
Reading back IPMI data from EEprom address 64...
Verifying data...
Writing IPMI data to EEprom address 80...
Reading back IPMI data from EEprom address 80...
Verifying data...
Writing IPMI data to EEprom address 96...
Reading back IPMI data from EEprom address 96...
Verifying data...
Writing IPMI data to EEprom address 112...
Reading back IPMI data from EEprom address 112...
Verifying data...
Writing IPMI data to EEprom address 128...
Reading back IPMI data from EEprom address 128...
Verifying data...
Writing IPMI data to EEprom address 144...
Reading back IPMI data from EEprom address 144...
Verifying data...
Writing IPMI data to EEprom address 160...
Reading back IPMI data from EEprom address 160...
Verifying data...
Done, exiting.
Upgrade succeeded

But I still met the issue when I tried to config i2c reset.
This symptom was found both on zc702 and zedboard with the same hdmi-fmc.
Does it possible HW issue of hdmi-fmc?
If yes, how to check it efficiently and immediately?

Thanks.

BR
Blake

Share this post


Link to post
Share on other sites
  • 0

Hello @Blake,

Yes, right now is possible for you to have an hardware issue. I will also try on the ZedBoard project given by @jpeyron. I will test it, I hope that I have some functional fmc-hdmi devices in here, and after that I will make an bin file for you, in order to test your device. If we will conclude that you have some hardware issues, I will go further with the replacement request procedure to our sales department. Thank you.       

Share this post


Link to post
Share on other sites
  • 0

Hello @Blake,

For me it works. So, there are big chances for you to have an defective device. In order to raise the replacement request please send me in private the fallowing info:

1.      Date of Purchase:
2.      Seller:
3.      Purchase Order/ Web order Number:
4.      Serial Number:

Thank you.

 

Best Regards,

Bogdan Vanca 

Share this post


Link to post
Share on other sites
  • 0

Hi @Blake,

Since the board was not purchased from Digilent directly, you will need to pursue an RMA with Haley Technology (note that we don't have control over what they decide to do) and then Haley Technology will pursue their own RMA with Digilent as needed.

Thank you,
JColvin

Share this post


Link to post
Share on other sites
  • 0

Hi JColvin,

I already entrusted the agent to handle the replacement request, thanks.

Hi Bogdan Vanca,

We also ordered another HDMI-FMC which is in the purchase process.
Could you provide the bin file that you previously mentioned for quickly verifying HDMI-FMC?
It will be helpful for us to verify HDMI-FMC quickly, thanks.

BR
Blake

Share this post


Link to post
Share on other sites
  • 0

Hello @Blake,

I've used the project provided by @jpeyron, an I was able to test the I2C interface communication. I will see if I can make you an different project for testing your device. Thank you. 

Best Regards,

Bogdan Vanca   

Share this post


Link to post
Share on other sites
  • 0

Hi Sirs, 

Unfortunately, I got confused again.
We already received another HDMI-FMC card, but the symptom was the same.

 I found some new message when I first time to upgrade EEPROM via FRU programmer.

*****************************************************************************
---------------------------------------------------------- 
FMC-HDMI IPMI FRU programmer 
This app checks the FRU data in the EEPROM on the FMC-HDMI and upgrades it, if necessary. 
---------------------------------------------------------- 
Common Header Checksum failed. 
Invalid FRU data. Force upgrade? [y/n] 
Please enter FMC-HDMI serial number (seven characters just below the barcode): 

Starting the FMC EEprom program... 
Generating IPMI... 
Writing IPMI data to EEprom address 0... 
Reading back IPMI data from EEprom address 0... 
Verifying data... 
Writing IPMI data to EEprom address 16... 
Reading back IPMI data from EEprom address 16... 
Verifying data... 
Writing IPMI data to EEprom address 32... 
Reading back IPMI data from EEprom address 32... 
Verifying data... 
Writing IPMI data to EEprom address 48... 
Reading back IPMI data from EEprom address 48... 
Verifying data... 
Writing IPMI data to EEprom address 64... 
Reading back IPMI data from EEprom address 64... 
Verifying data... 
Writing IPMI data to EEprom address 80... 
Reading back IPMI data from EEprom address 80... 
Verifying data... 
Writing IPMI data to EEprom address 96... 
Reading back IPMI data from EEprom address 96... 
Verifying data... 
Writing IPMI data to EEprom address 112... 
Reading back IPMI data from EEprom address 112... 
Verifying data... 
Writing IPMI data to EEprom address 128... 
Reading back IPMI data from EEprom address 128... 
Verifying data... 
Writing IPMI data to EEprom address 144... 
Reading back IPMI data from EEprom address 144... 
Verifying data... 
Writing IPMI data to EEprom address 160... 
Reading back IPMI data from EEprom address 160... 
Verifying data... 
Done, exiting. 
Upgrade succeeded.

*****************************************************************************

I think it will be a very small chance that we got two defect HDMI-FMC card with the same issue, right?
Therefore, do you have any idea about my situation?

BTW, when I build the project - Zed_FMC_HDMI; I met following critical warring. Does this have any effect?

image.thumb.png.71825116e60ca563f33e6125d8169284.png


BR
Blake

Edited by Blake

Share this post


Link to post
Share on other sites
  • 0

Hi Sir,

I already blocked by this issue for a long time, let me rearrange my problem clearly; and wish it helpful for us.
My purpose is to verify the input of HDMI-FMC with Zedboard, the connection environment as below :
Camera or NB output -> HDMI-FMC input1 -> Zedboard HDMI output -> Display

I tried the following sample projects :
1. LK tutorial + zc702 (base on original code without any modification)
I can see initial message from UART port without any error.
When I plug the hdmi connector to input1 of FMC, the LED(LD1) was on and the preview of camera was turned off.
But it is nothing happen on display.
I tried to set debug message and found the failure on i2c reset config as previous code flow.

2. Adam Taylor FMC-HDMI-Zed + Zedboard (base on original code without any modification)
Regardless, I programmed the original bitstream or generated by me; the UART log always showed  
"control 9 status F00 Error 7F00000 Int Status 0 H and V Size 1E00280 Detector Timing Status 7 Video Mode = 5"
I set the debug message again and found the same failure.

We originally suspected this is HW issue of FMC, but I just received another FMC last week and verified it with previous flow.
Unfortunately, the symptom was the same.
I think it will be a very small chance that we got two defect HDMI-FMC card with the same issue.


My question as below :
1. Does the failure of i2c reset config be a key point? Or we can just ignore it.

2. For the Zedboard, what config should we take care first?
e.g. the 
Vadj select J18, I used the default config of 2.5V.

3. For the sample code  Adam Taylor FMC-HDMI-Zed
3.1 
The constraint file - const.xdc as below :
# FMC2    
set_property PACKAGE_PIN M19 [get_ports {clk}];  # "FMC-LA00_CC_P"
set_property PACKAGE_PIN G16 [get_ports {hsync_in}];  # "FMC-LA19_N"
set_property PACKAGE_PIN E20 [get_ports {iic_0_scl_io}];  # "FMC-LA21_N"
set_property PACKAGE_PIN F19 [get_ports {active_video_in}];  # "FMC-LA22_N"
set_property PACKAGE_PIN G19 [get_ports {vsync_in}];  # "FMC-LA22_P"
set_property PACKAGE_PIN E15 [get_ports {GPIO_O}];  # "FMC-LA23_P"
set_property PACKAGE_PIN C22 [get_ports {Int_in}];  # "FMC-LA25_N"
set_property PACKAGE_PIN D22 [get_ports {iic_0_sda_io}];  # "FMC-LA25_P"

set_property IOSTANDARD LVCMOS18 [get_ports -of_objects [get_iobanks 34]];
set_property IOSTANDARD LVCMOS18 [get_ports -of_objects [get_iobanks 35]];


There are only defined the input of FMC, how about the HDMI output?
The default config is LVCMOS18, should I modify it? (although I already modified it to 2.5V, but nothing different)


3.2 Could you help to check the Block design as below :
image.thumb.png.0ef52aa3613400219e89890eb8ea5c79.png

4. For quickly verification, could you help to provide the bin file to verify the HDMI-FMC?

Finally, thank you very much for your help.

BR
Blake

Share this post


Link to post
Share on other sites
  • 0

Hi @Blake,

Sorry for the delay. Your issue was escalated and we'll return with an answer as soon as possible.

Thanks for the patience.

Best regards,

Bianca

Share this post


Link to post
Share on other sites
  • 0
On 11/2/2018 at 5:43 AM, Blake said:

Common Header Checksum failed. 

 

Invalid FRU data. Force upgrade? [y/n] 
Please enter FMC-HDMI serial number (seven characters just below the barcode): 

Hello Blake,

Sincere apologies for the process taking so long. I will have to ask for your patience again. @BogdanVanca will send you a test project for the Zedboard + FMC-HDMI combo and instructions on how to execute the tests that are also used in manufacturing.

I have to commend you for the clear description of the problem and all the debug work you already did. The message quoted above is expected for the first run on a new FMC-HDMI. It is unrelated to your issue.

Let's wait for the test project and see the results before we go further.

Share this post


Link to post
Share on other sites
  • 0

Hello @Blake,

I've created for you an image that test your FMC-HDMI adapter. It does a basic data transfer between the HDMI output of the ZedBoard and both of the adapter hdmi inputs. Prior to this it also uses all the I2C lines. Please check the .rar attached file. In order to recreate the test, please fallow the fallowing steps:

1.Make sure that you have everything in place, check the bellow instructions and the first image.

  • Connect USB cable from PC to ZED USB PROG port (J17)
  • Connect USB cable from PC to ZED UART port (J14)
  • Connect FMC-HDMI board to FMC connector J1 (of ZED)
  • Connect Power cable to J20 (of ZED)
  • Set mode jumpers for JTAG programming (all to GND)
  • Set J18 (of ZED) jumpers to 3V3 or 2V5. I'v tested both variants.
  • Create a loop between HDMI-OUT J9(ZED) and FMC-HDMI IN1 of the adapter.
  • Turn ZED board onIMG_20181114_133648.thumb.jpg.8416c40c67932205763223175dcebee8.jpg

2. Open Vivado (I used Vivado 2017.4).

  • Open Vivado, and click on Open Hardware Manager within the Welcome Page.
  • After this click on Auto-Connect.
  • You should see the Zed into the upper left panel.Check the image bellow.

step_1.thumb.PNG.c4c79b65cc7a2d0c90813c14b037a9be.PNG

3. Add Configuration Memory Device

  • Right click on xc7z020_1 and choose "Add Configuration Memory Device". Check image bellow.step_2.thumb.png.2dd139802d368da372476d120d841e5b.png

4. Choose the right memory device for ZED. 

  • Please choose "s25fl256s-3.3v-qspi-x1-dual_stacked" from the list. Click to program the device. Check images bellow.step_3.thumb.png.dcc0ab78e183d28417bfe5c8a761ed58.pngstep_4.thumb.png.7aa1439c2dc8e0e745411b791c94b3bf.png

 

 5.Program the device with the files attached to this message.

  • For "Configuration file" you choose BOOT.bin.
  • For "Zynq Fsbl" you choose fsbl.elf. 
  • Click OK.

step_5.thumb.png.f7d8846f22e41ab1b07aee63fb216642.png

6. Wait until it gets programmed. After finish, you click OK. step_6.thumb.png.c42fe620eddb93891fd27411dc02be17.pngstep_7.thumb.png.e218307814abe79f17bcd45bf6095983.png

7. Prepare the board for testing. 

  • Open a serial terminal, termite, putty, teraterm etc. Find the COM port and choose 115200 for baud rate.
  • Set jumpers for QSPI programming (MIO5 on 3V3 and SIG, the others on 3V3 and GND).
  • Power OFF the Board.
  • Power ON  the Board. 
  • The image should boot. See the image bellow.  

IMG_20181114_134554.thumb.jpg.d872cd13fefac2161e95d3dcb31fde12.jpg

8.Do the actually test.

  • Make sure that the HDMI-OUT (ZED) is connected to HDMI-IN1 of the FMC-HDMI adapter. 
  • Press ENTER.
  • Wait for the test to finalize. 

step_8.thumb.png.4fba02f37b87954e2da4e3deaad7eb61.png

  • Make sure that the HDMI-OUT (ZED) is connected to HDMI-IN2 of the FMC-HDMI adapter. Make sure that your adapter is not loose
  • Press ENTER.
  • Wait for the test to finalize.step_9.thumb.png.d1a91b63353fee23a3914b5583f798c7.png

9.Check the results, and give me an update :) .

 

image.rar

Edited by BogdanVanca

Share this post


Link to post
Share on other sites
  • 0

Hi BogdanVanca,

First, thank you very much for your full and clear support.:)
The test result as below :
DDR audio write: started.
DDR audio write: completed (total 34).
DDR video write: started (length 2073600)
----------------------------------------------------------
Digilent FMC-HDMI adapter Test
----------------------------------------------------------
Please connect the HDMI cable to the first input (HDMI1 IN), and after that press ENTER to continue
Start testing the first input of the FMC-HDMI adapter (HDMI1 IN)

MM2S Status: 0x10001
Configuring HDMI Output (ADV7511).
MM2S Status (after config.): 0x10001
S2MM Status: 0x10001
Configuring HDMI Input (ADV7611).
S2MM Status (after config.): 0x10001
Starting the Audio I2S testing...
Audio data: 0x0
Audio data: 0x0
Audio data: 0x0
Audio data: 0x0
Audio data: 0x0
Audio data: 0x0
Audio data: 0x0
Audio data: 0x0
Audio data: 0x0
Audio data: 0x0
Audio data: 0x0
Audio data: 0x0
Audio data: 0x0
Audio data: 0x0
Audio data: 0x0
Audio data: 0x0
Audio data: 0x0
Audio data: 0x0
Audio data: 0x0
Audio data: 0x0
Audio data: 0x0
Audio data: 0x0
Audio data: 0x0
Audio data: 0x0
Audio data: 0x0
Audio data: 0x0
Audio data: 0x7F81B380
Audio data: 0x7EAF3400
Audio data: 0x7F37FC00
Audio data: 0x7DEAA000
Audio data: 0x79BFE000
Audio data: 0x77AA8000
> Right audio channel OK.
Audio data: 0x77AA8000
Audio data: 0x55E68000
> Left audio channel OK.
> State of the INT1 before config.: 1
> State of the INT1 after config.: 0

Starting the CEC testing...
Sending CEC packet.
-----------------------------------------------------------

HDMI1: PASS
-----------------------------------------------------------
The test for the first input of the FMC-HDMI adapter has ended
Please connect the HDMI cable to the second input (HDMI2 IN), make sure that the adapter didn't get loose and after that, press ENTER to continue
Start Testing the second input of the FMC-HDMI adapter (HDMI2 IN)

Configuring HDMI Output (ADV7511).
Sending CEC packet.
-----------------------------------------------------------

HDMI2-IN: PASS
-----------------------------------------------------------
The test for the second input of the FMC-HDMI adapter has ended
----------------------------------------------------------
Digilent FMC-HDMI adapter Test has ended
----------------------------------------------------------

The test results were similar on my both hdmi-FMC, I think my HW should run well; right?

Now my question is why we used the same project (e.g. Adam Taylor FMC-HDMI-Zed) but couldn't get the expected result?
About the I2C reset fail of initial process of FMC(ADV7611), does it a key point of initial process or I can just ignore it?
Especially, I met the same failed point in different project (LK tutorial / Adam Taylor FMC-HDMI-Zed) with different platform (ZC702 / Zedboard).

BR
Blake

Share this post


Link to post
Share on other sites
  • 0

Hello @Blake,

I have done some digging into Adam project and I reached to some conclusions. I will start from your serial terminal message:


"control 9 status F00 Error 7F00000 Int Status 0 H and V Size 1E00280 Detector Timing Status 7 Video Mode = 5"

On a first glimpse, if you look into the .xdc file of the project, you will found out that this project doesn't output anything on Zed HDMI Output. It only uses a couple of the FMC-HDMI inputs, so is normal for you to don't see anything on your monitor. The message that you see on the serial terminal, outputs the content of some state registers within Video Timing Controller ip (please check this document:https://www.xilinx.com/support/documentation/ip_documentation/v_tc/v6_1/pg016_v_tc.pdf). Those registers are useful for testing your software application and the adapter. Your message tells me that your project actually works, and let me tell you why:

The fallowing number : "1E00280"  is the horizontal and vertical frame size,  without blanking of your HDMI source, where 1E0 is equal with 480, and 0280 is equal with 640, both in decimal. Also the value "5" of the Video Mode, is the returned by this function "u16 XVtc_GetDetectorVideoMode(XVtc *InstancePtr)". This function gets the video mode currently reported by the detector in the VTC core. The number 5 points to Video mode VGA. You can check that into the xvtc.h header file. You can check the rest of the registers by accessing the link. 

Regarding to your debug message, you don't have to add it, because this function XIicPs_MasterSendPolled(&Iic, SendBuffer,2, IIC_SLAVE_ADDR) from Adam code, check line 132, checks for completion of transfer. So, I think that your problem may come from the way you wrote your verification algorithm. You can check for example if you used the correct base address for the iic driver instance. For that you can look into the function above, and check if your base-address match to the one that this function uses. 

Unfortunately I don't know why the lk project doesn't work. I don't have the board, so I cannot test it. 

I will try to clean Adam hardware project from errors, and after that you may adapt it for ZCU102. For now,  I think that this would be a good starting point.

Best Regards,

Bogdan Vanca  

 

 

 

Share this post


Link to post
Share on other sites
  • 0

Hi BogdanVanca,

I must thank you again for your detailed explanation.
My question as below :
1. 
No matter I plugged hdmi input source into input of FMC or not, the return message was the same.
I think the message of frame size (480x640) and video mode 5 (VGA) were the default message.
Therefore, the project seems to not detect the input source from FMC, right?  (My input source/path is NB's display port -> DP to HDMI -> HDMI_IN of FMC)

2.
I don't understand following sentence very well.
"I think that your problem may come from the way you wrote your verification algorithm."
Actually, I don't change the code flow of this project; I just add some debug message to check the initial flow.
I also print the address of each step as below :
Hello World
SendBuffer[0] = ff
SendBuffer[1] = 80
iic_IO_hdmi_config[0][0] = ff
iic_IO_hdmi_config[0][1] = 80
~~~ XST_FAILURE
SendBuffer[0] = f4
SendBuffer[1] = 80
iic_IO_hdmi_config[1][0] = f4
iic_IO_hdmi_config[1][1] = 80
SendBuffer[0] = f5
SendBuffer[1] = 7c
iic_IO_hdmi_config[2][0] = f5
iic_IO_hdmi_config[2][1] = 7c
SendBuffer[0] = f8
SendBuffer[1] = 4c
iic_IO_hdmi_config[3][0] = f8
iic_IO_hdmi_config[3][1] = 4c
SendBuffer[0] = f9
SendBuffer[1] = 64
iic_IO_hdmi_config[4][0] = f9
iic_IO_hdmi_config[4][1] = 64
SendBuffer[0] = fa
SendBuffer[1] = 6c
iic_IO_hdmi_config[5][0] = fa
iic_IO_hdmi_config[5][1] = 6c
SendBuffer[0] = fb
SendBuffer[1] = 68
iic_IO_hdmi_config[6][0] = fb
iic_IO_hdmi_config[6][1] = 68
SendBuffer[0] = fd
SendBuffer[1] = 44
iic_IO_hdmi_config[7][0] = fd
iic_IO_hdmi_config[7][1] = 44
SendBuffer[0] = 1
SendBuffer[1] = 6
iic_IO_hdmi_config[8][0] = 1
iic_IO_hdmi_config[8][1] = 6
SendBuffer[0] = 2
SendBuffer[1] = f5
iic_IO_hdmi_config[9][0] = 2
iic_IO_hdmi_config[9][1] = f5
SendBuffer[0] = 3
SendBuffer[1] = 80
iic_IO_hdmi_config[10][0] = 3
iic_IO_hdmi_config[10][1] = 80
SendBuffer[0] = 5
SendBuffer[1] = 28
iic_IO_hdmi_config[11][0] = 5
iic_IO_hdmi_config[11][1] = 28
SendBuffer[0] = 6
SendBuffer[1] = a6
iic_IO_hdmi_config[12][0] = 6
iic_IO_hdmi_config[12][1] = a6
SendBuffer[0] = b
SendBuffer[1] = 44
iic_IO_hdmi_config[13][0] = b
iic_IO_hdmi_config[13][1] = 44
SendBuffer[0] = c
SendBuffer[1] = 42
iic_IO_hdmi_config[14][0] = c
iic_IO_hdmi_config[14][1] = 42
SendBuffer[0] = 14
SendBuffer[1] = 7f
iic_IO_hdmi_config[15][0] = 14
iic_IO_hdmi_config[15][1] = 7f
SendBuffer[0] = 15
SendBuffer[1] = 80
iic_IO_hdmi_config[16][0] = 15
iic_IO_hdmi_config[16][1] = 80
SendBuffer[0] = 19
SendBuffer[1] = 83
iic_IO_hdmi_config[17][0] = 19
iic_IO_hdmi_config[17][1] = 83
SendBuffer[0] = 33
SendBuffer[1] = 40
iic_IO_hdmi_config[18][0] = 33
iic_IO_hdmi_config[18][1] = 40
62
 Control 9 Status F00 Error 7F0000 Int Status 0 H and V Size 1E00280 Detector Timing Status 7 Video Mode = 5

If I just want to transfer the hdmi input signal from fmc to hdmi output of Zedboard, is there any sample project for reference?
Thanks.


BR
Blake

Share this post


Link to post
Share on other sites
  • 0

Hello @Blake,

1.  Yes, you are right. I did not know that your message remain the same, regardless if there was a connection or not.

2.  Please send me your entire project, as it is. I will go trough it and I will do all the debugging.

"If I just want to transfer the hdmi input signal from fmc to hdmi output of Zedboard, is there any sample project for reference?"

We are working on it. I will update you with the project as soon as we finish it. Again, sorry for the long process into solving your issue. 

 

Best Regards,

Bogdan Vanca 
 

 

Share this post


Link to post
Share on other sites
  • 0

Hello @Blake

Check out the attached file. It does a functional test for your adapter. You have to connect a VGA monitor to Zed VGA output, and create a loop-back between Zed HDMI output and HDMI IN2 of the adapter. Please give me an update after you finish. Thank you. 

image.rar

Share this post


Link to post
Share on other sites
  • 0

Hi Bogdan Vanca,

1. My project as the following link : (upload file limit is 1.9 mb only)
https://www.dropbox.com/s/j9no96qzs4ef7ib/zed_fmc.7z?dl=0
I just add debug message only.

2. The test result from UART as below :
----------------------------------------------------------
FMC-HDMI Board Manufacturing Test
----------------------------------------------------------
HDMI2-IN to ZED Out: PASS

I can also see colored output from monitor (Zed VGA out -> display VGA in).
Zed hdmi out -> hdmi-FMC in2

Thanks.

BR
Blake

Edited by Blake

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now