Dear All: Customer has encountered eMMC boot failure issue in their i.MX8X platform, finally we confirmed this issue related to external pull-up resistors on DAT0~7 and CMD pins to comply with eMMC SPEC. Please refer to attached "Case Study-i.MX8X boards eMMC boot failure issue.pdf". Thanks.

本文说明在STR Resume后，如何解决M 核与A核的GPIO状态冲突的问题，并简单剖 析了Linux GPIO驱动。 目录 1 背景说明与参考资料 .................................................. 2 1.1 背景说明 ................................................................. 2 1.2 参考资料 ................................................................. 2 2 S32G linux GPIO驱动说明 ......................................... 3 2.1 SIUL2 GPO功能说明 .............................................. 3 2.2 Linux GPIO驱动DTS .............................................. 4 2.3 Linux GPIO驱动初始化 ........................................... 6 3 Rework办法 ............................................................... 7 3.1 SIUL2 GPO驱动PM函数 ........................................ 7 3.2 Rework方法 ............................................................ 9 4 测试办法 .................................................................. 10

Chinese version   S32G的partition off流程要求核稳定的进 入到WFI状态，本文说明如何修改Linux内核， 在A53 Linux关机或kernel panic时，如何让所 有A53 Core进入WFI。 目录 1 背景说明与参考资料 .................................................. 2 1.1 背景说明 ................................................................. 2 1.2 参考资料 ................................................................. 5 1.3 测试工具 ................................................................. 6 2 Panic ......................................................................... 7 2.1 Panic代码流程分析 ................................................. 7 2.2 BSP30修改说明(Non-ATF) ................................... 10 2.3 BSP36修改说明(ATF) .......................................... 15 3 Poweoff ................................................................... 17 3.1 Poweroff代码流程分析 ......................................... 17 3.2 BSP30修改说明(Non-ATF) ................................... 19 3.3 BSP36修改说明(ATF) .......................................... 20 4 Reboot情况说明 ....................................................... 20 5 STR情况说明 ........................................................... 21   Contents 1    Background and Reference. 2 1.1  Background. 2 1.2  Reference materials. 5 1.3  Test Tools. 6 2    Panic. 7 2.1  Panic code flow analysis. 7 2.2  BSP30 Modification (Non-ATF) 10 2.3  BSP36 Modification (ATF) 16 3    Poweoff 18 3.1  Poweroff code analysis. 18 3.2  BSP30 Modification (Non-ATF) 20 3.3  BSP36 Modification (ATF) 21 4    Reboot Description. 21 5    STR Description. 21

由于NXP之前使用的git服务器codeaurora已经永久性关闭，本文说明针对S32G如何迁移到github服务器的方法。 目录 1    服务器迁移情况说明... 2 2    参考文档和工具... 4 3    Yocto迁移说明... 4 3.1  从头开始新建Yocto工程说明... 4 3.2  对已有Yocto工程的迁移说明... 6 3.3  Migrate.sh的帮助... 7 4    独立编译迁移说明... 10 4.1  PFE独立编译... 11 4.2  IPCF独立编译... 13

This doc explain the S32G STR feature details and how to modify it to integrate with M kernel STBY demo, to achieve the fast boot. chinese version: 本文说明S32G A53核STR详细情况及定 制，定制部分说明如何与M7 standby demo结 合，来实现整个产品的快速启动。 请注意本文为培训和辅助文档，本文不是 官方文档的替代，请一切以官方文档为准。 目录 1 参考资料说明 ............................................................. 2 2 Demo创建运行过程 ................................................... 2 3 Linux STR流程 ........................................................... 2 4 ATF Suspend流程 ..................................................... 5 4.1 Suspend流程 .......................................................... 5 4.2 Full boot resume流程 ............................................. 7 5 定制修改 .................................................................... 9 5.1 ATF中实现主核切换为M7 ....................................... 9 5.2 ATF中去掉PMIC与I2C4 ....................................... 11 5.3 ATF中去掉wkpu驱动 ............................................ 17 5.4 Uboot中去掉PMIC与I2C4 ..................................... 18 5.5 Kernel中去掉I2C4 ................................................ 19 6 发布 ......................................................................... 20   This article explains the details and customization of S32G A53 core STR. The customization part explains how to combine with M7 standby demo to realize the quick start of the whole product. Please note that this article is a training and auxiliary document. This article is not a substitute for the official document. Please refer to the official document. Contents 1    Reference materials. 2 2    STR Demo. 2 3    Linux STR call flow.. 2 4    ATF Suspend call flow.. 5 4.1  Suspend flow.. 5 4.2  Full boot resume flow.. 7 5    Customization. 9 5.1  The STR main core is switched to M7 in ATF. 9 5.2  ATF remove PMIC and I2C4. 11 5.3  ATF remove wkpu driver 17 5.4  Uboot remove PMIC and I2C4. 18 5.5  Kernel remove I2C4. 19 6    Release. 20

