These are chat archives for marvell-iot/aws_starter_sdk

10th
Dec 2015
Anuj Deshpande
@anujdeshpande
Dec 10 2015 04:59

@xoff00 to reset the board, you can also use the --reset flag
wmsdk/tools/Openocd/flash.py --reset
make sure you are using an updated github repo

also, it would be great to have the console output using something like minicom/screen

@niknaknet c-sdk-client-id is the name of the mqtt client.
http://marvell-iot.github.io/aws_starter_sdk/aws__iot__config_8h.html#ae5283c01e3f612fd5eb92dbc3e446d38
can you post a git diff for the changes that you have made ?
Anuj Deshpande
@anujdeshpande
Dec 10 2015 05:18

@stevefulton that's strange
the output should be something like this

➜  ~  ls -l /dev/tty.*
crw-rw-rw-  1 root  wheel   18,   2 Dec 10 10:43 /dev/tty.AnujsiPhone-WirelessiAP
crw-rw-rw-  1 root  wheel   18,   0 Dec 10 10:43 /dev/tty.Bluetooth-Incoming-Port
crw-rw-rw-  1 root  wheel   18,   4 Dec 10 10:43 /dev/tty.Siddhartha-Bluetooth-In
crw-rw-rw-  1 root  wheel   18,   8 Dec 10 10:43 /dev/tty.usbserial-1423A
crw-rw-rw-  1 root  wheel   18,   6 Dec 10 10:43 /dev/tty.usbserial-1423B
➜  ~  sudo kextunload -p -b com.apple.driver.AppleUSBFTDI
Password:
➜  ~  sudo kextutil -b com.apple.driver.AppleUSBFTDI -p AppleUSBEFTDI-6010-1
➜  ~  ls -l /dev/tty.*
crw-rw-rw-  1 root  wheel   18,   2 Dec 10 10:43 /dev/tty.AnujsiPhone-WirelessiAP
crw-rw-rw-  1 root  wheel   18,   0 Dec 10 10:43 /dev/tty.Bluetooth-Incoming-Port
crw-rw-rw-  1 root  wheel   18,   4 Dec 10 10:43 /dev/tty.Siddhartha-Bluetooth-In
crw-rw-rw-  1 root  wheel   18,  14 Dec 10 10:44 /dev/tty.usbserial-1423B

can you please share the output of the following commands

uname -a
libusb-config --version
lsusb
I'll try reproducing the bug on my end

niknaknet
@niknaknet
Dec 10 2015 09:58
it appears that the POST connections are aborting when i submit the configuration form - this is true on both Firefox and Safari (mac) occasionally they succeed, and sometimes i get a 400 Bad Request
Nikita Nerkar
@nikitanerkar
Dec 10 2015 10:13
@niknaknet : So the way I see it is, device boots up in micro-AP mode with SSID aws_starter-WXYZ and you connect your MAC device to this micro-AP. And then you open configuration page on 192.168.10.1 (Make sure that you open only one configuration page on either Firefox or Safari). After entering the details and posting it on the device, the device is failing to receive the details right ? Are there any debug prints device side ?
Nikita Nerkar
@nikitanerkar
Dec 10 2015 10:26
This message was deleted
niknaknet
@niknaknet
Dec 10 2015 14:00
no debug prints device side, and the four posts vary, but usually it's the cert and key that fail, with occasional fails on the region and thing name
... running the posts independently doesn't help either.
Chris Kurtz
@xoff00
Dec 10 2015 16:16
@anujdeshpande Thanks, the reset via flash.py does reset the board, but not to the code itself (so I can redo setup), and minicom output shows that it thinks it connected to wifi but is failed to reach amazon (which may or may not be true, there may be a captive portal in the way, I'm waiting on seeing if I can get the MAC whitelisted)
Chris Kurtz
@xoff00
Dec 10 2015 16:27
@anujdeshpande @niknaknet Ah, I got it reset using GPIO24 (I noticed it's connected to a button, convenient!). Thanks!
niknaknet
@niknaknet
Dec 10 2015 22:56
@xoff00 i'd be interested to know what's going on on the wire between your browser and the board - i use firebug to see what's happening in that conversation... do you see anything like what i see?