This document describes step-by-step how to run NFC on Raspberry Pi platform. Hardware setup: You need:    - Raspberry Pi (any model) : https://www.raspberrypi.org/products/:        - OM5578(PN7150 demokit) in RPi configuration (or OM5577(PN7120 demokit)😞         Then simply assemble boards together, stacking OM5578RPI (or OM5577RPI) to Raspberry Pi expansion connector:       Software setup:   Use Raspbian  (https://www.raspberrypi.org/software/operating-systems/) or any other Linux distribution (guidelines to set up Linux environment on raspberry pi: https://www.raspberrypi.org/documentation/installation/installing-images/). Step by step procedure: Enable i2c support:        On Raspbian: Run "sudo raspi-config" Use the down arrow to select "5 Interfacing Options" Arrow down to "P5 I2C" Select "yes" when it asks you to enable I2C Also select "yes" if it asks about automatically loading the kernel module Use the right arrow to select the <Finish> button Select "yes" when it asks to reboot       The system will reboot. when it comes back up, log in and enter the following command "ls /dev/*i2c*".       The Pi should respond with "/dev/i2c-1" which represents the user-mode I2C interface.   Install necessary tools:         On Raspbian execute the command:    sudo apt-get install autoconf automake libtool git Clone Linux libnfc-nci library repository:         Execute the command:    git clone https://github.com/NXPNFCLinux/linux_libnfc-nci.git Configure the library:         Execute the commands:    cd linux_libnfc-nci    ./bootstrap    ./configure --enable-alt Build and install the library:         Execute the commands:    make       sudo make install    export LD_LIBRARY_PATH=/usr/local/lib Run demo application (built and installed together with the library during previous step):         To simply display all data collected from remote NFC device (Peer, reader/writer or card), run the demo application in poll mode executing the command:    nfcDemoApp poll         For more details about the demo application modes execute command:    nfcDemoApp --help   One step further: Set environment variable to reference library installation:         Execute command: export LD_LIBRARY_PATH=/usr/local/lib         You may wan't to make this setting permanent by adding it to your .bashrc file for instance : echo "export LD_LIBRARY_PATH=/usr/local/lib" >> .bashrc Write your own application:         Several simple examples demonstrating use of the linux_libnfc-nci library for different use cases (Reader, Peer to peer, Host Card Emulation) are given as reference: https://github.com/NXPNFCLinux/linux_libnfc-nci_examples        - Simply clone the repository    git clone https://github.com/NXPNFCLinux/linux_libnfc-nci_examples.git        - Browse to the targeted example:    cd linux_libnfc-nci_examples/xxx_example        - Build the example:    make        - Run the example    ./xxx_example   Additional information: Another Platform ?        Using UDOO NEO (with OM5577 or OM5578 in Arduino configuration) ?           -> Follow step-by-step procedure, just updating src/halimpl/pn54x/tml/i2c/phTmlNfc_alt.h file to set CONFIGURATION flag to value 2, before building the library        Using BeagleBone Black (with OM5577 or OM5578 in BBB configuration) ?           -> Follow step-by-step procedure, just updating src/halimpl/pn54x/tml/i2c/phTmlNfc_alt.h file to set CONFIGURATION flag to value 2, before building the library        Using other Linux platform or others OM5578/OM5577 demokits configuration ?           -> Follow step-by-step procedure, just updating src/halimpl/pn54x/tml/i2c/phTmlNfc_alt.h file to set CONFIGURATION flag to value 0 and defining I2C_BUS, PIN_INT and PIN_ENABLE flags according to the HW connection, before building the library Running Android ? -> Follow guidelines provided in the related documentation: https://www.nxp.com/docs/en/application-note/AN11690.pdf

