7005 - Propel: How to bring up serial UART terminal for Propel RiscV project with MachXO5™-NX Development Kit?
Description:
This bring up guideline is based on Propel Builder default hello world template.
Hardware setup pre-requisites
1. Power up the development kit with USB header (J19) instead of 12V power.
2. Removed JP8 and JP9 reset jumper to enable USB FTDI for both User USB header and Config USB header.
Radiant project device pin constraint
Please refer to: MachXO5-NX Development Board Evaluation Board User Guide (FPGA-EB-02052-1.1) Appendix C. User Defined Preference File Listing.
Port Name | Pin |
rstn_i | F20 |
rxd_i | B11 |
txd_o | B12 |
led_o[0] | R3 |
led_o[1] | R2 |
led_o[2] | R1 |
led_o[3] | P7 |
led_o[4] | H12 |
led_o[5] | H11 |
led_o[6] | G13 |
led_o[7] | G12 |
Solution:
Bring up steps
1. Connect mini-USB cable to JTAG/USB (J11).
2. Connect mini-USB cable to UART/USB (J19).
3. You should detect two USB cables.
1) Cable 1: FTUSB-0 is for JTAG bitstream configuration
2) Cable 2 is mainly use for UART COM ports
4. You should also make sure Device Manager able to detect four COM ports.
1) You may remove UART cable (J19) to check which COM port is for meant for UART terminal.
5. Connect and configure a serial terminal in Propel SDK before running the debug session.
1) Select Terminal TAB.
2) Click on Terminal icon to Open the Terminal.
3) Choose Serial Terminal in Launch Terminal popup window.
4) Now Launch Terminal provides new setting entries of Serial Terminal.
5) Select the correct UART COM port.
6) Set BAUD RATE = 115200.
7) Click OK.
8) You should be able to successfully run OpenOCD debugger, with printout in Terminal after this.
Related Articles
7326 - Propel: Why does the RISC-V debug session hang during exception handling?
Description: RISC V CPU instruction/data manager consists of exception handling routine in the BSP source: ..\src\bsp\driver\riscv_mc\interrupt.c The API is a standard RISC V practice where it prints out the failure based on the mcause register when ...6915 - Propel: Is it possible to do Propel OpenOCD debugging on a device that is part of a JTAG chain?
It is possible to do a Propel OpenOCD debugging on a device that is part of a JTAG chain. An example setup here is with a CertusPro-NX Evaluation Board and a CertusPro-NX Versa Board. The first board is the evaluation board while the second board is ...7268 - Propel: What is the workaround for the OpenOCD Debugger Error - Err: can not found the device from device family database, use default value to access this device?
Description: When you perform an OpenOCD debug session with the MachXO3LF Evaluation Kit, you may encounter the error message below, where the debugger is unable to identify the device family from the database. Device List: LCMXO3LF-9400C:0x612BE043 ...7012 - Propel: Is it possible to script the process of creating a project in Lattice Propel SDK?
Propel SDK project is based on "Eclipse CDT Management Build System". Since the system has no command-line support for creating projects fundamentally, Propel SDK also has no command-line support for creating projects.7053 - Propel: Why I unable to run debugger with Propel SDK on my RISC-V Project?
Description: 1. RISC-V reset vector is fixed at address 0x00000000, thus instruction memory must start at address 0x0. 2. RISC-V instruction port is a read only port. To run debugger with Propel SDK, the SoC design must support writes to the ...