QorIQ T1040 Communications Processor as "Router on a Chip" See a "routing on a chip" solution on the QorIQ Processor T1040 QDS with Layer 2 switching, including Layer 2 and Layer 3 processing through the L2 switch and FMan, and detailing drivers and stacks support.       Features Integrated switching (LAN, WAN, WLAN) Firewall support with HW offload DMZ partition using NXP Embedded Hypervisor Remote administration   Featured NXP Products T1040: QorIQ T Series Quad- and Dual-Core Communications Processors Industrial

TFT ドライバ設計 (TFT ドライバ).pdf <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> この記事では、Kinetis KL シリーズと K シリーズを使用して LCD を駆動するさまざまな方法を紹介します。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> この記事では、Kinetis KL シリーズと K シリーズを使用して LCD を駆動するさまざまな方法を紹介します。

LCD43原理图.pdf SSD1963驱动4.3寸屏原理图。 SSD1963驱动4.3寸屏原理图。

LCD43 Schematic Diagram.pdf <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Schematic diagram of SSD1963 driving a 4.3-inch screen. <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Schematic diagram of SSD1963 driving a 4.3-inch screen.

[MQX 4.1.0] Patch for USB Host CDC demo MQX 4.1.0 provides a USB Host CDC demo in the folder of "C:\Freescale\Freescale_MQX_4_1\usb\host\examples\cdc\cdc_serial", but to get it work, several steps need to be done: 1. Change CDC_EXAMPLE_USE_HW_FLOW in cdc_serial.h to 1. #define CDC_EXAMPLE_USE_HW_FLOW 1 2. In config\twrk70f120m\user_config.h, interrupt mode for UART should be set.//It depends on the platform, here given TWR-K70F120M is used. #define BSPCFG_ENABLE_TTYC 0 #define BSPCFG_ENABLE_ITTYC 1 In mqx\source\bsp\twrk70f120m\twrk70f120m.h, specify 'ittyc' instead of 'ttyc' #ifndef BSP_DEFAULT_IO_CHANNEL #if BSPCFG_ENABLE_ITTYC #define BSP_DEFAULT_IO_CHANNEL "ittyc:" /* OSJTAG-COM polled mode */ #define BSP_DEFAULT_IO_CHANNEL_DEFINED #else #define BSP_DEFAULT_IO_CHANNEL NULL #endif #else 3. In usb\host\source\classes\cdc\usb_host_cdc.c, pass fd_ptr instead of data_instance as the argument. a. Around line 977 //usb_hostdev_tr_init(&tr, (tr_callback) usb_class_cdc_in_data_callback, (void *) data_instance); usb_hostdev_tr_init(&tr, (tr_callback) usb_class_cdc_in_data_callback, (void *) fd_ptr); b. Around line 1116 //usb_hostdev_tr_init(&tr, (tr_callback) usb_class_cdc_in_data_callback, (void *) data_instance); usb_hostdev_tr_init(&tr, (tr_callback) usb_class_cdc_in_data_callback, (void *) fd_ptr); c. Around line 1226 //usb_hostdev_tr_init(&tr, (tr_callback) usb_class_cdc_out_data_callback, (void *) data_instance); usb_hostdev_tr_init(&tr, (tr_callback) usb_class_cdc_out_data_callback, (void *) fd_ptr); With above modification , the Host CDC demo can work with a Device CDC demo, such as the one in "C:\Freescale\Freescale_MQX_4_1\usb\device\examples\cdc\virtual_com", which is an echo demo, it would send back anything charactor that it receives. But to see the echo more clearly, I made it echo back the charactor that greater than what is received, for example, if you type A, and will see B from the HyperTerminal. To do that , you have to change Virtual_Com_App(void) in the virtual_com.c as below: void Virtual_Com_App(void) {     /* User Code */     if(g_recv_size)     {         _mqx_int i;                 /* Copy Buffer to Send Buff */         for (i = 0; i < g_recv_size; i++)         {             printf("Copied: %c\n", g_curr_recv_buf[i]);             g_curr_send_buf[g_send_size++] = g_curr_recv_buf[i]+1;         }         g_recv_size = 0;     }         if(g_send_size)     {         uint8_t error;         uint8_t size = g_send_size;         g_send_size = 0;         error = USB_Class_CDC_Send_Data(g_app_handle, DIC_BULK_IN_ENDPOINT,             g_curr_send_buf, size);         if (!error && !(size % DIC_BULK_IN_ENDP_PACKET_SIZE)) {             /* If the last packet is the size of endpoint, then send also zero-ended packet,             ** meaning that we want to inform the host that we do not have any additional             ** data, so it can flush the output.             */             error = USB_Class_CDC_Send_Data(g_app_handle, DIC_BULK_IN_ENDPOINT, NULL, 0);         }         if(error != USB_OK)         {             /* Failure to send Data Handling code here */         }     }     return; } After you download code into, for example, TWR-K70F120(Host) and TWR-K60D100M(Device), and assemble them with TWR-SER and TWR-ELEV, you may connect them via USB port as below: Please also pay attention to J10(USB VBUS Select) and J16(USB Mode Select) according to the function of each tower system. With HyperTerminal connected with TWR-K70F120M system, you may type in any charactor ended with ENTER, and you will see the charactor echoed back as the attached video. This issue would be fixed in the next release, and sorry for the inconvenience that has caused. USB HostDevice Stacks Re: [MQX 4.1.0] Patch for USB Host CDC demo Hi Chris, Yes, I think this piece of code is wrong. In our new USB stack, this part should be: Best Regards, Kan Re: [MQX 4.1.0] Patch for USB Host CDC demo HI, thanks for this, it has been very helpful! I have application code I am porting to MQX 4.1 and the file pointer error was causing me a problem. I have spotted what I think may be another issue - in usb_host_cdc_intf.c at lines 222 and 209 i think the behavior for in and out pointers have been swapped - if I am interpreting correctly it now only allocates an rx buffer if the pipe is outgoing... which doesn't seem right.

