Training Class: MQX RTOS for Kinetis SDK, Kinetis Design Studio (6 labs, including TCP/IP)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Training Class: MQX RTOS for Kinetis SDK, Kinetis Design Studio (6 labs, including TCP/IP)

Training Class: MQX RTOS for Kinetis SDK, Kinetis Design Studio (6 labs, including TCP/IP)

Here is a hands-on training session for MQX RTOS with KSDK

Based on

Kinetis Design Studio (KDS) v2.0.0

Kinetis SDK v1.1.0

FRDM-K64F

The agenda for the content is:

•RTOS Theory

−Scheduling

−Tasks Communication

•MQX RTOS Basics

−Tasks

−LAB 1 – Get the Tools Working

−LAB 2 – Using Tasks

•MQX RTOS Services

−Mutex

−Semaphores

−Events

−Messages

−Interrupt Handling

−LAB 3 – Using MQX RTOS Services

•MQX RTOS for Kinetis SDK

−KSDK Architecture

−MQX Integration with KSDK

−Startup

−BSP Configuration

−Using KSDK Drivers with MQX

−Other New Features

•Ethernet Connectivity with MQX

−Initialization

−Sockets (Client-Server Model)

−LAB 4 – Client-Server

−Web Server

−LAB 5 – HTTP Server

−Ethernet Hardware

•Memory File System

•USB Stack

−Overview, Diagram, Documentation

•Using Processor Expert with MQX RTOS for KSDK

−LAB 6 – Using PEx with MQX for KSDK

•Hardware Support

−Freedom Platform

•IDE Options

−KDS

•Porting a MQX for KSDK Application

•Installation

•Evolution and Roadmap

•Support and Resources

Attachments
Comments

Congratulations ! Very good your training!

Using your guide I create e new project for a custom board using KSDK + PEx and then I add MQX like your example.

Looking the way HAL and FSL work I think is not any more necessary create a BSP. PEx take care of the hardware configuration.

Then I create tasks, RS232 for debug is Ok, interrupts GPIO when MCU is wake and for LLWU when is in STOP and everithing is working

But I note when I change my clock using:

Starts in clock #0 at 48Mhz

CLOCK_SYS_SetConfiguration(&clockMan1_InitConfig1);  // Will run in 4Mhz for Low power mode

the _time_delay()  function from MQX not work as expectec taking much more time to execute, I think because the clock #1 I´m running in lower clock.

then I call:

POWER_SYS_SetMode(1U, kPowerManagerPolicyAgreement);   // put in STOP mode LLS

And is in LLS just fine.

My question is:  How can I tell to MQX that the clock changed to calculate the _time_delay()  correctly?

Thank you

