PIC-IoT-WA-4.1.0.hex

[allannogueras]

Hi,
I bought two PIC-IoT WA boards and plugged one of them in. After opening up the Curiocity drive and clicking CLICK-ME.HTM

https://pic-iot.com/pic-iot/aws/
I got to this landing page where it adviced me to upgrade the firmware as the first thing.

That brought me to this page on github where a version of the firmware in version 4.1.0 resided
https://github.com/microchip-pic-avr-solutions/pic-iot-aws-sensor-node/releases/tag/4.1.0

After upgrading the board with this version the board is not able to establish a connection.
I got a board with BLUE on, GREEN flashing, rest of LESD are off.

I thought for a while this was a wifi connection problem and tried to disable various levels of security. didnt help

When i plugged in the 2nd board and update the wifi settings by pulling WIFI.CFG to the curiocity drive it worked immeadtely.
I then decided to figure out if this was just a good and a bad board, so I upgraded the 2nd board, and now I have two identical boards without MQTT activity.

What am I missing here ?

thanks and regards

Allan

[Keiji-SS]

Hi.
I'm encountering the exact same problem.

I get "We couldn't retrieve recent data from your device. To connect to a network automatically, ensure the device is plugged in." and cannot connect to the network.

1)PIC-Iot-WA-4.1.0.hex---> Unable to connect
2)Compile and write the latest project---> Unable to connect
3)PIC-Iot-WA-2.0.2.hex--->Connection allowed
4)Compile and write v2.0.2 project--->Connection allowed

thanks and regards

Keiji

[tonydahb]

Echo the problems others are seeing above.

[allannogueras]

Hi,

I resolved the problem by running the iotprovisioning tool.

iotprovision-bin -c aws -m sandbox -P COM8 -ssid -psk -auth wpa-psk

Replace ssid and pass with the actual Wifi credentials ofcourse. Had to specify the COM port also since the tool wasnt able to find it .

After running the tool the sandbox demo was again able to connect to the cloud service on my two PIC-IoT-WA boards.

regards
Allan

[tonydahb]

Running the above command e.g. ./iotprovision-bin -c aws -m sandbox -ssid -psk -auth wpa-psk resulted in the following output:

Upgrading debugger firmware...

Currently installed firmware is version 1.21.37
Upgrade candidate firmware is version 1.20.25
Skipping upgrade. Attempted downgrade from 1.21.37 to 1.20.25.

Programming provisioning firmware
Erasing flash...
Programming flash...
Get provisioner FW version

Provisioning kit with serial number <removed from post> using FW version 1.1.2 at port /dev/cu.usbmodem142102

Erase WINC TLS certificate sector
    Done.

Request signer certificate

Saving signer certificate to /Users/tonydahb/.microchip-iot/signer_21DB.pem

Request device certificate

Saved device certificate in '/Users/tonydahb/.microchip-iot/<removed from post>/device_sandbox.crt'

Send Signer Certificate signer_21DB.pem
Send Device Certificate
    Done.

Transfer certificates to WINC
Error 0xf400 in xferCerts: M2M_ERR_FAIL
Provisioning failed, aborted

The lights then all turned off and will not come back on (except for the power light).

[Keiji-SS]

Hi.
The -P option was helpful.
I was able to confirm the connection to AWS by following the tutorial below.

https://github.com/microchip-pic-avr-solutions/microchip-iot-developer-guides-for-aws

Thank you very much

Keiji