Edocecrous

Members
  • Content Count

    7
  • Joined

  • Last visited

About Edocecrous

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi, I was told if i just add some interrupt sources and generate the code with vitis it will by default generate the code for fast interrupts. I tried many different ways to build the system, left it on auto, or manually set the processor to FAST interrupts, the generated code not once included XIntc_ConnectFastHandler()... The design evaluates to be ok, and both the axi intc and the processor is set up for fast interrupts, and the reset and clk is connected, so i believe the HW is set up correctly.
  2. Hi, I made it work in normal mode, concat receiving 2 sources (timer and gpio), and going into the interrupt controller. Now i want to change to FAST mode, so i changed both the microblaze and the interrupt controller to fast mode, run connection automat, and it hooked up the clock and the reset to the interrupt controller. I also generated new code in vitis, but i can't see any change in the generated software... The timer still has both the XTmrCtr_SetHandler(&TimerCounter, TimerCounterHandler, &TimerCounter); //Setup the handler for the timer counter a
  3. Hello, I checked the tutorials and read the pdf-s on the AXI Interrupt controller. However, i could use come clarification about a couple of things. In Microblaze advanced configuration there's an option to set interrupts to NONE/NORMAL/FAST, or leave it in AUTO mode. Is this setting linked to the AXI interrupt controller creation process? I mean if it run Block Automation, and enable Interrupt Controller, then AXI Interrupt Controller IP is created, but the setting doesn't change in the microblaze settings (for example it stays AUTO/NONE). Does that mean if i want a normal
  4. It might help someone, so i note that if the leds and buttons are connected to separate GPIO blocks, then Vitis generates the correct code for both. Based on the help above i managed to make it work from one dual GPIO.
  5. Hi, On my Arty A7 board i have the hello world running with Microblaze and UART. I added from the board tab the 4 buttons then i added the 4 LEDs. I'm using 2020.1, and by default it combined the AXI GPIO so there is a dual channel GPIO where both the leds and the buttons are connected. My problem is, that in Vitis the generated IO example code uses the same port, and only the buttons work... the device gets configured as such in the code: #define GPIO_OUTPUT_DEVICE_ID XPAR_GPIO_0_DEVICE_ID #define GPIO_INPUT_DEVICE_ID XPAR_GPIO_0_DEVICE_ID In xparameters.h i fou
  6. After poking around, i issued TCL command: write_xdc -file I2Cconst.xdc, and it generated a super xdc, and when searching through it i found this section: #################################################################################### # Constraints from file : 'I2COled_axi_iic_0_0_board.xdc' #################################################################################### #--------------------Physical Constraints----------------- current_instance -quiet set_property BOARD_PART_PIN i2c_scl_i [get_ports i2c_scl_io] set_property IOSTANDARD LVCMOS33 [get_ports i2c_
  7. Hi, I have an Arty A7 and using Vivado/Vitis 2019.2, installed BSP, and based on 'Arty - Getting Started with Microblaze', created my design, but added an I2C IP (besides the UART). In Vitis chose the example that tests the IP-s in the project. I got the I2C self test reporting success on UART to the serial console on the PC. The project didn't use constraints, there was no mention in the tutorial either. So my question is this: Where would i connect my external I2C device? And if i need to set it in constraints, how come the UART works 'out of the box' ? All advice appreciate