Q&A: レジスタMMDCx_MPSDCTRL SDCLKx_DEL単位の遅延単位 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 質問: i.MX6 RMに記載されている遅延ユニットがあるかどうかを明確にします 2つの場所で同じです: 1. データストロボには遅延ユニットがあり、キャリブレーション手順で考慮されます。 2. クロック SDCLK には遅延ユニットがあり、RM のセクション 44.12.54 「MMDC PHY CK Control Register (MMDCx_MPSDCTRL)」に記載されています。 一般的な遅延ユニットの説明には、次のように記載されています。 遅延線によって発行される遅延(設定値による)は絶対的であり、動作条件と温度条件を考慮に入れます。遅延線には、デバイスごとに異なる可能性のある解像度があります。1 遅延ユニットの増分は、20 pSec から 50 pSec の間で変化する可能性があります。 SDCLK 遅延にも同じことが関係していると推測されますが、i.MX6 の予備仕様では、ビット フィールド SDCLKx_DEL (x=0,1) が SDCLK 遅延を制御し、最大 1 サイクルになると記載されています。 これはSDCLKx_DELステップが SDCLK の 1/4 であることを意味します 。 SDCLK 遅延 (SDCLKx_DEL) の詳細については、こちらをご覧ください。 答え: 「SDCLK パスの遅延要素は、データ ストロボの遅延エレメントと似ていますが、まったく同じではありません。 ただし、遅延はピコ秒のオーダーであり、古いドキュメントから解釈されたような完全なSDCLKサイクルではありません。」 i.MX6_All

North America Recruiting Campus Events Freescale - North America - is looking for you!  If you want to use the innovative and fresh ideas you are learning in the classroom to contribute to projects that help change lives, then a Freescale internship or co–op position is for you. I want to know more about Freescale internship and co-op opportunities. University Recruiting Calendar for 2013 Quick Facts about Freescale Freescale at a Glance Research More University Programs opportunities(PDF attachment)

Q&A: Delay units in SDCLKx_DEL of MMDCx_MPSDCTRL register Question: Clarify if the delay units, mentioned in  i.MX6 RM in two places are the same : 1. There are delay units for data strobes, that are considered in calibration procedures. 2. There are delay units for clocks SDCLK, mentioned in section 44.12.54 “MMDC PHY CK Control Register (MMDCx_MPSDCTRL)” of the RM. General delay units description states : “ The delay issued by the delay-line (according to the configured value) is absolute and takes into account the operating and temperature conditions. The delay-line has a resolution that may vary from device to device; an increment of 1 delay unit may vary between 20 pSec to 50 pSec.” It may be guessed that the same relates to SDCLK delays, but preliminary i.MX6 specs mention that bit fields SDCLKx_DEL (x=0,1) control SDCLK delay, that can be up to 1 cycle.  This means SDCLKx_DEL step is 1/4  of the SDCLK. Please clarify SDCLK delays (SDCLKx_DEL) in more details. Answer: "The delay elements in the SDCLK path are similar to those in the data strobes but they are not exactly the same. The delay is on the order of picoseconds, though, not a full SDCLK cycle as might have been interpreted from the older document." i.MX6_All

i.MX51 EVK U-boot Working with mainline U-Boot Freescale BSP provides an i.MX51 EVK U-boot port. However, i.MX51 EVK is also supported on I-boot main tree. This quick "how to" teaches how to use it. 0. Get u-boot code from the imx U-Boot Custodian tree: $ git clone git://git.denx.de/u-boot-imx.git 1. Prepare the environment: $ export PATH="$PATH:/opt/freescale/usr/local/gcc-4.1.2-glibc-2.5-nptl-3/arm-none-linux-gnueabi/bin/" $ export CROSS_COMPILE=arm-none-linux-gnueabi- 2. Configure for i.MX 51 EVK $ cd u-boot-imx $ make mx51evk_config 3. Compile $ make u-boot.imx   iMX may SoCs use its internal ROM to execute some instructions at boot time, using "make u-boot.imx" an image containing the instructions 4. Copy the compiled file to a SD card on your host machine, insert the SD card and: $ sudo dd if=u-boot.imx of=/dev/mmcblk0 bs=512 seek=2 "/dev/mmcblk0" should replaced according to your host, use "dmesg" after inserting the SD to find out where is the SD on your host. Unmount it before issuing the dd command. seek 2, skips the first 1K bytes (2x512) of the SD where the ROM expects the boot image for SD. 5. Insert the SD on the i.MX51 EVK, and set the switches for SD card boot and power on the board. i.MX51 Re: i.MX51 EVK U-boot Yocto has this version already 😉 Re: i.MX51 EVK U-boot Great post.    I just used this to replace the u-boot from LTIB and it was straight forward and was working in less than half an hour.   The latest version of u-boot is quite a bit nicer than the old LTIB version.  Do you know where to get a .spec for the git version that could be put into LTIB?  

