Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
S32K3XX MBD TOOL BOX PROJECT DEPLOYMENT ERROR I'm trying to deploy  s32k3xx_dio_ebt.slx example code using S32K312 EVB .I'm facing issue while deploying the code in to the board . Attaching the error i'm getting . If anyone have any documents to refer for S32K3 model based example project please let me know . Re: S32K3XX MBD TOOL BOX PROJECT DEPLOYMENT ERROR Hi, @reshma97 , Thank you for your interest into Model-Based Design Toolbox for S32K3. The error in the attached image generally occurs when the connection with the board is not correctly established. Check again the USB connection cable of the board and the power cable, or you can try with another USB cable. To understand the method you used, I wanted to know how you tried to deploy: building the model in Simulink or to directly download the .elf file next to the model on the board? Let us know if you problem persists. Best regards, Dragos
View full article
LS1028ARDB 使用 SD 卡启动问题 我无法使用 SD 卡启动 LS1028ARDB。将 SW2 从 eMMC 切换到 SD(1001100 到 10001000)模式后,电源 LED 变为黄色,并且 PuTTY 终端中没有任何显示。 但是,在 eMMC 模式 sw2-1001100 启动时,我收到以下日志输出: U-Boot SPL 2018.03-00144-gc53e2aca78(2018 年 12 月 7 日 - 12:38:39 +0000) 初始化 DDR.... 警告:在没有缓冲区且环境尚未准备好的情况下调用__hwconfig without a buffer and before environment is ready WARNING: Calling __ hwconfig 警告:在没有缓冲区且环境尚未准备好的情况下调用__hwconfig without a buffer and before environment is ready WARNING: Calling __ hwconfig 尝试从 MMC1 启动 U-启动2018.03-00144-gc53e2aca78(2018 年 12 月 7 日 - 12:38:39 +0000) SoC:LS1028AE Rev1.0(0x870b0010) 时钟配置: CPU0(A72): 1300 MHz CPU1(A72): 1300 MHz 总线:400 MHz DDR:1600 MT/s 复位配置字(RCW): 00000000: 34004010 00000030 00000000 00000000 00000010: 00000000 00bf0000 0030c000 00000000 00000020: 00a03150 00002580 00000000 00002496 00000030: 00000000 00000010 00000000 00000000 00000040: 00000000 00000000 00000000 00000000 00000050: 00000000 00000000 00000000 00000000 00000060: 00000000 00000000 2006705a 00000000 00000070: bb580000 00000000 型号:NXP Layerscape 1028a RDB 板 主板:LS1028AE Rev1.0-RDB,版本:C,从eMMC启动 FPGA:v8(发布日期:RDB_2020_0330_1829) SERDES1 参考:Clock1 = 100.00MHz Clock2 = 100.00MHz I2C:就绪 动态随机存取存储器:3.9 GiB DDR 3.9 GiB(DDR4,32 位,CL=11,ECC 开启) “错误”处理程序,esr 0xbf000002 elr:0000000096042730 lr:00000000960020a0(重定位) elr:00000000fbda9730 lr:00000000fbd690a0 x0:0000000020400000 x1:0000000000000000 x2 : 00000000d00dfeed x3 : 0000000001e00210 x4 : 0000000001e00214 x5 : 00000000000011a0 x6 :0000000000001168 x7 :0000000000000002 x8 : 0000000000001164 x9 : 0000000000000000c x10:00000000fbb6093c x11:00000000fbb60a88 x12:0000000000001168 x13:00000000fbb6099c x14:00000000fbb60a88 x15:00000000fbb609ac x16:0000000000000001 x17:0000000000000000 x18:00000000fbb62d88 x19:0000000020400000 x20:00000000fbdd2298 x21:0000000065d67000 x22:000000001801deb1 x23:0000000018009dd8 x24:000000001801de99 x25:0000000018020000 x26:00000000deadbeef x27:0000000001e00404 x28:0000000001e00210 x29:00000000fbb60960 重置 CPU ... # ## ERROR ## # 请重置主板### 您能提供解决方案吗? 回复:LS1028ARDB 使用 SD 卡启动问题 谢谢。现在它运行良好。 回复:LS1028ARDB 使用 SD 卡启动问题 请进入LS1028ARDB上的u-boot提示符,检查是否可以得到以下结果。 => ext2ls mmc 0:4 4096。 4096 .. 16384 失物招领 7 箱 4096 启动 4096 设备 4096 等 4096 主页 4096 包括 7 库 4096 媒体 4096 mnt 4096 选项 4096 过程 4096 根 4096 运行 8 sbin 4096 分享 4096 服务 4096 系统 4096 临时文件 4096 用户 4096 变量 10 初始化 => 此外,您能否提供在主机上将图像部署到 SD 卡的控制台日志? 回复:LS1028ARDB 使用 SD 卡启动问题 完成所有步骤后,我收到以下错误: 尝试从 SD 加载 HDP 固件。 切换到分区#0,确定 mmc0是当前设备 设备:FSL_SDHC 制造商 ID:9f 原始设备制造商:5449 名称: SD32G 总线速度:50000000 模式:SD 高速(50MHz) 路块长度:512 SD 版本 3.0 高容量:是 容量:28.8 GiB 总线宽度:4位 擦除组大小:512 字节 MMC 读取:设备号 0,块号 18944,计数 512...读取 512 个块:OK 从 0x00000000a0000000 偏移量 0x0000000000002000 加载 hdp 固件 加载hdp固件完成 切换到分区#0,确定 mmc0是当前设备 扫描 mmc 0:1... libfdt fdt_check_header():FDT_ERR_BADMAGIC 正在扫描磁盘 [email protected]... 正在扫描磁盘 [email protected]... ** 无法识别的文件系统类型 ** 找到 6 个磁盘 没有 EFI 系统分区 错误:无效的设备树 正在扫描 mmc 0:2... 找到 U-Boot 脚本 /ls1028ardb_boot.scr 17 毫秒内读取 1038 字节(59.6 KiB/s) ## Executing script at 80000000 41159168 bytes read in 1723 ms (22.8 MiB/s) 32751 bytes read in 14 ms (2.2 MiB/s) ##扁平设备树 blob 位于 90000000 使用位于 0x90000000 的 fdt blob 进行引导 正在加载设备树至 000000008fff5000,结束于 000000008fffffee ... 确定 无法更新属性/sysclk:clock-frequency,err=FDT_ERR_NOTFOUND 正在启动内核... [ 0.000000] 在物理 CPU 0x0000000000 上启动 Linux [0x410fd083] [0.000000] Linux 版本 5.10.35(jenkins@pluto)(aarch64-linux-gnu-gcc(Ubuntu 9.3.0-17ubuntu1~20.04)9.3.0,GNU ld(适用于 Ubuntu 的 GNU Binutils)2.34) #1 SMP PREEMPT 2021 年 8 月 27 日星期五 22:03:58 CST [0.000000]机器型号:LS1028A RDB板 [0.000000]earlycon: uart8250 at MMIO 0x00000000021c0500(选项'') [0.000000] printk:启动控制台[uart8250]已启用 [ 0.000000] efi: 未找到 UEFI。 [0.000000] cma:保留640 MiB,位于0x00000000d3c00000 [ 0.000000] NUMA:未找到NUMA配置 [ 0.000000] NUMA: 伪造位于 [mem 0x0000000080000000-0x00000020ffffffff] 的节点 [0.000000]NUMA:NODE_DATA[内存0x20ff7fdb00-0x20ff7fffff] [0.000000]区域范围: [0.000000]DMA[内存0x0000000080000000-0x00000000ffffffff] [0.000000]DMA32为空 [0.000000]正常[mem 0x0000000100000000-0x00000020ffffffff] [ 0.000000] 每个节点的可移动区域起始 [ 0.000000] 早期内存节点范围 [0.000000]节点 0:[mem 0x0000000080000000-0x00000000fbdfffff] [0.000000]节点 0:[mem 0x0000002080000000-0x00000020ffffffff] [ 0.000000] Initmem 设置节点 0 [mem 0x0000000080000000-0x00000020ffffffff] [ 0.000000] psci:从 DT 探测导管方法。 [ 0.000000] psci: 在固件中检测到 PSCIv1.1。 [ 0.000000] psci: 使用标准 PSCI v0.2 函数 ID [ 0.000000] psci: 不需要可信操作系统迁移 [0.000000]psci: SMC调用约定v1.2 [ 0.000000] percpu:嵌入式24页/cpu s60120 r8192 d29992 u98304 [ 0.000000] 在 CPU0 上检测到 PIPT I-cache [0.000000]CPU功能:检测到:GIC系统寄存器CPU接口 [0.000000]CPU功能:检测到:EL2矢量强化 [ 0.000000] CPU 功能:KASLR 强制启用内核页表隔离 [ 0.000000] CPU功能:检测到:内核页表隔离(KPTI) [ 0.000000] CPU 功能:检测到:Spectre-v2 [ 0.000000] CPU 功能:检测到:ARM 勘误表 1165522、1319367 或 1530923 [ 0.000000] 构建了 1 个区域列表,并进行移动分组。总页数:1015296 [0.000000]政策区域:正常 [ 0.000000] 内核命令行:console=ttyS0,115200 earlycon=uart8250,mmio,0x21c0500 root=PARTUUID=db6a277d-04 rw rootwait video=1920x1080-32@60 cma=640M iommu.passthrough=1arm-smmu.disable_bypass=0 [0.000000]Dentry缓存哈希表条目:524288(顺序:10,4194304字节,线性) [0.000000]inode缓存哈希表条目:262144(顺序:9,2097152字节,线性) [ 0.000000] mem 自动初始化:堆栈:关闭,堆分配:关闭,堆释放:关闭 [ 0.000000] 软件 IO TLB: 映射 [mem 0x00000000cfc00000-0x00000000d3c00000] (64MB) [0.000000]内存:3283016K/4126720K可用(20416K内核代码、3074K rwdata、9944K rodata、6656K init、1035K bss、188344K保留、655360K cma保留) [ 0.000000] rcu:可抢占的分层 RCU 实现。 [ 0.000000] rcu: RCU 事件跟踪已启用。 [ 0.000000] rcu: RCU 将 CPU 从 NR_CPUS=16 限制到 nr_cpu_ids=2。 [ 0.000000] Tasks RCU 的 Trampoline 变体已启用。 [ 0.000000] rcu: RCU 计算的调度程序登记延迟值为 25 jiffies。 [ 0.000000] rcu: 调整 rcu_fanout_leaf=16、nr_cpu_ids=2 的几何形状 [0.000000]NR_IRQS:64,nr_irqs:64,预分配的irqs:0 [0.000000]GICv3:GIC:使用拆分EOI/停用模式 [ 0.000000] GICv3:实施了 256 个 SPI [0.000000]GICv3:0扩展SPI已实现 [ 0.000000] GICv3: 分销商没有范围选择器支持 [0.000000]GICv3:已实施16个PPI [0.000000] GICv3: CPU0: 找到重新分配器 0 区域 0: 0x0000000006040000 [0.000000]它的[内存0x06020000-0x0603ffff] [ 0.000000] ITS@0x0000000006020000:分配了65536个设备@2080080000(平面,esz 8,psz 64K,shr 0) [ 0.000000] ITS: 使用缓存刷新命令队列 [0.000000]GICv3:使用预分配的重新分配表 [ 0.000000] GICv3:使用LPI属性表@0x0000000080000000 [ 0.000000] GICv3: CPU0: 使用保留的 LPI 待处理表 @0x0000000080010000 [ 0.000000] 随机:从 start_kernel+0x32c/0x4f0 调用 get_random_bytes,crng_init=0 [ 0.000000] arch_timer: cp15 计时器以 25.00MHz (phys) 运行。 [0.000000]时钟源:arch_sys_counter:掩码:0xffffffffffffff max_cycles:0x5c409fb33,max_idle_ns:440795203156 ns [0.000002] sched_clock: 56 位,25MHz,分辨率 39ns,每 4398046511103ns 包装一次 [0.008576]控制台:彩色虚拟设备80x25 [ 0.013104]校准延迟循环(跳过),使用定时器频率计算的值.. 50.00 BogoMIPS(lpj = 100000) [0.023557]pid_max:默认值:32768 最小值:301 [0.028271]LSM:安全框架初始化 [0.033003]挂载缓存哈希表条目:8192(顺序:4,65536字节,线性) [0.040494]挂载点缓存哈希表条目:8192(顺序:4,65536字节,线性) [0.049213] rcu:分层SRCU实现。 [0.054172]平台MSI:gic-its@6020000域已创建 [0.059612]PCI/MSI:/interrupt-controller@6000000/gic-its@6020000 域已创建 [0.067208]fsl mc MSI:gic its@6020000 域已创建 [ 0.073093] EFI 服务将不可用。 [ 0.077745] smp: 启动辅助 CPU ... [0.082658]在CPU1上检测到PIPT I-cache [0.082676] GICv3: CPU1: 找到重新分配器 1 区域 0:0x0000000006060000 [ 0.082686] GICv3: CPU1: 使用保留的 LPI 待处理表 @0x0000000080020000 [ 0.082709] CPU1:已启动辅助处理器 0x0000000001 [0x410fd083] [0.082756]smp:启动1个节点,2个CPU [ 0.111660] SMP:共激活2个处理器。 [0.116408]CPU功能:检测到:32位EL0支持 [ 0.121601] CPU 功能:检测到:CRC32 指令 [0.126787]CPU功能:检测到:32位EL1支持 [0.145167]CPU:所有CPU均从EL2启动 [ 0.149318] 替代方案:修补内核代码 [0.154512]devtmpfs:已初始化 [0.160538]已启用KASLR [0.163281]时钟源:jiffies:掩码:0xffffffff max_cycles:0xffffffff,max_idle_ns:7645041785100000 ns [0.173125] futex 哈希表条目:512(顺序:3,32768 字节,线性) [0.186728]pinctrl核心:初始化pinctrl子系统 [0.192631] DMI不存在或无效。 [0.196780]网络:注册协议系列16 [ 0.202054] DMA: 预分配 512 KiB GFP_KERNEL 池用于原子分配 [ 0.209265] DMA: 预分配 512 KiB GFP_KERNEL|GFP_DMA 池用于原子分配 [ 0.217227] DMA: 预分配 512 KiB GFP_KERNEL|GFP_DMA32 池用于原子分配 [0.225240]审计:初始化netlink子系统(已禁用) [0.230783]审计:类型=2000审计(0.156:1):状态=已初始化 audit_enabled=0 res=1 [0.231299]thermal_sys:注册热调节器‘step_wise’ [0.238605]thermal_sys:注册热调节器'power_allocator' [0.244880]cpuidle:使用调速器菜单 [ 0.255675] hw-breakpoint:找到6个断点和4个观察点寄存器。 [ 0.262553] ASID 分配器已初始化,包含 32768 个条目 [0.268653]序列号:AMBA PL011 UART驱动程序 [0.272838]imx mu驱动程序已注册。 [0.276815]imx rpmsg驱动程序已注册。 [0.291530]机器:LS1028A RDB板 [0.295318]SoC系列:QorIQ LS1028A [0.299007] SoC ID:svr:0x870b0010,修订版:1.0 [0.314818] HugeTLB 注册了 1.00 GiB 页面大小,预分配了 0 页 [ 0.321595] HugeTLB 注册了 32.0 MiB 页面大小,预分配了 0 页 [0.328365] HugeTLB 注册了 2.00 MiB 页面大小,预分配了 0 页 [ 0.335131] HugeTLB 注册了 64.0 KiB 页面大小,预分配了 0 页 [0.342870]cryptd:max_cpu_qlen设置为1000 [0.413965]raid6:neonx8 gen()4243MB/s [0.485989]raid6:neonx8异或()3194MB/s [0.558024]raid6:neonx4 gen()4317 MB/s [0.630059]raid6:neonx4异或()3304MB/s [0.702097]raid6:neonx2 gen()3894 MB/s [0.774129]raid6:neonx2异或()3032MB/s [0.846167]raid6:neonx1 gen()2987 MB/s [0.918198]raid6:neonx1异或()2416MB/s [0.990244] raid6: int64x8 gen() 2481 MB/s [1.062595]raid6: int64x8 xor() 1462 MB/s [1.134944]raid6: int64x4 gen() 2467 MB/s [1.207290]raid6:int64x4 xor()1487MB/s [1.279640]raid6: int64x2 gen() 2317 MB/s [1.351987]raid6: int64x2 xor() 1316 MB/s [1.424334]raid6: int64x1 gen() 1812 MB/s [1.496683]raid6: int64x1 xor() 978 MB/s [1.500991] raid6:使用算法neonx4 gen() 4317 MB/s [1.506438]raid6:.... xor() 3304 MB/s,已启用rmw [1.511446]raid6:使用neon恢复算法 [1.516431]ACPI:解释器已禁用。 [1.521400] iommu:默认域类型:直通(通过内核命令行设置) [1.529064]vgaarb:已加载 [1.531940]SCSI子系统已初始化 [1.535922]usbcore:注册的新接口驱动程序usbfs [1.541481]usbcore:注册的新接口驱动程序集线器 [1.546854]usbcore:注册的新设备驱动程序usb [1.552206]imx-i2c 2000000.i2c:无法获取 pinctrl,不支持总线恢复 [1.559720]i2c i2c-0:imx i2c适配器已注册 [1.564816]mc:Linux媒体接口:v0.10 [1.569136]videodev:Linux视频捕获接口:v2.00 [1.574718]pps_core:LinuxPPS API ver.1已注册 [1.579728]pps_core:软件版本。5.3.6 - 版权所有 2005-2007 Rodolfo Giometti [1.588964]已注册PTP时钟支持 [1.592984]EDAC MC:版本:3.0.0 [ 1.596794] 没有可用的 BMan 门户! [ 1.600825] QMan: 已分配查找表于 (__ __ptrval__ __),条目数为 65537 [ 1.608313] 没有可用的 QMan 门户! [1.612240]无USDPAA内存,设备树中无“fsl,usdpaa-mem” [1.618642]FPGA管理器框架 [1.622131]高级Linux声音架构驱动程序已初始化。 [1.628982]时钟源:切换到时钟源arch_sys_counter [1.635249]VFS:磁盘配额dquot_6.6.0 [1.639238]VFS:Dquote缓存哈希表条目:512(顺序0,4096字节) [1.646276]pnp: PnP ACPI:已禁用 [1.653137]网络:注册协议系列2 [1.657844]tcp_listen_portaddr_hash哈希表条目:2048(顺序:3,32768字节,线性) [1.666506]TCP建立的哈希表条目:32768(顺序:6,262144字节,线性) [1.674639]TCP绑定哈希表条目:32768(顺序:7,524288字节,线性) [1.682292]TCP:哈希表已配置(已建立32768绑定32768) [1.688962]UDP哈希表条目:2048(顺序:4,65536字节,线性) [1.695783]UDP-Lite哈希表条目:2048(顺序:4,65536字节,线性) [1.703111]网络:注册协议系列1 [1.707755]RPC:已注册名为UNIX套接字传输模块。 [1.713739]RPC:已注册的UDP传输模块。 [1.718496]RPC:已注册的TCP传输模块。 [1.723243]RPC:已注册tcp NFSv4.1反向通道传输模块。 [1.729748]PCI:CLS 0字节,默认64 [1.734132]硬件性能:启用armv8_cortex_a72 PMU驱动程序,7个计数器可用 [ 1.742548] kvm [1]: IPA 大小限制: 44 位 [1.747636] kvm [1]: GICv3: 没有 GICV 资源条目 [1.752473]kvm[1]:禁用GICv2仿真 [1.756970]kvm[1]:GIC系统寄存器CPU接口已启用 [1.762881]kvm[1]:vgic中断IRQ9 [ 1.766892] kvm [1]: Hyp 模式初始化成功 [1.774049]初始化系统信任的密钥环 [1.778609]工作集:timestamp_bits=42 max_order=20 bucket_order=0 [1.785410]squashfs:版本4.0(2009/01/31)菲利普·劳格 [1.791460]NFS:注册id_resolver密钥类型 [1.796571]密钥类型id_resolver已注册 [1.800795]密钥类型id_legacy已注册 [1.804855] nfs4filelayout_init: NFSv4 文件布局驱动程序正在注册... [1.811620] nfs4flexfilelayout_init: NFSv4 Flexfile 布局驱动程序正在注册... [1.819096]jffs2:版本2.2。(NAND) © 2001-2006 红帽公司 [1.825390]保险丝:init(API版本7.32) [1.829503]9p:安装v9fs 9p2000文件系统支持 [1.861030]xor:测量软件校验和速度 [1.867437]8个寄存器:6285 MB/秒 [1.873187]32个寄存器:7266 MB/秒 [1.879112]arm64_neon:6428 MB/秒 [1.883506]异或:使用函数:32regs(7266 MB/秒) [1.888605]已注册非对称密钥类型 [1.892736]非对称密钥解析器‘x509’已注册 [1.897677]块层 SCSI 通用(bsg)驱动程序版本 0.4 已加载(主要 243) [1.905198]io调度程序mq-deadline已注册 [1.909772]io调度程序kyber已注册 [1.919058]pci主机通用1f0000000.pcie:主桥 /soc/pcie@1f0000000 范围: [1.926900]pci主机通用1f0000000.pcie:内存 0x01f8000000..0x01f815ffff -> 0x0000000000 [1.935781]pci主机通用1f0000000.pcie:内存 0x01f8160000..0x01f81cffff -> 0x0000000000 [1.944660]pci主机通用1f0000000.pcie:内存 0x01f81d0000..0x01f81effff -> 0x0000000000 [1.953539]pci主机通用1f0000000.pcie:内存 0x01f81f0000..0x01f820ffff -> 0x0000000000 [1.962421]pci主机通用1f0000000.pcie:内存 0x01f8210000..0x01f822ffff -> 0x0000000000 [1.971316]pci主机通用1f0000000.pcie:内存 0x01f8230000..0x01f824ffff -> 0x0000000000 [1.980197]pci主机通用1f0000000.pcie:内存 0x01fc000000..0x01fc3fffff -> 0x0000000000 [1.989111]pci主机通用1f0000000.pcie:ECAM 位于 [mem 0x1f0000000-0x1f00fffff],用于 [bus 00] [1.997957]pci主机通用1f0000000.pcie:PCI 主桥至总线 0000:00 [2.004988]pci_bus 0000:00:根总线资源[总线00] [2.010264]pci_bus 0000:00:根总线资源[mem 0x1f8000000-0x1f815ffff](总线地址[0x00000000-0x0015ffff]) [2.020716]pci_bus 0000:00:根总线资源[mem 0x1f8160000-0x1f81cffff pref](总线地址[0x00000000-0x0006ffff]) [2.031610]pci_bus 0000:00:根总线资源[mem 0x1f81d0000-0x1f81effff](总线地址[0x00000000-0x0001ffff]) [2.042062]pci_bus 0000:00:根总线资源[mem 0x1f81f0000-0x1f820ffff pref](总线地址[0x00000000-0x0001ffff]) [2.052952]pci_bus 0000:00:根总线资源[mem 0x1f8210000-0x1f822ffff](总线地址[0x00000000-0x0001ffff]) [2.063403]pci_bus 0000:00:根总线资源[mem 0x1f8230000-0x1f824ffff pref](总线地址[0x00000000-0x0001ffff]) [2.074294]pci_bus 0000:00:根总线资源[mem 0x1fc000000-0x1fc3fffff](总线地址[0x00000000-0x003fffff]) [2.084759]PCI 0000:00:00.0:[1957:e100] 类型 00 类 0x020001 [2.090852]PCI 0000:00:00.0:BAR 0:[mem 0x1f8000000-0x1f803ffff 64bit](来自增强分配,属性 0x0) [2.101393]PCI 0000:00:00.0:BAR 2:[mem 0x1f8160000-0x1f816ffff 64bit pref](来自增强分配,属性 0x1) [2.112373]PCI 0000:00:00.0:VF BAR 0:[mem 0x1f81d0000-0x1f81dffff 64bit](来自增强分配,属性 0x4) [2.123176]PCI 0000:00:00.0:VF BAR 2:[mem 0x1f81f0000-0x1f81ffff 64bit pref](来自增强分配,属性 0x3) [2.134430]PCI 0000:00:00.0:D0 D3hot 支持 PME# [2.139975]PCI 0000:00:00.0:VF(n) BAR0 空间:[mem 0x1f81d0000-0x1f81effff 64bit](包含 2 个 VF 的 BAR0) [2.149991]PCI 0000:00:00.0:VF(n) BAR2 空间:[mem 0x1f81f0000-0x1f820ffff 64bit pref](包含 2 个 VF 的 BAR2) [2.160569]PCI 0000:00:00.1:[1957:e100] 类型 00 类 0x020001 [2.166653]PCI 0000:00:00.1:BAR 0:[mem 0x1f8040000-0x1f807ffff 64bit](来自增强分配,属性 0x0) [2.177194]PCI 0000:00:00.1:BAR 2:[mem 0x1f8170000-0x1f817ffff 64bit pref](来自增强分配,属性 0x1) [2.188173]PCI 0000:00:00.1:VF BAR 0:[mem 0x1f8210000-0x1f821ffff 64bit](来自增强分配,属性 0x4) [2.198976]PCI 0000:00:00.1:VF BAR 2:[mem 0x1f8230000-0x1f823ffff 64bit pref](来自增强分配,属性 0x3) [2.210231]PCI 0000:00:00.1:D0 D3hot 支持 PME# [2.215774]PCI 0000:00:00.1:VF(n) BAR0 空间:[mem 0x1f8210000-0x1f822ffff 64bit](包含 2 个 VF 的 BAR0) [2.225788]PCI 0000:00:00.1:VF(n) BAR2 空间:[mem 0x1f8230000-0x1f824ffff 64bit pref](包含 2 个 VF 的 BAR2) [2.236336]PCI 0000:00:00.2:[1957:e100] 类型 00 类 0x020001 [2.242423]PCI 0000:00:00.2:BAR 0:[mem 0x1f8080000-0x1f80bffff 64bit](来自增强分配,属性 0x0) [2.252964]PCI 0000:00:00.2:BAR 2:[mem 0x1f8180000-0x1f818ffff 64bit pref](来自增强分配,属性 0x1) [2.263953]PCI 0000:00:00.2:D0 D3hot 支持 PME# [2.269587]PCI 0000:00:00.3:[1957:ee01] 类型 00 类 0x088001 [2.275674]PCI 0000:00:00.3:BAR 0:[mem 0x1f8100000-0x1f811ffff 64bit](来自增强分配,属性 0x0) [2.286215]PCI 0000:00:00.3:BAR 2:[mem 0x1f8190000-0x1f819ffff 64bit pref](来自增强分配,属性 0x1) [2.297205]PCI 0000:00:00.3:D0 D3hot 支持 PME# [2.302846]PCI 0000:00:00.4:[1957:ee02] 类型 00 类 0x088001 [2.308930]PCI 0000:00:00.4:BAR 0:[mem 0x1f8120000-0x1f813ffff 64bit](来自增强分配,属性 0x0) [2.319470]PCI 0000:00:00.4:BAR 2:[mem 0x1f81a0000-0x1f81affff 64bit pref](来自增强分配,属性 0x1) [2.330460]PCI 0000:00:00.4:D0 D3hot 支持 PME# [2.336091]PCI 0000:00:00.5:[1957:eef0] 类型 00 类别 0x020801 [2.342178]PCI 0000:00:00.5:BAR 0:[mem 0x1f8140000-0x1f815ffff 64bit](来自增强分配,属性 0x0) [2.352718]PCI 0000:00:00.5:BAR 2:[mem 0x1f81b0000-0x1f81bffff 64bit pref](来自增强分配,属性 0x1) [2.363697]PCI 0000:00:00.5:BAR 4:[mem 0x1fc000000-0x1fc3fffff 64bit](来自增强分配,属性 0x0) [2.374247]PCI 0000:00:00.5:D0 D3hot 支持 PME# [2.379920]PCI 0000:00:00.6:[1957:e100] 类型 00 类 0x020001 [2.386004]PCI 0000:00:00.6:BAR 0:[mem 0x1f80c0000-0x1f80fffff 64bit](来自增强分配,属性 0x0) [2.396547]PCI 0000:00:00.6:BAR 2:[mem 0x1f81c0000-0x1f81cffff 64bit pref](来自增强分配,属性 0x1) [2.407535]PCI 0000:00:00.6:D0 D3hot 支持 PME# [2.413888]PCI 0000:00:1F.0:[1957:e001] 类型 00 类 0x080700 [ 2.419988] OF: /soc/pcie@1f0000000: 没有针对 id 0xf8 的 msi-map 转换 (null) [2.428102]layerscape pcie 3400000.pcie:主桥/soc/pcie@3400000 范围: [2.435516]layerscape pcie 3400000.pcie:IO 0x8000010000..0x800001ffff -> 0x0000000000 [2.444140]layerscape pcie 3400000.pcie:内存 0x8040000000..0x807fffffff -> 0x0040000000 [2.452841]layerscape pcie 3400000.pcie:PCI 主桥至总线 0001:00 [2.459614]pci_bus 0001:00:根总线资源[总线00-ff] [2.465151]pci_bus 0001:00:根总线资源[io 0x0000-0xffff] [2.471391] pci_bus 0001:00:根总线资源[mem 0x8040000000-0x807fffffff](总线地址[0x40000000-0x7fffffff]) [2.482032]PCI 0001:00:00.0:[1957:82c0] 类型 01 类 0x060400 [2.488147]PCI 0001:00:00.0:支持D1 D2 [2.492457]PCI 0001:00:00.0:D0 D1 D2 D3hot 支持 PME# [ 2.500047] pci_bus 0001:01: busn_res: [bus 01-ff] 结束更新为 01 [2.506733]PCI 0001:00:00.0:PCI 桥接至 [总线 01] [2.511863]layerscape pcie 3500000.pcie:主桥/soc/pcie@3500000 范围: [2.519272]layerscape pcie 3500000.pcie:IO 0x8800010000..0x880001ffff -> 0x0000000000 [2.527896]layerscape pcie 3500000.pcie:内存 0x8840000000..0x887fffffff -> 0x0040000000 [2.536585]layerscape pcie 3500000.pcie:PCI 主桥至总线 0002:00 [2.543353]pci_bus 0002:00:根总线资源[总线00-ff] [2.548891]pci_bus 0002:00:根总线资源[io 0x10000-0x1ffff](总线地址[0x0000-0xffff]) [2.557939] pci_bus 0002:00:根总线资源[mem 0x8840000000-0x887fffffff](总线地址[0x40000000-0x7fffffff]) [2.568578]PCI 0002:00:00.0:[1957:82c0] 类型 01 类 0x060400 [2.574689]PCI 0002:00:00.0:支持D1 D2 [2.579001]PCI 0002:00:00.0:D0 D1 D2 D3hot 支持 PME# [2.586594] pci_bus 0002:01: busn_res:[bus 01-ff] end 更新为 01 [2.593277]PCI 0002:00:00.0:PCI 桥接至 [总线 01] [2.599033]EINJ:ACPI 已禁用。 [2.606220]总线频率驱动模块已加载 [ 2.614029] 串行:8250/16550 驱动程序,4 个端口,启用 IRQ 共享 [2.621709]printk:控制台[ttyS0]已禁用 [2.626065]21c0500.序列号:MMIO 0x21c0500 处的 ttyS0(irq = 22,base_baud = 12500000)是 16550A [2.634958]printk:控制台[ttyS0]已启用 [2.634958]printk:控制台[ttyS0]已启用 [2.643370]printk: bootconsole[uart8250]已禁用 [2.643370]printk: bootconsole[uart8250]已禁用 [2.653484]21c0600.序列号:MMIO 0x21c0600 处的 ttyS1(irq = 22,base_baud = 12500000)是 16550A [2.662592]SuperH(H)SCI(F)驱动程序已初始化 [2.667424]msm_serial:驱动程序已初始化 [2.672532]arm-smmu 5000000.iommu:探测硬件配置... [2.679002]arm-smmu 5000000.iommu:SMMUv2 具有: [2.683634]arm-smmu 5000000.iommu:第一阶段翻译 [2.688964]arm-smmu 5000000.iommu:第二阶段翻译 [2.694293]arm-smmu 5000000.iommu:嵌套翻译 [2.699539]arm-smmu 5000000.iommu:流与 128 个寄存器组匹配 [2.706701]arm-smmu 5000000.iommu:64 个上下文库(仅限 0 个 stage-2) [2.713254]arm-smmu 5000000.iommu:支持的页面大小:0x61311000 [2.719718]arm-smmu 5000000.iommu:第 1 阶段:48 位 VA -> 48 位 IPA [2.726184]arm-smmu 5000000.iommu:第 2 阶段:48 位 IPA -> 48 位 PA [2.738493]brd:模块已加载 [2.745143]循环:模块已加载 [2.748453]pci端点测试0001:00:00.0:添加到 iommu 组 0 [2.754856]pci端点测试0002:00:00.0:添加到 iommu 组 1 [2.761712]MegaSAS:07.714.04.00-RC1 [2.766209]imx ahci驱动程序已注册。 [2.770524]ahci-qoriq 3200000.sata:添加到 iommu 组 2 [2.776244]ahci-qoriq 3200000.sata:未找到电源 ahci,使用虚拟调节器 [2.783824]ahci-qoriq 3200000.sata:未找到电源 phy,使用虚拟调节器 [2.791275]ahci-qoriq 3200000.sata:未找到供电目标,使用虚拟调节器 [2.799036]ahci-qoriq 3200000.sata:AHCI 0001.0301 32 个插槽 1 个端口 6 Gbps 0x1 impl 平台模式 [2.808033]ahci-qoriq 3200000.sata:标志: 64 位 ncq sntf pm clo 仅 pmp fbs pio slum 部分 ccc sds apst [2.818161]scsi主机0:ahci qoriq [2.821698]ata1:SATA最大UDMA/133 mmio [mem 0x03200000-0x0320ffff]端口0x100 irq 28 [2.831208]自旋或spi0.0:mt35xu02g(262144 KB) [2.842351]libphy:固定MDIO总线:已探测 [2.847230]tun:通用TUN/TAP设备驱动程序,1.6 [2.852504]mscc_felix 0000:00:00.5:添加到 iommu 组 3 [2.858386]mscc_felix 0000:00:00.5:无法注册 DSA 开关:-517 [2.865542]thunder_xcv,版本1.0 [2.868795]thunder_bgx,版本1.0 [2.872059]nicpf,版本1.0 [2.874984]飞思卡尔FM模块,FMD API版本21.1.0 [2.880304]飞思卡尔FM端口模块 [2.883977]fsl_mac: fsl_mac:基于FSL FMan MAC API的驱动程序 [2.889625]fsl_dpa:FSL DPAA以太网驱动程序 [2.894040]fsl_advanced:FSL DPAA高级驱动程序: [2.899021]fsl_proxy:FSL DPAA代理初始化驱动程序 [2.904658]fsl_oh:FSL FMan离线解析端口驱动程序 [2.910160]fsl_enetc 0000:00:00.0:添加到 iommu 组 4 [2.915880]fsl_enetc 0000:00:00.1:添加到 iommu 组 5 [3.029027]fsl_enetc 0000:00:00.1:使能装置 (0400 -> 0402) [3.035860]fsl_enetc 0000:00:00.1:设备已禁用,正在跳过 [3.041964]fsl_enetc 0000:00:00.2:添加到 iommu 组 6 [3.047668]fsl_enetc 0000:00:00.6:添加到 iommu 组 7 [3.143169]ata1:SATA链接关闭(SStatus 0 SControl 300) [3.160989]fsl_enetc 0000:00:00.6:使能装置 (0400 -> 0402) [3.167419]fsl_enetc 0000:00:00.6:设备已禁用,正在跳过 [3.173729]fsl_enetc_mdio 0000:00:00.3:添加到 iommu 组 8 [3.284992]fsl_enetc_mdio 0000:00:00.3:使能装置 (0400 -> 0402) [3.291804]libphy:FSL PCIe IE中央MDIO总线:已探测 [3.301344]fsl_enetc_ptp 0000:00:00.4:添加到 iommu 组 9 [3.307317]fsl_enetc_ptp 0000:00:00.4:使能装置 (0404 -> 0406) [3.313976]ptp_qoriq:设备树节点缺少所需元素,尝试自动配置 [3.322728]pps pps0:新的pps源ptp0 [3.327171]hclge正在初始化 [3.330516]hns3:适用于Hip08系列的海思以太网网络驱动程序-版本 [3.337771]hns3:版权所有(c)2017华为公司。 [3.343137]e1000:Intel(R)PRO/1000网络驱动程序 [3.348032]e1000:版权所有(c)1999-2006 英特尔公司。 [3.353824]e1000e:Intel(R)PRO/1000网络驱动程序 [3.358804]e1000e:版权所有(c)1999-2015英特尔公司。 [3.364769]igb:Intel(R)千兆以太网网络驱动程序 [3.370185]igb:版权所有(c)2007-2014英特尔公司。 [3.375795]igbvf:Intel(R)千兆虚拟功能网络驱动程序 [3.382084]igbvf:版权所有(c)2009-2012英特尔公司。 [3.388211]sky2:驱动程序版本1.30 [3.392427]usbcore:注册的新接口驱动程序r8152 [3.397947]usbcore:注册的新接口驱动程序asix [3.403384]usbcore:注册的新接口驱动程序ax88179_178a [3.409798]VFIO-用户级元驱动程序版本:0.3 [3.415323]dwc3 3100000.usb:添加到 iommu 组 10 [3.420966]dwc3 3110000.usb:添加到 iommu 组 11 [3.427627]ehci_hcd:USB 2.0“增强型”主机控制器(EHCI)驱动程序 [3.434196]ehci-pci:EHCI PCI平台驱动程序 [3.438682]ehci平台:EHCI通用平台驱动程序 [3.443998]ehci orion:ehci orion驱动程序 [3.448073]ehci-exynos:EHCI Exynos驱动程序 [3.452314]ohci_hcd:USB 1.1‘Open’主机控制器(OHCI)驱动程序 [3.458523]ohci-pci:OHCI PCI平台驱动程序 [3.463004]ohci平台:OHCI通用平台驱动程序 [3.468309]ohci exynos: OHCI Exynos 驱动程序 [3.472758]xhci-hcd xhci-hcd.0.auto:xHCI主机控制器 [3.478279]xhci-hcd xhci-hcd.0.auto:已注册新的USB总线,分配总线编号1 [3.486054]xhci-hcd xhci-hcd.0.auto:hcc 参数 0x0220f66d hci 版本 0x100 怪癖 0x0000000002010010 [3.495506]xhci-hcd xhci-hcd.0.auto:irq 26,io mem 0x03100000 [3.501817]集线器1-0:1.0:已找到 USB 集线器 [3.505593]集线器1-0:1.0:检测到1个端口 [3.509674]xhci-hcd xhci-hcd.0.auto:xHCI主机控制器 [3.515184]xhci-hcd xhci-hcd.0.auto:已注册新的USB总线,分配总线编号2 [3.522873]xhci-hcd xhci-hcd.0.自动:主机支持 USB 3.0 SuperSpeed [ 3.529447] usb usb2: 我们不知道该主机的 LPM 算法,因此禁用 LPM。 [3.537796]集线器2-0:1.0:已找到 USB 集线器 [3.541571]集线器2-0:1.0:检测到1个端口 [3.545905]usbcore:注册的新接口驱动程序uas [3.551277]usbcore:注册的新接口驱动程序usb存储 [3.559016]ftm警报2810000.计时器:注册为 rtc1 [3.564751]i2c/dev条目驱动程序 [3.570491]I2C I2C-0:添加了多路复用I2C总线1 [3.575540]i2c i2c-0:添加了多路复用i2c总线2 [3.580531]I2C I2C-0:添加了多路复用I2C总线3 [3.585622]i2c i2c-0:添加了多路复用i2c总线4 [3.590527]I2C I2C-0:添加了多路复用I2C总线5 [3.595437]I2C I2C-0:添加了多路复用I2C总线6 [3.600340]i2c i2c-0:添加了多路复用i2c总线7 [3.605248]I2C I2C-0:添加了多路复用I2C总线8 [3.610060]pca954x 0-0077:为I2C mux pca9847注册了8条多路复用总线 [3.629643]sp805 wdt c000000.看门狗:注册成功 [3.635698]sp805 wdt c010000.看门狗:注册成功 [3.642816]qoriq-cpufreq qoriq-cpufreq:飞思卡尔QorIQ CPU频率调节驱动程序 [3.651357]sdhci:安全数字主机控制器接口驱动程序 [3.657592]sdhci:版权所有(c)Pierre Ossman [3.662246] Synopsys Designware多媒体卡接口驱动程序 [3.668800]sdhci pltfm:SDHCI平台和OF驱动程序助手 [3.674916]SDHCI ESDHC 2140000.mmc:添加到 iommu 组 12 [3.675452]SDHCI ESDHC 2150000.mmc:添加到 iommu 组 13 [3.680969]ledtrig-cpu:已注册以指示CPU上的活动 [3.692934]SMCCC:SOC_ID:ARCH_SOC_ID未实现,跳过.... [3.699805]usbcore:注册的新接口驱动程序usbhid [3.705405]usbhid:USB HID核心驱动程序 [3.709531]mmc0:2140000.mmc上的SDHCI控制器[2140000.mmc]使用 ADMA [3.710007]无fsl,qman节点 [3.716447]mmc1:2150000.mmc上的SDHCI控制器[2150000.mmc]使用 ADMA [3.719327]飞思卡尔USDPAA流程驱动程序 [3.719329]fsl-usdpaa:未找到区域 [3.719332]飞思卡尔USDPAA进程IRQ驱动程序 [3.740928] optee:探测导管方法。 [3.745405]optee:修订版3.13(2c1092df) [3.745772]optee:初始化驱动程序 [3.754127]Galcore F0C0000.GPU:添加到 iommu 组 14 [3.759706]Galcore版本6.4.3.p2.336687 [3.792687] [drm] 已在 minor 0 上为 f0c0000.gpu 初始化 vivante 1.0.0 20170808 [3.802355]mmc1:地址0001处的新HS400 MMC卡 [3.802364]fsl sai f130000.音频控制器:无法获取 mclk0 时钟:-2 [3.807743]mmcblk1:mmc1:0001 Q2J55L 7.13 GiB [3.817939]网络:注册协议系列26 [3.819140]mmcblk1boot0:mmc1:0001 Q2J55L分区1 2.00 MiB [3.823361]U32分类器 [3.829511]mmcblk1boot1:mmc1:0001 Q2J55L分区2 2.00 MiB [3.832015]输入设备检查 [3.838038]mmcblk1rpmb:mmc1:0001 Q2J55L分区3 4.00 MiB,chardev(507:0) [3.841635]已配置操作 [3.852771]初始化XFRM netlink套接字 [3.857133]网络:注册协议系列10 [3.861964]使用 IPv6 的分段路由 [3.865691]sit: IPv6、IPv4 和 MPLS over IPv4 隧道驱动程序 [3.871961]网络:注册协议系列17 [3.876450]网络:注册协议系列15 [3.880952]已注册桥接防火墙 [3.888135]8021q:802.1q VLAN支持v1.8 [3.892350]lib80211: IEEE802.11 驱动程序的常用例程 [3.894195]mmc0:位于地址5048的新型超高速SDR104 SDHC卡 [3.904714]9pnet:安装9p2000支架 [3.909022] tsn通用netlink模块v1初始化… [3.909236]mmcblk0:mmc0:5048 SD32G 28.8 GiB(ro) [3.913812]密钥类型dns_resolver已注册 [3.919966]mmcblk0:p1 p2 p3 p4 [3.923103]注册taskstats版本1 [3.930282]加载编译后的X.509证书 [3.936324]Btrfs已加载,crc32c=crc32c-generic [3.943073]fsl edma 22c0000.dma控制器:添加到 iommu 组 15 [3.950539]pcieport 0001:00:00.0:PME:使用 IRQ 29 发出信号 [3.956458]pcieport 0002:00:00.0:PME:使用 IRQ 31 发出信号 [3.962501]mscc_felix 0000:00:00.5:无法注册 DSA 开关:-517 [4.077124]fsl_enetc 0000:00:00.0:使能装置 (0400 -> 0402) [4.083498]fsl_enetc 0000:00:00.0:未为 SI1 指定 MAC 地址,使用 96:ab:cf:f7:cb:be [4.092114]fsl_enetc 0000:00:00.0:未为 SI2 指定 MAC 地址,使用 4a:fb:36:fb:eb:3f [4.102849]libphy:飞思卡尔ENETC MDIO总线:已探测 [4.109064]libphy:Freescale ENETC内部MDIO总线:已探测 [4.115254]fsl_enetc 0000:00:00.0:enetc_tsn_init: 设置完成 [4.229108]fsl_enetc 0000:00:00.2:使能装置 (0400 -> 0402) [4.238019]fsl_enetc 0000:00:00.2:enetc_tsn_init: 设置完成 [4.250401]fsl sai f130000.音频控制器:无法获取 mclk0 时钟:-2 [4.267590]libphy:VSC9959内部MDIO总线:已探测 [4.272693]mscc_felix 0000:00:00.5:在内部 MDIO 地址 0 处找到 PCS [4.279538]mscc_felix 0000:00:00.5:在内部 MDIO 地址 1 处找到 PCS [4.286365]mscc_felix 0000:00:00.5:在内部 MDIO 地址 2 处找到 PCS [4.293190]mscc_felix 0000:00:00.5:在内部 MDIO 地址 3 处找到 PCS [4.795106]mscc_felix 0000:00:00.5 swp0(未初始化):PHY [0000:00:00.3:10]驱动程序[Microsemi GE VSC8514 SyncE](irq=POLL) [5.027149]mscc_felix 0000:00:00.5 swp1(未初始化):PHY [0000:00:00.3:11]驱动程序[Microsemi GE VSC8514 SyncE](irq=POLL) [5.259154]mscc_felix 0000:00:00.5 swp2(未初始化):PHY [0000:00:00.3:12]驱动程序[Microsemi GE VSC8514 SyncE](irq=POLL) [5.491103] mscc_felix 0000:00:00.5 swp3(未初始化):PHY [0000:00:00.3:13]驱动程序[Microsemi GE VSC8514 SyncE](irq=POLL) [5.514263]mscc_felix 0000:00:00.5:配置固定/内部链接模式 [5.521568]mscc_felix 0000:00:00.5:链路已连接 - 2.5Gbps/满载 - 流量控制关闭 [5.521698]设备eth1进入混杂模式 [5.533771]DSA:树0设置 [5.539096]ALSA设备列表: [5.542092]未找到声卡。 [5.545776] VFS:无法打开根设备“PARTUUID=db6a277d-04”或未知块(179,100):错误-30 [ 5.554984]请附加正确的“root=”启动选项;以下是可用的分区: [5.563379]0100 4096 RAM0 [5.563380](司机?) [5.569512]0101 4096 RAM1 [5.569513](司机?) [5.575632]0102 4096 RAM2 [5.575634](司机?) [5.581755]0103 4096 RAM3 [5.581757](司机?) [5.587876]0104 4096 RAM4 [5.587877](司机?) [5.593998]0105 4096 RAM5 [5.594000](司机?) [5.600117]0106 4096 RAM6 [5.600119](司机?) [5.606251]0107 4096 RAM7 [5.606253](司机?) [5.612375]0108 4096 RAM8 [5.612376](司机?) [5.618518]0109 4096 RAM9 [5.618520](司机?) [5.624638]010A 4096 RAM10 [5.624640](司机?) [5.630858]010b 4096 RAM11 [5.630859](司机?) [5.637076]010C 4096 RAM12 [5.637078](司机?) [5.643283]010d 4096 RAM13 [5.643285](司机?) [5.649502]010e 4096 RAM14 [5.649504](司机?) [5.655710]010F 4096 RAM15 [5.655712](司机?) [5.661932]1f00 262144 mtdblock0 [5.661934](司机?) [5.668491]b300 7471104 mmcblk1 [5.668494]驱动程序:mmcblk [5.675322]b360 30220288 mmcblk0 [5.675325]驱动程序:mmcblk [5.682150]b361 131072 mmcblk0p1 db6a277d-01 [5.682152] [5.688968]b362 2097152 mmcblk0p2 db6a277d-02 [5.688970] [5.695793]b363 5242880 mmcblk0p3 db6a277d-03 [5.695795] [5.702610]b364 22676480 mmcblk0p4 db6a277d-04 [5.702611] [5.709440]内核崩溃-未同步:VFS:无法在未知块上挂载根文件系统(179,100) [ 5.718082] CPU: 0 PID: 1 通信: swapper/0 未受污染 5.10.35 #1 [5.724105]硬件名称:LS1028A RDB板(DT) [5.728820]呼叫跟踪: [5.731277]转储回溯+0x0/0x1a8 [5.734947]显示堆栈+0x18/0x68 [5.738269]转储堆栈+0xd0/0x12c [5.741678]恐慌+0x16c/0x334 [5.744738]安装块根+0x1c0/0x250 [5.748756]安装根+0x10c/0x144 [5.752250]准备命名空间+0x130/0x170 [5.756354]内核_init_freeable+0x210/0x23c [5.760721]内核初始化+0x14/0x118 [5.764216]从_fork+0x10/0x34返回 [5.767799]SMP:停止辅助CPU [5.771737]内核偏移量:0x501115e00000 来自 0xffff800010000000 [5.777847]物理偏移:0xffffc09140000000 [5.782038]CPU功能:0x0240022,21806008 [5.786317]内存限制:无 [ 5.789379] ---[结束内核恐慌 - 未同步:VFS:无法在未知块(179,100)上挂载根文件系统]--- 请帮我解决这个问题。 回复:LS1028ARDB 使用 SD 卡启动问题 我遵循了上述所有步骤。现在启动时我收到以下错误。 [5.544216] VFS:无法打开根设备“PARTUUID=8c8ecbd4-04”或未知块(179,100):错误-30 [5.707876]内核崩溃-未同步:VFS:无法在未知块上挂载根文件系统(179,100) [ 5.787811] ---[结束内核恐慌 - 未同步:VFS:无法在未知块(179,100)上挂载根文件系统]--- 我检查了根文件夹,它是空的。 请给我一个解决方案。
View full article
Need a help about SDK of S32K is the class of ASPICE Need a help about SDK of S32K is the class of ASPICE,thanks! Re: Need a help about SDK of S32K is the class of ASPICE Hi See the description(A-SPICE) of the Software Quality Levels section of the S32 Software Development Kit - Fact Sheet Best Regards, Robin ------------------------------------------------------------------------------- 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
S32K3XX MBD工具箱项目部署错误 我正在尝试使用 S32K312 EVB 部署 s32k3xx_dio_ebt.slx 示例代码。在将代码部署到电路板时遇到了问题。 附上我遇到的错误。 如果有人有任何基于 S32K3 模型的示例项目可供参考,请告诉我。
View full article
FLASH NOR boot frequency issue Hello NXP support, i have an issue regarding the Flash NOR clock frequency , i have an RT1176 custom board , and i have a  IS25LP128 flash NOR  on FlexSpi2 portA with mux  attached , i have configured the FCB as attached below and i wanted to change the frequency from 60Mhz to 133Mhz , now after doing that i try to compare two exact similar  boards one with 60Mhz and the second with 133Mhz and i still get the same perf with no difference whatsoever ! i need to understand first if i configure the serialClkFreq in FCB  to be 133Mhz and the board boots up correctly but could it default to 60Mhz or is there some place else i have to set the frequency ?  i'd really appreciate any help on the matter   i.MX-RT1170   Re: FLASH NOR boot frequency issue Hi @yosri_c  The maximum frequency of different types of flash varies. For example, the flash model uses MX25UM51345G, and according to the information in the flash manual, the normal operating frequency can reach 200MHz. BR Hang Re: FLASH NOR boot frequency issue Hi there Hang, i'll try that and be back with an answer. althought i think the max freq for NOR flash is 133Mhz isn' it ? Regards yosri Re: FLASH NOR boot frequency issue Hi @yosri_c  If you try to change it to 166MHz, are their performances the same? BR Hang
View full article
S32K3XX MBD ツール ボックス プロジェクトのデプロイ エラー 私はS32K312 EVBを使用してs32k3xx_dio_ebt.slxサンプルコードをデプロイしようとしています。コードをボードにデプロイする際に問題に直面しています。 私が得ているエラーを添付しています。 S32K3モデルベースのサンプルプロジェクトについて参照するドキュメントがある場合は、お知らせください。
View full article
Availability of board design files for MIMXRT1180-EVK Hello, Would it be possible to share the board design files for the MIMXRT1180-EVK? There is a link in the user manual (UM12021) which unfortunatly does not work (The collateral "MIMXRT1180-EVK-DESIGNFILES" does not exist). Fixing the link would of course also help me. Thank you, Kind regards, Jasper Re: Availability of board design files for MIMXRT1180-EVK Hello, the documentation is not available yet on the page until the launch date will be confirmed. I suggest contact your sales representative. Best regards, Pavel
View full article
Report dfu boot problem to LPC Link2 with lpscrypt under Linux There is a problem in dfu_boot script in lpcscrypt under linux. the version is installed via LinkServer_1.6.133.x86_64.deb.bin My installed dfu-util is 0.11 whose output is following dfu-util 0.11 Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc. Copyright 2010-2021 Tormod Volden and Stefan Schmidt This program is Free Software and has ABSOLUTELY NO WARRANTY Please report bugs to http://sourceforge.net/p/dfu-util/tickets/ Found DFU: [1fc9:000c] ver=0100, devnum=115, cfg=1, intf=0, path="3-1", alt=0, name="DFU", serial="ABCD" but vp_hex generated is not corrected: cause here DEVICE_VID_PID is 0x1f9c:0x000c Which prevents from detecting dfu mode Re: Report dfu boot problem to LPC Link2 with lpscrypt under Linux Thanks. I have made my own fixes. Just hope next release will have a more general fixes for it. Re: Report dfu boot problem to LPC Link2 with lpscrypt under Linux Hi @sprhawk  It looks like the script is not correctly parsing the dfu-util version and as a result, the vp_hex variable is not being set properly. Your output indicates dfu-util version 0.11, but the script is not handling this correctly. Here’s a fix for the script to correctly handle dfu-util version 0.11: 1. Adjust the script to correctly parse the dfu-util version. 2. Set the vp_hex variable based on the version detected. # Establish what kind of prefix VID:PIDs have when listed in -l vp_hex="" # Extract major and minor versions dfu_major_ver=$(echo "$dfu_ver" | cut -d '.' -f 1) dfu_minor_ver=$(echo "$dfu_ver" | cut -d '.' -f 2) # Check if dfu_major_ver is 0 and dfu_minor_ver is 11 if [ "$dfu_major_ver" -eq 0 ] && [ "$dfu_minor_ver" -eq 11 ]; then vp_hex="0x" fi # echo "DFU version $dfu_ver means we should use hex prefix '$vp_hex'" DEVICE_VID_PID="${vp_hex}${DEVICE_VID}:${vp_hex}${DEVICE_PID}" # DEVICE_VID_PID="\(0x\|\)$DEVICE_VID:\(0x\|\)$DEVICE_PID" This script correctly checks for the major and minor version of dfu-util and sets the vp_hex variable accordingly. It should resolve the issue of incorrectly setting the DEVICE_VID_PID variable. BR Hang
View full article
How To read the IAP Flash Memory read on LPC865 Hi NXP Experts, I am trying to write and read data to the IAP flash memory on the LPC865M201JHI48 microcontroller. My condition is that I want to write and read data for different pages of one sector. Case 1: Data = 10 Sector = 60 Data1 Address = 0x0000F000 Page = 960 Case 2: Data = 3999 Sector = 60 Data2 Address = 0x0000F040 Page = 961 Case 3: Data = 200 Sector = 60 Data3 Address = 0x0000F080 Page = 962 Case 4: Data = 1234 Sector = 60 Data4 Address = 0x0000F0C0 Page = 963 I am trying to write the data individually to single pages. In Case 1, I write data to the address 0x0000F000 and read the data using the same address. I get the correct data that I wrote. Later, I use Case 2 with the address 0x0000F040, and I read the data using the same address. I get the correct data perfectly as I wrote before. However, whenever I try to write to both addresses at the same time (0x0000F000 and 0x0000F040), the last written address prints the correct data, but the first written address prints garbage values. My question is, can I write and read a single page of data at one time? Is this true? #read part : #define dummy_ADD   0x0000F000 #define dummy_ADD1 0x0000F040 uint32_t dum,dum1; dum = IAP_ReadFlash(dummy_ADD); printf(dum) dum1 = IAP_ReadFlash(dummy_ADD1); printf(dum1) uint32_t IAP_ReadFlash(uint32_t FLASH_DATA_ADDRESS) { uint32_t *flashAddress = (uint32_t *)FLASH_DATA_ADDRESS; uint32_t data = *flashAddress; // Read the data from the flash memory address return data; } LPC800 Re: How To read the IAP Flash Memory read on LPC865 I want to configure USART0 with TX on P0_4 and RX on P0_1. Re: How To read the IAP Flash Memory read on LPC865 Hi, @Alice_Yang you are great! Thank you so much for your wonderful effort.   Alice, I am new to NXP controllers. Previously, I had been working on STM32 controllers, where I found it easy to configure the USART peripherals using the IOC configuration tool. We just had to select the UART number, choose synchronous or asynchronous mode, set the baud rate, and data length, and the code would be auto-generated. In a similar way, if I want to configure the UART in the LPC865, how should I go about it? Could you share a screenshot of the configuration process? Re: How To read the IAP Flash Memory read on LPC865 Hello @BerlinRaj  There are many errors in your code. So refer to your requirements, I create a project for you.  I have tested on my side, there is no issue when writing two pages and reading. From the result, we can see write to flash 78 and 190. They are read back correclty. I attach my project  for you.  Hope it helps. BR Alice Re: How To read the IAP Flash Memory read on LPC865 hii @Alice_Yang , i just try to write the code this console consider, i have to stored the VERSION and Temperature on the IAP FLASH Memory, and i displayed theVERSION and Temperature value with 1.8 inch TFT DISPLAY. uint32_t DEMO_IAP_FLASH_SECTOR = 63;//sector number uint32_t PAGE_SIZE_BYTES = 64; #define SECTOR_SIZE_BYTES (1024) static uint32_t s_IapFlashAddress = 64512;//=>1008(page_num)*64(page size) static uint32_t s_IapFlashAddress1 = 64576;//=>1009(page_num)*64(page size) int main() { TFT_Init(); home_screen(); while(1) { } } void home_screen() { static uint32_t s_PageBuf=78; static uint32_t s_PageBuf1=190; Erace(DEMO_IAP_FLASH_SECTOR); Writing_Data _one(s_PageBuf); Writing_data_two(s_PageBuf1); //read part uint32_t *read_ptr = (uint32_t *)(s_IapFlashAddress); uint32_t Version_value = *read_ptr; uint32_t *read_ptr1 = (uint32_t *)(s_IapFlashAddress1); uint32_t Temp_value = *read_ptr; print_tft(145, 2,Version_value , YELLOW_COLOR, BLUE_COLOR); print_tft(145, 20,Temp_value , YELLOW_COLOR, BLUE_COLOR); } void Write_data_one(uint32_t s_PageBuf) { IAP_FLASH_WRITE(DEMO_IAP_FLASH_SECTOR,s_IapFlashAddress,s_PageBuf,PAGE_SIZE_BYTES); } void Write_data_two(uint32_t s_PageBuf1) { IAP_FLASH_WRITE(DEMO_IAP_FLASH_SECTOR,s_IapFlashAddress1,s_PageBuf1,PAGE_SIZE_BYTES); } void IAP_FLASH_WRITE(uint32_t DEMO_IAP_FLASH_SECTOR,uint32_t FlashAddress,uint32_t s_PageBuf,uint32_t PAGE_SIZE_BYTES) { // IAP_PrepareSectorForWriteone(DEMO_IAP_FLASH_SECTOR, DEMO_IAP_FLASH_SECTOR); // IAP_EraseSectorone(DEMO_IAP_FLASH_SECTOR, DEMO_IAP_FLASH_SECTOR, SystemCoreClock); IAP_PrepareSectorForWriteone(DEMO_IAP_FLASH_SECTOR, DEMO_IAP_FLASH_SECTOR); IAP_CopyRamToFlashone(FlashAddress, &s_PageBuf,PAGE_SIZE_BYTES, SystemCoreClock); } void Erace(uint32_t DEMO_IAP_FLASH_SECTOR) { IAP_PrepareSectorForWriteone(DEMO_IAP_FLASH_SECTOR, DEMO_IAP_FLASH_SECTOR); IAP_EraseSectorone(DEMO_IAP_FLASH_SECTOR, DEMO_IAP_FLASH_SECTOR, SystemCoreClock); } void IAP_PrepareSectorForWriteone(uint32_t startSector, uint32_t endSector) { uint32_t command[5] = {0x00U}; uint32_t result[5] = {0x00U}; command[0] = (uint32_t)kIapCmd_IAP_PrepareSectorforWrite;//50u command[1] = startSector; command[2] = endSector; iap_entry(command, result); } void IAP_EraseSectorone(uint32_t startSector, uint32_t endSector, uint32_t systemCoreClock) { uint32_t command[5] = {0x00U}; uint32_t result[5] = {0x00U}; command[0] = (uint32_t)kIapCmd_IAP_EraseSector;//52u command[1] = startSector; command[2] = endSector; // command[3] = systemCoreClock / HZ_TO_KHZ_DIV; iap_entry(command, result); } void IAP_CopyRamToFlashone(uint32_t dstAddr, uint32_t *srcAddr, uint32_t numOfBytes, uint32_t systemCoreClock) { uint32_t command[5] = {0x00U}; uint32_t result[5] = {0x00U}; command[0] = (uint32_t)kIapCmd_IAP_CopyRamToFlash;//51u command[1] = dstAddr; command[2] = (uint32_t)srcAddr; command[3] = numOfBytes; // command[4] = systemCoreClock / HZ_TO_KHZ_DIV; iap_entry(command, result); } Whenever I write the above program, the FLASH MEMORY writes and reads the data properly. However, whenever I hide the #Erace(DEMO_IAP_FLASH_SECTOR); function, the first data is not read properly, but the second data is read well. Why? explain  these below two function if i hide why first data should not printed. IAP_PrepareSectorForWriteone(DEMO_IAP_FLASH_SECTOR, DEMO_IAP_FLASH_SECTOR); IAP_EraseSectorone(DEMO_IAP_FLASH_SECTOR, DEMO_IAP_FLASH_SECTOR, SystemCoreClock); Re: How To read the IAP Flash Memory read on LPC865 Yes, I have an issue with my code! I can't post the code because of my company's policy. Anyway, I will try to send my issue through a private ticket.. thank you @Alice_Yang  Re: How To read the IAP Flash Memory read on LPC865 Hello @BerlinRaj  Yes, you can write and read more data for a single page.  I recommend you debug step by step to check.  If you still have issue, and do not want to publish your code. You can also create a private ticket.  https://support.nxp.com/s/?language=en_US   BR Alice Re: How To read the IAP Flash Memory read on LPC865 hi, @Alice_Yang  thank you for your reply. i can write and read each data on a single page,can you tell me can i write and read more data for a single page? Re: How To read the IAP Flash Memory read on LPC865 Hello @BerlinRaj  For better help you, please share your project. I will help you check on my side. Thanks. BR Alice
View full article
i.MX7D RS485 problems Hi, I'm trying to get RS485 running on our custom i.MX7D based board. I can write some data to RS485 correctly, but when any data is received, there are some random data automatically generated to the line probably by imx.c driver. I have tried to interconnect 2 RS485 lines, open them from C++ code and just write few bytes to one of them and it results in endless pinging of random data on the line. Both RS485 are working in half-duplex mode with SN65HVD1780 chip, direction control using RTS as GPIO. Devicetree (UARTS are aliased to ports 2,3): &uart4 { pinctrl-names = "default"; pinctrl-0 = <&pinctrl_uart4>; assigned-clocks = <&clks IMX7D_UART4_ROOT_SRC>; assigned-clock-parents = <&clks IMX7D_OSC_24M_CLK>; rts-gpios = <&gpio3 21 GPIO_ACTIVE_HIGH>; //DIR control linux,rs485-enabled-at-boot-time; rs485-rts-delay = <1 1>; // in milliseconds status = "okay"; }; &uart6 { pinctrl-names = "default"; pinctrl-0 = <&pinctrl_uart6>; assigned-clocks = <&clks IMX7D_UART6_ROOT_SRC>; assigned-clock-parents = <&clks IMX7D_OSC_24M_CLK>; rts-gpios = <&gpio3 22 GPIO_ACTIVE_HIGH>; //DIR control linux,rs485-enabled-at-boot-time; rs485-rts-delay = <0 1>; // in milliseconds status = "okay"; }; Part of testing code: bool InitRS485(int fd) { struct serial_rs485 rs485conf; rs485conf.flags |= SER_RS485_ENABLED; //Enable RS485 mode rs485conf.flags |= SER_RS485_RTS_ON_SEND; //Set logical level for RTS pin equal to 1 when sending rs485conf.flags &= ~(SER_RS485_RTS_AFTER_SEND); //Set logical level for RTS pin equal to 0 after sending rs485conf.delay_rts_before_send = 1; //Set rts delay before send rs485conf.delay_rts_after_send = 1; //Set rts delay after send if(ioctl(fd, TIOCSRS485, (void*)&rs485conf) == 0) { struct termios tty; //Get current settings if(tcgetattr(fd, &tty) == 0) { tty.c_cflag &= ~PARENB; //No Parity tty.c_cflag &= ~CSTOPB; //1 Stop Bit tty.c_cflag &= ~CSIZE; tty.c_cflag |= CS8; //8 Bits cfsetspeed(&tty, 19200); //Set baudrate if(tcsetattr(fd, TCSANOW, &tty) == 0) //Set settings to port { return true; } } } return false; } void rs485TaskTest1() { int fd = open("/dev/ttymxc2", O_RDWR); if (InitRS485(fd)) { const uint8_t data[] = { 0x11, 0x01, 0x02, 0x32, 0x00}; write(fd, data, sizeof(data)); } close(fd); } void rs485TaskTest2() { int fd = open("/dev/ttymxc3", O_RDWR); if (InitRS485(fd)) { while (1) { std::this_thread::sleep_for(100ms); } } close(fd); } As you can see, I'm writing on first RS485 and just opening port on second with sleeping. Result caught on analyzer (1 - DIR, 2 - RX, 3 -TX): As you can see, there is also problem, that on first transition with normal data, RTS delay before send (delay_rts_before_send) is not applied. On randomly generated transitions it is applied correctly. Any ideas, what am I doing wrong, or I have hit some kind of bug? I'm running kernel version 5.15.52. I have tried to backport changes in imx.c from 6.x kernel, but with same results. Thanks in advance, Michal Špánik Re: i.MX7D RS485 problems Hi, I found call to cfmakeraw() in second test code, which seems to solve the issue. It was caused by ISIG flag, which is set by default and probably triggers on transferred data in our protocol/my test scenario. Thank you very much for your support, Michal Špánik Re: i.MX7D RS485 problems Hello, Have you tried usin latest kernel instead of backporting? Also, you may try using test code we have available under unit_test: https://github.com/nxp-imx/imx-test/blob/lf-6.6.3_1.0.0/test/mxc_mcc_tty_test/mxc_mcc_tty_test.c https://github.com/nxp-imx/imx-test/blob/lf-6.6.3_1.0.0/test/mxc_uart_test/mxc_uart_test.c Best regards/Saludos, Aldo. Re: i.MX7D RS485 problems To simplify the usecase, this happens, when I echo "12345" > /dev/ttymxc3 with interconnected port 2 and 3 (port 2 is with connected analyzer) It seems OK. But when I run cat /dev/ttymxc2 and echo "12345" > /dev/ttymxc3 which opens the receiving port (but does not process data in any way), it looks like this: It seems, that data is automatically echoed back to transmit after receive (even with correct RTS). If I disable DMA, First byte is echoed immediately and rest of data is cut (because of direction change).
View full article
S32K3XX_IOMUX MISSING. Hi team,  I seen Missing Pins In IOMUX PTB6 and PTB7 pins Not Available in IOMUX can I know the what is the Reason behind pin not availability. PF Snippet in that directly pin Available PTB5 After PTB8. thank u  Re: S32K3XX_IOMUX MISSING. Hello @gadilinga , As S32K3 is the next gen of S32K1, PTB6 and PTB7 is just a "gap" in the pin naming, caused by removing possibility to configure XTAL/EXTAL pins as GPIO. Best regards, Pavel
View full article
S32K3 Lin从模式问题 尊敬的S32K3团队: 我希望你一切安好。 我目前在尝试使用 S32K311 上的 LIN-LPUART 进行通信时遇到问题,希望请求您的帮助。下面,我概述了我遇到的问题,非常感谢您提供的任何解决方案或指导。 1.在主模式下,当以响应 rx 格式传输 LIN 数据时,Canoe 检测到“同步分隔符长度不正确”错误。 1.1.尽管如此,Canoe 还是发送了响应,但 LIN IRQ 处理程序检测到帧错误,从而阻止传输正确的响应。 2.我需要一个从属模式的示例。(RTD版本:SW32K3_RTD_R21-11_3.0.0_P07) 2.1.在从属模式下初始化并运行程序后,我观察到当从 Canoe 发送消息时,LIN 总线的波形与 LPUART-RX 引脚匹配。但是,没有发生中断,并且没有触发 IRQ 处理程序。 我真诚希望得到有关这些问题的指导或解决方案。 非常感谢您付出的时间和帮助。 顺祝商祺!
View full article
S32K3 Lin スレーブ モードの問題 S32K3チームの皆様へ このメッセージがあなたによく伝わることを願っています。 現在、S32K311でLIN-LPUARTを使用して通信を試みる際に問題が発生しており、サポートをリクエストしたいと思います。以下では、私が遭遇している問題の概要を説明しましたので、解決策やガイダンスを提供していただければ幸いです。 1.マスターモードでLINデータをresponse-rx形式で送信する際に、Canoeが「同期区切り文字の長さが正しくありません」というエラーを検出します。 1.1.それにもかかわらず、Canoe は応答を送信しますが、LIN IRQ ハンドラーはフレーミング エラーを検出し、正しい応答が送信されません。 2. スレーブモードの例が必要です。(RTDバージョン:SW32K3_RTD_R21-11_3.0.0_P07) 2.1.スレーブモードで初期化してプログラムを実行したところ、Canoeからメッセージを送信すると、LINバスの波形がLPUART-RXピンと一致することが確認されました。ただし、割り込みは発生せず、IRQ ハンドラはトリガされません。 これらの課題について、ご指導や解決策をいただけることを心から願っております。 ご多忙のご協力をいただき、誠にありがとうございました。 よろしくお願いいたします。
View full article
S32K3 Lin Slave Mode Issue Dear S32K3 Team, I hope this message finds you well. I am currently facing issues while attempting communication using LIN-LPUART on the S32K311 and would like to request your assistance. Below, I have outlined the issues I am encountering and would greatly appreciate any solutions or guidance you can provide. 1. In master mode, when transmitting LIN data in the response-rx format, Canoe detects an "Incorrect sync delimiter length" error. 1.1.  Despite this, Canoe sends a response, but the LIN IRQ handler detects a framing error, preventing the correct response from being transmitted. 2. I require an example for the slave mode. (RTD Version: SW32K3_RTD_R21-11_3.0.0_P07) 2.1.  After initializing in slave mode and running the program, I observed that the waveform of the LIN bus matches the LPUART-RX pin when a message is sent from Canoe. However, no interrupt occurs, and the IRQ handler is not triggered. I sincerely hope to receive guidance or solutions regarding these issues. Thank you very much for your time and assistance. Best regards, Re: S32K3 Lin Slave Mode Issue Hi, 1) this can point to bit timing issue. Be sure bitrate is set similarly. You can measure geenrated signal on TX/RX if it as expected. 2) here are two RTD demos you can refer to, where LPUART is used as LIN Slave - "Lin_Ip_FrameTransfer_S32K344"...  simple application which shows a communication between a Lin Master and a Lin Slave of both Lpuart Ip and Flexio Ip  - "Lin_Slave_S32K344_Example_DS" ... LINStack example demonstrating the LIN communication between S32K344 Slave and other board Master using unconditional frames. There is no direct example for S32K311, but you can reuse existed one to create new. For slave mode be sure module interrupt is properly enabled and Auto-detect baudrate feature is properly implemented, as shown in the example and described in  the chapter 3.6.5 Auto-detect baudrate feature of RTD_LIN_43_LPUART_FLEXIO_UM.pdf BR, Petr
View full article
Single-ended CLRC663 RF design Hi,  I have a question related to the single-ended CLRC663 RF circuit design. The datasheet mentions that the receiver can be configured in single-end mode by connecting RxN and RxP and setting the quasi differential mode in the rcv_rx_single register.  May I know how to configure the single-ended mode for TxN and TxP? Can I connect TxN and TxP? If so, is there any register setting for the TxN and TxP? Thanks, Heng NFC Frontend Solutions Re: Single-ended CLRC663 RF design Hi Tomas, Thanks for the confirming. Heng Re: Single-ended CLRC663 RF design Hello hengma,  Yes, for single ended, the target impedance would be around 10 Ohms.  Once you tune your system to 10 Ohm, please also check the trasmitter current. You should not exceed the maximum TVDD current.  BR Tomas  Re: Single-ended CLRC663 RF design Hi Tomas, One more question, what is the desired impedance for the single-end solution? For the differential solution, the desired impedance is between 18 and 20 ohms for maximum field strength and power transfer. For the single-end solution, will the desired impedance become 10 ohms when measuring the TX and GND? Thanks, Heng Re: Single-ended CLRC663 RF design Hello @hengma ,  Correct, Once both Tx paths are anabled and they are in phase. The maximum power of the TX driver can be used.  If only one TX side is enabled (TxEn), the power is reduced by 50%.  BR Tomas  Re: Single-ended CLRC663 RF design Hi Tomas, Thanks for your prompt reply. In order to use a single-ended transmitter solution, shall I configure both Tx1Inv and Tx2Inv to 1 or 0? In this case, both TxN and TxP will deliver a non-inverted or inverted 13.56 MHz carrier, which is in phase.  Also, may I know the setting of TxEn? Can we define the source of the transmitter using the setting of TxEn? Thanks, Heng Re: Single-ended CLRC663 RF design Hello hengma, You should be able to change the phase of the TX signal using the following register. If both signal are in phase (TX1 and TX2). You should be able to connect them and get proper signal and waveform.  BR Tomas 
View full article
imx-voiceui をコンパイルできません こんにちは、私はiMX93 EVKボードを使用してプロジェクトに取り組んでおり、現在imx-voiceuiのコンパイルで問題に直面しています。 私のVIT_KOモデルで 'voice_ui_app'を得るためには、それをコンパイルする必要があります。しかし、"make" を実行するたびに、常に次のエラーが発生します。 /usr/bin/ld: ./platforms/iMX9_CortexA55/lib/libvoiceseeker_no_aec.a(VOICESEEKER_OBJ_0.o): 汎用ELFでの再配置 (EM: 183) /usr/bin/ld: ./platforms/iMX9_CortexA55/lib/libvoiceseeker_no_aec.a(VOICESEEKER_OBJ_0.o): 汎用ELFでの再配置 (EM: 183) /usr/bin/ld: ./platforms/iMX9_CortexA55/lib/libvoiceseeker_no_aec.a(VOICESEEKER_OBJ_0.o): 汎用ELFでの再配置 (EM: 183) /usr/bin/ld: ./platforms/iMX9_CortexA55/lib/libvoiceseeker_no_aec.a: シンボルの追加エラー: ファイルの形式が間違っています collect2: エラー: ld が 1 つの終了ステータスを返しました SDKをインストールし、iMX93のツールチェーンを調整しようとしましたが、問題は解決しませんでした。さらに、 ${CC} および ${CXX} ツールチェーン変数を使用するように 'Makefile' を変更しましたが、問題は解決しません。 どうすればこれを修正できますか?どんな助けでも大歓迎です。 Re: imx-voiceui をコンパイルできません 問題を解決しました。通常のユーザーアカウントから 'sudo' を使用して make コマンドを実行する代わりに、root アカウントを使用してプロジェクトを正常にコンパイルしました。
View full article
Compatibility issues of different versions of guiguider I hope that when the official version is updated, it can still be compatible with the previous low-version project upgraded to the high-version version. Also, I created the official sample project ButtonCounter in 1.7.2, and then opened it with 1.8.0guiguider. It prompted to upgrade. After the upgrade, the compilation reported an error and duplicate definitions of variables appeared. Re: 不同版本guiguider该工程兼容问题 Hello @ZYQ, Thanks a lot for your feedback, we have reproduced the upgrade issue from V1.7.2 to 1.8.0 and will solve it in the future release. About upgrade project from old version to new version, GUI Guider now support upgrade from last major release, For example the V1.8.X will could import project created by V1.7.X. If you need upgrade project across major version, upgrade your project multiple times could be a choice, for example: import your V1.5.x project into V1.6.X, make sure the project work properly. import upgraded project into V1.7.x , make sure the project work properly.  import it into latest Version V1.8.0. note that cross multiple major versions might have some upgrade issues, please check and fix manually. Hope this could help you. Best Regards, Wenbin
View full article
LPC865, I3C HDR模式 SDA和SCL边沿相位间隔太短. 在波形解析HDR数据时, 看到HDR模式下SCL双边沿采集SDA过于极限, 请问是否有软件配置可以修改SDA相位的? 在SDR下发送CCC进入HDR模式后, 在HDR的 Preamble 及之后的HDR数据中, 采样太极限了. 这里用 Preamble 示例:   这就导致许多示波器都不能正确的解码I3C协议. Re: LPC865, I3C HDR模式 SDA和SCL边沿相位间隔太短. Hi @Zahi  在 LPC865 的 I3C 外设中,SDA 的采样相位是由硬件控制的,不允许直接通过软件调整 SDA 的相位。 BR Harry
View full article
不同版本guiguider该工程兼容问题 希望官方在进行大版本更新的时候还是能够兼容跨版本的以前低版本工程升级到高版本 还有就是我在1.7.2中创建官方示例工程ButtonCounter ,然后使用1.8.0guiguider打开,提示升级,升级后编译报错,会出现变量的重复定义
View full article
ソフトウェアでリセットソースを検出します こんにちは: MCUがブートローダーにジャンプするときにS32K312でリセットソースを検出する機能を実行したいのですが、参照用のソースコードはありますか?どうもありがとうございました。
View full article