Other Parts Discussed in Thread: TMS320F28069M, LAUNCHXL-F280049C, BOOSTXL-DRV8320RS
I'm trying to figure out the role of SPI communications between the LaunchPadXL TMS320F28069M and the BOOSTXL-DRV8305EVM before messing about with it. My aim is to use a Raspberry Pi to communicate via SPI to the LaunchPad, so that I can send some of my own data across and use it for plotting/analysing long datasets more easily and also in real-time (the LaunchPad will be connected to the R-Pi, which is connected and run via Matlab on my laptop).
I've successfully run dummy code for sending/receiving data between just the LaunchPad and the R-Pi using SPI (SPIa), and now I want to do the same for when the BOOSTXL-DRV8305EVM is also connected. I guess my problem is, I'm a bit unsure of the role the SPI connection has between the LaunchPad and the BOOSTXL. I've based my InstaSPIN code around tutorial lab 11a and stripped it right back to what I found relevant. I noticed the following lines in the main function of the code:
#ifdef DRV8305_SPI HAL_writeDrvData(halHandle,&gDrvSpi8305Vars); HAL_readDrvData(halHandle,&gDrvSpi8305Vars); #endif
so I thought I'd assess what's going on at the SPIa lines of the board using an oscilloscope, but there's nothing being sent. Will I be able to just program and use SPIa as I have done before, or does this play a large role in communications between the LaunchPad and BOOSTXL? I find the hal environment pretty confusing to decipher, but from what I can see both SPI handles get initialised and remain unchanged throughout.
Cheers in advance,