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.

cc3200 Unable to detect Wifi or not working

Other Parts Discussed in Thread: UNIFLASH, CC3200

Initially the board was working properly. I updated the service pack via UniFlash. Now when i start out of the box experience i am unable to detect any wifi signal in any programs.

I again re formatted and flashed default out of box binary. Still the wifi is not detected. 

What is the problem>?

  • Hi Niraj,

         When you formatted your CC3200 did you set to correct size of 1 MB and left unchecked "Secure" and "Alert"?

         Try running a example program using your IDE like CCS and see if it works.

    - kel

  • I am new to this..

    I did format it but the out of box programs default 2 LED's stays on..

    I tried to format it again but they stay on.

    How do i format it and flash new binary

  • I think i was not clear in my reply.. Sorry!

    Yes i Did so. I got the following results. 

    [09:35:00] Begin Format operation.
    [09:35:00] INFO: > Executing Operation: Connect
    [09:35:00] DEBUG: waiting and clearing uart rx buffer
    [09:35:02] INFO: setting break signal
    [09:35:02] INFO: --- please restart the device ---
    [09:35:02] DEBUG: wait for ack
    [09:35:06] INFO: connection succeeded
    [09:35:06] INFO: getting storage list
    [09:35:06] DEBUG: wait for ack
    [09:35:06] INFO: > Executing Operation: Init
    [09:35:06] INFO: reading version info
    [09:35:06] DEBUG: wait for ack
    [09:35:06] INFO: DEVICE CC3200 ES1.32
    [09:35:06] INFO: reading version info
    [09:35:06] DEBUG: wait for ack
    [09:35:06] DEBUG: Bootloader version is 2, 0, 3, 2
    [09:35:06] DEBUG: It's a CC3200 device: PG1.32
    [09:35:06] DEBUG: raw storage write
    [09:35:06] DEBUG: wait for ack
    [09:35:06] DEBUG: BlockSize is 4096, number of blocks is 64
    [09:35:06] DEBUG: erasing 1 blocks starting from 4
    [09:35:06] DEBUG: wait for ack
    [09:35:06] DEBUG: status request
    [09:35:06] DEBUG: wait for ack
    [09:35:06] DEBUG: wait for ack
    [09:35:06] DEBUG: status request
    [09:35:06] DEBUG: wait for ack
    [09:35:06] DEBUG: status request
    [09:35:06] DEBUG: wait for ack
    [09:35:06] DEBUG: wait for ack
    [09:35:07] DEBUG: wait for ack
    [09:35:08] DEBUG: Switch to NWP bootloader complete
    [09:35:08] INFO: reading version info
    [09:35:08] DEBUG: wait for ack
    [09:35:08] DEBUG: Bootloader version is 2, 0, 3, 4
    [09:35:08] DEBUG: raw storage write
    [09:35:08] DEBUG: wait for ack
    [09:35:08] DEBUG: BlockSize is 4096, number of blocks is 16
    [09:35:08] DEBUG: erasing 12 blocks starting from 0
    [09:35:08] DEBUG: wait for ack
    [09:35:08] DEBUG: status request
    [09:35:08] DEBUG: wait for ack
    [09:35:08] DEBUG: wait for ack
    [09:35:08] DEBUG: status request
    [09:35:08] DEBUG: wait for ack
    [09:35:08] DEBUG: wait for ack
    [09:35:08] DEBUG: status request
    [09:35:08] DEBUG: wait for ack
    [09:35:08] DEBUG: wait for ack
    [09:35:08] DEBUG: status request
    [09:35:08] DEBUG: wait for ack
    [09:35:08] DEBUG: wait for ack
    [09:35:08] DEBUG: status request
    [09:35:08] DEBUG: wait for ack
    [09:35:08] DEBUG: wait for ack
    [09:35:08] DEBUG: status request
    [09:35:08] DEBUG: wait for ack
    [09:35:09] DEBUG: wait for ack
    [09:35:09] DEBUG: status request
    [09:35:09] DEBUG: wait for ack
    [09:35:09] DEBUG: wait for ack
    [09:35:09] DEBUG: status request
    [09:35:09] DEBUG: wait for ack
    [09:35:09] DEBUG: wait for ack
    [09:35:09] DEBUG: status request
    [09:35:09] DEBUG: wait for ack
    [09:35:09] DEBUG: wait for ack
    [09:35:09] DEBUG: status request
    [09:35:09] DEBUG: wait for ack
    [09:35:09] DEBUG: wait for ack
    [09:35:09] DEBUG: status request
    [09:35:09] DEBUG: wait for ack
    [09:35:09] DEBUG: wait for ack
    [09:35:09] DEBUG: status request
    [09:35:09] DEBUG: wait for ack
    [09:35:09] DEBUG: wait for ack
    [09:35:09] DEBUG: status request
    [09:35:09] DEBUG: wait for ack
    [09:35:09] DEBUG: wait for ack
    [09:35:09] DEBUG: status request
    [09:35:09] DEBUG: wait for ack
    [09:35:09] DEBUG: status request
    [09:35:09] DEBUG: wait for ack
    [09:35:09] DEBUG: 0
    [09:35:09] DEBUG: wait for ack
    [09:35:10] DEBUG: wait for ack
    [09:35:10] INFO: > Executing Operation: Format
    [09:35:10] INFO: Erase storage SFLASH
    [09:35:10] DEBUG: wait for ack
    [09:35:10] INFO: erase storage succeeded
    [09:35:10] INFO: erase storage completed
    [09:35:10] INFO: > Executing Operation: Disconnect
    [09:35:10] DEBUG: disconnecting from device . . .
    [09:35:10] DEBUG: wait for ack
    [09:35:10] Operation Format returned.

    Yet the LED remained ON

    I am new!, Am i doing some thing wrong. Please guide me.

  • Hi Niraj,

    Couple of questions i have:

    1. Which LEDs are you referring to? If you are referring to orange[p2(GP11)] and green[p1(GP10)] LED, then they might be due the jumpers on J2 and J3.  They are required for the i2c communcation with the on-board sensors(accelerometer and temperature sensor).


    2. While flashing the oob binary(using Uniflasher), are you using the out_of_box.ucf  as your target configuration. it can be found in your out_of_box example(..\cc3200-sdk\example\out_of_box\html\out_of_box.ucf) in the SDK.

    Regards,
    Rahul

  • Yes i meant that led's. Is it normal.

    I also tried to run the wlan station program i had following error.

    What shall i do?

    Thanx

  • Hi Niraj,

         From your CCS screenshot, you have a exclamation at wlan_station, meaning you got some warnings when you build it. I suggest you fix those warnings first before trying out the wlan_station.

    - kel

  • Hi Niraj,

    yes that is normal(regarding the LED staying ON).

    Please clarify couple of things for me:

    Q1. Did you try flashing the out_of_box using out_of_box.ucf configuration(as i mentioned previously). Did it work or not?

    Q2. Are you on the latest driver support package for CCS? if not, i suggest to update the driver support package. Refer to section 3.1.2 fo CC3200-Getting_Started_Guide.pdf

    Regards,

    Rahul