Project

General

Profile

Activity

From 03/21/2017 to 04/19/2017

04/15/2017

JK 02:41 PM Software Development: RE: SPI Comm - can transmit data from Linux, but not receive
For completeness:
I think the reason U-boot wouldn't boot the device tree I attached for you is because it's too large for the ubootenv.bin you are using.
In uBootMMCEnv.txt (used to generate ubootenv.bin), loadkerneladdr needs to ...
Jared Kirschner

04/14/2017

DV 06:01 PM Software Development: RE: SPI Comm - can transmit data from Linux, but not receive
That's awesome to hear! Sorry for the bit of delay, I was working on packaging up my old build to send out to you guys.
Glad to hear you got it working.
Dan
Daniel Vincelette
JK 05:57 PM Software Development: RE: SPI Comm - can transmit data from Linux, but not receive
Update:
We got loopback working (so no longer need the FPGA project to compare with).
After regenerating our preloader, the loopback behavior changed, in that the operation hung rather than returning with an empty receive buffer.
...
Jared Kirschner
JK 05:04 PM Software Development: RE: SPI Comm - can transmit data from Linux, but not receive
Edit: I see the device tree source above, so the FPGA project is the only information we'd need. Jared Kirschner
JK 04:08 PM Software Development: RE: SPI Comm - can transmit data from Linux, but not receive
Hello Dan,
I'm back from vacation and looking into this again with my hardware engineer colleague. Our first attempt at regenerating the preloader based on our current FPGA image didn't result in working loopback communication, so we'...
Jared Kirschner

03/21/2017

DV 07:21 PM Software Development: RE: SPI Comm - can transmit data from Linux, but not receive
Im thinking it's related to the preloader. The preloader is the one who does all the pin muxing for the HPS peripherals (including muxing any of these interfaces to the FPGA). If any HPS peripheral or any of the bridges between HPS and F... Daniel Vincelette
JK 07:06 PM Software Development: RE: SPI Comm - can transmit data from Linux, but not receive
Hello Dan,
When re-building an SD card image using my kernel (uImage), the DTB you attached, and the FPGA image (.rbf), U Boot image, and preloader image you attached, I am able to see data in the receive buffer.
That suggests to m...
Jared Kirschner
DV 04:19 PM Software Development: RE: SPI Comm - can transmit data from Linux, but not receive
I've attached my preloader/uboot/fpga image.
I've also attached the spi_test c++ code I was working with, I've removed the chrono's part because I was having issues with getting to build with my toolchain (I'm not sure if it supports ...
Daniel Vincelette
JK 03:00 PM Software Development: RE: SPI Comm - can transmit data from Linux, but not receive
Hello Dan,
I replaced the uImage on my SD card (at /boot) with the uImage I sent you (to ensure it's the same as what you tested), and replaced the DTB with the DTB you attached (also in /boot).
I rebooted the card and ran the C++ ...
Jared Kirschner
DV 02:07 PM Software Development: RE: SPI Comm - can transmit data from Linux, but not receive
I've tried your kernel and the RX buffer is still working. I couldn't get uboot to actually boot your device-tree, I try rebuilding it and that didn't work either.
I've attached the dts/dtb I'm using.
Dan
Daniel Vincelette
DV 12:29 PM Software Development: RE: SPI Comm - can transmit data from Linux, but not receive
I've tried it with our 3.16 kernel and Altera's 4.1.22 and 4.1.22 RT kernel. All get data on the RX side. I'll try your kernel and device tree this morning and get back to you.
Dan
Daniel Vincelette
JK 12:26 PM Software Development: RE: SPI Comm - can transmit data from Linux, but not receive
Hello Dan,
I've attached the requested files (Linux 4.1.22 LTSI RT branch compiled into "uImage" with defconfig "socfpga_mitysom5csx_custom_defconfig", and the device tree binary and source files).
That you were able to get the exp...
Jared Kirschner
DV 12:41 AM Software Development: RE: SPI Comm - can transmit data from Linux, but not receive
Hi Jared,
Unluckily I wasn't able to recreate the issue you are seeing. My RX buffer has the expected 0x8330 instead of 0x0000 after running. Would you mind posting the following: uImage, DTB, and DTS?
I'll try to run with your uIm...
Daniel Vincelette
 

Also available in: Atom