MM9Z1_638 Intelligent Battery Sensor Demo Owner: Neil Krohn NXP's MM9Z1_638 is a fully integrated battery monitoring device for mission critical automotive and industrial applications. An S12Z microcontroller, SMARTMOS analog control IC, CAN protocol module and LIN interface for communications functions are embedded into this single-package soltuion. The MM9Z1_^38 battery sensor measures key battery parameters for monitoring state of health, state of charge and state of function for early batteries as well as emerging battery applications, such as 14 V stacked cell Li-Ion, high voltage junction boxes, and 24 V truck batteries.     Features The MM9Z1_638 is a fully integrated battery monitoring device for mission critical automotive and industrial applications. An S12Z microcontroller, SMARTMOS analog control IC, CAN protocol module and LIN interface for communications functions are embedded into this single-package solution. The MM9Z1_38 battery sensor measures key battery parameters for monitoring state of health, state of charge and state of function for early batteries as well as emerging battery applications, such as 14 V stacked cell Li-Ion, high voltage junction boxes, and 24 V truck batteries. Featured NXP Products MM9Z1_638: Battery Sensor with CAN and LIN Product Features: Wide range battery current measurement; on-chip temperature measurement Four battery voltage measurements with internal resistor dividers, and up to five direct voltage measurements for use with an external resistor divider Measurement synchronization between voltage channels and current channels Five external temperature sensor inputs with internal supply for external sensors Low-power modes with low-current operation Links Freescale Concept Car   Automotive

