<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Open Source VHDL Verification Methodology | Thomas | Activity</title>
	<link>https://osvvm.org/members/tgbe/activity</link>
	<atom:link href="https://osvvm.org/members/tgbe/activity/feed" rel="self" type="application/rss+xml" />
	<description>Activity feed for Thomas.</description>
	<lastBuildDate>Wed, 24 Jun 2026 10:55:48 +0100</lastBuildDate>
	<generator>https://buddypress.org/?v=</generator>
	<language>en-US</language>
	<ttl>30</ttl>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>2</sy:updateFrequency>
	
						<item>
				<guid isPermaLink="false">1b4159998d0c85a8406050bc3390bc8d</guid>
				<title>Thomas replied to the topic Custom VC for image-sensor interface in the forum OSVVM</title>
				<link>https://osvvm.org/forums/topic/custom-vc-for-image-sensor-interface#post-2122</link>
				<pubDate>Tue, 13 Dec 2022 09:35:36 +0000</pubDate>

									<content:encoded><![CDATA[<p>Hi fpgaphreak,</p>
<p>I have two main goals with this test bench:</p>
<p>&#8211; Check that pixel values generated on the sensor input appear in the appropriate form on the AXI-Stream output, and completion interrupts and status registers are set correctly<br />
&#8211; Check that the interface logic is well-behaved in the case of errors on the LVDS inputs, i.e., no FSM&hellip;<span class="activity-read-more" id="activity-read-more-9193"><a href="https://osvvm.org/forums/topic/custom-vc-for-image-sensor-interface#post-2122" rel="nofollow ugc">[Read more]</a></span></p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">0b81b3d34cea073675692dd57d4395a7</guid>
				<title>Thomas replied to the topic Custom VC for image-sensor interface in the forum OSVVM</title>
				<link>https://osvvm.org/forums/topic/custom-vc-for-image-sensor-interface#post-2121</link>
				<pubDate>Tue, 13 Dec 2022 09:07:13 +0000</pubDate>

									<content:encoded><![CDATA[<p>Hi Jim,</p>
<p>thanks, I appreciate your detailed response. I have started implementing the VC with most parameters as model options. Originally I wanted to create a custom transaction type, but for now I am using the Stream MIT. I use the data parameter of Send() to pass the seed for pixel-data generation and generate a complete frame. This doesn&#8217;t&hellip;<span class="activity-read-more" id="activity-read-more-9192"><a href="https://osvvm.org/forums/topic/custom-vc-for-image-sensor-interface#post-2121" rel="nofollow ugc">[Read more]</a></span></p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">bdaf181a35b25feec549c0b7916bb7cd</guid>
				<title>Thomas started the topic Custom VC for image-sensor interface in the forum OSVVM</title>
				<link>https://osvvm.org/forums/topic/custom-vc-for-image-sensor-interface</link>
				<pubDate>Thu, 01 Dec 2022 09:28:36 +0000</pubDate>

									<content:encoded><![CDATA[<p>Hi,</p>
<p>we&#8217;re currently looking for a verification methodology to integrate into our VHDL-based FPGA flow. I&#8217;m interested in how to create stimulus for custom chip interfaces, in this case an image sensor with a proprietary serial interface with multiple LVDS lanes. The interface module translates the LVDS input into an AXI-Stream packet with video&hellip;<span class="activity-read-more" id="activity-read-more-9074"><a href="https://osvvm.org/forums/topic/custom-vc-for-image-sensor-interface" rel="nofollow ugc">[Read more]</a></span></p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">9169d6281f13eb05b3ec435e859f1445</guid>
				<title>Thomas became a registered member</title>
				<link>https://osvvm.org/activity/p/7287</link>
				<pubDate>Tue, 05 Apr 2022 12:02:16 +0100</pubDate>

				
									<slash:comments>0</slash:comments>
				
							</item>
		
	</channel>
</rss>