Memtool is a useful debug tool which can read/write some i.MX register. It is default supported in Linux while not supported in Android. This article describse how to integrate memtool into i.MX8MM Android 12 platform, which is also similar in other i.MX new android platform.  

i.MX RT1170 crossover MCUs are part of the Edge Verse™ platform and are setting speed records at 1 GHz. This ground-breaking family combines superior computing power and multiple media capabilities with ease-of-use and real-time functionality. For reducing the overall system cost, RT117x didn't have embeded flash, need external Flash as program storage and XIP place, NXP and third party like IAR, KEIL and Segger all provide mature tool to make Nor Flash‘s programing with their own flashloader, can fulfillment most customer’s application requirement, but still some users need to customize the flash programing algorithm due to programing speed optimization and difference of the nor Flash from different vendor and, such as SFDP support, QE bit's position, default sector size, DDR/OPI/QPI feature, default 3 Bytes/4 Bytes mode and also operating sequence, but the default Flashloader is based on the ROM API, it's hard to debug and customize as there is no source code. This reference demo will use source code Flash operation API instead of ROM API. In addition, it also add two new useful feature, first one is current Flashloader framework can't support some nor flash which need pre-configuration, such as Cypress's S25HL01GT, its sector size is not unified, need to config additionally. This reference demo give some function interface to implement it with 3 bytes/4bytes command mode and DDR/SDR mode, it also improve the original framework by adding read-erase-write demonstration code, which can help user to verify their customized Flashloader without need to copy to IDE every time, improve the efficiency greatly. Second advantage is it can support download flow‘s log generation, by default there is no log info in overall download flow, hard to locate which step(get configure/init/erase/program/verify) the failure occur, this demo code add log function to record every detailed download step, by which users can optimize their download speed, it's helpful for mass production. Developers can also debug and customize depend on their own specific requirement and different nor Flash.

EEPROM selection guide for serial RCON boot. On S32G reference manual, we only ask customer to make sure I2C address of EEPROM is 0xA0, no others requirement. Actually, S32G only supports EEPROM with one 8-bit address byte. For high capacity EEPROM such as AT24C64D@8K bytes, which need two 8-bit word address bytes. Can’t be supported by S32G ROM.   AT24C64D.pdf         AT24C01 has been validated on S32G EVK board, which need one word address byte AT24C01.pdf   Thanks, Lambert

This document introduce how to do LPDDR4 DQ Swapping in S32G platform.

The label printer requires some means of regulating the flow of data to and from the system to which they are attached. The suspension and resumption of data flow is necessary in a variety of circumstances. The attached PPT introduces a simple and effective flow control method running upon lwIP stack.  

目录 1 S32G Linux文档说明 .................................................. 3 2 创建S32G RDB2 Linux板级开发包编译环境 .............. 4 2.1 创建yocto编译环境: ................................................. 4 2.2 独立编译 ................................................................. 9 3 FSL Uboot 定制 ........................................................ 14 3.1 FDT支持 ............................................................... 14 3.2 DM(driver model)支持 ........................................... 20 3.3 Uboot目录结构 ...................................................... 31 3.4 Uboot编译 ............................................................. 34 3.5 Uboot初始化流程 .................................................. 35 3.6 使能了ATF后对Uboot初始化流程的影响 ............... 40 4 Uboot 定制 ............................................................... 41 4.1 修改 DDR大小 ....................................................... 41 4.2 修改调试串口与IOMUX说明 .................................. 44 4.3 DM I2C与PMIC初始化 .......................................... 53 4.4 通用GPIO ............................................................. 59 4.5 启动eMMC定制 ..................................................... 69 4.6 Ethernet定制 ......................................................... 78 5 Uboot debug信息 ..................................................... 89 5.1 Print env ............................................................... 89 5.2 dm - Driver model low level access ...................... 92 5.3 fdt .......................................................................... 95 5.4 I2C测试 ................................................................. 95 5.5 芯片寄存器访问 ..................................................... 98 updated to V5

