SD-CPE——与虚拟机（Docker 等）一起部署并由 Orchestrator 管理的 CPE <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> SD-CPE的概念、CPE上功能/应用的虚拟化、编排器对CPE的集中管理、优势以及在家庭、企业和工业中的应用场景。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> SD-CPE的概念、CPE上功能/应用的虚拟化、编排器对CPE的集中管理、优势以及在家庭、企业和工业中的应用场景。

S32K 损坏的演示 - 仍然运行良好！ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> S32K144 和 MPC5744P 电机控制演示平台被 UPS 运输公司破坏。电路板本身完好无损，第一次通电时运行良好。 （在 “我的视频” 中查看）

Example MPC5777C External SRAM_test GHS714 ******************************************************************************** * Detailed Description: * Application performs basic initialization then it initializes EBI for external * SRAM connected to MPC5777C-516DS and test it by write and read of block of * data. * * ------------------------------------------------------------------------------ * Test HW:         MPC5777C-512DS Rev.A + MPC57xx MOTHER BOARD Rev.C * MCU:             PPC5777CMM03 3N45H * Fsys:            PLL1 = core_clk = 264MHz, PLL0 = 192MHz * Debugger:        Lauterbach Trace32 * Target:          internal_FLASH * Terminal:        19200-8-no parity-1 stop bit-no flow control on eSCI_A * EVB connection:  jumper J4 on position 1-2 (choosing CS0) * ******************************************************************************** ******************************************************************************** * Detailed Description: * Application performs basic initialization then it initializes EBI for external * SRAM connected to MPC5777C-516DS and test it by write and read of block of * data. * * ------------------------------------------------------------------------------ * Test HW:         MPC5777C-512DS Rev.A + MPC57xx MOTHER BOARD Rev.C * MCU:             PPC5777CMM03 3N45H * Fsys:            PLL1 = core_clk = 264MHz, PLL0 = 192MHz * Debugger:        Lauterbach Trace32 * Target:          internal_FLASH * Terminal:        19200-8-no parity-1 stop bit-no flow control on eSCI_A * EVB connection:  jumper J4 on position 1-2 (choosing CS0) * ********************************************************************************

NXP/Maxim Small Cell Solution for MIMO Radios New Family of Doherty IC Power Amplifiers Coupled with a Dual-Path Pre-distortion Linearizer Demo / product features A2I20D040N 5 W final 42% efficiency 1.8-2.2 GHz wideband Doherty NXP’s A2I20D040N The Maxim SC2200 dual path linearizer enhances the already high linearity of the NXP devices with LTE signals as wide as 3x20 MHZ Maxim’s solution provides improvement of up to 28 dB in ACLR and 38 dBm in IMD NXP Recommends A2I20D040Nhttp://www.nxp.com/products/rf/rf-power-transistors/rf-cellular-infrastructure/1450-2200-mhz/1400-2200-mhz-5-w-avg.-28-v-wideband-integrated-rf-ldmos-amplifier:A2I20D040N?fsrch=1&sr=1&pageNum=1 SC2200: www.maximintegrated.com/SC2200 Fast-track 5G with NXP Application Note AN5296 - Effective Small Cell Solutions for MIMO Radios Mobile

SMI-N1948 ハンズオン・ワークショップ - Kinetis Motor Suite <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 新しいKinetis Motor Suite(KMS)ソフトウェア・ソリューションを使用して、設計サイクル・タイムとシステム効率を向上させる方法をご紹介します。高性能なKinetis Vシリーズ・マイクロコントローラを基盤とするKMSは、あらゆる経験レベルに対応するモータ制御を容易にします。このハンズオンクラスでは、最初に自分のモーターを回すところから、KMSを使用して初めてのカスタムアプリケーションを構築するまでをご案内します。自分のPMSMモーターを持参して、数分で回転させて調整する方法を学びましょう。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 新しいKinetis Motor Suite(KMS)ソフトウェア・ソリューションを使用して、設計サイクル・タイムとシステム効率を向上させる方法をご紹介します。高性能なKinetis Vシリーズ・マイクロコントローラを基盤とするKMSは、あらゆる経験レベルに対応するモータ制御を容易にします。このハンズオンクラスでは、最初に自分のモーターを回すところから、KMSを使用して初めてのカスタムアプリケーションを構築するまでをご案内します。自分のPMSMモーターを持参して、数分で回転させて調整する方法を学びましょう。 スマートマシナリー&インダストリアルオートメーション

eMSG インバウンドコンテキスト管理 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />

DwF杭州 - 2015-08-05 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 自動車およびコネクテッドカー 設計、ソフトウェア、サービス IAR: Cでの安全確保 スマートインダストリー インサイトとイノベーション スマートネットワーク

