亲爱的对话框，
我的应用程序必须执行600us的任务持续时间，以在给定频率为150Hz的频率下激活多个I / O.这些I / O的控制精度必须小于2美元。因此，在任务期间不会发生中断。此外，每个任务之间的时间的容差必须小于50us。任务之间没有什么可以做的，因此目前通过BLE Muss沟通。更多的是，BLE通信的持续时间不应该是长时间避免任何重载的下一个任务。
Is it possible to program the FreeRTOS in such a configuration?
（任务1）___________ble活动___________（task2）___________ble活动___________（任务3）___________ble活动___________等....
PYM
设备：
嗨pypuller，
关于你exet的BLE方案的一些事情，你不能指导在BLE通信发生时，你不能阻止服务BLE中断的系统（在BLE中丢失事件可能是非常关键的，因为失去事件它意味着失去了你连接）此外，50us还不足以使设备为服务提供BLE事件。这68倍通过单个CPU装备了BLE事件在特定时间片中应该发生，这不仅仅依赖于您的设备，而且还可以依赖于连接到您的对等设备，按顺序屏蔽BLE中断，按顺序优先考虑您的任务毁灭性的沟通。关于您要求的时间是非常差异的，如果不是不可能实现的，但应该有足够的信息有关任务切换以及释放RTOS如何将任务安排在可免费的RTOS文档中。
Thanks MT_dialog
亲爱的对话框，
感谢您的快速及时的反馈！:-)。让我问你有关你的答案的更多问题：
"you cannot instruct when the BLE communication will occur" -> in case BLE communication will occur during my not interrupted task, can I serve the BLE demand after my task?
“you cannot prevent the system of servicing a BLE interrupt” -> what is the maximum time before servicing a BLE interrupt?
“50us are not enough in order for the device to service a BLE event” -> what is the minimum BLE communication time duration? At the beginning of the program can’t we initialize a protocol with very short frame? At a very fast speed?
“BLE事件应在特定时间片中发生” - >在程序开头初始化特定时间片的定时持续时间？
“这不仅仅取决于您的设备，还不依赖于连接到您的对等设备” - >作为连接到我的设备的对等体是我自己的应用程序，我可以定义自己的BLE协议通信吗？
“应该有足够的信息有关任务切换以及Freertos如何安排Freertos文档中的任务” - > OK，请给我我应该阅读的最佳链接。
谢谢，Pym
嗨pypuller，
该设备将根据广告或连接间隔安排BLE事件，了解您应该可以的广告事件，您可以延迟甚至停止事件，但如果您因任务执行而松开事件，则在连接事件的情况下如果您继续丢失事件，那么有机会丢失连接，那么您不会能够建立或保持活动的连接。在两个设备交换其对连接的偏好之后，应决定连接间隔，因此当连接事件发生（BLE中断）并在事件前有多长时间时，它不固定，这取决于使用情况案例和建立的连接。
The way of servicing a BLE interrupt is quite complicated, since the interrupt will occur and the BLE manager task will take action in order to serve the interrupt and also schedule the upcomming events, so during the BLE event its not only your tasks that will take place but there should be also time for the BLE adapter and the BLE Manager and you cannot postpone those tasks since it will result in loosing events. Regarding the timimg and how much you can delay the execution of the BLE Adapter and the interrupt itself for service i dont have a number on that but there is no tollerance in that, as soon as the BLE interrupt occurs the ISR should be executed with no delay.
关于祝福事件的长度,这也depends on the event undirected advertising, non-connectable advertising, connection event (how long the connection event will be depending on the data that the device will have to carry to the other side), perhaps the statement "50 us are not enough for a BLE event to be served" isn't that proper since the device will just need to schedule the event and then the hw will serve the radio activity but 50us is very small in order for the BLE tasks to run. The bottom line is that the BLE has larger priority and by reducing that priority due to your tasks will result in unstable connections since you cannot predict what is exactly that will come from the protocol in order to keep your task's strict timing and also as mentioned above there are other tasks running from the SDK that will require processing during an event, you can't block those tasks, leaving a window of 50us for the BLE interrupts and BLE tasks to operate is not going to happen.
"The timing duration of theses specific time slices can't be initialized at the begging of the program" : I dont really get the question, the time duration of a BLE event depends on the kind of the event and on the data that the device will decide to send each time.
是的，如果您将拥有自定义应用程序，您可以只要想要设置连接间隔。
我可以分享没有具体的链接请查看免费的Rtos官方支持网站。
Thanks MT_dialog