I.MX51EVK Install U-Boot Installing U-Boot on i.MX51EVK using BDI3000 Unlike older i.MX processor you don't need to select CONFIG_SKIP_LOWLEVEL_INIT because U-Boot lowlevel for i.MX51 doesn't reconfigure RAM memory. It is configured on DCD table. Copy u-boot.bin to /tftpboot because BDI3000 will load it from there. Connect the serial console cable on your i.MX51EVK board and connect to it using minicom. Connect to your BDI3000 through telnet and execute these commands: FSL-iMX51> load 0x97800000 u-boot.bin Loading u-boot.bin , please wait .... Loading program file passed FSL-iMX51> rm pc 0x97800000 FSL-iMX51> go When you execute the last command (“go”) you will see U-Boot starting on serial console. i.MX51

LTIB 创建 Uimage Uboot <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> U-boot 需要 uImage 格式的内核映像。 为了 LTIB 生成 uImage 文件： $导出SYSCFG_KTARG = uImage $./ltib-p 内核 在 U-Boot 中设置内核引导参数： u-boot>setenv bootargs noinitrd console=ttymxc0,115200 init=/linuxrc root=/dev/nfs nfsroot=10.29.244.27:/tftpboot/rootfsip=dhcp 将 10.29.244.27 更改为您的主机 IP。 当 ltib 使用的默认引导加载程序是 redboot 时，需要执行上述过程。 在某些 ltib 版本（2010 年之前）中，默认引导加载程序是 u-boot。在这种情况下，ltib将默认创建uImage

Booting P2010 from On-Chip ROM (eSDHC or eSPI) The on-chip ROM code does not set up any local access windows (LAWs). Access to the CCSR address space or the L2 cache does not require a LAW. It is the user’s responsibility to set up a LAW through a control word address/data pair for the desired target address and execution starting address (which is typically in either DDR or local bus memory space). Required Configurations for SD Card/MMC Booting The configuration settings required to boot from an SD card/MMC are as follows: Ensure that cfg_rom_loc[0:3] (Boot_Rom_Loc) are driven with a value of 0b0111. Only one core can be in booting mode. If your device has multiple cores, all other cores must be in a boot hold-off mode. The CPU boot configuration input, cfg_cpux_boot, should be 0, where x is from 1 to n (n = the number of cores). Booting from the eSDHC interface can occur from different SD card slots if multiple SD card slots are designed on the board. In this case, ensure the appropriate SD card/MMC is selected For example, on the P1020 board, bit 7 of the SW8 is used to select which SD/MMC slot is used. If SW8[7] = 1, an SD card/MMC must be put to the external SD card/MMC slot (J1). TIP The polarity of the SDHC_CD signal should be active-low.  Required Configurations for EEPROM Booting The configuration settings required to boot from an EEPROM are as follows: Ensure that cfg_rom_loc[0:3] (Boot_Rom_Loc) are driven with a value of 0b0110. Only one core can be in booting mode. If your device has multiple cores, all other cores must be in a boot hold-off mode. The CPU boot configuration input, cfg_cpux_boot, should be 0, where x is from 1 to n (n = the number of cores). The eSPI chip select 0 (SPI_CS[0]) must be connected to the EEPROM that is used for booting. No other chip select can be used for booting. This is because during booting, the eSPI controller is configured to operate in master mode. Booting from the eSPI interface only works with SPI_CS[0]. QorIQ P2 Devices

P1020/P1011 本地公交车常见问题解答 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 对于 P1020，目标是实现本地总线的最大频率，那么时钟需要满足哪些要求？ 您应该密切关注平台时钟 PLL 滤波以尽量减少抖动。一般来说，应保持总线尽可能短，并使走线长度与时序匹配，以满足上述硬件规格要求。 QorIQ P1设备

P1010/P1014 DDR Specific FAQs P1010 has only a single pair of MCK signal, while my device has four Chip Select signals. In a scenario connecting a lot of memory devices under four CS, can the single pair of MCK really drive all of memory devices which are connected by fly-by topology on each CS? In case of P1010 (which has only one MCK), is it really practical to connect DDR3 memory devices under all of four CS? Would it be necessary to use "external CLK buffer" in such a case using four CS? P1010 was designed for low-cost systems, and as such some of the pins seen on other QorIQ devices (CKE2/3, ODT2/3) were removed to save on cost. For a single-rank, fly-by topology, only one CS would be used. If more ranks were needed, this would be addressed with stacked memories (DDR3 devices that take up to four CS signals). How does one set up the P1010 or P1014 for a 16 bit data bus size? To set the data bus width, you need to set DDR_SDRAM_CFG[DBW] bits of the register given in section 9.4.1.7, Page-9-20 of P1010RM Rev-B. Is it allowed to use four chip-selects with P1010? In my understanding, one ODT signal should be used and be controlled per chip-select? However P1010 has two MODT. P1010 is designed to use only one chip select with discrete DDR3 DRAM. This requires one CS, one ODT, and one CKE with one clock pair. Additional CS/ODT/CKE are designed for using stacked die DDR3 DRAMs. The four CS, two ODT & CKE, are useful if dual or quad stacked die discrete DDR3 DRAM were used. For the write leveling, does the P1010 use DQ[0,8,16,24] or use all DQ bit to drive status back to the DDR controller? P1010 DDR controller can support the write leveling status on any of the data bits within the data byte from a JEDEC standard DDR3 SDRAM. QorIQ P1 Devices

