Breaking News
View Comments: Newest First | Oldest First | Threaded View
Page 1 / 2   >   >>
MeasurementBlues
User Rank
Author
Re: Buses and software loops
MeasurementBlues   12/4/2013 10:16:57 AM
NO RATINGS
Also with regards to FPGAs, another test is to drive as many gates as possible all at once for testing power integrity on a board. That causes the FPGA to draw maximum current so you can see what it does to the power rails due to inductance in the power delivery network. Too deep a dive in power can cause havoc and you probably need better or more bypass capacitors on the board.

MeasurementBlues
User Rank
Author
Re: Buses and software loops
MeasurementBlues   12/4/2013 10:07:33 AM
NO RATINGS
When performing an emissions test, you usually want worst case and thus many systems have diagnostic software for the purpose of emissions testing. It would be like exercising more FPGA gates than are used in normal operation. Or you might drive a a whole lot of gates at once for a worst-case condition.

Max The Magnificent
User Rank
Author
Re: Buses and software loops
Max The Magnificent   12/4/2013 9:57:41 AM
NO RATINGS
@MeasurementBlues: Being more of a hardware type, I hadn't thought of software as a possible interference problem.

I agree -- this had never struck me -- very interesting

MS243
User Rank
Author
Re: Buses and software loops
MS243   12/4/2013 9:53:54 AM
NO RATINGS
Display's also radiate  -- CRT's were kind of bad with the magnetic deflection, and the new LCD, etc displays scan the array to update it -- this means that there are effectively long rows of horizontal and vertical ITO traces being switched on and off to make each pixel light or dark -- and ITO must be placed over the whole array to reduce these emmisions -- DO-160 is often hard to pass, for a display designed only to pass  FCC/CE

MS243
User Rank
Author
Re: Buses and software loops
MS243   12/4/2013 9:47:15 AM
NO RATINGS
SW Loops --And you change to a different memory type, with different wait states then everything changes also.

zeeglen
User Rank
Author
Re: Very Interesting
zeeglen   12/4/2013 9:42:20 AM
NO RATINGS
>Of course, there are cable grounding and shielding issues. The most significant is to make a 360° connection with a shield around a connector.

And make the shield connection to the chassis, not digital ground.  I once had to clean up a horrendous mess where the designer connected coaxial cable shields to his pcb digital ground plane and could not understand why the radiated emissions were so strong.


zeeglen
User Rank
Author
Re: Buses and software loops
zeeglen   12/4/2013 9:35:17 AM
NO RATINGS
>software  loop repetition frequency can also add spurs and harmonics

At a radiated emissions test site a manager type once told me to "Keep moving the cables around until it passes".  I can see the new version now - "Just keep tweaking the code until it passes".


MeasurementBlues
User Rank
Author
Re: Buses and software loops
MeasurementBlues   12/4/2013 9:07:55 AM
NO RATINGS
MS243, thanks for the tip on software loops. Being more of a hardware type, I hadn't thought of software as a possible interference problem.

MeasurementBlues
User Rank
Author
Re: Very Interesting
MeasurementBlues   12/4/2013 9:06:20 AM
NO RATINGS
Of course, there are cable grounding and shielding issues. The most significant is to make a 360° connection with a shield around a connector. No pigtails or you get emissions.

Understanding grounding, shielding, and guarding in high-impedance applications

Shields are your friend, except when... (Part 3), has links to Part 1 and Part 2

Grounding and shielding: No size fits all a piece I wrote in 2001, still relevalnt.

 

tom-ii
User Rank
Author
Re: Very Interesting
tom-ii   12/4/2013 8:54:04 AM
NO RATINGS
Excellent point.  It might also be noted that those openeings can create really strange effects and "nodes," too.

Page 1 / 2   >   >>
Most Recent Comments
michigan0
 
SteveHarris0
 
realjjj
 
SteveHarris0
 
SteveHarris0
 
VicVat
 
Les_Slater
 
SSDWEM
 
witeken
Most Recent Messages
9/25/2016
4:48:30 PM
michigan0 Sang Kim First, 28nm bulk is in volume manufacturing for several years by the major semiconductor companies but not 28nm FDSOI today yet. Why not? Simply because unlike 28nm bulk the LDD(Lightly Doped Drain) to minimize hot carrier generation can't be implemented in 28nm FDSOI. Furthermore, hot carrier reliability becomes worse with scaling, That is the major reason why 28nm FDSOI is not manufacturable today and will not be. Second, how can you suppress the leakage currents from such ultra short 7nm due to the short channel effects? How thin SOI thickness is required to prevent punch-through of un-dopped 7nm FDSOI? Possibly less than 4nm. Depositing such an ultra thin film less then 4nm filum uniformly and reliably over 12" wafers at the manufacturing line is extremely difficult or not even manufacturable. If not manufacturable, the 7nm FDSOI debate is over!Third, what happens when hot carriers are generated near the drain at normal operation of 7nm FDSOI? Electrons go to the positively biased drain with no harm but where the holes to go? The holes can't go to the substrate because of the thin BOX layer. Some holes may become trapped at the BOX layer causing Vt shift. However, the vast majority of holes drift through the the un-dopped SOI channel toward the N+Source,...

Datasheets.com Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)
Like Us on Facebook
EE Times on Twitter
EE Times Twitter Feed