MICROCHIP AN4229 Risc V Processor Subsystem
Product Information
Specifications
- Product Name: RT PolarFire
- Model: AN4229
- Processor Subsystem: RISC-V
- Power Requirements: 12V/5A AC power adapter
- Interface: USB 2.0 A to mini-B, Micro B USB 2.0
Product Usage Instructions
Design Requirements
The hardware and software requirements for building a Mi-V processor subsystem are as follows:
- 12V/5A AC power adapter and cord
- USB 2.0 A to mini-B cable
- Micro B USB 2.0 cable
- Refer to the readme.txt file in the design files for all software versions needed
Design Prerequisites
Before starting the design process, ensure the following steps are performed:
- [List of prerequisites]
Design Description
MIV_RV32 is a processor core designed to implement the RISC-V instruction set. The core can be implemented on an FPGA.
FAQ
- Q: What are the hardware requirements for RT PolarFire?
A: The hardware requirements include a 12V/5A AC power adapter and cord, USB 2.0 A to mini-B cable, and Micro B USB 2.0 cable. - Q: What is the processor subsystem of RT PolarFire?
A: The processor subsystem is based on the RISC-V architecture.
Introduction (Ask a Question)
Microchip offers the Mi-V processor IP and software toolchain at no cost to develop RISC-V processor based designs. RISC-V is a standard open Instruction Set Architecture (ISA) under the governance of the RISC-V foundation. It offers numerous benefits, which include enabling the open-source community to test and improve cores at a faster pace than closed ISAs. RT PolarFire® Field Programmable Gate Array (FPGAs) support Mi-V soft processors to run user applications. This application note describes how to build a Mi-V processor subsystem to execute a user application from the designated TCM memory initialized from the SPI Flash.
Design Requirements (Ask a Question)
The following table lists the hardware and software requirements for building a Mi-V processor subsystem.
Table 1-1. Design Requirements
Requirement | Description |
Hardware Requirements | |
RT PolarFire® Development Kit (RTPF500TS-1CG1509M) 12V/5A AC power adapter and cord USB 2.0 A to mini-B cable Micro B USB 2.0 cable | REV 1.0 |
Software Requirements | |
Libero® SoC FlashPro Express SoftConsole | See the readme.txt file in the design files for all software versions needed to create the Mi-V reference design |
Design Prerequisites (Ask a Question)
Before you start, perform the following steps:
- Download the reference design files from RT PolarFire: Building RISC-V Processer Subsystem.
- Download and install Libero® SoC from the following link: Libero SoC v2024.1 or later.
Design Description (Ask a Question)
MIV_RV32 is a processor core designed to implement the RISC-V instruction set. The core can be configured to have AHB, APB3, and AXI3/4 bus interfaces for peripheral and memory accesses. The following figure shows the top-level block diagram of the Mi-V subsystem built on RT PolarFire® FPGA.
The user application to be executed on Mi-V processor can be stored in an external SPI Flash. At device power-up, the system controller initializes the designated TCM with the user application. The system Reset is released after the TCM initialization is completed. If the user application is stored in SPI Flash, the System Controller uses the SC_SPI interface for reading the user application from SPI Flash. The given user application prints the UART message “Hello World!” and blinks user LEDs on the board.
Hardware Implementation (Ask a Question)
The following figure shows the Libero design of the Mi-V processor subsystem.
IP Blocks (Ask a Question)
The following table lists the IP blocks used in the Mi-V processor subsystem reference design and their function.
Table 4-1. IP Blocks Description
IP Name | Description |
INIT_MONITOR | The RT PolarFire® Initialization Monitor gets the status of device and memory initialization |
reset_syn | This is the CORERESET_PF IP instantiation which generates a system-level synchronous Reset for the Mi-V subsystem |
CCC_0 |
The RT PolarFire Clock Conditioning Circuitry (CCC) block takes an input clock of 160 MHz from the PF_OSC block and generates a 83.33 MHz fabric clock for the Mi-V processor subsystem and other peripherals. |
MIV_RV32_C0 (Mi-V Soft Processor IP) |
The Mi-V soft processor default Reset Vector Address value is 0✕8000_0000. After the device reset, the processor executes the application from 0✕8000_0000. TCM is the main memory of the Mi-V processor and is memory mapped to 0✕8000_0000. The TCM gets initialized with the user application which stored in the SPI Flash. In the Mi-V processor memory map, the 0✕8000_0000 to 0✕8000_FFFF range is defined for TCM memory interface and the 0✕7000_0000 to 0✕7FFF_FFFF range is defined for the APB interface. |
MIV_ESS_C0_0 | This MIV Extended Subsystem (ESS) is used to support GPIO and UART |
CoreSPI_C0_0 | CoreSPI is used to program the external SPI Flash |
PF_SPI | PF_SPI macro interfaces the fabric logic to the external SPI Flash, which is connected to System Controller |
PF_OSC | PF_OSC is a on board oscillator which generates 160 MHz output clock |
Important: All the IP user guides and handbooks are available from Libero SoC > Catalog
Memory Map (Ask a Question)
The following table lists the memory map of the memories and peripherals.
Table 4-2. Memory Map Description
Peripherals | Start Address |
TCM | 0x8000_0000 |
MIV_ESS_UART | 0x7100_0000 |
MIV_ESS_GPIO | 0x7500_0000 |
Software Implementation (Ask a Question)
Microchip provides SoftConsole toolchain to build a RISC-V user application executable (.hex) file and debug it. The reference design files include the Firmware workspace that contains the MiV_uart_blinky software project. The MiV_uart_blinky user application is programmed on an external SPI Flash using Libero® SoC. The given user application prints the UART message “Hello World!” and blinks user LEDs on the board.
As per the Libero SoC design memory map, the UART and GPIO peripheral addresses are mapped to 0x71000000 and 0x75000000, respectively. This information is provided in the hw_platform.h file as shown in the following figure.
The user application must be executed from the TCM memory (code, data, and stack). Therefore, the RAM address in the linker script is set to the starting address of the TCM memory as shown in the following figure.
The linker script (miv-rv32-ram.ld) is available in the FW\MiV_uart_blinky\miv_rv32_hal folder of the design files. To build the user application, perform the following steps:
- Create a Mi-V SoftConsole project
- Download the MIV_RV32 HAL files and drivers from GitHub using the link as follows: github.com/Mi-V-Soft-RISC-V/platform
- Import the firmware drivers
- Create the main.c file with application code
- Map firmware drivers and the linker script
- Map memory and peripheral addresses
- Build the application
For more information about these steps, see AN4997: PolarFire FPGA Building a Mi-V Processor Subsystem. The .hex file is created after successful build and it is used for design and memory initialization configuration in Running the Demo.
Setting Up the Demo (Ask a Question)
To set up the demo, perform the following steps:
- Setting up the Hardware
- Setting up the Serial Terminal (Tera Term)
Setting Up the Hardware (Ask a Question)
Important: Mi-V application debugging using SoftConsole debugger will not work if System Controller Suspend Mode is enabled. The System Controller Suspend Mode is disabled for this design to demonstrate Mi-V application.
To setup the hardware, perform the following steps:
- Power off the board using the SW7 switch.
- Open J31 jumper to use the external FlashPro programmer or Close J31 jumper to use the embedded FlashPro programmer.
Important: Embedded Flash Pro Programmer can only be used for Programming through Libero or FPExpress it cannot be used for debugging Mi-V based Application. - Connect the host PC to the J24 connector using the USB cable.
- To enable the SC_SPI, 1-2 pins of jumper J8 should be closed.
- Connect the FlashPro programmer to J3 connector (JTAG header) and use another USB cable to connect the FlashPro programmer to the Host PC.
- Ensure that the USB to UART bridge drivers are automatically detected, which can be verified through the device manager on the host PC.
Important: As shown in Figure 6-1, the port properties of COM16 show that it is connected to USB serial port. Hence, COM16 is selected in this example. The COM port number is system specific. If the USB to UART bridge drivers are not installed, download and install the drivers from www.microchip.com/en-us/product/mcp2200. - Connect the power supply to J19 connector and switch ON the power supply using switch SW7.
Setting Up the Serial Terminal (Tera Term) (Ask a Question)
The user application (MiV_uart_blinky.hex file) prints the “Hello World!” message on the serial terminal through the UART interface.
To set up the serial terminal, perform the following steps:
- Launch Tera Term on the Host PC.
- Select the identified COM Port in Tera Term as shown in the following figure.
- From the Menu bar, select Setup > Serial port to set up the COM port.
- Set the Speed (baud) to 115200 and Flow Control to none and click on New setting option as shown in the following figure.
After the serial terminal is set up, next step is to program the RT PolarFire® device.
Running the Demo (Ask a Question)
To run the demo, perform the following steps:
- Generating the TCM Initialization Client
- Programming the RT PolarFire® Device
- Generating the SPI Flash Image
- Programming the SPI Flash
Generating the TCM Initialization Client (Ask a Question)
To initialize the TCM in RT PolarFire® using the system controller, a local parameters l_cfg_hard_tcm0_en in the miv_rv32_subsys_pkg.v file must be changed to 1’b1 before Synthesis. For more information, see the MIV_RV32 User Guide.
In Libero® SoC, the Configure Design Initialization Data and Memories option generates the TCM initialization client and adds it to sNVM, μPROM, or an external SPI Flash, based on the type of non-volatile memory selected. In this application note, the TCM initialization client is stored in the SPI Flash. This process requires the user application executable file (.hex file). The hex file (*.hex) is generated using SoftConsole application project. A sample user application is provided along with the design files. The user application file (.hex) is selected for creating the TCM initialization client using the following steps:
- Launch Libero® SoC and run the script.tcl (Appendix 2: Running the TCL Script).
- Select Configure Design Initialization Data and Memories > Libero Design Flow.
- On the Fabric RAMs tab, select the TCM instance and double-click on it to open the Edit Fabric RAM Initialization Client dialog box, as shown in the following figure.
In the Edit Fabric RAM Initialization Client dialog box, set Storage type to SPI-Flash. Then, select Content from file and click the Import (…) button as shown in the following figure.
Programming the RT PolarFire Device (Ask a Question)
- The reference design files include the Mi-V processor subsystem project created using Libero® SoC. The RT PolarFire® device can be programmed using Libero SoC.
- The Libero SoC design flow is shown in the following figure.
To program the RT PolarFire device, open the Mi-V processor subsystem Libero project, which is created using the provided TCL scripts in Libero SoC, and double-click Run Program Action .
Generating the SPI Flash Image (Ask a Question)
- To generate the SPI Flash image, double-click Generate SPI Flash Image on the Design Flow tab.
- When the SPI Flash image is generated successfully, a green tick mark appears next to Generate SPI Flash Image.
Programming the SPI Flash (Ask a Question)
To program the SPI Flash image, perform the following steps:
- Double-click Run PROGRAM_SPI_IMAGE on the Design Flow tab.
- Click Yes in the dialog box.
- When the SPI image is successfully programmed on to the device, a green tick mark appears next to Run PROGRAM_SPI_IMAGE.
- After SPI Flash programming is completed, the TCM is ready. As a result, LEDs 1, 2, 3, and 4 blink, then prints are observed on the serial terminal, as shown in the following figure.
This concludes the demo.
The RT PolarFire® device and the SPI Flash can also be programmed using FlashPro Express, see Appendix 1: Programming the RT PolarFire Device and SPI Flash Using FlashPro Express.
Appendix 1: Programming the RT PolarFire Device and SPI Flash Using FlashPro Express (Ask a Question)
The reference design files include a programming job file for programming the RT PolarFire® device using FlashPro Express. This job file also includes the SPI Flash image, which is the TCM initialization client. FlashPro Express programs both the RT PolarFire device and the SPI Flash with this programming .job file. The programming .job file is available at DesignFiles_directory\Programming_files.
To program the RT PolarFire device with the programming file using FlashPro Express, perform the following steps:
- Set up the hardware, see Setting Up the Hardware.
- On the host PC, launch the FlashPro Express software.
- To create a new job project, click New or select New Job Project from FlashPro Express Job from the Project menu.
- Enter the following in the dialog box:
- Programming job file: Click Browse and navigate to the location where the .job file is located and select the file. The job file is available at DesignFiles_directory\Programming_files.
- FlashPro Express job project location: Click Browse and navigate to the location where you want to save the project.
- Click OK. The required programming file is selected and ready to be programmed.
- The FlashPro Express window appears as shown in the following figure. Confirm that a programmer number appears in the Programmer field. If it does not, check the board connections and click Refresh/Rescan Programmers.
- Click RUN. When the device is programmed successfully, a RUN PASSED status is displayed as shown in the following figure.
This concludes the RT PolarFire device and the SPI Flash programming. After programming the board, observe the “Hello World!” message printed on the UART terminal and the blinking of user LEDs.
Appendix 2: Running the TCL Script (Ask a Question)
TCL scripts are provided in the design files folder under directory HW. If required, the design flow can be reproduced from Design Implementation till generation of job file.
To run the TCL, perform the following steps:
- Launch the Libero software.
- Select Project > Execute Script…..
- Click Browse and select script.tcl from the downloaded HW directory.
- Click Run.
After successful execution of TCL script, Libero project is created within HW directory.
- For more information about TCL scripts, see rtpf_an4229_df/HW/TCL_Script_readme.txt. For more information on TCL commands, see Tcl Commands Reference Guide. Contact Microchip
- Technical Support for any queries encountered, while running the TCL script.
Revision History (Ask a Question)
The revision history table describes the changes that were implemented in the document. The changes are listed by revision, starting with the most current publication.
Table 10-1. Revision History
Revision | Date | Description |
B | 10/2024 | The following is the list of changes made in the revision B of the document:
|
A | 10/2021 | The first publication of this document |
Microchip FPGA Support
Microchip FPGA products group backs its products with various support services, including Customer Service, Customer Technical Support Center, a website, and worldwide sales offices. Customers are suggested to visit Microchip online resources prior to contacting support as it is very likely that their queries have been already answered.
Contact Technical Support Center through the website at www.microchip.com/support. Mention the FPGA Device Part number, select appropriate case category, and upload design files while creating a technical support case.
Contact Customer Service for non-technical product support, such as product pricing, product upgrades, update information, order status, and authorization.
- From North America, call 800.262.1060
- From the rest of the world, call 650.318.4460
- Fax, from anywhere in the world, 650.318.8044
Microchip Information
The Microchip Website
Microchip provides online support via our website at www.microchip.com/. This website is used to make files and information easily available to customers. Some of the content available includes:
- Product Support – Data sheets and errata, application notes and sample programs, design resources, user’s guides and hardware support documents, latest software releases and archived software
- General Technical Support – Frequently Asked Questions (FAQs), technical support requests, online discussion groups, Microchip design partner program member listing
- Business of Microchip – Product selector and ordering guides, latest Microchip press releases, listing of seminars and events, listings of Microchip sales offices, distributors and factory representatives
Product Change Notification Service
- Microchip’s product change notification service helps keep customers current on Microchip products. Subscribers will receive email notification whenever there are changes, updates, revisions or errata related to a specified product family or development tool of interest.
- To register, go to www.microchip.com/pcn and follow the registration instructions.
Customer Support
Users of Microchip products can receive assistance through several channels:
- Distributor or Representative
- Local Sales Office
- Embedded Solutions Engineer (ESE)
- Technical Support
Customers should contact their distributor, representative or ESE for support. Local sales offices are also available to help customers. A listing of sales offices and locations is included in this document.
Technical support is available through the website at: www.microchip.com/support
Microchip Devices Code Protection Feature
Note the following details of the code protection feature on Microchip products:
- Microchip products meet the specifications contained in their particular Microchip Data Sheet.
- Microchip believes that its family of products is secure when used in the intended manner, within operating specifications, and under normal conditions.
- Microchip values and aggressively protects its intellectual property rights. Attempts to breach the code protection features of Microchip product is strictly prohibited and may violate the Digital Millennium Copyright Act.
- Neither Microchip nor any other semiconductor manufacturer can guarantee the security of its code. Code protection does not mean that we are guaranteeing the product is “unbreakable”. Code protection is constantly evolving. Microchip is committed to continuously improving the code protection features of our products.
Legal Notice
This publication and the information herein may be used only with Microchip products, including to design, test, and integrate Microchip products with your application. Use of this information
in any other manner violates these terms. Information regarding device applications is provided only for your convenience and may be superseded by updates. It is your responsibility to ensure that your application meets with your specifications. Contact your local Microchip sales office for additional support or, obtain additional support at www.microchip.com/en-us/support/design-help/client-support-services.
THIS INFORMATION IS PROVIDED BY MICROCHIP “AS IS”. MICROCHIP MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WHETHER EXPRESS OR IMPLIED, WRITTEN OR ORAL, STATUTORY OR OTHERWISE, RELATED TO THE INFORMATION INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE, OR WARRANTIES RELATED TO ITS CONDITION, QUALITY, OR PERFORMANCE.
IN NO EVENT WILL MICROCHIP BE LIABLE FOR ANY INDIRECT, SPECIAL, PUNITIVE, INCIDENTAL, OR CONSEQUENTIAL LOSS, DAMAGE, COST, OR EXPENSE OF ANY KIND WHATSOEVER RELATED TO THE INFORMATION OR ITS USE, HOWEVER CAUSED, EVEN IF MICROCHIP HAS BEEN ADVISED OF THE POSSIBILITY OR THE DAMAGES ARE FORESEEABLE. TO THE FULLEST EXTENT ALLOWED BY LAW, MICROCHIP’S TOTAL LIABILITY ON ALL CLAIMS IN ANY WAY RELATED TO THE INFORMATION OR ITS USE WILL NOT EXCEED THE AMOUNT OF FEES, IF ANY, THAT YOU HAVE PAID DIRECTLY TO MICROCHIP FOR THE INFORMATION.
Use of Microchip devices in life support and/or safety applications is entirely at the buyer’s risk, and the buyer agrees to defend, indemnify and hold harmless Microchip from any and all damages, claims, suits, or expenses resulting from such use. No licenses are conveyed, implicitly or otherwise, under any Microchip intellectual property rights unless otherwise stated.
Trademarks
The Microchip name and logo, the Microchip logo, Adaptec, AVR, AVR logo, AVR Freaks, BesTime, BitCloud, CryptoMemory, CryptoRF, dsPIC, flexPWR, HELDO, IGLOO, JukeBlox, KeeLoq, Kleer, LANCheck, LinkMD, maXStylus, maXTouch, MediaLB, megaAVR, Microsemi, Microsemi logo, MOST, MOST logo, MPLAB, OptoLyzer, PIC, picoPower, PICSTART, PIC32 logo, PolarFire, Prochip Designer, QTouch, SAM-BA, SenGenuity, SpyNIC, SST, SST Logo, SuperFlash, Symmetricom, SyncServer, Tachyon, TimeSource, tinyAVR, UNI/O, Vectron, and XMEGA are registered trademarks of Microchip Technology Incorporated in the U.S.A. and other countries.
AgileSwitch, ClockWorks, The Embedded Control Solutions Company, EtherSynch, Flashtec, Hyper Speed Control, HyperLight Load, Libero, motorBench, mTouch, Powermite 3, Precision Edge, ProASIC, ProASIC Plus, ProASIC Plus logo, Quiet-Wire, SmartFusion, SyncWorld, TimeCesium, TimeHub, TimePictra, TimeProvider, and ZL are registered trademarks of Microchip Technology Incorporated in the U.S.A.
Adjacent Key Suppression, AKS, Analog-for-the-Digital Age, Any Capacitor, AnyIn, AnyOut, Augmented Switching, BlueSky, BodyCom, Clockstudio, CodeGuard, CryptoAuthentication, CryptoAutomotive, CryptoCompanion, CryptoController, dsPICDEM, dsPICDEM.net, Dynamic Average Matching, DAM, ECAN, Espresso T1S, EtherGREEN, EyeOpen, GridTime, IdealBridge, IGaT, In-Circuit Serial Programming, ICSP, INICnet, Intelligent Paralleling, IntelliMOS, Inter-Chip Connectivity, JitterBlocker, Knob-on-Display, MarginLink, maxCrypto, maxView, memBrain, Mindi, MiWi, MPASM, MPF, MPLAB Certified logo, MPLIB, MPLINK, mSiC, MultiTRAK, NetDetach, Omniscient Code Generation, PICDEM, PICDEM.net, PICkit, PICtail, Power MOS IV, Power MOS 7, PowerSmart, PureSilicon, QMatrix, REAL ICE, Ripple Blocker, RTAX, RTG4, SAM-ICE, Serial Quad I/O, simpleMAP, SimpliPHY, SmartBuffer, SmartHLS, SMART-I.S., storClad, SQI, SuperSwitcher, SuperSwitcher II, Switchtec, SynchroPHY, Total Endurance, Trusted Time, TSHARC, Turing, USBCheck, VariSense, VectorBlox, VeriPHY, ViewSpan, WiperLock, XpressConnect, and ZENA are trademarks of Microchip Technology Incorporated in the U.S.A. and other countries.
SQTP is a service mark of Microchip Technology Incorporated in the U.S.A. The Adaptec logo, Frequency on Demand, Silicon Storage Technology, and Symmcom are registered trademarks of Microchip Technology Inc. in other countries. GestIC is a registered trademark of Microchip Technology Germany II GmbH & Co. KG, a subsidiary of Microchip Technology Inc., in other countries.
All other trademarks mentioned herein are property of their respective companies.
© 2024, Microchip Technology Incorporated and its subsidiaries. All Rights Reserved.
- ISBN: 978-1-6683-0441-9
Quality Management System
For information regarding Microchip’s Quality Management Systems, please visit www.microchip.com/quality.
Worldwide Sales and Service
AMERICAS | ASIA/PACIFIC | ASIA/PACIFIC | EUROPE |
Corporate Office 2355 West Chandler Blvd. Chandler, AZ 85224-6199 Tel: 480-792-7200 Fax: 480-792-7277 Technical Support: www.microchip.com/support Web Address: www.microchip.com Atlanta Duluth, GA Tel: 678-957-9614 Fax: 678-957-1455 Austin, TX Tel: 512-257-3370 Boston Westborough, MA Tel: 774-760-0087 Fax: 774-760-0088 Chicago Itasca, IL Tel: 630-285-0071 Fax: 630-285-0075 Dallas Addison, TX Tel: 972-818-7423 Fax: 972-818-2924 Detroit Novi, MI Tel: 248-848-4000 Houston, TX Tel: 281-894-5983 Indianapolis Noblesville, IN Tel: 317-773-8323 Fax: 317-773-5453 Tel: 317-536-2380 Los Angeles Mission Viejo, CA Tel: 949-462-9523 Fax: 949-462-9608 Tel: 951-273-7800 Raleigh, NC Tel: 919-844-7510 New York, NY Tel: 631-435-6000 San Jose, CA Tel: 408-735-9110 Tel: 408-436-4270 Canada – Toronto Tel: 905-695-1980 |Fax: 905-695-2078 |
Australia – Sydney Tel: 61-2-9868-6733 China – Beijing Tel: 86-10-8569-7000 China – Chengdu Tel: 86-28-8665-5511 China – Chongqing Tel: 86-23-8980-9588 China – Dongguan Tel: 86-769-8702-9880 China – Guangzhou Tel: 86-20-8755-8029 China – Hangzhou Tel: 86-571-8792-8115 China – Hong Kong SAR Tel: 852-2943-5100 China – Nanjing Tel: 86-25-8473-2460 China – Qingdao Tel: 86-532-8502-7355 China – Shanghai Tel: 86-21-3326-8000 China – Shenyang Tel: 86-24-2334-2829 China – Shenzhen Tel: 86-755-8864-2200 China – Suzhou Tel: 86-186-6233-1526 China – Wuhan Tel: 86-27-5980-5300 China – Xian Tel: 86-29-8833-7252 China – Xiamen Tel: 86-592-2388138 China – Zhuhai Tel: 86-756-3210040 |
India – Bangalore Tel: 91-80-3090-4444 India – New Delhi Tel: 91-11-4160-8631 India – Pune Tel: 91-20-4121-0141 Japan – Osaka Tel: 81-6-6152-7160 Japan – Tokyo Tel: 81-3-6880- 3770 Korea – Daegu Tel: 82-53-744-4301 Korea – Seoul Tel: 82-2-554-7200 Malaysia – Kuala Lumpur Tel: 60-3-7651-7906 Malaysia – Penang Tel: 60-4-227-8870 Philippines – Manila Tel: 63-2-634-9065 Singapore Tel: 65-6334-8870 Taiwan – Hsin Chu Tel: 886-3-577-8366 Taiwan – Kaohsiung Tel: 886-7-213-7830 Taiwan – Taipei Tel: 886-2-2508-8600 Thailand – Bangkok Tel: 66-2-694-1351 Vietnam – Ho Chi Minh Tel: 84-28-5448-2100 |
Austria – Wels Tel: 43-7242-2244-39 Fax: 43-7242-2244-393Denmark – Copenhagen Tel: 45-4485-5910 Fax: 45-4485-2829Finland – Espoo Tel: 358-9-4520-820 France – Paris Germany – Garching Germany – Haan Germany – Heilbronn Germany – Karlsruhe Tel: 49-721-625370 Germany – Munich Germany – Rosenheim Israel – Hod Hasharon Italy – Milan Italy – Padova Netherlands – Drunen Norway – Trondheim Poland – Warsaw Romania – Bucharest Spain – Madrid |
Application Note
© 2024 Microchip Technology Inc. and its subsidiaries
Documents / Resources
![]() |
MICROCHIP AN4229 Risc V Processor Subsystem [pdf] User Guide AN4229, AN4229 Risc V Processor Subsystem, AN4229, Risc V Processor Subsystem, Processor Subsystem, Subsystem |