My EE guesses you have a problem with something like CTS lines on the M4 to duvero serial bridge direction. Have not looked at the schematics or scoped it.
This is a lot more debug work than I wanted to do on a standard product.
MotionLABs LLC.
Post by Andrew C. SmithHi Glen,
Wow, I'm really sorry about the delay on this.
I have attached a couple programs.
spidev_test.c <http://gumstix.8.x6.nabble.com/file/n4971263/spidev_test.c>
spi_bridge_m4.cpp
<http://gumstix.8.x6.nabble.com/file/n4971263/spi_bridge_m4.cpp>
spidev_test.c uses the spidev driver on the COM to initiate the transfer and
send data.
spi_bridge_m4.cpp is a program that runs on the M4 to receive data and send
some back.
In this setup, the M4 is the slave and the COM is the master. Setting a SPI
to slave on the M4 requires recompiling your code and making some changes to
the kernel and some of the SPI config files. I've added a couple of patches
here. I wouldn't suggest applying the patches directly to your tree because
they're based off an old version of PX4 and NuttX. Use them to create your
own patches. Some stuff may not be necessary, this was just stuff I used
for testing.
0001-Added-SPI-slave-mode-support.patch
<http://gumstix.8.x6.nabble.com/file/n4971263/0001-Added-SPI-slave-mode-support.patch>
0001-Added-spi_bridge-module-which-will-eventually-ta.patch
<http://gumstix.8.x6.nabble.com/file/n4971263/0001-Added-spi_bridge-module-which-will-eventually-ta.patch>
Hope this helps,
Andrew
--
View this message in context: http://gumstix.8.x6.nabble.com/I2C-interface-as-bridge-between-Aero2Core-to-Duvero-tp4971217p4971263.html
Sent from the Gumstix mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
gumstix-users mailing list
https://lists.sourceforge.net/lists/listinfo/gumstix-users