Re: [beagleboard] SPI BBB Master, BBB Slave

On Mon, 4 Apr 2016 14:54:37 -0700, you wrote: >If you are using an SPI master, then what you say is correct, but if you are a >SPI slave, then some other device is controlling the clock, which means you >have to have data available before the clock starts. If there is no delay >between

Re: [beagleboard] SPI BBB Master, BBB Slave

> On Apr 4, 2016, at 4:56 PM, ybeag...@rehut.com wrote: > > On Monday, April 04, 2016 16:05:47 John Syne wrote: > >> Yeah, this is the approach used by the I2C Slave Framework. So >> traditionally, the McSPI driver registers with the SPI Framework as an SPI >> Master. Now through DT config, we

Re: [beagleboard] SPI BBB Master, BBB Slave

On Monday, April 04, 2016 16:05:47 John Syne wrote: > Yeah, this is the approach used by the I2C Slave Framework. So > traditionally, the McSPI driver registers with the SPI Framework as an SPI > Master. Now through DT config, we could have the McSPI driver register with > the SPI Framework as an

Re: [beagleboard] SPI BBB Master, BBB Slave

> On Apr 4, 2016, at 3:25 PM, ybeag...@rehut.com wrote: > > On Monday, April 04, 2016 13:13:48 John Syne wrote: >>> On Apr 4, 2016, at 12:49 PM, ybeag...@rehut.com wrote: >>> >>> On Monday, April 04, 2016 12:04:56 John Syne wrote: I’m not sure that is correct. The master will normally send

Re: [beagleboard] SPI BBB Master, BBB Slave

On Monday, April 04, 2016 13:13:48 John Syne wrote: > > On Apr 4, 2016, at 12:49 PM, ybeag...@rehut.com wrote: > > > > On Monday, April 04, 2016 12:04:56 John Syne wrote: > >> I’m not sure that is correct. The master will normally send a command and > >> then your slave driver will have to

Re: [beagleboard] SPI BBB Master, BBB Slave

> On Apr 4, 2016, at 2:42 PM, Harvey White wrote: > > On Mon, 4 Apr 2016 13:13:48 -0700, you wrote: > >> >> >>> On Apr 4, 2016, at 12:49 PM, ybeag...@rehut.com wrote: >>> >>> On Monday, April 04, 2016 12:04:56 John Syne wrote: I’m not sure that is correct. The

Re: [beagleboard] SPI BBB Master, BBB Slave

On Mon, 4 Apr 2016 13:13:48 -0700, you wrote: > > >> On Apr 4, 2016, at 12:49 PM, ybeag...@rehut.com wrote: >> >> On Monday, April 04, 2016 12:04:56 John Syne wrote: >>> I’m not sure that is correct. The master will normally send a command and >>> then your slave driver will have to respond with

Re: [beagleboard] SPI BBB Master, BBB Slave

> On Apr 4, 2016, at 12:49 PM, ybeag...@rehut.com wrote: > > On Monday, April 04, 2016 12:04:56 John Syne wrote: >> I’m not sure that is correct. The master will normally send a command and >> then your slave driver will have to respond with relevant packet. The >> protocol will have to be well

Re: [beagleboard] SPI BBB Master, BBB Slave

On Monday, April 04, 2016 12:04:56 John Syne wrote: > I’m not sure that is correct. The master will normally send a command and > then your slave driver will have to respond with relevant packet. The > protocol will have to be well defined. None of that is required by SPI (in the most basic form

Re: [beagleboard] SPI BBB Master, BBB Slave

I’m not sure that is correct. The master will normally send a command and then your slave driver will have to respond with relevant packet. The protocol will have to be well defined. However, you are correct that the SPI slave must be preconfigured and waiting for the master to start clocking

Re: [beagleboard] SPI BBB Master, BBB Slave

Getting it to work is not hard. (Had it working for a project.) To get to work reliably at a high clock rate requires debugging the DMA or working out a protocol where timing isn't as tricky. As a slave the master can start clocking at anytime and unless the FIFO (or DMA) is preloaded with the

Re: [beagleboard] SPI BBB Master, BBB Slave

> > *Thank you very much about clarifying this point !* > > *I don't think that I can allocate enough time to dive into what John > described - I assume that at some stage there will be such a driver or > other form of such support* > > *Thanks for now* > People have been discussing this since

Re: [beagleboard] SPI BBB Master, BBB Slave

Thank you very much about clarifying this point ! I don't think that I can allocate enough time to dive into what John described - I assume that at some stage there will be such a driver or other form of such support Thanks for now On Sun, Mar 27, 2016 at 11:29 PM, John Syne

Re: [beagleboard] SPI BBB Master, BBB Slave

The McSPI needs a driver and there is currently no Linux Driver that supports SPI slave mode. The current driver /drivers/spi/spi-omap2-mcspi.c does not support slave mode. The Linux kernel SPI framework uses spi-omap2-mcspi driver on TI processors. Regards, John > On Mar 27, 2016, at

Re: [beagleboard] SPI BBB Master, BBB Slave

I'd actually look into using the McSPI module. Which is hardware, and does support slave mode. On Sun, Mar 27, 2016 at 11:29 AM, John Syne wrote: > Ah, what you are trying to do cannot be done with the current SPI driver > because Linux SPI framework does not support SPI

Re: [beagleboard] SPI BBB Master, BBB Slave

John Hi, Thank you for coming back on this. I'm trying to connect 2 SPI busses on the BBB (HDMI disabled) and configure SPI1 as SPI slave so that I can sent messages from SPI0 to SPI1 - this allows me my application development and laterone I'll connect the respective SPI slave and master

Re: [beagleboard] SPI BBB Master, BBB Slave

What exactly are you trying to do? Please explain your application so that we can propose a solution. Regards, John > On Mar 23, 2016, at 4:29 AM, yaron.leder...@gmail.com wrote: > > Hi, > > Is there any resolution about this ? Since I'm having the same consideration > > Thanks ! > > >

Re: [beagleboard] SPI BBB Master, BBB Slave

Hi John, Yes I can use UART or other protocol to achieve same data communication. But I'm working for client . They should require spi slave in kernel. So struggling to get it up. We asked TI also regarding this but they also don't have any sample code for testing spi slave.. Regards Ravi On 5

Re: [beagleboard] SPI BBB Master, BBB Slave

Hi Ravi, This is something I’m currently working on. However, for your application, why do you need to use SPI? Surely you could use IP Sockets or UART to achieve the same thing. Also, McASP has both master and slave support through the sound subsystem. Specifically you can use

[beagleboard] SPI BBB Master, BBB Slave

I am having issues with SPI between two BBB that may be simple to solve. I have spidev_test loopback working on each board but am having problems connecting the two. spi0 master dts: 0x150 0x10 /* spi0_sclk, OUTPUT_PULLUP | MODE0 */ 0x154 0x30 /* spi0_d0,

[beagleboard] SPI BBB Master, BBB Slave

I am having issues with SPI between two BBB that may be simple to solve. I have spidev_test loopback working on each board but am having problems connecting the two. spi0 master dts: 0x150 0x10 /* spi0_sclk, OUTPUT_PULLUP | MODE0 */ 0x154 0x30 /* spi0_d0,