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.

BOOSTXL-CC3120MOD: Inquiries regarding CC31XXEMUBOOST

Part Number: BOOSTXL-CC3120MOD
Other Parts Discussed in Thread: CC31XXEMUBOOST, CC3120, UNIFLASH

Hi TI.

 

 I bought the following products to develop the WIFI module.

====================

BOOSTXL-CC3120MOD

CC31XXEMUBOOST

MSP-EXP432P401R

====================

 

I have a question about the following operating conditions.

 

preparation:

  LED EN(J3) and Power Select(J8(2-3)) setting in BOOSTXL-CC3120MOD.

 

1. USB Power supply to CC31XXEMUBOOST(J5)

1.1 Connect BOOSTXL-CC3120MOD and CC31XXEMUBOOST

1.2 USB power supply to BOOSTXL-CC3120MOD.

1.3 USB Power supply to CC31XXEMUBOOST(J5)

1.4 BOOSTXL-CC3120MOD check.

    Power LED is displayed.

1.5 CC31XXEMUBOOST check.

    Power LED is displayed.

1.6 Check the Windows device manager.

========================

  Texas Instatuments Debug Probes

    - CC3100BP-WLAN DBG B

    - CC3100BP-WLAN RS232 A

  PORT(COM & LPT)

    - CC3100BP DBG(COMxx)

    - CC3100BP DBG(COMxx)

========================

 

2 USB Power supply to CC31XXEMUBOOST(J6)

2.1 Connect BOOSTXL-CC3120MOD and CC31XXEMUBOOST

2.2 USB power supply to BOOSTXL-CC3120MOD.

2.3 USB Power supply to CC31XXEMUBOOST(J6)

2.4 BOOSTXL-CC3120MOD check.

    Power LED is displayed.

    nHIB LED is blink.

    Reset LED is blink.

2.5 CC31XXEMUBOOST check.

    Power LED is displayed.

2.6 Windows device manager check details.

    The following drivers appear and disappear repeatedly.

========================

  Texas Instruments Debug Probes

    - CC3100BP-GPIO B

    - CC3100BP-NWP LOG D

    - CC3100BP-SPI A

    - CC3100BP-UART C

  PORT(COM & LPT)

    - CC3100BP DBG(COMxx)

    - CC3100BP DBG(COMxx)

    - CC3100BP DBG(COMxx)

    - USB Serial

========================

2.7 At this time, there is no change even if you press nHIB or Reset.

2.8 Pressing Factory Reset operates as follows.

    Power LED is displayed.

    nHIB LED is displayed.

    Reset LED is displayed.

 

Q1. Is this the correct behavior?

Q2. Can you tell me how to check the log at this time?

 

Q3. Is there any problem with supplying USB power to J5 and J6 at the same time in CC31XXEMUBOOST?
In my case, a blue screen occurred.

 

Thank you in advance.

 

 

Regards,

Simon

  • Hi Simon,

    If the CC3120BP is stacked on the CC31XXEMUBOOST, then you only need to connect J6 on the CC31XXEMUBOOST via USB.

    If you want to power the EMUBOOST and BP separately, you would need to change the power selection jumper on the CC3120BP. See the CC3120 BP Hardware User's Guide: https://www.ti.com/lit/swru457

    The CC3120 will run the out of box configuration when powered on, but it will not print logs via the CC31XXEMUBOOST. You will have to connect it to a host MCU. See the CC3120 Out of Box Experience and the documentation in the Wi-Fi plugin.

    Best regards,

    Sarah

  • Hi Sarah,


    Thanks for your answer.

    I have a question while checking the documentation for the CC3120 SimpleLink™ Wi-Fi® BoosterPack™ Plug-In Module and IoT Solution.

    This is the content to check the connection operation with CC31XXEMUBOOST.

    1.BOOSTXL-CC3120MOD Jumper Settings
      - J8(1-2): MCU
      - J6(short): No current measurement
      - LED_EN(short): LED Display

    2.CC31XXEMUBOOST Jumper Settings
      - J4(short): 3.3V
      - J22(short): 5.0V
      - J3(1-2): NWP logs.

    3. I combined the two boards and applied the power to CC31XXEMUBOOST(J5), but the driver is not recognized.

    4. The device manager is displayed as follows.

    5. The same symptom occurs when replacing BOOSTXL-CC3120MOD and CC31XXEMUBOOST with a new board.


    Q. Am I doing something wrong?
        I can't even use uniflash as it doesn't recognize the port.

    When power is applied to the board, the video is as follows.

    Regards,
    Simon

  • Hi Sarah,


    I solved the problem.

    There was a problem with the USB Cable I was using.

    Since the USB Cable provided by TI is used, the driver is recognized well.

    Thank you very much.


    Regards,
    Simon