Develop #3
Develop #3
Conversation
….com/aws/{ThingName};PAI-310: Updated description of .cfg file production.;
…n this update, pull up is enabled for the UART2 Rx (PF1) pin on ATmega4808.;
…more simple;PAI-310: Minor images fixes;PAI-310: not done; but ready to review.;PAI-310: Point to release tab; specified the yellow shadow toggle behavior.;PAI-310: Fix picture text.;
…e;PAI-310 replace image;PAI-310 replace delta toggle subscribe image;Updated the readme.md file for the DeltaToggle image to be displayed.;Removed the duplicate deltaToggleSub image.;
… focuses on the AVR platform. Also added the description of th WEP option used to connect to a Wi-Fi network.;
…ved to IoT_Sensor_Node_config.h;PAI-351 edits;PAI-351 macro to print debug messages renamed;PAI-351 cloud sub module reference updated;
…e received payload;PAI-351 cloudSubmodule and iotApplicationSubmoudle reference updated;
…e updated to reflect removal of header inclusions and API changes in cloud_service.h;PAI-387 iotApplication and cloud submodule reference updated to reflect migration of debug_print.c/.h;
…ROM_WINC";PAI-397 the tag to use custom endpoint url updated and hence fmpp config is modified;PAI-397 useCustomEndpointURL set to false;
…oved to "mcc_generated_files" directory;
…lication submodule reference updated;PAI-397 cloud submoduel reference updated;
…I-404 eidts in AWS multiaccount registration - readme;
…ml and ivysettings.xml updated to reflect the new folder structure;
…ince they will be generated on-the-fly using FMPP process.;PAI-435 Updated the tokens of the CAL library to generate exactly those files which are generated by MCC CAL v2.0.0 library. The MCC AVR IoT WA/WG example also generates essentially the same files.;PAI-435 Updated the commit number of the cryptoAuthLibSubmodule to pull the latest files.;PAI-435 Updating the submodule commit number to bring in the latest CAL files.;
shaimahusain
added
question
|
|
Please check the develop branch where the "readAWSEndpointFromWinc" API has been refactored. |
…in Metadata;changing toolchain version in metadata;changes in metadata file;mcc core version fix in metadata;
…erify metada stage moved out of deploy stage;
…he Server Name Indication (SNI) update.;
…4.1.0;PAI-633 Updated the tag name to RC1;
…596 portal deploy notififcation;PAI-596 edits in sending notification API call;
…ed for deployment;PAI-982 xc9-mplab image updated;PAI-982 metadata updated;PAI-982 metadata updated;PAI-982 metadata updated;
…eference updated, version in metadat updated;PAI-983 update in ivy;
…ified;PAI-983 update to metadata;PAI-983 build.xml update;PAI-983 updated hex dir in build.xml;PAI-983 update to fix path;PAI-983 fix for getting the right links in notification;PAI-983 updating version in ivy and metadata;
…b-module updated;PAI-1006 hotfix rc2;PAI-1006 ivy and metadat update for 4.1.2 release;
Hi,
I needed to modify wifi_service.c file to use custom configuration correctly.
The modification was remove awsEndpoint[AWS_ENDPOINT_LEN-1] form the vefirification.
status = spi_flash_read(awsEndpoint, AWS_ENDPOINT_FLASH_OFFSET, AWS_ENDPOINT_LEN);
if(status != M2M_SUCCESS || awsEndpoint[0] == 0xFF ) //Modification - X45079
{
sprintf(awsEndpoint, "%s", CFG_MQTT_HOSTURL);
debug_printIoTAppMsg("Custom endpoint not present, using the default endpoint which the hardware was pre-provisioned for : %s", awsEndpoint);
}
else
...
Line 181