Ubuntu 12.04 64-bit Precise Pangolin Host Setup for Building i.MX28 L2.6.35_MX28_SDK_10.12_SOURCE [1] [1] Overview Resources Download Ubuntu 12.04.01 Download i.MX28EVK BSP and Documents Ubuntu Host Setup Host Package Update Ubuntu Configuration PDF Sudo Priviledges Default Shell CCACHE Directory Layout Extract SDK and Documents Install BSP Sources Ubuntu Software Packages for LTIB Patching LTIB Create SD Card Using Ubuntu Host Media Booting Selection Cable Connections   Overview Freescale's i.M28EVK development kit provides a platform for running software and evaluating features of the i.MX28 processor. This document provides the details for running the Linux Board Support Package (BSP) on the Ubuntu 12.04 64-bit Precise Pangolin Host on an Intel/AMD architecture computer. The 32-bit host is not covered in this document and does have different configuration steps than described here.   An Ubuntu Linux host is used to cross-compile the BSP creating ARM images. The BSP provides a build system named Linux Target Image Builder, (LTIB),  the GNU tool suite for compiling and debugging, U-Boot boot loader, Linux kernel, and a root file system. Resources i.M28EVK- i.MX28 Evaluation Kit Web Page MCIMX28EVKJ Product Summary Page- i.MX28 Download Collateral L2.6.36_MX28_SDK_10.12_Source- BSP Source Download Linux documentation - i.MX28EVK Documentation Ubuntu 12.04.1 LTS (Precise Pangolin)- Ubuntu 12.04 Release Download Ubuntu 12.04.01 A dedicated computer running Ubuntu or a Virtual Machine, (VMware or VirtualBox), can be used for running the Host Ubuntu software. The Ubuntu image is available for downloaded from the Ubuntu site: Ubuntu 12.04.1 LTS (Precise Pangolin).   This Ubuntu host ISO was used with the md5 checksum: ubuntu-12.04.1-desktop-amd64.iso  06472ddf11382c8da1f32e9487435c3d   One way to acquire the ISO is to use zsync to download: zsync http://releases.ubuntu.com/12.04/ubuntu-12.04.1-desktop-amd64.iso.zsync  Once downloaded, installing the ISO is user preference - either a dedicated Linux PC or in a Virtual Machine.   Download i.MX28EVK BSP and Documents The BSP download is from this site L2.6.36_MX28_SDK_10.12_Source and the documents from Linux documentation that requires a free registration to specify login credentials,   436e0b8e1c7976c657d530a45f9dbd0c L2.6.35_10.12.01_SDK_source_bundle.tar.gz de0274320a17c1e989d1ef5c088973e2 L2.6.35_10.12.01_SDK_docs.tar.gz   Ubuntu Host Setup Ubuntu login credentials of User: user Password: user are used for this documents. Host Package Update Once logged in to the Ubuntu host, the existing packages are brought up to date to the latest version before installing the BSP. The Ubuntu package manager used is apt-get. $ sudo apt-get update $ sudo apt-get upgrade  01. Check all installed packages for new revisions 02. all newer packages found are installed.   Addtional packages are required for the ltib build system. Ubuntu Configuration PDF evince is the default pdf reader, another option is zathura. $ sudo apt-get install zathura Sudo Priviledges LTIB requires super user priviledges for some operations. To enable a visudo entry is added to the sudo'ers file. For more information run 'man visudo'.   $ sudo visudo  The first word, user, is the login account 'user' This can be changed to whatever login you used, or if you have groups configured you can provide a group that developers are in - refer to the man page for sudo for details. Add this line:   user ALL =NOPASSWD: /usr/bin/rpm/ /opt/freescale/ltib/usr/bin/rpm   Default Shell Ubuntu uses the default shell 'dash'. This however causes failures on bash scripting which is part of the ltib system. Change the default shell from 'dash' to 'bash'   $ sudo update-alternatives --install /bin/sh sh /bin/bash 1  CCACHE ccache provides a fast C/C++ compiler cache which is supported in the ltib system. To configure once the ccache package has been installed: $ sudo apt-get install ccache $ ccache -M 50M $ ccache -c  02. Set the cache limit to 50 Meg 03. Clear the cache folder   Directory Layout The following directory structure is used: /home/user/freescale/imx28/ |-- archive |-- L2.6.35_10.12.01_ER_source |-- L2.6.35_10.12.01_SDK_docs |-- L2.6.35_10.12.01_SDK_scripts |-- ltib |-- ubuntu-imx28-ltib-patch   The archive directory is where the BSP and documents are stored; command to create the directory: $ mkdir -p ~/freescale/imx28/archive   Extract SDK and Documents The following instructions were used to extract the contents of the Software Development Kit:   $ cd ~/freescale/imx28/archive $ tar -zxf L2.6.35_10.12.01_SDK_source_bundle.tar.gz -C ..    01. Change into the directory containing the tar ball that is compressed. 02. Extract the contents into the directory above (-C ..) the current directory -z unzip -x extract -f L2.6.35_10.12.01_SDK_source_bundle.tar.gz   $ tar -zxf L2.6.35_10.12.01_SDK_docs.tar.gz  01. Extract the contents into the directory above (-C ..) the current directory     -z unzip     -x extract     -f L2.6.35_10.12.01_SDK_docs.tar.gz this file The contents of both tar files are now in the directory /home/user/freescale/imx28. Install BSP Sources After extracting the content from the L2.6.35_10.12.01_SDK_source_bundle.tar.gz the file L2.6.35_10.12.01_SDK.source.tar.gz contains all the sources and the build system. Extract the contents and install. This will create the ltib directory which is the build system. $ tar -zxf L2.6.35_10.12.01_SDK_source.tar.gz $ cd L2.6.35_10.12.01_ER_source $ ./install  Read the license information and accept by entering YES. An installation directory is then asked for, providing:  .. which is the parent directory. The installation script copies the packages and will inform you that 'Installation complete, your ltib installation has been placed in ../ltib, to complete the installation: cd .../ltib ./ltib  HOWEVER before doing this, there are packages and patches that need to be applied to run ltib on Ubuntu 12.04.01. Ubuntu Software Packages for LTIB The following packages are required. The script pkg-setup.sh attached below has these packages which can be downloaded and executed to install. $ sh pkg-setup.sh  sudo apt-get -y install gettext libgtk2.0-dev rpm bison m4 libfreetype6-dev sudo apt-get -y install libdbus-glib-1-dev liborbit2-dev intltool sudo apt-get -y install ccache zlib1g zlib1g-dev gcc g++ libtool sudo apt-get -y install uuid-dev liblzo2-dev tcl wget libncurses5-dev sudo apt-get -y install libncursesw5-dev lib32z1 libglib2.0-dev xsltproc sudo apt-get -y install ia32-libs libc6-dev-i386 The file pkg2-setup.sh contains optional packages for development. To install, download and execute: $ sh pkg2-setup.sh Please refer to the document ltib_build_host_setup.pdf for more information on host setup. Patching LTIB The location of files from the glibc-devel and zlib Ubuntu 12.04 packages has changed from 9.0.4 Ubuntu which the original ltib was released against. To update ltib operation the following patches are implemented from the directory ~/freescale/imx28/ltib 1. The file ltib is changed at line 2387 adding the '-v' option to the rpm call OLD:     system('rpm --force-debian 2>/dev/null') == 0? NEW:     system('rpm -v --force-debian 2>/dev/null') == 0? 2. The file bin/Ltibutils.pm is updated to support glibc-devel and zlib.   glibc-devel update: Line 563 add check for /usr/lib32/libm.so 'glibc-devel' => sub {-f 'usr/lib/libm.so' || -f '/usr/lib64/libz.so' || -f '/usr/lib32/libm.so'},   zlibc update: Line 584 add /lib/x86_64-linux-gnu/libz.so* zlib => sub{my @f = (glob('/usr/lib/libz.so*'),               glob('/lib/x86_64-linux-gnu/libz.so*'),               glob('/lib/libz.so*'),   The above patches are also in the attachment 0001-patches-for-12.04-ubuntu.patch.   LTIB packages also need adjustments to correctly build on Ubuntu. The tar file below, ubuntu-imx28-ltib-patch.tgz contains all the updates. Download and extract the contents at the same directory level as your ltib source directory. $ tar -zxf ubuntu-imx28-ltib-patch.tgz ├── ltib ├── ubuntu-imx28-ltib-patch └── ubuntu-imx28-ltib-patch.tgz Change directories to ubuntu-imx28-ltib-patch and then run the install-patches.sh script. $ cd ubuntu-imx28-ltib-patch $ ./install-patches.sh   The following packages are updated: lkc mtd-utils mux_server sparse Create SD Card Using Ubuntu Host The tar file L2.6.35_10.12.01_SDK_scripts.tar.gz contains scripts for writing the images from the ltib build to a SD card. Extract the content, copy the scripts to the ltib directory, and update the mk_mx28_sd script to work with the updated fdisk command.   $ tar -zxf L2.6.35_10.12.01_SDK_scripts.tar.gz $ cd L2.6.35_10.12.01_SDK_scripts $ cp mk_hdr.sh ~/freescale/imx28/ltib $ cp mk_mx28_sd ~/freescale/imx28/ltib $ cd ~/freescale/imx28/ltib  Edit mk_mx28_sd script and add the 'u' at line 177 then the o command after. This changes cylinders to sectors.   OLD: echo "o n   NEW: echo "u o n   Once updated to create the SD card which is at /dev/sdb: $ ./mk_mx28_sd /dev/sdb  NOTE: if mounted automatically, you need to unmount for the script to work $ sudo umount /dev/sdb*      Media Booting Selection The i.MX28EVK has a boot option to execute from the SD Card in Slot 0 which is located on the bottom of the EVK. On the top of the EVK there are switches that are read during the start up process to determine what boot media to use. The SD Card in slot 0 is used for this example which requires the settings: B3/DIP1 B2/DIP2 B1/DIP3 B0/DIP4 1 0 0 1 Refer to the user guide, i.MX28_Linux_BSP_UG.pdf section 3.2.1. Boot Modes for all options. The user guide is found in the Linux documentation bundle documentation.  Refer to the next section for a picture showing the boot switch location and the SD Card Slot 0 location. Cable Connections A computer serial port is connected to the i.MX28EVK serial port. The communication setting is 115200 baud, 8 data bits, No parity, and 1 stop bit. There is NO flow control set for this port. This is typically shown as 115200, 8N1. The power supply is connected  