P1020/P1011 路線バス特有のよくある質問 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> P1020の場合、ローカルバスの最大周波数を達成するという目標があり、満たす必要のあるクロックの要件は何ですか? ジッターを最小限に抑えるために、プラットフォーム クロック PLL フィルタリングに細心の注意を払う必要があります。一般に、バスはできるだけ短くし、トレースの長さは前述のハードウェア仕様の要件を満たすためにタイミングに一致させます。 QorIQ P1デバイス

オンチップROM(eSDHCまたはeSPI)からのP2010の起動 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> オンチップROMコードでは、ローカルアクセスウィンドウ(RAW)は設定されません。CCSR アドレス・スペースまたは L2 キャッシュへのアクセスには、LAW は必要ありません。目的のターゲット アドレスと実行開始アドレス (通常は DDR またはローカル バス メモリ空間のいずれか) の制御ワード アドレス/データ ペアを使用して LAW を設定するのは、ユーザーの責任です。 SDカード/ MMCブートに必要な構成 SD カード/MMC から起動するために必要な設定は次のとおりです。 cfg_rom_loc[0:3] (Boot_Rom_Loc) が値 0b0111 で駆動されていることを確認します。 ブート モードにできるコアは 1 つだけです。デバイスに複数のコアがある場合は、他のすべてのコアをブートホールドオフモードにする必要があります。CPU ブート設定入力 cfg_cpux_boot は 0 で、x は 1 から n (n = コア数) です。 ボード上に複数のSDカードスロットが設計されている場合、eSDHCインターフェイスからの起動は、異なるSDカードスロットから発生する可能性があります。この場合、適切な SD カード/MMC が選択されていることを確認してください。たとえば、P1020 ボードでは、SW8 のビット 7 を使用して、使用する SD/MMC スロットを選択します。SW8[7] = 1の場合、SDカード/ MMCを外部SDカード/ MMCスロット(J1)に挿入する必要があります。 先端 SDHC_CD信号の極性はアクティブローである必要があります。 EEPROMブートに必要な設定 EEPROMからブートするために必要な設定は次のとおりです。 cfg_rom_loc[0:3] (Boot_Rom_Loc) が 0b0110 の値で駆動されていることを確認します。 ブート モードにできるコアは 1 つだけです。デバイスに複数のコアがある場合は、他のすべてのコアをブートホールドオフモードにする必要があります。CPU ブート設定入力 cfg_cpux_boot は 0 で、x は 1 から n (n = コア数) です。 eSPIチップセレクト0(SPI_CS[0])は、ブートに使用するEEPROMに接続する必要があります。他のチップセレクトは起動には使用できません。これは、ブート中に eSPI コントローラーがマスター モードで動作するように構成されているためです。eSPI インターフェイスからの起動は、SPI_CS[0] でのみ機能します。 QorIQ P2デバイス

P1020/P1011 メモリ コントローラー固有の FAQ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> P1020 で ABSWP ビット (LBCR) を設定すると、アドレス バイトはスワップされますか、それともミラーリングされますか。また、LBCR [ABSWP] は、NAND フラッシュを除くローカル バスで使用されているすべてのデバイス (チップ セレクト) に影響を与えていることを確認できますか? ABSWPビット(つまり、ABSWP=1) の場合、address=0x12345678.次に、LAD [0:15] = 0x7856 および LA[16:31]=0x5678 です。LBCR [ABSWP] は、NAND フラッシュを除くローカル バスで使用されるすべてのデバイス (チップ セレクト) に影響します P1011のNANDフラッシュコントローラーの速度とサイズはどれくらいですか? AeLBCは83MHzで動作します。最小twcでは、2 LCLK、つまりLCLKの半分の周波数に等しくなります。eLBC でサポートされる最大ページ・サイズは 2K です。 P1011の5つのddr3チップすべてを1つのmckで駆動する場合、レベリング機能を使用できますか?また、これにはどのトポロジをお勧めしますか? はい、フライバイトポロジーによって導入される異なるチップ間の追加の飛行時間スキュー遅延を補償するために、ライティングレベリング機能を使用する必要があります。ただし、クロックをフライバイ トポロジでルーティングし、アドレス、コマンド、および制御信号を他のトポロジでルーティングすることはお勧めしません。JEDEC DDR3 ルーティング トポロジの詳細については、[www.JEDEC.org] を参照してください。 32ビットデータインターフェースは、ABSWPを適用するかどうかを制御する唯一の方法ですか(つまり、ABSWPは8ビットおよび16ビットのデータインターフェイスに影響しますが、32ビットのデータインターフェイスには影響しません)? ABSWP は 32 ビット インターフェイスにも影響し、16 LSB アドレスのみが LAD[0:15] に表示され、ゼロが LAD[16:31] に出力されるため、ABSWP を 32 ビット インターフェイスに設定することはお勧めしません。 QorIQ P1デバイス

