Failed connecting to WiFi

Strange. Can you patch the old CC3000 and test again?

I don’t recommend doing patches if your core worked fine. Flashing blue just means it didn’t received any wifi credentials and does require any fix

Patched the old CC3000 with your link.

I get similar results, flashing yellow, then dfu successfully patches the CC3000 bin, light goes off. Holding mode for more than 1 sec, light stays off.

If I do a full reset, it goes back to flashing white

OK, I received my Spark a couple of days ago, and installation did not go along as smoothly as the website said it would. My Core is the u.FL version, and I have connected this antenna to it - “2.4GHz Antenna - Adhesive (U.FL connector)” - https://www.sparkfun.com/products/11320

I am using a PC with Ubuntu 14.04
My WiFi router is 802.11b+g (NOT n), Firewall disabled, DHCP enabled.

  1. http://docs.spark.io/start/ - done everything here and downloded Android App (My Phone is a SONY XPERIA ST27i running Android ver 4.1.2)
  2. http://docs.spark.io/connect/ - I got stuck at the Flashing GREEN stage.

The Android App says it cannot find any Core. Tried several times.

Via USB, I’m able to enter the WiFi credentials (SSID, Security, PW) , but I do not see a pulsing cyan light, no matter how long I wait. It just keeps flashing Green.

I also tried the Spark CLI interface, without any luck.

Running

spark flash 55ff6e065075555308431787 cc3000

from CLI, I got the response :

