Hi all,
I am trying to realize OTA on DA14583,and generate fw_1.img,fw_2.img,multi_part.bin as the "AN-B-10" stated step by step.But,after I burning the
multi_part.bin into DA14583 internal flash. It does not advertise(Only burnning fw_1.bin or fw_2.bin,DA14583 works fine).I have enabled SPI_FLASH_SUPPORTED
& SUPPORT_AN_B_001 in the boot_loader.h. When burn the flash, both "YES" and "NO" are tried when asked by the Smartsniper.
For DA14583,What else need I do?
Device:
I have figured it out,because the second bootloader project did not defeine the __DA14583__,so the SPI IO confiuer is not right！
May I request you to send the SUOTA source code for Andriod and IOS? I want to realize the OTA function in our app.thanks, may e-mail iskb502zjh@163.com.
Hi birenpeter,
Thanks for the indication, i can only send a mail to the registered email account and not to the one you are indicating, if your info are changed please correct your mail in your dialog account.
Thanks MT_dialog
The registered email is still in use,please send to my account email.Bye the way,please let me know what IDE and IDE version is used to develop the app.Thanks!
Hi,
We are also trying to realize SUOTA in our device using 14583.
Is the source code directly available somewhere or can you please send me the source-code for the app side?
Thanks,
Mutahir
Hi birenpeter,
A mail has been sent to the registered email account, regarding the IDE that is used for the Smart phone applications is the Android studio for android and Xcode for the iOS regarding the versions i dont think that really matter but its 1.5.1 for android studio and 7.3.1 for xcode.
Thanks MT_dialog
Many thanks!
Hi,
I replied the E-mail with "I accept the terms and conditions of this SLA",but have not received the source code yet.Can you kindly help me to check what is wrong?
Hi guys,
I tried to use 14583 as well but cannot make it working with dual image mode so far - on pro kit.
My understanding is that if you use DA14583, given you want to user internal FLASH, you keep the Jumper J6 to the UART side, right? Otherwise I would think the external & internal SPI flash will have conflict?
The other question is the boot loader working mode, 14583 has already got boot loader burnt in OTP, so the secondary boot loader mentioned here must reside in the internal flash for 14583? Hence it is using the SUOTA scheme 1, i.e., using the following command to generate the multi_part.bin:
mkimage.exe多spi secondary_bootloader.bin fw_1.img 0x8000 fw_2.img 0x13000 0x1F000 multi_part.bin
here is the boot_loader.h
************** Encrypted Image Support section**************/
#define AES_ENCRYPTED_IMAGE_SUPPORTED 1
#undef AES_ENCRYPTED_IMAGE_SUPPORTED
/************** UART Booter section**************/
#undef UART_SUPPORTED
/************** Flash memory section **************/
#define SPI_FLASH_SUPPORTED
#undef EEPROM_FLASH_SUPPORTED
#if defined (SPI_FLASH_SUPPORTED ) && defined ( EEPROM_FLASH_SUPPORTED )
#error "Both SPI_FLASH_SUPPORTED and EEPROM_FLASH_SUPPORTED configuration flags are defined."
#endif
/************** AN-B-001 based image /fast bootloader section **************/
// Define it if
// if AN-B-001 based image is burned in SPI flash and the bootloader is running from the OTP
#undef SUPPORT_AN_B_001 //Enable it for the secondary bootloader
#define SUPPORT_AN_B_001 //Enable it for the secondary bootloader
// Define ALLOW_NO_HEADER to enable loading 0x7f00 bytes from memory offset 0
// in case no valid AN-B-001 header is found.
#define ALLOW_NO_HEADER
#if defined (SUPPORT_AN_B_001) && AES_ENCRYPTED_IMAGE_SUPPORTED == 1
#warning "Encryption is not supported by the secondary bootloader"
#endif
#define AN001_SPI_HEADER_SIZE 8
#define AN001_SPI_STARTCODE_POSITION 8
#define AN001_EEPROM_HEADER_SIZE 8
#define AN001_EEPROM_STARTCODE_POSITION 32
Bides, I'm puzzled by the comment in UM-B-012, page 10, paragraph 3:
"The secondary bootloader application is configured to operate in dual image mode by undefining the
option SUPPORT_AN_B_001 in the header file bootloader.h."
We are using dual image mode here and trying to define SUPPORT_AN_B_001, is it something wrong?
Thanks,
uta_lc
Hi uta_lc,
The SUOTA application on the 583 uses the internal flash and the pins for the external flash are tottally different (P20/P23/P24/P29 and the external is P00/P03/P05/P06). Regarding the bootloader, you are right, the secondary bootloader should reside in the FLASH. The secondary bootloader should have the define __14583__ in order for the pins to be set correctly and if you are using encryption you should use the appropriate command in order to encrypt your image when creating it, please check the secondary bootloader document UM-B-012 in appendix A to see how to use the mkimage with encryption. The secondary bootloader as is, has the SUPPORT_AN_B_001 definition undefined so it operates as a dual image bootloader for the SUOTA why you want to define it since you want to use dual image functionallity?
Thanks MT_dialog
Thanks MT for the feedback.
Yes, by using the "#undef SUPPORT_AN_B__001" line I got it working.
As to why I tried to define the "SUPPORT_AN_B__001", see the first post of this thread "I have enabled SPI_FLASH_SUPPORTED & SUPPORT_AN_B_001 in the boot_loader.h.". and the whole context gave me the impression that I need to define the macro.
Hi uta_lc,
为了澄清,你可以有苏PPORT_AN_B_001 or the dual image booting, you can't have both of them, as mention by supporting the AN_B_001 the bootloader will search for the booting header in the fw and will not go to the product header to search for the active fw.
Thanks MT_dialog