Atheros Tower Module (TWR-WIFI-AR4100P) Patch for Freescale MQX™ 4.0.2 Available Atheros WiFi Tower Module (TWR-WIFI-AR4100P) support patch for Freescale MQX™ 4.0.2  is available at MQX Downloads. Files available # Name Description 1 FSL_MQX_ATHEROS_RELEASE_NOTES_4_0_2  Freescale   MQX™ Atheros Wifi package 4.0.2 Release Notes 2 Freescale   MQX RTOS 4.0.2 Atheros Wifi package Atheros   Wifi solution for MQX™ 4.0.2 Real-Time TCPIP Communications Suite

为飞思卡尔杯赛车设计速度传感器第一部分 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 该视频将探讨如何将速度感应设计到车辆平台中。图中显示了磁铁和传感器放置的示例。 （在 “我的视频” 中查看） 飞思卡尔杯内容

Creating and Adding Components to new Bareboard project.pdf This manual explains how to create a project in CW and add components to Processor Expert. It also includes a couple of examples to print and get data with the printf and scanf functions from the stdio library by using Serial component (UART). This manual explains how to create a project in CW and add components to Processor Expert. It also includes a couple of examples to print and get data with the printf and scanf functions from the stdio library by using Serial component (UART). Freedom Development Platform

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

オンチップ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デバイス

Codewarrior 10をダウンロードしてインストールします <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 1. CodeWarrior 10評価版のダウンロード(Eclipse、Windowsホスト) マイクロコントローラをプログラムするには、CodeWarrior統合開発環境をセットアップする必要があります。CodeWarrior は、 Freescale.com Web サイトで入手できます。 方法1:直接リンク 直接ダウンロードリンク (注意-リンクが最新ではない場合があります) 方法2:ダウンロードリンクに移動します Freescale.com から、以下をクリックしてください。 ページ上部の「デザインリソース」タブ 次に、「ソフトウェアとツール」に移動します。 そして「Codewarrior Devleopment Tools」へ 「CodeWarriorを今すぐダウンロード」リンクをクリックします。 「評価版のダウンロード」リンクをクリックしてください。 このページ内で、ブラウザの「検索」機能(通常はCTRL-F)を使用して、 テキスト文字列「Kinetis」を検索します。 「Evaluation: CodeWarrior for Microcontrollers(Eclipse, Windows-hosted) version」の隣にある「download」ボタンをクリックしてください。そしてそれをあなたのコンピュータに保存します。 2. CodeWarriorのインストール CodeWarrior Development Studio for Microcontrollers v10をインストールするには、インストールをダブルクリックします。 パッケージとウィザードがインストールプロセスをガイドします。 インストールに関する注意事項: Windows Vista または Windows 7 を使用していますか? 1. CodeWarriorインストーラは、「管理者として実行」オプションを使用して実行する必要があります。CodeWarriorサービス パックは Eclipse Updater と共にインストールされます。アップデーターもこのオプションと一緒に実行する必要があります。はじめに Eclipse Updaterは、メニューの「Window > Install new software」を選択します。 2. Eclipseには、インストールフォルダへの読み取り/書き込みアクセス権が必要です。Eclipseのインストールフォルダに すべてのユーザーに適切な権限を与えること。 3. プロジェクト ワークスペースに読み取りと書き込みのアクセス許可があることを確認する 評価版ユーザー: 評価版をインストールする場合、評価版ライセンスは 製品であり、登録する必要はありません。このライセンスでは、プロジェクトを次のように開発することができます。 Professional Edition は 30 日間の評価期間内です。30日後、ライセンスはスペシャルとして機能します エディションライセンス(永久無料ですが、機能制限があります)は、無制限のアセンブリコードをサポートします。 HCS08/RS08 派生物の場合は 32KB の C コード、V1 ColdFire 派生物の場合は最大 64KB の C コード V2-V4 ColdFireおよびKinetis派生物の場合は最大128KBのCコード、最大512KBのCコード MPC56xxの派生物。 CodeWarriorのダウンロードとインストールが完了したら、KinetisのLEDの点滅チュートリアルの一部として、P&Eのダウンロードとインストールに戻ることができます その他のリソース: CW10ユーザーマニュアル —上記のユーザーマニュアルには、CodeWarriorのインストールディレクトリ内にある他の役立つドキュメントのリストがあります。 (例: \MCU\Help\PDF\) フリースケール・カップの内容