サーボの紹介 - パートI <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> RCサーボとそのインターフェースの検討。パルス幅変調のレビューを行い、構成例を示します。 ビデオリンクを見る: 1465 (マイビデオで視聴)

Task #2 - First build Synchronize your source code Create your local branch Why should I create a local branch? Choose your board Start to build Synchronize your source code Source code you have is one week old now. So, first step is synchronize it. $ repo sync‍‍‍ Create your local branch $ repo start --all‍‍‍ Why should I create a local branch? If you change *any* source code (for choosing another preferred kernel, for example) and want to sync again, or use master instead of dylan, you may be able to rebase or sync your source code, even with changes. Or you found a bug, fixed that, and want to send a patch to community. Example of a system with 2 branches: zeus and new_feature (the asterisk shows the current branch)    $ repo branches * new_feature | in all projects zeus | in all projects‍‍‍ Choose your board The following command display the usage, with a list of all supported machines, all supported community distros and examples of Poky's distro: $ source setup-environment build‍ Usage: MACHINE= DISTRO= source setup-environment Usage: source setup-environment machine name distro name build directory The first usage is for creating a new build directory. In this case, the script creates the build directory , configures it for the specified and , and prepares the calling shell for running bitbake on the build directory. The second usage is for using an existing build directory. In this case, the script prepares the calling shell for running bitbake on the build directory . The build directory configuration is unchanged. Supported machines: apalis-imx6 ccimx6ulsbcexpress ccimx6ulsbcpro cgtqmx6 cm-fx6 colibri-imx6 colibri-imx6ull colibri-imx7 colibri-vf cubox-i imx233-olinuxino-maxi imx233-olinuxino-micro imx233-olinuxino-mini imx233-olinuxino-nano imx6dl-riotboard imx6qdl-variscite-som imx6q-dms-ba16 imx6qsabrelite imx6sl-warp imx6ul-pico imx7d-pico imx7s-warp m28evk m53evk nitrogen6sx nitrogen6x nitrogen6x-lite nitrogen7 nitrogen8m pcm052 tx6q-10x0 tx6q-11x0 tx6s-8034 tx6s-8035 tx6u-8033 tx6u-80x0 tx6u-81x0 ventana wandboard imx23evk imx25pdk imx28evk imx51evk imx53ard imx53qsb imx6qdlsabreauto imx6qdlsabresd imx6slevk imx6sllevk imx6sxsabreauto imx6sxsabresd imx6ulevk imx6ullevk imx7dsabresd imx7ulpevk imx8mmevk imx8mqevk imx8qmmek imx8qxpmek ls1012afrwy ls1012ardb ls1021atwr ls1043ardb ls1046ardb ls1088ardb ls1088ardb-pb ls2080ardb ls2088ardb lx2160ardb mpc8548cds p1020rdb p2020rdb p2041rdb p3041ds p4080ds p5040ds-64b p5040ds t1024rdb-64b t1024rdb t1042d4rdb-64b t1042d4rdb t2080rdb-64b t2080rdb t4240rdb-64b t4240rdb Supported Freescale's distros: fslc-framebuffer fslc-wayland fslc-x11 fslc-xwayland Available Poky's distros: poky-altcfg poky-bleeding poky poky-tiny Examples: - To create a new Yocto build directory: $ MACHINE=imx6qdlsabresd DISTRO=fslc-framebuffer source setup-environment build - To use an existing Yocto build directory: $ source setup-environment build ERROR: You must set MACHINE when creating a new build directory. ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ An example of command line to setup the build environment is (read and answer if you accept EULA or not): MACHINE=imx8mmevk DISTRO=fslc-wayland source setup-environment build‍ (...) Do you accept the EULA you just read? (y/n) y EULA has been accepted. Welcome to Freescale Community BSP The Yocto Project has extensive documentation about OE including a reference manual which can be found at: http://yoctoproject.org/documentation For more information about OpenEmbedded see their website: http://www.openembedded.org/ You can now run 'bitbake ' Common targets are: core-image-minimal meta-toolchain meta-toolchain-sdk adt-installer meta-ide-support Your build environment has been configured with: MACHINE=imx8mmevk SDKMACHINE=i686 DISTRO=fslc-wayland EULA= ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Now, you are in new created build directory. Your default build/conf/local.conf file can looks like: MACHINE ??= 'imx8mmevk' DISTRO ?= 'fslc-wayland' PACKAGE_CLASSES ?= 'package_rpm' EXTRA_IMAGE_FEATURES ?= "debug-tweaks" USER_CLASSES ?= "buildstats image-mklibs image-prelink" PATCHRESOLVE = "noop" BB_DISKMON_DIRS ??= "\ STOPTASKS,${TMPDIR},1G,100K \ STOPTASKS,${DL_DIR},1G,100K \ STOPTASKS,${SSTATE_DIR},1G,100K \ STOPTASKS,/tmp,100M,100K \ ABORT,${TMPDIR},100M,1K \ ABORT,${DL_DIR},100M,1K \ ABORT,${SSTATE_DIR},100M,1K \ ABORT,/tmp,10M,1K" PACKAGECONFIG_append_pn-qemu-system-native = " sdl" CONF_VERSION = "1" DL_DIR ?= "${BSPDIR}/downloads/" ACCEPT_FSL_EULA = "1"‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ For the current list of supported board, take a look on FSL Community BSP Release Notes 2.4 (Draft document) documentation Or, see the FSL Community BSP  Release Notes Start to build There are a huge list of images available. Some images includes more packages than others, you can see a list of FSL Community BSP images with description here. The list of supported images from Yocto Project (with description) is here. When an image has more packages included, it takes longer to build. Another way to list all the images you have installed in your metadata is: $ find ../sources -name *image*‍‍   For the goal of this training, any image is good, but a suggestion is presented in next command line: (make sure you are still in build directory) $ cd build $ bitbake core-image-base‍‍‍‍‍‍‍‍ Note (Sept2019): Required disk space for build image is ~31GB Go to Yocto Training - HOME Go to Task #1 - Download the source code Go to Task #3 - The build result Yocto Project Re: Task #2 - First build My memory is not trustable at all. I remember memtool was already installed on fsl-image-test at some point of time. When? I don´t know. But add on your local.conf: CORE_IMAGE_EXTRA_INSTALL += "memtool" and you will have it installed on *any* image (much better than rely on my memory :D) Re: Task #2 - First build I can help, for sure. Please try to reproduce your issue with dora branches and if you do, please get a patch applied in Poky to fix it. Once you does it, I can help with the upstreaming process for it 🙂 Re: Task #2 - First build Hi all, for LeonardoSandovalGonzalez : I don't know the other two my omonymous! I changed my avatar in a car (I work on automotive projects 😄 )! I've already deleted all my files and repeated the Daiane guide with dylan and with master branch. Master branch don't have the issue. for DaianeAngolini : if you suggest to use dora I'll be happy to follow your advice. The image fsl-image-test has the memtool already installed? for OtavioSalvador : I'm a beginner in this world but I'll be happy to learn how create and send a patch. I don't want to mess! If you have some time to help me I thanks in advance. Bye. Re: Task #2 - First build Dylan is still being maintained; it just needs to be send as a fix for oe-core mailing list. Please put: [for-dylan][PATCH] ... in subject for the patch. So people handle it accordingly. Re: Task #2 - First build Thanks for letting us know! You really need to be on dylan, now that dora was released? In this case we can work together to get it fixed on your local files. I would need to double check if dylan is still supported for bugfixes..... Re: Task #2 - First build Hi francpalm (there are three francesco Palmisanos on the community, is that you multiple times?!!) Tthanks for sharing the fix. This patch does not belong to meta-fsl-* layers (I think), so it must be send to another list. Before you send the patch, can you rebuilt your image with an new build folder? if case you have already done this, ignore this step and send the patch. OtavioSalvador FYI. Leo Re: Task #2 - First build Hi all, in dylan branch I think there is a bug in file: /build/tmp/work/i686-linux/elfutils-native/0.148-r11/line2addr.c at line 135 there is: switch (sscanf (a.arg, "%a[^:]:%d", &a.file, &a.line)) instead of: switch (sscanf (a.arg, "%m[^:]:%d", &a.file, &a.line)) This bug causes a compilation error when I try: bitbake fsl-image-test In master branch I don't found the same issue, but in this branch there isn't the memtool! Please verify! LeonardoSandovalGonzalez DaianeAngolini Bye. P.S.: the compilation error is: | /media/francesco/DATI/yocto-bsp/build/tmp/work/i686-linux/elfutils-native/0.148-r11/elfutils-0.148/tests/line2addr.c:135:7: error: format '%a' expects argument of type 'float *', but argument 3 has type 'char **' [-Werror=format=] |        switch (sscanf (a.arg, "%a[^:]:%d", &a.file, &a.line)) |        ^ Re: Task #2 - First build From your description it seems to be a hardware issue; I'd bet a fan issue. Re: Task #2 - First build I have a Intel dual-core 1.93Ghz(I guess) processor. More than 200GB hard disk space and 3GB RAM. OS: Ubuntu 12.04 LTS (32-bit) I dint have application running while building. Is this not sufficient ? Moreover, I was compiling only for a base image not gui. It automatically shuts down every time. Under build/tmp/work, I can find only 3 files. Any hints to overcome this problem? Re: Task #2 - First build muthuswamydikshit, without more context (as build log or something) it is hard to guess. My rough guess is not enough memory for the build and/or disk space. Yocto is voracious for computational resources so this might be the cause of problem. Re: Task #2 - First build Thanks for the material! It works fine on my 64-bit Ubuntu 12.04 with i5 processor but fails on my 32-bit Ubuntu 12.04 with qual-core processor. But something strange happens while giving 'bitbake core-image-base'. It automatically shuts down my system everytime. I have not copied anything betwenn my two machines. I need to work only on my 32-bit system. Can you please help?? Re: Task #2 - First build From yocto point of view, yes, it makes all difference. Yocto only "see" the right version package, because it only "looks for" the right version package. But, if you think you can use another version, you can change the recipe in order to "add a new package". I don´t think it worth. Be sure your Internet connection is OK. Be sure all mirrors are up. And try again. Yesterday I was able to go from download source code from a complete image downloading everything again. So I think it was only a period of instability. Re: Task #2 - First build I'm getting a bit further with this now. The packages I can't load are not actually present on the relevant web sites, because they have been superseded. http://www.zlib.net/zlib-1.2.7.tar.bz2 has been replaced with 1.2.8 http://www.apache.org/dist/apr/apr-util-1.5.1.tar.gz has been replaced with 1.5.2 http://www.apache.org/dist/subversion/subversion-1.7.8.tar.bz2 has been replaced with 1.7.11 The "master" branch in yocto poky has already made the necessary changes to use the new packages instead, but the "dylan" branch has not. I tried changing the repo manifest to use the "master" branch instead, but that causes other problems. I guess the answer is to push the necessary changes to yocto and then everyone can get them. Any comments? Re: Task #2 - First build Hi Daiane, Thanks for the response. I just modified my post a few minutes ago with new information, which you may not have seen: Taking the subversion link as an example, if I go to the parent directory http://www.apache.org/dist/subversion I can see that the required file (version 1.7.8) is not actually there - the oldest version seems to be 1.7.11. Does that make a difference? Regards, Dave C Re: Task #2 - First build Well, When I face the downloads issues I wait for sometime and try again. You can try to get the same package from other source. Re: Task #2 - First build I can use wget for the FTP link, but all three HTTP links fail with 404 using wget. Taking the subversion link as an example, if I go to the parent directory http://www.apache.org/dist/subversion I can see that the required file (version 1.7.8) is not actually there - the oldest version seems to be 1.7.11. Re: Task #2 - First build are you able to download those packages if you use wget? $ wget ftp://ftp.ossp.org/pkg/lib/uuid/uuid-1.6.2.tar.gz for example? Re: Task #2 - First build The instructions above are very simple, but I seem to be getting a few problems, I'm afraid. I changed conf/local.conf to use "imx6qsabrelite" and ran bitbake. I get a few warnings, which I'm guessing are OK since they seem to use mirror sites instead, but I'm also getting some errors which appear to be fatal, regarding the Boundary Devices git repository. I tried accessing the Boundary Devices git repository without bitbake (just typing "git clone git://github.com/boundarydevices/linux-imx6.git") and that seems to work without any errors, so is it possible that there's a problem with bitbake somewhere? All comments / suggestions welcome! Full output is shown below: dchirgwin@dc-ubuntu2:~/fsl-community-bsp/build$ bitbake core-image-base Pseudo is not present but is required, building this first before the main build Parsing recipes: 100% |#########################################| Time: 00:02:15 Parsing of 1277 .bb files complete (0 cached, 1277 parsed). 1645 targets, 68 skipped, 0 masked, 0 errors. Build Configuration: BB_VERSION        = "1.18.0" BUILD_SYS         = "i686-linux" NATIVELSBSTRING   = "Ubuntu-12.10" TARGET_SYS        = "arm-poky-linux-gnueabi" MACHINE           = "imx6qsabrelite" DISTRO            = "poky" DISTRO_VERSION    = "1.4.2" TUNE_FEATURES     = "armv7a vfp neon" TARGET_FPU        = "vfp-neon" meta             meta-yocto        = "bct:d734ab491a30078d43dee5440c03acce2d251425" meta-oe           = "bct:81bf02c1ed858b8a7ae9297b8eab7d9355d0a48c" meta-fsl-arm      = "bct:afe2162644544a92a517f1d51211fdcb76bb1a29" meta-fsl-arm-extra = "bct:5f5a9cfcad223f5a1c623346780510ffcdc012ab" meta-fsl-demos    = "bct:724cfb929748f47782dea3b1dc412b028f6f3515" NOTE: Resolving any missing task queue dependencies NOTE: Preparing runqueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks NOTE: Tasks Summary: Attempted 63 tasks of which 0 didn't need to be rerun and all succeeded. Loading cache: 100% |###########################################| ETA:  00:00:00 Loaded 1646 entries from dependency cache. Build Configuration: BB_VERSION        = "1.18.0" BUILD_SYS         = "i686-linux" NATIVELSBSTRING   = "Ubuntu-12.10" TARGET_SYS        = "arm-poky-linux-gnueabi" MACHINE           = "imx6qsabrelite" DISTRO            = "poky" DISTRO_VERSION    = "1.4.2" TUNE_FEATURES     = "armv7a vfp neon" TARGET_FPU        = "vfp-neon" meta             meta-yocto        = "bct:d734ab491a30078d43dee5440c03acce2d251425" meta-oe           = "bct:81bf02c1ed858b8a7ae9297b8eab7d9355d0a48c" meta-fsl-arm      = "bct:afe2162644544a92a517f1d51211fdcb76bb1a29" meta-fsl-arm-extra = "bct:5f5a9cfcad223f5a1c623346780510ffcdc012ab" meta-fsl-demos    = "bct:724cfb929748f47782dea3b1dc412b028f6f3515" NOTE: Resolving any missing task queue dependencies NOTE: Preparing runqueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks WARNING: Failed to fetch URL http://www.zlib.net/zlib-1.2.7.tar.bz2, attempting MIRRORS if available WARNING: Failed to fetch URL ftp://ftp.ossp.org/pkg/lib/uuid/uuid-1.6.2.tar.gz, attempting MIRRORS if available WARNING: Failed to fetch URL http://www.apache.org/dist/apr/apr-util-1.5.1.tar.gz, attempting MIRRORS if available WARNING: Failed to fetch URL http://www.apache.org/dist/subversion/subversion-1.7.8.tar.bz2, attempting MIRRORS if available WARNING: Failed to fetch URL git://github.com/boundarydevices/linux-imx6.git, attempting MIRRORS if available ERROR: Fetcher failure: Fetch command failed with exit code 128, output: Cloning into bare repository '/home/dchirgwin/fsl-community-bsp/downloads//git2/github.com.boundarydevices.linux-imx6.git'... fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed ERROR: Function failed: Fetcher failure for URL: 'git://github.com/boundarydevices/linux-imx6.git'. Unable to fetch URL from any source. ERROR: Logfile of failure stored in: /home/dchirgwin/fsl-community-bsp/build/tmp/work/imx6qsabrelite-poky-linux-gnueabi/linux-boundary/3.0.35-r0/temp/log.do_fetch.7065 ERROR: Task 281 (/home/dchirgwin/fsl-community-bsp/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary_3.0.35.bb, do_fetch) failed with exit code '1' NOTE: Tasks Summary: Attempted 983 tasks of which 148 didn't need to be rerun and 1 failed. Waiting for 0 running tasks to finish: Summary: 1 task failed:   /home/dchirgwin/fsl-community-bsp/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary_3.0.35.bb, do_fetch Summary: There were 5 WARNING messages shown. Summary: There were 2 ERROR messages shown, returning a non-zero exit code. dchirgwin@dc-ubuntu2:~/fsl-community-b Re: Task #2 - First build Hi if you ran the setup-enviroment script, it automatically sets these for your. Both values should be equal to the number of cores on your HOST machine. You can also try doubling this value for the MAKE related variable, but I do not think you gain much. Leo Re: Task #2 - First build I think I find the answer.  It seems these two fields are related to bitbake settings for the host computers. So it is not related to the target.. Source: Yocto Project Reference Manual Please correct me if I am wrong. thanks Re: Task #2 - First build What should be the value for the BB_NUMBER_THREAD and PARALLEL_MAKE for the sabrelite in the conf/local.conf file? By default, the value are: BB_NUMBER_THREADS = '1' PARALLEL_MAKE = '-j 1' Should I set the value to 4 or 8 ? Thanks Re: Task #2 - First build I think I find it, the conf file for the sabrelite is now in "meta-fsl-arm-extra". Re: Task #2 - First build hello, the conf file for "imx6qsabrelite.conf" is not in this folder anymore. I dont see it in the git folder or in my computer after the download. github.com/Freescale/meta-fsl-arm or /fsl-community-bsp/build/conf Where did it go ? Thanks ssinfo Re: Task #2 - First build I pointed to meta-fsl-arm release notes, but I can include the non-freescale board supported. For fsl-image-gui/-sdk, I think it´s not the right task to point how both images diverges.  I prefer to start with core-image-base and then include another task at the end showing a more complete "how to" for images, maybe how to create one image from scratch. What do you think? Thanks a lot Leo :smileygrin: Re: Task #2 - First build My 2 cents: 1. It would be nice to point to the other non-freescale machines Yocto supports. 2. The biggest image is (I believe) fsl-image-gui-sdk, but from user's perspective the fsl-image-gui is the fattest (perhaps adding a footnote to indicate this) 3. The link to Task # 1 is missing at the end of the document Daiane, let me know if you want me to include the above changes (if you first approve them ) Leo

