Are you ready for kernel 3.10.53? Learn how to boot with the device tree, understand bindings and syntax today. Presented by Massimo Bonazzi Presented at DwF Istanbul and Ankara - May 12 and 14, 2015 Session ID: EUF-DES-T1465

Introduce Freescale high-performance and high integrated MCU products for bootloader. Presented by David Chen Presented at DwF Taipei - May 7, 2015 Session ID: APF-DES-T1456

The MQX software release provides the makefiles to build MQX software libraries and applications from the Windows® operating system. This video shows how to build the MQX software libraries (BSP and PSP) and the hello MQX example for the TWR-K60D100M. The same instructions apply for all other BSPs and examples. For more details about how to use the makefiles to build MQX libraries and applications, please check the "Using Eclipse and GDB with Freescale MQX™ RTOS User's Guide" document, you can find this document after install MQX at the path: C:\Freescale\Freescale_MQX_4_2\doc\tools\gnu Regards Soledad

This is a 1-day Hands-On training for Kinetis Software Development Kit (KSDK) and MQX Real-Time Operating System.  The file includes the training presentation, lab software and lab guides.  The training agenda is: •Kinetis Overview −K24/K64 Details −Kinetis Hardware and Software Enablement •MQX Overview •Kinetis Software Development Kit (KSDK) Overview −HAL, Drivers, OSA Overview •MQX Comparison •MQX Startup and Initialization •KSDK Clock Manager •KSDK Power Manager •Porting KSDK to custom hardware •Interrupts in MQX for KSDK •MQX Support •Processor Expert with MQX/KSDK •Additional References The training focuses on KSDK v1.2.0, and the labs use the Keil MDK-ARM toolchain with the TWR-K64F120M development board.

Learn about what is an IoT Gateway? What are the feature requirements for different types of IoT Gateways? Why security is important and how Freescale addresses these needs? You will also learn about the connectivity options and software enablement for IoT solutions. Presented at DwF IoT Wireless Module Solutions - Jinan - April 23, 2015 & Guangzhou - June 11, 2015 Session ID: APF-SNT-T1356

Presented by Li Jun Presented at DwF RF Solutions - Chengdu - 9 April 2015

This session will introduce i.MX 6 series hardware design reference board and will walk through the i.MX 6 series SDP schematic. The session will also introduce hardware design consideration including the hardware checking list to facilitate the hardware design and development. Additionally i.MX6D/Q/DL/Solo power design and how to use DDR calibration will be covered. At the end of session, will share the experience of i.MX 6 hardware bring up. Presented at DwF Kinetis MCUs Based on ARM® Technology - Tianjin - 19 March 2015 Session ID: APF-DES-T1023

Presented by Bruce Tsai Presented at DwF Hsinchu

Presented by Geoff Lees and John Dixon Presented at DwF Silicon Valley - March 26, 2015

Presented by Bill Zheng Presented at DwF RF Solutions - Wuhan - 13 August 2015

The i.MX 8QuadXPlus Multisensory Enablement Kit (MEK) is a NXP development platform based on Cortex A-35 + Cortex-M4 cores. Built with high-level integration to support graphics, video, image processing, audio, and voice functions, the i.MX 8X processor family is ideal for safety-certifiable and efficient performance requirements. This tutorial shows how to enable the Cortex-M4 using the MCUXpresso SDK package and loading the binary from the network. NOTE: It is also possible to load the Cortex-M4 image from the SCFW using the imx-mkimage utility. Please see next blog posts for this tutorial. Setting up the machine NOTE: This shows the procedure for a Linux environment. For the Windows OS, please see the Getting Started documentation on the SDK package. Install cmake on the host machine: $ sudo apt-get install cmake Download the armgcc toolchain from here :https://launchpad.net/gcc-arm-embedded/5.0/5-2016-q2-update/+download/gcc-arm-none-eabi-5_4-2016q2-20160622-linux.tar.bz2  and export the location as ARMGCC_DIR: $ export ARMGCC_DIR=<your_path_to_arm_gcc>/gcc-arm-none-eabi-5_4-2016q2/ NOTE: The ARMGCC_DIR variable needs to be exported on the terminal used for compilation. To setup the TFTP server on the host machine, follow the first two sections on this blog post https://imxdev.gitlab.io/tutorial/How_to_boot_Kernel_and_File_System_from_the_network/ (Configuring your Host PC for TFTP and Configuring your Host PC for NFS). Downloading the SDKPermalink Download the MCUXpresso SDK following these steps: Click on “Select Development Board”; Select MEK-MIMX8QX under “Select a Device, Board, or Kit” and click on “Build MCUXpresso SDK” on the right; Select “Host OS” as Linux and “Toolchain/IDE” as GCC ARM Embedded; Add “FreeRTOS” and all the wanted Middleware and hit “Request Build”; Wait for the SDK to build and download the package. Building the image All demos and code examples available on the SDK package are located in the directory <<SDK_dir>>/boards/mekmimx8qx/. This tutorial shows how to build and flash the hello_world demo but similar procedures can be applied for any example (demo, driver, multicore, etc) on the SDK. To build the demo, enter the armgcc folder under the demo directory and make sure that the ARMGCC_DIR variable is set correctly. $ cd ~/SDK_2.3.0_MEK-MIMX8QX/boards/mekmimx8qx/demo_apps/hello_world/armgcc $ export ARMGCC_DIR=<your_path_to_arm_gcc>/gcc-arm-none-eabi-5_4-2016q2/ Run the build_release.sh script to build the code. $ ./build_release.sh NOTE: If needed, give the script execution permission by running chmod +x build_release.sh. This generates the M4 binary (hello_world.bin) under the release folder. Copy this image to the /tftpboot/ directory on the host PC. NOTE: This procedure shows how to build the M4 image that runs on TCM. To run the image from DDR, use the build_ddr_release.sh script to build the binary under the ddr_release folder. Flashing the image Open two serial consoles, one for /dev/ttyUSB0 for Cortex-A35 to boot Linux, and one for /dev/ttyUSB1 for Cortex-M4 to boot the SDK image. On the A35 console, with a SD Card with U-Boot, stop the booting process and enter the following commands to load the M4 binary to TCM: => dhcp => setenv serverip <ip_from_host_pc> => tftp 0x88000000 hello_world.bin => dcache flush => bootaux 0x88000000 Then the M4 core will load the image to the /dev/ttyUSB1 console.    

