Hello,
We recently ran into a problem where the Bootloader on F28027 stopped working. We used to use Boot ROM library for Flash operations (erase, program etc.), but that stopped working on another batch of this MCU. To solve the problem I linked in Flash2802x_API_V200.lib to the Bootloader and stopped using Boot ROM. To confirm the Boot ROM was the problem I saved its memory space (memory from address 0x3FE000 and 0x1FC0 words long) from the two MCUs and the files were different. The files are attached (they are .bin files, but had to rename it to .txt to be able to upload).
Could you confirm that the Boot ROM has been changed in between two releases of the micro? Was it changed in a way that the APIs were not placed in the same memory locations?
Based on what I’ve experienced I believe the answer to both questions is ‘yes’. If so, I am concerned about Boot ROM on F28035. It is still working (the Boot ROMs on the two batches of the micro I have are the same), but is there any possibility that the Boot ROM on F28035 could be changed in future that would break the current functionalities? I hope the answer to this question is ‘no’ and then you can stop reading the rest of this post :-). However, if the answer is ‘yes’, then we could run into ‘Bootloader does not work’ on F28035 as well. I understand there is library Flash28035_API_V100.lib that has to be ‘ordered’ through the marketing channel. That would be ok, but linking this library in would significantly increase the Bootloader size which we do not have available. I am looking for an advice on how to make sure the flash API will work in some future releases of the F28035 micro.
Thanks a lot,
Slavica