doc&patch explain how to decrease the qspi init clock to avoid the spi read qspi id error in linux S32G Linux BSP初始化QSPI Nor时钟是默认200Mhz，但是JEDEC规范建议读QSPI Nor ID是使用SPI模式，低速时钟，所以默认BSP是有可能读ID不成功的，本文说明如何解决这个问题。 本文采用软件版本为Linux BSP43 目录 1    背景与资料说明... 2 1.1  背景说明... 2 1.2  所需资料说明... 2 2    Linux QSPI Nor驱动说明... 3 2.1  QSPI Nor控制器驱动说明... 3 2.2  QSPI Nor设备驱动说明... 4 2.3  SPI Mem驱动说明... 5 3    代码修改... 6 3.1  将初始化时钟切换成133Mhz. 6 3.2  在初始化后将时钟切换回200Mhz. 7 4    测试... 7 4.1  软件测试... 7 4.2  硬件测量... 7 5    其它注意事项... 8    

This doc explain how to support RGMII/RMII/MII 100Mbps device in Mcal, and also the debug suggestion. in Chinese version. 目录 1    背景与资料说明... 2 1.1  背景说明... 2 1.2  所需资料说明... 2 2    RGMII RMII MII区别说明... 2 2.1  IO管脚与信号方向... 2 2.2  时钟说明... 7 2.3  注意事项... 7 3    RGMII MCAL配置... 8 3.1  MCAL配置... 8 3.2  注意事项... 10 4    RMII MCAL配置... 11 4.1  MCAL配置... 11 4.2  注意事项... 13 5    MII MCAL配置... 14 5.1  MCAL配置... 14 5.2  注意事项... 15 6    其它建议... 16 6.1  Debug. 16 6.2  EMI 16  

本文说明在S32G上，如何升高以太网MDIO总线速度，其应用场景主要是为了提高MDIO的访问速度，来应对S32G对外部交换机的高速诊断要求，因为通常外部交换机可以支持高速MDIO。 本文说明方法并不保证信号质量和符合规范，请注意。 目录 1    需要的资料... 2 2    背景说明... 2 3    硬件说明... 3 4    PFE MCAL驱动代码修改... 4 4.1  MDIO时钟树说明... 4 4.2  创建PFE MCAL Master工程... 7 4.3  MDIO源代码说明... 7 4.4  源代码修改... 7 4.5  测试... 8 5    PFE Linux驱动修改说明(未测试) 9

本文说明在S32G上如何修改eMMC时钟，来避开200Mhz的或及倍频的频率EMI干扰检查点。 目录 1    背景说明和需要的资料... 2 1.1  背景说明... 2 1.2  需要的资料... 2 2    eMMC的硬件连接... 3 3    eMMC时钟初始化方法... 4 3.1  eMMC时钟源说明及修改目标... 4 3.2  M7+Bootloader方法(可选项) 6 3.3  ATF初始化方法... 7 4    修改eMMC时钟... 9 4.1  ATF的修改... 9 4.2  Uboot相关的修改... 9 4.3  非整除时钟的修改考虑... 10 5    测试结果... 11 update to V2，增加分数分频： 6    分数分频... 13 6.1  调试方法... 13 6.2  代码修改... 14 6.3   测试结果   15

本文说明S32G在Linux中如何使用内存读写工具来发起一个HSE Server服务请求，以确认HSE是否正常工作。本说明的目的旨在在极端缺少Debug手段的情况下，确认HSE的状态。 目录 1    背景说明与参考资料... 2 1.1  背景说明... 2 1.2  参考资料... 2 2    启动包含HSE的Linux镜像... 3 3    HSE服务代码逻辑与寄存器状态... 3 3.1  HSE Demo示例... 3 3.2  IDEL情况下MU寄存器状态... 6 4    使用Linux memtool命令来访问HSE. 10 4.1  检查HSE状态... 10 4.2  准备hseSrvDescriptor_t数据结构... 10 4.3  申请HSE服务... 11 5    其它建议... 12

本文说明如何配置MCAL UART模块为DMA模式。 默认的MCAL UART模块是使用的PIO模式。 本文采用软件版本为MCAL RTD 4.0.2。 目录 1    背景与资料说明... 2 1.1  背景说明... 2 1.2  所需资料说明... 2 2    创建UART工程... 2 2.1  打开工程... 2 2.2  修改波特率... 3 2.3  编译... 3 2.4  默认工程说明与运行... 4 3    配置UART DMA模式... 5 3.1  参考资料... 5 3.2  增加并配置MCL模块... 5 3.3  修改UART模块... 6 3.4  修改Platform模块... 7 3.5  处理Cache相关问题... 7 3.6  测试结果... 8