MCUXpresso for VS Code Curriculum Documentation MCUXpresso for VS Code Documentation  This training currently covers the following areas: General Usage Getting Started - Step by step [video series] Getting Started - Installation and importing SDKs Importing Projects from the MCUXpresso SDK  Working with SDK examples Debugging with the RTOS DETAILS view  How to import a GUI Guider project to VS Code Reference Guides for specific hardware Getting started with MIMXrt1060-EVK Trustzone Examples on LPC55S6x Multicore Examples on LPC55S6x  SDRAM Examples on RT1060 AN14120: Debugging Cortex-M on i.MX 8M, i.MX 8ULP, and i.MX 93   Zephyr Zephyr: Getting Started in VS Code Zephyr: Hello World Zephyr: Kconfig Zephyr: Debug Zephyr: Devicetree  Zephyr: Revert Workspace Zephyr: Custom Board  MCUXpresso for VS Code

KL02 与键盘按键相比...太棒了！ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 您可能已经听说过 Kinetis 方面的新产品。 是的，说到 KL02，尺寸仅为 1.9 毫米 x 2.0 毫米。看一下这张图片，其中这款基于 ARM 的强大芯片与实际规模进行了比较，虽然体积如此之小，但其 GPIO 却比最接近的竞争 MCU 多 60%。：笑脸：！！！ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 您可能已经听说过 Kinetis 方面的新产品。 是的，说到 KL02，尺寸仅为 1.9 毫米 x 2.0 毫米。看一下这张图片，其中这款基于 ARM 的强大芯片与实际规模进行了比较，虽然体积如此之小，但其 GPIO 却比最接近的竞争 MCU 多 60%。：笑脸：！！！ Kinetis L系列MCU

MCUXpresso SDK: GitHub + VS Code Overview The MCUXpresso SDK 24.12.00 is fully hosted on GitHub. Users are able to clone the SDK and easily keep up to date with changes. Version control transparency allows users to review commits, tags, diffs, etc. Source Control The MCUXpresso SDK on GitHub is composed of multiple groups of software distributed among different repositories. The MCUXpresso SDK uses the popular west manifest to specify what software is included. This method of delivering software was inspired by Zephyr. The manifests folder contains the manifest file to initialize and update the west workspace. In the mcuxsdk folder you'll find the MCUXpresso SDK source code, examples, middleware integration and script files. Both of these folders contain a .git directory that contains information to track changes, branches, and history of the project. Visual Studio Code: CLI To interact with the repo within VS Code through a CLI, open a Terminal. The Terminal can be opened from the menu in the top left of the screen. Alternatively, the Terminal and other monitors are hidden in a bar at the bottom of the screen. Navigate to the bottom of the screen, use the cursor to drag the bar and reveal the Terminal. Once in the CLI, git commands can be run to track the status of the MCUXpresso SDK repositories. Visual Studio Code: GUI The command line is useful for many things, however, sometimes a gui might be productive. The source control gui that VS Code provides can be accessed through the menu on the top left of the screen or in the extensions sidebar. The source control gui in Visual Studio Code contains three sections: Source Control Repositories - These are the repositories that are currently visible to the workspace. Each repository contains a menu that allows the user to pull, push, navigate across branches, etc. Source Control - This tracks changes made by the user. Here, you will see staged changes, commits, etc. *Note: Contribution to the MCUXpresso SDK is currently not open.     Source Control Graph - This provides a comprehensive overview of the project. The graph shows a representation of commits and their related data. The image below shows the source control graph for the MCUXpresso SDK. Hovering over a commit will show the author, commit date, documentation messages, and the commit ID. Viewing Changes to source One of the main benefits of hosting the MCUXpresso SDK on GitHub is that enables better project management. Users now have access to the entire MCUXpresso SDK project history. Navigate to the Source Control Graph view and select any entry. Doing so will open the diff view highlighting the changes across the modified files in the commit. MCUXpresso for VS Code MCUXpresso SDK

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

