LPSPI FreeRTOS Initialization Only for Master?

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

LPSPI FreeRTOS Initialization Only for Master?

ソリューションへジャンプ
1,074件の閲覧回数
nbgatgi
Contributor IV

Within the MCUXpresso SDK, the non-RTOS initialization drivers for LPSPI include "LPSPI_MasterInit" and "LPSPI_SlaveInit".  When FreeRTOS is included, the associated RTOS driver is "LPSPI_RTOS_Init" which I initially presumed would have parameters for master or slave, but that doesn't appear to be the case.  Within LPSPI_RTOS_Init, LPSPI_MasterInit is called, but LPSPI_SlaveInit is not.  In fact, in the file "fsl_lpspi_freertos.c" there is no reference to the word "slave" at all!

When looking at the LPSPI / FreeRTOS example code (not available in the SDK for the RT1060 and RT1064), the FreeRTOS slave task initializes directly with "LPSPI_SlaveInit".

Why is their only a master LPSPI initialization function for FreeRTOS?

ラベル(1)
0 件の賞賛
1 解決策
866件の閲覧回数
danielchen
NXP TechSupport
NXP TechSupport

Hi Nick:

Currently we do not plan to prepare FreeRTOS SPI slave driver. We have created initial set of drivers and we decided that Baremetal ISR api is most appropriate for use.

SPI slave is usually implementing custom protocol, where number of transferred bytes depends on payload (command) sent, most of such processing should be done directly in the ISR.

Regards

Daniel

元の投稿で解決策を見る

0 件の賞賛
1 返信
867件の閲覧回数
danielchen
NXP TechSupport
NXP TechSupport

Hi Nick:

Currently we do not plan to prepare FreeRTOS SPI slave driver. We have created initial set of drivers and we decided that Baremetal ISR api is most appropriate for use.

SPI slave is usually implementing custom protocol, where number of transferred bytes depends on payload (command) sent, most of such processing should be done directly in the ISR.

Regards

Daniel

0 件の賞賛