Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
加密的QuadSPI映像实现 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 加密的QuadSPI映像实现 Kinetis 系列 MCU 包括系统安全和闪存保护功能,可用于保护代码和数据免遭未经授权的访问或修改。本应用说明讨论了使用 KBOOT 加密启动以及使用 FRDM-K82 板的实验。 FRDM-K82板 Freedom开发平台 Kinetis K系列MCU
View full article
NAND坏块标记 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 即使是新的,NAND 设备也可能有坏块。坏块可能是某个位发生故障或无法正确擦除的块。供应商通常会为每个部件提供已知现有坏块的预建地图。工厂坏块在每个块的第一页上的工厂坏块标记偏移量中用非 0xFF 值进行标记。 对于小页设备,此工厂偏移量通常为页面中的字节 516 和 517。对于大页面设备,此工厂偏移量通常为 2048。您可以通过扫描 NAND 设备上每个块的第一页并检查数据中的工厂坏块标记偏移量中的值是否为非 0xFF 值来获取坏块列表。 SLC NAND 控制器和所有 NXP 为 SLC NAND 控制器开发的软件(Linux、WinCE 或独立软件)使用与工厂标记相同的位置进行坏块标记和检测。因此,NAND 设备不需要对坏块进行特殊处理或重新定位。 MLC NAND 控制器只能以 528 字节的块读取和写入带有 ECC 的数据。因此,数据和 ECC 值在 NAND 页面中交错。此方案的工厂坏块标记无法使用。如果必须将 MLC NAND 控制器用于芯片启动以外的任何用途,则需要在将数据写入设备之前记录并移动工厂坏块标记。对于使用 MLC 控制器在 LPC32x0 上进行 NAND 启动的块 0,任何 NXP 软件均不使用坏块检测或标记。这是因为 NAND 设备制造商通常只保证有限次数(即 1000 次)写入周期内块 0 的数据可靠性。
View full article
AMF-DES-T2305 - 普通人理解的电磁场:请给我看图并记住方程式 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 所呈现的材料将集中于电磁能基本原理的物理学,并以易于理解的语言和大量图表呈现。与会者将发现了解电磁场的行为如何有助于设计更坚固且具有更好的 EMC 性能的 PCB。这不是火箭科学,而是一个易于理解的 PCB 几何应用。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 所呈现的材料将集中于电磁能基本原理的物理学,并以易于理解的语言和大量图表呈现。与会者将发现了解电磁场的行为如何有助于设计更坚固且具有更好的 EMC 性能的 PCB。这不是火箭科学,而是一个易于理解的 PCB 几何应用。
View full article
NXP FTF Connects - 底特律 - 2016年10月5日至6日 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 安全互联汽车和自动化汽车 AMF-AUT-T1811 - 联网汽车的四层汽车安全保障 AMF-AUT-T2366 - 面向汽车市场的先进标准产品包装 AMF-AUT-T2411 - Altia:打破汽车电子驾驶舱设计挑战 AMF-AUT-T1764 - 为 V2X 通信创建安全网络 AMF-AUT-T1944 - 设计未来汽车:i.MX 8 虚拟化和媒体功能,助力下一代电子驾驶舱 AMF-AUT-T2345 - 更快的电机控制开发 AMF-AUT-T2341 - 汽车边缘节点固件更新 AMF-AUT-T2363 - 功能安全方法和能力 AMF-AUT-T2358 - 功能安全电源 SBC:FS6500 / FS4500 AMF-AUT-T2344 - 实践研讨会:S32K 的 MCT - MATLAB/Simulink 建模和代码生成 AUT-N1891 动手实践研讨会:不到 10 分钟即可完成 NXP eXtreme 交换机的编程.pdf AMF-AUT-T2346 - 实践研讨会:S32K、设计工作室和 SDK AMF-AUT-T1782 - 传感器融合和自动驾驶车辆算法简介 AMF-AUT-T1823 - 推出具有功能安全性和更高扭矩的新型 SPI 控制有刷直流电机驱动器 AMF-AUT-T2324 - 制造工具 AMF-AUT-T2353 - 基于 MOSFET 的 H 桥车窗升降装置 AMF-AUT-T2343 - S32K 和 MagniV 概述 AMF-AUT-T2354 - 面向汽车边缘节点的 S32K 安全 AMF-AUT-T2325 - S32V234 ADAS 视觉处理器概述 AMF-AUT-T2371 - 通过 IGBT 栅极驱动器的改进简化您的逆变器 AMF-AUT-T2364 - S32V 的软件提示和技巧 AMF-AUT-T2348 - NXP 音频视频桥接 (AVB) 堆栈 AMF-AUT-T2347 - 恩智浦 IVI 平台 AMF-AUT-T2349 - 恩智浦可信执行环境 (TEE) 堆栈 AMF-AUT-T1813 - 车辆架构趋势 AMF-AUT-T2367 - TPMS 本地化 视频演示:FTF-AUT-N1773 - 安全 V2X 简介 视频演示:FTF-AUT-N1788 - BlueBox - 强大的大脑,助力设计安全、可靠且运动规划系统的自动驾驶汽车 AMF-AUT-T2323 - 适用于 S32V 系列的视觉 SDK AMF-AUT-T2310 - 面向 BSP 开发人员的 Yocto Project ™工具 设计、软件与服务 AMF-DES-T2412 - Cog Systems:推出 D4 Secure SDK - 利用虚拟化构建安全连接设备 AMF-DES-T2409 - DornerWorks:i.MX 8 应用处理器上的 Xen AMF-DES-T2304 - 高效印刷电路板设计:提高性能的技术 AMF-DES-T2305 - 普通人理解的电磁场:请给我看图并记住方程式 AMF-DES-T2360 - EMI 变得简单:一切都与空间有关! AMF-DES-T1740 - i.MX 8 和 Vulkan API - 高性能图形实现的未来 AMF-DES-T1894 - 使用 i.MX 应用处理器进行加密密钥管理的技术 AMF-DES-T1939 - 教你看世界:i.MX 8 视觉架构简介 AMF-DES-T2001 - 轻松配电 AMF-INS-T2024 - 半导体 101/102:集成电路的功能和制造 AMF-DES-T2352 - 使用适用于 i.MX 应用处理器的全新“引脚工具” 回复:恩智浦 FTF Connects - 底特律 - 2016 年 10 月 5-6 日 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 嗨,蕾妮, 我参加了底特律 FTF 有关 CAN FD 的会议。我没有看到这里的幻灯片。您也可以将其上传到这里吗?
View full article
在低功耗模式下运用ADC范围比较模式实现恒温控制 最近在论坛、QQ群里好多人都在讨论低功耗设计,想到之前遇到的一个客户也有这方面的一个要求,顺着他的想法做了一个在低功耗模式下使用ADC的例子。客户要做的是一个恒温控制,在设定温度范围内让MCU进入休眠状态,只有在超过温度范围后才唤醒MCU进行温度调节。话不多说,让我们开始例程介绍。 运行平台: FRDM-25Z IARv7.3 在KL25_SC代码包中platinum工程上修改 Low Power Mode 简介 飞思卡尔Kinetis系列MCU基于90纳米TFS技术,使得MCU在低功耗模式下,拥有良好的性能和功耗表现,KL系列更是被评为业内最低功耗的MCU。KL25Z 功耗模式总共有 11 种,分别是:Run、VLPR、Wait、VLPW、Stop、VLPS、LLS、VLLS3、VLLS2、VLLS1、VLLS0,能够满足客户对MCU各种低功耗的配置要求,在深度睡眠模式下智能外设能够处理相应数据而不需要唤醒内核。    图1 在本设计中需要在低功耗模式下监控温度,热电偶的电信号需要用到ADC进行采样,查手册可知ADC能够运行的最低功耗模式是VLPS模式。VLPS模式下大部分外设仍然可以使用,但需要注意的是在VLPS模式下总线时钟是禁止的,因此在进入VLPS模式前应该将ADC的时钟设为ADACK,不然它进入VLPS模式后就嗝屁了。VLPS模式下只能采用硬件触发来触发ADC采样,本例采用的是LPMR定时器来触发ADC采样。VLPS模式下可以采用中断唤醒方式,本例采用ADC中断唤醒。当然也可以采用异步DMA通道来搬运ADC转换结果,搬运完成后自动回到VLPS模式下,感兴趣的话也可以试一下这种方式哈。   图2 代码介绍:    int main (void) {      #ifdef CMSIS  // If we are conforming to CMSIS, we need to call start here     start(); #endif          lptmr_init(1000,LPTMR_USE_LPOCLK);   //trigger ADC per 1000ms     // 初始化代码中设置LPO作为lptmr的时钟源,保证lptmr在VLPS下能够正常工作;     init_ADC16();                                                                                          //初始化ADC,设置ADC硬件触发源为lptmr,使能ADC范围比较模式,即当转换结果小于C1V,大于C2V时保存结果;     enable_irq(ADC0_irq_no);                                                                      //在进入低功耗模式前使能ADC中断。     printf("Enter VLPS mode...\r\n");     clockMonitor(OFF);     enter_vlps();     while(1)   {                  if(flag_wakeup == 1)           {             flag_wakeup = 0;             ADC0_SC2 &= ~ADC_SC2_ACFE_MASK;              disable_irq(ADC0_irq_no);                                                              //退出后,为调节温度需关闭范围比较模式,同时关闭ADC中断,采用查询模式;             printf("Wake up from VLPS..\n");             printf("adcresult = %d\n",adcresult);           }                              if((ADC0_SC1(0) & ADC_SC1_COCO_MASK) == ADC_SC1_COCO_MASK)     //查询转换结果           {             adcresult = ADC0_R(0);             printf("wake up adcresult = %d\n",adcresult);             if((adcresult>= 4000) && (adcresult<= 5000))                                   //当调节到ADC结果再次进入调节范围时,准备进入低功耗模式;             {               ADC0_SC2 |= ADC_SC2_ACFE_MASK;                                         //为实现监控,重新使能范围比较模式和ADC中断。               enable_irq(ADC0_irq_no);               printf("Enter VLPS mode...\n");               clockMonitor(OFF);               enter_vlps();             }           }              } }        实验结果:      设置比较值为4000~5000,打印结果如下: 图3       好了,就这些了,第一次写技术文章,很浅显的东西说了一大堆,比较乱,望批评指正哈。       附件为参考代码。 Re: 在低功耗模式下运用ADC范围比较模式实现恒温控制 Hi FanXi,非常感谢!实测电流是多少呢?
View full article
Share Design Experience Using i.MX Applications Processors based on ARM® Cortex®-A7 and Cortex-A9 Cores Share design experience on Freescale i.MX applications processors. Presented by Jim Lin Presented at DwF Taipei - May 7, 2015 Session ID: APF-SHB-T1452 Share design experience on Freescale i.MX applications processors. Presented by Jim Lin Presented at DwF Taipei - May 7, 2015 Session ID: APF-SHB-T1452 i.MX Applications Processors
View full article
基于 LS2085 NADK 的 IPSEC 应用程序与 AIOP 通信 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 在LS2085平台上,基本网络产品在AIOP上执行自主IP转发和IPSEC,数据路径功能大多独立于GPP软件运行,并且仅在必要时涉及GPP。 NADK(网络加速开发套件)是一个完整的用于网络应用程序的用户空间开发套件。 该IPSEC应用程序使用NADK框架在Linux用户空间中实现,该应用程序通过netlink事件通知学习Linux配置,并使用相应的NF API将配置发送到AIOP DP。应用程序调用 NF API 将配置详细信息发送到 AIOP 上的 IPsec 数据路径。 1.基于AIOP-NADK的IPSEC应用概述及架构 2.基于NADK的GPP监听器程序设计 2.1 应用程序中使用的NADK API介绍 2.2 多线程模式下NADK应用程序的数据包处理 2.3 监听器监控的IPSEC XFRM事件 3. IPSEC应用程序通过NF API与AIOP通信 3.1 AIOP 实现的 IPSEC 功能 3.2 用于配置AIOP的IPSEC NF API 3.3 在IPSEC应用中添加SPD策略的流程 4. 设置网络环境以验证 IPSEC 应用程序 QorIQ LS2 设备
View full article
iMX28 WinCE 6.0 UART 驱动程序更新以修复 RX DMA 数据丢失问题。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 最新的 iMX28 WinCE 6.0 BSP“WCE600_MX28_SDK1008”存在 UART RX DMA 数据丢失问题。 测试用例以重现该问题: 使用 UART 电缆连接 iMX28 UART1 和 PC,然后在 iMX28 和 PC 端运行一些 UART 测试应用程序,PC 可以向 IMX28 发送文件,文件大小应大于默认 RX DMA 缓冲区大小 1024 字节,然后从 iMX28 端,将会丢失数据。 附件“SERIALAPP.zip”是更新的UART驱动程序代码,用于修复此问题,您可以解压缩并将其更新到“ wince600\platform\common\src\soc\common_fsl_v2_pdk1_9\serialapp ”文件夹,并重建WinCE映像。 本次更新针对 UART RX DMA 实现了以下改进: 1.添加DMA恢复代码。 当 DMA 模式下发生 UART 错误时,驱动程序将重新初始化 DMA 以进行下一次传输。 2.将UART DMA超时中断设置为5ms。“#定义SERIAL_DMA_RX_TIMEOUT 5” UART DMA中断发生后,IST需要将数据从DMA缓冲区复制到MDD缓冲区,因此需要时间。默认的BSP已经把这个延迟设置为31位传输时间,这个时间非常短,如果PC向iMX28发送“DMA缓冲区+1”个字节,在第一次DMA缓冲区满中断发生后,很快就会发生第二次DMA超时中断,这个中断将会丢失,因为驱动程序仍在处理预中断。 3. 更新 MDD 代码以确保发送到 PDD 的缓冲区始终大于 RX DMA 缓冲区。 此 MDD 代码修改仅在 DMA 模式下有效,因此对 PIO 模式没有影响。 4.更新UART DMA中断处理程序代码。 当发生UART DMA中断时,立即设置下一次DMA传输,这样DMA就可以继续用另一个DMA缓冲区接收数据,同时IST会将数据从预DMA缓冲区复制到MDD缓冲区。 回复:iMX28 WinCE 6.0 UART 驱动程序更新以修复 RX DMA 数据丢失问题。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 您看到我关于这个问题的长篇文章了吗?我发现是循环缓冲区的处理导致了 RX DMA 数据丢失。这篇文章中有很多信息,但我的修复似乎与您的不同,所以看起来我可能也需要研究您的更改! i.MX28 Windows CE BSP 串行端口错误导致接收数据丢失 Mark
View full article
MAPS 启动和介绍 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 梁平主讲 基于 ARM ®技术的 DwF Kinetis MCU 南京站 — 2015 年 3 月 12 日 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 梁平主讲 基于 ARM ®技术的 DwF Kinetis MCU 南京站 — 2015 年 3 月 12 日 Arm® 处理器 Kinetis Cortex ® -M 微控制器
View full article
MMA9553L 计步器使用指南     MMA9553L是飞思卡尔的一款计步传感器,本文就如何快速使用该传感器做一个简单介绍。    你可能还见到过MMA955xL, 它与MMA9553L是什么关系呢?简单的来说MMA955xL是一个统称,它包括MMA9550L、MMA9551L、MMA9553L和MMA9559L这几个具体型号,其实这四种传感器在硬件上都是一样的。其内部主要由ColdFire 内核、模拟前端、Flash、IIC和SPI接口等部分组成,原理框图如下图所示:    它们的不同之处在于内部的Firmware不同,Firmware在芯片出厂时就已经固化在芯片里面了,不同的Firmware对于不同的功能。这里介绍的MMA9553L主要就用作计步器功能。        MMA9553L和MCU之间可以通过IIC接口或者SPI接口通讯,所以使用MMA9553L的首要前提是把MCU的IIC或者SPI调通。接口调通之后就可以来操作此传感器了。这里以IIC为例来说明。附件为参考代码。 测试平台:IAR7.2 + FRDM_KL25Z+FRDM-FXS-MULTI FRDM-FXS-MULTI开发板上带有MMA9553L,将FRDM-FXS-MULTI开发板和FRDM_KL25Z连接在一起就可以使用了。     下面分析一下源代码:        首先是调用初始化函数pedometer_init(),此函数主要调用以下几个函数:      pedometer_write_config();       // config     pedometer_enable();         // enable pedometer     pedometer_int0_enable();    // enable INT_O pin     pedometer_active();         // active MMA9553 pedometer_wakeup();   // wakeup 在此重点分析前两个函数。第一个函数 pedometer_write_config(),该函数的具体实现如下: void pedometer_write_config(void) {     unsigned char Buf[]={0x15,0x20,0x00,0x10,                            0x0C,0xE0,                            0x13,0x20,                            0x00,0x96,                            0x60,0x50,                            0xAF,0x50,                            0x04,0x03,                            0x05,0x01,                            0x00,0x00};     dvMMA9553_Write(MMA9553_Slave_Addr, MMA9553_Sub_Addr, Buf, 20); } 此函数很简单,就是通过IIC给9553发送一条命令,命令的内容Buf数组中的20个字节    的数据。 dvMMA9553_Write()函数的第一个参数代表MMA9553L的地址,为0x4C。datasheet中有说明。 #define MMA9553_Slave_Addr  0x4C dvMMA9553_Write()函数的第二个参数代表寄存器地址,为0x00。 #define MMA9553_Sub_Addr    0x00 发送的这一串命令:0x15,0x20,0x00,0x10,0x0C,0xE0,0x13,0x20,0x00,0x96,0x60,0x50,0xAF,0x50,0x04,0x03,0x05,0x01,0x00,0x00 具体是什么含义呢? 0x15:表示Application ID,计步器的Application ID就是0x15 0x20:表示这条命令是Write Config command,即这条命令是用来写Configuration 寄存器的。 0x00:表示配置寄存器的偏移地址。 0x10:表示要写16字节的内容。 0x0C,0xE0,0x13,0x20,0x00,0x96,0x60,0x50,0xAF,0x50,0x04,0x03,0x05,0x01,0x00,0x00 这16字节就是写入配置寄存器中的具体内容。 配置寄存器共用8个,分别是Sleep Minimum register,Sleep Maximum register,Sleep Count Threshold register,Configuration/Step Length register,Height/Weight register,Filter register,Speed Period/Step Coalesce register,Activity Count Threshold register,每个寄存器为16 bit(2 字节),所以总共16字节。 第二个函数 pedometer_enable(),该函数的具体实现如下: void pedometer_enable(void) {     unsigned char Buf[]={0x17,0x20,0x05,0x01,0x00};     dvMMA9553_Write(MMA9553_Slave_Addr, MMA9553_Sub_Addr, Buf, 5); } 这次写入的命令是0x17,0x20,0x05,0x01,0x00 0x17:表示Application ID 0x20:表示这条命令是Write Config command 0x05,0x01,0x00 这三个表示在偏移地址0x5处,写入一个字节的数据0x00 其他几个函数也类似,都是写入一条命令,对某种Application的配置寄存进行设置。 初始化完了,现在就可以读取步数了。 通过调用pedometer_main() 函数就可以读取到步数。 该函数的实现如下: void pedometer_main(void) {     unsigned char Buf[20];     pedometer_cmd_readstatus(); // read  status      while(1)         {            dvMMA9553_Read(MMA9553_Slave_Addr, MMA9553_Sub_Addr, Buf, 2);            if(Buf[1]==0x80)            {               dvMMA9553_Read(MMA9553_Slave_Addr, MMA9553_Sub_Addr, Buf, 16);               break;             }         }         m_status.StepCount = Buf[6] * 256 + Buf[7];         m_status.Distance  = Buf[8] * 256 + Buf[9];         m_status.Calories  = Buf[12] * 256 + Buf[13]; } 主要调用了两个函数,一是pedometer_cmd_readstatus(),这个函数的实现如下: void pedometer_cmd_readstatus(void) {     unsigned char Buf[]={0x15,0x30,0x00,0x0C};     dvMMA9553_Write(MMA9553_Slave_Addr, MMA9553_Sub_Addr, Buf, 4 ); } 它是发送了0x15,0x30,0x00,0x0C这条命令 0x15:表示Application ID 0x30:表示Read Status command 0x00:表示偏移地址 0x0C:表示需要读的字节数为12 之后调用dvMMA9553_Read()函数,通过IIC读取16字节的数据(4字节起始信息+12字节status register内容),读到的16字节数据如下: Step count register寄存器如下,通过其值可以算出步数来。    另外还可以读取三轴加速度的值,过程与读取步数是类似的,也是先写配置寄存器,然后再读取状态寄存器。   总的来说操作MMA955L的关键搞清楚有两个重要的寄存器:配置寄存器和状态寄存器。配置寄存器可读可写,状态寄存器只可读。 写配置寄存器,格式是: APP_ID+0x20+offset+number+number字节的内容 读配置寄存器,格式为: 先发送:APP_ID+0x10+offset+number, 再通过IIC读number+4字节的内容,前4字节为起始信息。 读状态寄存器,格式为: 先发送:APP_ID+0x30+offset+number,再通过IIC读number+4字节的内容,前4字节为起始信息。 读Command 回的内容如下:
View full article
Build Ubuntu For i.MX8 Series Platform The Guide is how to use Ubuntu filesystem with i.MX8 series platform.At present, I had try it on i.MX8QXP with 4.14.98 kernel with ubuntu16.04. The Document will be continuously updated with enable VPU, ubuntu18.04. The desktop we can chose Gnome or weston.  Because driver  support issue, gc7000 series gpu not support render Gnome destop but it can render weston destop.  Update 2019/7/31: Ubuntu-i.MX8-weston.pdf   Feature: weston + ubuntu18.04 + 4.14.98 kernel VPU (enable with gplay or gst-play)  GPU (could render desktop and run GPU demo under root privileges on Weston Desktop) I also try ubuntu with gnome desktop, ubuntu18.04 can not run gnome, need use ubuntu19.04. But Gnome Desktop just render by CPU.  ------------------------------------------------------------------------------------- Update 2020/3/6: Ubuntu-i.MX8M.pdf Just a simple guide for IMX8M series, will be  continuously updated.  i.MX 8 Family | i.MX 8QuadMax (8QM) | 8QuadPlus Re: Build Ubuntu For i.MX8 Series Platform I believe the Google Coral Dev Board 4GB and ASUS Tinker Edge T both use the NXP i.MX 8M processor. Hence, would the Ubuntu i.MX 8M PDF at the top of this chain be applicable? Has this instruction been updated at all? And has anyone done it/be interested in helping out? If possible, I'd be thinking go to the latest LTS of Ubuntu. Re: Build Ubuntu For i.MX8 Series Platform Hi all, I am following the guide for imx8mq guide for ubuntu 20.04, I came across an error for building weson-imx, the error is as follows. libweston/compositor-drm.c: In function ‘hdr10_metadata_set_metadata’: libweston/compositor-drm.c:7250:29: error: storage size of ‘hdr_metadata’ isn’t known struct hdr_static_metadata hdr_metadata; This query is already posted on this thread by @prashanthkumar, but there was no solution posted for it. So how can I solve this problem Re: Build Ubuntu For i.MX8 Series Platform Hii PrashanthKumar  Could you please provide me the steps for solving the below problem which you also encountered while running  sudo -E weston --tty=1 [13:03:01.810] warning: XDG_RUNTIME_DIR "/run/user/1000" is not configured correctly. Unix access mode must be 0700 (current mode is 755), and must be owned by the user (current owner is UID 1000). Refer to your distribution on how to get it, or http://www.freedesktop.org/wiki/Specifications/basedir-spec on how to implement it. [13:03:01.817] Starting with no config file. [13:03:01.821] Output repaint window is 16 ms maximum. [13:03:01.822] Loading module '/usr/lib/libweston-5/drm-backend.so' [13:03:01.830] Failed to load module: /usr/lib/libweston-5/drm-backend.so: undefined symbol: gbm_surface_get_in_fence_fd [13:03:01.830] fatal: failed to create compositor backend regards, Abhijeet Re: Build Ubuntu For i.MX8 Series Platform Refere to the yocto's  weston.ini file. Re: Build Ubuntu For i.MX8 Series Platform Hi Gnar, I want weston auto load on device startup, where can I add weston --tty=1? Re: Build Ubuntu For i.MX8 Series Platform you can refernce the yocto script to build xwayland.   But I am not sure if you use LXQT could use GPU, The best way, you should build LXQT source code with our gpu driver instead of apt-get LXQT directly. Re: Build Ubuntu For i.MX8 Series Platform how to enable xwayland in lxqt.I can install gnome-wayland only.In lxqt desktopNo xwayland related configuration options. Re: Build Ubuntu For i.MX8 Series Platform Hi,   our GPU is support wayland only. You should try build the desktop with source code and enable xwayland. Re: Build Ubuntu For i.MX8 Series Platform In Ubuntu-i.MX8M.pdf ,I did not build weston in step 7 and I apt-get install lxqt.Use lxqt as the display desktop.I get follow results: I have successfully loaded the gpu driver,But why no application uses gpu.When I do not use ubuntu filesyste,I get follow results: have 26 apps uses gpu. Please help me answer,thanks,have a nice day! Re: Build Ubuntu For i.MX8 Series Platform It guide is support use GPU when running Ubuntu file system Re: Build Ubuntu For i.MX8 Series Platform Hi,Gnar Fang Whether the GPU cannot be enabled as long as the Ubuntu file system is used? Re: Build Ubuntu For i.MX8 Series Platform HI : yes, It' yocto-wayland desktop. If you want other desktop , you can try apt-get to install . 江亚强 软件工程师 Shenzhen Huameishi Technology Co., Ltd 深圳市华美视科技有限公司 深圳市南山区科苑路6号科技园工业大厦605 Tel:0755-26037882-616 Mail:[email protected] Re: Build Ubuntu For i.MX8 Series Platform Hi prashanth:    How do you get this desktop? After I run "sudo -E weston --tty = 1", the displayed desktop is just the same as the yocto-wayland desktop. Does your system have apt-get install some software?   Tks~ Re: Build Ubuntu For i.MX8 Series Platform Hi , I am not sure why cause it.  you can check if there are /usr/lib/aarch64-xx  libGLES, libEGL。if so, delete them. Re: Build Ubuntu For i.MX8 Series Platform Hi Gnar Fang,               My apologies for the late reply. Yes, i did use the arguments as per the documents to build Weston/Wayland. Regarding the rUNTIME_DIR whatever the ownership/permission i change the warning message continues to exist. Thanks Re: Build Ubuntu For i.MX8 Series Platform Hi, The issue is look like below. 1.warning: XDG_RUNTIME_DIR "/run/user/1001" is not configured correctly. Unix access mode must be 0700 (current mode is 700), and must be owned by the user (current owner is UID 1001). 2.[17:00:10.627] EGL error state: EGL_BAD_ALLOC (0x3003) [17:00:10.627] EGL error state: EGL_SUCCESS (0x3000) [17:00:10.627] failed to initialize egl You can try it. $ sudo su $ XDG_RUNTIME_DIR =/run/user/1001 $ weston --tty=1 It is sure that need to enable HW acceleration during weston compilatio. which the config parameter in build weston? same as my guide? Re: Build Ubuntu For i.MX8 Series Platform Hi Gnar Fang,             If i run weston --use-pixman then there is no issue with the display. This means HW acceleration is not working. This is due to the OpenGL ES driver issue or we need to enable HW acceleration during weston compilatio? Thanks Re: Build Ubuntu For i.MX8 Series Platform Hi Gnar Fang,        Thanks for the doc. Yes, i verified and added galcore module to auto load on startup. But unfortunately i am still not getting the desktop with the following error: sudo -E weston --tty=1 Date: 2019-04-11 UTC [17:00:10.607] weston 5.0.0 https://wayland.freedesktop.org Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/ Build: 5.0.0-33-gfb563901 MGS-4627 [#ccc] weston will turn off when panel-psotion=none and use gplay (2019-03-14 11:30:30 +0800) [17:00:10.607] Command line: weston --tty=1 [17:00:10.607] OS: Linux, 4.19.35-1.1.0+g0f9917c56d59, #1 SMP PREEMPT Wed Oct 30 13:54:51 UTC 2019, aarch64 [17:00:10.608] warning: XDG_RUNTIME_DIR "/run/user/1001" is not configured correctly. Unix access mode must be 0700 (current mode is 700), and must be owned by the user (current owner is UID 1001). Refer to your distribution on how to get it, or http://www.freedesktop.org/wiki/Specifications/basedir-spec on how to implement it. [17:00:10.608] Starting with no config file. [17:00:10.608] Output repaint window is 16 ms maximum. [17:00:10.608] Loading module '/usr/lib/libweston-5/drm-backend.so' [17:00:10.612] initializing drm backend [17:00:10.614] using /dev/dri/card0 [17:00:10.614] DRM: supports universal planes [17:00:10.614] DRM: supports atomic modesetting [17:00:10.614] DRM: supports picture aspect ratio [17:00:10.614] Loading module '/usr/lib/libweston-5/gl-renderer.so' [17:00:10.626] EGL client extensions: EGL_EXT_client_extensions EGL_EXT_platform_base EGL_KHR_platform_wayland EGL_EXT_platform_wayland EGL_KHR_platform_gbm [17:00:10.627] warning: neither EGL_EXT_swap_buffers_with_damage or EGL_KHR_swap_buffers_with_damage is supported. Performance could be affected. [17:00:10.627] EGL_KHR_surfaceless_context available [17:00:10.627] failed to create context [17:00:10.627] EGL error state: EGL_BAD_ALLOC (0x3003) [17:00:10.627] EGL error state: EGL_SUCCESS (0x3000) [17:00:10.627] failed to initialize egl Segmentation fault Re: Build Ubuntu For i.MX8 Series Platform Hi, I had update the DOC for enable weston.  See if there is  gpu driver . root@ubuntu:~# ls /dev/galcore /dev/galcor Re: Build Ubuntu For i.MX8 Series Platform Hi Gnar Fang,             Thanks looking forward to it, kindly let me know once done. I will also update if i make any progress. Re: Build Ubuntu For i.MX8 Series Platform Hi, I will write the guide for 8MM about this week.  Re: Build Ubuntu For i.MX8 Series Platform Hi Prashanth,                I am getting a similar error could you please share how you got the "drm need to run on background" error. Thanks Re: Build Ubuntu For i.MX8 Series Platform Hi Gnar Fang,        Currently I am using IM8MM DDR4 EVK.Thanks Re: Build Ubuntu For i.MX8 Series Platform Which platform are you used? Re: Build Ubuntu For i.MX8 Series Platform Hi Gnar Fang,       While running the Weston tty im getting error either "No such device or directory" or "Fatal : DRM should run in background". Could you please share some guidance in this. Thanks Regards, Raajesh K Re: Build Ubuntu For i.MX8 Series Platform Hi downey: I don't know which platform you are using. I use imx8md/q , it doesn't support "g2d", so just add "--disable-imxg2d" when config weston-imx with fix the issue. 江亚强 软件工程师 Shenzhen Huameishi Technology Co., Ltd Mail:[email protected] Re: Build Ubuntu For i.MX8 Series Platform Hi Gnar,    could you please check this issue about the header file ,It seems about dpu,But I can't find the dpu lib under my yocto project. Thanks a lot. Best Regards. downey. Re: Build Ubuntu For i.MX8 Series Platform Hi jiang yaqiang:    could you please tell me where do you find the imx-dpu-g2d-1.7.0 directory,I can't find this lib ,So I get an error when I compile weston-imx.    I put this issue above , But no one replied about this. Thanks a lot. downey Re: Build Ubuntu For i.MX8 Series Platform HI  Gnar Fang: Following your doc, I can success to run the ubuntu18.04 on imx8mq, but I face a problem: the system could not load firmware: imx-sdma 30bd0000.sdma: external firmware not found, using ROM firmware I have comfirm the firwmware is in /lib/firmware/ . Do you have the same problem ? or where should I check ? Thanks. Re: Build Ubuntu For i.MX8 Series Platform Hi Gnar Fang:       I've found the libdrm/ under aarch64-poky-linux/, and copied it to corresponding directory which you guide in the document. But , I got another error when I compiled weston-imx : ```          ...          In file included from libweston/g2d-renderer.c:44:0:          libweston/g2d-renderer.h:30:10: fatal error: g2dExt.h: No such file or directory          #include          ^~~~~~~~~~          compilation terminated.          Makefile:5107: recipe for target 'libweston/g2d_renderer_la-g2d-renderer.lo' failed ``` There seems to be some system libraries(libweston) that are missing, or some packages that I haven't installed but that library depends on that package.   I tried again to build from scratch to avoid an operational error problem, but the problem was the same on both occasions. Regards. Downey. Re: Build Ubuntu For i.MX8 Series Platform Hi,Prashanth I have not received new requirement, so there is not any update. BR Gnar Re: Build Ubuntu For i.MX8 Series Platform Hi Gnar,    Thanks for your reply. Is there any updated Documents for building Ubuntu 18.04 on i.MX8 platform. Best Regards, Prashanth Kumar K Re: Build Ubuntu For i.MX8 Series Platform Hi,prashanth You install weston, so it show weston GUI. I think you want to get Gnome GUI, but I enable it just with CPU sotfware render (just apt-get                install gnome-core).   Gnome GUI with GPU render meet some mistakes. BR Gnar Re: Build Ubuntu For i.MX8 Series Platform Hi Gnar, We are able to get GUI with Weston, but this GUI look is not like desktop Ubuntu GUI. Whether you are getting same GUI? The terminal showing following output, # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:    Ubuntu 18.04.2 LTS Release:        18.04 Codename:    bionic Regards, Prashanth Kumar K Re: Build Ubuntu For i.MX8 Series Platform Hi, 1. libdrm is under buildxwayland/tmp/work/aarch64-poky-linux. 2. The issue may be caused by your rootfs lost libdrm, copy libdrm to your rootfs. If you have any other question could tell me. These day have too many other case, may reply late. BR Gnar  Re: Build Ubuntu For i.MX8 Series Platform Hi Gnar Fang:    Thanks for your reply,Looking forward to your updates.    BTW,Please check the second question above(compile weston-imx errors ) Regards downey Re: Build Ubuntu For i.MX8 Series Platform Hi,  I also found 8mq yocto have not libdrm. I will check it next week. I think the drm is a necessary component for Linux display. BR Gnar Re: Build Ubuntu For i.MX8 Series Platform Hi Gnar Fang:    I'm trying to port the ubuntu 18.04  to my i.mx8mq-evk,I read your document and followed,But I get two errors:     1. Step 9,part 2: I can't find the targets  "libdrm/2.4.91.imx-r0/image/*"  and  "imx-dpu-g2d-1.7.0/imx-dpu-g2d/1.7.0-r0/image/*" ,I'm sure that these two             target don't exist in my yocto project. I assume that the i.mx8mq-evk does not have dpu,but for libdrm,I'm not sure,So please give me a signal.                btw, I compile with instructions:                         DISTRO=fsl-imx-wayland MACHINE=imx8mqevk source fsl-setup-release.sh -b build                          bitbake fsl-image-qt5-validation-imx    2.Regardless the error 1 above,I'm trying to continue with the document,but when I compile  weston-imx,some errors occured:          steps below:                git clone https://source.codeaurora.org/external/imx/weston-imx.git                cd weston-imx                git checkout fb563901657b296c7c7c86d26602a622429e334f                ./autogen.sh --prefix=/usr --disable-silent-rules --disable-dependency-tracking .........                make   This is error message:   make[1]: Entering directory '/root/weston/weston-imx'  /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I./libweston -I./libweston -I./clients -I./tests -I./shared -I./protocol -DLIBWESTON_MODULEDIR='"/usr/lib/libweston-5"' -DLIBEXECDIR='"/usr/libexec"' -DBINDIR='"/usr/bin"' -DIN_WESTON -Wall -Wextra -Wno-unused-parameter -Wno-shift-negative-value -Wno-missing-field-initializers -g -fvisibility=hidden -Wstrict-prototypes -Wmissing-prototypes -Wsign-compare -DLINUX -DEGL_API_FB -DWL_EGL_PLATFORM -I/usr/include/pixman-1 -DLINUX -DEGL_API_FB -DWL_EGL_PLATFORM -I/usr/include/libdrm -g -O2 -c -o libweston/libweston_5_la-pixel-formats.lo `test -f 'libweston/pixel-formats.c' || echo './'`libweston/pixel-formats.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I./libweston -I./libweston -I./clients -I./tests -I./shared -I./protocol -DLIBWESTON_MODULEDIR=\"/usr/lib/libweston-5\" -DLIBEXECDIR=\"/usr/libexec\" -DBINDIR=\"/usr/bin\" -DIN_WESTON -Wall -Wextra -Wno-unused-parameter -Wno-shift-negative-value -Wno-missing-field-initializers -g -fvisibility=hidden -Wstrict-prototypes -Wmissing-prototypes -Wsign-compare -DLINUX -DEGL_API_FB -DWL_EGL_PLATFORM -I/usr/include/pixman-1 -DLINUX -DEGL_API_FB -DWL_EGL_PLATFORM -I/usr/include/libdrm -g -O2 -c libweston/pixel-formats.c -fPIC -DPIC -o libweston/.libs/libweston_5_la-pixel-formats.o libweston/pixel-formats.c:268:13: error: 'DRM_FORMAT_P010' undeclared here (not in a function); did you mean 'DRM_FORMAT_NV12'? .format = DRM_FORMAT_P010,  ^~~~~~~~~~~~~~~ DRM_FORMAT_NV12 Makefile:5527: recipe for target 'libweston/libweston_5_la-pixel-formats.lo' failed Could you please send me some signals to solve these two issues? Regard downey Re: Build Ubuntu For i.MX8 Series Platform Hi Gnar, Is there any update regarding above issue for Ubuntu 18.04 using Weston file system nxf47724‌ ? Thanks in advance. Regards, Prashanth Kumar K Re: Build Ubuntu For i.MX8 Series Platform Hi,  I am  deleted the rootfs form my PC, if you want,create ticket to me. BR Gnar Re: Build Ubuntu For i.MX8 Series Platform Hi Gnar, Can you please provide your built ubuntu-rootfs.tar.gz file system for testing in iMX8QM custom board. Thanks in advance. BestRegards, Prashanth Kumar K Re: Build Ubuntu For i.MX8 Series Platform Thank you Gnar, deleting those libraries worked for me. Several programs downloaded from "apt-get" (like firefox, chromium and others) try to use X11. We see that you disable xwayland during the weston compilation. What are the reasons for this? Do you think that having xwayland may solve the issue? Do you have any idea of how to get xwayland? Thank you a lot for your help. Best regards, Lorenzo Re: Build Ubuntu For i.MX8 Series Platform Hi Gnar, I used section "10.build weston" steps to build Weston in ubuntu-rootfs in qemu enviroment. Also copying full ubuntu-rootfs to board using below steps mentioned in provided user guide. 12. replace filesystem $ mkdir mountpoint $ umount /dev/sdb2 $ mkfs.ext4 /dev/sdb2 $ mount /dev/sdb2 /home/gnar/mountpoint $ cp -a /home/gnar/rootfs/ubuntu-rootfs /* /home/gnar/mountpoint/ umount /home/gnar/mountpoint sync But  still facing same issue. ubuntu@ubuntu:~$ export XDG_RUNTIME_DIR=/run/user/1000 ubuntu@ubuntu:~$ sudo -E weston --tty=1 [sudo] password for iwave: Date: 2019-10-20 UTC [12:05:59.961] weston 5.0.0 https://wayland.freedesktop.org Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/ Build: 5.0.0-33-gfb563901 MGS-4627 [#ccc] weston will turn off when panel-psotion=none and use gplay (2019-03-14 11:30:30 +0800) [12:05:59.961] Command line: weston --tty=1 [12:05:59.961] OS: Linux, 4.14.98-imx_4.14.98_2.0.0_ga+g5d6cbea, #1 SMP PREEMPT Mon Oct 14 08:11:41 UTC 2019, aarch64 [12:05:59.961] warning: XDG_RUNTIME_DIR "/run/user/1000" is not configured correctly. Unix access mode must be 0700 (current mode is 700), and must be owned by the user (current owner is UID 1000). Refer to your distribution on how to get it, or http://www.freedesktop.org/wiki/Specifications/basedir-spec on how to implement it. [12:05:59.961] Starting with no config file. [12:05:59.962] Output repaint window is 16 ms maximum. [12:05:59.962] Loading module '/usr/lib/libweston-5/drm-backend.so' [12:05:59.964] Failed to load module: /usr/lib/libweston-5/drm-backend.so: undefined symbol: gbm_surface_get_in_fence_fd [12:05:59.964] fatal: failed to create compositor backend ubuntu@ubuntu:~$ Can you please suggest how to resolve  "drm-backend.so"  loading issue? Also kindly provide path to copy "weston" related libraries from yocto build to ubuntu-rootfs. Regards, Prashanth Kumar K Re: Build Ubuntu For i.MX8 Series Platform Hi, According my setp, start simulate ARM64 enviroment on host and build weston. Then copy whole filesystem, not only copy weston lib. BR Gnar Re: Build Ubuntu For i.MX8 Series Platform Hi, This is a script to start up arm64-linux simulate environment. You build weston in the enviroment? I had not meet the issue. Check if there are /usr/lib/aarch64-xx  libGLES, libEGL。if so, delete them. BR, Gnar Re: Build Ubuntu For i.MX8 Series Platform Hi Gnar, I am facing some problem about Weston. While loading below commands, export XDG_RUNTIME_DIR=/run/user/1000 sudo -E weston --tty=1 I am getting following errors. ubuntu@ubuntu:~$ export XDG_RUNTIME_DIR=/run/user/1000 ubuntu@ubuntu:~$ sudo -E weston --tty=1 [sudo] password for iwave: Date: 2019-10-20 UTC [12:05:59.961] weston 5.0.0 https://wayland.freedesktop.org Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/ Build: 5.0.0-33-gfb563901 MGS-4627 [#ccc] weston will turn off when panel-psotion=none and use gplay (2019-03-14 11:30:30 +0800) [12:05:59.961] Command line: weston --tty=1 [12:05:59.961] OS: Linux, 4.14.98-imx_4.14.98_2.0.0_ga+g5d6cbea, #1 SMP PREEMPT Mon Oct 14 08:11:41 UTC 2019, aarch64 [12:05:59.961] warning: XDG_RUNTIME_DIR "/run/user/1000" is not configured correctly. Unix access mode must be 0700 (current mode is 700), and must be owned by the user (current owner is UID 1000). Refer to your distribution on how to get it, or http://www.freedesktop.org/wiki/Specifications/basedir-spec on how to implement it. [12:05:59.961] Starting with no config file. [12:05:59.962] Output repaint window is 16 ms maximum. [12:05:59.962] Loading module '/usr/lib/libweston-5/drm-backend.so' [12:05:59.964] Failed to load module: /usr/lib/libweston-5/drm-backend.so: undefined symbol: gbm_surface_get_in_fence_fd [12:05:59.964] fatal: failed to create compositor backend ubuntu@ubuntu:~$ ubuntu@ubuntu:~$ How to copy "weston" libraries from yocto build to ubuntu-rootfs? Thank you. Regards, Prashanth Kumar K Re: Build Ubuntu For i.MX8 Series Platform Hi Gnar, Thank you for sharing this procedure. I would like to ask you: what is the purpose of the commands "sudo mount -t proc /proc ${2}proc" and the others?  It bring us some problems on the host machines. I also faced a problem about weston. I followed your procedure, but when i try to execute weston i get this: sudo -E weston --tty=1 [sudo] password for user: Date: 2019-10-18 UTC [08:42:03.809] weston 5.0.0                https://wayland.freedesktop.org                Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/                Build: 5.0.0-33-gfb563901 MGS-4627 [#ccc] weston will turn off when panel-psotion=none and use gplay (2019-03-14 11:30:30 +0800) [08:42:03.816] Command line: weston --tty=1 [08:42:03.816] OS: Linux, 4.14.98-imx_4.14.98_2.0.0_ga+g64ad07d, #1 SMP PREEMPT Tue Aug 13 13:06:25 UTC 2019, aarch64 [08:42:03.816] warning: XDG_RUNTIME_DIR "/run/user/1000" is not configured correctly.  Unix access mode must be 0700 (current mode is 700), and must be owned by the user (current owner is UID 1000). Refer to your distribution on how to get it, or http://www.freedesktop.org/wiki/Specifications/basedir-spec on how to implement it. [08:42:03.826] Starting with no config file. [08:42:03.839] Output repaint window is 16 ms maximum. [08:42:03.845] Loading module '/usr/lib/libweston-5/drm-backend.so' [08:42:03.952] initializing drm backend [08:42:03.955] using /dev/dri/card0 [08:42:03.955] DRM: supports universal planes [08:42:03.955] DRM: supports atomic modesetting [08:42:03.955] DRM: does not support picture aspect ratio [08:42:03.960] Loading module '/usr/lib/libweston-5/gl-renderer.so' [08:42:04.302] EGL client extensions: EGL_EXT_device_base                EGL_EXT_device_enumeration EGL_EXT_device_query                EGL_EXT_platform_base EGL_KHR_client_get_all_proc_addresses                EGL_EXT_client_extensions EGL_KHR_debug                EGL_EXT_platform_wayland EGL_EXT_platform_x11                EGL_MESA_platform_gbm EGL_MESA_platform_surfaceless [08:42:04.304] failed to initialize display [08:42:04.304] EGL error state: EGL_NOT_INITIALIZED (0x3001) [08:42:04.304] failed to initialize egl [08:42:04.341] fatal: failed to create compositor backend Have you ever seen a similar error message? Thank you. Regards, Lorenzo Re: Build Ubuntu For i.MX8 Series Platform Hi Gnar, During below make command execution I am getting following header file declaration error message for weston-imx. From where we can get header files for weston? #cd ~/weston #git clone https://source.codeaurora.org/external/imx/weston-imx.git #cd weston-imx #git checkout fb563901657b296c7c7c86d26602a622429e334f #./autogen.sh --prefix=/usr --disable-silent-rules --disable-dependency-tracking  --enable-setuid-install --disable-rdp-compositor --enable-clients --enable-simple-clients --enable-demo-clients-install --disable-colord --enable-egl --enable-simple-egl-clients --enable-fbdev-compositor --disable-headless-compositor --enable-drm-compositor --enable-weston-launch --disable-lcms --disable-libunwind --with-pam--disable-vaapi-recorder --enable-wayland-compositor --without-webp --disable-x11-compositor --enable-xwayland --enable-imxg2d --enable-imxgpu --enable-drm-compositor --enable-opengl #make libweston/compositor-drm.c: In function ‘drm_fb_addfb’: libweston/compositor-drm.c:962:23: error: ‘DRM_FORMAT_MOD_AMPHION_TILED’ undeclared (first use in this function); did you mean ‘DRM_FORMAT_MOD_VIVANTE_TILED’? if (fb->modifier == DRM_FORMAT_MOD_AMPHION_TILED) { DRM_FORMAT_MOD_VIVANTE_TILED libweston/compositor-drm.c:962:23: note: each undeclared identifier is reported only once for each function it appears in libweston/compositor-drm.c: In function ‘drm_clip_overlay_coordinate’: libweston/compositor-drm.c:1518:36: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] if (state->dest_x + state->dest_w > output->base.current_mode->width){ ^ libweston/compositor-drm.c:1526:36: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] if (state->dest_y + state->dest_h > output->base.current_mode->height){ ^ libweston/compositor-drm.c: In function ‘drm_get_gbm_alignment’: libweston/compositor-drm.c:2184:9: error: ‘DRM_FORMAT_MOD_VIVANTE_SUPER_TILED_FC’ undeclared (first use in this function); did you mean ‘DRM_FORMAT_MOD_VIVANTE_SUPER_TILED’? case DRM_FORMAT_MOD_VIVANTE_SUPER_TILED_FC: DRM_FORMAT_MOD_VIVANTE_SUPER_TILED libweston/compositor-drm.c: In function ‘drm_output_apply_state_atomic’: libweston/compositor-drm.c:2600:4: warning: implicit declaration of function ‘gbm_surface_set_sync_post’; did you mean ‘gbm_surface_destroy’? [-Wimplicit-function-declaration] gbm_surface_set_sync_post(output->gbm_surface, 0); gbm_surface_destroy libweston/compositor-drm.c:2601:18: warning: implicit declaration of function ‘gbm_surface_get_in_fence_fd’; did you mean ‘wl_surface_send_enter’? [-Wimplicit-function-declaration] in_fence_fd = gbm_surface_get_in_fence_fd(output->gbm_surface); wl_surface_send_enter libweston/compositor-drm.c: In function ‘drm_query_dmabuf_modifiers’: libweston/compositor-drm.c:3291:49: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] if (p->formats[i].format != format) libweston/compositor-drm.c: In function ‘drm_import_dmabuf’: libweston/compositor-drm.c:3342:37: error: ‘DRM_FORMAT_P010’ undeclared (first use in this function); did you mean ‘DRM_FORMAT_R16’? && dmabuf->attributes.format == DRM_FORMAT_P010) DRM_FORMAT_R16 libweston/compositor-drm.c: In function ‘drm_output_propose_state’: libweston/compositor-drm.c:3752:38: error: ‘DRM_FORMAT_P010’ undeclared (first use in this function); did you mean ‘DRM_FORMAT_R16’? || dmabuf->attributes.format == DRM_FORMAT_P010 DRM_FORMAT_R16 libweston/compositor-drm.c: In function ‘hdr10_metadata_set_metadata’: libweston/compositor-drm.c:7250:29: error: storage size of ‘hdr_metadata’ isn’t known struct hdr_static_metadata hdr_metadata; Best Regards, Prashanth Kumar K Re: Build Ubuntu For i.MX8 Series Platform Hi Build weston in qemu enviroment. BR Gnar Re: Build Ubuntu For i.MX8 Series Platform Hi, I am also porting Ubuntu 18.04 to iMX8 Quad Max custom board with 4.14.98 BSP by referring https://community.nxp.com/servlet/JiveServlet/download/343939-3-454211/Ubuntu-i.MX8-weston.pdf  Document. Till section 9. copy imx-gpu-viv in mentioned document able to understand properly. But after section 10.build weston, its not saying that where need to build weston, wayland, gstreamer and gst-plugins? How to link/add above features with "ubuntu-rootfs" ? Best Regards, Prashanth Kumar K Re: Build Ubuntu For i.MX8 Series Platform Yes, may GPU dirver not fit. Re: Build Ubuntu For i.MX8 Series Platform Hi nxf47724‌ : The GPU can't render gnome because of limitations in the OpenGL library or is there another reason? Re: Build Ubuntu For i.MX8 Series Platform Hi,  A easy way is download linux-imx for linux-imx - i.MX Linux kernel , Then use command "$ make defconfig,  $ make" to build Image . Use the Image replace your current Image. BR Gnar Re: Build Ubuntu For i.MX8 Series Platform thanks for your answer.Can you tell me how to compile the kernel separetely? I use fellowing methods make it : bitbake -c compile -f -v linux-imx  bitbake linux-imx -c compile_kernelmodules -f -v bitbake -c deploy -f -v linux-imx   result: Compare with before: galcore used numbers different.and no have qca6174 driver.and a lot of drivers have been added。 how to resolve it? Re: Build Ubuntu For i.MX8 Series Platform Hi, gao Because in default, GPU driver  galcore is compiled as .ko file, so need compile the kernel separately to make galcore in kernel. BR Gnar Re: Build Ubuntu For i.MX8 Series Platform First of all, thank you very much for your proposal。But i have a question that I hope you can help me with this。In Ubuntu-imx8.pdf setp 2 Compile the kernel separately to replace yocto kernel,Specifically which is kernel to replace yocto kernel? thanks! Re: Build Ubuntu For i.MX8 Series Platform Hi,Anrit 1.  imx-dpu-2d path in yocto is /buildxwayland/tmp/work/aarch64-mx8mm-poky-linux/imx-gpu-g2d  ,8MM have not DPU. 2.  back to first command: ./autogen.sh --prefix=/usr --disable-silent-rules --disable-dependency-tracking --enable-setuid-install --disable-rdp-compositor --enable-clients --enable-simple- clients --enable-demo-clients-install --disable-colord --enable-egl --enable- simple-egl-clients --enable-fbdev-compositor --disable-headless-compositor -- enable-drm-compositor --enable-weston-launch --disable-lcms --disable-libunwind --with-pam --disable-vaapi-recorder --enable-wayland-compositor --without-webp --disable-x11-compositor --disable-xwayland   The error log is : 1)configure: WARNING: you should use --build, --host, --target 2)checking build system type... Invalid configuration `clients': machine `clients' not recognized Are you build in qemu enviroment ? I had not meet the error in my step and not set any  enviroment variables. Try google how build weston, according to the log you need  add the arguments about  --build, --host, --target. The second command, try disable xwayland at first.  The xwayland is not necessary. BR Gnar Re: Build Ubuntu For i.MX8 Series Platform Hello Gnar, Thank you for your reply. I think I am now very close to building ubuntu after following your document. I now have these remaining items. 1. I do not see anything called  imx-dpu-2d in my yocto build folder. So I am not able to run this step in your document: sudo cp -Pra imx-dpu-g2d-1.7.0/imx-dpu-g2d/1.7.0-r0/image/* ubuntu18.04/ My DISTRO is fsl-imx-xwayland and MACHINE is imx8mmevk 2.. I tried the new autogen step as you mentioned in your last post for weston-imx but it still does not build. I now get different errors during autogen step. Here is my log: ......................... root@UB160401:~/weston/weston-imx# ./autogen.sh --prefix=/usr --disable-silent-rules --disable-dependency-tracking --enable-setuid-install --disable-rdp-compositor --enable-clients --enable-simple-clients --enable-demo-clients-install --disable-colord --enable-egl --enable-simple-egl-clients --enable-fbdev-compositor --disable-headless-compositor --enable-drm-compositor --enable-weston-launch --disable-lcms --disable-libunwind --with-pam --disable-vaapi-recorder --enable-wayland-compositor --without-webp --disable-x11-compositor --enable-xwayland --enable-imxg2d --enable-imxgpu --enable-drm-compositor --enable-opengl.... .................. ................. checking for OPENGL... yes checking for GL_RENDERER... yes checking for XKBCOMMON_COMPOSE... yes checking for XWAYLAND... no configure: error: Package requirements (xcb xcb-xfixes xcb-composite xcb-shape xcursor cairo-xcb) were not met: No package 'xcb-xfixes' found No package 'xcb-composite' found No package 'xcb-shape' found No package 'xcursor' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables XWAYLAND_CFLAGS and XWAYLAND_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. Any suggestions? Thank you so much. Amrit Re: Build Ubuntu For i.MX8 Series Platform Hello Gnar and Kyle, I am glad to see that more than one person is working on this project. First of all thank you Gnar for creating the documents and outlining the essential steps. Kyle, I also went through and located all folder that need to be copied from yocto build folders to ~/rootfs/ubuntu-rootfs (or ~/rootfs/ubuntu18.04). Here are the  the source folder names in each case: cd ~/imx-yocto-bsp/build/tmp/work/aarch64-mx8mm-poky-linux sudo cp -Pra libdrm/2.4.91.imx-r0/image/* ~/rootfs/ubuntu-rootfs sudo cp -Pra imx-gpu-viv/1_6.2.4.p4.0-aarch64-r0/image/* ~/rootfs/ubuntu-rootfs sudo cp -Pra ~/imx-yocto-bsp/build/tmp/work/aarch64-mx8mm-poky-linux/imx-gpu-g2d/6.2.4.p4.0-r0/image/* ~/rootfs/ubuntu-rootfs cd ~/imx-yocto-bsp/build/tmp/work sudo cp -r all-poky-linux/firmware-imx/1_8.1-r0/image/* ~/rootfs/ubuntu-rootfs In my case rootfs folder is ~/rootfs/ubuntu-rootfs. Gnar, I am able to run ubuntu18.04 in basic form with Gnome or xfce4 but still in the process of trying to put all the components in my rootfs. I noticed a weird error in step 3) for weston-imx. Here is the error log,  when I run autogen for weston-imx: root@UB160401:~/weston/weston-imx# ./autogen.sh --prefix=/usr --disable-silent-rules --disable-dependency-tracking --enable-setuid-install --disable-rdp-compositor --enable-clients --enable-simple- clients --enable-demo-clients-install --disable-colord --enable-egl --enable- simple-egl-clients --enable-fbdev-compositor --disable-headless-compositor -- enable-drm-compositor --enable-weston-launch --disable-lcms --disable-libunwind --with-pam --disable-vaapi-recorder --enable-wayland-compositor --without-webp --disable-x11-compositor --disable-xwayland autoreconf: Entering directory `.' autoreconf: configure.ac: not using Gettext autoreconf: running: aclocal --force -I m4 autoreconf: configure.ac: tracing autoreconf: running: libtoolize --copy --force libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'. libtoolize: copying file 'build-aux/ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'. libtoolize: copying file 'm4/libtool.m4' libtoolize: copying file 'm4/ltoptions.m4' libtoolize: copying file 'm4/ltsugar.m4' libtoolize: copying file 'm4/ltversion.m4' libtoolize: copying file 'm4/lt~obsolete.m4' autoreconf: running: /usr/bin/autoconf --force autoreconf: running: /usr/bin/autoheader --force autoreconf: running: automake --add-missing --copy --force-missing configure.ac:35: installing 'build-aux/compile' configure.ac:43: installing 'build-aux/missing' Makefile.am: installing 'build-aux/depcomp' autoreconf: Leaving directory `.' configure: WARNING: you should use --build, --host, --target configure: WARNING: you should use --build, --host, --target configure: WARNING: you should use --build, --host, --target configure: WARNING: you should use --build, --host, --target configure: WARNING: you should use --build, --host, --target configure: WARNING: you should use --build, --host, --target configure: WARNING: you should use --build, --host, --target configure: WARNING: you should use --build, --host, --target configure: WARNING: you should use --build, --host, --target configure: WARNING: you should use --build, --host, --target configure: WARNING: you should use --build, --host, --target configure: WARNING: you should use --build, --host, --target configure: WARNING: unrecognized options: --enable-simple-, --enable- checking for clients-gcc... no checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking whether gcc understands -c and -o together... yes checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... no checking whether sys/types.h defines makedev... no checking sys/mkdev.h usability... no checking sys/mkdev.h presence... no checking for sys/mkdev.h... no checking sys/sysmacros.h usability... yes checking sys/sysmacros.h presence... yes checking for sys/sysmacros.h... yes checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking for style of include used by make... GNU checking whether make supports nested variables... yes checking dependency style of gcc... none checking whether make supports nested variables... (cached) yes checking for clients-gcc... gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking whether gcc understands -c and -o together... (cached) yes checking for a sed that does not truncate output... /bin/sed checking build system type... Invalid configuration `clients': machine `clients' not recognized configure: error: /bin/bash build-aux/config.sub clients failed Any clue what I may be missing? BTW: I am using imx8m mini evk  - yocto, but that should not make difference as far as these steps are concerned. Thank you both. Amrit Re: Build Ubuntu For i.MX8 Series Platform Hi Gnar, I think i've gotten a bit confused on what specifically to copy.  From your awesome manual (Ubuntu-imx8-weston.pdf) there are several commands here: 2) copy libdrm, wayland, vpu-firmware from yocto $sudo cp -Pra libdrm/2.4.91.imx-r0/image/* ubuntu18.04/ $sudo cp -Pra imx-gpu-viv/1_6.2.4.p4.0-aarch64-r0/image/* ubuntu18.04/ $sudo cp -Pra imx-dpu-g2d-1.7.0/imx-dpu-g2d/1.7.0-ro/image/* ubuntu 18.04/ $sudo cp -r all-poky-linux/firmware-imx/1_8.1-r0/image/* ubuntu18.04/ What would help me is to understand the actual folder paths for each of them. My assumption is that you are copying from the Yocto build... could you give me the full paths to /libdrm/2.4.91.imx-ro/image/,  /imx-gpu-viv/1_6.2.4.p4.0-aarch64-ro/image/, /imx-dpu-g2d-1.7.0/imx-dpu-g2d/1.7.0-ro/image/* and all-poky-linux/firmware-imx/1_8.1-r0/image/* 2nd, when you point out the destination folder of 'ubuntu18.04/'  do i assume that /ubuntu18.04/ is the base of the ubuntu rootfs? thanks kylef Re: Build Ubuntu For i.MX8 Series Platform Hi, Kyle      I am not test webcam but other one test it ok. I am not sure he do other config for it. If you webcam is usb camera, may should enable UVC driver in kernel. About VPU firmware, are you copy it under  /lib/firmware ? You also can copy unit_test file form yocto,  use v4l2 to open camera. BR Gnar Re: Build Ubuntu For i.MX8 Series Platform Hi Gnar, i was curious whether you have tested a webcam with ubuntu and seen if it works?  i'm struggling to get a simple logitech webcam to work.  It looks like i'm getting a dmesg alert that "VPU_firmware_download Failed"... so i assume the VPU firmware is messed up. maybe i copied in the wrong file at some point... k Re: Build Ubuntu For i.MX8 Series Platform Hi, Amrit 1.which folder (cd ~/????)  The command run Host PC side. To  build a ubuntu rootfs, decompression rootfs first such as tar -xvf ubuntu-base-18.04.2-base-arm64.tar.gz -C ubuntu-rootfs, in my case  modify ubuntu-rootfs to ubuntu 18.04, May cause you misunderstand and I will uniform naming. This command purpose is copy  libraries related GPU to ubuntu-rootfs. 2.Compile the kernel separately Because the GPU dirver be builded as galcore.ko by yocto default. So compile the kernel separately to make Image include gpu dirver. In kernel source code(I download form linux-imx - i.MX Linux kernel , not use the yocto code), after command $ make menuconfig, you can see the .config CONFIG_MXC_GPU_VIV=y. BR Gnar Re: Build Ubuntu For i.MX8 Series Platform Hello Gnar, Thank you for posting this detailed document. I was trying to follow it for nxp imx8m-mini evk. I have been able to build yocto for this board and that seems to work fine but now want to try ubuntu with weston on this evk. I have these questions for you in your Ubuntu-i.MX8-weston.pdf document. In section 9 you write: 2)copy libdrm,wayland vpu-firmware from yocto $sudo cp -Pra libdrm/2.4.91.imx-r0/image/* ubuntu18.04/ $sudo cp -Pra imx-gpu-viv/1_6.2.4.p4.0-aarch64-r0/image/* ubuntu18.04/ $sudo cp -Pra imx-dpu-g2d-1.7.0/imx-dpu-g2d/1.7.0-r0/image/* ubuntu18.04/ $sudo cp -r all-poky-linux/firmware-imx/1_8.1-r0/image/* ubuntu18.04/ Could you tell me from which folder (cd ~/????)  you are running these commands? Also this folder ubuntu 18.04 does not exist anywhere, where does it get used later? I do not see any other reference to "ubuntu 18.04" folder in this document. Is imx-dpu-g2d a typo, should it be imx-gpu-g2d ? Also you say: 2.Compile the kernel separately to replace yocto kernel Do you mean bitbake linux-imx after I have built yocto? Currently in the yocto build I do see that a kernel Image that has been built. Thanks, Amrit Re: Build Ubuntu For i.MX8 Series Platform <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> Hello, Is your issue resolved? I also encountered the same problem. My solution was to compile the module but not load it during kernel configuration. Then load it manually after the system is up. However, this will cause some error logs about dependency issues. Although it can be solved, I think this method is not very good. Do you have a better idea?
View full article
S32K344 - FOC with dual shunt current measurement S32K344 - FOC with dual shunt current measurement These examples demonstrate a 3-phase Permanent Magnet Synchronous Motor (PMSM) vector control (Field Oriented Control - FOC) drive with 2- shunt current sensing with and without position sensor. This design serves as an example of motor control design using NXP S32K3 automotive family. Examples were designed on S32K344 Brushless Direct Current and Permanent Magnet Synchronous Motor Control Development Kit.  C-project based examples are part of MCSPTE1AK344 Development Kit Application Software. An innovative drivers set, Real-Time Drivers (RTD),are used to configure and control the MCU. It complies with Automotive-SPICE, ISO 26262, ISO 9001 and IATF 16949. Production-ready Automotive Math and Motor Control Library set provides essential building blocks for algorithm. FreeMASTER is used as useful run-time debugging tool. Application software contains:  MCSPTE1AK344_PMSM_FOC_2Sh_ll - Low-level drivers of RTD and S32 Design Studio Configuration Tools (S32CT) are used to demonstrate non-AUTOSAR approach. Detailed description of the example can be found in application note AN13767. MCSPTE1AK344_PMSM_FOC_2Sh_as_tr - RTD, EB (Elektrobit) tresos Studio and S32 Design Studio are used to demonstrate AUTOSAR (AUTomotive Open System ARchitecture) approach. Detailed description of the example can be found in application note AN13884. MATLAB Simulink based project (Motor Control PMSM Example - s32k344_mc_pmsm_ebt) is build using Model-Based Design Toolbox (MBDT) and can be downloaded from NXP Model-Based Design Toolbox for S32K3xx - version 1.4.0 or newer releases. Example is described in article  3-Phase Sensorless PMSM Motor Control Kit with S32K344 using MBDT blocks. 
View full article
32.768kHz Crystal for RW612 Hello, I'm currently working on a PCB design project that includes an IRIS-W10 module from u-blox with an RW612 inside. This is my first design with an NXP MCU. I'm unsure, how I should design the circuit for the RTC external crystal. From other MCUs like STM32 I know they need an external load capacitor on both of the crystal pins. But for NXP MCUs it seems that some have internal configurable load caps. In the RW612 register list I stumbled upon the RTC CTRL register and in particular the field RTC_OSC_LOADCAP. To me this indicates that this MCU has in fact internal load caps, but I couldn't find any documentation on this field. So my question is: What is the bit-format to set a specific capacitor value in this register? Product: WiFi RW6XX Re: 32.768kHz Crystal for RW612 Here is the related register for 32k XTAL. The register for RTC_OSC_LOADCAP looks as a mystery since may not applicable to this product Re: 32.768kHz Crystal for RW612 Thank you for your reply. It seems that the configuration of the RTC crystal is split up into two section. The one you showed me is from the PMU. What causes me a headache is the RTC section. In the screen shot below you can see there are no external capacitors, but I don't see any internal caps eighter And in this screen shot you can see the particular register I was talking about in my question. You might be right that this MCU has no internal capacitors at all, but if so the RTC_OSC_LOADCAP field should not be visible in the register documentation. On the other hand this crystal circuit from the FRDM-RW612 has no load caps from factory. Re: 32.768kHz Crystal for RW612 Hi @Niwo, hope you are doing well. Could you please confirm if you have already selected a 32kHz crystal? This is important as each crystal requires a certain load capacitance defined in their datasheet. Also, it is strongly recommended to work along the crystal manufacturer to determine the proper characteristics around the crystal circuitry. Re: 32.768kHz Crystal for RW612 Hello @RomanVR, Thank you for your response. I haven't ordered any parts yet, but I intend to use this one: https://eu.mouser.com/de/ProductDetail/ECS/ECS-.327-6-16-TR3?qs=A6eO%2BMLsxmSq6P7XbVvfvw%3D%3D Best regards Re: 32.768kHz Crystal for RW612 Hi @Niwo, I apologize for the delay. As per the shared crystal datasheet, the required load capacitance is 12pF, hence this should be taken as guide to configure any external circuitry and further analyzed with the crystal manufacturer for optimal performance suggestions. Regarding the mentioned register, it should not be used to configure the external crystal load capacitance, this observation has been raised with the appropriate teams to take further action. For XTAL32K functionality and crystal-related requirements, Chapter 10 of UM11865 is the proper reference. Hope this helps! Re: 32.768kHz Crystal for RW612 Hello @RomanVR, I would like to suggest a few changes for the documentation that I think will make it easier for others to approach the design for the 32.768kHz crystal: Removal of the RTC_OSC_LOADCAP field in the RTC CTRL register from RM00278 and also from the MCUXpressoSDK drivers Add external load capacitors to figure 71 of UM11865 or even better add a schematic to chapter 10 that shows the crystal and load caps beeing connected to GPIO[22] and GPIO[23] In chapter 10 section 2 of UM11865 I don't understand what "External capacitor: 18 pF" should tell the reader. Please go into more detail about this I hope my feedback is helpful to you. Best regards
View full article
正在寻找 FS5600 FRDM-K82F 固件 我正在修复一台与 KITFS5600FRDMEVM 一起使用的 FRDM-K82F。它是几年前建立的,相关的文件和知识很难找到。 我按照UM11526中的固件恢复步骤进行了操作。OpenSDA 固件已成功恢复,现在板的型号为FRDM-K82FD。 UM11526 的下一步需要以下固件: nxp-gui-fw-frdmk82f-usb_hid-fs5600_xxx.bin 手册中指出,该文件位于NXP GUI软件包的MCU文件夹中。然而,当前的NXPGUI_PR_11.1.0软件包已不再包含K82F固件;其MCU目录仅包含KL25Z和S32K144固件。 请问有人知道哪里可以找到这个固件,或者包含它的旧版 NXPGUI 软件包吗? 目前我只需要FS5600应用固件。K20/OpenSDA引导加载程序和FRDM-K82F接口固件已经可以正常工作。 先行致谢。 i.MX 的 PMIC Re: Looking for FS5600 FRDM-K82F firmware 谢谢郭伟孙。效果很好,我会尽量记住在适当的时候使用支持工单。 谢谢! Re: Looking for FS5600 FRDM-K82F firmware 嗨 jbarns 请尝试从附件下载。 顺便提一下,DFAE 的各位,请优先在 Salesforce 提交工单中提问,而不是在社区中提问。
View full article
FS65 - Enable load dump feature on IO2 IO3 I am currently working with the SBC FS65. According to the reference manual, IO2 and IO3 are not load dump proof. While IO0, IO4, and IO5 (with external protection) are load dump proof, IO4 and IO5 are being used for external IC monitoring. This leaves only IO0 available for external connections, such as ignition or other wake-up sources. Could you please clarify if we can make IO2 and IO3 load dump proof externally (similar to IO5) so that external loads can be connected to them? Re: FS65 - Enable load dump feature on IO2 IO3 Hello Sandeep, IO2 and IO3 are logic-level local inputs and are not designed to be connected directly outside the ECU. Their absolute maximum voltage range is only −0.3V to 8V. If they must be used for an external wake-up source, a separate automotive-qualified, load-dump capable input-conditioning or level-shifting circuit would be required. This circuit must ensure that the voltage at IO2 or IO3 remains within the pin ratings under all normal and transient conditions and that the specified input thresholds are satisfied. BR, Tomas Re: FS65 - Enable load dump feature on IO2 IO3 Hi Tomas, Thanks for clarification.....
View full article
适用于 Mcuxpresso 的 MIMXRT1010 SDK 您好, 我一直使用 mcuxpresso ide(版本 25.6)和 SDK_2.x_FRDM-K64F,利用连接到 FRDM-K64F 评估套件上的 nrf24l01 芯片,在 2.4 GHz 频段上构建网络。我想在网络中添加几套MIMXRT1010评估套件。我正在尝试安装 SDK_2_11_0_EVK-MIMXRT1010-AGM01.zip,以便使用同一个 IDE 在 RT1010s 上构建系统。它似乎已经下载并安装,但却被默默忽略了。系统提示该软件已存在,但在“已安装的SDK”面板中只有FRDM-K64F。我已经仔细地重新编译了SDK,确保包含了mcuxpresso IDE,并且我是在Linux系统上进行开发。 我是否可能受到了某种未知病毒的攻击? 非常感谢您的帮助。 干杯 奈杰尔 Re: MIMXRT1010 SDK for Mcuxpresso 嗨@ve3id , 以下是一些需要测试的项目,以确保 SDK 已正确重新安装: 在“已安装的 SDK”面板中,单击“打开 SDK 处理首选项页面”: 你应该会看到类似这样的内容: 请在所有列出的 SDK 搜索根路径中搜索“SDK_2_11_0_EVK-MIMXRT1010-AGM01.zip”,然后手动将其删除。 如果您尚未修改工作区的 SDK 位置路径,则应该看到已选择“通用 'mcuxpresso' 文件夹”选项,并且仅显示 'mcuxpresso\02\SDKPackages' 搜索根目录,因为这是默认位置。 删除后,点击重新加载按钮刷新 SDK 列表: 然后再次尝试将 SDK zip 文件拖放到“已安装的 SDK”文件夹中。如果过一段时间仍未出现,请尝试再次重新加载 SDK 列表。 BR, 埃德温。 Re: MIMXRT1010 SDK for Mcuxpresso 谢谢回复。我完全按照你说的做了,/home/nigel/mcuxpresso/02/SDKPackages# 目录是唯一显示的目录,我删除了里面的 zip 文件并重新拖入,它再次出现,但之后却没有出现在已安装 SDK 面板中。我试了两次,但刷新后仍然没有出现在已安装的SDK面板中。 Re: MIMXRT1010 SDK for Mcuxpresso 我还尝试了从“可用SDK”面板中“下载并安装SDK”选项。我选择了 MIMXR1011 处理器,它将此文件下载到 /02/SDKPakcages 目录 com.nxp.mcuxpresso.sdk.sdk_2.x_mimxrt1011xxxxx_p2site_26.9.0.20191125144617176723704789806225.zi,但它没有在面板中显示为已安装。 Re: MIMXRT1010 SDK for Mcuxpresso 问题解决了! 我尝试直接在 ~/mcuexpresso/02/SDKPackages 目录中手动解压缩,但失败了,因为它想要覆盖 cmsis 编译器,而我不想这样做。于是我在现有的 SDKPackages 目录下创建了一个名为 MIMX 的目录,并将其解压到该目录中,瞧,它就出现在我的“已安装 SDK”面板中了。我可以用 MIMXRT1011 微处理器启动一个新项目,看来我现在可以开始了。 谢谢你帮我指明了正确的方向! 干杯 奈杰尔
View full article
A Streaming Service That Surprised Me I’ve tried several streaming services over the years, and finding one that remains consistent can be harder than expected. Recently, I spent some time testing NexusIPTV and was positively surprised by the overall experience. The streaming quality was good, channels loaded quickly, and the service worked well across the devices I tested. For people in the USA, UK, and Canada, it may be worth adding to the list of services to compare. I wrote more about my experience here: 👉 My full experience
View full article
模块 phalFelica 中的 NXPNfcRdLib 漏洞 - 常见漏洞与后门-2026-87726 概述 支持软件 NXPNfcRdLib 中发现了一个软件漏洞 - 常见漏洞与后门-2026-87726。NXP NXPNfcRdLib 模块 phalFelica(固件版本 07.14.00_Pub 之前)的 API 边界检查不足,可能允许具有特权的攻击者或不受信任的第三方访问非预期的内存区域,从而可能导致机密性、完整性和可用性的有限损失。 受影响的设备 当 NXPNfcRdLib 版本 07.14.00 及更早版本与基于 FeliCa 的应用程序一起使用时,在基于 CLRC663 系列、PN5180、PN7462 和 PN5190 平台构建的 NFC 阅读器解决方案上部署时,该漏洞会影响这些应用程序。 减轻 请使用NFC读取器库 | NXP 半导体上提供的最新 NXPNfcRdLib。从 07.18.00 开始的所有固件版本都已修复此问题。 致谢 NXP感谢Ezhilamuthan的负责任披露。
View full article
Secure boot in imxrt1024..5A Abhay2080_0-1788352073442.pngAbhay2080_0-1788352073442.pngAbhay2080_0-1788352073442.pngAbhay2080_0-1788352073442.png I have attached a snap of hex compare of signed and unsigned image (signed using SPT) i can see IVT have several changes that i didnt understand.  At 0x1000 offset Unsigned -> D1 00 20 41 00 20 00 60 00 00 00 00 00 00 00 00 Signed ->     D1 00 20 40 DD 22 00 60 00 00 00 00 00 00 00 00 Question 1 i understand that 41 is the IVT version that is hardcode inside my code how this is changed to 40? question 2. Also i dont understand  how 00 20 -> DD 22 At 0x1010 offeset This is clear as here CSF pointer got updated At 0x1020 Unsigned -> 00 00 00 60 00 00 40 00 00 00 00 00 Signed ->     00 00 00 60 00 A0 00 00 00 00 00 00 Question 3 how 00 40 is update with A0 00 The reason to ask these question is as per my understanding if development team gave bootable binary then i just need to append CSF.bin and update the CSF pointer in IVT to make it sign , but after seeing the difference i feel there are more things happening Re: Secure boot in imxrt1024..5A Abhay2080_0-1788520801299.pngAbhay2080_0-1788520801299.pngAbhay2080_0-1788520801299.png In earlier post i got this answer so i thought just appending csf and updating the vsff pointer in IVT means firmware is signed but since i want to use CST for signing the image how to do that? I already have bootable image (FCFB, IVT, BOOTDATA,...) . I just need to sign and ship the package how to do that , i have created hab.csf  [Header] Version = 4.0 #Avalibale engine are DCP, SW, ANY for IMXRT Engine = DCP Engine Configuration = 0 Certificate Format = x509 Signature Format = CMS Hash Algorithm = sha256 #Install root public key for use in subsequent INSTALL CSFK or Install KEY #HAB install in slot 0 of its internal public key store # HAB just re-hashes the table and compares against the fused SRK-hash. [Install SRK] File = "keys/SRK_1_2_3_4_table.bin" #Tell which SRK to use, installation will fail if revocation fuse with this index is burned Source index = 0 Hash Algorithm = sha256 #HAB install CSF key's cert in slot 1 [Install CSFK] File = "crts/CSF1_1_sha256_4096_65537_v3_usr_crt.pem" Certificate Format = x509 #Authenticate CSF command authenticates the CSF from which it is executed [Authenticate CSF] #Install a public key for use in subsequent Install key or Authenticate Data commands #HAB install IMG cert into key slot 2 [Install Key] #Means this cert is checked against the SRK Verification index = 0 Target index = 2 File = "crts/IMG1_1_sha256_4096_65537_v3_usr_crt.pem" [Authenticate Data] #Should be same as Target Index in Install Key Verification index = 2 Blocks = 0x60001000 0x1000 0x6580 "evkmimxrt1024_iled_blinky_unsigned_original.bin" Re: Secure boot in imxrt1024..5A Hi @Abhay2080 , Thanks for your questions! Based on the RT1024 IVT / Boot Data definition, the differences you see are expected and are not limited to the CSF pointer update. Q1: Why does D1 00 20 41 become D1 00 20 40 ? D1 00 20 41 is the IVT header: 0xD1 is the IVT tag, 0x0020 is the fixed IVT length of 32 bytes, and the last byte is the version. The RT1024 Reference Manual defines the IVT version as 0x40/0x41 , so 0x40 is valid and not an error. Please check this online guide: https://mcuxpresso.nxp.com/mcuxsdk/latest/html/middleware/mcu_bootloader/docs/iMXRT1024_Manufacturing_User_Guide/topics/imx_rt_bootable_image.html Q2: Why does 00 20 00 60 become DD 22 00 60 ? This is the IVT entry field. In little-endian format: 00 20 00 60 = 0x60002000 DD 22 00 60 = 0x600022DD The RT1024 RM defines entry as the absolute address of the first instruction to execute from the image. AN12108 also states that if the default entry point is not Reset_Handler , entryPointAddress should be set to the Reset_Handler address. So SPT likely updated the IVT entry from 0x60002000 to the actual application entry point. Please confirm the Reset_Handler address in the map file / ELF symbol table. Q3: Why does 00 00 40 00 become 00 A0 00 00 ? At 0x1020 this is Boot Data: start remains 0x60000000 length changes from 0x00400000 to 0x0000A000 The RT1024 RM defines Boot Data as containing the image start address and image length, and the Boot ROM reads the image address and length from this structure. Therefore, SPT updated the length field to match the final generated bootable/signed image layout. For RT-series HAB secure boot, the final signed image is not just “append CSF.bin + update the CSF pointer”. The IVT header, entry, Boot Data length, CSF pointer, and the address/length covered by the CSF Authenticate Data command must all be consistent. HAB recalculates the hash from the software in flash and compares it with the reference hash recovered from the signature; if an authenticated region is modified after signing, verification fails.[0dfe-E1] The recommended approach is to use the final signed image generated by SPT/CST, not to manually append CSF.bin only. I hope this clarification helps! Best regards, Gavin Re: Secure boot in imxrt1024..5A Hi @Abhay2080 , Good question. The key point is: CST does not modify your image — it only computes the hash over the region you specify and produces the CSF (signature). It never changes IVT entry, Boot Data length, or version. That is why those fields changed under SPT: SPT rebuilds the boot image from the ELF and normalizes IVT.entry (to the real Reset_Handler) and Boot Data length. Those changes come from image re-building, not from the signing step. With the CST-direct flow you do not need to reproduce them — if your original image already boots in the open/development state, its entry and version are already correct and can stay as-is. However, there is one hard requirement. Your [Authenticate Data] block Blocks = 0x60001000 0x1000 0x6580 covers the entire IVT, and the IVT CSF pointer sits inside this signed region. HAB re-hashes this region and compares it against the signature, so if any byte in it is changed after signing, authentication fails. This is exactly why "sign first, then append CSF and update the CSF pointer" does not work — the order is wrong. Correct CST sign-and-ship procedure (do this before running cst): Decide where the CSF will sit (appended after the App). With your block, App ends at 0x1000 + 0x6580 = 0x7580 , so the CSF starts at file offset 0x7580 (memory 0x60007580 ). In the image to be signed, pre-set: IVT CSF pointer  → CSF memory address (e.g. 0x60007580 ); Boot Data length → total image size including the CSF. Keep FCFB and entry unchanged (FCFB is outside the HAB scope; ROM reads it before HAB). Run: cst -i hab.csf -o csf.bin (your hab.csf with Engine = DCP is correct for RT1024). Concatenate: cat prepared.bin csf.bin > signed_firmware.bin , place CSF at the address from step 1, and flash directly. So your hab.csf itself is fine; the only fix is to set the CSF pointer and Boot Data length before signing, not after. Best regards, Gavin
View full article
推出“NTAG X DNA”,这是一款NFC标签IC,仅需一枚芯片即可安全支持从制造到报废的整个产品生命周期(日本博客)。 介绍   如果只需举起智能手机就能完成更改设置或对交付的机械进行维护的过程(这需要到现场、连接电缆和打开电脑),那会怎样呢? 除了这些运营效率的提升之外,产品安全相关的监管环境也在迅速变化。欧盟的《网络弹性法案》(CRA)将分阶段实施,直至2027年,该法案强制要求联网产品必须满足安全要求。数字产品护照(DPP)和电池护照(DBP)要求对产品材料、制造和处置信息进行数字化追踪。我们经常听到人们说:“我们知道我们需要做些什么,但我们究竟该从何入手呢?” NTAG X DNA是一款 NFC 标签 IC,旨在应对现场挑战并满足监管要求。本文将展示它在工业设备制造、安装、运行、维护以及最终处置的各个阶段的应用。   什么是NTAG X DNA?   NTAG X DNA 是一款安全可靠的 NFC 标签 IC,具有 NFC 和 I²C 双接口。其主要特点如下: NFC(*T4T)+ I²C 双接口:即使断电也能进行 NFC 通信。通过 NFC 与智能手机等设备连接,通过 I²C 与微控制器 (MCU) 连接。 最大 16KB 内存:足以存储证书、日志和配置数据。 通过 GPIO 进行硬件触发:身份验证成功后,通过 GPIO 直接控制设备。 NTAG_X_DNA.png无需更改现有 MCU 即可添加安全功能作为配套芯片,这对于希望最大限度减少设计更改的开发人员来说无疑是一个有用的优势。 *什么是NFC T4T(4型标签)? 这是 NFC 论坛定义的标签类型之一,它是一种高性能、高安全性的 NFC 标签,符合 ISO/IEC 14443-4 标准。   NTAG X DNA 安全   以下是 NTAG X DNA 的四个主要安全优势。   1. 在文件级别控制访问权限。   NTAG X DNA 与其他 NFC 标签的不同之处在于它能够在文件级别控制访问权限。 “任何人都可以读取此文件,但需要制造商密钥才能重写它。” “没有经过认证的技术人员密钥,无法读取或写入此文件。” 您可以为每个文件设置类似的访问条件。在任何阶段——制造、安装、维护或处置——您都可以实施一个系统,仅允许拥有正确密钥的正确人员或设备执行必要的操作。   2. 使用 PKI 的非对称加密(ECC 256 位)   除了 AES-128/256 加密外,该系统还支持使用 PKI(ECC 256 位)的非对称加密。AES 由于共享密钥,在密钥分发和管理方面存在挑战,而 PKI 则无需向验证方提供私钥,即使在大规模供应链和涉及大量未指定参与方的场景中,也能实现安全可靠的身份验证。   3. 经第三方认证   整个系统已获得第三方认证,达到*CC EAL6+级别。尤其值得注意的是,评估不仅涵盖硬件和操作系统,还包括应用层。由于安全漏洞通常存在于应用层,因此对整个技术栈进行评估,为将其集成到产品中提供了可靠性基础。 CC EAL是什么? CC(通用准则)是国际安全评估标准,EAL(评估保证级别)表示该评估的保证级别。 EAL6+ 代表了商用安全集成电路的最高认证级别,展现出与智能卡相当的高安全保障水平。   4. 为每个软件包提供 UID。   此外,NTAG X DNA提供的是封装级而非晶圆批次级的唯一标识符 (UID) 。这使您可以追踪每个 UID 的交付目的地,即使交付给多个生产合作伙伴,也能简化管理。而且,由于您可以追踪这些信息,因此还有助于防止代工制造中的欺诈行为。 “生产过剩:生产超过标准数量的产品,然后将剩余产品转售。” “虚报缺陷产品数量并转售合格产品,或者少报缺陷产品数量。” 除非知道每个包裹使用了哪个唯一标识符 (UID),否则无法检测到此类欺诈行为。通过逐个包裹明确识别 UID,可以验证已签发证书的数量与实际产品数量是否一致,从而更容易及早发现此类欺诈行为。   用单个芯片支持整个产品生命周期   接下来,我们将把产品生命周期分解成各个阶段,并介绍如何利用 NTAG X DNA。 阶段 利用 NTAG X DNA 可以做什么 ① 生产和运输 关机状态下写入证书和设置,验证真伪,兼容DPP。 ② 安装和调试 只有经过认证的人员才能进行安全配置,CRA 支持。 ③ 运行中 通过点击实时显示数据,数据采用 PKI 签名保证。 ④ 维护 错误日志采集、固件更新准备、设备可追溯性 ⑤ 零件更换 通过 PKI 进行正品认证 ⑥ 处置和回收 撤销和删除身份验证信息,DBP 和 GDPR 合规性。     ① 生产和运输:从产品诞生的那一刻起就证明其真实性。   CRA(信用报告机构)要求提供唯一的产品识别信息,以便在发生安全事件时能够识别和追踪受影响的产品。然而,序列号仅仅是一串字符,很容易被篡改或复制。只有与 PKI(公钥基础设施)证书结合使用,才能实现“此序列号属于此特定设备”的不可篡改的关联。 NTAG X DNA 可分两个阶段使用 PKI 证书。首先,在发货时,NXP 密钥对和 NXP 签名证书已写入芯片,可立即验证“此芯片为 NXP 制造的 NTAG X DNA”。此外,通过使用EdgeLock 2GO (NXP 云服务)添加自定义证书,还可以提供产品级证明,证明“此产品为 A 厂商的正品”。 由于每个包装都预先提供了唯一标识符 (UID) 和公钥,因此可以在安全的环境中预先颁发证书,并且只有公开可用的证书数据才能传递给生产线,从而消除了保障生产线本身安全的难题。结合 EdgeLock 2GO,证书的生成、分发和吊销管理可以从云端集中进行,从而更容易在整个生命周期内管理“谁收到了什么以及哪些证书有效”。 (注:EdgeLock 2GO 需要网络连接和单独的合约。详情请联系恩智浦半导体或恩智浦半导体经销商。) 即使在发货后,只需将NFC读取器靠近设备,即可在分销的每个阶段执行基于PKI的签名验证。与序列号或二维码的视觉验证不同,加密验证使得伪造和复制变得极其困难。制造商、材料和生产日期等DPP(分销产品包装)要求的信息也可以存储在片上存储器中,并受到PKI保护。 NTAG_X_DNA_UID_CERT.png   ② 安装和调试:现场完成安装,无需电缆。   设备到达现场后的初始安装过程也将与以往有所不同。 以前,技术人员需要携带电脑和线缆到现场,连接设备,然后手动输入设置。而现在,配备 NTAG X DNA 的设备只需经过身份验证的人员将安装了 NFC 应用的智能手机靠近设备即可写入设置。由于通信经过加密,因此可以防止未经授权的设置更改。这种安全的设置管理机制符合临床研究管理员 (CRA) 的要求。   ③ 操作中:点击“当前状态”进行查看。   我们有时会听到有人说:“条形码和二维码就足够了。” 虽然它们非常方便,但条形码和二维码只能包含在打印或生成时就已固定的静态信息。它们无法传达设备运行过程中的动态“当前状态”。 由于 NTAG X DNA 通过 I²C 与 MCU 通信,MCU 可以持续地将最新数据写入 NTAG X DNA 的内存。即使在无法安装 LCD 或显示面板的设备中,智能手机也可以用作屏幕。例如,对于电机,只需将智能手机靠近电机,即可立即查看 MCU 记录的运行时间、温度、异常标志和报警历史记录。由于签名数据可以嵌入 NDEF URL 中,因此只需使用浏览器即可完成读取和签名验证,无需专用应用程序,同时还可以确认“此信息来自合法设备”。   ④ 维护和故障排除:只需一部智能手机即可提供现场支持   传统上,当工厂或户外设备出现问题时,唯一的办法是携带线缆和电脑前往现场。而安装了 NTAG X DNA 后,只需将智能手机靠近 MCU,即可读取 MCU 在完成操作前写入的错误日志。如果需要固件更新,您可以将更新写入 NTAG X DNA 的内存,MCU 将在下次启动时自动应用更新(MCU 必须启动才能应用实际的固件更新)。此外,它还提供用户身份验证和加密通信功能,让您在工作的同时防止未经授权的访问和篡改。 在电缆缠绕的控制面板中,追踪故障电机所连接的驱动器变得异常困难,而NTAG X DNA彻底改变了这一难题。只需将其连接到每台设备,并预先注册设备ID、连接目的地、安装日期和负责人信息,即可通过智能手机靠近设备轻松获取所需信息。这大大减少了查阅线路图或手动转动电机进行检查所需的时间。   ⑤ 零件更换:检查是否为原装零件。   令人惊讶的是,验证耗材和替换零件是否为正品通常依赖于模拟方法。目视检查、标签和包装上的印刷——这些方法都很容易伪造。 通过将 NTAG X DNA 集成到耗材中,并在设备端安装过程中实现自动读取标签并执行 PKI 认证的系统,加密验证无需任何用户干预即可运行。但需要注意的是,这种“自动验证”仅在设备端设计和实现正确的情况下才能正常工作。NTAG X DNA 本身无法独立运行。   ⑥ 处置和回收:确保产品生命周期的最终安全结束   在处置或回收设备时,如何处理与设备相关的认证信息和配置数据成为一个重要问题。如果不加以控制,报废设备中的某些组件可能会被连接到其他设备上并重复使用,存在一定的风险。 当设备被处置时,管理系统会撤销与唯一标识符 (UID) 关联的证书,从而消除废弃设备被误认为是正品的风险。此外,随机 ID 功能可防止处置后设备被追踪,符合 DBP 和 GDPR 的隐私保护要求。 为了进一步加强隐私保护,您可以将文件访问条件设置为“禁止访问”来阻止外部访问。但是,由于更改此设置本身需要修改文件的权限(密钥),因此在处置流程的设计阶段,预先决定“谁将进行更改、何时进行更改以及使用哪个密钥”至关重要。 总结   NTAG X DNA 不仅仅是一个 NFC 标签;它是一个平台,可在产品的整个生命周期内提供安全性和便利性。 这次我们以工业设备为例进行了介绍,但同样的机制可以应用于医疗器械、家用电器和可穿戴设备等各种产品。如果您正在考虑“我无法放置液晶显示屏,但或许可以放置NFC天线?”,那么NTAG X DNA正是您所需要的。请购买一套评估套件( NTAG-X-DNA-EVAL ) ,并在您自己的应用场景中进行测试。 NTAG_X_DNA_EVAL.png   ========================= 我们目前无法回复此帖子“评论”部分留下的评论。 对于由此造成的不便,我们深表歉意,但在进行咨询时,请参考“ NXP 技术问题 - 如何联系我们(日语博客) ”。 (如果您已经是恩智浦的分销商或与恩智浦有合作关系,您可以直接咨询您的代表。) 产品安全监管要求正迅速提高,例如《网络安全韧性法案》(CRA) 和《数字产品护照》(DPP) 等法规。NTAG X DNA 是一款 NFC 标签 IC,它将 NFC + I²C 双接口和智能卡级安全功能集成于单芯片,可实现对产品整个生命周期的安全管理,涵盖从制造、安装到运行、维护和处置的各个环节。本文将介绍一个使用单个工业设备的具体应用案例。 (阅读时间:约10分钟) 安全 日本博客
View full article