This doc explain our Mcal driver and how to custome them. contents as follows: 目录 1 AutoSAR MCAL基本概念 .......................................... 2 1.1 AutoSAR目标 ......................................................... 2 1.2 AutoSAR概念 ......................................................... 2 1.3 AutoSAR基本方法 .................................................. 2 1.4 BSW(Basic Software) ............................................. 4 1.5 NXP Basic AutoSAR软件 ....................................... 4 1.6 RTE与BSW的配置 ................................................. 5 1.7 BSW的配置流程 ..................................................... 6 1.8 MCAL驱动 .............................................................. 7 2 MCAL工具 ................................................................. 7 3 MCAL说明 ................................................................. 8 3.1 MCAL的下载与说明 ................................................ 8 3.2 EB Tresos的下载，安装 ....................................... 13 3.3 RTD-MCAL安装 ................................................... 16 3.4 Trace32的下载与安装 .......................................... 18 3.5 样例工程的编译，运行 ......................................... 20 4 MCAL驱动配置与定制 ............................................. 40 4.1 MCU ..................................................................... 45 4.2 PORT ................................................................... 59 4.3 DIO ....................................................................... 69 4.4 FlexCAN ............................................................... 71 4.5 FlexLin ................................................................. 87 4.6 GMAC .................................................................. 93 4.7 I2C ..................................................................... 101 4.8 PMIC .................................................................. 108 4.9 PMIC WDOG ...................................................... 127 4.10 WDOG ............................................................... 137 4.11 UART ................................................................. 144 4.12 SPI ..................................................................... 149 4.13 PWM .................................................................. 165 4.14 ADC ................................................................... 171 4.15 Thermal .............................................................. 177

This doc explain how to configure a new LPDDR4 and test it on S32G, contents as follows: 目录 1    硬件资源，文档及工具下载... 2 1.1    硬件资源... 2 1.2    内存配置测试相关的文档... 2 1.3    内存配置与压力测试工具. 3 2    内存设计要求... 3 3    LPDDR4基础... 3 3.1    基本知识... 3 3.2    Inline ECC.. 4 4    硬件连接... 6 5    S32G+LPDDR4内存配置与测试步骤... 8 5.1    配置LPDDR4初始化寄存器设置... 9 5.2    使用内存测试工具初始化PHY及生成DDRC配置Uboot源代码    11 5.3    生成DDRC配置ATF源代码(从BSP32开始) 14 5.4    测试内存... 18 5.5    其它尺寸的LPDDR4配置... 19 6    测试失败的DEBUG.. 24 7    内存参数应用到Uboot中... 25 8    内存参数应用到ATF中... 25 9    附录... 25 9.1    一个重要的DDR TOOL bug Fix. 25 9.2    Uboot DDR测试工具... 26 9.3    Kernel DDR测试工具... 27 9.4    附DDR tool测试项截图... 28   Contents 1    Hardware Materials, Docs and Tools Needed. 2 1.1    Hardware resource. 2 1.2    Related docs of memory configuration and test 2 1.3    Memory configuration and test tools. 3 2    Memory Hardware Design Requirement 3 3    LPDDR4 Basics. 3 3.1    Basic Knowledge. 3 3.2    Inline ECC.. 5 4    Hardware Design. 7 5    S32G+LPDDR4 Memory Configuration and Test Steps. 8 5.1    Configure LPDDR4 DDRC Register Settings. 9 5.2    Use the Memory Test Tool to Initialize the PHY and Generate the DDRC Configuration Uboot Source Code  12 5.3    Generate ddrc configuration ATF source code (starting from bsp32) 15 5.4    Memory Test 19 5.5    Other size LPDDR4 configurations. 20 6    Debug of the Fails of Test 25 7    Modify the DDRC register settings in Uboot 26 8    Modify the DDRC register settings in ATF. 26 9    Appendix. 26 9.1    A importance DDR TOOL bug Fix. 26 9.2    Uboot DDR Test Tools. 27 9.3    Kernel DDR Test Tool 28 9.4    Attached Screenshot of DDR Tool Test Items. 29

