Hello Kees, something is always better than... nothing ;-) That's was exactly what I was looking for: a "working" driver for compare initialization sequence and register settings.
My init was very similar... but I noticed you deal also with interrupt registers and that you used the "FORCE" option in CH0CONF. This last one is the turnkey: simply adding the FORCE flag setting to my sequence, the SPI start workings properly, transmitting and receiving data as expected. Many thanks! Gianfranco On Thursday, November 19, 2015 at 4:50:58 PM UTC+1, Kees k wrote: > > I did some work on this in January. I am not sure it worked well, at least > it did something. > The code (so far) may help: > https://github.com/kkwekkeboom/am335x_pru_package/blob/csk_spidriver2/pru_sw/example_apps/PRU_spidriver/PRU_spidriver.p > > On Wednesday, November 18, 2015 at 2:15:31 PM UTC+1, Gianfranco Rosso > wrote: >> >> Hello Jason, thanks for advices. >> >> I've done the first and I've found a bug: just after soft resetting the >> module I have to rewrite register MCSPI_SYSCONFIG (to 0x0308) 'cause the >> module also resets this register... >> The others settings seems ok. >> SPI trasmission still doesn't occours, so there must be something else. >> >> I'll try the other 2 suggestions. >> >> On Tuesday, November 17, 2015 at 7:34:53 PM UTC+1, Jason Kridner wrote: >>> >>> Are you reading back all the registers to make sure all your writes work >>> OK? >>> >>> -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
