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.

MSP-EXP432P401R: SPPDemo example doesn't fit in flash

Part Number: MSP-EXP432P401R

Hello,

I'm trying to evaluate the MSP-EXP432P401R launch pad along with the CC2564MODA booster pack.

I've downloaded and installed the dual-mode bluetopia stack and imported both SPPDemo projects into CCS.

However, whenever I build either project, the firmware image is too large to fit into flash with any optimization level.

Is there something I'm overlooking?

thanks,

Anthony

  • Hello,

    I looked through the TI Dual-mode Bluetooth® stack on MSP432 MCUs User Guide, and the demo code should fit on the MSP432. Did you check that the correct device is selected under your CCS project properties? Did you follow the instructions in Section 5.2 in the User Guide?

    Regards,

    James

  • Hi James,

    Thanks for the prompt reply.  Yes i did verify the correct device was selected and I did follow the instructions from section 5.2.

    264k was the smallest build size.

    The one thing different from the instructions is the compiler version (and IDE version).

    I'm using newer versions of both.  The instructions list compiler version TI v5.2.6 which is not installed with CCS version 9.0.1.0004.

    [TI v16.9.4.LTS] is the version that CCS listed as compatible, so perhaps that is not actually true?

  • Hi Anthony,

    I tried importing the projects into CCS v10, and the project got created but the source files didn't seem to be copied in correctly. They show up but when clicked, aren't accessible. I got multiple build errors. The user's guide is several years old, but the instructions and code should work using the CCS version originally used, v6.1.1.00022.

    I would try using that CCS and compiler version and see if you can get things to work.

    Regards,

    James

  • Quick update. I resolved the build errors. The source files were not getting copied into the workspace project even when selecting "Copy projects into workspace". After deleting the SPPDemo project in my workspace and then deselecting that option when re-importing, I got the SPPDemo project to build cleanly in CCS v10.

    Next, I opened the Memory Allocation (found under View) in CCS and learned that the total Flash memory required was ~134KB. Finally, I was able to successfully program my MSP-EXP432P401R LaunchPad.

    I hope this helps! Not having to install CCS v6.1.1 should save you some time.

    Regards,

    James

  • Thanks again for the reply.

    I was puzzled why your results were different than mine so I tried again seeing the same results as you.

    I later realized the difference was because I named the wrong project in this thread.  My apologies.

    I was actually trying to import the projects named SPPLEDemo and SPPDMMultiDemo.  Both of those are too large to fit. 

    I was assuming that those projects included both classic bluetooth and BLE stacks while SPPDemo only contains classic bluetooth.

    Is my assumption correct?  If so, what do you recommend for evaluating the dual-mode?  I need to be able to use both for the project I'm working on.

    Thanks again,

    Anthony

  • Hi Anthony,

    Have you considered using the larger-memory MSP432P4111 device? It should be pin-to-pin compatible with the MSP432P401R that's on your LaunchPad. Alternatively, you could order the 100-pin target board, MSP-TS432PZ100. That should give you enough memory for these projects.

    Regards,

    James

  • Hi James,

    I had considered using the MSP432P411 but I only found support for the MSP-EXP432P401R in the Bluetopia stack.  So I wasn't certain they were interchangeable.

    Is there anything additional I need (linker files etc)?

    Thanks,

    Anthony

  • Hi Anthony,

    It should be easy to change devices since they should be identical except memory sizes. In CCS, you'd just select the P4111 which should switch linker files automatically. There may be hard-coded references to P401R files in various files, but those should also be easy to change. You could always try to make those changes and build the project(s) before ordering the P4111.

    Regards,

    James

  • Thank you James for your continued support.

    I tried building these projects with the P4111 selected as you suggested.  I had to modify an include inside "msp.h".

    After doing that, there are still quite a few undefined symbols all referenced from "system_msp432p4111.c".

    What else am I missing?

    Thanks again,

    Anthony

  • Hi Anthony,

    I think I know why. Under the Project Properties in CCS, change --preinclude="msp432p401r.h" to "msp432p4111.h" under Build > ARM Compiler > Edit Flags. In this screenshot, you can see that the define=__MSP432P4111__ was automatically changed since I changed the device variant under General. I think you updated 'msp.h' to use the right header file, but perhaps that symbol is used by other files.

    Another thing I noticed is that there's a 'msp432p401.cmd' linker file in the SPPLEDemo > Platforms > MSP-EXP432P401R > ccs folder. That may be causing an issue, you could try replacing that with the 'msp432p4111.cmd' file.

    If you get any other errors, please feel free to share them. I can't guarantee I'll be able to resolve them, but I'll try my best to help.

    Regards,

    James

  • Ok I've now changed that pre-include, the processor define, and deleted the old .cmd file.

    Still I have a large number of compiler errors.  See the screenshot below.

  • Hi Anthony,

    I think these errors are caused by the identifiers using slightly different names in the 'msp432p4111.h' file. I'm not sure why they are different, but you may need to manually update them unfortunately. I think the P401R header file identifiers just use a "FLCTL_" prefix.

    For example, "FLCTL_BANK0_INFO_WEPROT" is used for P401R and "BANK0_INFO_WEPROT" is used for P4111.

    Regards,

    James

**Attention** This is a public forum