Nrf sample app aws iot - Revision history

Ted: /* AWS_IOT_ events */

2022-01-24T16:31:53Z

AWS_IOT_ events

2022-01-24T16:21:58Z

AWS_IOT_ events

2022-01-24T16:03:43Z

Add new page section "AWS_IOT_ events".

2021-10-05T22:45:30Z

OVERVIEW

2021-10-05T22:41:04Z

^ Toolchain Variant Matters

2021-09-27T21:14:38Z

^ References

2021-09-20T23:59:05Z

^ References

2021-09-20T23:51:33Z

^ References

2021-09-19T07:13:18Z

^ Build and Execution on nRF9160 DK Board

2021-09-19T04:28:45Z

← Older revision		Revision as of 16:31, 24 January 2022
Line 3,168:		Line 3,168:
	</pre>		</pre>

		+	And here are the event types from the same file . . .
		+
		+	<i>figure x - excerpt from nrf/include/net/aws_iot.h</i>
		+
		+	<pre>
		+	79 /** @brief AWS IoT notification event types, used to signal the application. */
		+	80 enum aws_iot_evt_type {
		+	81 /** Connecting to AWS IoT broker. */
		+	82 AWS_IOT_EVT_CONNECTING = 0x1,
		+	83 /** Connected to AWS IoT broker. */
		+	84 AWS_IOT_EVT_CONNECTED,
		+	85 /** AWS IoT library has subscribed to all configured topics. */
		+	86 AWS_IOT_EVT_READY,
		+	87 /** Disconnected to AWS IoT broker. */
		+	88 AWS_IOT_EVT_DISCONNECTED,
		+	89 /** Data received from AWS message broker. */
		+	90 AWS_IOT_EVT_DATA_RECEIVED,
		+	91 /** FOTA update start. */
		+	92 AWS_IOT_EVT_FOTA_START,
		+	93 /** FOTA update done, request to reboot. */
		+	94 AWS_IOT_EVT_FOTA_DONE,
		+	95 /** FOTA erase pending. */
		+	96 AWS_IOT_EVT_FOTA_ERASE_PENDING,
		+	97 /** FOTA erase done. */
		+	98 AWS_IOT_EVT_FOTA_ERASE_DONE,
		+	99 /** FOTA progress notification. */
		+	100 AWS_IOT_EVT_FOTA_DL_PROGRESS,
		+	101 /** FOTA error. Used to propagate FOTA-related errors to the
		+	102 * application. This is to distinguish between AWS_IOT irrecoverable
		+	103 * errors and FOTA errors, so they can be handled differently.
		+	104 */
		+	105 AWS_IOT_EVT_FOTA_ERROR,
		+	106 /** AWS IoT library irrecoverable error. */
		+	107 AWS_IOT_EVT_ERROR
		+	108 };
		+	</pre>

← Older revision		Revision as of 16:21, 24 January 2022
Line 3,153:		Line 3,153:
	</pre>		</pre>