本文说明如何配置MCAL ICU模块为GPIO Input。 默认的MCAL ICU模块是使用FTM输入为示例的。 本文采用软件版本为MCAL RTD 4.0.2 目录 1    背景与资料说明... 2 1.1  背景说明... 2 1.2  所需资料说明... 2 2    创建ICU工程... 3 2.1  打开工程... 3 2.2  编译与运行... 3 2.3  默认工程说明... 4 3    增加GPIO输入支持... 6 3.1  修改说明... 6 3.2  修改Port模块... 6 3.3  修改ICU模块... 7 3.4  Platform模块... 8 3.5  主测试程序修改... 9 3.6  测试结果... 10

本文说明S32G3 M7核Standby MCAL demo 详细情况及定制，并在进入Standby之前 调用QSPI 接口将QSPI NOR flash配置进入 deep power down模式，以节省用电。 目录 1    参考资料说明... 2 2    G2和G3 Demo的区别... 2 3    G3 MCAL Demo的实现... 4 3.1  修改UART驱动... 4 3.2  实现时钟关闭代码... 4 3.3  配置电源模式切换驱动... 5 3.4  配置唤醒源... 5 3.5  加入PMIC驱动... 6 3.6  主函数逻辑实现... 7 3.7  运行测试... 7 3.8  未来开发计划... 8 4    将QSPI NOR设置进入Deep Power Down模式... 8 4.1  Fls层的修改... 10 4.2  中间层的修改... 10 4.3  QSPI_IP层的修改... 13 4.4  主测试函数调用... 16 4.5  Fls驱动的测试... 17 5    将Deep Power Down功能集成到STANDBY工程中并测试    18 5.1  EB配置... 18 5.2  主测试函数与编译修改... 20 5.3  运行测试... 21

现在越来越多的客户，对于S32G PFE在master/slave的使用有了需求。 但是，PFE只有4个HIF接口，HIF0~HIF3，而PFE有3个EMAC口，以及LLCE2PFE也需要要给HIF，从而HIF成为一个关键资源。 同时，有些客户需要从A核，M核的业务考量，A核和M核的网络不仅要和外部设备进行通信，同时A核和M核内部也有通信需求，并且需要把业务报文和管理报文分离，这就对PFE master/slave的使用场景有了更多变化，以及对各种配置有了更多需求。 因此，针对PFE/Slave的几种使用典型的使用场景，进行配置。

在进行时钟同步时，目前S32G2/G3有一种很典型的使用场景： Grand master clock  <-> S32G PFE <-> 其余连接在PFE 某些 eMAC口上的设备 外部的grand master clock，连接在PFE的一个eMAC上，要同步S32G以及连接在PFE其余eMAC上的设备时钟。 但是S32G2/G3的PFE仅仅是支持timestamp，对于将S32G PFE设置成交换机使用时，PFE不能实现Transparent clock的功能。 因此，本文讨论将PFE + S32G SoC当作Transparent clock，以及将PFE + S32G当作boundary clock，来同步S32G以及其余部件的时钟。

本文说明了S32G如何储存mac地址，包括dts保存，systemd指定和fuse保存的办法： 目录 1 需要的软件................................................................. 2 2 背景说明 .................................................................... 2 3 PFE eMAC MAC地址说明 ......................................... 2 3.1 DTS配置 ................................................................. 2 3.2 源代码说明 ............................................................. 3 3.3 测试 ........................................................................ 4 4 GMAC0 MAC地址说明 .............................................. 4 4.1 DTS配置 ................................................................. 4 4.2 源代码说明 ............................................................. 4 4.3 SystemD脚本 ......................................................... 5 4.4 固定GMAC MAC地址的修改办法 ........................... 6 5 用Uboot命令烧写FUSE MAC地址项 .......................... 7 6 修改为从fuse中获得GMAC0 MAC地址 ...................... 9 6.1 Uboot代码修改 ....................................................... 9 6.2 Uboot写MAC寄存器说明 ...................................... 10 6.3 测试 ...................................................................... 10  

