Continue to Site

Welcome to EDAboard.com

Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.

packet formation and convolution coding..single ended to external lvds on actel fpga

Status
Not open for further replies.

incisive29

Newbie level 6
Joined
Jun 17, 2010
Messages
13
Helped
0
Reputation
0
Reaction score
0
Trophy points
1,281
Activity points
1,373
Hi..
I have designed a program which packetizes data and performs convolution coding in actel fpga A3P1000,
i have converted the single ended output i q and clk to differential output within fpga, the program runs fine.
On the second board I then used the single ended output and used an external lvttl to lvds convertor. the output is transmitted to the microD connector to decode it on matlab. I get the desired frames sometimes and sometimes I don't. can anyone tell me what can be the issue? The hardware is fine. the matlab code is perfect. the external Tranceivers are all ok. the board is perfect.
 

I get the desired frames sometimes and sometimes I don't. can anyone tell me what can be the issue? The hardware is fine. the matlab code is perfect. the external Tranceivers are all ok. the board is perfect.

Uh, obviously something is NOT perfect. First rule of debugging, suspect anything could be wrong, then prove one-by-one something is absolutely not wrong (this is the hard part).

I've noticed that the people that are the worst at debugging are the ones with lots of ego, that always think the problem is NOT in their stuff.

The times it's taken me the longest to find a problem have always been when I take at face value, another engineer instance that they have checked out their stuff and it's doing everything correctly...and I don't look at their stuff. It usually ends up the problem is in the interface between their stuff and mine. Things like a signals that suddenly change timing/protocol intermittently so my design can't capture the data (as it now violates the interface timing/protocol, which I got from them in the first place :bang:).
 

Status
Not open for further replies.

Part and Inventory Search

Welcome to EDABoard.com

Sponsor

Back
Top