APF-IND-T1090 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 本次会议将针对中国市场介绍MAPS开发套件。了解如何使用它并运行一些示例。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 本次会议将针对中国市场介绍MAPS开发套件。了解如何使用它并运行一些示例。

Freescale H.I.T. Project #1: MonkeyJam - A DIY Guitar Stomp Box Project Summary Skills Developed: Materials: Step 0: Prerequisite Videos Step 1: Get a FRDM-JAM Step 2: Put it Together Step 3: Download Step 4: Hack and Slash! Sound Samples Utilities, etc: Project Summary MonkeyJam will use the FRDM-K20D50 board (which has a Cortex M4 core with DSP instructions) along with the FRDM-JAM shield so you can  make your very own guitar /bass  stomp box.  The end result will be a functional DSP system that will allow you to do high quality amplifier simulation and effects. The FRDM-JAM does not limit you to DSP on musical instruments!  There are 3.5mm stereo jacks to DSP filtering any type of audio signal.    You could even use the USB interface to create a USB-MIDI Synthesizer!  Lastly,  no need to bring the house down.....  a headphone amplifier circuit is provided so you can jam out without bothering the neighbors. MBED Support coming *very soon* Skills Developed: Real Time Processing DSP Algorithms Fixed Point Mathematics 24-bit I2S Data Converter Interfacing Soldering SOIC8 and 1206 Surface mount devices Cortex CMSIS DSP Library Materials: FRDM-K20D50 FRDM-JAM Development Tools Install Codewarrior 10.5 for Microcontrollers (Eclipse) Special Edition to your  machine Example Code Get the latest copy from Github Step 0: Prerequisite Videos The videos are organized into a nice YouTube playlist: H.I.T 1: Monkey Jam - YouTube https://www.youtube.com/playlist?list=PLWM8NW5LEukgM-D5eRMtKZ8R2WfXnqKGp MonkeyJam Watch Me 1st FRDM-JAM Hardware Overview MonkeyJam Software Overview Introduction to Fixed Point Math for Embedded Systems - Part 1 of 3 Introduction to Fixed Point Math for Embedded Systems - Part 2 of 3 Introduction to Fixed Point Math for Embedded Systems - Part 3 of 3 Real Time Signal Processing Part 1 of 3 Real Time Signal Processing Part 2 of 3 Real Time Signal Processing Part 3 of 3 q31_t (Q0.31) Number Format for the CMSIS DSP Libraries and the MonkeyJam Software Guitar physics in a nutshell Ideas for hacking the MonkeyJam Step 1: Get a FRDM-JAM MonkeyJam Build Package on the FRDM-JAM site.    Please let us know if you are interested in a pre-assembled version.  If there is enough demand we will get some preassembled for purchase, I will get a Kickstarter going!   Don't be afraid to build it yourself,  Soldering is fun!  There is plenty of good stuff on the web on how to do SMT soldering.  All of the parts on the board are fairly simply once you get the hang of it and everything can be hand soldered  The key is having some decent tools. Step 2: Put it Together Attach the FRDM-JAM to the FRDM-K20D50.  The FRDM-K20D50 comes with female headers that you can solder on so the boards can be easily separated.  Note that as of Rev Gamma (current version),   it is possible to connect to a K64F.    The software isn't quite there but it hardware connections are available.   If you are unsure,  stick with the FRDM-K20D50 Step 3: Download Download the Example Software from Github.  The video "Loading and Configuring the MonkeyJam Example Software" will step you though downloading the program and doing some basic configuration. Step 4: Hack and Slash! Plug In and jam! Sound Samples Each sound sample was my Carvin Ultra-V guitar plugged direct into the MonkeyJam Board.  The output was fed to a Zoom Handy Recorder H4n (Thanks to Brandin Claar of Remodulate LLC for the recorder).  The H4N recorded the signal at 44.1KHz Sample rate @16-bit.  The sound files were converted to mono format via Goldwave.  No processing (other than a  volume boost on the files) was performed.   I listen to the recording in real-time via a line out on the H4N.  File (See Attachments) Patch Notes STE-003-Neck-a12b12g12-mlike.wav PATCH_TUBEY_CLEAN Neck Pickup Alpha Pot - 12 O'Cock Beta Pot - 12 O'Cock Gamma Pot - 12 O'Cock Pattern Similar to Metallica Sanitarium STE-005-Neck-a7b5g5-mlike.wav PATCH_TUBEY_CLEAN Neck Pickup Alpha Pot - 7 O'Cock Beta Pot - 5 O'Cock Gamma Pot - 5 O'Cock Pattern Similar to Metallica Sanitarium STE-006-Neck-a12b7g5-mlike.wav PATCH_TUBEY_CLEAN Neck Pickup Alpha Pot - 12 O'Cock Beta Pot - 7 O'Cock Gamma Pot - 5 O'Cock Pattern Similar to Metallica Sanitarium STE-007-Neck-VariousSettings-d-g-em_strum.wav PATCH_TUBEY_CLEAN Neck Pickup The pots were moved around throughout the file Strummed D-Major, G-Major and E-Minor STE-008-Neck+Bridge-VariousSettings-d-g-em_strum.wav PATCH_TUBEY_CLEAN Neck + Bridge Pickup The pots were moved around throughout the file Strummed D-Major, G-Major and E-Minor STE-009-Bridge-VariousSettings-d-g-em_strum.wav PATCH_TUBEY_CLEAN Bridge + Bridge Pickup The pots were moved around throughout the file Strummed D-Major, G-Major and E-Minor STE-010-Neck-VariousSettings-Jammy.wav PATCH_TUBEY_CLEAN Neck + Bridge Pickup The pots were moved around throughout the file B-Minor Type Jam STE-011- Bridge - Various Settings - On-Off Demo-RandomDroppedD.wav PATCH_OVERDRIVE Bridge Pickup Alpha Pot - 5 O'Cock Beta Pot - 12 O'Cock Gamma Pot - 12 O'Cock Random Dropped D twiddling STE-012- Neck - Various Settings - On-Off Demo-Jammy.wav PATCH_OVERDRIVE Neck Pickup Alpha Pot - 5 O'Cock Beta Pot - 7 O'Cock Gamma Pot - 7 O'Cock Random B-Minor twiddles (bluesy) PATCH_OVERDRIVE             +––––––––––––––––––+      +––––––––––––––––––––––––––+      +–––––––––––––––––––––+                               |                  |      |                          |      |                     |                    Signal In  |    IIR BiQuad    |      |      Hard Overdrive      |      |      IIR BiQuad     |  Signal Out       +–––––––––+>|                  +––––+>|                          +––––+>|                     +–––––––––––––+>                |   [Peaking EQ]   |      | [atan24pi Look Up Table] |      |  [Low Pass Filter]  |                               |                  |      |                          |      |                     |                               +––––––––––––––––––+      +––––––––––––––––––––––––––+      +–––––––––––––––––––––+                                                                                                                                                     0.1 < Q < 1.5    [Pot Alpha]                                     Q = 0                                                                                                                                                              50 < Fs < 750    [Pot Gamma]                                   Fs = 2000                                                                                                                                                          -20 < dbGain < 20  [Pot Beta]                                                                                                                                                                                        PATCH_TUBEY_CLEAN              +––––––––––––––––––+      +––––––––––––––––––––––––––+      +–––––––––––––––––––––+                               |                  |      |                          |      |                     |                    Signal In  |    IIR BiQuad    |      |      Soft Overdrive      |      |      IIR BiQuad     |  Signal Out       +–––––––––+>|                  +––––+>|                          +––––+>|                     +–––––––––––––+>                |     [LowShelf]   |      | [atan4pi Look Up Table]  |      |  [Low Pass Filter]  |                               |                  |      |                          |      |                     |                               +––––––––––––––––––+      +––––––––––––––––––––––––––+      +–––––––––––––––––––––+                                                                                                                                                     0.05 < Q < 2.58   [Pot Alpha]                                     Q = 2.0                                                                                                                                                             1000 < Fs < 4000    [Pot Beta]                                   Fs = 2500                                                                                                                                                      -15 < dbGain < 15  [Pot Gamma]                                                                                                                                                                                    Utilities, etc: Biquad Filter View - A IIR Biquad Filter Design & Visualization Tool Student Project Re: Freescale H.I.T. Project #1: MonkeyJam - A DIY Guitar Stomp Box Hi Eli I have implemented the CMSIS code and also made the document for others , kindly look if anything is incorrect in the process and please update it. https://community.freescale.com/message/414670#414670 Kind Regards Amit Kumar Re: Freescale H.I.T. Project #1: MonkeyJam - A DIY Guitar Stomp Box Hi Eli Hughes Can you provide me the link of the video in which you have demonstrated how to implement  CMSIS library with codwarrior basically I am concerned with FFT library which you have implemented? It Will be a great help. Thanks Kind Regards Amit Kumar Re: Freescale H.I.T. Project #1: MonkeyJam - A DIY Guitar Stomp Box Hi Eli Thanks for your reply. when I am opening your project for the 1st time I am getting some warning message. Is this message of any concern?. Kind Regards Amit Kumar Re: Freescale H.I.T. Project #1: MonkeyJam - A DIY Guitar Stomp Box Amit: If you click on the project properties for the library and look at processor settings, there are 2 symbols (ARM_CM4 and ARM_ROUNDING).   This is all I had to do to get it compile. I think I covered it in one of the videos.  If not, I will certainly have to get some sort of small video for it!. -Eli Re: Freescale H.I.T. Project #1: MonkeyJam - A DIY Guitar Stomp Box Hi Eli Hughes I Imported the MonkeyListen Project and it got compiled without any error. right now for testing I am targeting FRDM-K20D50M (MK20DX128). After this I will be targeting mk60fn1m0vlq12. What are the settings required to be done for using the library in any project ? If you can provide some snapshot of  the settings required to make it work It will be helpful for all the community members. As I went across some queries which was unanswered regarding the same. In ARM's website also I didn't find any help regarding this. When I saw your tutorial everything was well explained. So If this portion is also covered in it than it will a great help for people like me. and I am sure many people want to use it but can't use due to this implementation part. Thanks in advance Kind Regards Amit Kumar Re: Freescale H.I.T. Project #1: MonkeyJam - A DIY Guitar Stomp Box Amit: Do you try importing the MonkeyListen project and see the settings I used?   What chip are you targeting? Re: Freescale H.I.T. Project #1: MonkeyJam - A DIY Guitar Stomp Box Hi eli_hughes Thanks For the awesome tutorial. It pretty much shows the real life implementation of DSP. I wanted to ask you about implementation of CMSIS library in codewarrior. In one of my projects I wanted to implement DSP library to implement FFT. But I am stuck in implementing CMSIS library. I saw your Video for this as well as the 2nd project i.e Project #2: Monkey Listen! Audio Spectrum Analyzer Display That was also awesome like this. But again I cannot move further as I am facing problem in implementing the library.I went through some post regarding implementing the CMSIS library but that was not compiling and was giving errors. and sometimes was exceeding the m-text limit. I went through the following links. Tutorial: Using the ARM CMSIS Library | MCU on Eclipse Adding the CMSIS-DSP library 移植CMSIS-DSP库到CodeWarrior的步骤以及Kinetis FPU单元应用的对比 Please look into the matter. I hope this post will be beneficial for many community users. Thanks in advance Kind Regards Amit Kumar