ISF Sensor Data Speed Problems.docx Intelligent Sensing Framework

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

MCUXpresso SDK 2.12.1 RT Platform: UM11441 Getting Started with NXP-based Wireless Modules Wireless module combinations from Tables 2 and 3 are not updated with the latest SDK 2.12.1 in the user manual UM11441. Major updates in Table 2 and Table 3: u-blox modules are supported only on rt1060 Murata modules are only tested with i.MX RT1060 EVKB and i.MX RT1040 EVK platforms Modified Murata modules names Renamed i.MX RT685S EVK to IMXRT685-AUD-EVK Please refer to the attached PDF for updated information.

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.

MBDT for MPC57xx - Frequently Asked Questions General Installer and Setup  External mode External mode example wouldn't compile after update  Others MPC57xx MBD Toolbox not appears in Simulink Library Browser  Peripherals Apps Motor Control BMS Request for HSD/LSD/MSDI Communication Examples for MPC5775B BMS and VCU Reference Design 

StarCore DSP FAQs How can I distinguish between various MSC8154/MSC8156 devices? My configuration sets up the L2 unified cache/M2 memory to 256KB of M2 and 256 KB of L2 cache. Does this mean L2 cache is 8 ways of 32 KB each? Does an M3 ECC event trigger an interrupt? The L2 cache features 4 L2 software prefetch channels. Are there 4 software prefetch channels per core or is this the total number per device? Do I need an I2C serial EEPROM for loading of the Reset Configuration Word (RCW)? How does MSC8156 MAPLE-B TVPE support Viterbi and Turbo decoding? I want to use the Debug and Profiling Unit (DPU) in the MSC8156 to log information into the virtual trace buffer. I have set up the DPU registers for core 0. How do I set up the DPU for the other cores 1/2/3/4/5 since there is only one set of DPU registers? I only need to reset an individual core in the MSC8156. How can I do that? The MSC8156 Reference Manual shows the default DDR1 and DDR2 memory address spaces are 512 MB. How do I change the memory space to 1 GB? What is the maximum heat sink attachment force to avoid damaging the solder balls? What does the NO_INC bit indicate in the DMA buffer descriptor BD_ATTR field? When would you use this? If a MSC8156 DMA port A or B bus error happens, i.e., DMAERR[PAE] or DMAERR[PBE] bit is set, can I clear these bits and continue with the DMA operation? If a DMA BD size 0 error occurs, i.e., DMAERR[BDSZ] is set, to indicate that the buffer descriptor field BD_SIZE is cleared, how can I tell which DMA channel is associated with the error? How can I distinguish between various MSC8154/MSC8156 devices? You can read the System Part and Revision ID Register (SPRIDR) from address  to get the part ID and revision ID numbers. Device             SPRIDR[PARTID] MSC8154                0x8304 MSC8154EC           0x831C MSC8154E             0x830C MSC8156               0x8302 MSC8156EC           0x831A MSC8156E             0x830A Revision           SPRIDR[REVID] Rev. 1                       0x0000 Rev. 2                       0x0001 [ return to top ] My configuration sets up the L2 unified cache/M2 memory to 256KB of M2 and 256 KB of L2 cache.  Does this mean L2 cache is 8 ways of 32 KB each? No. The L2/M2 is 512 KB, arranged in 8 ways of 64 KB each way. In your configuration, the L2 cache becomes 4 ways. Each way is still 64 KB. [ return to top ] Does an M3 ECC event trigger an interrupt? M3 memory is ECC-protected so a single-bit error is detected and corrected, therefore an interrupt is not necessary. [ return to top ] The L2 cache features 4 L2 software prefetch channels.  Are there 4 software prefetch channels per core or is this the total number per device? The L2 cache is private for each core, therefore the 4 software prefetch channels are per core. Each core configures its own set of L2 software prefetch registers. Each core can only configure its own L2. The L2 software prefetch registers cannot be configured externally from the DSP subsystem. [ return to top ] Do I need an I2C serial EEPROM for loading of the Reset Configuration Word (RCW)? No, there are other options for loading of the RCW besides the I2C serial EEPROM. Multiplexed RCW loading option(RCW_SRC[0:2]=000) - all 64-bits of the RCW are loaded in four passes using the external pins RC[15:0]  using the /RCW_LSEL[0:3] pins as lane select signals. Reduced RCW loading option (RCW_SRC[0:2]=011) - some bits of the RCW are latched from external pins and some bits are loaded from default hard-coded values. [ return to top ] How does MSC8156 MAPLE-B TVPE support Viterbi and Turbo decoding? Turbo and Viterbi decoding are supported by MSC8156 MAPLE-B TVPE in same µcode. You can initialize the Maple with one TVPE standard, plus some Viterbi parameters. Then you can use different Buffer Descriptors for Turbo and Viterbi. Note that MAPLE-B doesn't support multiple Turbo standards with the same µcode because Maple µcode is standard specific and a µcode re-load is required to switch from one standard to another. So supporting a mixture of users of different standard in real time cannot be done with current MAPLE-B.  Turbo and Viterbi decoding are supported in same µcode, since Viterbi decoding parameters are fully configurable and are not standard related. [ return to top ] I want to use the Debug and Profiling Unit (DPU) in the MSC8156 to log information into the virtual trace buffer. I have set up the DPU registers for core 0. How do I set up the DPU for the other cores 1/2/3/4/5 since there is only one set of DPU registers? Each DSP subsystem includes a DPU. Each core can access its own DPU registers using the same physical addresses. [ return to top ] I only need to reset an individual core in the MSC8156. How can I do that? All cores are reset together. There is not a method to reset a particular core in the MSC8156. [ return to top ] The MSC8156 Reference Manual shows the default DDR1 and DDR2 memory address spaces are 512 MB. How do I change the memory space to 1 GB? The MSC8156 Reference Manual shows the DDR address spaces as follows: 0x40000000–0x5FFFFFFF      DDR1 Memory (default value)                                               512 M 0x60000000–0x7FFFFFFF      Reserved.  Used for DDR1 memory if configured for 1 GB.      512 M 0x80000000–0x9FFFFFFF      DDR2 Memory (default value)                                               512 M 0xA0000000–0xBFFFFFFF     Reserved. Used for DDR2 memory if configured for 1 GB.       512 M After reset, the default DDR1 and DDR2 memory space is 512 MB. To increase to 1GB DDR memory range, you need to configure the CLASS registers as follows: For DDR1 memory controller, change C0EAD5 from the reset value of 0x0005FFFF to 0x0007FFFF [ return to top ] What is the maximum heat sink attachment force to avoid damaging the solder balls? Detailed information about the Flip-Chip Plastic Ball Grid Array (FC-PBGA) package type devices (MSC8144 and MSC8156) can be found in this document FC-PBGAPRES.pdf The maximum heat sink attachment force is 4 Newtons (10 lb force). [ return to top ] What does the NO_INC bit indicate in the DMA buffer descriptor BD_ATTR field? When would you use this? You can set NO_INC if you want to transfer to or from the same address. The address will not be incremented. For example, if you want to fill memory with data from a single memory location, you will need to set NO_INC for the source. However, the destination will have the NO_INC bit cleared. [ return to top ] If a MSC8156 DMA port A or B bus error happens, i.e., DMAERR[PAE] or DMAERR[PBE] bit is set, can I clear these bits and continue with the DMA operation? A port error will freeze the DMA channel so clearing the error bit has no effect. In this case, the DMA channel needs to be reinitialized before it can be used again. [ return to top ] If a DMA BD size 0 error occurs, i.e., DMAERR[BDSZ] is set, to indicate that the buffer descriptor field BD_SIZE is cleared, how can I tell which DMA channel is associated with the error? The DMAERR register does not indicate which channel accessed the BD with size 0. However, you can check the DMACHCRx registers to determine which channel did not finish the transfer by checking if the active ACT bit is high. A channel that does not encounter the error will finish (ACT bit gets cleared). [ return to top ] .

