In the examples in the SDK and the discussions in the forums related to running the host externally, they all point to using an RTOS on the external host. Our current platform in which we are trying to incorporate using the 14580 chipset via SPI, we do not use an RTOS. Is is possible to external host the BLE app without using an RTOS? Have there been previous examples posted of doing this that I have not come across?
If it is not possible then my only option is to run the application on the 14580, which I am fine with doing, and using the SPI_BOOTER code, I've been able to successfully transfer a hex file over to the 14580, but my question then that I am having a hard time understanding is how do I control the transfer of data from the 14580 back to the external CPU? In my case, I need to transfer a set of data from a standalone peripheral sensor via BLE to the device in question. From what I understand, in an externally hosted application, GTL commands are used to indicate the arrival of new data, and then it is processed by the externally hosted application. However if the application is hosted on the 14580, how does one transfer data from the 14580 application via SPI to the external CPU? In my situation, it seems redundant to have the BLE application on the 14580 because one still then needs and application on the external CPU to control the BLE stack. In that case I'm back to my original question of hosting the application on the external CPU in a NON RTOS environment.
Thanks for your help,
Hi medelman,
The only available example for an external MCU over GTL implementation is the proximity, monitor/reporter and it doesn't use RTOS. Also there is an application in the SDK that uses the spi interface, check the SDK5.0.3\DA1458x_SDK_5.0.3\DA1458x_SDK\5.0.3\projects\host_apps\da1458x\proximity\reporter for the application side and the SDK5.0.3\DA1458x_SDK_5.0.3\DA1458x_SDK\5.0.3\projects\target_apps\ble_examples\prox_reporter_ext_spi\Keil_5 for the host side.
Thanks MT_dialog