I used following steps
1. I made fw_1.img , fw_1.img
2. ran command -- mkimage.exe multi eeprom fw_1.img 0x8000 fw_2.img 0x13000 0x1F000 multi_part.bin
3. loaded multi_part.bin in offset 0 of eeprom -- with option make_eeprom_bootable = no ( it comes as the popup after pressing burn button)
4. burn secondary_bootloader.hex in otp
5. burn otp header with
application flag 1 ---- yes
application flag 2 ---- yes
remapping flag --- Otp at 0
DMA length ---- 0x1FC0
JTAG enable flag --- enable
i have three question:
1. did i missed any steps ?
2. i enabled jtag so that i can debug my hardware even after otp , will keeping jtag enabled increase the current consumption of device?
3. also we have to store some data in our device as the ota eeprom contains two image starting from 0x8000 can i use the same memory to store application specific data
Hi mohit3112,
1) I dont see any missing steps. You can check the AN-B-029 for making a multipart bin, your remapping flag and your DMA length is ok.
2) i am not aware of something like that, i dont think so though.
3) We haven't tested this kind of scenario, but i dont see anything that can cause you trouble, the beacon reference design is using SUOTA and some configuration data stored on the same SPI flash.
Thanks MT_dialog
hi tried all the steps it worked fine but when i tried to update the device using android souta app it displayed message " writing to external device failed " settings in my app was was block size 240 and i check i am using correct i2c pins also
Hi mohit3112,
Have you compliled the sw in order to use the i2c as external memory and have you produced your multi_part.bin to use the EEPROM. Seems by the error that when downloading code the sw cant access the i2c memory.
Thanks MT_dialog
I have checked it with my hardware team seems like a board issue , i conform all the steps and final files is working well in our prototype boards . so problem is solved .
thanks
Mohit
Hi mohit3112,
Thanks for indicating.
Best Regards MT_dialog