使用 Processor Expert 为 IAR 生成代码 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 附件文档展示了如何使用 Processor Expert Driver Suit 为 IAR 生成代码。您可以在幻灯片底部的注释中看到详细信息。 顺祝商祺！ 卡洛斯

FRDM-MK64ボードを使用して、KDSのSDカードに加速度計データを書き込む <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> KDSのSDカードへの加速度計データの書き込み   形容：   KDS で FRDM-MK64FN1MOVLL12 ボードを使用して Accelerometer データを SD カードに書き込むプロジェクト。 加速度計から取得した変数x、y、zの時間と値が毎秒SDカードに書き込まれます。 これらはlog.txtファイルに書き込まれ、存在しない場合は作成されます。 書き込み中は、LEDが毎秒緑色に点滅します。 エラーが発生した場合、LCDは毎秒赤く点滅します。   http://mcuoneclipse.com/2014/05/26/tutorial-data-logger-with-the-frdm-k64f-board/ から取得したコードのセクション   問題：   フラッシュ後、時間は常に17:51:31から始まります。 これは、TmDt1_Initでそのように設定されているためです。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> KDSのSDカードへの加速度計データの書き込み   形容：   KDS で FRDM-MK64FN1MOVLL12 ボードを使用して Accelerometer データを SD カードに書き込むプロジェクト。 加速度計から取得した変数x、y、zの時間と値が毎秒SDカードに書き込まれます。 これらはlog.txtファイルに書き込まれ、存在しない場合は作成されます。 書き込み中は、LEDが毎秒緑色に点滅します。 エラーが発生した場合、LCDは毎秒赤く点滅します。   http://mcuoneclipse.com/2014/05/26/tutorial-data-logger-with-the-frdm-k64f-board/ から取得したコードのセクション   問題：   フラッシュ後、時間は常に17:51:31から始まります。 これは、TmDt1_Initでそのように設定されているためです。 全般