This doc explain  where is the design resource and what they are of S32G in Chinese,  Contents as follows: 目录 1 www.nxp.com 官网资源 ............................................. 2 1.1 www.nxp.com Documentation ................................ 4 1.2 www.nxp.com Tools&Software ............................. 10 2 Flexera资源 ............................................................. 18 2.1 Automotive HW-S32G Evaluation Board .............. 21 2.2 Automotive HW-S32G GoldBox ........................... 22 2.3 Automotive HW-S32G RDB2(RDB不再说明) ....... 22 2.4 Automotive SW-S32G2 Standard Software.......... 23 2.5 Automotive SW-S32G2 reference Software ......... 28 2.6 Automotive SW-S32G2 Tools .............................. 30 3 Docstore资源 ........................................................... 31

         LittleVgl作为一款开源免费的嵌入式GUI得到越来越多工程师的厚爱，我们可以看到很多小型HMI项目或者一些开源社区都在使用它作为GUI的框架，同时也受益于用户群的不断扩大以及一些半导体原厂的青睐（通俗点就是说有赞助有钱儿了），LittleVgl本身也在快速的不断更新迭代，易用的组件和相关的辅助开发工具在不断的增加，而RT1050/1060/1170系列作为一款带有LCD控制器的平台，自然成为了LittleVgl最佳的载体之一了。         LittleVgl本身的组件已经很丰富了，但是遗憾的是一直没有加入对中文输入法Keyboard的支持（看了下它在Github上的Contributor List没有华人），这让它在我们国内的应用有了一些限制（注意在某组件上显示中文和真正的中文输入法是不同的概念），所以本项目旨在解决该问题，即把一个简单轻量的中文输入法框架嵌入到LittleVgl并跑在RT1050平台上，并把它开源开放出来，所以不要小看了我的“公益心”，哈哈。下图是该示例设计的UI界面        下面进入正题，首先把测试环境给出来，方便有兴趣有能力的朋友可以自行搭建（当然应一部分偷懒的强烈需求，我随本文档也附赠了完整的移植好的工程），然后我再一步一步地给出如何移植这套框架到用户自己的工程里，当然我已经把代码本身做了很多优化，尽量减小环境依赖，力求最少步骤的移植过程，理论上来讲不太会出现移植后编译出一堆Error的问题，咳咳。。。下面我们赶紧开整吧： 测试环境： SDK版本：SDK_v2.9.1 SDK参考例程：boards\evkbimxrt1050\littlevgl_examples\littlevgl_demo_widgets LittleVgl版本：v7.4.0 IDE工具：Keil_v5.31 开发板：MIMXRT1050-EVK + 480*272 RGB LCD屏 软件说明： 我们先看下这套中文输入法所需的几个文件，如下图所示，.c和.h文件加起来一共7个，其中nxp_logo.c只是我额外加的一个NXP的官方logo图标转成的C数组文件供littleVgl调用显示，属于锦上添花的东西，可有可无，真正跟输入法相关的是剩下的6个文件，下面我们逐一介绍下这几个文件的作用： 1. qwerty_py.c/.h：        实际上这两个文件才是这套全键盘拼音中文输入法的核心框架，实现了对输入的拼音字母进行索引匹配对应的汉字候选列表，这部分我是移植了如下链接中网友分享的代码，所以这两个文件我的角色只是一个大自然搬运工，不过说实话我是很感激该网友的无私分享的（这也是我一直推崇开源分享精神的源动力），之前对平时使用的各种输入法里面的算法原理一直充满好奇，直到看了这篇文章后才豁然开朗，“So that is what it is!”，让我获益匪浅（可能人的学习曲线和知识体系就是这样一点一滴的积累吧），而且更关键的是，如果让我继续往下开发诸如拼音联想和多汉字输入等功能的话，我更多关心的可能只是逻辑搭建的工作量问题，而不是纠结于Yes or No的问题了，因为咱已经了解了其最底层的工作原理了，所以很多复杂的事情，我们如果能抽丝剥茧的找到其最底层的本质（虽然这真的很难），那很多让人抓耳挠腮的问题很快就可以理清思路。说到这里我思维又发散了，呵呵，我想起让Linus Torvalds等一波老大神们一直头疼的Linux内核维护后继无人的问题，其实我的个人理解有很大一部分原因是如今的Linux太庞大了以至于几乎没有后辈的人对Linux的理解能赶上这些老辈大神，而这些老辈大神的最大优势是他们创建了Linux最早期的底层框架而且难能可贵的是一直在follow Linux每个版本的历史。总之，推荐大家看看如下这篇文章吧（实际上主要内容也都是代码），希望能各有所获； https://www.amobbs.com/thread-5668320-1-1.html?_dsign=0939dcbd 2. lv_chs_keyboard.c/.c文件：        这部分就是我的工作了（咱也不能啥都搬运…，这是体现咱的value的东西不是），我把它当作littleVgl的一个补充组件来写的，里面的大多数API参考官方littlevgl的lv_keyboard.c，所谓的文章开头的嵌入中文输入法到LittleVgl GUI环境中实际上就是这两个文件干的活，即将上面提到qwerty.c/.h实现的拼音输入法与LittleVgl框架结合到一块，起到一个桥梁的作用，所以如果你想把这套中文输入法嵌入到其他GUI环境中的话（比如emWin，GUIX，TouchGFX等），那主要的工作就是参考这两个文件的内容了； 3. lv_font_NotoSansCJKsc_Regular.c字体文件：        虽然littleVgl官方源码包里自带了一个中文字体文件（\lvgl\src\lv_font\lv_font_simsun_16_cjk.c），但是它只包含了1000个左右最常用的字，我实际体验了下很多我们想用的字都找不到，所以这个时候就需要自己去做一个更全一点的字体库了。这里面涉及到两个问题需要考虑，第一是很多我们常见的中文字体是收费的（咱PC机的Microsoft Office套件里的中文字体都是微软付费买的，所以咱也理解下早年正版Windows为啥辣么贵了，那你问为啥现在便宜了？因为人家现在不靠这个赚钱了呗），第二个是字体转换工具的问题，我们网上找到的字体都是TTF或者OTF格式的，但littleVgl是不认的，需要转换成它支持的字体格式。        对于第一个问题，我网上搜了好久最终选择了目前用的比较多的Google开源免费的字体，Google真乃金主也，它维护的网站里面字体各种各样啥都有且是开源免费的，如下链接，我选择的是NotoSansCJKsc字体（最后面的sc表示simplified Chinese，简体中文），然后它里面又包含了各种字形（regular, bold, light等），可以根据需要自行选择，整个包很大（100多MB），拆分成不同字形的就小了（每个14~16MB左右）； https://www.google.com/get/noto/        对于第二个字体转换工具的问题，LittleVgl官方自带了一个字体转换工具（online font converter）,我个人觉着不太好用（对OTF字体支持的不行），这里推荐阿里大神自己做的一个LittleVgl字体转换工具（LvglFontTool），非常方便好用，且支持加入Awesome图标； http://www.lfly.xyz/forum.php?mod=viewthread&tid=24&extra=page%3D1        关于字体这部分我需要再补充个问题，就是它占用的memory大小，毕竟我们是在嵌入式MCU平台Flash和RAM的资源是受限的，如下图所示，该字体文件占用大概1Mbytes的rodata空间（即可寻址的Flash空间，当然该大小可以通过在上图转换工具中增减一些文字来调 整），所以在移植本套输入法之前需要预留足够的Flash空间，当然对RT平台来说这部分还好，毕竟其本身就外扩至少几MB空间的QSPI Flash作为存储空间的。 4. lv_demo_chineseinput.c/.h文件：        这两个文件属于应用层实现了，主要关注该文件中下图的ta_event_cb函数（即textarea事件的callback，点击文本框的输入时回调），在里面我们需要按照1，2，3去调用即可（这三步的API均在lv_chs_keyboard.c/h文件里实现）；        至此，这套全键盘拼音中文输入法框架所需的几个文件就介绍完了，用户只需要把这几个文件放到自己的工程设置好文件搜索路径，并参考随本文档附带的代码工程示例，再结合自己产品的GUI样式，把这套中文输入法嵌入到自己应用当中。