i.MX Android Debug Tips for Power Management by b47504 Overview This document is intended to introduce debug tips about i.MX power management based on i.MX Android software. The following topics are involved in this document: How to debug suspend/resume issues How to do power optimization How to debug suspend/resume issues General method: Capture more PM  debug message Enable PM debug system to get more info about PM in kernel and debug interface Power management options  ---> [*] Power Management Debug Support                                     [*]   Extra PM attributes in sysfs for low-level debugging/testing Enable wakelock debug_mask to capture more message about wakelock root@android:/ # echo 15 > /sys/module/wakelock/parameters/debug_mask root@android:/ # echo 15 > /sys/module/userwakelock/parameters/debug_mask Enable earlysuspend debug_mask to capture more message about early suspend and late resume. root@sabresd_6dq:/ # echo 15 > /sys/module/earlysuspend/parameters/debug_mask Add no_console_suspend=1 to the boot option for kernel This makes the system print more useful info before entry in suspend Eg: --- a/sabresd_6dq/BoardConfig.mk +++ b/sabresd_6dq/BoardConfig.mk -BOARD_KERNEL_CMDLINE := console=ttymxc0,115200 init=/init video=mxcfb0:dev=ldb,bpp=32 video=mxcfb1:off video=mxcfb2:off fbmem=10M fb0base=0x27b00000 vmalloc=400M androidboot.console=ttymxc0 androidboot.hardware=freescale +BOARD_KERNEL_CMDLINE := console=ttymxc0,115200 init=/init video=mxcfb0:dev=ldb,bpp=32 video=mxcfb1:off video=mxcfb2:off fbmem=10M fb0base=0x27b00000 vmalloc=400M androidboot.console=ttymxc0 androidboot.hardware=freescale no_console_suspend=1 System cannot enter suspend mode Check below setting items have been disabled: §  Whether the usb cable has been removed(usb gadget will hold a wake lock) §  Setting->Display->Sleep, check whether the inactivity timeout period setting is longer than your expected time. §  Setting->System->Developer options->stay awake(stay awake not be set), check whether the option is disabled Check if all wake locks have been released(You can see which wake lock is held, and then debug into the specific module): root@sabresd_6dq:/ # cat /sys/power/wake_lock System could not resume from suspend/System crash when resume or suspend Check the PMIC_STBY_REQ signal. System use PMIC_STBY_REQ signal to notify power management IC to change voltage from standby voltage to functional voltage and vice versa. In general, pmic_stby_req pin is connected to pmic standby pin. So measure the pin to check whether the  de-assert signal is triggered. If the signal is not triggered, we may consider whether wake-up sources are correctly setup. If the signal is triggered, we may double-check whether the pmic supply power normally. And not limited to the two points, we should also double-check everything we doubt according to the system log and hardware measured waves.  Using Trace32 or ICE to locate the problem. Please view trace32 website to get more details. Track from mx6_suspend_enter in arch/arm/mach-mx6 .                Track "state" value and try to map to different the low power mode via function mxc_cpu_lp_set.                Check "mx6_suspend.S" which conduct the detailed operations in suspend: "MEM" is mapped to "dormant" mode. So goto "dormant" symbol and try to dump different operations to narrow down suspend/resume failure If this failure maybe related to DDR operation, try to dummy DDR IO relative low power operation. Using ram console to dump kernel log after reboot. Ram console will keep one kernel log copy into one certain memory space. You can use the following command to check last time kernel log, if memory power was not cut off during the reboot process. Eg(if it is the first time boot, you cannot find the /proc/last_kmsg file): root@sabresd_6dq:/ # cat /proc/last_kmsg Kernel resume back from suspend but android not This is usually introduced by the wrong key layout file Use getevent/sendevent tool to get power key scan code #getevent  Correct the Keylayout file    system/usr/keylayout/****.kl Correct the scandcode with your power key report value to Match the POWE key Suspend/Resume consume too much time: We can print the specific module name and time consume details, if the module's suspend/resume time consume more than the threshold parameter by read/write /sys/power/device_suspend_time_threshold file. By default, the parameter is setup to 0, via disabled the function. We can enable it by the following command: Eg: root@android:/ # echo 10  > /sys/power/device_suspend_time_threshold This command means that if the module's suspend/resume time consume more than 10 us, the system will print the module's detail out. If you want to know the more details how to implement it on kernel, please check kernel/power/main.c Notes: Can use the shell command to enter different system level low power modes for debug (For more details: you can check Linux_6DQ_RM.pdf): #echo mem > /sys/power/state #echo standby > /sys/power/state How to do power optimization Runtime Mode Check whether CPUFreq and  Bus_freq scale are enabled root@android:/ # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor root@android:/ # cat /sys/devices/platform/imx_busfreq.0/enable More details about this, please refer to "Documentation/cpu-freq/ governors.txt” . Check whether the system bus is working on your expected frequency. For MX6Q: root@android:/ #  cat /sys/kernel/debug/clock/osc_clk/pll2_528_bus_main_clk/periph_clk/mmdc_ch0_axi_clk/rate Check CPU Loading and Interrupt(cat /proc/interrupts)                root@android:/ #  cat /proc/interrupts                Through this command you can check whether some module will trigger interrupt frequently.  And consider that whether we have some chances to reduce the interrupt count. Check clock tree carefully to see which clocks are not gated off  but no any modules need them. root@android:/ # powerdebug -d -c Reduce GPU frequency.GPU also offered interface to modify the frequency. According to your own product, you can reduce the gpu frequency. Default gpu3DMaxClock is set to 64 in init.rc file, we can tuning a suitable value by ourselves. diff --git a/imx6/etc/init.rc b/imx6/etc/init.rc index 8c420b5..eb11ffe 100755 --- a/imx6/etc/init.rc +++ b/imx6/etc/init.rc @@ -397,6 +397,9 @@ on boot #  Set GPU 3D minimum clock to 3/64     write /sys/module/galcore/parameters/gpu3DMinClock 3 +#  Set GPU 3D maximum clock to 64/64 +   write /sys/module/galcore/parameters/gpu3DMaxClock 64 + Suspend Mode Check whether all devices enter suspend mode or low power mode: Add debug message into devices drivers to check whether all devices driver suspend interface are called Use oscilloscope to measure the related signal (depend on specific device datasheet and custom hw design) to check whether every device enter low power mode Remove devices from the board(or rmmod the device driver) , and do hardware rework to exclude some hardware module if needed. Then we can figure out which module introduced the high consumption, and debug into the specific module. Add debug message in device drivers which may lead high power consumption, catch the waveform from these modules which may impact the high power consumption Check whether DDR enter in self-refresh mode(Please check the DDR datasheet to figure out which pin indicate self-refresh state, and check it with oscilloscope) Config GPIO PADs as output zero or input mode (depending to HW design) Cut off LDOs/DCDCs which no modules need (depending to HW design) Check all PLLs will cut off, just 32KHZ sleep clock living Android i.MX6_All Re: i.MX Android Debug Tips for Power Management Yes ~ I also want to know Thanks. Re: i.MX Android Debug Tips for Power Management Hi,Yuan Zhao   Could you update these tips for Android 5.0+?   Because some tips cannot suitable for it. For example, I cannot find the /proc/wakelocks, the content of wakelock.c has changed. Thank you !

