如何将固件下载到DA14580 BLE芯片

Hi,

Please verify that you have connected the UART as defined in Table 1, step 2,4,5, or 6 of UM-B-001http://support.dialog-seminile.com/resource/b-001-da14580-booting-serial-interfaces.。通过UART从外部源引导负载固件的标准方法是该文档中的ALO。如果您未在上面定义的UART连接，则唯一的选项是通过J-Link将辅助引导加载程序刻录到OTP中，这将允许您在DA14580上定义作为引导加载销的任何引脚组合。

The UART boot loader sequence is pretty straight forward. Your host needs to power on (or reset) the DA14580 and wait for it to transmit a STX (0x02) character. After this simply follow table 5 of the above referenced document.

Hi,

I'm also interesting in the alternative of flashing SPI flash (or event OTP) through Linux OS based environment.
It would be great that Dialog can provide such alternative.

To Shrimanth, from the example on github, it seems to use direct control to the SPI flash (not via DA14580) from host PC. But this is also kind of thought of flushing firmware while manufacturing.

Hi, Dialog team,

注意到了。

But I'm trying to implement 2 protocols for fulfilling my needs.
I suppose that 1) implementation of booting from serial interface (referring to 6.2 of AN-B-001) AND 2) SPI Flash command supported by 'flash_programmer' utility on target could be a try for my purpose.

从'programmer.c'的源代码出来的两个问题

Q＃1未定义Develope_Mode时，默认的“port_sel”是什么。
--
#ifdef USE_UART
#pragma arm section zidata =“non_init”
uint8_t gpio_port;// __attribute__ ((section ("non_init")));
uint8_t gpio_pin;// __attribute__ ((section ("non_init")));
uint8_t port_sel; // __attribute__（（部分（“non_init”）））;
#pragma arm section zidata
#else

.... <>

#ifdef DEVELOPMENT_MODE // To use the debugger, define it and set the UART_PIN_PAIR according to board configuration (periph_setup.h)
port_sel = UART_PIN_PAIR;
#endif
--

Q＃2“尺寸”是什么，我要为“action_spi_write”的第一个命令，我不太了解以下代码的目的，在an-b-001的第6.3节关于“代码的定义”第6.3节中定义的协议表7中的长度MS字节'和“代码长度LS字节”。

--
标题=尺寸+ 8;
if (starting_address==8)
{
标题缓冲器[6] =（无符号char）（0xff＆（标题>> 8））;
HeaderBuffer [7] =（无符号char）（0xff和标题）;
spi_flash_write_data(Headerbuffer, 0, 8);
spi_flash_write_data(p,starting_address, size);
}
--
else

嗨虾仁，

There is no other valid proper firmware. You have to download the bin file, not the .hex file. You can either compile the prod_test project and take the .bin file from the out directory or convert the .hex file to a .bin file.

谢谢mt_dialog.

嗨倒数，

- The SYS_CTRL_REG are the registers are controlled by the da if you are workiing with an external proccessor you can take a look at the reference design of the proximity monitor in the SDK at the following directory \DA1458x_SDK_5.0.2.1\DA1458x_SDK\5.0.2.1\projects\host_apps\windows\proximity\monitor you can check this alsohttp：//support.dialog-semicondiondiondum/resource/um-b-010-user-manual-pr ...。

- You can test your application in any application that supports BLE on android or LInux.

- 不，我不认为有这样的事情。

谢谢mt_dialog.

您好虾，请参阅DSP的用户指南：这包含所有详细信息。

http://support.dialog-semiconductor.com/resource/um-b-038-user-manual-di...

BR JE_DIALOG.

你好je_dialog，

我们正在研究I.MX6 SoloLote Android平台和Murata Lbca2hnzyz-711 BLE模块（基于对话框的DA14580 BLE芯片）通过UART接口。我们能够通过Android UI启用蓝牙时成功加载Prod_test.bin固件，但我们无法进一步继续。Logcat成功加载固件后显示以下消息。

I / BT_HCI_BDROID（3104）：内部BT_HC_WORKER_THREAD功能HC_EVENT_TX
E/bt_h4 ( 3104): [h4] Unknown HCI message type drop this byte 0x0
E/bt_h4 ( 3104): H4: Unable to acquire buffer for incoming HCI message.

Can you please help us to understand the probable cause of the above error. Do you have any Reference Android porting guide that describes the required changes/modifications to be done for porting BLE drivers.

Thanks & Regards
Raghu Chaitanya

嗨拉古基塔anya.l.

I suppose that the issue is that, if you are using 580, it does not support HCI commands, the 581 does.

谢谢mt_dialog.

你好mt_dialog，

Thanks for your reply. We are trying to integrate the (DA14580 based) Murata BLE module in Android 4.4 . In the DA14580x software architecture guide, it is mentioned that " The BLE core protocol stack is a third party implementation licensed from Riviera Waves " .

1) Does this mean that the BLE stack is already embedded inside the module ?
2) Can we use the Bluedroid stack ?
3) The serial port service application guide has the information only about flashing the firmware to the module. How do we proceed after loading the firmware to the module ?
4）您是否有任何介绍完整的集成程序的文档？

Please help . We are stuck up at this issue for almost two weeks.

Regards
Raghu Chaitanya

嗨拉古基塔anya.l.,

1) Yes the BLE is located in ROM.

2) About the Bluedroid the 580 doesn't support HCI commands the 581 does.

3) What do you mean how to proceed after loading the fw to the module, if you want to run the application you can donwload DSPS application and the data flowing from your pc to your android application.

4) There are docs explaining how to use the da580 with an external MCU please have a look in the documents section of the support site, but there isn't a doc about how to integrate the da with android.

谢谢mt_dialog.

你好mt_dialog，

Thanks for your prompt response. Can you please help me with the following ?

我们如何映射Android本机蓝牙应用程序（从Android设置 - >蓝牙（ON / OFF））到对话框14580芯片通信。由于Android本机蓝牙应用程序与Android蓝牙状态机进行通信，它与Android Bluedroid堆栈绑定，它使用Libbt HAL接口与UART接口进行通信。

蓝牙本机应用程序 - > Android蓝牙状态机 - > Android蓝牙堆栈 - > Libbt供应商 - > UART接口 - >蓝牙芯片固件。

- How DSPS apk communicates with Dialog Bluetooth application which internally communicates with Dialog Firmware.

Regards
Raghu Chaitanya

Hi raghuchaitanya,

Sorry, but there is no doc or example in doing what you are asking, you can have a look at the external proccessor configuration examples, also as i ve posted in my previous post the 580 doesn't support HCI only 581 does.

关于DSP的应用程序，它使用自定义配置文件将UART数据推入Android应用程序，Plase向DSPS应用笔记查看更多信息。此外，如果您有兴趣，我可以向您发送DSP的Android源代码。

谢谢mt_dialog.

你好mt_dialog，

Thank you. Yes, please send the android source code for the DSPS.apk.

Regards
Raghu Chaitanya

Hi raghuchaitanya,

Mail sent

谢谢mt_dialog.