How to download Firmware to DA14580 BLE chip

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-semiconductor.com/resource/b-001-da14580-booting-serial-interfaces.The standard way to boot load firmware from an external source via UART is alo described in that document. If you have not connected the UART as defined above, your only option is to burn a secondary boot-loader into OTP via J-Link, which would allow you to define any pin combination on the DA14580 as boot loader pins.

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,

Well noted.

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.

Two question out from source code of 'programmer.c'

Q#1 what would be the default 'port_sel' when DEVELOPMENT_MODE is not defined.
--
#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__ ((section ("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 What the 'size' shall I put for the first command of 'ACTION_SPI_WRITE', I don't quite understand the purpose of following code with protocol defined at section 6.3 of AN-B-001 regarding to the definition of 'Code length MS byte' and 'Code length LS byte' in table 7.

--
headersize = size+8;
if (starting_address==8)
{
Headerbuffer[6]= (unsigned char) (0xfF&(headersize>>8));
Headerbuffer[7]= (unsigned char)(0xfF&headersize);
spi_flash_write_data(Headerbuffer, 0, 8);
spi_flash_write_data(p,starting_address, size);
}
--
else

Hi shrimanth ramesh,

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.

Thanks MT_dialog

Hi remesh,

-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-semiconductor.com/resource/um-b-010-user-manual-pr....

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

-No i dont think there is such thing.

Thanks MT_dialog

Hello Shrimanth, please see the user guide for DSPS : this contains all the details.

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

BR JE_Dialog

Hello JE_Dialog,

We are working on i.MX6 Sololote Android platform and the MURATA LBCA2HNZYZ-711 BLE module(based on Dialog's DA14580 BLE chip ) is interfaced via UART. We are able to load the prod_test.bin firmware successfully when the Bluetooth is enabled through the Android UI, but we are unable to proceed further. The logcat shows the following messages after the firmware is loaded successfully.

I/bt_hci_bdroid( 3104): Inside bt_hc_worker_thread function 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

Hi raghuchaitanya.l

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

Thanks MT_dialog

Hello 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) Do you have any document that explains the complete integration procedure?

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

Regards
Raghu Chaitanya

Hi raghuchaitanya.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.

Thanks MT_dialog

Hello MT_Dialog,

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

How we can map the Android Native Bluetooth Application (From Android Settings -> Bluetooth(ON/OFF)) to Dialog 14580 chip communication. Because Android Native Bluetooth App communicates with Android Bluetooth state Machine, which bind with Android Bluedroid stack which uses libbt HAL interface to communicate with UART interface.

Bluetooth Native App -> Android Bluetooth State Machine -> Android Bluetooth Stack -> Libbt Vendor -> UART interface - > Bluetooth Chip Firmware.

-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.

About the dsps the application, it uses a custom profile to push uart data into the android application, plase have a look to the DSPS application note for more info on this. Also, if you are interested i can sent you the android source code for the DSPS.

Thanks MT_dialog

Hello MT_Dialog,

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

Regards
Raghu Chaitanya

Hi raghuchaitanya,

Mail sent

Thanks MT_dialog