< div class = "字段field-name-taxonomy-forums field-type-taxonomy-term-reference field-label-above”> < div class = "字段标签" >论坛:,< / div > < div class = "字段条目" > < div class =”field-item甚至“rel = " sioc: has_container " > < a href = " /论坛/ dialog-smartbond-bluetooth-low-energy - % E2 % 80% 93 -软件”“=“sioc:容器sioc:论坛”属性=“rdfs: label skos: prefLabel”数据类型= " " >对话框Smartbond蓝牙低能量——软件< / > < / div > < / div > < / div > < div class =”字段field-name-body field-type-text-with-summary field-label-hidden”> < div class = "字段条目" > < div class =”field-item甚至“财产= "内容:编码" > < p >亲爱的支持,< / p > < p >目前我实现GTL接口(UART)在一个定制的嵌入式项目。我的第一个目标是让prox_reporter_ext项目工作结合我们的外部处理器(DA1458x_SDK \ 5.0.2.1 \ \ target_apps \ ble_examples项目文件夹)。我用host_proxr_sdk项目作为参考(DA1458x_SDK \ 5.0.2.1 \ host_apps \ windows \ \项目邻近\记者\文件夹)。< / p > < p >我面临的挑战是内存分配。直到现在我们都避免使用malloc / free嵌入代码,只是为了防止引入灾难性的副作用,比如内存泄漏(也可能会带来新的挑战与我们的RTOS)。在ble_msg malloc和free的上述项目,我看到通过使用例如BleMsgAlloc BleFreeMsg, uart.c SendToMain也是一样。此外UARTProc的接收缓冲区(uart.c)的大小是1000字节,MAX_PACKET_LENGTH是350字节(uart.h)。另一个500字节分配UARTSend (uart.c)。< / p > < p >从我理解的来源和阅读嗯- b - 017 GTL界面集成的流程应用程序。pdf和嗯- b - 010 - _da14580_581_583接近application_v1.3。pdf, GTL接口不能归类为停止前进,等待风暴过去协议。换句话说,多个事件包/由DA14580可以将消息发送到外部处理器在任何给定的时刻。 On the other hand the external processor can send a command packet / message whenever required by the application. I fully understand the reason for using dynamic memory allocation, it makes sense with a variable number of packets and a variable PAR_LEN field value. However I would like to know if static memory allocation is a viable option (and achievable looking at memory requirements). In this case I would like to know what the max value for PAR_LEN is (the maximum number of bytes of Parameters that a message can contain) and how many packets / messages could potentially be sent by the DA14580. If feasible, I could create a circular buffer of X number of packets, each with MAX_PAR_LEN bytes of Parameters (we have 32kB of RAM available in total, so for example 3 packets of each 350 bytes with a separate read buffer of 350 bytes and a write buffer of 350 bytes (for asynchronous reading/writing) is not very realistic).
I would love to hear your thoughts on this. If at all possible, I would rather not use malloc / free.
Kind regards,
Arjan
Edit 02-11-2015
I have added information regarding endianness and data structure padding below, perhaps other forum users might find this useful as well.