search.noResults

search.searching

saml.title
dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
Focus


microcontrollers to high-performance data centre processors. Market adoption trends further highlight RISC-V’s accelerating momentum. RISC-V has already demonstrated rapid growth in embedded systems, outpacing x86 and emerging as a credible alternative to Arm. While Arm remains dominant in mobile devices, RISC-V is gaining traction with increasing support for smartphone SoCs. In data centres, x86 still dominates, yet RISC-V shows potential, especially in custom accelerators. For IoT, RISC-V’s open-source fl exibility and power effi ciency make it a front-runner for future deployments, outperforming both x86 and Arm in adaptability and cost-effi ciency.


Market disruptor T e RISC-V allows a straightforward pipeline structure with fi xed-length instructions that simplify fetching and decoding, reducing latency and enabling faster write-back operations. Arm’s pipeline can handle variable-length instructions, supporting broader operation sets, but this increases decoding complexity and slows execution stages. Figure 2 shows the evolution of BOOM (Berkeley Out-of-Order Machine) cores, designed for high-performance RISC-V implementations. BOOMv1 introduces a basic branch


prediction model with a 7-cycle penalty on mispredictions. BOOMv2 improves this with GShare branch prediction and additional decode/issue stages, cutting load-use latency to 4 cycles. BOOMv3 integrates advanced predictors such as TAGE, RAS and uBTB, plus a custom RoCC accelerator, further reducing latency and improving parallel execution. T ese enhancements demonstrate how RISC-V enables open-ended innovation in processor design, providing customisation opportunities not available in proprietary architectures.


Challenges and opportunities RISC-V suff ers from some challenges and barriers that include verifi cation and compliance complexity. Open-source fosters collaboration, but


managing IP in shared environments remains complex. Ensuring reliable functionality across


Figure 1: Simplifi ed RISC-V processor pipeline highlighting instruction fetch (IF), decode (ID), execute (EX), memory access (MEM) and write- back (WB) stages


custom implementations demands advanced methodologies, specialised tools and highly skilled teams. T e openness of RISC-V is its strength but leads to implementation variations and, without robust compliance standards, ecosystem fragmentation can occur. T is is why RISC-V International’s ongoing eff orts are essential for establishing shared metrics, best practices and certifi cation pathways. Also, Arm boasts a well-established soſt ware


stack, whereas the RISC-V ecosystem is just developing. Gaps in toolchains, drivers and middleware can slow adoption. However, accelerating commercial and


community-driven development is key to ecosystem maturity. Enterprises entrenched in Arm or x86 architectures may hesitate to switch due to existing tooling, developer familiarity and support ecosystems. Mitigating this inertia requires clear ROI, phased migration strategies, and proven case studies. Clear licensing models, IP governance


frameworks and legal safeguards are crucial to protecting innovation and encouraging industry trust. Its open-source model fi rmly positions it for future scaleability, driven by the


growing demand for customised processors in emerging technologies like AI, IoT and edge computing.


Making RISC-V part of the business plan To start integrating RISC-V, engineers and businesses should fi rst evaluate a strategic fi t, conduct in-depth feasibility studies to determine how the architecture aligns with their technical and business goals, and consider the short-term integration needs and the long-term potential for diff erentiation. Internal engineering teams should be upskilled through training, workshops and webinars, and equipped with verifi cation frameworks and tools optimised for RISC-V development and compliance. It also helps to actively participate in RISC-V forums, open-source initiatives and standardisation eff orts, since collaborations foster innovation, enhance internal capabilities and place an organisation in a leadership position. It is also worth to proactively address


soſt ware readiness by investing in internal developments, supporting RISC-V-


www.electronicsworld.co.uk October 2025 09


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44