Introduction Background There is not an official data for PCIe latency and performance, while some customers pay attention to and request these data. This paper utilizes Lmbench lat_mem_rd tool and DPDK qdma_demo to test the PCIe latency and performance separately. Requirement 1) Plug Advantech iNIC (LX2160A) into LX2160ARDB. 2) Configure EP ATU outbound window at console. 3) Apply the patch to lmbench-3.0-a9, and recompile lmbench tool. 4) There is qdma_demo in iNIC kernel rootfs by default. Test Environment     PCIe Latency Overview   Direction Description Latency(ns) PCIe(Gen3 x8) – DDR read from EP to RC 900 PCIe – PCIe – DDR Read from EP to EP (through CCN-508) 1550 PCIe – PCIe – DDR Read from EP to EP (through HSIO NOC) 1500 Setup 1) LX2160ARDB 2) iNIC – PCIe EP Gen3 x8 with LX2160A 3) Test App running at iNIC: Lmbench lat_mem_rd   # ./lat_mem_rd_pcie -P 1 -t 1m   PCIe Performance Overview    Direction Throughput (Gbps) PCIe EP to EP 50   Setup 1) LX2160ARDB 2) iNIC – PCIe EP Gen3 x8 with LX2160A 3) Test App : qdma_demo running at iNIC   $./qdma_demo -c 0x8001 -- --pci_addr=0x924fa00000 --packet_size=1024 --test_case=mem_to_pci Peer to Peer On LX2 Rev. 2      Products   Product Category NXP Part Number URL MPU LX2160A https://www.nxp.com/products/processors-and-microcontrollers/arm-processors/layerscape-processors/layerscape-lx2160a-lx2120a-lx2080a-processors:LX2160A LSDK software Layerscape Software Development Kit https://www.nxp.com/design/software/embedded-software/linux-software-and-development-tools/layerscape-software-development-kit:LAYERSCAPE-SDK   Tools    NXP Development Board URL LX2160ARDB https://www.nxp.com/design/qoriq-developer-resources/layerscape-lx2160a-reference-design-board:LX2160A-RDB Advantech ESP2120 Card      

        S32G just support serial download a M7 image to run by internal rom codes, our S32G DS IDE have a flash tools to use this feature to burn the image to external device. So current image burn method will divide into 2 step: 1: burn a uboot into the external device by S32G DS flash tools. 2: reboot the codes with uboot and run with network to burn the linux image into external device.      which need two working place on manufacture line, and customer wish to have a one time on-line tools, which means we need use serial port to boot uboot directly but S32G rom codes do not support it.       We have a reference tools of S32V but which IP difference is big between on S32V and S32G, So we can not reuse it and have to develop a new one.       The development working include: 序号 开发工作 说明 开发者 1 开发 根据S32G的serial boot协议要求，开发PC端的串口工具来下载M7镜像 John.Li 2 开发 根据自定义协议要求，开发PC端的串口工具来下载A核Bootloader到SRAM中 John.Li 3 开发 根据自定义协议要求，开发M7镜像的串口接收与Checksum逻辑 John.Li 4 开发 修改M7镜像支持串口0 John.Li 5 开发 开发实现M7镜像的串口单字节同步收发函数 John.Li 6 开发 开发实现A53启动功能 John.Li 7 调试与Debug 调试解决串口接收乱码问题(Serial boot rom codes仍然在回送消息串口) John.Li 8 调试与Debug 提供 解决A核启动串口halt思路(Serial boot rom codes仍然占用串口) John.Li 9 调试与Debug 优化M7镜像，缩小大小 Tony.Zhang 10 调试与Debug 根据M7镜像和A核 Uboot在SRAM中的内存分配要求，重排M7镜像位置，避免冲突 Tony.Zhang 11 调试与Debug 在M7中初始化SRAM空间 Tony.Zhang 12 调试与Debug 在M7中设置SRAM可执行空间 Tony.Zhang 13 调试与Debug 调试解决由于cache没有及时回写导致的下载镜像错误的问题 Tony.Zhang 14 调试与Debug 集成，调优与文档 John.Li   Pls check the attachment for the doc/codes/binary release which include:    Release      |->M7: Linflexd_Uart_Ip_Example_S32G274A_M7: S32DS M7工程。      |->PC: s32gSerialBoot_Csharp: PC端的Visual Studio的C#的串口工具工程。      |->Test:      |    |-> 115200_bootloader.bin: S32DS M7工程编译出来的bin文件，波特率为115200      |    |-> 921600_bootloader.bin: S32DS M7工程编译出来的bin文件，波特率为921600      |    |->load_uboot.bat: 运行工具的批处理文件，运行成功后打开串口可以看到Uboot执行，默认使用的波特率是115299         |    |->readme.txt:其它测试命令 |    |->s32gSerialBoot.exe:编译出来的PC端串口工具 |    |->u-boot.bin: BSP29默认编译出来的u-boot.bin.      Product Category NXP Part Number URL Auto MPU     S32G274     https://www.nxp.com/s32g    

