{"id":2599,"date":"2026-06-28T14:09:52","date_gmt":"2026-06-28T14:09:52","guid":{"rendered":"https:\/\/www.pickplace.de\/?post_type=projekt&#038;p=2599"},"modified":"2026-06-28T14:11:06","modified_gmt":"2026-06-28T14:11:06","slug":"xilinx-kria","status":"publish","type":"projekt","link":"https:\/\/www.pickplace.de\/en\/projekte\/xilinx-kria\/","title":{"rendered":"Xilinx KRIA"},"content":{"rendered":"<div class=\"wp-block-rank-math-toc-block\" id=\"rank-math-toc\"><h2>Content<\/h2><nav><ul><li class=\"\"><a href=\"#unsere-leistungen\">Our Services<\/a><\/li><li class=\"\"><a href=\"#technische-bewertung-und-machbarkeitsklarung\">Technical Assessment and Feasibility Clarification<\/a><\/li><li class=\"\"><a href=\"#architekturarbeit-fur-kria-basierte-systeme\">Architectural Work for KRIA-based Systems<\/a><\/li><li class=\"\"><a href=\"#carrier-board-und-schnittstellenbetrachtung\">Carrier Board and Interface Analysis<\/a><\/li><li class=\"\"><a href=\"#entwicklung-mit-fpga-logik-und-embedded-software\">Development with FPGA Logic and Embedded Software<\/a><\/li><li class=\"\"><a href=\"#fehleranalyse-debugging-und-redesign\">Error analysis, debugging, and redesign<\/a><\/li><li class=\"\"><a href=\"#dokumentation-und-ubergabe-in-die-umsetzung\">Documentation and handover to implementation<\/a><\/li><\/ul><\/nav><\/div>\n\n\n\n<h2 id=\"unsere-leistungen\" class=\"wp-block-heading\">Our Services<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">PICKPLACE supports <a href=\"https:\/\/www.amd.com\/de\/products\/system-on-modules\/kria.html\" target=\"_blank\" rel=\"noopener\">Xilinx-KRIA<\/a>-Projects ranging from technical classification to the implementation of individual hardware and software components. Since KRIA modules combine multiple disciplines, the work usually doesn't begin with a single development task, but rather with clarifying the system configuration: Which functions run on the processor, which tasks belong in programmable logic, what data rates need to be processed, and which interfaces determine the hardware design.<\/p>\n\n\n\n<div class=\"wp-block-stackable-image stk-block-image stk-block stk-d307a0c\" data-block-id=\"d307a0c\"><style>.stk-d307a0c .stk-img-wrapper{width:70% !important;}.stk-d307a0c .stk-img-wrapper img{border-radius:var(--stk--preset--border-radius--xx-large, 32px) !important;}<\/style><figure><span class=\"stk-img-wrapper stk-image--shape-stretch\"><img loading=\"lazy\" decoding=\"async\" class=\"stk-img wp-image-2602\" src=\"https:\/\/www.pickplace.de\/wp-content\/uploads\/2026\/06\/computer-cpu-processor-chip-circuit-board-motherboard-background-closeup-with-redblue-lighting-1200.jpg\" width=\"1200\" height=\"798\" alt=\"Xilinx Kria Projects by PICKPLACE\"\/><\/span><\/figure><\/div>\n\n\n\n<h2 id=\"technische-bewertung-und-machbarkeitsklarung\" class=\"wp-block-heading\">Technical Assessment and Feasibility Clarification<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">At the beginning of a Xilinx Kria project, the question often arises whether an existing approach can be transferred to a Kria module or if a new system architecture will be necessary. PICKPLACE analyzes the existing requirements, hardware, software components, data paths, and interfaces for this purpose. This process determines which parts of the application can run on the ARM-based Processing System and which parts will benefit from the programmable logic of the SoC. PICKPLACE develops baseboards for Xilinx Kria as part of the <a href=\"https:\/\/www.pickplace.de\/en\/hardware-development\/\" data-type=\"page\" data-id=\"865\">Hardware Development<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Feasibility studies also include the consideration of data rates, latencies, memory accesses, and external interfaces. For camera, sensor, network, or control applications, it is not enough to only consider the computational function. Data must enter the system, be processed there, temporarily stored, and then output. PICKPLACE views this chain as a continuous path because bottlenecks often arise at transitions: between the sensor and the carrier board, between the PL and PS, between the driver and the application, or between memory and the output interface.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If a prototype already exists, the evaluation can be based on measurements, source code, schematics, or existing development stages. If the project is still in the concept phase, the requirements are broken down into technical sub-areas. This forms a basis for decisions on module selection, the carrier board approach, software architecture, and the scope of FPGA development.<\/p>\n\n\n\n<h2 id=\"architekturarbeit-fur-kria-basierte-systeme\" class=\"wp-block-heading\">Architectural Work for KRIA-based Systems<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Xilinx Kria projects require a clear separation between the module, carrier board, operating system, FPGA design, and application code. PICKPLACE supports this architectural work by considering functions, interfaces, and responsibilities separately. A typical work step is determining which components are permanently on the Kria module and which must be implemented on a carrier board for specific projects.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The architecture also encompasses the question of how programmable logic is integrated into the overall system. FPGA functionalities can preprocess data, handle interfaces, implement protocols, or execute time-critical operations. Simultaneously, these functionalities must communicate with software processes. To achieve this, register interfaces, DMA paths, interrupts, memory areas, and driver concepts are considered. PICKPLACE ensures that these transitions are described early on, so that hardware and software development are not planned in isolation from each other.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Embedded Linux systems also consider the boot process, device tree, kernel drivers, userspace applications, and update paths. The Xilinx KRIA can be used in various project forms: as an evaluation platform, as the basis for a prototype, as a module in custom electronics, or as a starting point for migration from an older Xilinx platform. The appropriate scope depends on whether the goal is a demonstrator, a lab setup, a pre-series, or a development stage close to production.<\/p>\n\n\n\n<div class=\"wp-block-stackable-columns stk-block-columns stk-block stk-f980141 stk-block-background stk--has-background-overlay\" data-block-id=\"f980141\"><style>.stk-f980141 {background-image:url(https:\/\/www.pickplace.de\/wp-content\/uploads\/2026\/02\/mil-military-entwicklungsdienstleister-elektronik-aerospace-1200.jpg) !important;border-top-left-radius:var(--stk--preset--border-radius--xx-large, 32px) !important;border-top-right-radius:var(--stk--preset--border-radius--xx-large, 32px) !important;border-bottom-right-radius:var(--stk--preset--border-radius--xx-large, 32px) !important;border-bottom-left-radius:var(--stk--preset--border-radius--xx-large, 32px) !important;overflow:hidden !important;}<\/style><div class=\"stk-row stk-inner-blocks stk-block-content stk-content-align stk-f980141-column\">\n<div class=\"wp-block-stackable-column stk-block-column stk-column stk-block stk-3eb05d6\" data-v=\"4\" data-block-id=\"3eb05d6\"><style>.stk-3eb05d6 {border-top-width:0px !important;border-right-width:0px !important;border-bottom-width:0px !important;border-left-width:0px !important;}.stk-3eb05d6-container{padding-top:var(--stk--preset--spacing--60, 2.25rem) !important;padding-right:var(--stk--preset--spacing--60, 2.25rem) !important;padding-bottom:var(--stk--preset--spacing--60, 2.25rem) !important;padding-left:var(--stk--preset--spacing--60, 2.25rem) !important;}<\/style><div class=\"stk-column-wrapper stk-block-column__content stk-container stk-3eb05d6-container stk--no-background stk--no-padding\"><div class=\"stk-block-content stk-inner-blocks stk-3eb05d6-inner-blocks\">\n<div class=\"wp-block-stackable-heading stk-block-heading stk-block-heading--v2 stk-block stk-61c3574\" id=\"heading-placeholder\" data-block-id=\"61c3574\"><style>.stk-61c3574 {align-items:center !important;max-width:500px !important;min-width:auto !important;display:flex !important;}<\/style><h2 class=\"stk-block-heading__text\"><span style=\"color: #ffffff;\" class=\"stk-highlight\">PICKPLACE Hardware Development<\/span><\/h2><\/div>\n\n\n\n<div class=\"wp-block-stackable-text stk-block-text stk-block stk-628a190\" data-block-id=\"628a190\"><p class=\"stk-block-text__text\"><span style=\"color: #ffffff;\" class=\"stk-highlight\"><strong>Develop your hardware faster and more reliably \u2013 with PICKPLACE. Request a project now and efficiently bring your electronic system to implementation.<\/strong><\/span><\/p><\/div>\n\n\n\n<div class=\"wp-block-stackable-button-group stk-block-button-group stk-block stk-f2b9581\" data-block-id=\"f2b9581\"><div class=\"stk-row stk-inner-blocks stk-block-content stk-button-group\">\n<div class=\"wp-block-stackable-button stk-block-button stk-block stk-027953f\" data-block-id=\"027953f\"><a class=\"stk-link stk-button stk--hover-effect-darken\" href=\"https:\/\/www.pickplace.de\/en\/hardware-development\/\"><span class=\"stk-button__inner-text\">More <\/span><\/a><\/div>\n<\/div><\/div>\n<\/div><\/div><\/div>\n<\/div><\/div>\n\n\n\n<h2 id=\"carrier-board-und-schnittstellenbetrachtung\" class=\"wp-block-heading\">Carrier Board and Interface Analysis<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Since Xilinx KRIA modules are typically connected to a project-specific environment, the carrier board plays a central role. PICKPLACE supports the technical clarification of the interfaces without considering the module in isolation. Relevant points include power supply, reset and boot signals, clock supply, high-speed interfaces, GPIOs, sensor connections, network connections, and mechanical constraints.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For existing designs, it will be checked which signals are already available and what adjustments will be necessary for a KRIA integration. For new designs, the requirements will be derived from the application. This also includes the question of which interfaces can be directly controlled by the module and where additional components, level adjustments, or protection circuits are required. PICKPLACE can incorporate this clarification into the hardware design and document the dependencies on software development.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Especially for data-intensive applications, the interplay between the physical interface, FPGA design, and driver must be considered. A camera connection, an industrial data bus, or an Ethernet connection is not just a port on the circuit board. The interface influences pin assignments, clocks, constraints, memory paths, drivers, and test strategy. PICKPLACE handles such topics as an integrated technical chain.<\/p>\n\n\n\n<h2 id=\"entwicklung-mit-fpga-logik-und-embedded-software\" class=\"wp-block-heading\">Development with FPGA Logic and Embedded Software<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Xilinx KRIA connects classic embedded software with FPGA development. In this environment, PICKPLACE takes on tasks where both sides need to be coordinated. These include structuring FPGA functions, defining interfaces to software, integrating existing IP blocks, and preparing tests on the target system.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">On the software side, tasks can include boot configuration, Linux customization, driver integration, userspace applications, or communication with FPGA registers. During a migration, existing software components are checked for dependencies on old hardware, older toolchains, or specific interfaces. Subsequently, it can be determined which parts need to be adopted, adapted, or rewritten.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For FPGA components, data widths, clock domains, timing requirements, and resource utilization are considered. PICKPLACE can analyze existing designs, clean up interfaces, add test points, and prepare for integration into a Xilinx KRIA project. If Vitis, Vivado, or PetaLinux based workflows exist, they will be included in the project assessment. This is not about using a specific tool for its own sake, but about understandable development states, repeatable builds, and clear handoffs between hardware and software components.<\/p>\n\n\n\n<h2 id=\"fehleranalyse-debugging-und-redesign\" class=\"wp-block-heading\">Error analysis, debugging, and redesign<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Many KRIA projects do not originate from a blank development slate but from a concrete technical problem. An existing prototype doesn't boot reliably, a data path drops packets, a driver delivers incorrect values, an FPGA block behaves differently under load than expected, or an interface only works in certain operating states. PICKPLACE supports the isolation of such errors by consolidating measurements, logs, schematics, constraints, software versions, and configurations.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Troubleshooting can occur at several levels. At the hardware level, power supply, signal routing, signal levels, clocks, and reset behavior are examined. At the FPGA level, timing, clock domain crossings, interface protocols, and internal data paths can be investigated. At the software level, boot messages, kernel output, driver initialization, memory access, and application behavior are analyzed. In Xilinx KRIA systems, the cause is often not in a single file or a single component, but in an interaction between configuration, hardware connection, and software access.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If an existing solution cannot be viably further developed, a redesign may become necessary. PICKPLACE supports the process of defining the scope of a redesign. Not every anomaly requires a new PCB or an FPGA redesign. Sometimes, an adjustment of the interface description, a correction in the device tree, a modified driver initialization, or a clearer separation of test and production configurations is sufficient. The decision is derived from the technical findings.<\/p>\n\n\n\n<h2 id=\"dokumentation-und-ubergabe-in-die-umsetzung\" class=\"wp-block-heading\">Documentation and handover to implementation<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">KRIA projects require documentation that describes hardware, FPGA logic, and software collectively. PICKPLACE creates or supplements technical documentation so that development statuses can be understood and further processed. This includes architectural overviews, interface descriptions, register definitions, build notes, test descriptions, and open issues for the next project phase.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For the handover to further implementation, dependencies are named: used tool versions, required configurations, external components, known limitations, and assumptions from the development phase. This information helps to scope follow-up work and to shorten later troubleshooting. PICKPLACE describes not only which solution was implemented, but also which decisions were made behind it and which alternatives were ruled out in the project.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In the Xilinx Kria topic area, PICKPLACE therefore primarily takes on tasks requiring a system understanding across multiple levels: module platform, carrier board, FPGA design, embedded Linux, interfaces, and application. The concrete scope of services is derived from the existing development status and the technical goals of the project.<\/p>","protected":false},"excerpt":{"rendered":"<p>Xilinx KRIA describes a System-on-Module platform from AMD Xilinx, which integrates a processor, programmable logic, and central memory and I\/O functions onto a single module. PICKPLACE works in this area on projects where existing electronics, embedded software, or data-intensive applications are to be evaluated, migrated, or redeveloped on a KRIA-based architecture. Typical tasks lie at the intersection of hardware, FPGA logic, embedded Linux, interface integration, and application-oriented system development.<\/p>","protected":false},"featured_media":2600,"template":"","meta":{"footnotes":""},"categories":[],"tags":[],"class_list":["post-2599","projekt","type-projekt","status-publish","has-post-thumbnail","hentry"],"blocksy_meta":[],"_links":{"self":[{"href":"https:\/\/www.pickplace.de\/en\/wp-json\/wp\/v2\/projekt\/2599","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.pickplace.de\/en\/wp-json\/wp\/v2\/projekt"}],"about":[{"href":"https:\/\/www.pickplace.de\/en\/wp-json\/wp\/v2\/types\/projekt"}],"version-history":[{"count":2,"href":"https:\/\/www.pickplace.de\/en\/wp-json\/wp\/v2\/projekt\/2599\/revisions"}],"predecessor-version":[{"id":2606,"href":"https:\/\/www.pickplace.de\/en\/wp-json\/wp\/v2\/projekt\/2599\/revisions\/2606"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.pickplace.de\/en\/wp-json\/wp\/v2\/media\/2600"}],"wp:attachment":[{"href":"https:\/\/www.pickplace.de\/en\/wp-json\/wp\/v2\/media?parent=2599"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.pickplace.de\/en\/wp-json\/wp\/v2\/categories?post=2599"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.pickplace.de\/en\/wp-json\/wp\/v2\/tags?post=2599"}],"curies":[{"name":"WP","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}