The i.MX 6UltraLite EVK kernel release includes the parallel camera OV5640 support by default. However, depending on the base board revision, this camera might require the SCH700-27820 adapter below: Camera Adapter According to the following image, the FX12B-40P-0.4SV connector layout was changed in the RevC, giving the possibility to use the OV5640 directly:   Rev B in the left and Rev C in the right, which does not need the adapter So, if you are using a base board older than Rev C, plug in the camera with the adapter and connect the other end of the adapter to the board.   In order to use the parallel OV5640 camera, it’s necessary to set up the environment variable below on U-Boot, independent of the base board revision: => setenv fdt_file ‘imx6ul-14x14-evk-csi.dtb’ => saveenv Follow the GStreamer pipeline example to test the camera connection: $ gst-launch-1.0 v4l2src device=/dev/video1 ! video/x-raw,width=640,height=480 ! autovideosink   This test was done using the kernel BSP release 5.10.35v.  

This section describes some advanced topics and tips to get high experiences in camera use cases in the i.MX 8 boards The i.MX 8QM MEK includes the use of the dual MIPI-CSI interfaces and two MX8XMIPI4CAM2 in combination with eight MCIMXCAMERA1MP daughter cards connected to them. For this, change the DTB file to fsl-imx8qm-mek-8cam.dtb and boot the board. Figure 1. Show i.MX 8QM MEK 8 cameras example.   Multiple cameras output In order to use more than one camera at the same time displayed in the same monitor output, boot the board and enter with the following command line to get the cameras ids: $ v4l2-ctl --list-devices It will result in something similar to the image below: Figure 2. v4l2-ctl results According to the image, mxc-isi found and set four cameras to /dev/video0, video1, video2, and video3. So we can build the GStreamer pipeline below changing it as required: $ gst-launch-1.0 -v imxcompositor_g2d name=comp \ sink_0::xpos=0 sink_0::ypos=0 sink_0::width=640 sink_0::height=480 \ sink_1::xpos=0 sink_1::ypos=480 sink_1::width=640 sink_1::height=480 \ sink_2::xpos=640 sink_2::ypos=0 sink_2::width=640 sink_2::height=480 \ sink_3::xpos=640 sink_3::ypos=480 sink_3::width=640 sink_3::height=480 \ ! video/x-raw,format=RGB16 ! waylandsink \ v4l2src device=/dev/video0 ! video/x-raw,width=640,height=480 ! comp.sink_0 \ v4l2src device=/dev/video1 ! video/x-raw,width=640,height=480 ! comp.sink_1 \ v4l2src device=/dev/video2 ! video/x-raw,width=640,height=480 ! comp.sink_2 \ v4l2src device=/dev/video3 ! video/x-raw,width=640,height=480 ! comp.sink_3   This pipeline enables the user to set up more than one camera to the same screen using the imxcompositor_g2d for it. This is the unique solution available to create an interface over Weston/Wayland interface, i.e., in i.MX 8 devices we need to use GPU to create interfaces GUI. This pipeline results in the image below: Figure 3. GStreamer 4 cameras output It is just an example and you are encouraged to change it for other camera use cases, such as the eight cameras supported by the i.MX 8QM MEK.          

Presented by Tiefeng Shi Presented at DwF RF Solutions - Chengdu - 9 April 2015

Design, Software and Services Insight and Innovation Smart Industry

Microcontroller Products and Solutions - Hsinchu Advanced Design with Freescale Wireless Charger Solutions Wireless Connectivity for the Internet of Things QorIQ SDN Service Switch Solution

Freescale QorIQ based access point/router is a complete production-ready, Bill of Materials (BOM)-optimized solution that can support single- or dual-radio 802.11 a/b/g/n/ac devices through MiniPCI or Mini PCI Express® interfaces.  Presented by Jason Wang Presented at DwF Taipei - May 7, 2015 Session ID: APF-SNT-T1460

Automotive and Connected Car Smart Industry Smart Networks