Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [threadx] What is the future of the Azure RTOS ThreadX training once Eclipse ThreadX is up and running?
  • From: Stefan Wick <swick@xxxxxxxxxxxxx>
  • Date: Wed, 31 Jan 2024 17:12:26 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=pXYFIr7jmU9ptLjNd8mB83ntSbTKR8/0HJNet2Sb1O8=; b=LO7yPChzPWB1gdcUNUqMHNKVYoUVCQjIAE+FaSNCXbzl/y8E/diqUvmxH6Iw5Hq7lqf87lAzrezyO8pKzUUmaJsEMVJWDOzVABvN1C4n9FCba+Y6VFzNa51qrz4MYvVoL66nZkPOX07gZGu2KQ2B35GByrQYx2NFty6ZQZL4MIV91wOzjR4m6HkJUsxpg3093o7Ufg3DFImGJeXQbEtVnNvsCpZPDoisRGXMMWWWSehLz7i7APGiTwarj0U0dChk8DuysIZJrcdPyGG3T+NAjtA8k/9CTJz10nyP/YsZMJ2JMafN1QDVqtIeLGl3ruuxZkhAzZ0Ke9EP0fKrGaIQBQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=DXokqs69ehkNdxhPKl2lWN31xBJEjxWNkPsizwaO798W488eERQECPDu0px483pNTTfDy2uNq5FAqetao5/Fzk6zcdrxJSUeI1Hhai77sUsH2wa0zlZFGXPzFb3dkiiFIILRXRleg7rqa8jASI4dpeULow2QHKWk5/9C9s3vFFHkbsmMOP8Jo2l4QIZHV9Jz9Xe9O6OqpaNU5jF4OBIqaL/9Cm8YlSpZ0k1MwbKFpWjzoQR/jz2/DEkDUUNWGuWMyYF3sLjftrj6/WOaVQq/2EzZN4uNtYkAPFRT28MTU+5LjPU3SLefW4HqR3dP+RWJ6pHPOSK1fSYMWyF0v/KB+g==
  • Delivered-to: threadx@xxxxxxxxxxx
  • List-archive: <https://www.eclipse.org/mailman/private/threadx/>
  • List-help: <mailto:threadx-request@eclipse.org?subject=help>
  • List-subscribe: <https://www.eclipse.org/mailman/listinfo/threadx>, <mailto:threadx-request@eclipse.org?subject=subscribe>
  • List-unsubscribe: <https://www.eclipse.org/mailman/options/threadx>, <mailto:threadx-request@eclipse.org?subject=unsubscribe>
  • Msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ActionId=8b3825a5-8e46-4e53-afad-5149220e612f; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ContentBits=0; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=true; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Method=Standard; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=Internal; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2024-01-31T17:10:06Z; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47;
  • Thread-index: AdpUZ3jhIPiryc4vSW+x4CcpUQVVKQAAN2BQ
  • Thread-topic: What is the future of the Azure RTOS ThreadX training once Eclipse ThreadX is up and running?

Hi Jason,

 

Thanks for your interest in ThreadX. We are planning to migrate all relevant and applicable Azure RTOS learning content over to Eclipse ThreadX. The transition is currently in progress.

 

Stefan Wick

 

From: threadx <threadx-bounces@xxxxxxxxxxx> On Behalf Of Jason Armistead via threadx
Sent: Wednesday, January 31, 2024 9:04 AM
To: threadx@xxxxxxxxxxx
Cc: Jason Armistead <Jason.Armistead@xxxxxxx>
Subject: [EXTERNAL] [threadx] What is the future of the Azure RTOS ThreadX training once Eclipse ThreadX is up and running?

 

Some people who received this message don't often get email from threadx@xxxxxxxxxxx. Learn why this is important

Hi all

 

At present Microsoft Learn hosts a nearly 9 hour long online training course for ThreadX at

 

 

I only recently came across this, and it seems like a really good way to introduce developers to ThreadX

 

I am hoping there’s plans to migrate this to Eclipse Foundation’s servers going forward.

 

Regards

Jason Armistead

 

 

This E-mail message may contain confidential information. It is only for the use of the individual or entity named. If you are not the intended recipient, or the employee or agent responsible to deliver it to the intended recipient, you are notified that your dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify us by return E-mail.

Back to the top