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.

Basic Wi-Fi Application, Warning: Compiler Version

I know warnings are usually ignored, but I am wondering if this has any consequence to my current issue. 

This project was created using a version of compiler that is not currently installed: 4.0.0 [MSP430].
Another version of the compiler will be used during build: 4.1.0.B1. 
Please install the compiler of the required version, or migrate the project to one of the available compiler versions by adjusting project properties.

I am able to build all the files fine, and debug/download it on to the MSP430FRAM board. LED6 glows solid, but when I go into HyperTerminal, 
CC3000 does not go to First Time Configuration
Mode when I send '01' to it. It does however display the driver version on reset (the driver version is 1.7.2.2). 
  • Hi,

    Which version of CCS are you specifically using? The project was compiled using v5.1.

    It seems to me that you might be using 5.2.0.Beta which is not to be used for production. It might not be the issue behind the failure of the software.

    Do you press 01 and then enter? How did you configure your hyperterminal?

    Gustavo

  • Gustavo,

    I am using the  Version: 5.2.0.00032. Can I remove this version and download the 5.1 version while still retaining my free license? Is there a binary in the zip file that I can load directly?

    I pressed 01 and enter. I configured hyperterminal by following the instructions from here. I am also thinking there might be an issue with HyperTerminal because I am using Windows 7 with the files for HyperTerminal from Windows xp. Are there instructions for other software like Putty?


     

    Thanks! 

  • Windows 7 has sometimes serial ports issues.

    To resolve this, go to Device Manager-> Right click on the port for the MSP430 Application UART-> Properties-> Port Settings -> Advanced

    Then change the COM port number to another number. Even though it says they're busy, you can still assign the COM port number. it will complain that it is being used but press OK. Then Disconnect, wait then reconnect the FRAM board and try the terminal. I've successfully used putty at 9600 8N1. No special configuration required.

    Regards,
    Gustavo

  • Gustavo, 

    I tried that, no change. 

    The Wiki says to use 115200 8N1, also windows 7 by default lists 9600 8N1 in Device Manager. But I still don't understand how I am able to get it to display the splash screen if you will which indicates the version number of the app, but I am not able to get a response for sending in the opcode. 

  • Try running the CCS debugger and put a breakpoint on line 938 in basic_wifi_application.c:

    DemoHandleUartCommand(g_ucUARTBuffer);

    Then type 01 [Enter] and see if it gets there.

    Gustavo

  • Also, when I tried to download the file through IAR, I get this message, when I try rebuilding the BasicWiFiApplication file, no errors with the other re-builds though  : 

    [Og007]: Assembler list file generation not allowed in this version of the compiler 
    Error while running C/C++ compiler 
  • You will need the 30-day evaluation version of IAR available here:

    http://supp.iar.com/Download/SW/?item=EW430-EVAL

    Gustavo

  • Gustavo, 

    Thank you for the help so far! 

    1. I was able to get the board into first time Configuration in Debug Mode, I was also able to connect to the AP.  LED's 6, 7 and 8 are lit solid now. 

    2. I tried the same procedure without debug mode, it did not work. 

    3. It does go to the break point while in debug mode. 

    I am not sure how to move forward now. What is the debug mode doing that the regular run is not?  Also, now after powering on and off, it now shows LED's 6 and 8 solid. So it seems to have saved the profile. 

  • Hi,

    I'm glad you were able to make it work. I am not sure what is going on in the release mode. We will look at it and resolve it.

    As for your last question, yes, the CC3000 saves the profiles, especially First Time Config, and will automatically connect to the AP at startup. It is possible of course to change this behavior.

    Regards,
    Gustavo

  • Hi,

    It appears that the issue might be related to a bug that is to be resolved in our next release.

    In the beginning of the main at basic_wifi_application.c change:

    __bis_SR_register(LPM3_bits + GIE);  

    To:

    __bis_SR_register(LPM2_bits + GIE);

     

    This should enable you to run the program without the debugger.

    Regards,
    Gustavo

  • Gustavo, 

    Thanks again. I have flashed the new program with the change. But since I have already have the profile saved in the EEPROM it hasn't made a difference. But I shall try deleting the profiles on it and repeating the procedure. If you could enlighten me on why the change had to be made, it would be great. It's always useful for future reference.

    Thanks! 

  • Gustavo,

    I was able to put it into first time configuration successfully,  without using debug mode. Thanks! 

  • Hello,

    I am doing same application but i m not getting any response from hyper terminal. Led & is blinking on board.

    After that what should I do. 

    Please do help

  • I mean LED 7 is blinking

  • HI  K_Chandrashekar

    I read all your above posts.

    As these posts are old,

    I want to know how you connected your cc3000 to access point in basic wifi application.

    After 01, do we have to first use 08 command to connect to AP or 02 to connect cc3000.

    And what is default SSID in this code or do we have to enter ssid through hyper terminal.

  • Hi,

    command 01 (First Time Config) and command 02 (explicit connect) are two ways to connect to AP.

    If you want to connect via FTC, choose 01 in the terminal and wait for the CC3000 to connect (the blinking LED should stop when FTC is successful).

    The prefix used for FTC is hard coded to 'TTT' so if you want to use a different one you need to recompile.

    The 08 command should be used only if your AP cannot provide an IP address. In this case, you would need to configure the IP address statically.

    BR,

    Shlomi

  • Nikit, 

    1. You first enter 01, LED7 should start blinking which means the device is now in first time configuration mode. During this time you will have to send either probe requests or beacons from your chosen wifi device, read more about how to do it here:http://processors.wiki.ti.com/index.php/CC3000_First_Time_Configuration (FTC)
    2. Additionally you can avoid step 1 and connect to the AP directly without FTC using 02 followed by security type,ssid length and ssid. For instance, if your ssid is TP-LINK_2ABCD. You will have to enter '02000DTP-LINK_2ABCD' on hyper-terminal.

    There is no such thing as a default ssid, your ssid is based on your router, it is just the name of the access point. You can also find it on your router's configuration page at : http://192.168.1.1/

    The 08 command  followed by its arguments is only necessary if you want to assign a static IP to your device. Just go through the code you will have a much clear understanding of whats happening. 

  • Thank you for your reply.

    Let me know after i connect cc3000 to AP without step 1, how exchange of data takes place.

    If i type 03 in hyper terminal nothing is happen as it says open socket. 

    So before sending any data or receiving data i have to press 03 but hyper terminal dosen't respond.

    please let me know how exchange of data has to be done.

  • Hi,

    Can you elaborate what you mean by "hyper terminal doesn't respond"?

    Basically, you should see 'Done' on the hyper terminal. If you don't get it, it might be that the WiFi connection is not established properly.

    You need to be connected to the AP and gets a valid IP address before openning a socket.

    After the socket is opened successfuly, you can send and recieve data via '04' and '05' commands respectively.

    BR,

    Shlomi

  • Just to add:

    If you want to recieve data you need to bind first to a local UDP port using '06' command.

    Please note: you may be stuck when openning a socket if you don't have an IP address assigned. E.g. if the AP you are using does not have a DHCP server, the open socket command would be stuck. In this case, you need to assign the IP address statically using '08' command.