Multi Source Translation Content

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Multi Source Translation Content

Discussions

Sort by:
当使用 FRDM-MCXN947 的 I3C 接口进行 I2C 通信时,时钟拉伸功能失效。 您好,我目前遇到一个问题:我想使用 FRDM-MCXN947 的 I3C 接口进行 I2C 通信,但我连接的从设备在数据准备期间会出现时钟拉伸,因此我必须等待从设备释放 SCL 信号才能开始数据传输。 我尝试使用 MCXNP184M150F70RM 参考,引用文件中的可配置寄存器(例如 MCONFIG[SKEW] = 0、MCONFIG[HKEEP] = 0b11、MCONFIG[MSTENA] = 0b11),但似乎不起作用。我该如何解决这个问题? #FRDM-MCXN947 #I3C 通信与控制(I3C | I2C | SPI | FlexCAN | 以太网 | FlexIO) MCX N Re: When using the FRDM-MCXN947's I3C interface for I2C communication, the Clk stretching capability 嗨@kevin_Jhuang 寄存器设置目前在 I3C_MasterInit() 之前应用,因此可能会被 SDK 初始化覆盖。 请启用: masterConfig->disableTimeout = true; 然后在 I3C_MasterInit() 之后配置 MSTENA = 3、HKEEP = 3 和 SKEW = 0。请先清除相应的寄存器字段,然后再写入数据,不要使用 |=。 初始化完成后,请读取 MCONFIG 以验证设置是否仍然有效。同时提供时钟拉伸故障后立即捕获的 MSTATUS 和 MERRWARN 值。 请确认 SCL 和 SDA 是否配置为开漏工作状态,以及是否安装了外部上拉电阻。 BR 哈里 Re: When using the FRDM-MCXN947's I3C interface for I2C communication, the Clk stretching capability 嗨,哈里: 非常感谢您的回复。为了测试,我再次尝试设置 MCONFIG。 1.在测试中,disableTimeout 设置为 true。 2. 该图像显示了当前的寄存器设置,包括 MCONFIG、MSTATUS 和 MERRWARN 的值,以及 I2C 总线信号。(配置 A 和配置 B 的区别在于 MSTENA 的设置:配置 A:MCONFIG[MSTENA] = 3,配置 B:MCONFIG[MSTENA] = 1)。 3. 按照示例,应将 SDA/SCL IO 引脚设置为 openDrainEnable = kPORT_OpenDrainDisable,并连接上拉电阻(4.7K)。应该在场。 目前看来,I2C总线扩展功能似乎无法实现。 Re: When using the FRDM-MCXN947's I3C interface for I2C communication, the Clk stretching capability 根据以上回复,配置B图 谢谢 Re: When using the FRDM-MCXN947's I3C interface for I2C communication, the Clk stretching capability 嗨@kevin_Jhuang 我能重现这个问题,并将继续调查。一旦有任何发现,我会立即通知您。 BR 哈里 Re: When using the FRDM-MCXN947's I3C interface for I2C communication, the Clk stretching capability 嗨@kevin_Jhuang 我已与内部团队核实了这个问题。根据他们的测试,当使用 MSTENA = 11b(I2C 控制器模式)时,还应满足以下条件: PPBAUD = 0 I2CBAUD < 15 BR 哈里
View full article
一个让我感到惊喜的流媒体服务 这些年来我尝试过好几种流媒体服务,但要找到一个始终保持稳定的服务比想象中要难得多。 最近我试用了NexusIPTV ,整体体验让我非常满意。流媒体播放质量很好,频道加载速度很快,而且在我测试过的所有设备上都能流畅运行。 对于 美国、英国和加拿大 的人们来说 ,或许值得将这项服务添加到比较列表中。 我在这里详细描述了我的经历: 👉 我的完整经历
View full article
Solution to FRDM-A-S32K144 and FRDM-A-S32K144N not detected during initial USB-C connection Overview The FRDM-A-S32K144 and FRDM-A-S32K144N boards ship with a factory-programmed demonstration application that showcases USB Power Delivery functionality through an RGB LED example. Under certain USB-C host and cable combinations, the factory application may prevent the on-board OpenSDA/K20 debugger from completing its initialization sequence and becoming available to the host system. When this occurs, the board may appear unresponsive and cannot be programmed through the standard OpenSDA interface. This article describes how to identify the condition and provides a simple one-time recovery procedure. This behavior is limited to the following boards: FRDM-A-S32K144 FRDM-A-S32K144N No other FRDM boards are affected. Symptoms The behavior is typically observed during the initial programming session while the factory application is still present. During the first use of the board, users may observe the following: The board is connected using a USB-C to USB-C cable. The operating system does not detect the board. No OpenSDA programming interface appears. Debugging and programming tools cannot establish communication. The OpenSDA/K20 status LED (D4) remains OFF. Although the board may not be detected by the host computer, the factory application may continue running on the target MCU. FRDM-A-S32K144 OpenSDA/K20 debugger status LED (D4) not working as expectedFRDM-A-S32K144 OpenSDA/K20 debugger status LED (D4) not working as expected     Issue The factory image included on the affected boards performs USB Power Delivery negotiation during startup. On certain USB-C host configurations, this initialization sequence may prevent the on-board OpenSDA/K20 debugger from reaching its operational state. As a result, the debugger does not enumerate on the host PC and programming access is not available. Once the factory image is replaced with a user application, the startup sequence changes and the OpenSDA/K20 debugger initializes normally. Workaround Materials required FRDM-A-S32K144 or FRDM-A-S32K144N board USB-A to USB-C data cable Host computer with an available USB port S32 Design Studio IDE 3.6.5 or above Any valid S32K144 application image If the board is not detected through a USB-C to USB-C connection during the initial programming session: Disconnect the board from the host PC Reconnect the board using a USB-A to USB-C cable Verify that the D4 LED is illuminated solid orange Program in S32 Design Studio any valid application to the S32K144 MCU, such as: S32K144 GPIO LED Blink example Any S32K144 Application Code Hub demonstration project Any S32K144 custom user application Wait for the programming operation to complete successfully The newly programmed application replaces the factory image and restores normal debugger operation.   Expected operation Once the workaround described above is applied successfully, the board LED D4 is illuminated with a solid orange light, and the device manager operating system detects the board as a COM port and a PEMicro OpenSDA Debug Driver. FRDM-A-S32K144 OpenSDA/K20 debugger status LED (D4) working as expectedFRDM-A-S32K144 OpenSDA/K20 debugger status LED (D4) working as expected FRDM-A-S32K144 correctly detected by Windows device managerFRDM-A-S32K144 correctly detected by Windows device manager After a successful programming session: USB-C to USB-C cables can be used normally. Debugging functions operate as expected. Programming functions operate as expected. No additional configuration is required. The recovery process only needs to be performed once. Subsequent application updates can be performed using either USB-C to USB-C or USB-A to USB-C connections (if no PD is needed). Troubleshooting checklist If D4 is OFF, the OpenSDA/K20 debugger has not completed initialization. Check the next list before applying the turnaround again:  Verify that D4 is solid orange. Confirm the USB cable supports data transfer. Check that the operating system detects the OpenSDA device. Reprogram the board using a USB-A to USB-C connection. Test with an alternative USB port or host PC. Choose another project application to flash. If D4 is still OFF, the OpenSDA/K20 debugger may be damaged or present another error. Please review the S32K Knowledge Base or the FRDM community for more information. Any support, information, and technology (“Materials”) provided by NXP are provided AS IS, without any warranty express or implied, and NXP disclaims all direct and indirect liability and damages in connection with the Material to the maximum extent permitted by the applicable law. NXP accepts no liability for any assistance with applications or product design. Materials may only be used in connection with NXP products. Any feedback provided to NXP regarding the Materials may be used by NXP without restriction. If your FRDM-A-S32K144 or FRDM-A-S32K144N is not detected during its first USB-C connection, this article explains the cause, how to verify OpenSDA/K20 status, and the steps to quickly enable normal operation.
View full article
CWH-CTP-BASE-HE 的 TX/RX 指示灯一直亮着红色——没有 USB 枚举或以太网连接 你好, 我最近购买了一台 CodeWarrior TAP CWH-CTP-BASE-HE,但我无法让它正常工作。 当前状况: TX/RX LED 指示灯持续保持红色常亮。 通过 USB 连接或断开 TAP 设备时,Windows 设备管理器中没有任何设备出现。 我尝试过不同的USB数据线和不同的USB接口。 我还将以太网端口连接到一台正常工作的交换机/路由器,同时通过 USB 连接供电。 以太网连接指示灯不亮。 目前未连接目标处理器、目标板或探针尖端。 我的设备似乎没有外部重置按钮。 根据 CodeWarrior TAP 文档,我了解到,当 TAP 成功启动时,TX/RX LED 指示灯通常会从红色变为闪烁的橙色,然后变为闪烁的绿色。我的这只眼睛始终保持纯红色。 请问您能否提供以下建议: TX/RX LED 指示灯常亮红色是否意味着 TAP 引导加载程序或操作系统无法正常启动? 即使以太网连接指示灯也不亮,这会不会是由于缺少 USB 驱动程序造成的? 如果 USB 和以太网通信都不可用,CWH-CTP-BASE-HE 是否有任何恢复模式或引导加载程序模式? 是否有可用于恢复 TAP 固件的内部 JTAG 或编程连接器? NXP 是否提供恢复固件映像或恢复工具? 在认定设备故障之前,我是否还需要执行其他诊断程序? 如有需要,我可以提供硬件版本、序列号、设备照片和PCB照片。 谢谢! Re: CWH-CTP-BASE-HE stuck at solid red TX/RX LED – no USB enumeration or Ethernet link 它与Windows 11兼容吗?我已经安装到Win11系统中,但仍然和以前一样,没有在设备管理器中显示。 Re: CWH-CTP-BASE-HE stuck at solid red TX/RX LED – no USB enumeration or Ethernet link 请下载附件中的 ccs.zip 文件,并从中安装 CCS USB 驱动程序。 C:\Users\nxa22585\Downloads\260821\ccs\ccs\ccs\drivers\usb\x64 安装驱动程序时请不要插入 CodeWarrior TAP。 然后插入 CodeWarrior TAP,并在设备管理器中检查是否可以找到与附件类似的 CodeWarrior TAP 信息。 Re: CWH-CTP-BASE-HE stuck at solid red TX/RX LED – no USB enumeration or Ethernet link 是的,它与Windows 11兼容。 您的 CodeWarrior TAP 似乎有问题,您可以退回此 CodeWarrior TAP,并通过以下链接更换一个新的。 https://www.nxp.com/support/sample-and-buy/how-to-buy-from-nxp/dev-tool-warranty-return-request-form:WTB_DTD_WARRANTY
View full article
PE微编程问题 嘿,恩智浦 我正在使用一个 S32K344 EVB定制板 PEmicro Multilink Universe FX Rev-D 10 针 JTAG/SWD 调试探针 和 S32 设计工作室 (S32DS) 版本 3.6.8 。 我想将一个应用程序刷入到 正常内部程序闪存 S32K344。 我没有使用 HSE 安全启动、安全调试或任何其他不在我们范围内且我们的调试要求不需要的安全功能。 目前我在调试时遇到了附件中的问题,您的及时指导将有助于我在所需字段中解决此问题。 请问谁能提供以下详细步骤: 将 PEmicro 10 针 JTAG/SWD 调试器连接到 10 针 - S32K344 定制 EVB。 在 S32DS 3.6.8 中创建正确的调试/运行配置。 选择合适的接口(SWD 或 JTAG)。 配置闪存编程设置(擦除、编程、验证)。 设置正确的目标设备和连接模式。 标准内部闪存编程所需的任何链接器或内存配置。 为避免安全调试/HSE相关问题,建议进行以下设置。 如果调试器检测到设备但在闪存编程过程中失败,请执行以下故障排除步骤。 我正在寻找使用 PEmicro 探针成功对 S32K344 EVB 进行编程和调试所需的完整烧录程序和确切的 S32DS 配置。 Re: PE Micro Programming Issue 你好@sharathkumar2026 , 您看到的错误(PEmicro“安全调试”警告)并不一定意味着 HSE 固件处于活动状态。也可以完全通过 UTEST OTP 启用安全调试,只需将调试密码编程到 0x1B000080 并推进生命周期状态即可——无需任何 HSE 固件参与。我猜你也没有这样做过,但还是值得一提。 此外,当 MCU 在调试器初始连接握手期间意外复位时,此错误可能会表现为误报。能不能请你: 在调试器断开连接的情况下,用示波器或逻辑分析仪监测 RESET_B 引脚——它是在切换还是保持低电平? 确认电路板在发生故障之前是否工作正常,或者这是否是一块从未成功编程过的新电路板。 与我们联系有多少块板处于这种状态——是仅限于一个单元,还是多块板受到影响? 关于 PEmicro 算法的说明 PEmicro 调试器使用专有的闪存算法,因此内部错误代码的确切含义没有公开文档。我还建议您直接联系PEmicro 技术支持。 1 & 2. S32DS 使用 PEmicro GDB 服务器插件。完整的插件文档请点击此处查看: S32DS 使用 PEmicro GDB 服务器插件。完整的插件文档请点击此处查看: 适用于基于 Eclipse 的 IDE 的 PEmicro GDB 服务器 NXP知识库文章: 操作指南:使用 GDB PEmicro (S32DS 3.x) 构建项目并设置调试 如何:在 S32 Design Studio 中构建项目并设置调试配置以进行调试 3. 两种接口均适用于 S32K344。 4. 这些设置由 PEmicro 闪存算法自动处理。 5. 只需在调试配置中选择衍生产品即可。 6. S32K344 的任何 RTD(实时驱动程序)示例项目都包含一个可直接使用的链接器文件和针对内部闪存的内存配置。 7. 如果您的设备上未安装 HSE 固件,请确保在 PEmicro 调试器设置中选择 hse_disabled 闪存算法变体。 danielmartynek_0-1788161026086.png 8. 请检查以下内容: 上电复位后,RESET_B 信号是否稳定,还是会波动?闪存操作过程中意外重启可能是根本原因。 运行过程中电源是否清洁稳定? 上电复位后,之前编程的应用程序能否正常运行,还是设备会出现卡顿或反复 RESET 的情况? 您能否使用另一根 PEmicro 探针(或者其他供应商的探针,例如 J-Link 的探针)来排除探针本身的问题? 所有电路板都出现同样的故障,还是仅限于一个电路板? 此致, 丹尼尔
View full article
PN7220 Android 16 Porting to i.MX95 FRDM EVK Board Introduction Many customers are using PN7220 + Android 16 recently. In this document, I will show you how to porting the PN7220 to Android 16. I use the i.MX95 FRDM board as a reference target board. NOTE :  All the modifications are just for reference. They are NOT a NXP official patches for the newer release of AOSP porting. So the modifications may not be the best solution. Customer please base on their needs to modify the AOSP source code. This is not for production. Customer still need to perform full testing after the porting.  Hardware boards: i.MX95 FRDM Board (FRDM i.MX 95 Development Board | NXP Semiconductors) PN7220 EVK -- PNEV7220BP1 (PNEV7220BP1 Development Board for PN7220 NFC Controller | NXP Semiconductors) There is a 40pins connector on both PN7220 EVK and i.MX95 FRDM board. So PN7220 + i.MX95 FRDM connecting together is like this: Build the Android BSP for i.MX95 FRDM board: The i.MX Android BSP that I used is Android 16.0.0_1.4.0 (L6.12.49_2.2.0 BSP). It could be downloaded from here: Android OS for i.MX Applications Processors | NXP Semiconductors 1. Download the "Documentation" and the "Install Source Package".  2. Follow the steps in Android User's Guide to build the Android BSP for "evk_95" first.  $ export MY_ANDROID=`pwd` $ source build/envsetup.sh $ lunch evk_95-nxp_stable-userdebug $ export TARGET_RELEASE=nxp_stable $ build_build_var_cache $ ./imx-make.sh -j4 2>&1 | tee build-log.txt According to the android_build/.repo/manifests/aosp-android-16.0.0_1.4.0.xml, you will see the AOSP version is android-16.0.0_r4. According to the PN7220 Android 16 porting guide (PN7160/PN7220 – Android 16 porting guide), the patches is for AOSP release android-16.0.0_r2. So fortunately, the AOSP release version between them is not big different.  Now, we start the porting: 1. Kernel Driver To establish connection with the PN7220, the Android stack uses the nxpnfc kernel driver.  You could download the driver from github below: nfcandroid_platform_drivers/drivers at br_ar_16_comm_infra_dev · nxp-nfc-infra/nfcandroid_platform_drivers · GitHub The command is : git clone "https://github.com/nxp-nfc-infra/nfcandroid_platform_drivers.git" -b br_ar_16_comm_infra_dev There is driver for Kernel 6.6 and 6.12. So, please download the correct one for your porting. For example, the kernel in i.MX Android BSP Android 16.0.0_1.4.0 is 6.12. So I will use the 6.12 driver for my porting. In your porting, make sure the PATH in Makefile and Kconfig files are setting properly.  For example in my porting: android_build/vendor/nxp-opensource/kernel_imx/drivers/nfc/pn7220$ tree . ├── common.c ├── common.h ├── i2c_drv.c ├── i2c_drv.h ├── Kbuild ├── Kconfig └── Makefile 0 directories, 7 files For simplifying everything, we will only add a support for I2C and not SPI. Replace drivers/nfc/pn7220/Makefile default code with following code (for easier understanding) nxpnfc-i2c-objs = i2c_drv.o common.o obj-$(CONFIG_NXP_NFC_I2C) += nxpnfc_i2c.o The contents of drivers/nfc/Makefile. Add the PN7220 like below: # SPDX-License-Identifier: GPL-2.0 # # Makefile for nfc devices # obj-$(CONFIG_NXP_NFC_I2C) += pn7220/ obj-$(CONFIG_NFC_FDP) += fdp/ obj-$(CONFIG_NFC_PN544) += pn544/ obj-$(CONFIG_NFC_MICROREAD) += microread/ obj-$(CONFIG_NFC_PN533) += pn533/ obj-$(CONFIG_NFC_MEI_PHY) += mei_phy.o obj-$(CONFIG_NFC_SIM) += nfcsim.o obj-$(CONFIG_NFC_PORT100) += port100.o obj-$(CONFIG_NFC_MRVL) += nfcmrvl/ obj-$(CONFIG_NFC_TRF7970A) += trf7970a.o obj-$(CONFIG_NFC_ST21NFCA) += st21nfca/ obj-$(CONFIG_NFC_ST_NCI) += st-nci/ obj-$(CONFIG_NFC_NXP_NCI) += nxp-nci/ obj-$(CONFIG_NFC_S3FWRN5) += s3fwrn5/ obj-$(CONFIG_NFC_ST95HF) += st95hf/ obj-$(CONFIG_NFC_VIRTUAL_NCI) += virtual_ncidev.o The contents of drivers/nfc/Kconfig. Add the PN7220 like below: source "drivers/nfc/microread/Kconfig" source "drivers/nfc/nfcmrvl/Kconfig" source "drivers/nfc/st21nfca/Kconfig" source "drivers/nfc/st-nci/Kconfig" source "drivers/nfc/nxp-nci/Kconfig" source "drivers/nfc/s3fwrn5/Kconfig" source "drivers/nfc/st95hf/Kconfig" source "drivers/nfc/pn7220/Kconfig" endmenu 2. Adding the "nxpnfc" to the i.MX95 FRDM board device tree file android_build/vendor/nxp-opensource/kernel_imx/arch/arm64/boot/dts/freescale/imx95-15x15-frdm.dts We need to check the connection between two boards and then to decide which pins to use in the device tree file. Here is the 40 pins connector on the PN7220: Here is the 40 pins connector on the i.MX95 FRDM board. According to the 40 pins connection between PN7220 EVK and the i.MX95 FRDM board, I decided to use the I2C6 and the GPIO2_20, GPIO2_21 and GPIO2_26. So, in the imx95-15x15-frdm.dts, I added: &lpi2c6 { clock-frequency = <400000>; pinctrl-names = "default"; pinctrl-0 = <&pinctrl_lpi2c6>; status = "okay"; nxpnfc@28{ compatible = "nxp,nxpnfc"; reg = <0x28>; pinctrl-names = "default"; pinctrl-0 = <&pinctrl_nfc>; nxp,nxpnfc-irq = <&gpio2 26 0>; nxp,nxpnfc-ven = <&gpio2 21 0>; nxp,nxpnfc-mode_sw = <&gpio2 20 0>; }; }; And the IOMUX settings in the imx95-15x15-frdm.dts. pinctrl_nfc: nfcgrp { fsl,pins = < IMX95_PAD_GPIO_IO26__GPIO2_IO_BIT26 0x39e // IRQ IMX95_PAD_GPIO_IO21__GPIO2_IO_BIT21 0x39e // VEN IMX95_PAD_GPIO_IO20__GPIO2_IO_BIT20 0x39e // MODE_SW >; }; pinctrl_lpi2c6: lpi2c6grp { fsl,pins = < IMX95_PAD_GPIO_IO02__LPI2C6_SDA 0x40000b9e IMX95_PAD_GPIO_IO03__LPI2C6_SCL 0x40000b9e >; }; 3. Modify the imx95_gki.fragment File:  android_build/vendor/nxp-opensource/kernel_imx/arch/arm64/configs/imx95_gki.fragment Add the "CONFIG_NXP_NFC_I2C=m" into the imx95_gki.fragment 4. Add the settings in your corresponding board configuration files in Android - Go to the android_build/device/nxp/imx9/evk_95/  - Modify the BoardConfig.mk. # Add KVM support BOARD_BOOTCONFIG += androidboot.hypervisor.vm.supported=true + # ---- selinux permissive ---- + BOARD_KERNEL_CMDLINE += androidboot.selinux=permissive # -------@block_sepolicy------- BOARD_SEPOLICY_DIRS := \ $(CONFIG_REPO_PATH)/imx9/sepolicy \ $(IMX_DEVICE_PATH)/sepolicy \ + vendor/nxp/nfc/sepolicy \ + vendor/nxp/nfc/sepolicy/nfc \ + vendor/nxp/emvco/sepolicy +include vendor/nxp/nfc/BoardConfigNfc.mk  - Add the "nxpnfc_i2c.ko" to the ShareBoardConfig.mk. Make sure the path and the filename are correct. ifeq ($(LOADABLE_KERNEL_MODULE),true) IMX_ANDROID_FIRST_STAGE_MODULES += \ $(KERNEL_OUT)/drivers/hwmon/hwmon.ko \ $(KERNEL_OUT)/drivers/hwmon/scmi-hwmon.ko \ .... .... .... $(KERNEL_OUT)/drivers/soc/imx/soc-imx9.ko \ $(KERNEL_OUT)/drivers/gpio/gpio-adp5585.ko \ $(KERNEL_OUT)/drivers/gpio/gpio-pca953x.ko \ $(KERNEL_OUT)/drivers/gpio/gpio-vf610.ko \ + $(KERNEL_OUT)/drivers/nfc/pn7220/nxpnfc_i2c.ko .... .... BOARD_VENDOR_KERNEL_MODULES += \ $(KERNEL_OUT)/drivers/media/i2c/ap1302.ko \ $(KERNEL_OUT)/drivers/media/i2c/ox03c10.ko \ $(KERNEL_OUT)/drivers/media/i2c/max96717_lib.ko \ .... .... $(KERNEL_OUT)/drivers/net/ethernet/freescale/enetc/fsl-enetc-vf.ko \ $(KERNEL_OUT)/drivers/net/ethernet/freescale/enetc/fsl-enetc4.ko \ $(KERNEL_OUT)/drivers/net/phy/realtek.ko \ $(KERNEL_OUT)/drivers/hwmon/pwm-fan.ko \ + $(KERNEL_OUT)/drivers/nfc/pn7220/nxpnfc_i2c.ko - Add the INxpNfc and INxpEmvco to the device_framework_matrix.xml nxp.hardware.secureime 1 ISecureIME default nxp.hardware.ele 1 ISecureEnclave default nxp.hardware.imx_dek_extractor 1 IDek_Extractor default vendor.nxp.nxpnfc_aidl 2 INxpNfc default vendor.nxp.emvco 1 INxpEmvco default  - Add the following to the evk_95.mk # ------nfc------- $(call inherit-product, vendor/nxp/nfc/device-nfc.mk) $(call inherit-product, vendor/nxp/emvco/device-emvco.mk) PRODUCT_PACKAGES += \ android.hardware.nfc2-service.nxp PRODUCT_PACKAGES += \ com.nxp.emvco \ com.nxp.nfc \ nfc_nci_nxp_pn72xx - Add the nxpnfc_i2c in init.rc exec u:r:vendor_modprobe:s0 -- /vendor/bin/modprobe -a -d \ /vendor/lib/modules nxpnfc_i2c write /sys/power/wake_lock nosleep - Add nxpnfc to ueventd.nxp.rc /dev/ttymxc1 0666 nfc nfc /dev/ttymxc2 0666 nfc nfc /dev/nxpnfc 0666 nfc nfc 5. Apply the NXP AOSP patches I write a script to download the patches from the github. The script file and the android_build folder is on the same directory. Run the AOSP_adaptation.sh.  AOSP_adaptation.sh # nfcandroid_nfc_modules git clone "https://github.com/nxp-nfc-infra/nfcandroid_modules_nfc.git" cd nfcandroid_modules_nfc git checkout br_ar_16_comm_infra_dev cp -rf * ../android_build/packages/modules/Nfc cd .. # nfcandroid_nfc_hidlimpl git clone "https://github.com/nxp-nfc-infra/nfcandroid_nfc_hidlimpl.git" cd nfcandroid_nfc_hidlimpl git checkout br_ar_16_comm_infra_dev cp -rf * ../android_build/hardware/nxp/nfc cd .. # nfcandroid_frameworks git clone "https://github.com/nxp-nfc-infra/nfcandroid_frameworks.git" cd nfcandroid_frameworks git checkout br_ar_16_comm_infra_dev mkdir ../android_build/packages/modules/Nfc/framework cp -rf * ../android_build/packages/modules/Nfc/framework cd .. # nfcandroid_emvco_aidlimpl git clone "https://github.com/nxp-nfc-infra/nfcandroid_emvco_aidlimpl.git" cd nfcandroid_emvco_aidlimpl git checkout br_ar_16_comm_infra_dev mkdir ../android_build/hardware/nxp/emvco cp -rf * ../android_build/hardware/nxp/emvco cd .. # nfcandroid_platform_reference git clone "https://github.com/nxp-nfc-infra/nfcandroid_platform_reference.git" cd nfcandroid_platform_reference git checkout br_ar_16_comm_infra_dev cp -rf vendor/nxp/* ../android_build/vendor/nxp/ cd .. Apply a patch. $ cd android_build/system/logging $ patch -p1 < ../../../nfcandroid_platform_reference/build_cfg/build_pf_patches/AROOT_system_logging.patch Add TDA Test support: # Clone repositories for test applications and TDA support # nfcandroid_infra_test_apps git clone https://github.com/nxp-nfc-infra/nfcandroid_infra_test_apps.git cd nfcandroid_infra_test_apps/ git checkout br_ar_16_comm_infra_dev cd test_apps/ cp -rf SMCU_Switch/ ../../android_build/packages/apps/ cp -rf EMVCoModeSwitchApp/ ../../android_build/packages/apps/ cd ../.. # nfcandroid_infra_comm_libs git clone "https://github.com/nxp-nfc-infra/nfcandroid_infra_comm_libs.git" cd nfcandroid_infra_comm_libs git checkout br_ar_16_comm_infra_dev cp -rf nfc_tda/ ../android_build/packages/modules/Nfc/libnfc-nci/ cp -rf emvco_tda/ emvco_tda_test/ ../android_build/hardware/nxp/emvco/ cp -rf NfcTdaTestApp/ ../android_build/packages/apps/ cd .. 6. Put changes into hardwatre/interfaces/compatibility_matrices  File: hardware/interfaces/compatibility_matrices/compatibility_matrix.202504.xml android.hardware.audio.effect 1-3 IFactory default nxp.hardware.imx_dek_extractor 1 IDek_Extractor default nxp.hardware.ele 1 ISecureEnclave default vendor.nxp.nxpnfc_aidl 2 INxpNfc default vendor.nxp.emvco 1 INxpEmvco default android.hardware.authsecret 1 IAuthSecret default 7. Add the firmware $ git clone https://github.com/NXP/nfc-NXPNFCC_FW.git $ cp -r nfc-NXPNFCC_FW/InfraFW/pn7220/64-bit-2.5/pn7220_64bits.so android_build/vendor/nxp/pn7220/firmware/lib64/libpn72xx_fw.so 8. Add the NXPAndroidDTA $git clone https://github.com/NXPNFCProject/NXPAndroidDTA.git $cd NXPAndroidDTA $git checkout br_ar_new_dta_arch cp -r NXPAndroidDTA android_build/vendor/nxp/ 9. Some fixes before build: $ cd android_build $ mv hardware/nxp/nfc/snxxx/Android.bp hardware/nxp/nfc/snxxx/_Android.bp $ mv hardware/nxp/nfc/snxxx/halimpl/power-tracker/Android.bp hardware/nxp/nfc/snxxx/halimpl/power-tracker/_Android.bp $ mv hardware/nxp/secure_element/snxxx/aidl/Android.bp hardware/nxp/secure_element/snxxx/aidl/_Android.bp $ cd hardware/nxp/nfc $ rm pn8x -rf Now, build the Android BSP again. Use "mm" to build the Android source code. After fixed all the errors of the AOSP build, use "imx-make.sh" to build the whole i.MX Android image.  When building the Android, there may have some errors during the build. I listed some errors and the workaround below for your reference. Error: error: packages/modules/Nfc/tests/cts/tests/Android.bp:20:1: "CtsNfcTestCases" depends on undefined module "CtsAppTestStubsShared". Workaround : Comment out "CtsAppTestStubsShared" in packages/modules/Nfc/tests/cts/tests/Android.bp Error: error: hardware/nxp/nfc/snxxx/halimpl_v2/power-tracker/Android.bp:17:1: "power_tracker_v2" depends on undefined module "nfc_nci_nxp_snxxx_headers_v2". Workaround: mv hardware/nxp/nfc/snxxx/halimpl_v2/power-tracker/Android.bp hardware/nxp/nfc/snxxx/halimpl_v2/power-tracker/_Android.bp Error: error: platform_testing/Android.bp:255:1: module "continuous_native_tests" variant "android_common": depends on //packages/modules/Nfc/NfcNci/nci/jni:libnfc-nci-jni-tests which is not visible to this module You may need to add "//platform_testing" to its visibility error: platform_testing/Android.bp:255:1: module "continuous_native_tests" variant "android_common": depends on //packages/modules/Nfc/libnfc-nci/tests:libnfc-nci-tests which is not visible to this module You may need to add "//platform_testing" to its visibility Workaround: nano packages/modules/Nfc/NfcNci/nci/jni/Android.bp In cc_test {     name: "libnfc-nci-jni-tests", .. ..     visibility: [         "//platform_testing:__subpackages__",     ], Same in packages/modules/Nfc/libnfc-nci/tests/Android.bp Error: FAILED: out/soong/.intermediates/packages/modules/Nfc/framework/framework-nfc.stubs.source.system/android_common/exportable/framework-nfc.stubs.source.system-stubs.srcjar out/soong/.intermediates/packages/modules/Nfc/framework/framework-nfc.stubs.source.system/android_common/exportable/framework-nfc.stubs.source.system_annotations.zip out/soong/.intermediates/packages/modules/Nfc/framework/framework-nfc.stubs.source.system/android_common/exportable/framework-nfc.stubs.source.system_api.txt out/soong/.intermediates/packages/modules/Nfc/framework/framework-nfc.stubs.source.system/android_common/exportable/framework-nfc.stubs.source.system_removed.txt out/soong/.intermediates/prebuilts/sdk/framework-nfc.api.system.latest/gen/framework-nfc.api.system.latest:52: error: Binary breaking change: Removed method android.nfc.NfcOemExtension.emulateNfcTechnologyATag(boolean,byte,byte,byte,byte[],byte,byte[]) [RemovedMethod] out/soong/.intermediates/prebuilts/sdk/framework-nfc.api.system.latest/gen/framework-nfc.api.system.latest:64: error: Binary breaking change: Removed method android.nfc.NfcOemExtension.overwriteRoutingTable(int,int,int,int,int) [RemovedMethod] out/soong/.intermediates/prebuilts/sdk/framework-nfc.api.system.latest/gen/framework-nfc.api.system.latest:77: error: Binary breaking change: Removed field android.nfc.NfcOemExtension.EMULATE_NFC_A_TAG_STATUS_FAILED_INTERNAL [RemovedField] out/soong/.intermediates/prebuilts/sdk/framework-nfc.api.system.latest/gen/framework-nfc.api.system.latest:78: error: Binary breaking change: Removed field android.nfc.NfcOemExtension.EMULATE_NFC_A_TAG_STATUS_FAILED_NFC_NOT_ENABLED [RemovedField] out/soong/.intermediates/prebuilts/sdk/framework-nfc.api.system.latest/gen/framework-nfc.api.system.latest:79: error: Binary breaking change: Removed field android.nfc.NfcOemExtension.EMULATE_NFC_A_TAG_STATUS_OK [RemovedField] out/soong/.intermediates/prebuilts/sdk/framework-nfc.api.system.latest/gen/framework-nfc.api.system.latest:120: error: Binary breaking change: Removed method android.nfc.NfcOemExtension.Callback.onRoutingChangeCompleted() [RemovedMethod] out/soong/.intermediates/prebuilts/sdk/framework-nfc.api.system.latest/gen/framework-nfc.api.system.latest:160: error: Binary breaking change: Removed method android.nfc.RoutingStatus.getDefaultFelicaRoute() [RemovedMethod] Aborting: Found compatibility problems checking the public API (/home/nxa08017/android16_1.4.0/android_build/out/soong/.temp/sbox/d1717a17fe92a8b2da806db0f1cb87830019487b/packages/modules/Nfc/framework/java) against the API in /home/nxa08017/android16_1.4.0/android_build/out/soong/.temp/sbox/d1717a17fe92a8b2da806db0f1cb87830019487b/./out/soong/.intermediates/prebuilts/sdk/framework-nfc.api.public.latest/gen/framework-nfc.api.public.latest exit status 255 Workaround: Comment out the lines 52,64,77,78,79,120,160 in out/soong/.intermediates/prebuilts/sdk/framework-nfc.api.system.latest/gen/framework-nfc.api.system.latest Error: out/soong/.intermediates/prebuilts/sdk/framework-nfc.api.public.latest/gen/framework-nfc.api.public.latest:77: error: Binary breaking change: Removed method android.nfc.NfcAdapter.isExitFramesSupported() [RemovedMethod] out/soong/.intermediates/prebuilts/sdk/framework-nfc.api.public.latest/gen/framework-nfc.api.public.latest:80: error: Binary breaking change: Removed method android.nfc.NfcAdapter.isPowerSavingModeEnabled() [RemovedMethod] out/soong/.intermediates/prebuilts/sdk/framework-nfc.api.public.latest/gen/framework-nfc.api.public.latest:81: error: Binary breaking change: Removed method android.nfc.NfcAdapter.isPowerSavingModeSupported() [RemovedMethod] out/soong/.intermediates/prebuilts/sdk/framework-nfc.api.public.latest/gen/framework-nfc.api.public.latest:91: error: Binary breaking change: Removed method android.nfc.NfcAdapter.setPowerSavingMode(boolean) [RemovedMethod] out/soong/.intermediates/prebuilts/sdk/framework-nfc.api.public.latest/gen/framework-nfc.api.public.latest:196: error: Binary breaking change: Removed method android.nfc.cardemulation.CardEmulation.getPollingLoopFiltersForService(android.content.ComponentName) [RemovedMethod] out/soong/.intermediates/prebuilts/sdk/framework-nfc.api.public.latest/gen/framework-nfc.api.public.latest:197: error: Binary breaking change: Removed method android.nfc.cardemulation.CardEmulation.getPollingLoopPatternFiltersForService(android.content.ComponentName) [RemovedMethod] out/soong/.intermediates/prebuilts/sdk/framework-nfc.api.public.latest/gen/framework-nfc.api.public.latest:202: error: Binary breaking change: Removed method android.nfc.cardemulation.CardEmulation.isDeviceScreenOnRequiredForService(android.content.ComponentName) [RemovedMethod] out/soong/.intermediates/prebuilts/sdk/framework-nfc.api.public.latest/gen/framework-nfc.api.public.latest:203: error: Binary breaking change: Removed method android.nfc.cardemulation.CardEmulation.isDeviceUnlockRequiredForService(android.content.ComponentName) [RemovedMethod] out/soong/.intermediates/prebuilts/sdk/framework-nfc.api.public.latest/gen/framework-nfc.api.public.latest:214: error: Binary breaking change: Removed method android.nfc.cardemulation.CardEmulation.setRequireDeviceScreenOnForService(android.content.ComponentName,boolean) [RemovedMethod] out/soong/.intermediates/prebuilts/sdk/framework-nfc.api.public.latest/gen/framework-nfc.api.public.latest:215: error: Binary breaking change: Removed method android.nfc.cardemulation.CardEmulation.setRequireDeviceUnlockForService(android.content.ComponentName,boolean) [RemovedMethod] out/soong/.intermediates/prebuilts/sdk/framework-nfc.api.public.latest/gen/framework-nfc.api.public.latest:248: error: Binary breaking change: Removed method android.nfc.cardemulation.CardEmulation.NfcEventCallback.onOffHostAidSelected(String,String) [RemovedMethod] Aborting: Found compatibility problems checking the public API (/home/nxa08017/android16_1.4.0/android_build/out/soong/.temp/sbox/6245059c063e0ae76fa4356a9b840b923ddb8764/packages/modules/Nfc/framework/java) against the API in /home/nxa08017/android16_1.4.0/android_build/out/soong/.temp/sbox/6245059c063e0ae76fa4356a9b840b923ddb8764/./out/soong/.intermediates/prebuilts/sdk/framework-nfc.api.public.latest/gen/framework-nfc.api.public.latest exit status 255 Workaround: Same as the previous workaround. Comment out the lines (line number shown in error) in out/soong/.intermediates/prebuilts/sdk/framework-nfc.api.public.latest/gen/framework-nfc.api.public.latest. Error: FAILED: out/soong/.intermediates/system/sepolicy/vendor_sepolicy.cil.raw/android_common/evk_95/vendor_sepolicy.cil.raw out/host/linux-x86/bin/checkpolicy -C -M -L -c 30 -o out/soong/.intermediates/system/sepolicy/vendor_sepolicy.cil.raw/android_common/evk_95/vendor_sepolicy.cil.raw out/soong/.intermediates/system/sepolicy/vendor_sepolicy.conf/android_common/evk_95/vendor_sepolicy.conf && out/host/linux-x86/bin/build_sepolicy filter_out -f out/soong/.intermediates/system/sepolicy/reqd_policy_mask.cil/android_common/reqd_policy_mask.cil -t out/soong/.intermediates/system/sepolicy/vendor_sepolicy.cil.raw/android_common/evk_95/vendor_sepolicy.cil.raw # hash of input list: 7a5f97fdfa590e2ec5a2c6b745c65293680d0202c9b5869c1425905c209b9bf1 vendor/nxp/emvco/sepolicy/service.te:1:ERROR 'Duplicate declaration of type' at token ';' on line 21764: type hal_emvco_service, hal_service_type, service_manager_type; #line 1 "vendor/nxp/emvco/sepolicy/service.te" checkpolicy:  error(s) encountered while parsing configuration 11:50:27 ninja failed with: exit status 1 Workaround: nano vendor/nxp/emvco/sepolicy/hwservice.te Change the hal_emvco_service to hal_emvco_hwservice like this: type hal_emvco_hwservice, hwservice_manager_type; nano vendor/nxp/emvco/sepolicy/hwservice_contexts vendor.nxp.emvco::INxpEmvco                             u:object_r:hal_emvco_hwservice:s0 nano vendor/nxp/emvco/sepolicy/hal_emvco_default.te + allow hal_emvco_default hal_emvco_hwservice:hwservice_manager { add find }; Error: FAILED: out/soong/.intermediates/hardware/nxp/nfc/intf/nxpnfc/aidl/vendor.nxp.nxpnfc_aidl_interface/checkhash_2.timestamp if [ $(cd 'hardware/nxp/nfc/intf/nxpnfc/aidl/aidl_api/vendor.nxp.nxpnfc_aidl/2' && { find ./ -name "*.aidl" -print0 | LC_ALL=C sort -z | xargs -0 sha1sum && echo 1; } | sha1sum | cut -d " " -f 1) = $(tail -1 'hardware/nxp/nfc/intf/nxpnfc/aidl/aidl_api/vendor.nxp.nxpnfc_aidl/2/.hash') ]; then touch out/soong/.intermediates/hardware/nxp/nfc/intf/nxpnfc/aidl/vendor.nxp.nxpnfc_aidl_interface/checkhash_2.timestamp; else cat 'system/tools/aidl/build/message_check_integrity.txt' && exit 1; fi ############################################################################### # ERROR: Modification detected of stable AIDL API file                        # ############################################################################### Above AIDL file(s) has changed, resulting in a different hash. Hash values may be checked at runtime to verify interface stability. If a device is shipped with this change by ignoring this message, it has a high risk of breaking later when a module using the interface is updated, e.g., Mainline modules. Workaround: echo $(cd 'hardware/nxp/nfc/intf/nxpnfc/aidl/aidl_api/vendor.nxp.nxpnfc_aidl/2' && { find ./ -name "*.aidl" -print0 | LC_ALL=C sort -z | xargs -0 sha1sum && echo 1; } | sha1sum | cut -d " " -f 1) d9e99a62ff5ebed44083a79577ec7ed32d264775 Then,  nano hardware/nxp/nfc/intf/nxpnfc/aidl/aidl_api/vendor.nxp.nxpnfc_aidl/2/.hash replace the value to d9e99a62ff5ebed44083a79577ec7ed32d264775 A runtime error: Problem: You will find the following failed about the permission in the log. java.lang.IllegalStateException: Signature|privileged permissions not in privileged permission allowlist: {com.android.nfc (/apex/com.android.nfcservices/priv-app/[email protected]😞 android.permission.OBSERVE_ROLE_HOLDERS} Workaround: Add :                 To the file : out/target/product/evk_95/system/etc/permissions/privapp-permissions-platform.xml 10. Download the image to the target board: - We use the tool UUU to download the image to the i.MX boards. Download the UUU from here : Releases · nxp-imx/mfgtools - Download the Android 16 BSP i.MX95 EVK demo image from the Android i.MX BSP web page first. There are UUU script and necessary image files already in the demo image package.  - Put the UUU executable file into the demo image folder. uuu_imx_android_flash.bat is the script also in the same folder. - After your Android BSP building is completed and succeed, copy the images to the demo image folder. The image files are located in android_build/out/target/product/evk_95/. - Switch the boot mode to "Download" mode on the i.MX95 FRDM board. - Run the UUU script to download the images to the FRDM board. uuu_imx_android_flash.bat -f imx95 -a -e -u 15x15-frdm -d 15x15-frdm Run the "TagInfo" on the board: - Download the TagInfo apk file from the NXP TagInfo App web page . - Use the "adb install" command to install the TagInfo to the FRDM board. C:\>adb install com.nxp.taginfo-6.2.0-play-release-protected.apk * daemon not running; starting now at tcp:5037 * daemon started successfully Performing Streamed Install Success After TagInfo installed, the TagInfo icon will be available on the GUI. Run the TagInfo, and then put a card on the board. The information of the card will be show on the TagInfo App. Reference: PN7160/PN7220 – Android 16 porting guide PN7220 NFC Frontend IC with Integrated Power Management | NXP Semiconductors Android OS for i.MX Applications Processors | NXP Semiconductors nxp-nfc-infra · GitHub
View full article
EdgeLock SE050/SE051 Capability Inquiry for Ed25519/X25519-Based IoT Device Hello NXP Team, We are evaluating the EdgeLock SE050/SE051 family for a Raspberry Pi based IoT device and would appreciate guidance on the most suitable part number. Our primary requirements are secure storage and hardware execution of cryptographic operations. The device is a Raspberry Pi 4 - running Raspberry Pi OS (Linux). We would like clarification on the following points: 1. Key Storage       - Can the SE050/SE051 securely store non-exportable private keys?    - Can certificates and public keys be stored in the secure element? 2. Key Generation       - Can the secure element generate key pairs internally?    - Specifically, does it support generation of Ed25519 and X25519 key pairs within the secure element? 3. Ed25519 Operations       - Can Ed25519 signing and signature verification be supported inside the secure element? 4. X25519 Operations       - Can X25519 key agreement (ECDH shared secret computation) be performed inside the secure element using a non-exportable private key? 5. AES Operations       - Does the secure element support AES encryption and decryption operations?    - If so, which AES modes are supported?   6. Storage read/write    - Storing/removing/accessing files like wifi passwords? 7. Linux / Raspberry Pi Integration       - Is there an SDK or middleware available for Raspberry Pi OS?    - Are there example applications demonstrating the above operations? 8. Product Selection       - Which EdgeLock SE050/SE051 variant would you recommend for the above requirements?    - What are the major differences between the recommended variants?    - Are there any newer EdgeLock products that would be a better fit for these requirements? Our intended use case is: - Ed25519 signing for device authentication / JWT generation - X25519 key agreement for mobile-device provisioning - AES encryption/decryption using derived session keys - Storage and handling of security files like Wifi passwords etc - Large-scale deployment of IoT devices If available, we would also appreciate links to any of these: - Relevant datasheets - Application notes - SDK documentation - Evaluation boards - Linux/Raspberry Pi examples Thank you for your assistance. Best regards, Sahil Pai Re: EdgeLock SE050/SE051 Capability Inquiry for Ed25519/X25519-Based IoT Device Hi @SahilPai , Please kindly have my comments as below: 1. Key Storage       - Can the SE050/SE051 securely store non-exportable private keys? //Yes, private keys are non-exportable on SE05x.    - Can certificates and public keys be stored in the secure element? // Yes, certs are stored as binary files within the SE , and public key can be stored standalone or together with the private key in SE05x. 2. Key Generation       - Can the secure element generate key pairs internally?// Yes, it supports.    - Specifically, does it support generation of Ed25519 and X25519 key pairs within the secure element?// Yes, Ed25519 and X25519 key pairs are supported. 3. Ed25519 Operations       - Can Ed25519 signing and signature verification be supported inside the secure element?// Yes, Ed25519 signing and signature verification are supported inside the SE05x. 4. X25519 Operations       - Can X25519 key agreement (ECDH shared secret computation) be performed inside the secure element using a non-exportable private key? //Yes, ECDH is performed with a private key within SE05x and an external  public key which can be stored in SE05x as well. 5. AES Operations       - Does the secure element support AES encryption and decryption operations? //Yes,    - If so, which AES modes are supported?// Support for AES Modes:CBC, ECB, CTR, GCM, CCM.   6. Storage read/write    - Storing/removing/accessing files like wifi passwords?//Yes, SE050/SE051 can store binary objects in its secure object store, including Wi-Fi credentials. 7. Linux / Raspberry Pi Integration       - Is there an SDK or middleware available for Raspberry Pi OS?// Yes, please refer to https://www.nxp.com/webapp/Download?colCode=SE05x-PLUG-TRUST-MW&appType=license for details.    - Are there example applications demonstrating the above operations?//Yes. 8. Product Selection       - Which EdgeLock SE050/SE051 variant would you recommend for the above requirements?// Either SE050E2 or SE051C2 can be used.    - What are the major differences between the recommended variants?// They both have the latest applet version, but SE051 supports applet upgrade while SE050 doesn't.    - Are there any newer EdgeLock products that would be a better fit for these requirements?//not yet so far.   Please kindly refer to https://www.nxp.com/products/SE050 and https://www.nxp.com/products/SE051 for more details.   Hope that helps,   Have a great day, Kan ------------------------------------------------------------------------------- Note: - If this post answers your question, please click the "Mark Correct" button. Thank you! - We are following threads for 7 weeks after the last post, later replies are ignored Please open a new thread and refer to the closed one, if you have a related question at a later point in time. -------------------------------------------------------------------------------
View full article
S32K311チップ用のModbusプロトコルの参考例はありますか? Re: 有没有S32K311芯片 modbus协议的参考例程 こんにちは、 @Finnc 私の投稿をこちらでご覧ください。 https://community.nxp.com/t5/S32K/Modbus-RTU/mp/2184516/highlight/true#M53445 よろしくお願いいたします。 ルーカス
View full article
How to use the HCI_bb on Kinetis family products and get access to the DTM mode This article is presenting 2 parts:    Part1: How to flash the HCI_bb binary into the Kinetis product (here is the example of the KW38).    Part 2: Perform RF measurements using the R&S CMW270  2 attached files:    - bci_black_box.bin (zip file)    - mbed_WinSerial.exe (zip file) Part1: How to flash the HCI_bb binary into the Kinetis product (here is the example of the KW38). The HCI_bb application example is on the SDK folder below: Plug the FRDM-KW38 board on your PC using the USB cable. The FRDM-KW38 board will be seeing as a hard disk. Disk 😧 in this example. Select the hci_black_box_frdmkw38.bin file and drag and drop this file to the FRDM-KW38 (D:) The KW38 is flashed when 100% is reached. The FRDM-KW38 board is ready to be used with the DTM mode. Part 2: Perform RF measurements using the R&S CMW270  The FRDM-KW38 board could be connected to the R&S CMW270 using the USB cable. The hci_bb set the KW38 in DTM mode. The CMW270 could communicate by sending DTM commands. Note: You need to install the mbedWinSerial driver (attached in this article) in the CMW270 to detect the FRDM-KW38 board. Re: How to use the HCI_bb on Kinetis family products and get access to the DTM mode I am trying to doing this DTM test on KW36(specific application hardware, not a development board) ,can you please help or share the entire process as well as firmware & list of tools required to perform this test?
View full article
How to Disable Mass Erase on the FRDM-A-S32K344 have created two applications for the FRDM-A-S32K344. One application is located at address 0x00400000, and the other is located at address 0x00500000. When I flash one of the applications using the onboard debugger, it performs a mass erase and removes the other application as well. How can I disable mass erase and configure the debugger to erase only a specific flash region or section during programming? Re: How to Disable Mass Erase on the FRDM-A-S32K344 Hello, OK, So you are able to load both binaries at once successfully. But, you didn't mention that you will use bootloader. What you actually want Reset → Bootloader runs → wait for SW2 → jump to App   When using Launch Group in S32DS, each debug configuration loads its ELF and the last one determines the current PC. Therefore, the application entry point overrides the bootloader, causing it to be skipped. To ensure correct bootloader execution, use a single debug configuration that loads both images but starts execution from the bootloader reset vector. Also disable “Run to main” to avoid skipping startup code. After a real reset the S32K3 always starts execution from the predefined boot address (internal flash at 0x00400000), and the first valid image (typically your bootloader) is executed. However, during debugging with S32DS, this behavior can be overridden by the debugger, which may set the program counter to the application entry point after loading ELF files, effectively bypassing the bootloader. Best regards, Peter Re: How to Disable Mass Erase on the FRDM-A-S32K344 Hello, Thank you for the suggestion. I created a Launch Group and added both the Bootloader and Application ELF debug configurations. However, when I start the debug session, it appears that only the application code is running, and the bootloader execution is being bypassed. My requirement is for the bootloader to execute first after reset and then jump to the application only when SW2 is pressed. Could you please advise if there are any additional Launch Group settings or debugger configurations required to ensure the bootloader runs before the application? I am using on board debugger in FRDM-A-S32K344 Re: How to Disable Mass Erase on the FRDM-A-S32K344 Hello, In Debug Configurations, you can create a Launch Group and simply add all the ELF files you want to load. This lets you load multiple images (e.g. bootloader + application) in one go. Best regards, Peter Re: How to Disable Mass Erase on the FRDM-A-S32K344 Hello Can you explain how to configure S32DS so that both ELF files are loaded, but the PC is set to the bootloader Reset_Handler at 0x00400000 instead of the application entry point?  Re: How to Disable Mass Erase on the FRDM-A-S32K344 Hi,  can you please check in Memory Browser (during Debug session) if the memory space from 0x00400000 is empty (has been erased by PE Micro) or there is only rewritten entry point?  The multiple .elf files are typically used with multicore MCUs. With single core it may be little bit tricky. One usable way is to have two debug session - in first one use the bootloader .elf file and second one with app, but you need to define which memory space should be preserved. PE Micro always performs mass erase, the preserve memory simply reads data from the preserved memory space, performs mass erase, write back the preserved data and write data from second .elf file.  Other possibility is use s-record tool ( https://srecord.sourceforge.net/ ) , from both .elf files create s-record and merge both s-records with this tool and use merged .srec instead of .elf. You can still use .elf files for debug and symbols. 
View full article
Debug application started by the MCUBOOT Dear Everyone, the board we use is IMXRT1176. I would like to debug my application which is started by mcuboot. I would like the debugger to flash a signed application and debug it afterwards. Let me show you what i did: 1. Original build produced me an app.elf 2. I converted an app.elf to app.bin and singed it with imgtool to create app_signed.bin 3. I used arm-none-eabi-objcopy to wrap app_signed.bin into app_signed.bin.elf 4. I used this lanuch.json configuration ``` { "type": "mcuxpresso-debug", "name": "Debug bootloader app", "request": "launch", "cwd": "${workspaceFolder}", "executable": " /app.elf", "isAttach": false, "probeType": "LinkServer", "stopAtSymbol": "main", "skipBuildBeforeDebug": true, "extraSymbolFiles": [     " /app.elf",     " /bootloader.elf", ], "postLaunchCommands": [     "load /app_signed.bin.elf 0x30100000" ], "gdbInitCommands": [    "set remotetimeout 600",     "set debug-file-directory",     "set non-stop off", ], "gdbServerConfigs": {     "linkserver": {          "device": "MIMXRT1176xxxxx:MIMXRT1170-EVKB",          "core": "cm7", }, "segger": {}, "pemicro": {} }, }, ``` It seems to work, meaning i can debug both bootloader and app, but it feels like a hack. What I don't like the most is that flash is written twice. Once for executable where we write unsigned binary and one for load where we write signed binary (which has the same core code obviously). Could you please tell me if i missed something obvious? Do you think there is a cleaner way to achieve that. Just as an info, I know how to attach to already flashed image, the process above is more about convenience to start debugging in one step, I mention this to express what my goal is. Thanks a lot in advance for any help and suggestions! Best Regards, Jakub Re: Debug application started by the MCUBOOT Hello @jslota13245, There are currently no defined steps that combine flashing and debugging a signed image into a single workflow, as these are typically handled as separate processes. In general, you would first flash the signed image onto the device and then attach the debugger afterwards. As a reference, you may find it helpful to review the "Running the demo" section of the ota_mcuboot_basic example, which demonstrates two different approaches for flashing a signed image that could be adapted to your setup. Additionally, the "Transferring data" to the flash memory section provides an overview of the available tools that can be used for the flashing process. On the other hand, could you please clarify the reason for converting the signed image into a .bin.elf file? Also, could you confirm if you followed a guide for this process? BR Habib Re: Debug application started by the MCUBOOT Hello Habib! thank you for the reply. To answer your question. I followed this guide for flashing multiple binaries at the start-up. We use mcuxpresso for vs-code instead of IDE but the premise should be the same: https://mcuoneclipse.com/2022/11/01/loading-multiple-binary-files-with-gdb/ The idea here is that the elf file has information to debug a signed binary, as signed binary is just a binary with header and trailer attached. If the .elf file was generated with this layout in mind it should work as intended.  For future reference, approach i suggested in my original post doesn't work too well as debugger gets stuck on non-existing 0x00000 breakpoints while the CPU is still running so i suspect no real crash has occurred. There is clearly some configuration/integration debugger problem here but I can't point exactly where. Did you encounter such behaviour by any chance? As for your suggested approach, I found this section: ``` programing signed application image to the primary application partition using an external tool (direct method) jump-starting the application by debugger, performing an image update with the signed image, resetting the board and letting the bootloader to perform the update (indirect method) The latter method is used in the following step-by-step description: Open the demo project and build it. Known issue: MDK linker issues warning about unused boot_hdr sections. This does not affect the functionality of the example. Prepare signed image of the application from raw binary as described in the readme of mcuboot_opensource SDK example. In case of MCUXpresso raw binary may not be generated automatically. Use binary tools after right clicking Binaries/.axf file in the project tree to generate it manually. Launch the debugger in your IDE to jump-start the application. In case of MCUXpresso IDE the execution stalls in an endless loop in the bootloader. Pause the debugging and use debugger console and issue command jump ResetISR.  ``` But I'm a bit lost on what do i need to do with the extension for VS-code - I don't have ide backend unfortunately. Could you please help me by answering the questions below? Let's assume i do have a signed binary and original elf file with symbols.  1. How can debugger kick start signed image? 2. How can debugger kick start it without flashing it first? The point 1 explicitly states to flash it with some tool - i assume point 2 does something else?.  3. The debugger can't flash just base elf file as it'll be discarded by the mcuboot as it doesn't have mcuboot header and a trailer. 4. When point 2.3 states 'Launch the debugger in your IDE to jump-start the application' - does it mean the debugger flashes something? Or does it attach to already flashed image? Thanks in advance for your help and time 🙂 Best Regards, Jakub Re: Debug application started by the MCUBOOT Hello @jslota13245, When you mention "I don't have ide backend unfortunately" I understand this may refer to limited familiarity with the MCUXpresso extension for VS Code, is my understanding correct? If so, I recommend reviewing the chapter "Explore Extension" in the official documentation for the extension, as it provides a helpful overview of its features. Regarding your questions, when you start a debug session, the tool by default programs the generated image into flash and then attaches the debugger, which automatically jump to the main function. this is described in the "starting a debug sesion" section, inside this page you will find more information about the functionality of the debug in the extension.  I can also, suggest you review the chapter "debug a project" which shows the steps to debug your code. I highly recommend first validating and debugging your application without MCUboot or image signing and only introducing MCUboot once your application is fully tested. For make this process we strongly recommend using MCUxpresso Secure Provisioning Tool, which has the capabilities to manage security features such as key generation and image signing for MCUboot, which is why this is standard tool to handle applications just like this one. You can find more information about how sign image and flash your MCUboot in the chapter 7.6.2 " Steps to start MCUboot with such a processor manually"of the Secure Provisioning Tool User Guide 26.03. On the other hand, when integrating MCUboot, ensure that it is placed in a dedicated flash region that is not overwritten by other images, the mcuboot_opensource_cm7 example offers an alternative of how place each image:   | Region         | From       | To         | Size   | |----------------|------------|------------|--------| | MCUboot code   | 0x30000000 | 0x3003FFFF | 256kB  | | Primary slot   | 0x30040000 | 0x3023FFFF | 2048kB | | Secondary slot | 0x30240000 | 0x3043FFFF | 2048kB | You should first program the MCUboot image into its dedicated flash region, and then place the signed application image into the primary or secondary slot. The MCUXpresso Secure Provisioning Tool can facilitate this process by handling both, program the bootloader and program the image within a single workflow, as described in section 7.6.2 of the user guide I previously shared. BR Habib Re: Debug application started by the MCUBOOT I will read about about it. Thanks a lot! 🙂 Re: Debug application started by the MCUBOOT Some comments regarding the debug configuration from your first post: 1. MCUXpresso for VS Code extension relies on "runners.yaml" from Zephyr (or MCUXpresso SDK). Usually, there could be separate values for ELF/BIN files. In your case, you should probably have the "bin_file" property pointing to your "app_signed.bin" (see screenshot below). Important note: if ELF & BIN are pointing to the same file (e.g. "app", but file extensions differ), there's the "executableLoadTypePriority" property inside the debug configuration that controls what is actually loaded on target. 2. If you have the "runners.yaml" file defined as described above, you will not need to specify anything in the MCUXpresso debug configuration (see screenshot below). 3. If you have the "runners" file defined as described above, the ELF file from "runners" will be used by the extension for loading debug symbols only and the BIN file to load app on target. As a result, no "postLaunchCommands" property needed. 4. The "bootloader.elf" must still be added in the "extraLoadFiles" property, but you won't need "app.elf" alongside. If the "runners.yaml" is not defined as above, you can have something like: "executable": {   "elf": ".../app.elf",   "binary": {    "path": ".../app_signed.elf",    "address": 256   } } The two approaches should have similar outcome. Re: Debug application started by the MCUBOOT Hi Adrian, Sounds very promising 🙂 I'll give it a try, thank you very much - for both sharing details about the extension and for your suggestions! Best Regards, Jakub
View full article
VOL for I2C lines at IOL 3mA Hello, This is Arumugam. May I know the VOL max voltage to consider for I2C lines. Should I consider as 0.7V @1mA or 3mA Thanks Arumugam Re: VOL for I2C lines at IOL 3mA Hi @Arumugam1982  The VOL/VOH levels for the I2C lines depend on the pad supply rail and the corresponding electrical specification of the selected pin configuration. The LPI2C pads can be supplied from either VDD_HV_A or VDD_HV_B, depending on the pin muxing and pad assignment, so this should be verified using the device IOMUX information. The datasheet defines the input thresholds (VIH/VIL) directly in the GPIO DC electrical characteristics tables. However, VOH/VOL are usually defined indirectly through the output drive current conditions, such as IOH and IOL. In practice, the recommended approach is to rely on the VOH/VOL conditions linked to the corresponding IOH/IOL parameters for the selected pad configuration, rather than assuming a specific current value (mA). A specific current should only be used if it is explicitly defined in the datasheet for that electrical characteristic. BR, VaneB Re: VOL for I2C lines at IOL 3mA Should I consider the same VOL for IOL -1mA /3mA /8mA. I need this number for my WCA calculation. Re: VOL for I2C lines at IOL 3mA Hello, Which Symbol are you using in the data sheet from Table 27 (ex. IOL_33_S)? Regards, John
View full article
RT1180-EVK上でVS Codeを使用してFreeRTOSをデバッグする evkmimxrt1180_freertos_message_buffers_secondary_core サンプルプロジェクトにおける FreeRTOS の設定は以下のとおりです。 #define configMAX_PRIORITIES 56年 #define configUSE_PORT_OPTIMISED_TASK_SELECTION 0 アプリケーションは通常IDE(MCUXpresso IDE)でデバッグ可能です。しかし、VS Codeでデバッグを行う場合、FreeRTOSがスケジューラを開始した後にデバッガーが終了してしまう。 デバッグセッションは、vTaskStartScheduler() 内の次のコードに実行が到達した時点で終了します。 xNextTaskUnblockTime = portMAX_DELAY; xSchedulerRunning = pdTRUE; xTickCount = ( TickType_t ) configINITIAL_TICK_COUNT; これらの変数が初期化された後、最初のタスクがスケジュールされる前に、デバッガーは切断され、デバッグセッションが終了します。 IDEとVS Codeでテストして解決策を見つけるのを手伝ってもらえますか? MCX C Re: FreeRTOS Debugging in VS Code on RT1180-EVK こんにちは@yanyanwangさん Domainsフォルダでプロジェクトをビルディングした後、このフォルダにはプライマリコアアプリケーションとセカンダリコアアプリケーションの両方が見つかるはずです。 両方の.elfの再生ボタンをクリックするとファイルごとにデバッグセッションが開始されますか? プライマリコアがMCMGR_StartCore関数を通過するまで実行した場合、セカンダリコアのデバッグセッションを一時停止できますか? よろしくお願いします、 パブロ Re: FreeRTOS Debugging in VS Code on RT1180-EVK こんにちは、 セカンダリコアでデバッグセッションを正常に開始でき、FreeRTOSスケジューラが始まる前にすべて正常に動作します。 しかし、FreeRTOSがタスクのスケジューリングを開始すると(vTaskStartScheduler()が呼び出された後)、デバッガはすぐに切断され、デバッグセッションが終了します。 この問題の原因を特定するのを手伝ってもらえますか?確認すべき推奨デバッガー設定やFreeRTOSの設定があれば教えてください。 よろしくお願いします。 よろしくお願いいたします。 ヤンヤン Re: FreeRTOS Debugging in VS Code on RT1180-EVK ハイ 以下の質問に答えてもらえますか? プロジェクトはどのようにインポートしましたか? プロジェクトの設定を何か変更しましたか? 外部デバッガーを使用していますか? よろしくお願いします、 パブロ
View full article
MCXN547 - 运行时从IFR(CMPA)加载以太网MAC地址的最佳方法是什么? 你好 我们正在基于 MCXN547 芯片并采用 Zephyr RTOS 4.3.0 开发一款产品。作为出厂配置流程的一部分,我们使用 MCUXpresso 安全配置工具将每单位唯一的 EUI64 编程到 IFR 的 CMPA 区域(地址为 “0x01004190”)。从这个 EUI64 中,我们得出了 6 字节的以太网 MAC 地址。 我们希望以太网驱动程序在启动时自动使用这个 MAC 地址,而不是设备树中的静态 “本地 mac 地址”。 我们已验证,位于 `0x01004190` 的 CMPA 区域可在运行时通过内存映射访问直接读取(`devmem` 已确认这一点)。 我们的问题是:有什么推荐的方法,可以让 `nxp,enet-qos-mac` 驱动程序(MCXN547 使用的)在启动时从 IFR/CMPA 中的自定义位置读取 MAC 地址? 我们了解到,经典的 `nxp,enet-mac` 驱动程序支持 `nvmem-cells` 功能,但我们不确定 `nxp,enet-qos-mac` 驱动程序是否也支持或能够实现此功能,以及 MCXN547 的正确设备树配置应如何设置。 如果能得到恩智浦(NXP)或社区的任何指导或示例,我们将不胜感激。 运行环境: - MCU:MCXN547 - Zephyr:4.3.0(恩智浦分支 nxp-v4.3.0) -驱动程序:`驱动程序/以太网/eth_nxp_enet_qos/eth_nxp_enet_qos/eth_nxp_enet_qos_mac.c`-IDE:VS Code + mcuxPresso 扩展程序-配置:M CUXpresso 安全配置工具 MCX N Re: MCXN547 - Best approach to load Ethernet MAC address from IFR (CMPA) at runtime? 如果你愿意尝试其他方案,可以试试内置 TCP/IP 协议栈的 Mongoose。Mongoose 允许您将 MG_SET_MAC_ADDRESS 重新定义为您自己的自定义函数。 尝试一下, 1. 在项目配置中禁用 Zephyr TCP/IP 2. 创建 mongoose/ 目录,并将 mongoose.c 文件复制到该目录。和 mongoose.h来自https://github.com/cesanta/mongoose 3. 创建 mongoose_config.h 文件由此: #实用主义 // 请参阅https://mongoose.ws/documentation/#build-options #define MG_ARCH MG_ARCH_ARMGCC #define MG_OTA MG_OTA_MCXN #define MG_ENABLE_TCPIP 1 #define MG_ENABLE_DRIVER_MCXN 1 #define MG_ENABLE_CUSTOM_MILLIS 1 // extern void my_function(unsigned char *mac); // #define MG_SET_MAC_ADDRESS(mac) my_function(mac) 4. 实现“uint64_t mg_millis(void)”函数,返回自启动以来经过的毫秒数。 创建一个运行 mongoose 的 Zephyr 任务,并为其分配 8kb 的堆栈空间: struct mg_mgr mgr; mg_mgr_init(&mgr); for (;;) mg_mgr_poll(&mgr, 1); 就到此为止吧。将 printf 重定向到 UART 以查看调试日志。此外,Mongoose 还内置了支持 CRA 的 OTA 更新功能, https://mongoose.ws/ota/ 有一个针对略有不同的MCU的版本测试项目, https://github.com/cesanta/mongoose/tree/master/tutorials/nxp/frdm-mcxn947-make-baremetal-builtin- 关闭 mongoose 仓库,然后在该目录中输入“make”进行构建,这需要安装 make 和 ARM GCC。 Re: MCXN547 - Best approach to load Ethernet MAC address from IFR (CMPA) at runtime? 嗨@Jorini 谢谢你的帖子! 您可以按照 Zephyr 文档中的说明,选择在运行时更改 MAC 地址: MAC 地址配置 — Zephyr 项目文档 请告诉我这些信息是否有帮助! Re: MCXN547 - Best approach to load Ethernet MAC address from IFR (CMPA) at runtime? 谢谢你们两位的建议! 关于 mac_config.html 方法:我们研究过,并认为这是 Zephyr 实现此功能的“简洁”方法。但是,这需要修改 eth_nxp_enet_qos_mac.c 以调用 net_eth_mac_load(),向 nxp,enet-qos-mac 绑定添加 nvmem-cells 支持,并为 CMPA/IFR 区域提供 nvmem 提供程序——这些在 Zephyr 4.3 的 MCXN547 中都不存在。所以,虽然这是正确的长期方向,但今天并不直接适用。 关于 Mongoose:对于从零开始的新项目来说,这是一个有趣的选择,但就我们而言,这意味着要替换整个 Zephyr 网络协议栈并重写我们所有的网络代码(DHCP、TLS、HTTP、OTA、基于套接字的云通信)。鉴于我们已经有了可行的解决方案,这个成本并不合理。 我们最终采用的方案(在生产环境中运行良好)是在应用程序代码中使用两个 SYS_INIT 钩子,而无需对驱动程序进行任何更改: 1. POST_KERNEL 优先级 83:在驱动程序以优先级 82 初始化后立即覆盖 ENET QoS 硬件寄存器(MAC_ADDRESS0_HIGH/LOW,地址为 0x40100300/304)。这样可以确保 MAC 芯片过滤掉地址正确的帧。 2. 应用程序优先级 1:更新 Zephyr 软件网络接口表(net_if link_addr)。如果没有这第二步,Zephyr 的 IP 协议栈会默默地丢弃所有传入的帧,因为软件 MAC 地址与硬件 MAC 地址不匹配。 感谢您
View full article
请问guider的table控件怎样在guider软件里调整每个单元格的宽度? 我在使用table控件时,在guider界面没找到调整每个单元格的宽度的按钮或输入框。请问应该怎样在设计时调整单元格宽度? Re: 请问guider的table控件怎样在guider软件里调整每个单元格的宽度? Hi @alen-liao  您好,您可以尝试修改这个参数。 BR Harry
View full article
HDMI Brightness Control on i.MX8M Mini (AOSP 16) Hi NXP Team, I am working on an i.MX8M Mini platform running AOSP 16 and using HDMI as the primary display output. Platform: i.MX8M Mini OS: AOSP 16 Display Output: HDMI Use Case: Control the brightness level of an HDMI connected LCD display on i.MX8M Mini running AOSP 16. Could you please clarify: Is HDMI brightness control supported on i.MX8M Mini? If yes, what is the recommended implementation. If not, what is the suggested workaround for Android brightness control with an HDMI display? I would like to understand the correct and supported method for implementing display brightness control for HDMI output on this platform. Thank you. Android i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Re: HDMI Brightness Control on i.MX8M Mini (AOSP 16) Hi @vp1, Are you using an EVK board? Which DSI-to-HDMI bridge are you currently using? If you are using an HDMI monitor, please note that controlling brightness via HDMI is not typically supported, as brightness control is not commonly handled through HDMI signaling. Could you provide more details about your current setup and configuration? Best regards, Chavira Re: HDMI Brightness Control on i.MX8M Mini (AOSP 16) hi @Chavira  Thanks for response  Yes, we are using the i.MX8M Mini EVK. Our setup consists of a Waveshare LCD connected through a MIPI-DSI to HDMI adapter card. The display is therefore being driven over an HDMI interface rather than through a direct MIPI-DSI connection. Could you please confirm if brightness control is supported when using a MIPI-DSI to HDMI bridge, or if this limitation is due to the HDMI interface itself? Thanks. Vikas P
View full article
MCUXpresso for VSCODE 无法从资源库导入示例 安装环境: 从资源库导入示例: 发生错误: 无法运行注入命令:west build-b kw47loc-p always 😧 /file/kw47/sdk/kw47_25_12_00/kw47_00/kw47_loc/mcuxsdk/examples/cmsis_driver_examples/lpi2c/int_B2B_Transfer/master-d 为什么会这样?如何解决? Re: MCUXpresso for VSCODE cannot Import Example from Repository 问题已解决。这就是电脑被加密的原因。因此,某些文件无法被某些 .exe 文件读取文件。 
View full article
Is there mismatch between eIQ guideline? I see these guideline to convert tflite to npu tflite model.  The first guideline: https://docs.nxp.com/bundle/AN14700/page/topics/model_conversion_for_npu.html It is interactive guideline. In this guideline, NXP said that we need to choose right MCUXpresso SDK version. It seems that this guideline is for eIQ Toolkit 1.17.0.110 Ubuntu 20.04.03 Installer. Is that right? The second guideline: https://docs.nxp.com/bundle/AN14700/page/topics/eiq_enablement.html It uses command line neutron-converter --input mobilenet_quant.tflite --output mobilenet_npu.tflite --dump-header-file-input --dump-header-file-output --target imxrt700 --use-sequencer I downloaded eIQ Neutron SDK 3.1.2 (Linux package) and I could run the about command to create npu_tflite model. But in this case, it did not mention about compatible MCUXpresso SDK version. It makes me confused. An I am not sure whether I can used the created npu model in example of MCUXpresso SDK without knowing version. Do you have any comment on this problem? Re: Is there mismatch between eIQ guideline?  @anthony_huereca Could you help me in this case? I ask in the Wednesday, and maybe you missed this post. Thank you. Re: Is there mismatch between eIQ guideline? The Neutron Converter enablement has been reorganized since that app note was written. The latest Neutron Converter can now be found in latest eIQ Neutron SDK. Also inside the eIQ Neutron SDK is the Neutron libraries to use in your project. See this post for details: https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs-Knowledge/How-to-Update-eIQ-Projects-with-the-Latest-eIQ-Neutron-SDK/ta-p/2270833?lightbox-message-images-2270833=382154i8450392E2394C882 If you use a model converted with the 3.1.2 Neutron Converter then you'll get an mismatch error if you try to run it with the MCUXpresso SDK 26.03. However you can easily update the MCUXpresso SDK 26.03 projects to use the 3.1.2 Neutron libraries to get it to work. You can also follow the latest eIQ NPU MCU labs (RT700 and MCX N) which go through this process.  The app note is already in the process of being updated to reflect the new enablement flow.  Re: Is there mismatch between eIQ guideline? Hi. Thank you. I got your points. I will refer the documentation that you send me.
View full article
[S32DS 3.6.7] S32K1xx RTD 3.0.0 not detected when creating new project Hello everyone, I am having issues with S32 Design Studio 3.6.7 and the S32K1xx RTD Drivers version 3.0.0. Current setup: S32 Design Studio version: 3.6.7 Device: S32K1xx family RTD Drivers version: 3.0.0 OS: Windows 11 The RTD does not appear in the SDK selection when creating a new project. Has anyone experienced the same issue or found a solution? Thank you very much for your support. Antonio Re: [S32DS 3.6.7] S32K1xx RTD 3.0.0 not detected when creating new project Hi Julián, You were correct — the issue was that S32DS comes with GCC 11. I installed GCC 10.2, and everything is working properly now. Thank you for your help. Re: [S32DS 3.6.7] S32K1xx RTD 3.0.0 not detected when creating new project Hi @antonio_esal, When installing the RTD packages, have you made sure the correct NXP GCC version has been installed? Out of the box, S32DS 3.6.0 and up comes with NXP GCC 11.4, however, S32K1 RTD 3.0.0 has been built and tested with NXP GCC 10.2 (As noted in the release notes): When creating a new S32DS application, make sure the correct toolchain is selected: If this is not the root cause of your issue, please share your installation details (Help > Installation Details) so I can confirm all of the required dependencies for S32K1 RTD are installed. Best regards, Julián
View full article
RW612 Nonsecure Flash Setting Breaks Reset Functionality Hello, I'm experiencing a weird bug with ARM TF-M and Zephyr (NXP downstream v4.3.0) on the FRDM-RW612.  I want to use a region of my flash chip for a nonsecure LittleFS filesystem.  I followed the NXP guide for adding a NS region (link) and I can successfully use the region for my filesystem, no problems with the Zephyr/FS API or access issues. My problem is that when I have the CONFIG_FLASH KConfig option enabled, I can no longer reset my board.  Calling tfm_platform_system_reset(), NVIC_SystemReset(), or even pressing the physical reset button all lock up the processor and do not actually reset the board anymore. I stepped through with a debugger and the last line executed before the debugger is detached/broken away from is core_cm33.h:2683 (within __NVIC_SystemReset): SCB->AIRCR = (uint32_t)((0x5FAUL << SCB_AIRCR_VECTKEY_Pos) | (SCB->AIRCR & SCB_AIRCR_PRIGROUP_Msk) | SCB_AIRCR_SYSRESETREQ_Msk ); If I attach a debugger after the reset occurs, GDB says the program at address 0x20005840 forever. I've tried the same thing on a very basic program, even adding CONFIG_FLASH to the zephyr hello world program causes resets to fail in the same way. Any help is appreciated, thank you! Re: RW612 Nonsecure Flash Setting Breaks Reset Functionality Hi @jm-streametric, hope you are doing well. In order to help me better analyze this behavior, would you please confirm if in the tests that you have done with the hello world example, the only setting that you add is the CONFIG_FLASH? Or are you also enabling your added NS region with the setting created from the guide (CONFIG_TFM_CUSTOM_DATA_IMPORT_REGION=y)? I have tried to run the hello world example from Zephyr (v4.3.0 downstream) only adding the CONFIG_FLASH setting and I am able to reset the board. Re: RW612 Nonsecure Flash Setting Breaks Reset Functionality Hello Jake, thank you for the clarification. The difference between RW610 and RW612 is that RW610 does not support 802.15.4 protocol, therefore there is no difference with the flexspi peripheral. Would you please confirm if you are using the FRDM-RW612 files to test these features? Or have you done your own directory for your board in Zephyr? Also, are you able to run the examples properly without the reset functionality? Or is the MCU going to hardfault at a certain point? Re: RW612 Nonsecure Flash Setting Breaks Reset Functionality Hi Roman, I made an error on the post when specifying the board, I am using a custom board with the RW610 but the flash configuration is exactly the same as the FRDM-RW612. I can get the development board to reset even with CONFIG_FLASH=y, but my custom board has the issue described in my post. Even with the TF-M and Zephyr repos set to FRDM-RW612 defaults, I get the problem of being unable to reset the board when CONFIG_FLASH=y (with and without the custom data regions). Is there a difference between the RW610 and RW612 that could cause flash/flexspi problems? Or do you think it may be another problem with my board? Re: RW612 Nonsecure Flash Setting Breaks Reset Functionality Hi Jake, thank you for the information. So, when you add the "CONFIG_FLASH=y" setting to any project, you are able to run the application normally, except when you try to do any type of reset, which leads your program to be in an infinite loop at address 0x20005840, is my understanding correct? Would you please check the Reset status Register (SYS_RST_STATUS) to check if the reset cause is being registered? Additionally, have you done all your tests with the non-secure version of the board? If you have a FRDM-RW612 board, could you please perform some tests on it and let me know whether this behavior is present or not, with the same configs you are adding to test with your custom board? Re: RW612 Nonsecure Flash Setting Breaks Reset Functionality Hi Roman, I am using the unmodified FRDM-RW612 files to test my board for the flash features since my board uses the same flash IC. I have different peripherals on my board which I have overlays for, but I'm not applying those overlays for this flash test case. The flash does work, I can access the flash data within my custom region just fine. When I access flash outside of the custom region I get a fault, which is expected. The only thing that doesn't work is that trying to reset the board either physically or with tfm_platform_system_reset() locks the board up as described above. Thank you Re: RW612 Nonsecure Flash Setting Breaks Reset Functionality Hi Roman, So, when you add the "CONFIG_FLASH=y" setting to any project, you are able to run the application normally, except when you try to do any type of reset, which leads your program to be in an infinite loop at address 0x20005840, is my understanding correct? Yes, this is correct.  I'm only able to restart the program by powering the board off and back on. Would you please check the Reset status Register (SYS_RST_STATUS) to check if the reset cause is being registered? I'm currently trying these tests with the zephyr sample hello_world.  With or without CONFIG_FLASH=y, and with my custom board or the actual FRDM-RW612, I wasn't able to get a value on SYS_RST_STATUS.  I tried pressing the physical reset button (connected to PDn on the SOC), calling tfm_platform_system_reset() after the printf statement, and triggering a hardfault by accessing a NULL pointer, but none of these produced values on the reset status register. I tried sampling it before reset, after reset in the loop at address 0x20005840, and after reset in the BL2 stage and no matter what SYS_RST_STATUS was 0.  I'm not sure if I'm checking it wrong, I use GDB (through west attach) to debug and got the value within the PMU block by printing p *((PMU_Type*)0x40031000u).  If it helps to know, the SYS_RST_EN register was always 0x39 when I sampled. Additionally, have you done all your tests with the non-secure version of the board? Yes, I build all of these tests clean by removing the build folder then running west build -b frdm_rw612/rw612/ns. let me know whether this behavior is present or not, with the same configs you are adding to test with your custom board? Most of my configs are related to peripherals on the flexcomm ports.  For my testing on this issue, I've only left changes I made to the TF-M profile.  I am using the TF-M medium arotless profile instead of large so I can perform over-the-air firmware updates with the TF-M FWU partition.  For this I have 3 extra zephyr KConfig options: CONFIG_TFM_PROFILE_TYPE_AROTLESS=y CONFIG_TFM_SFN=y CONFIG_TFM_ISOLATION_LEVEL=1 And the only thing I've edited in the TF-M module folder is the following profile setting in modules/tee/tf-m/trusted-firmware-m/platform/ext/target/nxp/frdmrw612/config.cmake: set(TFM_PROFILE "profile_medium_arotless" CACHE STRING "The TF-M profile") Which was modified from "profile_large" Thank you for your help, please let me know if I can provide any more information. Re: RW612 Nonsecure Flash Setting Breaks Reset Functionality Hi Jake, thank you for answering my questions. Since you mentioned that you tested with the FRDM-RW612, are you able to replicate the reset behavior in this board? I have tried by adding your configs and TF-M build changes (TF-M profile), but I am still unable to reproduce your behavior. If you are able to replicate this, would you please share the detailed steps that you are following to reproduce the behavior on the FRDM-RW612? Re: RW612 Nonsecure Flash Setting Breaks Reset Functionality Hi Roman, I found out the schematic for my board was wrong, and the flash chip I was using was really the W25Q01 instead of the W25Q512 like the FRDM-RW612. I soldered a W25Q512 to my board and now it resets with no problem. I apologize for wasting your time before. Are there any resources for how to reconfigure the flash settings to work with my chip? I see the fc_flexspi_nor_config_t struct in flash_config.c which is set up for the W25Q512, but is there a document or guide that specifies what I would need to change to adapt to my new chip? Re: RW612 Nonsecure Flash Setting Breaks Reset Functionality Hello Jake, don't worry about it, thank you for letting me know the root cause. Unfortunately, there is no specific guide to reconfigure the flash. However, you could take as reference the structure of the RD-RW612-BGA board directory, or the IRIS-W1-EVK board directory (from u-Blox) which both have different flash ICs from the FRDM board, on what changes are required in case of using a different flash. In the case of TF-M there is also the directory of the RD-RW612-BGA non-secure version of the board, which also may serve as reference for the required changes. Hope this helps!
View full article