. |
![]() |
|
|
Crunch time on projects always seems to come during lab debug. That's when the FPGA, software and PCB all come together for the first time. It's also the last, and frequently, most difficult phase in the project. Any slack time in the schedule has long since been eaten up by unanticipated delays of one sort or another. The entire team has to work together on the same thing and in the same place, possibly for the first time. Many developers put off thinking seriously about the latter stages
of the project and what tools they might need once they get there. There's
so much to do initially in specifying the design, partitioning it and
keeping all the parallel efforts on track and in sync to consider what
you ll do when you get to the lab. Electronics Design
The Specification is the customer's instructions to the designer describing the features the new product should have. (See: More info - Specifications) A specification starts out as ideas and a wish list, then gradually gets nailed down to something more formal and explicit. It is a good idea to have a list of "reasons why" and "how it's done" to explain the specification, but keep these separate from the main document. We have, online, a guide to writing a specification for a new electronic product, help with specification construction, examples of specifications, and a glossary of technical information. The basic, introduction explanation of the products function within a specification should be quite short, keep it to one page:
Contact Detail: Specs Specs Where you see the magnifying glass symbol you can CLICK to get MORE DETAIL
The Circuit Diagram, also called the Schematic or Logic Diagram, maps out the electronics and connections in the most readily readable form. (See: More info - Circuit Design) The designer needs to do background work while producing the Circuit diagram, researching specifications of components, interaction between components (especially timing and loading) physical packages, and arrangement of connector pinouts. The circuit will often start on paper and finish in Computer Aided Design (CAD) format.
Detail: Circuit Design Circuit The Printed Circuit Board Layout The Printed Circuit Board (PCB) is the laminate to which all the electronic components are soldered, with one or more layers of etched metal tracks making the connections. (See: More info - PCB Layout) The components and connections in the PCB Layout are derived from the circuit diagram, and physically placed and routed by the designer to get the best result. The PCB Layout defines the final physical form of the circuit, and enclosure and labelling details can be finalised as the layout is completed.
At AirBorn Electronics we usually make 2 or 3 identical prototypes at the same time. (See: More info - Prototypes) The Prototype circuitry is debugged in stages. The debugging proceeds according to the debug test procedure, which is written for the product as it is designed. Prototype microprocessor circuits are generally debugged with specially written diagnostic code, again progressing in stages.
Software for the electronics is often 50% or more of the design work in a project. The programming that controls the microprocessor usually gives the electronic product its features and "glitz" whereas the hardware is the purely functional side of the equation. The programming or coding for electronic products is usually written in 'C' or assembler, whereas the programming that runs on a PC will normally be written in C++, java or another language (and almost certainly not assembler). The programming for microcontrollers is totally different from that for a PC in any case - it is usually "more detailed" and less "generic" than the type of programming made for a personal computer, because it is more tightly coupled to the electronic hardware on which it runs, and because it usually has to respond more quickly - that is it has to run in "real time". There is usually a great deal of care and testing involved with programming for electronic products - while for some reason clients seem willing to accept bugs in windows software as somewhat normal, they are pretty unacceptable in, say, an engine control unit for a modern car.
Pilot Run To test the product further, a Pilot run normally follows the prototyping stage (See: More info - PCB Assembly). In the Pilot run, a small quantity of units (for instance 25) are field trialed in a beta test. The Pilot run is also an opportunity to assess the manufacturability of the design, and the useability of the documentation (See: More info - PCB Documentation).
Production Following the pilot run there will likely be changes to the firmware, and possibly the circuit design, as the unit develops into a stable, final product. This process is controlled by ECOs and version numbers. We handle the actual production of electronics for some customers, but others prefer to produce the circuitry in house, or use other assembly subcontractors. Our technical documentation is sufficiently detailed for our customers to have the electronics produced by a third party subcontractor. The cost of the final production, and to some degree the style of design, is heavily influenced by the number of units manufactured (see Economies of scale). Detail: PCB Assembly Innovation and Inspiration ... an opinion Creative aptitude is really important in making new technology products come to life, and also in identifying the market and the need the product will fill. The ability to bring that inspiration through into a final product requires the level-headed decision making. Some electronic designs are not really new products as such, but developments of existing products. These designs, also, require creative vision to see which new features are really the most desirable, and how the design can be economically produced.
Hardware Verification For lab debug you will need to gather information about what's going on inside your FPGA and relate it back to the source RTL to implement corrections. If, for example you do not see the expected outputs from a state machine, you need to know what state you're in and what inputs are failing to move you through the states. When you detect a bug, you have to iterate the design swiftly so that the team does not lose focus waiting. Probing Logic You gather that information by probing the logic and storing the results. To probe you need a way to quickly isolate logic and attach sensors and triggers. One probing solution would be to use a logic analyzer to monitor internal signals. You do that by bringing the signals to pins on the device that are connected to PCB headers. The headers logic analyzer pods plug into the headers. Typically you then select one of the signals as a clock and one as a trigger to begin storage. One set of vectors is stored each clock. This method does provide a window into the device in operation without any cost in logic resources. In addition the analyzer may be familiar to the design team and its use avoids the delay in learning a new tool. At the same time it has a number of shortcomings. One big issue is that you have to connect signals in your design to the device manually. Nodes at lower levels of the hierarchy have to be routed up to the top level by editing the designs pins and iterating through debug manually each time. Any nodes you seek to view that are not at the device level of the design must be routed to the top-level. The probing capacity of the analyzers is limited by the number of free pins available on the device and the number of pins placed on the board. The names of the signals have to be entered into the logic analyzer viewer in order to track which node in the design is displayed on which line. The entire process has to be performed every time the probes are moved. Routing nodes in the design to the pins may interfere with device operation or timing. A few programmable logic vendors offer tools for hardware debugging using the programming channel to access device operation information. These tools use the programming port on the device to connect to the internal nodes so that external pins are not required. Connections are made using a two tiered component. One component connects to nodes in the design and transfers the results to the second component that forwards them to the JTAG port. The tools support more sampling channels than would be practical using an analyzer and can sample at varying ranges around a trigger event. The vendor tools offer some advantages over logic analyzers in that they do not require external package pins. The tools also support multiple clock domain sampling and more levels of triggering than a logic analyzer. Unlike logic analyzers the vendor tools use logic resources, however few, that are then unavailable for use in the application. The vendor tools share some shortcomings with analyzers such as manual text editing to insert probes, limited results reporting and lengthy iteration cycles. Another solution is the Identify RTL debugger from Synplicity. This
product is made up of two tools ¨?(C an instrumentor and a debugger.
The Instrumentor uses a component system similar to those offered by
the device vendors. But instead of editing your source files to add
nets to connect pins or add probing components to connect nodes, you
use the Instrumentor to display the design hierarchy in one window and
select the module you wish to view as shown in Figure 1. When you complete
the instrumentation, the logic is added automatically. Like the vendor
tools, adding probes requires the use of some logic resources, but it
is minimal. The hierarchical design display lets you find lines of code fast because it exactly reflects the structure you used to create them. When you navigate to a module or architecture, you'll see the branching statements displayed along with their line number. ll the code branch statements such as IF and ELSE are marked as potential breakpoints and you activate them merely by clicking on the circle. Examples of probes and breakpoints are shown in Figure 2.
The tool supports multiple instrumentations of a single design and
you can switch between them simply by clicking a tab and compiling.
That feature allows you to leverage the same resources over several
sets of probes. Different engineers can use the tool to instrument the
same version of the design without interfering with each other. East China Headquarter ¨CDiamond Shanghai R & D Center
Debugging the Design When debugging with a logic analyzer you set one signal value as a trigger. When the analyzer sees the value, it captures data in a buffer and displays it on its screen. Logic analyzers do not support complex triggering on multiple events easily although such mechanisms could be designed by the user. The vendor tools and Synplicity's Identify tool perform all the triggering and storage of results internally. After you have programmed the device and it is operating in the system, the components sample and store behavior of nodes using logic and memory resources on the device. The vendor tools include a viewer that runs on a PC and accesses the information over the programming port and displays it in the signal waveforms. The second tool in the Identify suite is the Debugger that offers complex and user-defined triggering for data capture to trap exactly those events that resolve design malfunctions. It also supports multiple sets of probes and the means to seamlessly toggle between sets on a single version of the design. Controlling Debug Reporting Results Logic analyzers contain displays and one benefit of using the analyzer to show FPGA signals is that it may display PCB signals in addition to those from the FPGA. The analyzer screen is smaller than a typical PC monitor and as a result is a cumbersome object in the lab. The vendor tools have their own waveform viewers that run on a PC. Waveform signals can be labeled and the text displayed between iterations. Waveform viewing shows signal timing relationships, but does not directly relate values back to the code. You still have to relate the behavior of signals observed back to the source code to understand what caused the transitions. This is a time-consuming and error prone task without an RTL debugger like the Identify product. Like the vendor tools, the Identify Debugger supports waveform viewing, but it can also annotate the logic values directly back into the source code. The values may be binary or enumerated data types. You can step backward and forward in time to view the results over a series of clocks and watch the code being updated each cycle. ou use the icons, shown in Figure 3, and menus to set the various trigger options, start and stop debugging and view the instrumentation. You use the cycle tabs to move back and forth through the results on individual clocks.
Iterating the Design Logic analyzers are completely outside of the tool flow of design iterations. The iterations are performed by editing the source code to move probes, synthesizing and routing the entire design. Vendor tools also require you to re-synthesize unless you do post synthesis insertion of the probe cores. In that case, however, you must have synthesized with an option to retain all net names and also re-specify the prove connections with every iteration because they are not retained through synthesis. The Identify tool allows you to perform very fast iterations by directly calling the vendor place and route in incremental mode so that only those connections required to move the probes are routed and the remainder of the design is frozen. That allows debug compilations to complete in a fraction of the time required for the entire design. That means the team can see the results of changes right away. Summary The Identify product is the only tool that offers you a complete solution to hardware debug and helps you to quickly find out what you need to complete your design and move it out of the lab. ARM/XScale Emulator Supported MCUs Compilers/Debuggers Package List Development Platform ARM7-DevPlatform AT91RM9200DevKit AT91RM9200DevKit S3C2510-DevPlatform IXP425-DevPlatform
ARM7-Development-Kits ARM9-Development-Kits Embedded Linux Kits
Advanced FPGA&SOPC
Single Computer Embedded System ODMProfessional Service AT91RM9200DevKit High-Powered AT91RM9200 Linux Development Kits AT91RM9200DevKit development platform provides the rich software and
hardware functions, providing one 10/100M Ethernet Interface, two USB2.0
HOST interfaces, one USB2.0 DEVICE interface, Five standard RS232 interfaces,
two CAN-Bus interfaces, SD card interface, CF card interface, TFT/STN
LCD interface, touch panel interface, one 320x240 TFT LCD Panel and
touch panel, CRT interface, 4x4 small keyboard, 8x8 keyboard interface,
8 7Segment lights, I/O LED and so on.AT91RM9200DevKit is made up of
one CPU Module board (FD9200-CARD-ENGINE ) and one application base
board, and one TFT LCD Panel and touch panel. The CPU module board---AT91RM9200-CARD-ENGINE
is the perfect OEM Single Computer, all most of functions have been
integrated on the CPU module board. The customer can directly use CPU
module board into the project. It is very easy to develop your products
if you use CPU module board. For more information of CPU module board,
you can refer to AT91RM9200-CARD-ENGINE .
Specifications Network 10/100 Ethernet Interface CAN-BUS Interface Two CAN-BUS Interfaces, Support CAN specification
V2.0 A/B Touch Panel Interface Touch Panel Interface RTC RTC function Software Components SDK Software Development Kits(SDK) for ARM Linux DEMO Many Example source code and sample application: GUI We provide embedded GUI software development package free Technology open document We have provided all the technology documents
Embedded GUI Tools MicroWindows GUI Developmnent tools: GUI Examples Provide several GUI demos examples: Document Technology development manual
Software ARM Linux embedded OS Development tools - GNU compiler, linker, the full development tools
Documents - Embedded Linux technology development manual Accessories - One 5V adaptor Application: Advantages of AT91RM9200DEVKIT:
Categories Industrial Market Trends
Latest New Product News Adhesives and Sealants Agricultural and Farming Products Architectural and Civil Engineering Products Automatic ID Chemical Processing and Waste Management Cleaning Products and Equipment Communication Systems and Equipment Computer Hardware and Peripherals Construction Equipment and Supplies Controls and Controllers Display and Presentation Equipment Electrical Equipment and Systems Electronic Components and Devices Explosives, Armaments and Weaponry Fasteners and Hardware Fluid and Gas Flow Equipment Food Processing and Preparation Health, Medical and Dental Supplies and Equipment HVAC Labels, Tags, Signage and Equipment Laboratory and Research Supplies and Equipment Lubricants Machinery and Machining Tools Material Handling and Storage Materials and Material Processing Mechanical Components and Assemblies Mechanical Power Transmission Mining, Oil Drilling & Refining Mounting and Attaching Products Non-Industrial Products Optics and Photonics Packaging Equipment Paints and Coatings Plant Furnishings and Accessories Portable Tools Printing and Duplicating Equipment Retail and Sales Equipment Robotics Safety and Security Equipment Sensors, Monitors and Transducers Services Software Test and Measuring Instruments Textile Industry Products Thermal and Heating Equipment Timers and Clocks Transportation Industry Products Vision Systems Waste Handling Equipment Welding Equipment and Supplies Association News
Browse Companies Press Releases Products in the News Company News Mergers & Acquisitions People in the News Literature & Websites Resources
PR Resources Licensing Advertising How to Write an effective Press Release Trade Associations Small Business Support MEP Simplicity of Design- Mercury Monitoring made easy
Archive News Story
July 20, 2006 - Designed to provide new or additional test points on printed circuit boards (PCBs), PCB Probe Kit offers functionality for probing and viewing signals on logic analyzer, oscilloscope, meter, or other instrument. Hands-free system includes arm probe with heavy base, spring loaded tip, rotatable head, and fine vertical adjustment knob. Kit also includes lead clips, SMD clips, SMD clip support with guide wire, and integrated magnifying glass with tweezers.
-------------------------------------------------------------------------------- Join the forum discussion at:
The following components are included in the in the PCB Probe Kit: Arm probe with a heavy base, spring loaded tip, rotatable head and fine vertical adjustment knob to enable precise positioning to adjacent test points; Small lead clips enabling quick connection to SMD leads from 0.5mm down to 0.2mm lead pitch; Large lead clips enabling connection to leads from 1.25mm down to 0.3mm lead pitch; SMD clips available in four sizes: 0201, 0402, 0603, and 0805; SMD Clip Support with Guide Wire; and an integrated Magnifying Glass with Tweezers designed to assist the user when working on small components in tight areas. Please review our website or contact us directly for more information. Company Name: OptoTherm Contact Name: Al Stricker
More news from this company: More related stories: 1.How to inHow to istinguish original and fake of PC Analyzer? 3.How do we distinguish "intiative code" and " trouble
code"? Top
12.Statement of FRAME LED and BIOS LED. Top
|
|
|
|
|
|
|
|
||||||
| Electronic product design1 PCB design2 Electronic design house3 Product blue print design4 microcontrollor system design5 controller board design6 remote control design7 remote control switch8 1394 card manufacture9 DV TV card10 equipment PCB circuit design11 power inverter manufacture12 3D design13 product prototype PCB debug14 product prototype PCB design15 PCB circuit rebuild16 PCB prototype design17 new product design and exploitation18 circuit schematic design19 hardware design20 software design21 telecommunication PCB design22 PCBA China23 PCB tailor24 product PCB improve25 infrared wireless remote control26 Power inverter27 PCB trade commercial business28 china sourcing outsourcing29 pcb fabrication and supplier30 pcb prototype layout and PCBA31 china PCB manufacturing32 flexible pcb circuit board FPC repair33 pcb layout & rework service34 Sell PCB and PCBA35 pcb reverse engineering36 multilayer PCB37 chinese PCB manufacturer38 flexible printed circuit board39 PCB board assembly services40 pcb board design services41 pcb board layout services42 smt assembly43 electronics design44 circuit board accessories45 prototype pcb fabrication&assembly46 board circuit manufacturing47 electronic contract manufacturing48 cheap PCB49 Pb-Free PCB design&Assembly50 electrical engineering51 china trade52 china supplier53 made in china54 Rapid Prototyping55 assemblies56 PCB Populating57 rc toys58 circuit supplies59 circuit diagrams60 Turnkey OEM/ODM61 ac dc power supplies62 wind power63 battery charger64 power adapter65 rc airplanes66 rc cars67 rc boats68 universal remote control69 transmitter receiver70 remote control caddy71 tv remote control72 pcb factories73 electronic factories74 PCB route75 express PCB76 inventions idea77 electronic circuits78 electronics development79 design engineering80 design firm81 electronics product prototyping82 PCB83 84 85 86 |
| |
|||
|