P4080 USB固有のFAQ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 4080 の USB インターフェイスを使用しない場合、USBx_VDD_3P3 ピンと USBx_VDD_1P0 ピンを接続しないままにしておくことはできますか?P4040では、接続しないという注意で予約されています。それぞれ3.3Vと1.0Vに接続できますか? USB_VDD_1P0は、1Vまたはプラットフォーム電圧(SOCコアデジタル電源に基づく)に接続する必要があります。USB_VDD_3P3は浮いたままにすることができます。 USBを使用しない場合、USBx_IBIAS_REXTやUSBx_VDD_1P8_DECAPを放置しても安全ですか? USBをまったく使用しない場合は、次のUSB信号をフローティング状態に保ちます:USB1_IBIAS_REXT、USB2_IBIAS_REXT、USB1_VDD_1P8_DECAPおよびUSB2_VDD_1P8_DECAP、USB1_VDD_3P3、USB2_VDD_3P3。 QorIQ P4デバイス

P4080 USB Specific FAQs If I don’t use the USB interface in the 4080, can I leave USBx_VDD_3P3 and USBx_VDD_1P0 pins not connected? In P4040 they are reserve with note do not connect. Can they be connected to 3.3V and 1.0V respectively? USB_VDD_1P0 must be tied to 1V or the platform voltage (based on whatever the SOC core digital power supply is). USB_VDD_3P3 can be left floating. If I don’t use USB, is it safe to leave USBx_IBIAS_REXT and USBx_VDD_1P8_DECAP 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 and USB2_VDD_1P8_DECAP, USB1_VDD_3P3, USB2_VDD_3P3. QorIQ P4 Devices