彼らはここにいます！ARM Cortex-M4コアをベースとするフリースケールKinetisマイクロコントローラ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> フリースケールのジェフ・ボックが、ARM Cortex-M4コアをベースとするKinetisの32ビット・マイクロコントローラの 優れた 機能を紹介します

问答：i.MX6 参考手册中有关 UART 时钟树的错误 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 问题： 在参考手册的 Rev. 1.0 版本中看到了有关 UART 时钟树的以下矛盾信息： 第813页： PLL3_PFD1 -> 除以 6 -> 可调后分频器 -> UART 第839页： PLL3 -> 除以 6 -> UART 在旧的 Rev DI 中发现： 第803页： PLL3 -> 除以 6 ... 大约 80MHz 假设正确的路径是： PLL3 -> 除以 6 -> 后分频器 -> UART。 回答： 设计人员说 UART _CLK_ROOT 来自 PLL3（而不是 PLL3:PFD1）并除以 6 产生 80 MHz。 我正在等他确认他提到的分频器是CSCDR1[UART_CLK_PODF ]。 i.MX6_全部

ビデオ - i.MX53 クイック スタート ボード入門 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 追加した人 マーシャ・チャン on 2011年3月16日 at 11:16am (マイビデオで視聴)

Adeneo Embeddedは、i.MX53上のLinuxとWEC7のベンチマーク比較をリリース <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 多くのお客様が特定のプラットフォームで次の製品のオペレーティングシステムを選択するのが難しいと感じているため、Adeneo Embeddedは、i.MX53プラットフォーム上のLinuxとWEC7の非常に詳細な比較をまとめました。この比較では、プラットフォームのセットアップ、最初のビルドの作成にかかる時間から、パフォーマンスと消費電力のベンチマークまで、すべてを文書化しています。以下は、ドキュメントの内容のスナップショットです。   完全なドキュメントにアクセスするには、Adeneo Embedded([email protected])にお問い合わせください 全般