适用于 CodeWarrior Power Architecture 的 Aurora Trace <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 概述

Exercise 4: Kinetis Random Number Generator To do: The development platform is Eclipse. The EVAL Board is the Kinetis Tower TWR K60. On the Tower, you find 2 pushbuttons and 4 LEDs. a) Generate a hexadecimal random number from 0x0 to 0xF as long as pushbutton1 is pressed. Display the result with the 4 LEDs for about 3 seconds. b) Replace the code for recognizing a pressed key by a macro "KEY1_PRESSED". c) Replace the access to the 4 LEDs by a macro "LEDx_TOGGLE" with x = 0...3". Use active wait loops instead of the timer in this Kinetis exercise. Result: TWR_K60_RANDOM.zip

フリーマスター - TSA <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> FreeMASTER TSA(Target Side Address translation)の機能を説明するチュートリアルビデオです。   音楽: Bensbound (マイビデオで視聴)

フローティングライセンスサーバーデーモン - Hiware <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Re:フローティングライセンスサーバーデーモン - Hiware <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ザ  lmgrd  daemon とベンダーデーモンは連携してライセンスキーを管理します。  lmgrd  デーモンは、クライアント・アプリケーション・プログラムとの最初の接続を処理し、接続を適切なベンダー・デーモンに渡します。  lmgrd  デーモンは、ベンダーデーモンも起動および再起動します。

