amurices

Members
  • Content Count

    5
  • Joined

  • Last visited

About amurices

  • Rank
    Newbie

Recent Profile Visitors

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

  1. I found the issue! It was that the interrupt port from the second device wasn't connected. I had to add a Concat IPCore to enable interrupts from both devices, and now everything is dandy. Seems like the spi-xilinx.c driver counts on that pin to probe the device correctly.
  2. I'm trying to set up two AXI Quad SPI IPCores as Masters to use with Linux on my MicroZed. I've been using a single interface, which works fine, by taking the M_AXI_GP0 interface, connecting it to an AXI Interconnect, and using that to connect to the IPCore. However, with two or more IPCores, I don't know how to get this to work. The block design of my attempt is below. But it just doesn't work. The device tree nodes for both devices look identical (apart from their addresses and the fact that the second one has a disconnected interrupt pin (which doesn't do anything in my case)), but whe
  3. @morsucci I'm using Petalinux, yeah. The problem went away by (seemingly) magic, however, and brought another problem in its stead. I now can't set the SPI frequency via the ioctl() call. Currently working on that by digging into the spi-xilinx.c driver, putting up printk() calls everywhere. The only way I can calibrate frequency is via regenerating the design and exporting it to Petalinux via Vivado. And anything above 20MHz incurs in data loss. But I'll update the forum on anything I find!
  4. Hi guys @Enrico and @sbobrowicz, I ran into an extremely similar issue, only I'm using a PL SPI interface instead of the PS. I posted the question here. I wonder if either of you guys have any insight on what might be causing this. It seems the solution to my issue is different, as there's nothing unusual about my SS. SS_IN doesn't seem to be floating; its pin is always plugged to the correct pin in the SAMA. I've been stuck on this all week. Hope you guys have any ideas.
  5. Hi all, I'm having an issue with the FPGA SPI interface I programmed onto my microzed. The issue is that the interface cannot read the data sent back from my slave device! I'm using a SAMA5d3-xplained devboard, and an oscilloscope to measure signals. I made the SAMA return the same buffer it received, only with every byte shifted. So it's a semi-loopback routine. The oscilloscope captures both the correct signal back from the SAMA (every byte divided by 2), AND the signal going into it (out of the MicroZed). However, the spidev_test.c (that seemingly famous SPI testing utility on the torv