Hi all,
frist of all: my goal is to get the the host application of the external proximity reporter app (projects\host_apps\da1458x\proximity\reporter) running on an MSP430.
In order to accomplish that, I am trying to "port" the project to Code Composer Studio (CCS). My initial thought was to just create a clean project in CCS and add the source and header files of the Keil project and replace the device-specific drivers (such as SPI). My problem is that I'm not able to get the project running, since CCS doesn't have access to the DA14580 SDK. (app.c, app_task.c, ble_msg.c, .... all include files from the SDK.) Is it correct that the project needs access to the SDK? How do I accomplish that?
I imagine I am not the first one trying to get the proximity reporter running on an MSP430. Is there a how-to guide for that problem? I tried to work with UM-B-010 and UM-B-013, but I didn't find them very useful, since they're just explaining the scenario in which the host application runs on a DA1458x.
感谢您的帮助！
Let me refine my question. In the attached screenshot you can see the basic architecture for a external processor configuration, as described in various Dialog user manuals. Generally speaking, I don't know what part of the proximity reporter app is part of the "host application" (green box in screenshot), and how to connect the host application to the rest of the platform.
What I need to know is:
1. Which header/source files of the proximity reporter app are part of the "host application"?
2. Which parts of the DA14580 sdk do those files (the host application) need to compile? (the sdk is structured into 'app_modules', 'ble_stack', 'common_project_files' and 'platform'. Can I just delete the 'platform' part from the project?)
3.“主机应用程序”与其余系统的接口是什么？如何将主机应用程序连接到MSP平台？我正在寻找主机应用程序功能的简明列表，这些功能需要连接到平台。
提前谢谢!
嗨，马勃伦，
The proximity application in external proccessor configuration executes in combination with the windows reporter application located in the SDK/projects/host_apps/windows/proximity/reporter there you can find all the nessecary headers and source files that are used in order to create your custom external host. The user_platform should be there in order to setup the UART and communicate with the extrernal host. The external application with the 580 communicates through UART over GTL, please check the UM-B-010 proximity application for more info on this.
谢谢你的对话
Hi MT_dialog,
thanks for your reply. So from what I understand, the SDK provides two different examples for the proximity reporter in external processor configuration:
1.windows应用程序（SDK/projects/host\u apps/windows/proximity/reporter），打算通过UART与DA14580连接。
2.在SDK\projects\host\u apps\da1458x\appricity\reporter下找到的项目。在这种情况下，两个DA14580通过SPI连接；一个DA14580是外部微控制器的角色，另一个DA14580是BLE收音机的角色。此安装不需要Windows应用程序。
Can you confirm this?
My intention is to connect my DA14580 to the external microcontroller via SPI, thus I'm trying to use example #2 (SDK\projects\host_apps\da1458x\proximity\reporter) as a reference, and not the windows application.
Hope that makes sense.
干杯，
马勃朗
Edit: I'm only talking about the proximity REPORTER here. I'm aware that an additional DA14580 is needed for the proximity monitor.
嗨，马勃伦，
Yes that right, you can use two 580s (one has the external application and the other the stack) and interract with each other over GTL via SPI you can find more info about this in the UM-B-013.
谢谢你的对话
Hi MT_dialog,
thanks for the clarification. So that means that in the project "SDK\projects\host_apps\da1458x\proximity\reporter", the GTL layer corresponds to "spi_hci_msg.c". However, the file name "spi_hci_msg.c" suggests that the HCI interface is being used here. Also, all the comments in that file suggest the same thing. Is the used protocol really GTL in that example? Why all the talking about HCI? From what I understand there's a significant difference between the two interfaces (at least from a protocol-stack point-of-view).
谢谢，
马勃朗
嗨，马勃伦，
The 580 doesn't fully support the all the commands from of the HCI interface so the commands are over GTL.
谢谢你的对话
Hi MT_dialog,
thanks for your help, I finally got the project running! :)
I have one more question. Related to my problem described here (http://support.dialog-semiconductor.com/spi-slave-mode-not-working#comme...), I had to clear the SPI_EN_CTRL bit in SPI_CTRL_REG during SPI initialization in spi_hci_slave_init(). Otherwise the SPI connection would not be stable.
Are there any consequences of disabling SPI_EN_CTRL in the "projects\target_apps\ble_examples\prox_reporter_ext_spi" project?
谢谢，
马勃朗
Hi mabraun
也许您的线路有点嘈杂，这就是为什么禁用SPI时，您得到的数据没有错误。如果在MSB位和LSB位之间禁用SPI，则I/O缓冲区将重置并进入空闲状态。SPI被激活是件好事，它应该在一条清晰的线中保护无效的数据。
谢谢你的对话