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.

CC3235MODASF: Migration of project from LAUNCHXL-CC3235SF

Part Number: CC3235MODASF
Other Parts Discussed in Thread: UNIFLASH, LAUNCHXL-CC3235SF, CC3235SF

Hi,

We have developed our application with LAUNCHXL-CC3235SF and are now ready to migrate our application to our prototype board using CC3235MODASF.  Since we are still in the development and debug stage, we have not established a UART connection to CC3235MODASF but we have access to the JTAG pins (a note in the UniFlash documentation states that JTAG is available in development mode).  Our target host MCU does not have UART lines and we will be communicating to the CC3235MODASF using SPI, which is how we currently have it setup in the launchpad.

We are ready to port our Launchpad code to our prototype board with CC3235MODASF.  Can you please provide some guidelines/references on how to migrate the project and specifically how to flash the code in the CC3235MODASF Wifi module?

Thanks,

Jay 

  • Hi Jay,

    There is nothing like a porting from CC3235SF to CC3235MODASF. Both devices uses inside same QFN chip. Only thing you need to take into account is that pin numbers of QFN are not same as MOD (see data-sheet for MOD).

    Production line guide describes how to program CC3235MOD devices. At first steep you will need program your module into development mode using Uniflash. This can be done via UART only (pins GPIO1, GPIO2).

    If your hardware have some free pins, it make sense design your hardware to be available pin for NWP log. You can select one of these pins PIN_62, PIN_53, PIN_18, PIN_60 (pin number from QFN package!). NWP log is needed in case of some troubles with WiFI communication.

    Jan

  • Hi Jan,

    It is really good to know  that porting from CC3235SF to CC3235MODASF is seamless.  Yes, we noted the pin differences and comprehended those changes in our design.  On our pre production prototype board, all the pins on the MODASF were brought so we can connect headers for future access, like for NWP log purposes as you stated.  We excluded the MSP part in our design for the XDS110 Debug Probe emulation as we thought it was an overkill in our design but we have physical access to GPIO1, GPIO2 and nRESET pins.

    Thanks for sending the production line guide as it has important links for the different flashing options.  Just realized that JTAG headers added on the MODASF side is useless at this point for programmation.  This is our first exposure to SimpleLink CC3xxx family of Wifi devices but we have dealt with the Hercules and C2000 Microcontrollers where debug and flash programmation during development can be carried out through JTAG through the different emulator options, hence made similar assumptions.

    It looks like our code programming options on the CC3235 family is through UART and FlashSPI.  Since we do not have the on board MSP XDS110 Emulator, would a USB to UART interface (with nRST control, as illustrated in Fig.2 of production line guide) work in programming our code to the CC3235MODASF chip with the correct SOP pin positions?

    Regards,

    Jay

  • Hi Jay,

    JTAG for CC32xx devices is intended for development purpose only. But before you be able debug via JTAG, you need to program device into development mode. This can be done via UART.

    Production programming can be done via UART (Uniflash, Uniflash CLI, Embedded programming) or by direct programming via SPI flash programmer (Gang programming). But I strongly recommend to use UART because there are some advantages related to certificate for production mode (described at swru547).

    • For debugging you can connect your hardware to XDS110 from LaunchPad (pins TCK, TMS, TDI, TDO, GND). Same way you can use for Uniflash programming via UART (RX, TX, RST, GND).
    • Yes, you can program board via USB to UART converter like FT232RL. Be aware that Uniflash will not be able automatically detect COM port and control RST line. You you will need to set COM port manually like this:

    dslite.bat --mode cc32xx gui_cfg --port com8

    Jan

  • Hi Jan,

    Thanks for providing the directions and the useful links.  I am now able to flash our code to the CC3235MODASF chip!  Appreciate your help.

    Regards,

    Jay