视频 - 云开发教程 1/6：安装和配置适用于 MQX 的 iDigi 连接器 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 适用于 MQX 的 iDigi 连接器的视频教程 1/6：安装和配置适用于 MQX 的 iDigi 连接器（1/6） - iDigi 设备云 更多信息及免费下载请访问： http://www.freescale.com/webapp/sps/site/prod_summary.jsp? code=KINETIS_IDIGI_M2M

Power Architecture 的新服务包发布！（Windows）〜 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> QorIQ处理平台的优势已融入众多应用领域！例如，网络、移动无线基础设施、自动化功能、医疗应用等等！ 这样，您就可以更轻松地将高性能通信、基站和计算系统推向市场 先进的工具、多核、加速器、安全性等等。 一些服务包已经发布，以增强您在这项技术上的设计能力。其中第四个是与 Power Architecture Processors v10.1.2 一起介绍的。服务。 此次改进主要应用在以下设备中： P4040 DS  裸机支持 U-boot 调试 P4080 DS  裸机支持 U-boot 调试 P3041 DS 九头蛇  Linux 内核和应用程序调试 P3041 DS 超级九头蛇  Linux 内核和应用程序调试     Power Architecture Processors v10.1.2 新增并改进了更多功能 在发行说明中了解它们！ 立即下载Windows 版 Service Pack 4 ！   你更喜欢Linux 版本？ 概述