i.MX6 DDR3 Write Post Amble Delay (tWPST) too short. Issue: During DDR3 Burst Write, the DQS strobe signal must be driven low for a minimum of 0.3 x cycle period on the last data clock cycle before it is released. This ensures sufficient time for the write to be strobed correctly. When measuring this timing parameter, it has often been found to be too short. This may be contributing to write errors on customer boards, depending on the signal layout used by the board. Root Cause: The internal DQS strobe enable signal is controlled by the MMDC, which is tied to the SDCLK clock signal. But the DQS strobe signal can be delayed in the MMDC to match different SDCLK trace lengths by using Write Leveling parameters to ensure the the DQS strobe edge reaches the DDR3 device at the same time the SDCLK edges reaches the device. If the write level delay is too long, the MMDC can crop the end of the DQS strobe signal too short, causing a violation of the Write Post Amble Delay timing specification and potentially leading to  write errors. How much delay in the Write Leveling parameter would cause this problem? The Reference Manual states that a delay around half a cycle may cause problems, but testing on some boards indicates that delays even as short as 1/4 a cycle could cause violations of the Write Post Amble Delay. Solution: The MMDC was designed with the ability to add extra time to the strobe enable period during write procedures. This parameter is referred to as Write Additional Latency. It is found in the MMDCx_MDMISC register and the field is labeled as WALAT. Incrementing the value of this register field by one adds a full clock cycle delay to the Write Post Amble period, and ensures enough time at the end of a burst write to guarantee a correct write. There is no maximum value to Write Post Amble Delay. Setting WALAT = 1 (or larger if WL parameters are larger) will cause a small hit in overall performance, but will add to the reliability of write operations, particularly on boards that require larger WL parameter settings.

