<?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 | fpgaphreak | Activity</title>
	<link>https://osvvm.org/members/engineer/activity</link>
	<atom:link href="https://osvvm.org/members/engineer/activity/feed" rel="self" type="application/rss+xml" />
	<description>Activity feed for fpgaphreak.</description>
	<lastBuildDate>Tue, 15 Sep 2026 01:22:50 +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">ca9cb9dee8fa779beb7e2f258e6c9d27</guid>
				<title>fpgaphreak started the topic case splitting in the forum OSVVM</title>
				<link>https://osvvm.org/forums/topic/case-splitting</link>
				<pubDate>Sun, 17 Mar 2024 01:55:11 +0000</pubDate>

									<content:encoded><![CDATA[<p>In some cases i need a full coverage of cases when doing simulations of timing critial circuits which cause deviations in behaviour. I would like to know if OSVVM supports this in any way.</p>
<p>To understand the issue I would like to describe the problem:</p>
<p>Take a signal of unknown phase and level and a synchronizer to get it into a circuit with an&hellip;<span class="activity-read-more" id="activity-read-more-10052"><a href="https://osvvm.org/forums/topic/case-splitting" rel="nofollow ugc">[Read more]</a></span></p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">b1b26512d10509cea22886131f0b73d2</guid>
				<title>fpgaphreak replied to the topic Creating Asynchronous Clocks in the forum OSVVM</title>
				<link>https://osvvm.org/forums/topic/creating-asynchronous-clocks#post-2358</link>
				<pubDate>Sun, 17 Mar 2024 01:28:48 +0000</pubDate>

									<content:encoded><![CDATA[<p>Me too. What is about Jitter Simulation with min/max definitions of the phase to simulate short term jitter effects?</p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">46c3465318021ff1e7c594182474086d</guid>
				<title>fpgaphreak replied to the topic I2C Bus pins simulation? in the forum VHDL</title>
				<link>https://osvvm.org/forums/topic/i2c-bus-pins-simulation#post-2357</link>
				<pubDate>Sun, 17 Mar 2024 01:21:59 +0000</pubDate>

									<content:encoded><![CDATA[<p>Although old, a late response: This topic is often discussed together with pull ups constrained in the XDC for a pin which hardly can be simulated. Together with timing demands and driver issues, which are the common problems at I2C I recommend to use an analog behaviour model which transforms both the outout of the VHDL Pin and its input to a&hellip;<span class="activity-read-more" id="activity-read-more-10050"><a href="https://osvvm.org/forums/topic/i2c-bus-pins-simulation#post-2357" rel="nofollow ugc">[Read more]</a></span></p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">86c6b8dcdf618fa6b709c303939e9ff9</guid>
				<title>fpgaphreak replied to the topic Xilinx not supporting VHDL anymore? in the forum VHDL</title>
				<link>https://osvvm.org/forums/topic/xilinx-not-supporting-vhdl-anymore#post-2356</link>
				<pubDate>Sun, 17 Mar 2024 01:16:16 +0000</pubDate>

									<content:encoded><![CDATA[<p>I think the complaint refers to the issue that the testbenches and example code for the design more and more is limited to Verilog for an unknown reason. Recently I again stumbled over a thing: A DDR Design cannot be built with an AXI-Interface in VHDL. The AXI is only available for Verilog.</p>
<p>Xilinx disreagards the fact that VHDL has certain&hellip;<span class="activity-read-more" id="activity-read-more-10049"><a href="https://osvvm.org/forums/topic/xilinx-not-supporting-vhdl-anymore#post-2356" rel="nofollow ugc">[Read more]</a></span></p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">6e3b1f83d516d738b313d61b5c2f2d27</guid>
				<title>fpgaphreak replied to the topic Questa-Intel &#038; Reports in the forum OSVVM</title>
				<link>https://osvvm.org/forums/topic/questa-intel-reports#post-2355</link>
				<pubDate>Sun, 17 Mar 2024 01:11:26 +0000</pubDate>

									<content:encoded><![CDATA[<p>Questa Intel, yes.</p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">c26821a41931e88cf5726b3cbe8dc442</guid>
				<title>fpgaphreak 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-2123</link>
				<pubDate>Tue, 13 Dec 2022 20:15:15 +0000</pubDate>

									<content:encoded><![CDATA[<p>So it seems more check for implementation issues rather than functional.(?)<br />
I wonder how and in wich way one could alternatively simulation LVDS issues. Foussing on driever behavior?</p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">fc778ee582ea0225ed0c3d155cbbee9f</guid>
				<title>fpgaphreak replied to the topic Questasim Version in the forum OSVVM</title>
				<link>https://osvvm.org/forums/topic/questasim-version#post-2120</link>
				<pubDate>Sun, 11 Dec 2022 03:10:51 +0000</pubDate>

									<content:encoded><![CDATA[<p>Was there any reaction of Siemens? I wonder who is working there at Questa anyway &#8211; i suggest these are the former Mentor programmers?</p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">8347466653d0ef7f58d23d24a04686e6</guid>
				<title>fpgaphreak replied to the topic Questa-Intel &#038; Reports in the forum OSVVM</title>
				<link>https://osvvm.org/forums/topic/questa-intel-reports#post-2119</link>
				<pubDate>Sun, 11 Dec 2022 03:05:51 +0000</pubDate>

									<content:encoded><![CDATA[<p>I have the same issue here, but only newer Questa. Formerly i did not recognize this. Possibly a config issue.</p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">52f55da1994a53649461f4217c3f6564</guid>
				<title>fpgaphreak 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-2118</link>
				<pubDate>Sun, 11 Dec 2022 03:00:46 +0000</pubDate>

									<content:encoded><![CDATA[<p>My question would be what the intention is in detail: Typically sensor interfaces are simulated and tested independently from the image content. Therefore I produced a test package capeable of driving various signal schemes and bahaviour into the lvds lines which can be simulated and also synthesized into an FPGA for real investigations of eye&hellip;<span class="activity-read-more" id="activity-read-more-9152"><a href="https://osvvm.org/forums/topic/custom-vc-for-image-sensor-interface#post-2118" rel="nofollow ugc">[Read more]</a></span></p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">8992e9c5a7d07d83886db5db0d68ccc7</guid>
				<title>fpgaphreak replied to the topic How to improve VHDL in the forum VHDL</title>
				<link>https://osvvm.org/forums/topic/how-to-improve-vhdl#post-2117</link>
				<pubDate>Sun, 11 Dec 2022 02:47:29 +0000</pubDate>

									<content:encoded><![CDATA[<p>I still do not like the ambigious way, vectors are treated agains signals, and that there is conversion required in between a(0 downto 0) = &#8220;1&#8221; instead of using &#8220;a(0) = &#8216;1&#8217;). See the bram addressing regarding their write enable. This is one signal only, however one uses 0&#8230;0 instead of a signal. So VHDL could be made more tolerant for that.</p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">0983aba40a39aab3dab1b091f91d4ab9</guid>
				<title>fpgaphreak&#039;s profile was updated</title>
				<link>https://osvvm.org/activity/p/9150</link>
				<pubDate>Sun, 11 Dec 2022 02:23:32 +0000</pubDate>

				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">b23f4cd964858c5f05f0e3bd55273cc7</guid>
				<title>fpgaphreak changed their profile picture</title>
				<link>https://osvvm.org/activity/p/9149</link>
				<pubDate>Sun, 11 Dec 2022 02:21:33 +0000</pubDate>

				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">0ad573619c8e9716d1fb81296be3cc17</guid>
				<title>fpgaphreak became a registered member</title>
				<link>https://osvvm.org/activity/p/9062</link>
				<pubDate>Tue, 29 Nov 2022 17:10:35 +0000</pubDate>

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