Mbed/ArmMbed - Revision history

Daniel.hung at 01:39, 28 December 2018

2018-12-28T01:39:56Z

Daniel.hung at 03:52, 24 December 2018

2018-12-24T03:52:51Z

Daniel.hung at 09:43, 7 December 2018

2018-12-07T09:43:23Z

Daniel.hung at 09:40, 7 December 2018

2018-12-07T09:40:55Z

Daniel.hung at 07:52, 7 December 2018

2018-12-07T07:52:21Z

Daniel.hung at 07:32, 7 December 2018

2018-12-07T07:32:47Z

Daniel.hung at 07:18, 7 December 2018

2018-12-07T07:18:14Z

Daniel.hung: Created page with "== mbed Device Connector == mbed Device Connector can connect devices to Mbed cloud, but it's going to be deprecat..."

2018-12-07T07:15:14Z

Created page with "== mbed Device Connector == mbed Device Connector can connect devices to Mbed cloud, but it's going to be deprecat..."

New page

== mbed Device Connector ==

[[Mbed/mbed_Device_Connector|mbed Device Connector]] can connect devices to Mbed cloud, but it's going to be deprecated on the 31st of December 2018. You may refer to Arm Mbed (Pelion) Device Management for more advanced features and capabilities.

== Arm Mbed ==

=== Supported Platforms ===

'''[RISC]'''

*NXP i.MX6

:
*''RSB-4411''
:*''RSB-6410''
:*''UBC-220''

*Qualcomm APQ8016 

:
*''RSB-4760''

*TI AM335x/57xx

:
*''RSB-4220''

'''[WISE]'''

*Qualcomm IPQ806X

:
*''WISE-3610''

=== Frequently Asked Questions ===

@@ Line 95: / Line 95: @@
 '''3. No CA certificate for enrolled devices'''
 *How to solve?
 '''4. Invalid header'''

← Older revision		Revision as of 03:52, 24 December 2018
Line 97:		Line 97:

	*How to solve?		*How to solve?
		+
		+	'''4. Invalid header'''
		+
		+	[DBG ][PAAL]: arm_uc_paal_update.c:266: ARM_UCP_GetActiveFirmwareDetails
		+	[DBG ][PAAL]: arm_uc_pal_linux_implementation_internal.c:602: Extended pre-script command: /usr/sbin/arm_update_active_details.sh -h /cache/header.bin
		+	[DBG ][PAAL]: arm_uc_pal_linux_implementation_internal.c:381: header bytes: 110
		+	[ERR ][PAAL]: arm_uc_pal_linux_implementation_internal.c:404: '''<font color="#FF0000">invalid header in slot 0</font>'''
		+	[ERR ][PAAL]: arm_uc_pal_linux_implementation_internal.c:725: pre-script failed
		+	[DBG ][HUB ]: update_client_hub_event_handlers.c:185: UCFM_EVENT_GET_ACTIVE_FIRMWARE_DETAILS_ERROR
		+
		+	*How to solve?
		+
		+	:Try to remove '''header.bin''' in '''KCM '''folder. The system will generate a new one based on current images.

	==== <font color="#0070c0">Do OTA update failed</font> ====		==== <font color="#0070c0">Do OTA update failed</font> ====

@@ Line 35: / Line 35: @@
 === <font color="#0070c0">Frequently Asked Questions</font> ===
-'''[Cannot connect to Mbed]'''
+==== <font color="#0070c0">Cannot connect to Mbed</font> ====
 If Mbed client cannot connect to Mbed Cloud, you can check the syslog with the patterns below.
@@ Line 94: / Line 94: @@
    nameserver 8.8.4.4
-. No CA certificate for enrolled devices
+'''3. No CA certificate for enrolled devices'''
 *How to solve?
-'''[Do OTA update failed]'''
+==== <font color="#0070c0">Do OTA update failed</font> ====
 If OTA update procedure is not successful, you can check the syslog.
-. Failure in recovery mode
+'''1. Failure in recovery mode'''
   [INFO][mClt]: M2MNsdlInterface::send_reso'''Do update''' ...
@@ Line 126: / Line 126: @@
 :Check if OTA image size is too big? Make sure the free space of /cache is double size of new OTA image.
-. Rollback protection
+'''2. Rollback Protection'''
   [DBG ][HUB ]: update_client_hub_error_handler.c:55: error: 42480001 16

@@ Line 35: / Line 35: @@
 === <font color="#0070c0">Frequently Asked Questions</font> ===
-If Mbed client cannot connect to Mbed Cloud, you can check the syslog.
+'''[Cannot connect to Mbed]'''
-. Enrollment ID is not registered.
+If Mbed client cannot connect to Mbed Cloud, you can check the syslog with the patterns below.
   [INFO][mClt]: M2MNsdlInterface::received_from_server_callback - bootstrap message