本文为如下G2版本的升级篇，使用G3+更新的软件 目录 1    需要的软件与工具... 2 1.1  软件工具与文档... 2 1.2  开发说明... 3 2    测试软件安装编译说明... 3 2.1  安装LLCE Logger驱动... 3 2.2  编译LLCE驱动测试程序(以CAN Logger 为例) 4 2.3  Logger Demo功能说明... 5 2.4  M7 BootLoader ATF镜像冲突检查... 7 2.5  LLCE Logger Demo去掉CLOCK INIT. 9 2.6  LLCE Logger Demo去掉MCU 相关INIT. 10 2.7  LLCE Logger Demo程序去掉PORT INIT. 10 2.8  中断冲突说明... 10 2.9  去掉其它无用初始化... 11 3    Bootloader工程说明... 11 3.1  关掉XRDC支持... 12 3.2  关掉eMMC/SD支持(可选) 13 3.3  关掉secure boot(可选) 14 3.4  增加LLCE 驱动所需要的PORT 的初始化... 15 3.5  解决Bootloader,MCAL 与Linux 的clock 冲突... 16 3.6  配置A53 Boot sources: 34 3.7  配置M7 Boot sources: 36 3.8  关闭调试软断点... 37 3.9  编译Bootloader工程... 38 3.10 制造Bootloader的带IVT的镜像... 39 3.11 烧写镜像... 41 4    Linux LLCE logger功能修改... 42 4.1 ATF的修改... 42 4.2 Linux中关于LLCE配置... 44 4.3 LLCE相关初始化冲突说明... 45 5    测试... 46 5.1  硬件连接... 46 5.2  LLCE logger 测试过程... 46 S32G Boot customization doc how to run bootloader to run mcal&linux https://community.nxp.com/t5/NXP-Designs-Knowledge-Base/S32G-Bootloader-Customzition/ta-p/1519838

doc&project&patch&script explain to support GD qspi nor in lauterbach, flash tool,ivt,fls mcal, fls bootloader and linux/ chinese/english 目录 1    背景和参考资料... 2 1.1  背景说明... 2 1.2  参考资料... 3 1.3  硬件连接... 5 2    Lauterbach脚本驱动开发(可选) 5 2.1  准备参考脚本... 5 2.2  QuadSPI_ReadID.. 6 2.3  配置QSPI NOR为DOPI模式... 7 2.4  使用DOPI模式 READ_8DTRD.. 10 2.5  测试结果... 13 3    Flash tool算法镜像开发... 14 3.1  Flash SDK实现的算法... 15 3.2  开发新的flash源代码... 17 3.3  测试结果... 20 4    开发IVT参数头... 22 4.1  S32G QSPI控制器配置区别... 24 4.2  QSPI的配置区别... 28 4.3  测试结果... 29 5    开发MCAL Fls驱动... 30 5.1  MCAL Fls驱动工程说明... 30 5.2  FlsMem配置页... 34 5.3  MemCfg配置页... 35 5.4  测试结果... 49 6    开发Bootloader工程中Fls驱动... 51 6.1  Bootloader工程说明... 51 6.2  Bootloader与MCAL Fls驱动的不同点... 53 6.3  镜像打包... 54 6.4  测试结果... 56 7    开发Linux驱动(可选) 57 7.1  Linux GD驱动支持情况... 57 7.2  时钟相关的修改... 58 7.3  在DTS中增加GD flash的支持... 60 7.4  修改源代码增加flash信息结构体... 61 7.5  修改源代码中flash的fixup支持DTR模式... 62 7.6  Turning dummy值解决读错位的问题... 64 7.7  测试结果... 65   Content 1    Background and References. 2 1.1  Background. 2 1.2  References. 3 1.3  Hardware Link. 5 2    Lauterbach Script development(Optional) 6 2.1  Preparing the refer script 6 2.2  QuadSPI_ReadID.. 6 2.3  Configure QSPI NOR to DOPI mode. 8 2.4  Use DOPI mode  READ_8DTRD.. 11 2.5  Test report 13 3    Flash tool algorithm image development 15 3.1  Algorithms implemented by Flash SDK. 15 3.2  Develop new flash source code. 17 3.3  Test Report 21 4    Develop IVT Parameter Header 23 4.1  S32G QSPI Controllder configuration difference. 25 4.2  QSPI Configuration Difference. 30 4.3  Test Report 30 5    Develop MCAL Fls driver 31 5.1  MCAL Fls Driver Project Details. 31 5.2  FlsMem Configuration page. 35 5.3  MemCfg Configuration page. 36 5.4  Test Report 51 6    Develop Bootloader Project Fls Drivedr 52 6.1  Bootloader Project Details. 52 6.2  Difference of Bootloader and MCAL Fls Driver 54 6.3  Image Package. 56 6.4  Test Report 58 7    Develop Linux Driver(Optional) 59 7.1  Linux GD Driver Details. 59 7.2  Modification of Clock. 60 7.3  In DTS add GD flash Support 62 7.4  Modify source code and add flash information structure  63 7.5  Modify the fixup of flash in source code to support DTR mode  64 7.6  Turning Dummy Value to Solve the Misplacement Problem   66 7.7  Test Report 67