Floating License server daemon - Hiware Re: Floating License server daemon - Hiware The  lmgrd  daemon and the vendor daemons work together to manage the license keys. The  lmgrd  daemon handles the initial contact with the client application programs, passing the connection on to the appropriate vendor daemon. The  lmgrd  daemon also starts and restarts vendor daemons.

KDS で FRDM-KL25 ボードを USB マウスとして使用する <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> KDSのUSBマウス   形容：   KDS で FRDM-KL25Z128M4 ボード上の加速度計を使用して USB マウス入力を制御するプロジェクト。 USBマウスとして接続されていないときはLEDが赤く点滅し、接続されている場合は緑色に点滅します。 リセットボタンは左クリックします。   マウスの感度は、main.cのHIDM1_Moveコマンドを変更することで変更できます リセットボタンは、main.cのコメントを変更することにより、左クリックから右クリックに変更できます   コードのセクションは、以下から取得されます。 - http://mcuoneclipse.com/2012/09/21/tutorial-accelerating-the-kl25z-freedom-board/ - http://mcuoneclipse.com/2013/08/01/using-the-frdm-kl25z-as-a-usb-mouse-device/ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> KDSのUSBマウス   形容：   KDS で FRDM-KL25Z128M4 ボード上の加速度計を使用して USB マウス入力を制御するプロジェクト。 USBマウスとして接続されていないときはLEDが赤く点滅し、接続されている場合は緑色に点滅します。 リセットボタンは左クリックします。   マウスの感度は、main.cのHIDM1_Moveコマンドを変更することで変更できます リセットボタンは、main.cのコメントを変更することにより、左クリックから右クリックに変更できます   コードのセクションは、以下から取得されます。 - http://mcuoneclipse.com/2012/09/21/tutorial-accelerating-the-kl25z-freedom-board/ - http://mcuoneclipse.com/2013/08/01/using-the-frdm-kl25z-as-a-usb-mouse-device/ 全般 日時:KDSでFRDM-KL25ボードをUSBマウスとして使用する <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Bluetooth to UARTモジュールで可能になる場合があります。しかし、私はこの分野での経験がないことを認めます。 日時:KDSでFRDM-KL25ボードをUSBマウスとして使用する <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Bluetoothを使用するように、つまり付属のデバッグケーブルを使用せずにボードを適応させることは可能ですか?

産業用およびネットワーキングアプリケーション向けのLayerscapeマイクロプロセッサポートフォリオ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> エッジコンピューティングアプリケーションについて学習し、ゲートウェイとセキュリティを「管理」するための技術的な課題、クラウドサービスのコンテキストでEdgeScaleフレームワークを含むLayerscapeマイクロプロセッサソリューションを示します。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> エッジコンピューティングアプリケーションについて学習し、ゲートウェイとセキュリティを「管理」するための技術的な課題、クラウドサービスのコンテキストでEdgeScaleフレームワークを含むLayerscapeマイクロプロセッサソリューションを示します。 Layerscape処理プラットフォーム

