MEMORIES Expertise ?

[RealInfo]

Hi all

I am new to HDL and I am looking for an expertise direction.

Lately I came to conclusion that I want to focus on memories modeling from
all kinds , SRAM , ROM, FLASH etc.

My question is : Is it realistic to focus on memories modeling , is there a
market for such expertise.

I ask this because there are many free online models of memories but in the
other hand , there are many many memories and memories stacks
that need to be modeled for new ASIC , MICRO and FPGA based systems.

Thanks in advance

EC

 

[gabor]

On Apr 14, 8:40 am, "RealInfo" <therighti...@yahoo.com> wrote:

Hi all

I am new to HDL and I am looking for an  expertise direction.

Lately I came to conclusion that I want to focus on memories modeling from
all kinds , SRAM , ROM, FLASH etc.

My question is : Is it realistic to focus on memories modeling , is there a
market for such expertise.

I ask this because there are many free online models of memories but in the
other hand , there are many many memories and memories stacks
that need to be modeled for new  ASIC , MICRO and FPGA based systems.

Thanks in advance

EC

If you're new in the field, it's best to keep an open mind and
let your employment options direct you to your area of expertise.

Just my 2 cents,
Gabor

 

[hairyotter]

Lately I came to conclusion that I want to focus on memories modeling from
all kinds , SRAM , ROM, FLASH etc.

In ASICs, whenever you use a memory you already get the model from the
company that developed the memory IP.

Also, why would you want to limit your expertise to such a narrow
field ?

What you really need to do is to first of all learn the language
inside out and be a full-round designer.

The real needs of the industry is for
- people who can code actual circuits to be synthesized
- people who can do verification

And these are not necessarily mutually-exclusive.

However, as a hiring manager I have seen way too many people who think
that verilog/vhdl are programming languages. THEY ARE NOT.
They are languages meant to describe hardware and if you do not have a
clue about what hardware structures your code will turn into, you need
to either be lucky or have lots of silicon real-estate.

Writing some code is easy. Writing code that synthesizes well, meets
timings, does not create huge congestion in your P&R is a different
matter and requires training and an open mind.

On the other side, when you go into verification then it's ok if you
use the "software" paradigm, because you're not going to synthesize
it.
In this case you want to have understood data structures and
simulation performances, which is a different model.


Once you're a designer, you'll specialize, if needed, on the type of
circuits your company or customers need.

Marco.