element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • About Us
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Programmable Logic
  • Challenges & Projects
  • Project14
  • Programmable Logic
  • More
  • Cancel
Programmable Logic
Blog Using MKR Vidor 4000 as basic debug architecture
  • Blog
  • Forum
  • Documents
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Programmable Logic to participate - click to join for free!
  • Share
  • More
  • Cancel
Group Actions
  • Group RSS
  • More
  • Cancel
Engagement
  • Author Author: daniloo94
  • Date Created: 2 Jul 2019 2:17 AM Date Created
  • Views 1284 views
  • Likes 4 likes
  • Comments 2 comments
  • mod
  • programmablelogicch
  • debug
  • mkr_vidor
  • hardware
  • mkr vidor 4000
  • circuit
  • fpga
  • open source
  • arduino
  • verilog
Related
Recommended

Using MKR Vidor 4000 as basic debug architecture

daniloo94
daniloo94
2 Jul 2019

Hi folks, during my master's degree on computer science, i worked on the development of an architecture for checking digital circuits, based on FPGA focused on data centers, and high performance systems. But due to lack of support from the developers and the final cost of the FPGA using in this project, my project was a long time stopped. Based on this, I had the idea of proposing as project from element14 to remodel the way verification is performed using the Arduino MKR Vidor 4000 provided by the contest.

 

 

The initial idea of my project consist in the development of an architecture to be inserted with the design under debug during circuit synthesis, and using these system i can be able to collect the data of the systems with the purpose of detect possible failures in the hardware description. The architecture is composed by 4 main blocks, and many integration signals hehehe.

  • Trigger Logic: Detect when a possible failure happened inside the circuit. its use is directly related to the process of data collection of the circuit under analysis and in the information process of which specific part of the circuit under analysis happened the fault
  • Config Memory: Used to configure the other blocks, will be configurated receiving the data Over I/O which can be serial communication, jtag and etc.
  • Internal buffer: this memory, is responsible for storing a subset of faults within the circuit being analyzed. Its use is directly related to the large data rate that is commonly generated in a circuit debugging and low communication for sending this data directly
  • I/O:The communication bridge between the FPGA and the real world aims to send and receive data directly from the serial controller, or jtag to collect the data and configure the debug blocks

 

The first architecture proposal consisted of a system capable of collecting the information of several modules at the same time, exploring the high capacity that the FPGA circuit has in harboring large projects within its architecture. However, this process can not be done in FPGAs with little free area, which leads us to the second architectural proposalimage

 

image

 

 

The new idea is to use a MKR VIDOR 4000 FPGA cluster to divide the parts of the project under test so that it is possible to partition all the blocks that make up a module under analysis so that it is possible to reduce both the the final cost of the check, how many possible timing problems (Slack) and also allow regression tests on the hardware description

 

image

 

 

Initiating the process with Arduino MKR VIDOR 4000

After a few time installing libraries and testing the board i'm finally turn on the board image

 

image

  • Sign in to reply

Top Comments

  • gkasprow
    gkasprow over 6 years ago +1
    Correct me if I'm wrong, but you are trying to reinvent the SchipScope / SignalTap.
  • daniloo94
    daniloo94 over 6 years ago in reply to gkasprow

    In theory yes, but the idea is also to create a more flexible and reconfigurable debug architecture. For example, it is very common to use the SignalTap to debug a circuit in FPGA to happen the consumption of logical elements grow significantly and still add clock constraints to the debugging architecture. Overall, this project is the first part of an idea that consists of developing an entire reconfigurable infrastructure where the user can select subgroups of signals and collect that information more flexibly

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • More
    • Cancel
  • gkasprow
    gkasprow over 6 years ago

    Correct me if I'm wrong, but you are trying to reinvent the SchipScope / SignalTap.

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • More
    • Cancel
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube