EDACafe Weekly Review September 26th, 2013

EDAC Seminar: EDA & Export Compliance
September 26, 2013  by Peggy Aycinena

 

EDAC hosted an evening seminar last week that could have taught you everything your company needs to know to meet your Export Compliance requirements – an unbelievably labyrinthine set of rules, created and nurtured by various agencies of the U.S. Government, that are designed in part to prevent sensitive technical IP from falling into the hands of less-than-totally-friendly nation states.

If you weren’t there on September 18th, you were not alone. A surprisingly small number of people showed up for the seminar, although the speaker, Cadence Group Director for Export Compliance and Government Relations Larry Disenhof, is clearly a walking encyclopedia on this stuff, and although EDAC did a great job publicizing the event.

If you didn’t attend EDA & Export Compliance, it was probably for one of two reasons:  Your team already knows everything they need to know in order to meet their export obligations, or your team is oblivious to the fact that these requirements are not optional; they’re obligatory and failure to comply can precipitate fines of $250,000 and up, loss of export privileges, cancellation of pending M&A’s, and even jail time.

At the Verification Bar: Solutions from Here to Eternity
September 26, 2013  by Peggy Aycinena

 

A Professor, a Sage, and a Guru walked into a bar. Brian the Bartender, greeted them: “What’ll it be, boys?”

The Professor said, “We need some help, Brian, settling an argument.”

“No problema,” Brian the Bartender said. “I’ve got an answer for everything.”

“Well,” the Professor said, “I think ESL’s not going to happen in our lifetime, but the Guru here says it’s just around the corner now that he and his have finally got all the pieces of the flow in place.”

Brian the Bartender laughed, “Yeah, the Guru’s been saying that since the dawn of mankind!”

“Exactly,” the Professor said.

Again Brian the Bartender laughed, “Guru, can you defend yourself? And don’t even think about plunking your wordy White Paper down on the bar. This is a public house, not a public library.”

Come Back to the Future – EDA Style!
September 25, 2013  by Rob van Blommestein

 

“Sold! To…” Is a phrase we expect to hear a lot on the evening of October 16th.  That’s the date when we celebrate the past 50+ years of EDA at the EDA: Back to the Future industry reunion hosted by EDAC.

Why do we expect to hear this phrase a lot you ask?  Well, part of the festivities will include silent and live auctions that will help raise money for the Computer History Museum’s EDA Oral Histories Collection and Exhibit.  We want to capture and preserve our rich history of EDA.  There will be items to bid on for every taste and budget.  You could be the one to win a lunch with Aart or go home with a case of private reserve wine.  Maybe you’re a sports fan.  If so, then a private tour of AT&T Park, an autographed baseball from Giants Brandon Belt, or a round of golf with three of your closest friends is more up your alley.  Are you a “foodie”?  Well, how about dinner at some of Mountain View’s finest eateries?

This event offers more than just a chance to walk away with something tangible.  You’ll be able to mingle and dine with industry luminaries – the who’s who in EDA’s past, present, and future.  What other event brings everyone together like that?

And what event would be complete without some laughs and a little mystery?  To find out what I mean, you’ll need to come.

So get those bidding paddles ready and register to attend the must-be-at event in EDA. – http://www.edac.org/events/back_to_the_future

Why Randomize?
September 24, 2013  by Jerry Kaczynski

Jim Lewis, VHDL Training Expert at SynthWorks (and founding member of OSVVM, which Aldec was an early adopter of) was kind enough to author a guest blog for Aldec. Here’s an excerpt:

After presenting a conference paper on how to do OSVVM-style constrained random and intelligent coverage (randomization based on functional coverage holes), I received  a great question, “Why Randomize?”

The easiest way to answer this is with an example.  Let’s look at a FIFO test – test a FIFO, write to it, read from it, write to it and read from it simultaneously, fill it and see that additional writes are held off successfully, and empty it and see that additional reads are held off successfully. 

Most certainly a FIFO can be tested using a directed test (just code, no randomization).  The following simulation waveform shows diffcount (the number of words in the FIFO) for a directed test.   The lowest value is empty.  The highest is full.  Using this, you can visually check off all of the required conditions and see that the FIFO is indeed tested.

For the rest of this article, visit the Aldec Design and Verification Blog.

Let’s Coin a New Phrase: There Is no “I” in “Startup”
September 24, 2013  by Tom Anderson, VP of Marketing

I had planned to write today about the TrekBox module, an essential part of TrekSoC that links the code running in the embedded processors with the I/O pins of an SoC. But, in the course of reviewing my various daily news digests, I read the curiously titled blog post “Tightlipped Unicorns & Monochrome Rainbows” on the Electronic Engineering Times site. It moved my thoughts in other directions entirely, so here is the result.

In the post, Radfan CTO Simon Barker argues that startups should be more honest about the challenges they face in order to obtain help or advice from those who’ve already lived through such adventures. He maintains that company founders who automatically say “Great!” when asked how things are going are missing an opportunity to garner such assistance and are wasting their time at startup events. This position triggered three major lines of thought for me.

Following the Roadmap to Successful Traceability
September 23, 2013  by Louie De Luna

If DO-254 is both the mission and the map required to achieve compliance, then traceability represents the roads on that map. Consider this.

– Roads connect two or more places on a map; traceability connects two or more elements in a project (such as functions, requirements, concept, design, verification data and test results).

– Road names help identify specific places that are linked to it; traceability names help identify specific project elements that are linked to it.

– In the absence of roads, reaching your destination is practically impossible;  in the absence of traceability achieving compliance is also practically impossible.



You are registered as: [johnny_pham@mentor.com].

CafeNews is a service for EDA professionals. EDACafe.com respects your online time and Internet privacy. Edit or Change my newsletter's profile details. Unsubscribe me from this newsletter.

Copyright © 2017, Internet Business Systems, Inc. — 25 North 14th Steet, Suite 710 San Jose, CA 95112 — +1 (408) 882-6554 — All rights reserved.