S32G Host Secure debug methods with Lauterbach tool after LC is updated, and some details about secure debug knowledge in S32G. 本文主要描述S32G在演进生命后如何使用lauterbach工具来进行调试，涉及到S32G HSE相关知识点。

This doc explain how to compile PFE driver into kernel to accelerate the network boot time, chinese version: 目录 1    需要的软件，工具与文档... 2 2    目前PFE驱动的情况... 2 3    将PFE Slave驱动编译进内核... 3 3.1  将PFE驱动代码加入内核... 3 3.2  开发Makefile文件... 6 3.3  编译与测试... 8 4    将PFE Master驱动编译进内核... 10 4.1  编译Master工程... 10 4.2  测试... 11 4.3  解决FW的加载问题... 11 Contents 1    Related Materials. 2 2    Current PFE Driver 2 3    Compiled PFE Slave into Kernel 3 3.1  Put the PFE driver source into kernel source. 3 3.2  Develop the Makefile. 6 3.3  Compilation and Testing. 8 4    Compiled PFE Master Driver into Kernel 10 4.1  Compiling the Master driver 10 4.2  Testing. 11 4.3  Solve the FW loading fail issue. 11    

本文说明S32G HSE On-demand SMR验证的应用方法，本文演示的示例应用为： Secure Bootloader对Linux Bootloader fip.bin的验证 目录 1    背景说明与参考资料... 2 1.1  背景说明... 2 1.2  参考资料... 3 2    S32G On-demand SMR Verification说明... 4 2.1  SMR Verify的说明... 4 2.2  On-demand SMR Verify. 4 3    环境搭建... 5 3.1  EB配置说明... 5 3.2  ATF编译说明... 8 3.3  镜像烧写... 9 4    Bootloader代码开发... 9 4.1  OnDemand SMR install 9 4.2  OnDemand SMR verify. 13 5    测试... 16 5.1  Lauterbach跟踪... 17 5.2  Fip.bin破坏实验... 19 5.3  硬件确认... 19   This application doc explains the application method of S32G HSE On_demand SMR verification. The example application demonstrated in this doc is: Secure Bootloader verification of Linux Bootloader fip.bin This application doc explains the application method of S32G HSE On_demand SMR verification. The example application demonstrated in this doc is: Secure Bootloader verification of Linux Bootloader fip.bin Contents 1    Background Description and Reference Materials. 2 1.1  Background Description. 2 1.2  Reference Materials. 3 2    S32G On-demand SMR Verification. 4 2.1  SMR Verify. 4 2.2  On-demand SMR Verify. 4 3    Build the Development Environment 5 3.1  EB Configuration. 5 3.2  ATF Compiling. 8 3.3  Burn Image. 9 4    Bootloader Codes Development 9 4.1  OnDemand SMR install 9 4.2  OnDemand SMR verify. 13 5    Testing. 16 5.1  Lauterbach Tracking. 16 5.2  Fip.bin Broken Test 19 5.3  Probe the Hardware. 19

