The document introduces PHDL, a hardware description language for printed circuit boards. It describes creating device definitions that specify attributes and pin mappings. The example design shows how to instantiate devices and make connections to implement an LED seven-segment display controlled by switches. Device definitions allow creation of schematic symbols and mapping pins to pads on the PCB layout.
Wedding convenience and control with RemoteCondorIgor Sfiligoi
This presentation explains why Condor is not suitable for use on user-owned machines, and why RemoteCondor is the best available solution to the problem.
Microprocessors are used extensively in the design of any computing facility. It contains units to carry out arithmetic and logic calculations, fast storage in terms of registers and associated control logic to get instructions from memory and execute them. A number of devices can be interfaced with them to develop a complete system application. On the other hand, microcontrollers are single chip computers, integrating processor, memory and other peripheral modules into a single System-on-Chip (SoC). Apart from input-output ports, the peripherals often include timers, data converters, communication modules, and so on. The single chip solution makes the footprint of the computational element small in the overall system package, eliminating the necessity of additional chips on board. However, there exists a large range of such products. While the simpler microcontrollers are cheap, their capabilities (in terms of program size and analog and digital peripherals) are also limited. Such processors may be suitable for small applications. Microcontrollers like 8051, PIC belong to this category. On the other hand, advanced microcontrollers are often much more powerful, comparable to the very advanced microprocessors. The AVR and ARM processors are of this category.
Wedding convenience and control with RemoteCondorIgor Sfiligoi
This presentation explains why Condor is not suitable for use on user-owned machines, and why RemoteCondor is the best available solution to the problem.
Microprocessors are used extensively in the design of any computing facility. It contains units to carry out arithmetic and logic calculations, fast storage in terms of registers and associated control logic to get instructions from memory and execute them. A number of devices can be interfaced with them to develop a complete system application. On the other hand, microcontrollers are single chip computers, integrating processor, memory and other peripheral modules into a single System-on-Chip (SoC). Apart from input-output ports, the peripherals often include timers, data converters, communication modules, and so on. The single chip solution makes the footprint of the computational element small in the overall system package, eliminating the necessity of additional chips on board. However, there exists a large range of such products. While the simpler microcontrollers are cheap, their capabilities (in terms of program size and analog and digital peripherals) are also limited. Such processors may be suitable for small applications. Microcontrollers like 8051, PIC belong to this category. On the other hand, advanced microcontrollers are often much more powerful, comparable to the very advanced microprocessors. The AVR and ARM processors are of this category.
This workshop is all about having fun with an Arduino Nano & individually addressable RGB LED's using the FastLED library. Each attendee receives an Arduino Nano, a strip of 20 APA102 LED's, a battery back and batteries. We'll be programming the Arduino with some awesome animations and attach it to a hat.
It was created for scouting youth in the Fraser Valley of British Columbia, Canada.
Ariel Waizel discusses the Data Plane Development Kit (DPDK), an API for developing fast packet processing code in user space.
* Who needs this library? Why bypass the kernel?
* How does it work?
* How good is it? What are the benchmarks?
* Pros and cons
Ariel worked on kernel development at the IDF, Ben Gurion University, and several companies. He is interested in networking, security, machine learning, and basically everything except UI development. Currently a Solution Architect at ConteXtream (an HPE company), which specializes in SDN solutions for the telecom industry.
Synthesis in VLSI is the process of converting your code (program) into a circuit. In terms of logic gates, synthesis is the process of translating an abstract design into a properly implemented chip. Hardware Description Languages (HDLs) are specific programming languages that are used to explain the hardware of a circuit, and the computer subsequently builds the circuit depending on the programme you provided. A “Gate Level Netlist” is what you get once you finish synthesising. This is how your circuit will appear. It demonstrates how everything is interconnected. You can alter it if you like; the computer just synthesizes this netlist based on its best judgement. The synthesizer generates better netlists as the abilities improve and they become more proficient at creating HDL programmes.
This workshop is all about having fun with an Arduino Nano & individually addressable RGB LED's using the FastLED library. Each attendee receives an Arduino Nano, a strip of 20 APA102 LED's, a battery back and batteries. We'll be programming the Arduino with some awesome animations and attach it to a hat.
It was created for scouting youth in the Fraser Valley of British Columbia, Canada.
Ariel Waizel discusses the Data Plane Development Kit (DPDK), an API for developing fast packet processing code in user space.
* Who needs this library? Why bypass the kernel?
* How does it work?
* How good is it? What are the benchmarks?
* Pros and cons
Ariel worked on kernel development at the IDF, Ben Gurion University, and several companies. He is interested in networking, security, machine learning, and basically everything except UI development. Currently a Solution Architect at ConteXtream (an HPE company), which specializes in SDN solutions for the telecom industry.
Synthesis in VLSI is the process of converting your code (program) into a circuit. In terms of logic gates, synthesis is the process of translating an abstract design into a properly implemented chip. Hardware Description Languages (HDLs) are specific programming languages that are used to explain the hardware of a circuit, and the computer subsequently builds the circuit depending on the programme you provided. A “Gate Level Netlist” is what you get once you finish synthesising. This is how your circuit will appear. It demonstrates how everything is interconnected. You can alter it if you like; the computer just synthesizes this netlist based on its best judgement. The synthesizer generates better netlists as the abilities improve and they become more proficient at creating HDL programmes.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Software Delivery At the Speed of AI: Inflectra Invests In AI-Powered QualityInflectra
In this insightful webinar, Inflectra explores how artificial intelligence (AI) is transforming software development and testing. Discover how AI-powered tools are revolutionizing every stage of the software development lifecycle (SDLC), from design and prototyping to testing, deployment, and monitoring.
Learn about:
• The Future of Testing: How AI is shifting testing towards verification, analysis, and higher-level skills, while reducing repetitive tasks.
• Test Automation: How AI-powered test case generation, optimization, and self-healing tests are making testing more efficient and effective.
• Visual Testing: Explore the emerging capabilities of AI in visual testing and how it's set to revolutionize UI verification.
• Inflectra's AI Solutions: See demonstrations of Inflectra's cutting-edge AI tools like the ChatGPT plugin and Azure Open AI platform, designed to streamline your testing process.
Whether you're a developer, tester, or QA professional, this webinar will give you valuable insights into how AI is shaping the future of software delivery.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
1. PHDL
PRINTED CIRCUIT BOARD
HARDWARE DESCRIPTION LANGUAGE
Brent Nelson, Brad Riching, Richard Black
Dept. of Electrical and Computer Engineering
Brigham Young University
October 25, 2011
2. Acknowledgements
• Pete Dudley – Sandia
– Ideas, motivation, and passion for this project
• Wes Landaker - Sandia
– Ideas, language design, compiler consulting
• Sandia Management
– Funding
2
3. Overview
• Who are we?
• What is PHDL? (a very short intro)
• Examples of PHDL
– Example board designs
• Language and grammar
• Tool flow
• What is PHDL? (more in-depth)
– Why textual input?
3
4. Who Are We?
• Dr. Brent Nelson
– Brigham Young University, Dept. of Electrical
and Computer Engineering
• Brad Riching
– MS Student in Computer Engineering
– BS in Electrical Engineering, Brigham Young
University, 2010
• Richard Black
– Undergraduate in Computer
Engineering, Brigham Young University
4
5. What is PHDL?
Schematic Capture PCB Layout
produces netlist interprets netlist
netlist
Bill of
Material,
other
ancillary
data
5
6. What is PHDL?
Schematic Capture PCB Layout
produces netlist interprets netlist
netlist
PHDL Bill of
PHDL compiler Material,
Source other
Code ancillary
data
6
7. What is PHDL? (a very short intro)
• An HDL for PC Boards
– Hardware Description Language
– For schematic entry (not layout)
• Similar to HDLs for IC and FPGA design
– Verilog, VHDL, etc.
• Goal == significantly increase:
– Productivity
– Collaboration
– Reuse
7
8. Why PHDL? (the short version)
1. Automation & productivity
– Iteration, hierarchy, ERC/DRC
2. Collaboration
– SCCS (source code control system)
• Shared repository for designs and part libraries
• Design versions, change tracking/documentation
• Diff, revert
3. Textual IDEs and tools
– Templates, auto-completion, search and
replace, library reuse
8
9. High Pin Count Devices - FPGAs
How much of this schematic is meaningful?
• Most circuit context
is absent.
• Many pins map to
devices on other
pages.
• Larger devices must
be split across
multiple pages
• Schematics don’t
scale well.
• HDL’s do!
9
44. PHDL Example Design
design ssControl is net gnd, vcc;
device Resistor is net[1:8] segs, r2sw;
attr refPrefix = “R”; begin
attr pkg_type = “M0805”; inst source of Battery is
pin a = {1}; pos = vcc;
pin b = {2}; neg = gnd;
end device; end inst;
device Switch is inst segment of SevenSeg is
attr refPrefix = “SW”; segments = segs;
attr pkg_type = “MS243”; anode = <vcc>;
pin a = {1}; pin b = {2}; end inst;
end device; inst(1:8) swArray of Switch is
device Battery is combine.a = r2sw;
attr refPrefix = “G”; combine.b = segs;
attr pkg_type = “1V60R”; end inst;
attr value = “9V”; inst(1:8) rArray of Resistor is
pin pos = {2}; pin neg = {1}; newattr value = “120”;
end device; combine.a = r2sw;
device SevenSeg is each.b = gnd;
attr refPrefix = “LD”; end inst;
attr pkg_type = “MS243”; end design;
pin[1:8] segments =
{2,15,13,11, 5,3,14,10};
pin[1:3] anode = {4,12,17};
end device;
44
45. Creating a Design
inst(1:8) rArray of Resistor is
newattr value = “120”;
combine.a = r2sw;
each.b = gnd;
end inst;
45
46. Creating a Design
inst(1:8) rArray of Resistor is
newattr value = “120”;
combine.a = r2sw;
each.b = gnd;
end inst;
46
47. Creating a Design
inst(1:8) rArray of Resistor is
newattr value = “120”;
combine.a = r2sw;
each.b = gnd;
end inst;
47
48. Creating a Design
inst(1:8) rArray of Resistor is
newattr value = “120”;
combine.a = r2sw;
each.b = gnd;
end inst;
48
49. PHDL Example Design
design ssControl is net gnd, vcc;
device Resistor is net[1:8] segs, r2sw;
attr refPrefix = “R”; begin
attr pkg_type = “M0805”; inst source of Battery is
pin a = {1}; pos = vcc;
pin b = {2}; neg = gnd;
end device; end inst;
device Switch is inst segment of SevenSeg is
attr refPrefix = “SW”; segments = segs;
attr pkg_type = “MS243”; anode = <vcc>;
pin a = {1}; pin b = {2}; end inst;
end device; inst(1:8) swArray of Switch is
device Battery is combine.a = r2sw;
attr refPrefix = “G”; combine.b = segs;
attr pkg_type = “1V60R”; end inst;
attr value = “9V”; inst(1:8) rArray of Resistor is
pin pos = {2}; pin neg = {1}; newattr value = “120”;
end device; combine.a = r2sw;
device SevenSeg is each.b = gnd;
attr refPrefix = “LD”; end inst;
attr pkg_type = “MS243”; end design;
pin[1:8] segments =
{2,15,13,11, 5,3,14,10};
pin[1:3] anode = {4,12,17};
end device;
49
50. PHDL Example Design
design ssControl is
include “parts.phdl”;
net gnd, vcc;
net[1:8] segs, r2sw;
begin
inst source of Battery is
pos = vcc;
neg = gnd;
end inst;
inst segment of SevenSeg is
segments = segs;
anode = <vcc>;
end inst;
inst(1:8) swArray of Switch is
combine.a = r2sw;
combine.b = segs;
end inst;
inst(1:8) rArray of Resistor is
newattr value = “120”;
combine.a = r2sw;
each.b = gnd;
end inst;
end design;
50
51. How PHDL Works
~/user/brad/phdl/projects
$java phdl.Compile <file_name>.phdl [switches]
Abstract Syntax
Tree (AST)
PHDL Tree
Lexer Parser
source Parser
ANTLR framework
Command
line switches
• Netlist
• Bill of Materials
Analyzer / Output • Component List
Generator files • Layout Directions
• XML
51 • Tool-specific Scripts
52. Targeted Design Flows
EAGLE PCB
FPGA-based Motor
Controller - BYU
Mentor Graphics PADS
AD9739 High Speed DAC
FMC board – Pete Dudley
52
53. BYU Proof of Concept Board
FPGA-based motor controller (2-axes)
– Spartan3 400K 144-pin QFP implements:
• 32-bit position, vel. and accel. registers per axis
• Programmable PID filters, sampling intervals
• Trapezoidal velocity profile generators
• Packet router over RS232 to host PC application
– Supporting hardware
• 500+ CPR encoder feedback resolution
• PWM brushless and brushed motor drives
• The usual JTAG, Flash ROM, GPIO, etc.
53
54. Motor Controller Board
Single Axis Block Diagram
RS232 Host
Application
MOTOR DRIVERS
FPGA VHDL Hardware Outside
FPGA
54
59. Motor Controller Board
JTAG
Power Supply
12VDC IN: Motor Power
To 58VDC MAX
5V, 3.3V, 2.5
V, 1.2V
Brushless
FPGA / SRAM Drive (x2)
RS232
Brushed
Drive (x2)
Encoder
Feedback
60. Motor Controller Board
Host Application Interface (C#) Serial Config
Raw Data
Monitoring
Positioning
Commands
Reporting
Commands
Internal State
Registers
60
61. Automatic Device Generation
FPGA VHDL Location
Constraints PHDL Device Declaration
Design
library ieee;
device fpga is
#fpga.ucf attr refPrefix = "U";
use ieee.numeric_std.all;
use ieee.std_logic_1164.all; attr pkg_type = "tq144";
LOC “clk” = P52; attr mfgr = "XILINX";
entity fpga is
LOC “rst” = P40:
port( attr partNumber = "xc3s400-4tq144";
LOC “rxd” = P47;
clk : in std_logic;
LOC “rxd_a” = P41;
rst : in std_logic; // User I/O pins.
.
. pin clk = {P52};
-- RS232 serial ports pin rst = {P40};
.
rxd : in std_logic;
pin rxd = {P47};
txd : out std_logic;
rxd_a : in std_logic;
pin rxd_a = {P41};
txd_a : out std_logic; pin txd = {P46};
pin txd_a = {P44};
-- 12-bit DAC pin sclk = {P86};
sclk : out std_logic; pin sdata = {P87};
sync : out std_logic; pin sync = {P85};
sdata : out std_logic pin[7:0] data = {P23,P21,P20,P18...};
.
data : out .
std_logic_vector(7 downto 0)
.
. Synthesis, PAR, end;
.
. csv2phdl
);
end entity fpga;
61
62. Automatic Device Generation
Automated FPGA Device Declaration from HDL
HDL
csv2phdl PHDL
fpga.vhdl fpga.csv fpga.phdl Device
fpga.ucf Declaration
Synthesis, PAR
PHDL
Source Code
design myDes is
include “fpga.phdl”;
Revisions begin
…
end design;
62
66. The Group Construct
group "SWITCHES" is
inst fpga_switches of dipswitch is
a = <vcco>;
b = sw_res;
end;
inst(7:0) sw_pulldown of R0603 is
value = "4.7k";
partNumber = "P4.7KGCT-ND";
combine.a = sw_res;
each.b = gnd;
end;
inst(7:0) sw_lim of R0603 is
value = "4.7k";
partNumber = "P4.7KGCT-ND";
combine.a = sw_res;
combine.b = sw;
Group Initial
end; name Arrayed
end;
Layout
66
67. Why PHDL? (the longer version)
• Open format
– Any text tools can read and manipulate
– Design files do not get corrupted
– Easily shared, exchanged, emailed
– Design files forward/backward compatible
across tool revisions
67
68. Why PHDL?
• IDEs
– Templates and auto completion
– Color syntax highlighting
– Search, search-and-replace
– Scripting
• Example: Eclipse
68
69. Why PHDL?
• SCCS (source code control system)
– Shared repository for designs and part
libraries
– Design versions, change
tracking/documentation
– Diff, revert
• Collaboration
• Reusability
• Cross probing
69
70. Why PHDL?
• Hierarchy
• Focus on functionality rather than looks of
schematic
• Easy to mis-wire in graphics
– Rats nests
– Missed endpoints
– High pin count packages span multiple pages
– Dangling wires across schematic pages
• Non-electrical parts trivial to add
70
71. Why PHDL?
• Automation
– Higher level constructs
– Arrays, hierarchy
– Refdes handling
– DRC available to user due to open format
– Lint-like tools easily written
• Automatic generation of design files
– Example: device generation from UCF file for
FPGAs
71