Q&A: LVDS1_CLK Termination Question: LVDS in split mode (dual lvds) is used. In this configuration, only LVDS0_CLK is used. What is the suggestion for the LVDS1_CLK?  The HW user guide says that if this is unused, then to leave it floating.  Would we also suggest the same for this case or would termination be more appropriate?  Or is there some possible way to gate this clock?  (if so, it isn't obvious in the RM) Answer: According to the MX6 Developer's Guide, any unused LVDS pins should be left floating, so the LVDS1_CLK pair, in this case should be left floating. In order to minimize any potential EMC, the lands for those balls should not have any additional traces leading away. To add a bit more information, the customer ran some tests and found that the clock gate bits for the LVDS1 are essentially ignored in Dual mode.  The only way to disable it is if they are both disabled which is not helpful in this case.  It seems that the Dual mode setting overrides the CG. i.MX6_All

P2010/P2020 Clocking Specific FAQs P2010/P2020 H/W spec describes that Max SYSCLK frequency is 100MHz. Generically when user inputs 100MHz clock, actual clock speed become more faster. I think P2010/P2020 has enough margin for faster SYSCLK as long as I use up to 100MHz oscillator. Is my understanding correct? Yes, your understanding is correct. As long as you use 100MHz oscillator it should be fine. QorIQ P2 Devices

Setup Xorg 1.14 for i.MX6 LTIB does not support X11 acceleration, since the packages are too old. Ubuntu 11.10 prebuilt image part of i.MX6 BSP has Xorg version 1.10.4. Yocto 1.4 has Xorg version 1.11.4. This document is based on Yocto 1.4.1 yocto and Freescale BSP 3.5.7 Alpha release. Few simple steps to enable 1.14.0. 1. Let us consider your Yocto directory is  $(rootfs_builder) 2. Edit vi sources/meta-fsl-arm/conf/machine/include/imx-base.inc      PREFERRED_VERSION_xserver-xorg_mx6 = "2:1.14.0" 3.Edit vi sources/meta-fsl-bsp-release/imx/meta-fsl-arm/recipes-graphics/xorg-driver/xf86-video-imxfb-vivante_3.5.7-1.0.0.bb      SRC_URI = "${FSL_MIRROR}/xserver-xorg-video-imx-viv-${PV}.tar.gz \            file://Makefile-fix-cross-compile.patch \                    file://0001-add-compat.h.patch" 4. Copy the attached Makefile-fix-cross-compile.patch into sources/meta-fsl-bsp-release/imx/meta-fsl-arm/recipes-graphics/xorg-driver/xf86-video-imxfb-vivante/. 5. In the build directory, delete the tmp directory. Otherwise there will be build errors (I did not found easy way) 6. bitbake fsl-image-x11 7. Now the image is ready to flash. 8. Boot the board with the newly built image. 9. Check the Xorg version log in /var/log/Xorg.0.log. It will be 1.14.0. 10. Before executing any of the X11-EGL application, export VIV_DESKTOP=0 to the terminal. You can see the application running. There are some known issues related to performance in 3.5.7 Alpha release. Re: Setup Xorg 1.14 for i.MX6 I tried the GPU libraries from BSP 3.5.7 Alpha release against Xorg 13 (the rootfs is actually Ubuntu 13.04) with the 4.1.0 kernel. None of the sample in viv_sample/vdk run, they cause Xorg to hang. I can get glxgears/es2gears to run but only with a plain xserver running. glmark2/glmark2-es2 both cause Xorg to hang. If I switch back to the fb drivers, everything runs fine. If I switch back Xorg to 11.4, then everything runs (the viv samples now display in a tiled window) , however performance has been degraded. Seems like the vivante libraries aren't compatible with the built in DRI API in Xorg 13/14. Any plans to release new binaries? Re: Setup Xorg 1.14 for i.MX6 It works now. Re: Setup Xorg 1.14 for i.MX6 Hi Henry, Attached the correct patch(0001-add-compat.h.patch). Can you please try with this. Re: Setup Xorg 1.14 for i.MX6 Hi Prabhu, Some corrections in your description. 4. Copy the attached fix-swaps-and-compat-api.h.patch(after renaming it to 0001-add-compat.h.patch) into sources/meta-fsl-bsp-release/imx/meta-fsl-arm/recipes-graphics/xorg-driver/xf86-video-imxfb-vivante/. BTW, I encountered an error during patching as below. Applying patch 0001-add-compat.h.patch patching file src/vivante_extension/vivante_ext.c Hunk #1 FAILED at 59. 1 out of 1 hunk FAILED -- rejects in file src/vivante_extension/vivante_ext.c patching file src/vivante_fbdev/vivante.h patching file src/vivante_fbdev/vivante_dri.c patching file src/vivante_fbdev/vivante_dri.h patching file src/vivante_fbdev/vivante_fbdev_driver.c patching file src/vivante_util/compat-api.h patching file src/vivante_util/vivante_common.h Patch 0001-add-compat.h.patch does not apply (enforce with -f) $<50>ERROR: Function failed: patch_do_patch $<50>ERROR: Logfile of failure stored in: /home/share/MX_Product/MX6DQ/BSP/yocto/L3.5.7_1.0.0_20130701/fsl-community-bsp/build-x11/tmp/work/imx6qsabresd-poky-linux-gnueabi/xf86-video-imxfb-vivante/4_3.5.7-1.0.0-r21.0/temp/log.do_patch.4879 $<50>ERROR: Task 4980 (/home/share/MX_Product/MX6DQ/BSP/yocto/L3.5.7_1.0.0_20130701/fsl-community-bsp/sources/meta-fsl-bsp-release/imx/meta-fsl-arm/recipes-graphics/xorg-driver/xf86-video-imxfb-vivante_3.5.7-1.0.0.bb, do_patch) failed with exit code '1' $<50>NOTE: Tasks Summary: Attempted 6636 tasks of which 6631 didn't need to be rerun and 1 failed. Waiting for 0 running tasks to finish: I fixed the patch file manually, but still encountered some errors during building. | /home/share/MX_Product/MX6DQ/BSP/yocto/L3.5.7_1.0.0_20130701/fsl-community-bsp/build-x11/tmp/sysroots/imx6qsabresd/usr/include/xorg/exa.h:780:24: note: expected 'PixmapPtr' but argument is of type 'DrawablePtr' | vivante_extension/vivante_ext.c: In function 'SProcXF86VIVHelpDispatch': | vivante_extension/vivante_ext.c:484:11: error: 'VIVHelpErrorBase' undeclared (first use in this function) | vivante_extension/vivante_ext.c:484:11: note: each undeclared identifier is reported only once for each function it appears in | vivante_extension/vivante_ext.c: In function 'XFree86VIVHELPExtensionInit': | vivante_extension/vivante_ext.c:509:2: error: 'VIVHelpReqCode' undeclared (first use in this function) | vivante_extension/vivante_ext.c:510:2: error: 'VIVHelpErrorBase' undeclared (first use in this function) | make: *** [vivante_extension/vivante_ext.o] Error 1 | make: Leaving directory `/home/share/MX_Product/MX6DQ/BSP/yocto/L3.5.7_1.0.0_20130701/fsl-community-bsp/build-x11/tmp/work/imx6qsabresd-poky-linux-gnueabi/xf86-video-imxfb-vivante/4_3.5.7-1.0.0-r21.0/xserver-xorg-video-imx-viv-3.5.7-1.0.0/EXA/src' | ERROR: make failed Finally I downloaded xserver-xorg-video-imx-viv-3.5.7-1.0.0.tar.gz package again, but it couldn't fix the issue. Could you double check if your base code is different from released one? Regards, Henry.

Spectrum analyzer project Hi,     I will present to you my first personal initiated project named Spectrum analyzer. This spectrum is based on sampling signal and calculating his spectrum using FFT algorithm. Attached here presentation, documentation (french), electrical scheme of amplification circuit and source code of both programs (Computer and PXS20)   Picture of the spectrum analyzer with TWR-PXS20, TWR-SER and TWR-PROTO :   Picture of amplification circuit :   Picture of signal collected by the ADC :   And here we have the spectrum :   Thank you, and I hope you like it Student Project Re: Spectrum analyzer project Nice.  Thanks for posting!

Beijing University of Science and Technology 2013 Global Freescale Cup Champion. Video Link : 1589 Car Specs: Custom K60 Control Board

P1010/P1014 USB Specific FAQs Do you have any additional info on the USB VBUSCLMP pin. The manual says that it is the divided down Vbus. What is the divisor? The P1010 RDB schematic has a diode protecting this pin. What are the critical specifications for the diode? The diode was supposed to be used for in OTG mode. Since the USB phy in P1010 doesn't support OTG, you may choose to ignore it. The VBUS operates at 5V. But VBUSCLMP operates at 3.3V. So you should implement a potential divider to bring down 5V to 3.3V as shown in RDB. In case using on-chip USB PHY, low-speed mode is not supported at all? Or it can be supported if operating in "Host" mode? Low-speed mode (LS) is supported in Host mode but not in device mode. Can you tell me whether USB internal PHY on P1010 supports UTMI+ Level3 or not? UTMI+ Level3 is supported in P1010 Please advise how power supply to USB port should be controlled when using on-chip USB PHY. Without controlling through IFC bus (via CPLD) like P1010RDB schematic, is there other way to control for it? DRVVBUS should be used to control the external VBUS supply. By mistake this signal has been shown as a ULPI signal in P1010 RM because of which P1010RDB designer have not used it for externals VBUS control. About USBVDD1_8(J21,K21), on HWspec Table1 Notes 20 says that "20.This pin should be connected to Vss through 1μF.No need to supply power to this pin. 1.8V output may be observed on this pin during normal working conditions." Is it okay to tie J21 and K21 pins together and connect to Vss via a "single" 1uF capacitor? Or 1uF cap is required for each pin respectively? It should be okay to combine both the pins and connecting to Vss via single 1uF capacitor. If the whole USB (controller and PHY) is not used, user still needs to supply USBVDD3_3 power, Right? What is the reason?  Yes it is required to provide USBVDD3_3 even if USB controller and PHY are not used at all. This is a requirement from design to keep the logic in a sane state. If the whole USB is not used, does user need to follow power sequencing of USBVDD3_3, assuming USBVDD3_3 supply needs to be present? Following the sequence between USBVDD3_3 and other 3.3V supplies is not required. It is must to provide supply to USBVDD3_3 even if the USB PHY is not used. A suggestion, if USB PHY is not used customer can supply this pin with the same regulator which would be used to supply other 3.3V supply pins of SoC. Make sure that the ramp rate constraint is still followed for USBVDD3_3. QorIQ P1 Devices Re: P1010/P1014 USB Specific FAQs Hi, I have a further question. If the whole USB is not used, I have to provide USBVDD3_3 and USBVDD1_0 but not USBVDD1_8. Is this right? Do I have to feedback the VBUS to the controller or to which level I have to lay this pin? Thanks a lot!

7816-4 APDUの達成方法 MIFARE DESFire EV1 は、ISO/IEC に準拠した APDU メッセージ構造をサポートします 7816-4 は、ネイティブ MIFARE DESFire EV1 APDU 形式のオプションのラッピングと さらに、実用的な観点から7816-4コマンドを実装しました。

What is Processor Expert ? Processor Expert Software is a development system to create, configure, optimize, migrate, and deliver software components that generate source code for Freescale silicon. The main features of PEx are: Extensive and comprehensive knowledgebase for all supported silicon encapsulating all pins, registers, etc. Silicon resource conflicts flagged at design time, allowing early correction Simple creation of peripheral drivers without reading silicon documentation Easy integration of an RTOS with peripheral drivers The generated drivers have a cross-platform API that allows easy migration among supported processors. The user builds an application or library using a wide range of basic building block called Embedded components covering all common tasks (for example, serial communication, timers, ADC, DAC, digital I/O etc.). These components can be configured in graphical user interface and Processor Expert generate a C source code of initialization and runtime control drivers of the processor and its peripherals. Processor Expert is available: Integrated with CodeWarrior for Microcontrollers As a standalone package called Microcontroller Driver Suite. It supports Kinetis and ColdFire+ microcontrollers. It does not include a compiler or linker and can be used with other non-CodeWarrior IDEs. Integrated with Kinetis Design Stuido (KDS) For more details, refer to the Freescale website http://www.freescale.com/processorexpert.

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 组件

i.MX Yocto Project: Freescale Yocto Project Tutorial A tutorial on 'Freescale Yocto Project'. Source code is located here NOTE: When doing 'repo init -u .... -b ', make sure you are using the latest stable branch (dora is the latest when writing this note) A tutorial on 'Freescale Yocto Project'. Source code is located here NOTE: When doing 'repo init -u .... -b ', make sure you are using the latest stable branch (dora is the latest when writing this note) Yocto Project Re: i.MX Yocto Project: Freescale Yocto Project Tutorial Adding few notes regarding "Building the Kernel Manually" after review and test on my platform (DECEMBER 2015/MCIMX6UL-EVK) I am working with the i.MX6 UL EVK board (MCIMX6UL-EVK), my local BRANCH is imx_3.14.38_6ul_ga. The defconfig used for my setup is: imx_v7_defconfig (the configuration is stored in the kernel source code under arch/arm/configs). To be able to run make menuconfig properly on my Ubuntu host machine (Linux 3.13.x), I had to "apt-get install" the package called:libcurses5-dev. The SD card requires a zImage, so I just called "make zImage" to get the new image built. Re: i.MX Yocto Project: Freescale Yocto Project Tutorial Hello, The document is great!  However, I have some questions, as follows: On page 1, under "Build's local configuration file..." the first line says "MACHINE ??= 'wandboard-dual'.  However, on page 3 at the bottom, the document says "Machine configuration file: meta-fsl-arm/conf/imx6qsabresd.conf" I am using a wandboard-quad.  Should the page 1 statement be MACHINE ??='wandboard-quad' and the page 3 line be Machine configuration file: meta-fsl-arm-extra/conf/machine/wandboard-quad.conf"? On page 4, the document refers to "KERNEL_DEVICE_TREE = "${S}/arch/arm/boot/dts/imx6q-sabresd.dts".  Should this be changed to reflect the wandboard-quad? UBOOT_MACHINE = "mx6qsabresd_config".  Should this be changed to reflect the wandboard-quad? Where would I tell the Yocto system that the machine configuration file is "meta-fsl-arm-extra/conf/machine/wandboard-quad.conf"? I am used to the ./configure, make linux, make linux_install method of building an embedded kernel and similarly for applications.  I am finding the whole recipes thing quite confusing although I can see its merits.  Are there any other clear, current, step-by-step guides to help me? Thanks, and Best regards, Peter Re: i.MX Yocto Project: Freescale Yocto Project Tutorial Good day Leo, Just a heads up but the curl path you have in your document (i.e. https://dl-ssl.google.com/dl/googlesource/git-repo) is no longer valid...  I just tried today and I get an Error 404 in the resulting "repo" file. Secondly, I tried to find repo and when I googled it I found repo 1.19...however this version when doing the repo init... generates the following "could not verify the tag 'v1.12.7'".  When I investigated this error I found others had this issue and they ended up getting repo from "http://commondatastorage.googleapis.com/git-repo-downloads/repo".  So the resulting command I used was: "curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo" and all is fine now. Cheers, Sam Re: i.MX Yocto Project: Freescale Yocto Project Tutorial So I am assuming your MACHINE=imx6qsabresd and your are booting it the corresponding board. Seems that the device tree file is not being found. Which branches are you using? dora? If problem remains, please post the question into the meta-freescale list. Leo Re: i.MX Yocto Project: Freescale Yocto Project Tutorial Hi Leanardo, Now I am able to build the fsl-image-gui. But it is hanging while booting. Bootlog  is In:    serial Out:   serial Err:   serial Net:   FEC [PRIME] Warning: FEC using MAC address from net device Hit any key to stop autoboot:  0 mmc1 is current device reading boot.scr ** Unable to read file boot.scr ** reading uImage 3872628 bytes read in 342 ms (10.8 MiB/s) Booting from mmc ... reading imx6q-sabresd.dtb ** Unable to read file imx6q-sabresd.dtb ** ## Booting kernel from Legacy Image at 12000000 ...    Image Name:   Linux-3.0.35-1.1.0+yocto+g21304e    Image Type:   ARM Linux Kernel Image (uncompressed)    Data Size:    3872564 Bytes = 3.7 MiB    Load Address: 10008000    Entry Point:  10008000    Verifying Checksum ... OK After that boot is not going further, What might be the issue? Re: i.MX Yocto Project: Freescale Yocto Project Tutorial Hi Krishna Unfortunately fetch issues are common. It may be the case that either the site is down temporally so you may try later. One way to overcome this problem is find the tarball somewhere and place it on the 'downloads' folder. I know, it is ugly but you do not stuck. Leo Re: i.MX Yocto Project: Freescale Yocto Project Tutorial Hi Leonardo, I am trying to install Yocto on i.Mx6 and I am referring the above document But I am getting following error when I give bitbake fsl-image-gui | ERROR: Function failed: Unpack failure for URL: 'http://zlib.net/pigz/pigz-2.3.tar.gz'. gzip: stdin: invalid compressed data--crc error | tar: Child returned status 1 | tar: Error is not recoverable: exiting now I checked that link manually and that link is no more exists.only pigz-2.3.1.tar.gz is available. How to solve this problem and make bitbake to fetch latest pigz? Thanks in advance Re: i.MX Yocto Project: Freescale Yocto Project Tutorial New stable branch has been pushed called 'dora'. So replace 'dylan' to 'dora' in all slides to get latest stable commits. Re: i.MX Yocto Project: Freescale Yocto Project Tutorial Hi Leonardo I do not understand what do you mean with correct branch. Be careful: here is a deep newbie, me. The cloned linux root Makefile  has: VERSION = 3  PATCHLEVEL = 2 SUBLEVEL = 0 EXTRAVERSION = NAME = Saber-toothed Squirrel The yocto dylan build\tmp\work\imx6qsabrelite-poky-linux-gnueabi\linux-boundary\3.0.35-r0\git Makefile has: VERSION = 3 PATCHLEVEL = 0 SUBLEVEL = 35 EXTRAVERSION = NAME = Sneaky Weasel So I suppose, yoctolinux is 3.0.35 and clonedlinux is 3.2.0. The folder drivers/video/mcx is in 3.0.35 but it is not in 3.2.0.  Is it supressed? or is it not implemented yet? Thank you Re: i.MX Yocto Project: Freescale Yocto Project Tutorial On your cloned Linux kernel, did you move to the correct branch? You can compile either in the Yocto or your clone kernel folder, both are clones from the same source. In the other hand, the Yocto kernel may have some patches on top (look at the recipe), and the one you clone don't. Leo Re: i.MX Yocto Project: Freescale Yocto Project Tutorial Hi Leonardo We are having problems with HDMI resolution on a Sabrelite board. Looking for information about the  kernel graphic driver I came to your tutorial. The chapter about "Building the kernel manually" take my attention. I clonegited the linux and then looked for the file mxc_hdmi.c (I saw a reference on another page) ... and I did not find it. Then i looked for it at our yoctodylan directory (I already did not remenber why I clonedgited before I look here) and I found it at: build/tmp/work/imx6qsabrelite-poky-linux-gnueabi/linux-boundary/3.0.35-r0/git/drivers/video My first question is: If build/tmp/work/imx6qsabrelite-poky-linux-gnueabi/linux-boundary/3.0.35-r0/git seems to be the complete linux Yocto is using, why is necessary to download another copy? And the second: Why are the linux different? Thanks and best regards Re: i.MX Yocto Project: Freescale Yocto Project Tutorial Hi Thomas, did you run the setup-environment script? After its executing, the prompt is now under the build folder, and in that folder the correct layers paths are on conf/bblayers.conf. Make sure the setup script is running fine and the bblayers.conf has correct paths. Leo Re: i.MX Yocto Project: Freescale Yocto Project Tutorial I've followed the guide, but when running bitbake it seems it picks the wrong path... that is it ommits ../fsl-community-bsp/.. from the path and so it fails because it doesn't find layer.conf Ideas..? Re: i.MX Yocto Project: Freescale Yocto Project Tutorial Thanks. Re: i.MX Yocto Project: Freescale Yocto Project Tutorial Oh yes! I will correct it soon. The source code for this pdf is found on the github link. For your problem, please add 'dylan', resulting in: $ repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b dylan Leo Re: i.MX Yocto Project: Freescale Yocto Project Tutorial Is this PDF file cut off from the right side?  I am getting an error: $ repo init -u https://github.com/Freescale/fsl-community-bsp-platform -b Usage: repo init -u url [options] repo: error: -b option requires an argument

DIY: Using the FRDM-KL25Z as USB Keyboard Hello Community fellows! This time I would like to thank BlackNight for giving us great material to work on. There have been several posts inquiring the uses of USB stack and Processor Expert. The examples he has worked on and now shares with all of us, include this and many more useful concepts that you'll find interesting with the use of boards. For this issue he turns his FRDM-KL25Z into a generic USB keyboard device. With a simple button press he is able to send any keyboard actions to his laptop, making such as ‘print screen’ a single button press...isn't that amazing? :smileygrin: Well, I'll say no more, you better check it out yourself!  MCU on Eclipse by Erich Styger

Adeneo Embeddedは、i.MX6プラットフォーム用のWindows Embedded Compact 7 BSPにPCIeのサポートを追加 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Adeneo Embeddedは、PCIeのサポートを追加することで、i.MX6プラットフォーム用のすでに豊富な機能を持つWindows Embedded Compact 7(WEC7)BSPを強化します。PCIeのサポートにより、お客様はさまざまなPCIベースの周辺機器を高性能i.MX6プラットフォームに接続できるようになりました。ビデオで示されている例では、PCIeベースのネットワークカードがi.MX6 SABRE liteボードで動作しているのを確認できます。AdeneoのPCIバスおよびコントローラードライバーの実装は、製品品質です。 (マイビデオで視聴)

フリースケール・カップ・イーストチャイナ2013チャレンジ・ビデオ2 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> フリースケール・カップ・イーストチャイナ2013チャレンジ・ビデオ2 中国東部での正式な競技が終了した後、私たちは挑戦を与え、チームに>30の角度で丘を試すように依頼しました。 (マイビデオで視聴) フリースケール・カップの内容 イメージギャラリー 日時:フリースケールカップ東中国2013チャレンジビデオ2 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 涼しい。これは興味深い挑戦です。アイデアがくれる!! 共有してくれてありがとう! 日時:フリースケールカップ東中国2013チャレンジビデオ2 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 素晴らしい試み!!興味深い挑戦

FreeMaster_03.07.2013.PE更新済 <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コンポーネントのアップデート

Setting up Secure Boot on LS1028ARDB Platform Basic Concept of Secure boot on LS1028A Platform Build secure boot ATF image Generate secure boot CSF headers for Linux tiny itb image Deploy secure boot images on the target board Blow OTPMK fuse in u-boot and through CodeWarrior CCS Write SRK hash keys to the mirror registers through CCS Secure boot Trouble Shooting

複数の Python バージョンがインストールされている問題 VS Code の MCUXpresso 拡張機能は Python を活用します。特にWindowsでは、Pythonの複数のバージョンがインストールされている場合、ツールに問題が発生することがあります。MCUXpresso インストーラーは 、Python 仮想環境を使用します。ただし、Pythonモジュールをインストールするときに、他のPythonバージョンがすでにインストールされている場合は、問題が発生する可能性があります。 VS Code の MCUXpresso インストーラーまたは MCUXpresso 拡張機能に、Python モジュールの欠落によるエラーが表示される場合は、これを管理するためのヒントをいくつか紹介します。1 つのオプションは、他の Python バージョンが不要な場合は削除することです。コマンド プロンプトから、次のコマンドを使用して PATH 環境変数にあるさまざまな Python バージョンを見つけることができます。 ここで、Pythonは Python モジュールを特定の Python バージョンに手動でインストールすることもできます ( 「VS Code で使用される Python 仮想環境」を参照してください)。 別の可能なオプションは、PATH 環境変数を編集し、他の Python バージョンへのパスを削除することです。

MCUXpresso SDK: CMake Usage - Build Options Exploring CLI Build Options In a previous article, we demonstrated how to build a simple project using the CLI. However, we can easily build more complex projects using west build options. We can specify a specific toolchain, compiler, core, etc. To view the complete list of build options run the command: west build -h Dual Core Device Example For single core devices there is no need to specify a core ID. However, this must be done when working with a dual core device. For example, to build Hello_World for the FRDM MCXN947, the following command needs to be run: west build -b frdmmcxn947 example/demo_apps/hello_world -Dcore_id=cm33_core0 Specifying a Toolchain The MCUXpresso SDK supports several toolchains. To take the example above and build for IAR, we simply specify the IAR toolchain with a build option as follows: west build -b frdmmcxn947 example/demo_apps/hello_world -Dcore_id=cm33_core0 --toolchain iar Specifying a Different Build Directory As you can see the CLI is quick and easy to use for building projects. So far, we have covered some of the major build options to consider. What happens when we want to evaluate with different builds simultaneously? Well, we can specify different build directories within our workspace. To designate a different build directory for the project above, simply run: west build -b frdmmcxn947 examples/demo_apps/hello_world -Dcore_id=cm33_core0 --toolchain iar -d C:\temp-sdk\mcuxsdk\custom_build *Note the path shown has been personalized. The path for your system will vary. MCUXpresso for VS Code

PN53x with i.MX93 Linux (NFC) Hello everyone, this post is intended to add support to one of the most popular NFC chips on the market (PN532).  On this example I will use the I.MX93 EVK as reference board and focused in I2C communication for the PN532 Chip.  Details:   I.MX93 EVK  PN532 Module (I2C, SPI, UART)  BSP Linux 6.6.36_2.1.0 (Yocto)  STEP 1 (IMAGE COMPILATION).    At first, we need to compile our image for our board (in my case I.MX93 EVK) to add the NFC layer (Details on Yocto User's Guide😞😞 $ mkdir yocto-bsp $cd yocto-bsp $ repo init -u https://github.com/nxp-imx/imx-manifest -b imx-linux-scarthgap -m imx-6.6.36-2.1.0.xml $ repo sync $DISTRO=fsl-imx-wayland MACHINE=imx93evk source imx-setup-release.sh -b imx93evk-build Then, add the support for NFC in our local.conf file:  $ nano conf/local.conf We will add the below lines: CORE_IMAGE_EXTRA_INSTALL += "libnfc" CORE_IMAGE_EXTRA_INSTALL += "libnfc-dev" Then, we can compile the image with:  $ bitbake imx-image-full NOTE:  libnfc is a complete coverage of low-level PN53x chipset commands written in pure and plain C for portability and speed.  libnfc-dev are the development files and headers to use in our low-level applications.  By default, the NXP BSP support the NFC pn532 driver with a tool called nfctool, but this one is very limited compared with the libnfc.  STEP 2 (DEVICE TREE MODIFICATION).  We need to add the below lines to the Device tree:  &lpi2c5 { #address-cells = <1>; #size-cells = <0>; clock-frequency = <400000>; pinctrl-names = "default", "sleep"; pinctrl-0 = <&pinctrl_lpi2c5>; pinctrl-1 = <&pinctrl_lpi2c5>; status = "okay"; nfc@24 { compatible = "nxp,nxpnfc"; //we can set the "nxp,pn533" driver but it will just work for the nfctool mentioned before reg = <0x24>; clock-frequency = <400000>; interrupt-parent = <&gpio2>; interrupts = <18 IRQ_TYPE_EDGE_FALLING>; }; };  And to the iomux section(same in device tree):  pinctrl_lpi2c5: lpi2c5grp { fsl,pins = < MX93_PAD_GPIO_IO22__LPI2C5_SDA 0x40000b9e MX93_PAD_GPIO_IO23__LPI2C5_SCL 0x40000b9e MX93_PAD_GPIO_IO18__GPIO2_IO18 0x31e >; }; STEP 3 (Connection with PN532 MODULE).   For this example, we must connect the Module with the I.MX93 RP Header as follows:  I.MX93 SIDE  PN532 SIDE  GND  GND  VCC  VCC  GPIO_IO22  SDA  GPIO_IO23  SCL  GPIO_IO18  IRQ  STEP 4 (BOOT BOARD AND CREATE libnfc.conf FILE).  Once when we have booted our board and selected our modified Device Tree, we should see our i2c-4 under /dev of our Linux OS: root@imx93evk:~# ls /dev | grep i2c i2c-0 i2c-1 i2c-2 i2c-4 And see our specific device (0x24) with the i2cdetect tool:   root@imx93evk:~# i2cdetect -y 4 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- 24 -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- Now, we need to create a file called libnfc.conf under /etc/nfc/ (You can create that directory if does not exist).  This file must contain information about how the libnfc layer will communicate with the i2c device:  # Allow device auto-detection (default: true) # Note: if this auto-detection is disabled, user has to set manually a device # configuration using file or environment variable allow_autoscan = false # Allow intrusive auto-detection (default: false) # Warning: intrusive auto-detection can seriously disturb other devices # This option is not recommended, user should prefer to add manually his device. allow_intrusive_scan = true # Set log level (default: error) # Valid log levels are (in order of verbosity): 0 (none), 1 (error), 2 (info), 3 (debug) # Note: if you compiled with --enable-debug option, the default log level is "debug" log_level = 2 # Manually set default device (no default) # To set a default device, you must set both name and connstring for your device # Note: if autoscan is enabled, default device will be the first device available in device list. #device.name = "_PN532_SPI" #device.connstring = "pn532_spi:/dev/spidev0.0:500000" device.name = "_PN532_I2c" device.connstring = "pn532_i2c:/dev/i2c-4" As you can see, the most important line to modify is the device.connstring, that is the charged of interaction and connection between the PN53x Module and the libnfc layer. In my case is pn532_i2c:/dev/i2c-4.  Now we can use the NFC module:  root@imx93evk:~# nfc-list nfc-list uses libnfc 1.8.0 NFC device: _PN532_I2c opened root@imx93evk:~# And read UID of TAGs:  root@imx93evk:~# nfc-poll nfc-poll uses libnfc 1.8.0 NFC reader: _PN532_I2c opened NFC device will poll during 36000 ms (20 pollings of 300 ms for 6 modulations) ISO/IEC 14443A (106 kbps) target: ATQA (SENS_RES): 00 44 UID (NFCID1): 04 17 b5 d2 a2 11 90 SAK (SEL_RES): 00 Waiting for card removing...nfc_initiator_target_is_present: Target Released done. root@imx93evk:~# Also, attached is a little application using the NFC headers installed with libnfc-dev. Tha application will do a poll with a 10 seconds time out. If Tag is not detected in 10 seconds, the app will close. If a tag is detected before the timeout, the app will print the UID of the NFC TAG: OUTPUT of timeout: root@imx93evk:~# ./nfc-app NFC reader: _PN532_I2c opened Waiting for an NFC tag (timeout: 10 seconds)... No NFC tag detected within the timeout period. root@imx93evk:~# OUTPUT when tag is detected: root@imx93evk:~# ./nfc-app NFC reader: _PN532_I2c opened Waiting for an NFC tag (timeout: 10 seconds)... Tag detected - UID: 04:16:BC:D2:A2:11:90 root@imx93evk:~# To compile the app just copy the attached nfc-app.c file to the i.MX93 EVK and compile using this command: root@imx93evk:~# gcc nfc-app.c -o nfc-app -lnfc I hope this thread can be helpful! Best regards, Salas.