attempting to flash firmware to your core 55ff6e065075555308431787
flash core said {“error”:“Permission Denied”,“info”:“I didn’t recognize that core name or ID, try opening https://api.spark.io/v1/devices?access_token=b46113de7e5b9f90770580c7f0f843c537c50259”}

Same result when using sudo.

Visiting the mentioned URL, I can just see a pair of square brackets

[]

I cloned the GIT repo “https://github.com/spark/cc3000-patch-programmer.git

and then ran

dfu-util -d 1d50:607f -a 0 -s 0x08005000:leave -D cc3000-patch-programmer.bin

for which I got the response :

invalid dfuse address: 0x08005000:leave

I have gone through the troubleshooting steps at this link :

docs.spark.io/#/connect/troubleshooting

and read through all of the 209 posts on this topic.

What am I doing wrong ?

Anool, team WyoLum
Mumbai, India

It sounds like your dfu-util version is not 0.7.

Let me get back to you and do a troubleshoot when I get home :slight_smile:

I downloaded dfu-util from the current 14.04 Trusty-Tahr repository via the Software center.
This is the link :
https://launchpad.net/ubuntu/trusty/+package/dfu-util

Hmm… Can you just double check with this?

@Hypnopompia, what’s the version of DFU on Ubuntu 14.04?


OK i see what might be wrong as well.

Can you use this patch instead: https://github.com/spark/cc3000-patch-programmer/tree/nobuttons/build

You can use this this code to flash:

dfu-util -d 1d50:607f -a 0 -s 0x08005000 -D cc3000-patch-programmer.bin

1 Like

14.04 provides dfu-util 0.5, which is too old. @Anool_WyoLum, you’ll need to uninstall the one from ubuntu and then download the source and compile it to get the latest version.

Use the instructions from the How-to that @kennethlimcp posted above.

1 Like

ok, so following @Hypnopompia 's post on setting up the Spark toolchain on Ubuntu 14.04, I managed to install dfu-util ver 0.7

The only one step I couldn’t follow was :

Edit core-firmware/src/application.cpp and change it to your own code.

I’m not sure what that means.

I flashed the new firmware from the core-firmware/build directory, and this was the result :

dfu-util 0.7

Copyright 2005-2008 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2012 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util@lists.gnumonks.org

dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Opening DFU capable USB device…
ID 1d50:607f
Run-time device DFU version 011a
Claiming USB DFU Interface…
Setting Alternate Setting #0
Determining device status: state = dfuERROR, status = 10
dfuERROR, clearing status
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 1024
DfuSe interface name: "Internal Flash "
Downloading to address = 0x08005000, size = 73744
Download [=========================] 100% 74752 bytes
Download done.
File downloaded successfully
Transitioning to dfuMANIFEST state

I was still getting stuck at the flashing green stage, so I followed @kenneth​lim​cp 's suggestion to use the patch from : https://github.com/spark/cc3000-patch-programmer/tree/nobuttons/build and ran :

dfu-util -d 1d50:607f -a 0 -s 0x08005000 -D cc3000-patch-programmer.bin

which resulted in this :

dfu-util 0.7

Copyright 2005-2008 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2012 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to dfu-util@lists.gnumonks.org

dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Opening DFU capable USB device…
ID 1d50:607f
Run-time device DFU version 011a
Claiming USB DFU Interface…
Setting Alternate Setting #0
Determining device status: state = dfuERROR, status = 10
dfuERROR, clearing status
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 011a
Device returned transfer size 1024
DfuSe interface name: "Internal Flash "
Downloading to address = 0x08005000, size = 51548
Download [=========================] 100% 52224 bytes
Download done.
File downloaded successfully

The LED was flashing Yellow.

Pressing RESET caused the RGB LED to go OFF, and the small blue LED near the RST button to be ON.

Pressed MODE for a few seconds, and the rgb LED was flashing Magenta for a while, and then Solid Magenta (and small blue LED still ON)

I don’t see Solid Magenta as being listed under the list of LED colors :

Flashing blue: Listening for Wi-Fi credentials
Flashing green: Connecting to the Wi-Fi network
Flashing cyan: Connecting to the Spark Cloud
Flashing magenta: Updating to the newest firmware
Breathing cyan: Connected!

So I went back and re-flashed from the core-firmware/build folder :

sudo dfu-util -d 1d50:607f -a 0 -s 0x08005000:leave -D core-firmware.bin

which returned me back to the flashing Green LED. Pressed mode for >3 seconds to get the Blue Flashing LED, and then ran :

spark setup

and entered my SSID, Security (WPA2) and Password. This resulted in :

Done! Your core should now restart.

Please wait until your core is breathing cyan and then press ENTER

but it’s back again to flashing Green LED.

I’m about 8 feet from my WiFi router, whee my PC as well as mobile phone are able to receive the WiFi signal.

Using the Android app also results in “No Cores Found. Try Again”

Hmmm…

I’m suspecting something :fish:y going on with WPA2.

Could you do a WPA Wifi setup with non-funky SSID and password?

Thanks for your patience on this matter :smile:

Changed WiFi security to WPA-PSK and the encryption defaults to TKIP (not sure if that matters but there is no way to change / modify).

SSID is a regular name (11 alphabets - does length matter).

Password is now 8 characters long, all lower case alphabets with a single numeral in between.

I’m willing to work through this till we arrive at a solution. Let me also check with my buddy in Washington who has the second of the two Spark Cores we purchased. He hasn’t yet had time to set it up. I’ll ask him and get back.

So Security type is WPA now but still not connecting?

Flashing blue --> Solid Blue --> restart --> Flashing green?

The CC3000 patch should have fixed it. Can we try to go nearer to the router and leave it running for some time?

Sometimes, it gets connected after a while.

Also, just to be sure, perform a factory reset and triple check the Wifi Credentials! :smiley:

@kenneth​lim​cp
Yes to all of your Q’s.

When I try to compile the Spark firmware using :

cd core-firmware/build
make

I get these errors :

Building core-common-lib
Building file: …/CC3000_Host_Driver/cc3000_common.c
Invoking: ARM GCC C Compiler
mkdir -p obj/CC3000_Host_Driver/
arm-none-eabi-gcc -g3 -gdwarf-2 -Os -mcpu=cortex-m3 -mthumb -I…/CC3000_Host_Driver -I…/SPARK_Firmware_Driver/inc -I…/STM32F10x_StdPeriph_Driver/inc -I…/STM32_USB-FS-Device_Driver/inc -I…/CMSIS/Include -I…/CMSIS/Device/ST/STM32F10x/Include -I. -ffunction-sections -Wall -Wno-switch -fmessage-length=0 -MD -MP -MF obj/CC3000_Host_Driver/cc3000_common.o.d -DUSE_STDPERIPH_DRIVER -DSTM32F10X_MD -DRELEASE_BUILD -c -o obj/CC3000_Host_Driver/cc3000_common.o …/CC3000_Host_Driver/cc3000_common.c
make[1]: arm-none-eabi-gcc: Command not found
make[1]: *** [obj/CC3000_Host_Driver/cc3000_common.o] Error 127
make: *** [check_external_deps] Error 2

Does that give you any clue ?

I also probably need to mention that I’m using 64-bit version Ubuntu

i’m lost…

Are you having issues connecting to the :spark: Cloud right?

There’s no need to build the files yourself and we will stick to the already available .bin file for now…

Try this?

I placed it a few inches away from my WiFi router, and made sure my Laptop and Mobile phone were at least many feet away. Still no love. It’s still flashing green. Looking at my earlier post, I figured I was missing a few dependencies. I have since managed to clean up all of my installation, and can confirm that everything described in this thread https://community.spark.io/t/how-to-install-the-spark-toolchain-in-ubuntu-14-04/4139 has been tried, but still unable to connect.

So, in short :

I’m unable to connect to the Core via the Android App. I do a factory reset so it’s in listening mode (flashing Blue). Android app detects my SSID, and when I enter PW, the LED on the Spark core turns flashing Green. After a while, the App says - No Cores Found. Try again.

I do a factory reset again, and make sure Spark is in listening mode - flashing blue. I’m able to use the Spark CLI “spark setup” and set up my SSID, Security and PW. CLI response is :

Thanks! Wait about 7 seconds while I save those credentials…

Serial said: Awesome. Now we’ll connect!

If you see a pulsing cyan light, your Spark Core
has connected to the Cloud and is ready to go!
If your LED flashes red or you encounter any other problems,
visit https://www.spark.io/support to debug.
Spark <3 you!
Done! Your core should now restart.
Please wait until your core is breathing cyan and then press ENTER

but it continues to flash Green.

Is it possible for one of you folks to do a Google Hangout with me ? I can share and show you what’s going on.

1 Like

Flashing green is an issue which has occurred a couple of times and the steps mentioned above are what we run through to fix it.

The last resort is to have the core exchanged.

@Teke should be able to see if a hangout is possible.

I’ll wait for @Teke to confirm about the Hangout. It’ll be better to try and resolve this if possible without having to get the core exchanged.

Hi there, @Anool_WyoLum - I don’t think we can make a hangout happen, but one of our engineers will be in touch shortly to discuss options and do some additional troubleshooting. Hang in there!!

okay, standing by.

Meanwhile, I have one query - how do I confirm if the external antenna I have connected works or not ?
This one :

I did a basic continuity test using my multimeter to make sure there isn’t a short / open.

UPDATE :
The Spark Core works on my WiFi network at home.
I now need to figure out the difference in the WiFi settings between home and office.
The only obvious one I found was
802.11ng at home and 802.11b/g at work
Ch 1 at home and Ch 6 at work

I’ll report more later

1 Like

Hi @Anool_WyoLum,

Often work wifi networks will have in place strict MAC address filtering, or blocking of some outgoing TCP ports, your IT dept should be able to help get those working for your Core. If they’re using certificate based enterprise wifi encryption then that’s something the CC3000 can’t support as is.

Thanks!
David