Hi,
We are working to custom board based on DA14682. We are trying to flash bootloader but we are unable to flash, getting error -203. Logs attached.
Please help in this regard.
Thanks and Regards
Raj Johri
Hi,
We are planning to use Murata ZY Module in our design. The following are the functionalities we require -
1. BLE Beacon Detection
2. OTA update for the Host Controller and the Murata ZY Module itself.
My question is -
1. Does the CodeLess AT Command solution for DA14580 support the above functionalities? Does it have a Bootloader? If not is there any other solutions available?
2. My understanding is that in case we are using the CodeLess AT Command solution and we implement some application on Top of it, this code will reside in the ROM. What is the Use of OTP?
3. I also saw use of external Flash to store the application code - what would be the use case for this?
Hi,
I am trying to use the DA14580 factory delivered bootloader to load in my code (a slightly modified DSPS central), and I "almost" succeed...
Using the DA14580_CB_PXI_QFN48 module on a Development Kit Expert, I have tested that the Keil Project and its generated hex file works
as intended in every way.
I am now powering up an unprogrammed DA14580 (the setup from above), connecting a UART to GPIOA.4 and GPIOA.5 and communicate
with the DA14580 during its bootloading sequence. Following the application note AN-B-001, I can see the STX = 0x02 on the UART,
and I reply with SOH = 0x01, LEN_LSB = 0x00, LEN_MSB = 0x40. I then get ACK = 0x06 and I start shooting code bytes to the DA14580.
However, I do not get a consistent CRC back, and if I give the last ACK = 0x06 nothing happens
Actually, looking at the UART pins with an oscilloscope reveals that the GPIOA.4, DA14580 UART TX is being released and becomes floating
somewhere during the code bytes transmission.
One thing I am a bit unsure of is the hex file conversion into code bytes. I have written a C# program that converts the sps_host.hex
into a C header file with a const uint8_t thecode[16000] array. The one thing I was not sure how to handle was that in the hex file there
are some gaps; ie the intel hex file format specifies the start address for each line of 16 code bytes. But my sps_host.hex file has 4 regions of code, with 3
chunks of empty space of various length between them. Using SmartSnippets Toolbox's OTP Image tool, I load the sps_host.hex file and can see how the
empty spaces are represented by "--" symbols in the Hex field. In my conversion program I simply filled these bytes with "0" (zeroes).
Also, the sps_host.hex file contains 15360 bytes, whereas my program pads with zeroes up to a total length of 16000 bytes.
I feel very stuck, and would appreciate some hint what direction to run?
BR
Roger
1、参照SDK例程修改bootloader程序，实现固件升级、转移、跳转至应用程序等功能，通过调大MTU固件升级速度约为3kb/s；
2、参照SDK例程修改应用程序，FLASH偏移地址0x01E000，固件升级速度却只有1kb/s左右（若升级过程中不执行FLASH读写操作，速度约为1.3kb/s），且读写FLASH操作明显变慢；
3、若不使用bootloader程序，只使用应用程序（FLASH便宜地址改为0），则固件升级速度正常，FLASH读写速度正常；
4、应用程序执行完固件升级后，重启由bootloader转移固件程序存储位置时，有时需要10秒左右，有时只需1秒左右，固件大小约110k。
我的boot loader完全按照SDK例程修改，但仍出现上述情况，不知是那里设置有问题，望帮忙解答。
谢谢~
Dear Dialog,
We are working on a prototype with DA14850, with connections to i2c slaves and spi flash for the application,
after power up there is a lot of activity on the pins, I expect that some rom code is running.
Once we have a bootloader in the OTP,would this be still running? Toggling in the pins might disturb the other connected
IC's, corrupt flash etc.
After OTP programming would we still be able to connect with the debugger?
Is there a DFU bootloader available in the ROM which can be accessed via the UART lines?
Thank you in advance,
Best regards,
Laszlo
According to UM-B-012 DA14580 Creation of a secondary boot loader, my application can be booted successfullly when second bootloader burned into OTP. but When second bootloader was burned into external spi flash(address offset 0x0), It can not boot my application. I don't know why?