Video - product demo_i.MX53.mov http://www.youtube.com/watch?feature=player_embedded&v=fQjQPpfExTQ   Uploaded by dexterji on Nov 1, 2011 One XMBC and DLNA demo on i.MX53 for chinese customers. Category: Entertainment License: Standard YouTube License   General

Booting Linux From NAND Flash on the i.MX31 ADS - In LTIB generate a rootfs.jffs2 with a erase block size of 16KB: ./ltib -c ---Target Image Generation   Options ---> ---Choose your root file system image type     Target image: (jffs2) --->   (16) jffs2 erase block size in KB - Copy the generated rootfs.jffs2 to /tftpboot : cp rootfs.jffs2 /tftpboot - Program 200732 Redboot binary. The 200732 Redboot is available in the 20071008 BSP iso. After mounting the iso go to the bootloaders directory, extract the redboot_200732.tar.gz file and use the pre-built mx31ads_redboot.bin inside the bin directory. - Boot from NAND and setup the network parameters fis init load -r -b 0x100000 /tftpboot/zImage fis create -l 0x200000 kernel load -r -b 0x100000 /tftpboot/rootfs.jffs2 fis create -l 0x1d000000 root - Pass the following kernel command line: fis load kernel exec -b 0x100000 -l 0x200000 -c "noinitrd console=ttymxc0,115200 root=/dev/mtdblock6 rootfstype=jffs2 init=linuxrc ip=none mtdparts=mx" You need to replace mtdblock6 with your rootfs partition, see below: mx31# cat /proc/mtd dev:    size  erasesize  name mtd0: 00040000 00020000 "RedBoot" mtd1: 001a0000 00020000 "kernel" mtd2: 0001f000 00008000 "FIS directory" mtd3: 00001000 00008000 "RedBoot config" mtd4: 00040000 00004000 "RedBoot" mtd5: 00200000 00004000 "kernel" mtd6: 01d00000 00004000 "root" mtd7: 00003000 00004000 "FIS directory" mtd8: 00001000 00004000 "RedBoot config" mx31#

