Activity
From 04/14/2017 to 05/13/2017
05/10/2017
- DV 03:27 PM Software Development: RE: Altera spi
- Brian,
Would you mind posting your updated spi_test.c? I'll see if I can recreate what you're seeing on my dev kit.
Thanks,
Dan
05/09/2017
- BW 06:46 PM Software Development: RE: Altera spi
- Thanks Dan,
This cleared up the errors on the DTB. I have tried to run the spi_test.c provided in a different post and still get the Unable to handle kernel NULL pointer dereference at virtual address 00000000. I'm not sure if it's a pr...
05/08/2017
- DV 06:18 PM Software Development: RE: Altera spi
- Hi Brian,
Sorry you'll also have to set #size-cells to 0x0 for the altera spi driver nodes, this info was taken from here: https://support.criticallink.com/gitweb/?p=linux-socfpga.git;a=blob;f=Documentation/devicetree/bindings/spi/spi... - BW 05:11 PM Software Development: RE: Altera spi
- I'm still getting the same error.
- DV 04:57 PM Software Development: RE: Altera spi
- Hi Brain,
Sorry for the delay. Looking at the warnings you're getting from the critical link toolchain you need to set the #address-cells to 1.
For example: - BW 01:24 PM Software Development: RE: Altera spi
- I was able to comply the DTB using a tool chain from rocketboards and a spi device showed up under /dev/spidev. Writing to this device crashes Linux and gives me the following error:
Unable to handle kernel NULL pointer dereference at v...
05/02/2017
- BW 07:59 PM Software Development: RE: Altera spi
- Thanks for the reply. I have updated the dts and I'm getting the following warnings:
Warning (reg_format): "reg" property in /soc/bus@0ff200000/spi@0x0060/device@0 has invalid length (4 bytes) (#address-cells == 2, #size-cells == 0)
... - MW 02:54 PM Software Development: RE: Altera spi
- Hi Brian,
Are you trying to use the device from user space with the spidev driver? If so, then you need to fix the device tree to use:
05/01/2017
- I am trying to use an altera spi as a master. I have enabled the driver in the kernel and added the device to the DTB. No spi devices show up under /dev. I have been looking into using to the sysfs interface but I'm not sure if this is t...
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 ...
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 - 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.
... - 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.
- 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'...