Overview The S12ZVH-REF-V1 is a reference design engineered for being a design base for starting an instrument cluster project, also it helps to reducing Automotive Cluster development time and maximizing engineering resources. Based on the 16-bit S12 MagniV® S12ZVH mixed-signal microcontrollers, the S12ZVH-REF-V1 provides a production-looking design with impressive integration. The S12ZVH-REF-V1 reference design is not only provided as a hardware reference but also as a software and mechanical design. Block Diagram   Products Product Features S12ZVH MagniV Mixed-signal MCU  16-bit S12 MagniV® S12ZVH mixed-signal microcontrollers for instrument cluster.   Features Interfaces   LIN physical transceiver and connector CAN connector interfaced with MCUs CAN physical transceiver Components 1 x custom 160 segment LCD 1 x low-power piezoelectric speaker 4 x stepper motors 49 x LEDs used as telltales and backlights 6 x user buttons 2 x potentiometers S12ZVH The S12ZVH-REF-V1 does not include on-board programming/debugging circuitry; it requires an external programmer compatible with the BDM protocol. Files S12ZVH-REF-V1 Mechanical and Assembly files  S12ZVH-REF-V1 Reference Design Software (CW10.5) 

Overview   The PN7462 family consists of 32-bit Arm® Cortex®-M0-based NFC microcontrollers offering high performance and low power consumption. Because of the integrated NFC, many of the applications in which this product is used require interaction between some controllers, either to send data or instructions. In this case the board serves as a device for reading or writing NFC devices.   Required Material OM27462CDKP: NFC Controller development kit  MCUXpresso Software and Tools    Step-by-Step Download MCUXpresso Download and unzip attachment Open the Project in MCUXpresso Build it Connect LPC Link to PN7462 card Connect the two cards to the pc Debug the Project Use GPIO 4 and 5 for select interface Use GPIO 6, 7 and 8 for select operation mode

  i.MXRT系列具有内部ROM，并且ROM中暴露出了一些功能接口可供用户直接使用。 本文介绍了Flexspi Nor ROM APIs, 并且列举了API相关的参数及示例程序。 通过这些API可以很方便的操作外部Flexspi Nor Flash。用户无需关系细节。   Products Product Category NXP Part Number URL MCU MIMXRT1060 https://www.nxp.com/products/processors-and-microcontrollers/arm-microcontrollers/i-mx-rt-crossover-... MCU MIMXRT600 https://www.nxp.com/products/processors-and-microcontrollers/arm-microcontrollers/i-mx-rt-crossover-...   Tools NXP Development Board URL i.MX RT1060 Evaluation Kit https://www.nxp.com/design/development-boards/i-mx-evaluation-and-development-boards/mimxrt1060-evk-... i.MX RT600 Evaluation Kit https://www.nxp.com/design/development-boards/i-mx-evaluation-and-development-boards/i-mx-rt600-eval...   SDK SDK Version URL MCUXpresso SDK Builder https://mcuxpresso.nxp.com/en/welcome