飞思卡尔杯线扫描相机 - 第三部分 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 使用线扫描相机教程第 2 部分中描述的逻辑，将显示界面的实际实现。FRDM-TFC 屏蔽的示例代码将用作完全中断驱动的相机接口的参考实现。 （在 “我的视频” 中查看）

フリースケールカップラインスキャンカメラ-パートIII <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ラインスキャンカメラチュートリアルのパート2で説明したロジックを使用して、インターフェースの実際の実装を示します。FRDM-TFCシールドのサンプルコードは、完全割り込み駆動のカメラインターフェイスのリファレンス実装として使用されます。 (マイビデオで視聴)

サーボ入門 - パートII <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> FRDM-TFC に用意されているサーボのサンプル コードを確認します。TPM 周辺機器の初期化と簡単なドライバー インターフェイスが表示されます。 ビデオリンクを見る: 1464 (マイビデオで視聴)

Fuse Provisioning on LS1046ARDB 1. Fuse Provisioning Utility Introduction 2. Input File for Fuse Provisioning Tool 3. Build Fuse Provisioning Firmware Image with flex-builder and Deploy the Firmware Image 4. Build and Deploy Fuse Provisioning Image Manually 5. Validate Fuse Provisioning

Apply Arduino virtual adapter into compatible header This article was written for MCUXpresso Config tools v12 and older. Newer MCUXpresso Config tools can map Arduino expansion boards into compatible expansion headers automatically, without the need for any virtual adapter and even with possibility to utilize all the spare pins! This tutorial shows how to apply and use the appropriate Arduino virtual adapter file (virtual adapters are attached) to utilize Arduino compatibility across different expansion headers. Benefit Virtual adapter board files allow users of the Pins tool from the MCUXpresso Config tools suite to use the expansion board file intended for a standard Arduino expansion header with other NXP expansion headers that are compatible with the Arduino standard but not mechanically identical (for example, they use two rows of pins). Arduino-compatible expansion headers Freedom Header (Kinetis FRDM boards) LPCXpresso V3 (LPC boards) LPCXpresso V3 Mirrored Normally, such expansion headers are treated as different in the Pins tool, but the virtual adapter file transforms the current board header into the standard Arduino header so the user can apply the expansion boards referencing the standard Arduino header. For details on the expansion board, see Creating expansion board definition file for Arduino Multifunction shield.   Step 1: Open the Expansion Header view Open the Expansion Header view if it is not open. In the standalone MCUXpresso Config tools, select the command Views > Expansion header  In the MCUXpresso IDE, select the command Window > Show view > Expansion Header  Step 2: Apply the Arduino virtual adapter file The application of the virtual adapter file is the same as the application of the expansion board definition file. Use the attached virtual adapter files. Press the “Apply expansion board” button Locate the virtual adapter file and confirm Select if you want to create the functional group (recommended) Choose which names you would like to use in your source code Apply the expansion board Step 3: Switch to the newly created header Choose the Arduino adapter header option and select the newly created “Arduino adapter” header. Using the “+” button, select and apply an expansion board intended for the standard single-row Arduino header, and it will be connected to appropriate pins automatically.