@@ Line 59: / Line 61: @@
 :Input the enrollment id into your Mbed account.
-. DNS is invalid
+'''2. DNS is invalid'''
   [ERR ][mClt]: M2MConnectionHandlerPimpl::getAddressInfo failed with 0xFFFF0005
@@ Line 92: / Line 94: @@
    nameserver 8.8.4.4
-.
+. No CA certificate for enrolled devices

← Older revision		Revision as of 07:52, 7 December 2018
Line 34:		Line 34:

	=== <font color="#0070c0">Frequently Asked Questions</font> ===		=== <font color="#0070c0">Frequently Asked Questions</font> ===
		+
		+	If Mbed client cannot connect to Mbed Cloud, you can check the syslog.
		+
		+	1. Enrollment ID is not registered.
		+
		+	[INFO][mClt]: M2MNsdlInterface::received_from_server_callback - bootstrap message
		+	[ERR ][mClt]: M2MNsdlInterface::handle_bootstrap_error(bad-request:'''<font color="#FF0000">Enrollment ID not registered</font>''')
		+	[ERR ][mClt]: M2MInterfaceImpl::bootstrap_error(bad-request:Enrollment ID not registered)
		+	[ERR ][mClt]: ConnectorClient::error() - error: 2
		+	[ERR ][mClt]: ServiceClient::connector_error() error 2
		+	[ERR ][mClt]: ServiceClient::state_failure()
		+	[INFO][mClt]: MbedCloudClient::complete status (-1)
		+	[ERR ][mClt]: MbedCloudClient::error code (2)
		+	[ERR ][edgecc]: Error occured : MbedCloudClient::ConnectBootstrapFailed
		+	[ERR ][edgecc]: Error code : 2
		+	[ERR ][edgecc]: Error details : bad-request:Enrollment ID not registered
		+	[ERR ][mClt]: ServiceClient::state_failure()
		+	[INFO][mClt]: MbedCloudClient::complete status (-1)
		+	[INFO][mClt]: M2MInterfaceImpl::bootstrap_error - reconnecting in 4(s)
		+	[DBG ][PAL ]: SSL Read return code -26880.
		+
		+	*How to solve?
		+
		+	:Input the enrollment id into your Mbed account.
		+
		+	2. DNS is invalid
		+
		+	[ERR ][mClt]: M2MConnectionHandlerPimpl::getAddressInfo failed with 0xFFFF0005
		+	[ERR ][mClt]: M2MInterfaceImpl::socket_error: (5), retry (1), reconnecting (0), reconnection_state (0)
		+	[INFO][mClt]: M2MInterfaceImpl::socket_error - reconnecting in 4(s)
		+	[ERR ][mClt]: ConnectorClient::error() - error: 12
		+	[ERR ][mClt]: ServiceClient::connector_error() error 12
		+	[ERR ][mClt]: MbedCloudClient::error code (12)
		+	[ERR ][edgecc]: Error occured : MbedCloudClient::'''<font color="#FF0000">ConnectDnsResolvingFailed</font>'''
		+	[ERR ][edgecc]: Error code : 12
		+	[ERR ][edgecc]: Error details : Client in reconnection mode DnsResolvingFailed
		+	[ERR ][mClt]: ServiceClient::state_failure()
		+	[INFO][mClt]: MbedCloudClient::complete status (-1)
		+	[INFO][serv]: Listening 16777343 on port 22225.
		+
		+	*How to solve?
		+
		+	:Add Google DNS server into your network setting.
		+
		+	# sudo su
		+	# apt-get update
		+	# apt-get install resolvconf
		+	# vi /etc/resolvconf/resolv.conf.d/head
		+	nameserver 8.8.8.8
		+	nameserver 8.8.4.4
		+	# resolvconf -u
		+
		+	:After that, check the /etc/resolv.conf file
		+
		+	# cat /etc/resolv.conf
		+	nameserver 8.8.8.8
		+	nameserver 8.8.4.4
		+
		+	3.

@@ Line 10: / Line 10: @@
 *NXP i.MX6
+<ul style="margin-left: 40px;">
-:- ''RSB-4411''
+<li>''RSB-4411''</li>
-:- ''RSB-6410''
+<li>''RSB-6410''</li>
-:- ''UBC-220''
+<li>''UBC-220''</li>
 *Qualcomm APQ8016&nbsp;
+<ul style="margin-left: 40px;">
-:- ''RSB-4760''
+<li>''RSB-4760''</li>
 *TI AM335x/57xx
+<ul style="margin-left: 40px;">
-:- ''RSB-4220''
+<li>''RSB-4220''</li>
 '''[WISE]'''
 *Qualcomm IPQ806X
+<ul style="margin-left: 40px;">
-:- ''WISE-3610''
+<li>''WISE-3610''</li>
 === <font color="#0070c0">Frequently Asked Questions</font> ===