This doc explain bootloader secure boot feature and how to re-develop it to support: .FW update .OTP attribute access .IVT protect: 目录 1 参考资料 .................................................................... 2 2 S32G Secure Boot说明 ............................................. 2 2.1 IVT头格式与Secure Boot相关 ................................ 3 2.2 Secure Boot流程 .................................................... 3 2.3 Secure Boot配置 .................................................... 4 2.4 Secure Boot涉及到的HSE内容 ............................... 6 3 环境搭建 .................................................................... 7 3.1 搭建编译环境 .......................................................... 7 3.2 IVT镜像制造 ........................................................... 7 3.3 镜像烧写 ................................................................. 8 3.4 Bootloader Secure Boot测试 .................................. 8 4 Bootloader Secure Boot代码与功能说明 ................... 9 4.1 EB配置说明： ........................................................ 9 4.2 EB生成代码说明： ............................................... 15 5 定制1：HSE FW update .......................................... 22 5.1 代码开发 ............................................................... 22 5.2 测试 ...................................................................... 25 6 定制2：HSE OTP Attribute设置 ............................... 26 6.1 代码开发 ............................................................... 26 6.2 模拟测试 ............................................................... 33 7 定制3：IVT签名 ....................................................... 35 7.1 代码开发 ............................................................... 35 7.2 模拟测试 ............................................................... 40 Contents 1 Reference Materials .................................................. 2 2 S32G Secure Boot ..................................................... 3 2.1 IVT header format for the Secure Boot part .......... 3 2.2 Secure Boot Flow ................................................... 3 2.3 Secure Boot Configuration ..................................... 4 2.4 HSE background of Secure Boot ........................... 6 3 Build the Project ........................................................ 7 3.1 Build the Compiling Environment ........................... 7 3.2 Create IVT Image ................................................... 7 3.3 Burning Image ........................................................ 8 3.4 Bootloader Secure Boot Testing ............................ 9 4 Bootloader Secure Boot Codes and Function Description 9 4.1 EB Configuration .................................................... 9 4.2 EB output codes ................................................... 15 5 Customization 1：HSE FW update ......................... 22 5.1 Codes development ............................................. 23 5.2 Testing ................................................................. 26 6 Customization 2：HSE OTP Attribute Setting ......... 26 6.1 Code Development .............................................. 27 6.2 Simulation test ...................................................... 34 7 Customization 3：IVT Signature ............................. 36 7.1 Codes Development ............................................. 36 7.2 Simulation Testing ................................................ 40  

本文说明S32G LLCE CAN Linux驱动的 快速测试方法。 目录 1 参考资料 .................................................................... 2 1.1 参考资料 ................................................................. 2 1.2 版本匹配说明 .......................................................... 2 2 环境搭建 .................................................................... 3 2.1 使用Yocto编译 ........................................................ 3 2.2 使用Standalone编译 ............................................... 4 3 测试 ........................................................................... 5 3.1 硬件连接 ................................................................. 5 3.2 测试方法 ................................................................. 6 4 LLCE CAN Linux驱动说明 ......................................... 7 4.1 DTS ........................................................................ 7 4.2 源代码 .................................................................... 9  

this doc explain the HSE crypto driver and how to develop new feature 目录 1 参考资料 .................................................................... 2 1.1 参考资料 ................................................................. 2 1.2 版本匹配说明 .......................................................... 3 2 HSE FW服务 ............................................................. 3 2.1 服务描述符 ............................................................. 3 2.2 服务编号 ................................................................. 4 2.3 服务请求和响应 ...................................................... 6 2.4 服务执行 ................................................................. 9 2.5 Crypto驱动AES示例使用到的服务 ........................ 18 3 环境搭建 .................................................................. 19 3.1 安装与编译 ........................................................... 19 3.2 运行Demo ............................................................ 21 4 Crypto驱动代码与功能说明 ...................................... 23 5 定制1：增加GetAttribute功能 .................................. 28 6 CmacCtr Demo简介 ................................................. 31 7 SymmetricPrimitive Demo简介 ................................ 32 8 总结 ......................................................................... 34 9 其它注意事项 ........................................................... 34