The DA14531 SmartBond TINY™ Module is the Bluetooth® low energy solution that will power the next 1 billion IoT devices through ease of use.
DA14531 SmartBond Tiny™模块基于世界上最小和最低功率的蓝牙5.1系统,为集成模块带来DA14531 SOC优势。它只需要电源和印刷电路板来构建蓝牙应用。
The module is targeting broad market use and will be certified across regions providing significant savings in development cost and time-to-market.
It comes with an integrated antenna and easy to use software making Bluetooth low energy development easier than ever before.
这种令人敬畏的组合将移动连接到以前遥不可及的应用程序,启用下亿个物联网设备,智能字体TINY™核心。雷竞技安卓下载
特征
Bluetooth 5.1 core qualified
集成天线
全球认证
Cortex-M0+ @16MHz
iotmark™-ble得分为18300
23.75UA / MHz MCU电流
Memory: 48kB RAM, 32kB OTP &1Mb FLASH
1.8-3.3V供电范围
+2.2dBM max output power
-93dBm敏感性
RX电流2mA在3V时
Tx current 4mA at 3V at 0dBm
接口:2xuart,SPI,I2C
4通道10位ADC
8 GPIO
Built-in temperature sensor
工作温度:-40°C至+ 85°C
Dimensions: 12.5x14.5x2.8 mm
雷竞技安卓下载
Beacons
遥控器
近距离标签
玩具
低功率传感器
Bluetooth LE add-on “pipe” to existing applications
提供任何类型的设备,提供易于使用的基于智能手机应用程序的设置和控制,无需打印的用户手册
Related Links
DA14531 Block Diagram
每季度,我们都会为我们的产品,软件开发主题,培训,活动提供最佳技术信息,并将其交给您的收件箱。雷电竞官网登录
保持联系
通过我们的全球销售办事处直接与我们联系,或联系我们的全球经销商和代表之一。
询问 Distributors and Representatives Register for newsletters订购信息
DA14531 Smartbond TinyModule
- 部件号:DA14531MOD-00F01002
- Size (mm): 12.5x14.5x2.8
- 装运包数量:卷轴1k
蓝牙低在ergy Development Kit Pro for DA14531
- Part number: DA14531MOD-00DEVKT-P
- 描述:开发套件基于模块样本
专业发展套装的子板
- 部件号:DA14531MOD-00F1DB-P.
- 描述:DA14531 Pro开发套件的模块子板
- SmartBond TINY Module: Includes motherboard, daughterboard and cables; Primary usage is SW application development and power measurements
SmartBond TINY Module: Includes motherboard, daughterboard and cables;
主要用法是SW应用程序开发和功率测量
1个月前
Sleep interfering with UART write
张贴了单自然打击210 points 3回复I have a timer callback in which I write a short string out of the UART. I can see the output in a putty, but the string is truncated after a few characters, which I guess is due to the device going back to sleep.
控制这个的正确方法是什么?我想完成写字符串,然后允许设备睡觉。我想我可以使用UART TX回调作为其中的一部分,没有发现没有关于告诉SDK保持活动的信息。
1个月前
This is not for debugging but (eventually) for comms. The device has another microprocessor on board which is connected to UART2. I'm just trying to understand the UART driver at the moment. The following code is a representative extract.
// Called during startup void start(void) { app_easy_timer(LED_TIMER_VAL, timer_cb); } // Just a test #define LONG_MSG "The cat sat on the mat dreaming of this and that little mouse related thing" static void timer_cb(void) { app_easy_timer(LED_TIMER_VAL, timer_cb); pic_uart_send(LONG_MSG); } void pic_uart_send(const char* message) { // Attempt to stall sleeping while the message is sent arch_force_active_mode(); uart_register_tx_cb(PIC_UART, pic_uart_send_cb); uart_send(PIC_UART, (uint8_t*)message, strlen(message), UART_OP_INTR); } static void pic_uart_send_cb(uint16_t length) { // Allow sleeping now that the message is done. // This does not work because the TX FIFO contains the last block // of the message when the callback is called. arch_restore_sleep_mode(); }
这就是我的腻子:
“猫坐在席子上梦想着这个,那个小鼠相关的猫坐在席子上梦想着这个,那小鼠标相关的猫坐在席子上梦想着这个,那个小鼠标相关的猫坐在席子上梦见这个和那个小鼠标相关的猫坐在席子上梦想着这个,这只小的老鼠与猫坐在席子上梦想着这个,那几点鼠标相关的魔杖。
我看着UART驱动程序ISR,因为它看起来像回调在邮件的最后一个块被推入FIFO后立即调用。我可以解决这个问题,但是想知道是否有更好的方法。
I also looked at arch_console.c - I note that the TX callback in that code uses the same method I have tried, but explicitly blocks while the FIFO is not empty. I guess that works, but I prefer my code to never block.
我正在使用SDK 6.0.14.1114。我可以建议以下修改的UART_TX_ISR()吗?这允许在FIFO最终空之后发生一个发生的中断。只有这样它只会禁用中断并调用回调函数。我尝试过各种弦长度,在FIFO大小或附近,似乎做正确的事情。
static void uart_tx_isr(uart_t *uart_id) { uart_env_t *uart_env = UART_ENV(uart_id); // Condition to block callback until the FIFO is empty if (uart_env->tx_index < uart_env->tx_total_length) { // While there is available space, put data in thr_reg or FIFO while (uart_env->tx_index < uart_env->tx_total_length) { // If FIFO is enabled, exit if it is full if (uart_fifo_enabled_getf(uart_id)) { if(!uart_txfifo_not_full_getf(uart_id)) { return; } } // Else, exit if THR is full else if (!uart_thr_empty_getf(uart_id)) { return; } // Send one byte uart_thr_setf(uart_id, uart_env->tx_buffer[uart_env->tx_index++]); } return; } // Everything was sent // Disable TX interrupts uart_txdata_intr_setf(uart_id, UART_BIT_DIS); uart_thre_intr_setf(uart_id, UART_BIT_DIS); // Fire callback if (uart_env->tx_cb != NULL) { uart_env->tx_cb(uart_env->tx_total_length); } }
1个月前
Hi UnicycleBloke,
谢谢你的问题。Can you please share the code snippet you are using, so that we can replicate this issue?
Additionally, which SDK example you are using?
When the device is configured to extended sleep mode, then it will sleep between advertising or connection intervals. During sleep, all the peripheral domains (including UART) are powered-down, so you will able to have UART activity.
If the sleep mode is disabled, can you reproduce this issue?
If you are using the UART to print out some debugging information, the arch_puts() or arch_printf() can be also used.
http://lpccs-docs.dialog-semiconductor.com/Tutorial_SDK6/serial_port.html
Thanks, PM_Dialog