This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MSP432 Flash Ctrl A problem

Hi,

In "Driverlib User Guide" we find for Flash Ctrl A:

9.1 Module Operation Note that this module is for use exclusively on the MSP432P4111. If using the MSP432P401, please refer to the non-a variant. The MSP432 DriverLib Flash Controller A peripheral is designed to simplify the process or writing, erasing, and configuring the flash memory on the MSP432 part. Many of the stringent verification requirements/preconditions are handled entirely inside the FlashCtl APIs.

while originally seamed to work ok, it now doesn't. We are using a MSP432P4011. What seems to happen happen is that it looks like in the following code of the boorloader(originates from "oad_bootloader_source_MSP_EXP432P4111_nortos_ccs" which we transfered to the MSP432P4011(which seemed to work as well!):

Thus MSP432P4111 also means it is NOT for the MSP432P4011 we use? It works only with smalll files sofar!

rgds,

Laurent  

  • Hi Laurent,

    I tried to find that file, but couldn't under our SDK. We do have flash examples for the MSPEXP432P401R that you could use as a reference though. If you need access to the simplelink msp432p4 sdk please contact your sales representative. If you already have the SDK then the examples should be in the folder simplelink_msp432p4_sdk_[version]/examples/nortos/MSP_EXP401R.

    I would suggest to follow the user guides recommendation. Some recommendations aren't always for issues seen immediately, but are precautions on issues that could arise eventually.

    Regard,

    Luke

  • Hi Luke,

    thanks for reply! However I did some torough research and a range of tests and these are my results:

    - MAP_FlashCtl_A_unprotectMemory : works OK

    - MAP_FlashCtl_A_performMassErase : works OK

    - MAP_FlashCtl_A_programMemory : Has several errors and flaws, won't work ever on large files!

    However I was capable of creating a nice stable work-around, still using this MAP_FlashCtl_A_programMemory function successfully!

    rgds,

    Laurent