Video - Cloud Development Tutorial 5/6: Enabling Remote Firmware Update (K60) Tutorial 5 of 6 for the iDigi Connector for MQX: Enabling iDigi Remote Firmware Update (5 of 6) - iDigi Device Cloud More information and free download at http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=KINETIS_IDIGI_M2M

Developer’s Serial Bootloader. for M68HC08, HCS08, ColdFire and Kinetis MCUs by: Pavel Lajsner, Pavel Krenek, Petr Gargulak Freescale Czech System Center Roznov p.R., Czech Republic The developer's serial bootloader offers to user easiest possible way how to update existing firmware on most of Freescale microcontrollers in-circuit. In-circuit programming is not intended to replace any of debuging and developing tool but it serves only as simple option of embedded system reprograming via serial asynchronous port or USB. The developer’s serial bootloader supported microcotrollers includes 8-bit families HC08, HCS08 and 32-bit families ColdFire, Kinetis. New Kinetis families include support for K series and L series. This application note is for embedded-software developers interested in alternative reprogramming tools. Because of its ability to modify MCU memory in-circuit, the serial bootloader is a utility that may be useful in developing applications. The developer’s serial bootloader is a complementary utility for either demo purposes or applications originally developed using MMDS and requiring minor modifications to be done in-circuit. The serial bootloader offers a zero-cost solution to applications already equipped with a serial interface and SCI pins available on a connector. This document also describes other programming techniques: FLASH reprogramming using ROM routines Simple software SCI Software for USB (HC08JW, HCS08JM and MCF51JM MCUs) Use of the internal clock generator PLL clock programming EEPROM programming (AS/AZ HC08 families) CRC protection of serial protocol option NOTE: QUICK LINKS The Master applications user guides: Section 10, Master applications user guides. The description of Kinetis version of protocol including the changes in user application: Section 7, FC Protocol, Version 5, Kinetis. The quick start guide how to modify the user Kinetis application to be ready for AN2295 bootloader: Section 7.8, Quick guide: How to prepare the user Kinetis application for AN2295 bootloader. Full application note and  software attached. Freedom Development Platform Kinetis K Series MCUs Kinetis L Series MCUs Re: Developer’s Serial Bootloader. Hi, link is broken, can you fix it please? Re: Developer’s Serial Bootloader. Is there any support for the 9s12 parts?  It would seem to be a good fit. Bob Re: Developer’s Serial Bootloader. https://community.freescale.com/thread/38615?start=210&tstart=0 Re: Developer’s Serial Bootloader. Where I can find this bootloader for CW? I need implement it on KwikStick its running on K40X256VLQ. I have downloaded this version for IAR and can build it with iar but can't build debug version, so any help is good from you guys. When I try to build debug version with iar I get this error " Error[Li005]: no definition for "main" [program entry] Error[Lp014]: cannot fit "Section .text (bootloader.o #21)" (min size 0x5a0, alignment 0x4) into any of the ranges <[0x00000040-0x000003ff],  [0x00000410-0x000008ff]> Error while running Linker " I tried to edit project->options->debugger->runto __main but with no success. Re: Developer’s Serial Bootloader. Hi, Yes it is available for Kinetis K, L and M series. Re: Developer’s Serial Bootloader. Hi All, Is it available for Kinetis? Thanks. Re: Developer’s Serial Bootloader. Hello. Anyone know when it will be available the Serial Bootloader for Kinetis, for CodeWarrior 10.3? Thank you. Fernando. Re: Developer’s Serial Bootloader. CodeWarrior 10.4 is out. Any idea when the Serial Bootloader for Kinetis will be available? Thanks.. Joe Re: Developer’s Serial Bootloader. Actually I tried to enforce EWARM to jump to __main instead of main, but debugger report error as well. I forgot to mentioned in my previous post. I know supporting different compilers + mcu + boards + configurations are messy and difficult work. Re: Developer’s Serial Bootloader. Hi All, New version of the bootloader includes support for CodeWarrior 10.3 for all Kinetis families will be available in the next weeks. Pavel Krenek AN2295 developer Re: Developer’s Serial Bootloader. Hi, classic main function is not included in the bootloader source code, we used __main as you mentioned. This function has the same functionality. Re: Developer’s Serial Bootloader. It covers too many micros in one package. I doubt if you guys have enough time to test the code. Re: Developer’s Serial Bootloader. I use AN2295 for Kinetis KL25Z FRDM as bootloader. I can build it successfully, but its debugger reports following message: The stack plug-in failed to set a breakpoint on "main". The stack window will not be able to display stack contents. You can change this setting in the Tools>Options dialog box. Actually I can not find main(void), but I do find __main(void) in bootloader.c How can I fix it? Re: Developer’s Serial Bootloader. I heard freescale was suppose to release the software for the kinetis but I have not seen it. Still waiting. Re: Developer’s Serial Bootloader. Is there some gays to use this docment to do it sucessful Re: Developer’s Serial Bootloader. Same here. I am struggling to convert this over to CW 10.3 for the TWR-K20D50M using either CWC-compiler or the GNU-compiler. Has anyone succeeded with that yet? Re: Developer’s Serial Bootloader. I am struggling a little trying to convert this over to Codewarrior 10.2 and a K70. Has there been any work done on that yet? Or even a CW10.3 version? Re: Developer’s Serial Bootloader. It would be fantastic if a Codewarrior 10.x version were to be available. I am having a little difficulty figuring out the conversion. Linker files, etc. Thank you very much for posting this. P