Enabling SD Interface on P1024 Reference Design Board To enable SD interface in SPI boot on p1024RDB: 1. Perform the following updates in u-boot a) Modify pmuxcr to enable SD bus in case of SPI boot b) Update the corresponding static mux implementation in u-boot 2. Perform the following updates in Linux a) Disable IFC from device tree and kernel defconfig The patch details to enable SD interface are given below. A zip file, AN4336SW.zip, containing the patches for u-boot and Linux accompanies this application note. The file can be downloaded from [1]. U-Boot   Extract the u-boot code from the QorIQ SDK 1.0.1 iso   Apply the patch, u-boot-p1024rdb-enabling-sd-in-spi-boot.patch   Compile the u-boot using "make" command for SPI Flash    make ARCH=powerpc   CROSS_COMPILE=/opt/freescale/usr/local/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/bin/powerpc-linux-gnu- p1024RDB_SPIFLASH   Use the boot_format utility to generate the spiimage. For more information, see SDK manual.   Update the SPI Flash with the above built spiimage Linux Extract the Linux source code from QorIQ SDK 1.0.1 iso Apply the patch, linux-p1024rdb-enabling-sd-in-spi-boot.patch Compile Linux using make command #make ARCH=powerpc  CROSS_COMPILE=/opt/freescale/usr/local/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/bin/powerpc-linux-gnuarch/  powerpc/configs/qoriq_sdk_nonsmp_defconfig  #make ARCH=powerpc  CROSS_COMPILE=/opt/freescale/usr/local/gcc-4.5.55-eglibc-2.11.55/powerpc-linux-gnu/bin/powerpc-linux-gnu- Compile the dts ./sripts/dtc/dtc -f -I dts -O dtb -R 8 -S 0x3000  arc/powerpc/boot/dts/p1024rdb.dts.dts > p1024rdb.dtb.dtb With the updated SPI bootloader, Linux uImage and p1024rdb.dtb, the user must be able to enable SD interface on P1024RDB. NOTE The above-mentioned changes must be done only when the user specifically requires the SD interface using SPI boot. For all other boot methods, these patches must not be used. QorIQ P1 Devices

使用 Sigfox 发送 GPS 坐标 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 该视频展示了如何使用 Sigfox OL2385 开发板获取 GPS 坐标并将其发送到互联网 （在 “我的视频” 中查看） 智慧城市

功率和效率增强的 5G mMIMO 模块 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 完整系列的多功能放大器模块可快速部署基站，满足 5G 无线基础设施设备的超低延迟/高数据速率需求。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 完整系列的多功能放大器模块可快速部署基站，满足 5G 无线基础设施设备的超低延迟/高数据速率需求。 接口和连接

RDDSP56F8SRDS: 3-Phase SR Motor Sensorless Control Reference Design using 56F80X or 56F8300 DSCs Overview Features Block Diagram Board Design Resources Overview The reference design demonstrates sensorless control of the 3-Phase Switched Reluctance (SR) motor using 56F80x or 56F83XX Digital Signal Controllers. It can also be adapted to 56F81XX Digital Signal Controllers. The concept of this application is that of a sensorless speed closed loop SR drive using flux linkage position estimation. An inner current loop with PI controller is included. The change in phase resistance during motor operation due to its temperature dependency creates errors in the position estimation and significantly affects the performance of the drive. Therefore, a novel algorithm for on-the-fly estimation of the phase resistance is included. The Digital Signal Controller runs the main control algorithm. Rotor position is evaluated using the sensorless flux linkage estimation algorithm. The actual flux linkage is calculated at the rate of the PWM frequency and is compared with the reference flux linkage for a given commutation angle. When the actual flux linkage exceeds the reference, the commutation of the phases is done; the actual phase is turned off and the following phase is turned on. Flux linkage error is used for estimation of the phase resistance at low speeds (US Patent No.: 6,366,865). The actual speed of the motor is determined using the commutation instances. Based on the speed error, the speed controller generates the desired phase current. When the phase is commutated, it is turned on with a duty cycle of 100%. Then, during each PWM cycle, the actual phase current is compared with the desired current. As soon as the actual current exceeds the desired current, the current controller is turned on. The current controller controls the output duty cycle until the phase is turned off (following commutation). Finally, the 3-Phase PWM control signals are generated. The procedure is repeated for each commutation cycle of the motor. Features Sensorless control of an SR motor using a flux linkage estimation technique Targeted for 56F80X, 56F83XX, and 56F81XX Digital Signal Controllers Running on a 3-Phase SR HV Motor Control Development Platform The control technique: current control with a speed closed loop Position estimation based on flux linkage estimation Phase resistance measurement during start-up Phase resistance estimation at low speeds Motor starts from any position with rotor alignment Encoder position reference for evaluation of sensorless position estimation Manual interface FreeMASTER software control interface and monitor Fault protection Block Diagram Board Design Resources Legacy Designs