🇺🇦 haxadecimal<p>Renesas took more than two years to revise the silicon from the sampled rev AA to production rev BB, and that's the best fix they could come up with?</p><p>This suggests to me that they didn't have their "A team" working the problem.</p><p><a href="https://mastodon.social/tags/renesas" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>renesas</span></a> <a href="https://mastodon.social/tags/forgefpga" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>forgefpga</span></a></p>
techhub.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A hub primarily for passionate technologists, but everyone is welcome
Administered by:
Server stats:
4.6Kactive users
techhub.social: About · Status · Profiles directory · Privacy policy
Mastodon: About · Get the app · Keyboard shortcuts · View source code · v4.4.2
#forgefpga
0 posts · 0 participants · 0 posts today
🇺🇦 haxadecimal<p>Renesas released the datasheet for production rev BB of their ForgeFPGA SLG47910. They fixed the rev AA errata of not being able to use the part at Vdd=3.3V without raising Vcore to 1.5V (normally 1.2V).</p><p>The fix is that Vdd and Vddio are now specified to a maximum of 2.75V, for use at a nominal 2.5V.</p><p>Most of the potential uses I had for a super-cheap low-demsity FPGA in a tiny 3x3mm QFN are no longer viable when I would need level shifting for 3.3V I/O.</p><p><a href="https://mastodon.social/tags/renesas" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>renesas</span></a> <a href="https://mastodon.social/tags/forgefpga" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>forgefpga</span></a><br>1/</p>
TrendingLive feeds
Mastodon is the best way to keep up with what's happening.
Follow anyone across the fediverse and see it all in chronological order. No algorithms, ads, or clickbait in sight.
Create accountLoginDrag & drop to upload