%3CLINGO-SUB%20id%3D%22lingo-sub-1099688%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3ETraining%20Class%3A%20MQX%20RTOS%20for%20Kinetis%20SDK%2C%20Kinetis%20Design%20Studio%20(6%20labs%2C%20including%20TCP%2FIP)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1099688%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHere%20is%20a%20hands-on%20training%20session%20for%20MQX%20RTOS%20with%20KSDK%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3EBased%20on%3C%2FP%3E%3CP%3EKinetis%20Design%20Studio%20(KDS)%20v2.0.0%3C%2FP%3E%3CP%3EKinetis%20SDK%20v1.1.0%3C%2FP%3E%3CP%3EFRDM-K64F%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3EThe%20agenda%20for%20the%20content%20is%3A%3C%2FP%3E%3CP%3E%E2%80%A2RTOS%20Theory%3C%2FP%3E%3CP%3E%E2%88%92Scheduling%3C%2FP%3E%3CP%3E%E2%88%92Tasks%20Communication%3C%2FP%3E%3CP%3E%E2%80%A2MQX%20RTOS%20Basics%3C%2FP%3E%3CP%3E%E2%88%92Tasks%3C%2FP%3E%3CP%3E%3CSTRONG%3E%E2%88%92LAB%201%20%E2%80%93%20Get%20the%20Tools%20Working%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3E%E2%88%92LAB%202%20%E2%80%93%20Using%20Tasks%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%E2%80%A2MQX%20RTOS%20Services%3C%2FP%3E%3CP%3E%E2%88%92Mutex%3C%2FP%3E%3CP%3E%E2%88%92Semaphores%3C%2FP%3E%3CP%3E%E2%88%92Events%3C%2FP%3E%3CP%3E%E2%88%92Messages%3C%2FP%3E%3CP%3E%E2%88%92Interrupt%20Handling%3C%2FP%3E%3CP%3E%3CSTRONG%3E%E2%88%92LAB%203%20%E2%80%93%20Using%20MQX%20RTOS%20Services%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%E2%80%A2MQX%20RTOS%20for%20Kinetis%20SDK%3C%2FP%3E%3CP%3E%E2%88%92KSDK%20Architecture%3C%2FP%3E%3CP%3E%E2%88%92MQX%20Integration%20with%20KSDK%3C%2FP%3E%3CP%3E%E2%88%92Startup%3C%2FP%3E%3CP%3E%E2%88%92BSP%20Configuration%3C%2FP%3E%3CP%3E%E2%88%92Using%20KSDK%20Drivers%20with%20MQX%3C%2FP%3E%3CP%3E%E2%88%92Other%20New%20Features%3C%2FP%3E%3CP%3E%E2%80%A2Ethernet%20Connectivity%20with%20MQX%3C%2FP%3E%3CP%3E%E2%88%92Initialization%3C%2FP%3E%3CP%3E%E2%88%92Sockets%20(Client-Server%20Model)%3C%2FP%3E%3CP%3E%3CSTRONG%3E%E2%88%92LAB%204%20%E2%80%93%20Client-Server%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%E2%88%92Web%20Server%3C%2FP%3E%3CP%3E%3CSTRONG%3E%E2%88%92LAB%205%20%E2%80%93%20HTTP%20Server%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%E2%88%92Ethernet%20Hardware%3C%2FP%3E%3CP%3E%E2%80%A2Memory%20File%20System%3C%2FP%3E%3CP%3E%E2%80%A2USB%20Stack%3C%2FP%3E%3CP%3E%E2%88%92Overview%2C%20Diagram%2C%20Documentation%3C%2FP%3E%3CP%3E%E2%80%A2Using%20Processor%20Expert%20with%20MQX%20RTOS%20for%20KSDK%3C%2FP%3E%3CP%3E%3CSTRONG%3E%E2%88%92LAB%206%20%E2%80%93%20Using%20PEx%20with%20MQX%20for%20KSDK%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%E2%80%A2Hardware%20Support%3C%2FP%3E%3CP%3E%E2%88%92Freedom%20Platform%3C%2FP%3E%3CP%3E%E2%80%A2IDE%20Options%3C%2FP%3E%3CP%3E%E2%88%92KDS%3C%2FP%3E%3CP%3E%E2%80%A2Porting%20a%20MQX%20for%20KSDK%20Application%3C%2FP%3E%3CP%3E%E2%80%A2Installation%3C%2FP%3E%3CP%3E%E2%80%A2Evolution%20and%20Roadmap%3C%2FP%3E%3CP%3E%E2%80%A2Support%20and%20Resources%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1099688%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHere%20is%20a%20hands-on%20training%20session%20for%20MQX%20RTOS%20with%20KSDK%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3EBased%20on%3C%2FP%3E%3CP%3EKinetis%20Design%20Studio%20(KDS)%20v2.0.0%3C%2FP%3E%3CP%3EKinetis%20SDK%20v1.1.0%3C%2FP%3E%3CP%3EFRDM-K64F%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3EThe%20agenda%20for%20the%20content%20is%3A%3C%2FP%3E%3CP%3E%E2%80%A2RTOS%20Theory%3C%2FP%3E%3CP%3E%E2%88%92Scheduling%3C%2FP%3E%3CP%3E%E2%88%92Tasks%20Communication%3C%2FP%3E%3CP%3E%E2%80%A2MQX%20RTOS%20Basics%3C%2FP%3E%3CP%3E%E2%88%92Tasks%3C%2FP%3E%3CP%3E%3CSTRONG%3E%E2%88%92LAB%201%20%E2%80%93%20Get%20the%20Tools%20Working%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3E%E2%88%92LAB%202%20%E2%80%93%20Using%20Tasks%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%E2%80%A2MQX%20RTOS%20Services%3C%2FP%3E%3CP%3E%E2%88%92Mutex%3C%2FP%3E%3CP%3E%E2%88%92Semaphores%3C%2FP%3E%3CP%3E%E2%88%92Events%3C%2FP%3E%3CP%3E%E2%88%92Messages%3C%2FP%3E%3CP%3E%E2%88%92Interrupt%20Handling%3C%2FP%3E%3CP%3E%3CSTRONG%3E%E2%88%92LAB%203%20%E2%80%93%20Using%20MQX%20RTOS%20Services%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%E2%80%A2MQX%20RTOS%20for%20Kinetis%20SDK%3C%2FP%3E%3CP%3E%E2%88%92KSDK%20Architecture%3C%2FP%3E%3CP%3E%E2%88%92MQX%20Integration%20with%20KSDK%3C%2FP%3E%3CP%3E%E2%88%92Startup%3C%2FP%3E%3CP%3E%E2%88%92BSP%20Configuration%3C%2FP%3E%3CP%3E%E2%88%92Using%20KSDK%20Drivers%20with%20MQX%3C%2FP%3E%3CP%3E%E2%88%92Other%20New%20Features%3C%2FP%3E%3CP%3E%E2%80%A2Ethernet%20Connectivity%20with%20MQX%3C%2FP%3E%3CP%3E%E2%88%92Initialization%3C%2FP%3E%3CP%3E%E2%88%92Sockets%20(Client-Server%20Model)%3C%2FP%3E%3CP%3E%3CSTRONG%3E%E2%88%92LAB%204%20%E2%80%93%20Client-Server%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%E2%88%92Web%20Server%3C%2FP%3E%3CP%3E%3CSTRONG%3E%E2%88%92LAB%205%20%E2%80%93%20HTTP%20Server%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%E2%88%92Ethernet%20Hardware%3C%2FP%3E%3CP%3E%E2%80%A2Memory%20File%20System%3C%2FP%3E%3CP%3E%E2%80%A2USB%20Stack%3C%2FP%3E%3CP%3E%E2%88%92Overview%2C%20Diagram%2C%20Documentation%3C%2FP%3E%3CP%3E%E2%80%A2Using%20Processor%20Expert%20with%20MQX%20RTOS%20for%20KSDK%3C%2FP%3E%3CP%3E%3CSTRONG%3E%E2%88%92LAB%206%20%E2%80%93%20Using%20PEx%20with%20MQX%20for%20KSDK%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%E2%80%A2Hardware%20Support%3C%2FP%3E%3CP%3E%E2%88%92Freedom%20Platform%3C%2FP%3E%3CP%3E%E2%80%A2IDE%20Options%3C%2FP%3E%3CP%3E%E2%88%92KDS%3C%2FP%3E%3CP%3E%E2%80%A2Porting%20a%20MQX%20for%20KSDK%20Application%3C%2FP%3E%3CP%3E%E2%80%A2Installation%3C%2FP%3E%3CP%3E%E2%80%A2Evolution%20and%20Roadmap%3C%2FP%3E%3CP%3E%E2%80%A2Support%20and%20Resources%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1099689%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3ERe%3A%20Training%20Class%3A%20MQX%20RTOS%20for%20Kinetis%20SDK%2C%20Kinetis%20Design%20Studio%20(6%20labs%2C%20including%20TCP%2FIP)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1099689%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3ECongratulations%20!%20Very%20good%20your%20training!%20%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3EUsing%20your%20guide%20I%20create%20e%20new%20project%20for%20a%20custom%20board%20using%20KSDK%20%2B%20PEx%20and%20then%20I%20add%20MQX%20like%20your%20example.%20%3C%2FP%3E%3CP%3ELooking%20the%20way%20HAL%20and%20FSL%20work%20I%20think%20is%20not%20any%20more%20necessary%20create%20a%20BSP.%20PEx%20take%20care%20of%20the%20hardware%20configuration.%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3EThen%20I%20create%20tasks%2C%20RS232%20for%20debug%20is%20Ok%2C%20interrupts%20GPIO%20when%20MCU%20is%20wake%20and%20for%20LLWU%20when%20is%20in%20STOP%20and%20everithing%20is%20working%3C%2FP%3E%3CP%3EBut%20I%20note%20when%20I%20change%20my%20clock%20using%3A%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3EStarts%20in%20clock%20%230%20at%2048Mhz%3C%2FP%3E%3CP%3ECLOCK_SYS_SetConfiguration(%26amp%3BclockMan1_InitConfig1)%3B%26nbsp%3B%20%2F%2F%20Will%20run%20in%204Mhz%20for%20Low%20power%20mode%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3Ethe%20_time_delay()%26nbsp%3B%20function%20from%20MQX%20not%20work%20as%20expectec%20taking%20much%20more%20time%20to%20execute%2C%20I%20think%20because%20the%20clock%20%231%20I%C2%B4m%20running%20in%20lower%20clock.%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3Ethen%20I%20call%3A%20%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3EPOWER_SYS_SetMode(1U%2C%20kPowerManagerPolicyAgreement)%3B%26nbsp%3B%26nbsp%3B%20%2F%2F%20put%20in%20STOP%20mode%20LLS%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3EAnd%20is%20in%20LLS%20just%20fine.%20%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3EMy%20question%20is%3A%26nbsp%3B%20How%20can%20I%20tell%20to%20MQX%20that%20the%20clock%20changed%20to%20calculate%20the%20_time_delay()%26nbsp%3B%20correctly%3F%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3EThank%20you%3C%2FP%3E%3C%2FLINGO-BODY%3E
No ratings
Version history
Last update:
‎05-01-2015 08:54 AM
Updated by: