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.

LAUNCHCC3235MOD: programming and running application compare to CC3235SF-LaunchPad

Part Number: LAUNCHCC3235MOD
Other Parts Discussed in Thread: CC3235SF, CC3235MODSF, TMDSEMU110-U, CC3235S, CC3235MODS

Hello,

we had the CC3235SF-LaunchPad  and was able to develop the application framework (based on http server example).

things worked fine.  however, we noticed that there is LAUNCHCC3235MOD (CC3235MOD part) that could potentially save us time on layout/cap tuning, etc.

before buying the LAUNCHCC3235MOD to try out, can you please confirm with me the following things:

1- It seems LAUNCHCC3235MOD used MSP430 to emulate XDS110 while CC3235SF-LaunchPad use TIVA MCU to emulate the XDS110.  can you please confirm from user point of view, this is all transparent?  another word, i only need to hook up the USB and i can flash in the CC3235 directly from CCS (v10) flash option just like i did for the CC3235SF-LaunchPad.

2- the http server application that we have now running on CC3235SF-LaunchPad will run on LAUNCHCC3235MOD without any modification?  i think this is the case because it is the same CC3235, but i just want to make sure that is the case.

I already order XDS110 box for custom board but i will try to use XDS110 box on the launch pad to see how it perform vs the built in XDS110 on launch pad.

Thanks and Best Regards,

Henry

  • Hi Henry,

    1. LAUNCHCC3235MOD uses exact same XDS110 (TM4C MCU) as CC3235SF-LaunchPad. LAUNCHCC3235MOD works exact same as CC3235SF-LaunchPad from CCS stand point.

    2. Yes, code will stay exact same for CC3235SF QFN and CC3235MODSF. At your case I don't see any advantage of buy LAUNCHCC3235MOD. You should start designing of your board with module. After that you can ask TI for review of your design here.

    Main advantage of using TMDSEMU110-U instead XDS-110 from LaunchPad is that:

    • TMDSEMU110-U is at box and from this reason is usage little bit more practical
    • TMDSEMU110-U supports Energy trace for power consumption monitoring from CCS for some MCUs
    • There is no performance difference at TMDSEMU110-U and XDS-110 from LP (for example I have TMDSEMU110-U but I not used them with own hardware, I use XDS110 from LP for my hardware).

    Jan

  • Hi Jan,

    Thank you so much for the quick answer.  your answer confirmed my understanding.

    now, i just checked around for the part of CC3235SF or CC3235MODSF, there is nothing available.  

    there are a lot of  CC3235S and CC3235MODS which does not have 1 MB of internal flash for application M4 core.

    the part CC3235MODSM2MOB is available, but part CC3235MODSF12MOB (on LAUNCHCC3235MOD) is not available and lead time is too long.  this is show stopper for us because we need to run our prototype by early next year.

    if i use CC3235MODSM2MOB, how does the application processor code run? is it really shared with the data on 256KB RAM? how does it load its own application codes into SRAM from external 32 MBit or 16 MBit serial flash?

    if i look at the project in in CC3235SF like .out, or .sli image, how do i know how many KB is assigned to application M4 and how many KB is assigned to NWP?

    it would be greatly to know this partition so that by the time we got the CC3235MODSM2MOB or CC3235S, then we are not in any surprise.

    Thanks and Best Regards,

    Henry

  • Hi Henry,

    In case of S devices is code executed from RAM. 256kB RAM is shared for code and data (heap, stack, your variabels and buffers). At boot time is code loaded from SPI flash (4MB) inside module into RAM by the ROM bootlaoder.

    There is no difference at NWP between S and SF version. NWP does not use resource from application processor for own purpose. NWP is a separate MCU with own RAM. For determining how much memory needs your application, you can use Memory Allocation tool at CCS. It is hard to say if S variant is suitable for you application. This you need to determine according your application needs.

    Jan

  • Hi Jan,

    thank you so much again for your input.

    please see attached picture that I captured from CCS memory allocation for both MCU+Image.

    from this image, i can see that the Programming.sli size is about 307 KB.

    the memory allocation report said that the Flash (codes, etc) is about 90.7 KB and the SRAM is about 48.2 KB which total up about 140KB.

    i assumed that the memory allocation report is strictly reporting the application processor code and data; not including the NWP code and data right?

    Thanks and Best Regards,

    Henry

  • Hi Henry,

    Size of SLI image file is not important for you at this moment. Because this file is loaded into SPI flash with size 4MB. This file contains some additional data like a ServicePack, NWP configuration, etc.

    Important for you is size of code and data. At your case 140kB and this perfectly fit into 256kB RAM. If your application not grow at the feature dramatically, you will be fine with CC3235MODS.

    Jan

  • Hi Jan,

    thank you so much for your answers.  I think i understand the issue now.

    I do have some more questions regarding about the CC3235MODS because we intend to make sure it survives (not power up and not operating) the harsh environment but I will try that on different thread so that we can close this thread.  

    Thanks again for your help.

    Best Regards,

    Henry