Q&A: Is it really possible to implement the BT656 with SAV / EAV and without external HSYNC/VSYNC? Q: How to get the CSI BT656 without HSYNC/VSYNC working. The problem, is that all implemented driver in the BSP are using the external HSYNC/VSYNC synchronization signal. The SW designer is actually struggling to find the right way to generate the end of field active interrupt (end of frame). > mxc_v4l2_still.out I get an: > ERROR: v4l2 capture: mxc_v4l_read timeout counter 0 > > When using mxc_v4l2_capture.out or mxc_v4l2_tvin.out I get an: > ERROR: v4l2 capture: mxc_v4l_dqueue timeout enc_counter 0 > To help him implementing the driver, I need to get some insight on the IPUx_CSIn_CCIR_CODE_1/2/3 as it seems that the bit description 21 to 19 (CSI_STRT_FLD0_ACTV) is not described (same for all the multiple bit field in this register. Maybe it should match the ITU656, but here as well the driver examples does not match the bit description of the ITU standard. So my questions: IS it really possible to implement the BT656 with SAV / EAV and without external HSYNC/VSYNC? If yes, is it possible to review the IPUx_CSIn_CCIR_CODE_1/2/3 fields and communicate which parameter should be provided here? i.MX6Q A:      For no VSYNC and HSYNC case, in the sensor driver such as "linux-3.0.35\drivers\media\video\mxc\capture\adv7180.c", function ioctl_g_ifparm(), you should set p->u.bt656.bt_sync_correct to 0;      p->u.bt656.bt_sync_correct = 1; // It means external VSYNC and HSYNC will be used for SYNC.      p->u.bt656.bt_sync_correct = 0; // No external VSYNC and HSYNC, embedded EAV and SAV will be used for SYNC.      In iMX6 BSP, the CCIR related code is ready in "linux-3.0.35\drivers\mxc\ipu3\ipu_capture.c", function ipu_csi_init_interface(), no code modification was needed, that code was verified work.      For BT656 mode, your sensor driver such as adv7180, should also report correct parameters in function function ioctl_g_ifparm().      p->u.bt656.clock_curr = 0;  // This will tell linux-3.0.35\drivers\media\video\mxc\capture\mxc_v4l2_capture.c to use "IPU_CSI_CLK_MODE_CCIR656_INTERLACED" in function mxc_v4l2_s_param().      The current iMX6 BSP mxc_v4l2_capture.c driver doesn't support BT656 progressive mode, it only supports BT656 interlace mode. To support BT656 progressive mode, the customer should modify the code in mxc_v4l2_s_param(), let csi_param.clk_mode = IPU_CSI_CLK_MODE_CCIR656_PROGRESSIVE. This is exactly what they are doing, but still it doesn’t work. Actually, they see the code being executed following the right steps in the ipu_csi_init_interface() going through PAL 720x625 configuration. But still, they get the timeout! else if (cfg_param.clk_mode == IPU_CSI_CLK_MODE_CCIR656_INTERLACED) {       if (width == 720 && height == 625) {         /* PAL case */         /*         Field0BlankEnd = 0x6, Field0BlankStart = 0x2,         Field0ActiveEnd = 0x4, Field0ActiveStart = 0           */         ipu_csi_write(ipu, csi, 0x40596, CSI_CCIR_CODE_1);         /*         Field1BlankEnd = 0x7, Field1BlankStart = 0x3,         Field1ActiveEnd = 0x5, Field1ActiveStart = 0x1           */         ipu_csi_write(ipu, csi, 0xD07DF, CSI_CCIR_CODE_2);         ipu_csi_write(ipu, csi, 0xFF0000, CSI_CCIR_CODE_3); So, I believe the parameters are wrong. What could be missing. Can you review the driver? For me it looks like the adv example, except the bt_sync_correct=0, which is what we want. You can suggest the customer to capture the CSI data bus to check if there is correct output from sensor, such as EAV/SAV. For the "timeout" error, it always means there is no correct data on CSI data bus. This document was generated from the following discussion: CSI BT656 Re: Q&A: Is it really possible to implement the BT656 with SAV / EAV and without external HSYNC/VSYNC? Tie DATA_EN permanently to active source. Or, to save pins, just do not configure DATA_EN route outside. Re: Q&A: Is it really possible to implement the BT656 with SAV / EAV and without external HSYNC/VSYNC? If you have further question please go to community and create discussion there. Someone will answer your question. Thanks, Yixing Re: Q&A: Is it really possible to implement the BT656 with SAV / EAV and without external HSYNC/VSYNC? I got it, but it isn't the answer I want. It seems that nobody make imx6q+jb4.3+adv7180 works fine in intervelaved mode. Now I only make it in gated clock, see imx6q android jb4.3_1.0.0-ga adv7180 can't work in bt656 mode Re: Q&A: Is it really possible to implement the BT656 with SAV / EAV and without external HSYNC/VSYNC? That is what in CSI BT656. It has question and answer in Re: Q&A: Is it really possible to implement the BT656 with SAV / EAV and without external HSYNC/VSYNC? The document is only a copy of this topic! Re: Q&A: Is it really possible to implement the BT656 with SAV / EAV and without external HSYNC/VSYNC? Do you see attachment in just below Q&A? Re: Q&A: Is it really possible to implement the BT656 with SAV / EAV and without external HSYNC/VSYNC? where is attached document? Re: Q&A: Is it really possible to implement the BT656 with SAV / EAV and without external HSYNC/VSYNC? Please see attached. Re: Q&A: Is it really possible to implement the BT656 with SAV / EAV and without external HSYNC/VSYNC? Can I access CSI BT656?

P2040/P2041 USB Specific FAQs For P2041, if USB1 and USB2 ports are not implemented, what to do with the unused USB ports ie tie them to ground, 3.3V or leave them unconnected? If USB is not to be used at all, keep the following USB signals floating: USB1_IBIAS_REXT, USB2_IBIAS_REXT, USB1_VDD_1P8_DECAP, USB2_VDD_1P8_DECAP, USB1_VDD_3P3 and USB2_VDD_3P3. The following signals should be pulled-down: USB1_VBUS_CLMP, USB2_VBUS_CLMP and USB_CLKIN. Also, pins USB_VDD_1P0 and USB2_VDD_1P0 must be tied to 1V or the platform voltage (whatever is the SOC core digital power supply) If USB_VDD_3P3 must be connected to 3.3V, will the power sequence be same as other 3.3V (OVDD) (no special power sequence for USB_VDD_3P3)? Even if PHY is not used, USB_VDD_1P0 must be tied to 1V or the platform voltage (whatever is the SOC core digital power supply), other pins can be left floating: USB1_IBIAS_REXT, USB2_IBIAS_REXT, USB1_VDD_1P8_DECAP and USB2_VDD_1P8_DECAP, USB1_VDD_3P3, USB2_VDD_3P3. If signals USB_VDD_3P3 and USB_VDD_1P8 are left floating, there is no need to take of power sequencing on these pins, only USB_VDD_1P0 must be a part of standard power sequencing requirements. If signals USB_VDD_3P3 and USB_VDD_1P8 are used (i.e. not left floating), power sequencing is to be done as under: Follow a minimum ramp time of 350us on USB_VDD_3P3(most regulators would give a 350us ramp time) and standard power sequencing on USB_VDD_1P0,USB_VDD_3P3. USB_VDD_1P8_DECAP would only have 1uF capacitor and is automatically tolerant of sequencing on rest of the supplies are sequenced properly. Also based on silicon validation: There is no power down sequencing to be followed on the PHY. There requirements were added as a backup strategy in case the new regulator in the IP had a problem. We have tested this regulator, so no power down sequencing requirements is needed. There is no need to supply any power to USB_VDD_1P8_DECAP, as the circuit is working fine. QorIQ P2 Devices

FreeMaster_03.07.2013.PEupd <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 更新 PE 的 FreeMASTER 组件 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 更新 PE 的 FreeMASTER 组件

飞思卡尔杯伺服组件 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 如何安装伺服喇叭。更具体地说是飞思卡尔杯套件。[无音频] （在 “我的视频” 中查看） 飞思卡尔杯内容 回复：飞思卡尔杯伺服组件 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 我的理解是伺服器的行程可以是 90 度、180 度或 360 度。顺时针。0 是课程的起点。 回复：飞思卡尔杯伺服组件 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 它说在固定手臂之前伺服器要处于 0 度。汽车直行时，难道不应该处于中立位置（90 度）吗？ 回复：飞思卡尔杯伺服组件 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 没有声音就很好。消息已发送。 接下来我们将有黑白视频 查理·卓别林来到城里。 回复：飞思卡尔杯伺服组件 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 没有声音是故意的。我需要买一个好的麦克风并找一个更安静的地方来录音！ 回复：飞思卡尔杯伺服组件 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 视频有声音吗？因为我什么都没听到.... 顺祝商祺！ 回复：飞思卡尔杯伺服组件 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 是的——在绝对确定一切控制正常之前，绝对不要将伺服器连接到转向机构。在软件中添加保护带以防止可能损害物理机制的“过度转向”。 回复：飞思卡尔杯伺服组件 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 一旦启动，您就必须对其进行调整，并编写程序将伺服器“归零”。 回复：飞思卡尔杯伺服组件 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 谢谢——在使用喇叭之前如何定位伺服角度以使其具有完整的运动范围？我觉得必须先将其电气连接起来，以确保在最终组装之前能够将位置归零。