Re: [M-Labs devel] Testing new Mixxeo boards
AFAIR yes, on all boards. I've had to manually set video output (xrandr --addmode). I've tried with two computers: - Dell laptop, Core i7 Ivy Bridge, Intel graphics, Debian testing, kernel 3.12 - custom PC, Core i3 Ivy Bridge, Radeon X550, CentOS 6.4, kernel 2.6.32 Unfortunately I don't have enough time to test it more thoroughly, so there are no I2C traces to post. Cheers, Adrian On 29/11/13 20:42, Sebastien Bourdeauducq wrote: On 11/29/2013 08:30 PM, Adrian Byszuk wrote: Both HDMI and DVI. Did HDMI DDC fail on all boards (i.e. no mode shown in xrandr)? What is the configuration of the computer you used to test (graphics card, driver, operating system)? Have you tried with another computer? Can you post logic analyzer traces of the SDA and SDC signals? Thanks, Sebastien ___ Devel mailing list Devel@lists.milkymist.org https://ssl.serverraum.org/lists/listinfo/devel
Re: [M-Labs devel] Testing new Mixxeo boards
All boards tested. There were a few minor errors in mounting of PCB that we corrected. All HDMI inputs work, VGA and DVI outputs work. Ethernet works. DDC channel wasn't tested. Regards, Adrian On Wed 27 Nov 2013 19:45:41 CET, Adrian Byszuk wrote: Now it looks much better. I'm still not able to get EDID information (will look into that), but manually enabling HDMI output seems to work and I can see such output on console: dvisampler0: ph: 8 135 // charsync:111 [4 4 4] // WER: 0 0 0 // chansync:1 // res:1024x768 dvisampler0: ph: 9 146 // charsync:111 [4 4 4] // WER: 0 0 0 // chansync:1 // res:1024x768 dvisampler0: ph: 8 137 // charsync:111 [4 4 4] // WER: 0 0 0 // chansync:1 // res:1024x768 dvisampler0: ph: 7 146 // charsync:111 [4 4 4] // WER: 0 0 0 // chansync:1 // res:1024x768 I'll continue testing tomorrow. Adrian On 27/11/13 16:21, Sébastien Bourdeauducq wrote: On 11/27/2013 03:55 PM, Adrian Byszuk wrote: Does it keep printing that (it should repeat at ~1Hz), or does it go into the disconnected state immediately after? It goes into disconnected state immediately after. Basically screen is flooded with these messages. That could be the Spartan-6 PLL phantom lock feature. I guess you did not have the HDMI output enabled on your laptop? I have added a filter later on the PLL lock output to fix this bug. The new binaries below should not have the problem. This is weird... Don't you see any other messages before the freeze? No, it's just that it freezes suddenly. I've checked this with another board and I have the same symptoms. It even freezes much sooner, always after 'Executing booted program.' line. I just tried this exact binary on a board I have and it also tends to be very unstable, even though it does not crash immediately after startup here. It could be a ISE timing model/PR intermittent bug that affected that bitstream, it happens sometimes... I have compiled new binaries that hopefully will address both problems (you need to reflash bios.bin): http://milkymist.org/mixxeo_binaries_2.tar.bz2 I did not trust ISE this time and verified that everything is stable enough on the board... Press capital 'D' after videomixer.bin is loaded to enable HDMI debugging messages. You can also press 'm' to display the memory bandwidth statistics (it does not do so every second like the old firmware did). Additionally, you will find the memtest.bin firmware that you can netboot to stress-test the SDRAM. Sebastien ___ Devel mailing list Devel@lists.milkymist.org https://ssl.serverraum.org/lists/listinfo/devel
Re: [M-Labs devel] Testing new Mixxeo boards
Hi, On 11/29/2013 05:38 PM, Adrian Byszuk wrote: All boards tested. There were a few minor errors in mounting of PCB that we corrected. All HDMI inputs work, VGA and DVI outputs work. Ethernet works. Excellent news :) DDC channel wasn't tested. Which one? On the HDMI input ports, or on the DVI output port? Regards, Sebastien ___ Devel mailing list Devel@lists.milkymist.org https://ssl.serverraum.org/lists/listinfo/devel
Re: [M-Labs devel] Testing new Mixxeo boards
On 11/29/2013 08:30 PM, Adrian Byszuk wrote: Both HDMI and DVI. Did HDMI DDC fail on all boards (i.e. no mode shown in xrandr)? What is the configuration of the computer you used to test (graphics card, driver, operating system)? Have you tried with another computer? Can you post logic analyzer traces of the SDA and SDC signals? Thanks, Sebastien ___ Devel mailing list Devel@lists.milkymist.org https://ssl.serverraum.org/lists/listinfo/devel
Re: [M-Labs devel] Testing new Mixxeo boards
OK, I'm back after another debugging session. With the soc-mixxeo-ports23 bitstream I get something like this in console when connecting to port HDMI3: dvisampler1: PLL locked IDELAY busy timeout dvisampler1: delays calibrated dvisampler1: phase init OK dvisampler1: ph: 000 // charsync:000 [0 0 0] // WER: 0 0 0 // chansync:0 // res:0x0 dvisampler1: disconnected dvisampler1: connected dvisampler1: disconnected dvisampler1: connected dvisampler1: disconnected dvisampler1: connected dvisampler1: PLL locked IDELAY busy timeout dvisampler1: delays calibrated dvisampler1: phase init OK dvisampler1: ph: 000 // charsync:000 [0 0 0] // WER: 0 0 0 // chansync:0 // res:0x0 dvisampler1: disconnected dvisampler1: connected (...) when connecting to port HDMI2: dvisampler1: connected dvisampler1: disconnected dvisampler1: connected dvisampler1: disconnected (...) BUT, I think that with soc-mixxeo.bit bitstream SoC hangs soon after loading netboot firmware because with the ports23 bitstream I can see a continous output stream on console: read: 3008Mbps write:0Mbps all: 3008Mbps also, LED2 is blinking with ~1Hz frequency. With the ports01 bistream console output freezes soon after loading netboot firmware, for example during read: 3008Mbps write:0Mbps all: 3008Mbps or waiting for LOCKED...ok and LED2 stops blinking. Adrian On Wed 27 Nov 2013 12:00:26 CET, Sébastien Bourdeauducq wrote: Hi, On 11/27/2013 11:57 AM, Adrian Byszuk wrote: However HDMI connection still doesn't work. Some facts that I was able to check when comparing with schematics on OHWR (tested on HDMI_0 port): - +5V voltage is available on HDMI pin 18 - HPD signal (pin 19) stays low - HDMI0_HPD_NOTIF signal has 3.6V - HDMI0_HPD_EN has 0V Any ideas what to do next? Do you think it's firmware issue or should I check PCB? What happens with the other three HDMI ports? If HDMI0_HPD_NOTIF goes high, the firmware should print a message on the console and then drive HDMI0_HPD_EN. But maybe it is looking at the other ports (there is one bitstream for ports 0/1 and another one for ports 2/3 - check that they are not mistaken, e.g. try all 4 ports with the same bitstream), or there is a connectivity problem between your measurement point of HDMI0_HPD_NOTIF and the FPGA pad. Sebastien ___ Devel mailing list Devel@lists.milkymist.org https://ssl.serverraum.org/lists/listinfo/devel
Re: [M-Labs devel] Testing new Mixxeo boards
Hi, On 11/27/2013 01:44 PM, Adrian Byszuk wrote: With the soc-mixxeo-ports23 bitstream I get something like this in console when connecting to port HDMI3: dvisampler1: PLL locked IDELAY busy timeout dvisampler1: delays calibrated dvisampler1: phase init OK dvisampler1: ph: 000 // charsync:000 [0 0 0] // WER: 0 0 0 // chansync:0 // res:0x0 Does it keep printing that (it should repeat at ~1Hz), or does it go into the disconnected state immediately after? You should not have the IDELAY busy timeout messages, and the numbers should be non-zero. Also WER=0 means either no transmission errors (which is unlikely since the delay calibration failed) or no data at all (signal lines completely idle). Have you checked the TMDS signals for short circuits, possibly coming from the TVS solders? BUT, I think that with soc-mixxeo.bit bitstream SoC hangs soon after loading netboot firmware because with the ports23 bitstream I can see a continous output stream on console: read: 3008Mbps write:0Mbps all: 3008Mbps also, LED2 is blinking with ~1Hz frequency. Yes, you should keep seeing those messages on the console while the firmware is running. LED2 is just the serial transmission indicator, hardwired to the FTDI-chip. With the ports01 bistream console output freezes soon after loading netboot firmware, for example during read: 3008Mbps write:0Mbps all: 3008Mbps or waiting for LOCKED...ok and LED2 stops blinking. This is weird... Don't you see any other messages before the freeze? Sebastien ___ Devel mailing list Devel@lists.milkymist.org https://ssl.serverraum.org/lists/listinfo/devel
Re: [M-Labs devel] Testing new Mixxeo boards
On 27/11/13 13:55, Sébastien Bourdeauducq wrote: Hi, On 11/27/2013 01:44 PM, Adrian Byszuk wrote: With the soc-mixxeo-ports23 bitstream I get something like this in console when connecting to port HDMI3: dvisampler1: PLL locked IDELAY busy timeout dvisampler1: delays calibrated dvisampler1: phase init OK dvisampler1: ph: 000 // charsync:000 [0 0 0] // WER: 0 0 0 // chansync:0 // res:0x0 Does it keep printing that (it should repeat at ~1Hz), or does it go into the disconnected state immediately after? It goes into disconnected state immediately after. Basically screen is flooded with these messages. You should not have the IDELAY busy timeout messages, and the numbers should be non-zero. Also WER=0 means either no transmission errors (which is unlikely since the delay calibration failed) or no data at all (signal lines completely idle). Have you checked the TMDS signals for short circuits, possibly coming from the TVS solders? I've just did a quick check, and these lines seem to be OK, but I'll check it again. With the ports01 bistream console output freezes soon after loading netboot firmware, for example during read: 3008Mbps write:0Mbps all: 3008Mbps or waiting for LOCKED...ok and LED2 stops blinking. This is weird... Don't you see any other messages before the freeze? No, it's just that it freezes suddenly. I've checked this with another board and I have the same symptoms. It even freezes much sooner, always after 'Executing booted program.' line. Sebastien ___ Devel mailing list Devel@lists.milkymist.org https://ssl.serverraum.org/lists/listinfo/devel
Re: [M-Labs devel] Testing new Mixxeo boards
On 11/27/2013 03:55 PM, Adrian Byszuk wrote: Does it keep printing that (it should repeat at ~1Hz), or does it go into the disconnected state immediately after? It goes into disconnected state immediately after. Basically screen is flooded with these messages. That could be the Spartan-6 PLL phantom lock feature. I guess you did not have the HDMI output enabled on your laptop? I have added a filter later on the PLL lock output to fix this bug. The new binaries below should not have the problem. This is weird... Don't you see any other messages before the freeze? No, it's just that it freezes suddenly. I've checked this with another board and I have the same symptoms. It even freezes much sooner, always after 'Executing booted program.' line. I just tried this exact binary on a board I have and it also tends to be very unstable, even though it does not crash immediately after startup here. It could be a ISE timing model/PR intermittent bug that affected that bitstream, it happens sometimes... I have compiled new binaries that hopefully will address both problems (you need to reflash bios.bin): http://milkymist.org/mixxeo_binaries_2.tar.bz2 I did not trust ISE this time and verified that everything is stable enough on the board... Press capital 'D' after videomixer.bin is loaded to enable HDMI debugging messages. You can also press 'm' to display the memory bandwidth statistics (it does not do so every second like the old firmware did). Additionally, you will find the memtest.bin firmware that you can netboot to stress-test the SDRAM. Sebastien ___ Devel mailing list Devel@lists.milkymist.org https://ssl.serverraum.org/lists/listinfo/devel
Re: [M-Labs devel] Testing new Mixxeo boards
Now it looks much better. I'm still not able to get EDID information (will look into that), but manually enabling HDMI output seems to work and I can see such output on console: dvisampler0: ph: 8 135 // charsync:111 [4 4 4] // WER: 0 0 0 // chansync:1 // res:1024x768 dvisampler0: ph: 9 146 // charsync:111 [4 4 4] // WER: 0 0 0 // chansync:1 // res:1024x768 dvisampler0: ph: 8 137 // charsync:111 [4 4 4] // WER: 0 0 0 // chansync:1 // res:1024x768 dvisampler0: ph: 7 146 // charsync:111 [4 4 4] // WER: 0 0 0 // chansync:1 // res:1024x768 I'll continue testing tomorrow. Adrian On 27/11/13 16:21, Sébastien Bourdeauducq wrote: On 11/27/2013 03:55 PM, Adrian Byszuk wrote: Does it keep printing that (it should repeat at ~1Hz), or does it go into the disconnected state immediately after? It goes into disconnected state immediately after. Basically screen is flooded with these messages. That could be the Spartan-6 PLL phantom lock feature. I guess you did not have the HDMI output enabled on your laptop? I have added a filter later on the PLL lock output to fix this bug. The new binaries below should not have the problem. This is weird... Don't you see any other messages before the freeze? No, it's just that it freezes suddenly. I've checked this with another board and I have the same symptoms. It even freezes much sooner, always after 'Executing booted program.' line. I just tried this exact binary on a board I have and it also tends to be very unstable, even though it does not crash immediately after startup here. It could be a ISE timing model/PR intermittent bug that affected that bitstream, it happens sometimes... I have compiled new binaries that hopefully will address both problems (you need to reflash bios.bin): http://milkymist.org/mixxeo_binaries_2.tar.bz2 I did not trust ISE this time and verified that everything is stable enough on the board... Press capital 'D' after videomixer.bin is loaded to enable HDMI debugging messages. You can also press 'm' to display the memory bandwidth statistics (it does not do so every second like the old firmware did). Additionally, you will find the memtest.bin firmware that you can netboot to stress-test the SDRAM. Sebastien ___ Devel mailing list Devel@lists.milkymist.org https://ssl.serverraum.org/lists/listinfo/devel
[M-Labs devel] Testing new Mixxeo boards
Hi, I'm trying to test new PCBs according to instructions at: http://www.ohwr.org/projects/video-fpga-hdmi-dvi-ethernet/wiki/Bring_up_and_test_instructions However, with no luck so far. Are the instructions at wiki complete? Particularly, what about this TFTP server that is mentioned? Shouldn't I upload some additional firmware via netboot? I've succesfully flashed the SoC and BIOS with command 'm1nor-ng soc-mixxeo.fpg bios.bin'. HPD pin stays low. Currently, my testing fails at Connect HDMI ports 0 and 1 to video sources. My laptop doesn't detect the connection. Regards, Adrian ___ Devel mailing list Devel@lists.milkymist.org https://ssl.serverraum.org/lists/listinfo/devel
Re: [M-Labs devel] Testing new Mixxeo boards
Hi, On 11/26/2013 01:03 PM, Adrian Byszuk wrote: However, with no luck so far. Are the instructions at wiki complete? Particularly, what about this TFTP server that is mentioned? Shouldn't I upload some additional firmware via netboot? The board will download that firmware from the TFTP server, both at power-up and later if you enter netboot at the BIOS prompt (in case the first attempt failed). You can find it as videomixer.bin in the mixxeo_binaries_1.tar.bz2 archive I sent to Greg, rename it to boot.bin and place it at the root of the TFTP server. What do you see on the serial console? Open a serial terminal program such as GtkTerm on /dev/ttyUSB0 with 115200bps 8-N-1 communication parameters. I've succesfully flashed the SoC and BIOS with command 'm1nor-ng soc-mixxeo.fpg bios.bin'. HPD pin stays low. Yes, this is expected, and the videomixer.bin firmware should drive them high. Regards, Sebastien ___ Devel mailing list Devel@lists.milkymist.org https://ssl.serverraum.org/lists/listinfo/devel