−	The header file `[west_workspace]/nrf/include/net/aws_iot.h` defines symbol AWS_IOT_EVT_DISCONNECTED . . .	+	The header file `[west_workspace]/nrf/include/net/aws_iot.h` defines symbol AWS_IOT_EVT_DISCONNECTED . . . ok here is an interesting enumeration, looks like we may be able to tell with some granularity what is the reason for losing an AWS client connection to remote host:
		+
		+	<i>figure x - excerpt from nrf/include/net/aws_iot.h</i>
		+
		+	<pre>
		+	50 /*@ AWS broker disconnect results. /
		+	51 enum aws_disconnect_result {
		+	52 AWS_IOT_DISCONNECT_USER_REQUEST,
		+	53 AWS_IOT_DISCONNECT_CLOSED_BY_REMOTE,
		+	54 AWS_IOT_DISCONNECT_INVALID_REQUEST,
		+	55 AWS_IOT_DISCONNECT_MISC,
		+	56 AWS_IOT_DISCONNECT_COUNT
		+	57 };
		+	</pre>

@@ Line 3,134: / Line 3,134: @@
 And really the larger issue we encountered and learned here is that GNU gnuarmemb cross compiler tools are needed to succeed in building Zephyr apps from within Segger and command line.  The Zephyr toolchain installs `cross-NG` compiler and associates.  Those build Zephyr apps at the command line using `west`, but fail builds initiated from withing Segger Nordic version 5.60.
-<!-- comment -->
+== AWS_IOT_ events ==
 == [[#top|^]] References ==

@@ Line 3: / Line 3: @@
 == OVERVIEW ==
 This local page contains notes on effort to extract Nordic sample Zephyr app from [https://github.com/nrfconnect/sdk-nrf nrf-sdk] and compile this sample outside of the SDK.  This sample and others still have code dependencies, and in the end we crafted a simple manifest file `west.yml` to reference Nordic's nrf-sdk.  The important achievement however is that we are able to pull out a useful sample project, limited in scope, and begin to work with it as a stand alone Zephyr app.  Same as with Kionix out-of-tree driver.
 -09-15 Update:  revisited the `west` manifest file as a <code>git checkout ... && west update && west build ...</code> failed for not found board file.  Located a [https://docs.zephyrproject.org/latest/guides/west/basics.html good document on west and west manifest files], performed following:

@@ Line 3,116: / Line 3,116: @@
 arcmwdt  cross-compile  espressif  gnuarmemb  host  llvm  oneApi  xcc  xtools  zephyr
 ted@pulse-linux:~/ncs/zephyr/cmake/toolchain$
 <!-- comment -->

@@ Line 3,106: / Line 3,106: @@
 W: Not getting time from any NTP server
 </pre>
 <!-- comment -->

@@ Line 3,110: / Line 3,110: @@
 == [[#top|^]] References ==
+Message Queuing Telemetry Transport (MQTT) related:
 *  https://docs.zephyrproject.org/latest/reference/networking/mqtt.html
 AT commands reference:
 *  https://infocenter.nordicsemi.com/index.jsp?topic=%2Fref_at_commands%2FREF%2Fat_commands%2Fintro.html
 <!-- comment -->

@@ Line 3,088: / Line 3,088: @@
 E: Could not get current system mode, error: -8
 Modem could not be configured, error: -8
 </pre>

← Older revision		Revision as of 04:28, 19 September 2021
Line 3,043:		Line 3,043:

	</pre>		</pre>
		+
		+	<!-- comment -->
		+
		+	== [[#top\|^]] Build and Execution on nRF9160 DK Board ==
		+
		+	<pre>
		+	Peripheral Domain Status
		+	00 NRF_P0 Non-Secure OK
		+	01 NRF_CLOCK Non-Secure OK
		+	02 NRF_RTC0 Non-Secure OK
		+	03 NRF_RTC1 Non-Secure OK
		+	04 NRF_NVMC Non-Secure OK
		+	05 NRF_UARTE1 Non-Secure OK
		+	06 NRF_UARTE2 Secure SKIP
		+	07 NRF_TWIM2 Non-Secure OK
		+	08 NRF_SPIM3 Non-Secure OK
		+	09 NRF_TIMER0 Non-Secure OK
		+	10 NRF_TIMER1 Non-Secure OK
		+	11 NRF_TIMER2 Non-Secure OK
		+	12 NRF_SAADC Non-Secure OK
		+	13 NRF_PWM0 Non-Secure OK
		+	14 NRF_PWM1 Non-Secure OK
		+	15 NRF_PWM2 Non-Secure OK
		+	16 NRF_PWM3 Non-Secure OK
		+	17 NRF_WDT Non-Secure OK
		+	18 NRF_IPC Non-Secure OK
		+	19 NRF_VMC Non-Secure OK
		+	20 NRF_FPU Non-Secure OK
		+	21 NRF_EGU1 Non-Secure OK
		+	22 NRF_EGU2 Non-Secure OK
		+	23 NRF_DPPIC Non-Secure OK
		+	24 NRF_REGULATORS Non-Secure OK
		+	25 NRF_PDM Non-Secure OK
		+	26 NRF_I2S Non-Secure OK
		+	27 NRF_GPIOTE1 Non-Secure OK
		+
		+	SPM: NS image at 0x20200
		+	SPM: NS MSP at 0x2001f650
		+	SPM: NS reset vector at 0x26045
		+	SPM: prepare to jump to Non-Secure image.
		+	* Booting Zephyr OS build v2.6.0-rc1-ncs1 *
		+	The AWS IoT sample started, version: v1.0.0
		+	E: Could not send AT command
		+	E: Could not get current system mode, error: -8
		+	Modem could not be configured, error: -8
		+
		+	</pre>
		+
		+	<!-- comment -->

	== [[#top\|^]] References ==		== [[#top\|^]] References ==