Part Number:CC3220SF
Hello Everyone!
I face the strange issue, that I guess can not be explainde by bootflow chapter of Reference Manual.
The sequence of my actions:
1. I download dev-mode image via uniflash to extenral flash with mcuflashimg.bin created out of IAR binary,
the application reads data from some address in Flash and blinks diode, if data is the same as expected by app;
2. I use Uniflash to download some data to some address via SWD, (for example to the first bank 0x01070000 or to the second bank 0x01080000);
3. If I download correct data, diode blinks, if incorrect - does not, so the functional truly works;
4. Next I download prod-mode image with the same mcuflashimg.bin from the same IAR binary, and I compared mcuflashimg.bin from dev- and prod-modes, the are equal.
That means that their SHA-1 should be the same? And ROM-bootloader should not detect new mcuflashimg.bin and shoud not erase internal flash and upload new one from external.
5. After downloading prod-mode, app runs, but diode doesnt blink, so that means internal flash was erased and written again;
So my question is why internal flash erased, if mcuflashbin.img are equal in both modes?
Also why mcuflashbin.img size is about IAR binary size when I download it to some folder from Uniflash (78 KB in my case)? I guess it should be 1024 KB as written in Uniflash?
My goal is to write some special data to internal Flash, while debug-interfaces are enabled, then disable them by dowloading prod-mode image, but internal flash data I've written should be saved.
Regards,
Boris