MIIT (China) sharpened Homologation on FRDM-KW38 & KW36 The homologation requirements in China (MIIT [2002]353) obviously are planned (end of December 2022) to be sharpened (MIIT publication from 2021-01-27: “Notice on Matters Related to Radio Management in the 2400MHz, 5100MHz and 5800MHz Bands”). A modification register is need on the KW38 and KW36 to pass the new Chinese  requirement with acceptable margin: PA_RAMP_SEL value must be set to 0x02h (2us) instead of 0x01h (1us default value) Modification SW: XCVR_TX_DIG_PA_CTRL_PA_RAMP_SEL(2) in the nxp_xcvr_common_config.c All the details are in the attached file. Note: This SW modification is for China country only. BLE Software KW KW35 | 36

i.MX RT1170 DVFS Demo Dynamic voltage and frequency scaling (DVFS) is a power management technique that allows dynamically reducing power consumption of a CPU by dynamically scaling down supply voltage and CPU frequency. Because the internal DCDC of the i.MX RT1170 cannot cover the needed maximum current requirement at the junction temperature of 125 °C, the DVFS technique can be used to reduce current drain for compatibility with the internal DCDC. Lowering the processor frequency dynamically can help reduce the chip input current demand and ensure that the chip can continue to work at the junction temperature of 125 °C. The demo is attached. Only IAR and armgcc versions are enabled. The corresponding Application Note can be downloaded in the below link. https://www.nxp.com/docs/en/application-note/AN13267.pdf

EIQ Software Application based on OpenCV Neural Network Framework on Layerscape Platforms NXP created eIQ machine learning software for QorIQ Layerscape applications processors, a set of ML tools which allows developing and deploying ML applications on the QorIQ Layerscape family of devices. OpenCV is an open-source computer vision library. It offers a unitary solution for both the neural network inference (DNN module) and the standard machine learning algorithms (ML module). It includes many computer vision functions, making it easier to build complex machine learning applications in a short amount of time and without being dependent on other libraries. This document describe applications YOLO object detection, Image segmentation, Image colorization, Image classification, Human pose estimation and Text detection developed based on OpenCV DNN framework.

i.MX RT1170 DVFS デモ ダイナミック電圧および周波数スケーリング(DVFS)は、電源電圧とCPU周波数を動的にスケールダウンすることで、CPUの消費電力を動的に削減できる電力管理手法です。i.MX RT1170の内部DCDCは、125°Cの接合部温度で必要な最大電流要件をカバーできないため、DVFS技術を使用して電流ドレインを低減し、内部DCDCとの互換性を確保できます。プロセッサの周波数を動的に下げると、チップの入力電流需要を減らし、チップが125°Cの接合部温度で動作し続けることができます。 デモが添付されています。IAR と armgcc のバージョンのみが有効になります。 対応するアプリケーションノートは、以下のリンクからダウンロードできます。 https://www.nxp.com/docs/en/application-note/AN13267.pdf

NFC ON KW In the process of practical application, customers often need the combination of ble + NFC. At present, our IOT-DK006 is the only development board with NFC module. But the NFC example is not perfect. So we porting the library of NFC reader- PN7150, to support KW series microcomputer so that KW series can handle the demand of ble + NFC function. Now I will introduce you how to port the NFC lib to KW. 1 PN7150 Introduction PN7150 is the high-performance version of PN7120, the plug’n play NFC solution for easy integration into any OS environment, reducing Bill of Material (BOM) size and cost. PN71xx controllers are ideal for home-automation applications such as gateways and work seamlessly with NFC connected tags. nxf56274_0-1622614472750.png 2 Tools hardware：FRDM-KW36，PN7150 , some wire software：mcuxpresso11.3 package：NXP-NCI MCUXpresso example Project This package contains the nfc library and example that we need. We will refer the ‘NXPNCI-K64F_example’ firstly. Sdk version: 2.2.8， Example: frdmkw36_rtos_examples_freertos_i2c  3 Steps Hardware part：We need connect the PN7150 to KW36 like the picture. Although we can connect the PN7150 to board through the ardunio connector, the pin’s voltage is not enough to drive the PN7150. So we need a wire connected to U1 to get 3.3V.   PN7150 FRDM-KW36 VBAT/PVDD 3.3V VANT 5V GND GND IRQ PTA16 VEN PTC15 SCL PTB0，I2C0 SDA PTB1，I2C0 nxf56274_1-1622614472876.jpeg Software part：We should add the nfc library and directory into our project. You can check the following picture to know what file is necessary. If you want to know how to add directory into our project, you can refer this link. The red line shows what file we need. nxf56274_2-1622614472948.png Please notice that when we add file path into the mcuxpresso configuration, we also need add the path into ‘Path and Symbols’ . nxf56274_3-1622614473031.png We need add some macro into ‘Preprocessor’. nxf56274_4-1622614473134.png We copy the NXPNCI-K64F_example’s main file content into our ‘freertos_i2c.c’. Next, we need modify the file pin_mux.c, tml.c and board.h   In file board.h，add the following macro. Don't forget to enable the pin clock. /* NXPNCI NFC related declaration */ #define BOARD_NXPNCI_I2C_INSTANCE I2C0 #define BOARD_NXPNCI_I2C_BAUDRATE (100000) #define BOARD_NXPNCI_I2C_ADDR       (0x28) #define BOARD_NXPNCI_IRQ_PORTIRQn PORTA_IRQn #define BOARD_NXPNCI_IRQ_GPIO     (GPIOA) #define BOARD_NXPNCI_IRQ_PORT     (PORTA) #define BOARD_NXPNCI_IRQ_PIN      (16U) #define BOARD_NXPNCI_VEN_GPIO     (GPIOC) #define BOARD_NXPNCI_VEN_PORT     (PORTC) #define NXPNCI_VEN_PIN            (5U)     In file pin_mux.c, add head file ‘board.h’. Add the following code in function ’ BOARD_InitPins’. The step is to configure the VEN, IRQ and I2C0. This example contains the I2C1’s code, you can comment them.     /* Initialize NXPNCI GPIO pins below */   /* IRQ and VEN PIN_MUX Configuration */   PORT_SetPinMux(BOARD_NXPNCI_IRQ_PORT, BOARD_NXPNCI_IRQ_PIN, kPORT_MuxAsGpio);   PORT_SetPinMux(BOARD_NXPNCI_VEN_PORT, NXPNCI_VEN_PIN, kPORT_MuxAsGpio);   /* IRQ interrupt Configuration */   NVIC_SetPriority(BOARD_NXPNCI_IRQ_PORTIRQn, 6);   EnableIRQ(BOARD_NXPNCI_IRQ_PORTIRQn);   PORT_SetPinInterruptConfig(BOARD_NXPNCI_IRQ_PORT, BOARD_NXPNCI_IRQ_PIN, kPORT_InterruptRisingEdge); Finally, in file tml.c, modify PORTC_IRQHandler as PORTA_IRQHandler We finished all steps. 4 Results We use ntag to test the reading and writing operation. nxf56274_5-1622614473191.jpeg When the tag is closed to the PN7150, we will get the following message. nxf56274_6-1622614473213.png The text recording is ‘VER=03’. Next, we will modify the text recording We need add the new macro to preprocessor. nxf56274_7-1622614473283.png We can modify the variable NDEF_MESSAGE in function task_nfc_reader to modify the text recording. nxf56274_8-1622614473309.png Then we download the program again. We will see the original text ‘VER=03’ and the text has been modified. Then we read the tag again. We will see the new text. nxf56274_9-1622614473339.png If we want to send the larger text, what should we do? We need modify the macro ‘ADD’. When only 4 characters are sent, ‘ADD’ is 0. And every additional character is added, the ‘ADD’ will add. We modify the tag as ‘Ver=03’, and we have two more characters. So ‘ADD’ needs to be defined as 2 nxf56274_10-1622614473363.png It firstly shows the text ‘Test’. Then it will show the new text ‘Ver=03’. nxf56274_11-1622614473396.png Other tags’ reading and writing operation can be enabled by defining some macro.       BLE Software KW

尝鲜IAR 6.7集成Processor Expert工程代码功能(The Step to integrate Processor Expert code to IAR6.7) 最近有客户问到如何移植PE生成的TSI代码到IAR中，按照常规的方法在把头文件和库文件意义一一包含进来，非常繁琐，于是研究了一下相关的操作。在早期的IAR版本中，需要用户自己手动添加芯片名称，链接文件和包含的路径信息，特别是在PE增加或者删除组件后，需要用户去增减相应的文件，更增加了难度。而在最新版本的 IAR 6.7中集成了对PE工程的链接机制，它可以方便的读取PE工程的XML文件，从而实现移植PE生成的代码到 IAR Embedded Workbench中，相对于早期的IAR版本，主要完成以下几个工作： 自动检测使用的芯片类型； 自动添加PE的LCF连接配置文件； 自动更新包含的头文件路径； PE增加或者删除Component组件后，IAR工程会自动Add 或Delete 相应的组件代码； 尽管IAR完成了一些繁琐的工作，但网上没有太多的资源可以参考，对于首次使用的用户来说还是需要一些探索，为节省大家的时间，下面以一个具体的示例Step By Step的介绍如何在IAR中集成PE的工程。 1. 打开Processor Expert software 新建一个PE的工程并保存生成代码，这个过程比较简单，此处不再赘述，重点讲述一下在IAR中的使用步骤； 2. 在IAR Workbench中"Creat New Project"新建一个空的工程。 3. 保存新建的工程文件到PE工程的文件夹中，需要注意的是此处也可以选择其他路径，但为简便和易维护性上还是建议直接存放到PE工程中。 4. 打开Tools->Options->Project选项，勾选“Enable project connects”，这个选项的目的在于使能 IAR 能够读取Freescale Processor Expert和Infineon DAVE等第三方工具生成.XML文件。 5. 添加PE工程的XML文件，选择Project->Add Project Connection，会弹出链接选择对话框，选择使用Freescale Processor Expert，默认是IAR Project Connection； 6. 点击OK后，选择建立PE工程时生成的工程描述符文件Projectinfo.xml； 7. 完成上面步骤后，在IAR中自动完成以下三方面工作：自动加载PE生成的文件到IAR中，自动安装LCF链接配置文件，自动包含头文件路径。这几个步骤在之前版本的IAR中需要自己手动添加，并且当在PE中重新生成Code时需要重新添加对应的文件； 8. 完成上面步骤之后，需要根据实际情况配置采用的下载/调试器，Project->Options->Debugger->Setup 选择下载Driver，实验中使用的是KL25的FRDM板，所以在PE Macro中选择OpenSDA，点击OK，完成设置； 9. 编译工程，下载Debug； 总结下来，主要完成两个工作：（1）配置使能 Project connection，并导入PE生成的XML文件； （2）配置调试的下载器仿真器； Re: 尝鲜IAR 6.7集成Processor Expert工程代码功能(The Step to Integration Processor Expert code to IAR6.7) <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 问题可以在下面回复： 当您在“Libraries(-l)”中添加一个库时，gcc 链接器知道这是一个 gcc 库，因此无需添加“lib”前缀和“.a”后缀。 但是当您在“杂项”中添加库时，如果文件没有“lib”前缀和“.a”后缀，gcc 链接器就不会认为它是 gcc 库。 Re: 尝鲜IAR 6.7集成Processor Expert工程代码功能(The Step to integrate Processor Expert code to IAR6.7) 我看了一下.xml配置文件，上面显示的库的路径是在工程文件夹下面的,实际上在Open Containing Folder命令中打开的路径也是工程所在的路径，但是并不是库的路径，是他的上级路径，应该是他没有识别到。 你说的那个选项我勾选了（atuo runtime library selection），仍然不行，但是我在选项下面的Additional libraries 中添加了库的路径之后就可以了。 第二个方法就是上面我说的方法，取消链接之后自己添加一遍库，我注意到自动添加的库是带引号的，自己添加的不带引号，不知道这意味着什么。。 下面是XML的路径片段，路径中没有中文     D:\PE_K60\TEST1.0\Project_Settings\Linker_Files\ProcessorExpert.icf           D:\PE_K60\TEST1.0\Sources\TSS\       C:\Freescale\PExDrv v10.3\eclipse\ProcessorExpert\lib\Kinetis\iofiles\       C:\Freescale\PExDrv v10.3\eclipse\ProcessorExpert\lib\Kinetis\pdd\inc\       D:\PE_K60\TEST1.0\Sources\       D:\PE_K60\TEST1.0\Generated_Code\               D:\PE_K60\TEST1.0\Generated_Code\       D:\PE_K60\TEST1.0\Sources\       D:\PE_K60\TEST1.0\Sources\TSS\               D:\PE_K60\TEST1.0\Sources\TSS\       Re: 尝鲜IAR 6.7集成Processor Expert工程代码功能(The Step to integrate Processor Expert code to IAR6.7) 你要查看一下PathName 的路径了，因为默认的路径应该是在TSS的安装目录中，另外在IAR中Linker配置项的library选项配置也需要check一下，需要使能atuo runtime library selection。 Re: 尝鲜IAR 6.7集成Processor Expert工程代码功能(The Step to integrate Processor Expert code to IAR6.7) 您好！ 我按照你的文章使用PE建立了一个关于TSS库的工程，使用IAR编译文件时出现了错误： Error[Li005]: no definition for "TSS_Init" [referenced from D:\PE_K60\test1\Debug\Obj\TSS1.o] Error[Li005]: no definition for "TSS_SetKeypadConfig" [referenced from D:\PE_K60\test1\Debug\Obj\TSS1.o] Error[Li005]: no definition for "TSS_SetSystemConfig" [referenced from D:\PE_K60\test1\Debug\Obj\TSS1.o] Error[Li005]: no definition for "TSS_GetSystemConfig" [referenced from D:\PE_K60\test1\Debug\Obj\TSS_SensorTSI.o] Error while running Linker 我找到错误的原因是：在 文件中       "TSS_KXX_M4.a"     上述路径在IAR中识别为无效路径，导致库中的函数无法引用， 我在IAR加载文件之后，在你说的地4步《打开Tools->Options->Project选项，勾选“Enable project connects” 》中取消了工程链接，删除了IAR工程中包含的TSS_KXX_M4.a文件,然后重新加载了这个文件，这时候编译通过了。 请问这个应该怎么做呢。 我使用的是IAR6.7.1,PE10.3 Re: 尝鲜IAR 6.7集成Processor Expert工程代码功能(The Step to Integration Processor Expert code to IAR6.7) <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 好文档，对我很有用！谢谢！

将 USB 摄像头与 GStreamer 结合使用 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 如果您想在 i.MX6 设备（Linux 内核版本 >= 3.035）上将 USB 摄像头（这些类型的摄像头也称为“网络摄像头”）与 GStreamer 一起使用，您需要动态加载模块或静态编译和链接，并在内核配置中选择（Y）以下配置 设备驱动程序 -> 多媒体支持 -> 视频捕获适配器 -> V4L USB 设备 -> <*> USB 视频类 (UVC) 内核映像构建完成后，将其刷入目标，插入网络摄像头，然后在（目标）终端上运行 gst-启动 v4l2src！mfw_v4lsink 您应该在显示屏上看到相机捕捉到的内容。如果需要对相机源数据进行编码，则需要将编码器放入管道中 gst-launch v4l2src num-buffers=100 !队列！vpuenc编解码器=0！matroskamux！文件接收器位置=输出.mkv 同步=false 我们正在使用某种编解码器（codec=0 表示 mpeg4），使用“gst-inspect vpuenc”检查选项。 i.MX6_全部 多媒体 回复：使用带有 GStreamer 的 USB 摄像头 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 请修复链接！我看不到 最良好的问候！ 回复：使用带有 GStreamer 的 USB 摄像头 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 感谢分享，但当编码“无法协商格式”时，这不适用于我的 2 个符合 UVC 1.1 标准的相机。 vpuenc 需要 TNVP、NV12 或 I420 中的原始 uyv，我可以强制原始输出，但我的相机不支持这些（对文件进行测试给出了 YUY2）。可以使用软件中的颜色转换来完成这项工作（至少在 vga 30 fps 中）： gst启动v4l2src num缓冲区=100！视频/x-raw-yuv！队列 ！ffmpeg色彩空间！队列 ！vpuenc编解码器=6！avimux！文件接收器位置=outputh264.avi 同步=false 在 iMX53 上，有 mfw_ipucsc，但我在 12.09 BSP 上发现的只有 ipucsc.imx，它不起作用，可能只有 DP 路径中的 CSC，这应该在图像转换器中是可能的，但我没有找到任何插件。有人有更好的管道吗？

HOB Quick Start Guide What is HOB? Hob is a graphical user interface for BitBake. Its primary goal is to enable a user to perform common tasks more easily. It basically runs the Bitbake commands on the background while showing a Graphic User Interface. Hob may not work correctly with Daisy metadata as it is getting deprecated in favor of a new web based interface for Yocto under the name Toaster. Here is what you can do with the current version of Hob on the Freescale Community BSP and BSP Release. - Build images - Edit existing image recipes - Create your own image recipes Note: HOB will write the local.conf file and make modifications which may conflict with baking images outside of HOB. In this case you may need to re-run the environment initialization in order to restore the local.conf file. Starting HOB Once the environment has been initialized (using the setup-environment script on the Freescale Community BSP or the fsl-setup-release on the Freescale BSP Release) use the command below. $ hob & The GUI should then appear: You may then select the MACHINE for which you will build and the Layers of your project. HOB  will take and updated the local.conf and bblayers.conf values so the desired BSP layers will already be selected and available MACHINES on these layers will appear on the drop down menu. Once these options are set HOB will parse the recipes and create a dependency tree in order to show available images for that MACHINE. Image File System Types Advance configuration options include image file system types. Please note that HOB does not support the sdcard format so if it is needed it has to be added manually on the local.conf file and then run bitbake outside of HOB. As HOB changed the local.conf file even if the sdcard format was originally available it may be rewrite and no longer available until the following line is added to local.conf. IMAGE_FSTYPES="tar.bz2 ext3 sdcard" Recipes screen On the recipes screen we can see the recipes included on the image and available recipes, then also package groups. Time to bake! After these configurations you may either build the packages using HOB interface or run Bitbake outside of HOB. (In case you wish to have your image on the sdcard format please see the earlier image types clarification) The resulting image will be stored on /tmp/deploy/images/ You may also save your image recipe with the selected customizations. Re: HOB Quick Start Guide Please submit any questions or issues related to this document as a discussion in the community.

S32K14x SRAM ECC注入示例 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ******************************************************************************** 详细描述： 此示例显示了 SRAM ECC 注入。 默认情况下，在对 SRAM_U 区域中的位置进行读取访问时会注入双位 ECC 错误。 这可以通过 SRAM_U 和 DOUBLE_BIT 宏来改变。 ERM 和 MCM 模块都可以检测到错误，并可以调用相应的中断。 虽然只需要 ERM，但为了演示目的，MCM 中断也启用了 其优先级低于 ERM 中断。 首次调用的 ERM 中断会禁用注入机制 这样在堆栈读取访问期间就无法检测到后续错误。 默认的 S32 Design Studio start_up 文件将向量表复制到 SRAM_L 区域。 为了能够在此 SRAM 区域注入 ECC 错误并调用中断， 复制被 __flash_vector_table__ 符号禁用 在start_up.h中声明文件并在S32K144_64_flash链接器文件中定义。 -------------------------------------------------------------------------------------------- 测试硬件：S32K144EVB-Q100 单片机：S32K144 0N57U 调试器：S32DSR1 目标：internal_FLASH ********************************************************************************

iDrive_里程碑_2 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 在这个里程碑中，我们专注于创建控制从设备接收的数据流的基础设施。 我们创建了一个托管在 Google Cloud Platform 中的 Web API 应用程序（ASP .NET），用于存储和解释我们的数据（来自设备），并向移动应用程序发送通知，告知用户汽车被盗（已移动）。 我们还创建了移动应用程序（原生，在 Xamarin.Android 中创建），该应用程序使用 Google Maps API 来嵌入地图片段，用于显示我们设备的位置（以及隐式显示汽车的位置）。 通知系统已准备好投入生产，我们使用 Azure 通知中心作为传递通知的中间件，因为它具有可扩展性、可靠性、包含遥测数据并且安全。 （在 “我的视频” 中查看）

QorIQ Layerscape LS2085/88マルチコア通信プロセッサ、ネットワーキングの未来を支援 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> EUF-NET-T1743 - QorIQ LS2085/88は、汎用性の高いLayerscape 2デバイスです。GPP レイヤーには、8 つの A57/A72 ARM® コアが含まれています。APPレイヤーには、AIOP、PME、DCE、およびSECエンジンが含まれています。WRPPレイヤーには、WRIOP、SATA、およびPCIeエンジンが含まれています。このプレゼンテーションでは、QorIQ LS2085/88プロセッサのさまざまなコンポーネントとターゲットの使用例の概要を説明します。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> EUF-NET-T1743 - QorIQ LS2085/88は、汎用性の高いLayerscape 2デバイスです。GPP レイヤーには、8 つの A57/A72 ARM® コアが含まれています。APPレイヤーには、AIOP、PME、DCE、およびSECエンジンが含まれています。WRPPレイヤーには、WRIOP、SATA、およびPCIeエンジンが含まれています。このプレゼンテーションでは、QorIQ LS2085/88プロセッサのさまざまなコンポーネントとターゲットの使用例の概要を説明します。

LS1021A IoT ホストプロセッサと MKW20 zigbee を使用して色相電球を切り替えるためのクイックデモセットアップ <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> LS1021A IoTホストプロセッサとMKW20 zigbeeを使用して色相電球を切り替えるためのクイックデモセットアップ。ここでは、2 つのステップのセットアップを通じてライティングのデモを行います。最初のステップは、TWR-KW20 EVBを使用して、テストツールと呼ばれるPCツールを介して色相電球を制御することです。 次のステップは、PCテストツールの代わりにホストプロセッサとしてLS1021に移行することです。 KW20 USBドングル、LS1021A、Hue Bulbを使用しています。KW20 USBドングルは、Beekitを介してZigbeeコーディネーターとして構成され、このKW20 USBドングルを接続しLS1021A、LS1021Aオン/オフコマンドを発行して色相電球を切り替えます。その後、フリースケールのLS1021AとMKW20シリーズを使用して簡単なデモを作成できます <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> LS1021A IoTホストプロセッサとMKW20 zigbeeを使用して色相電球を切り替えるためのクイックデモセットアップ。ここでは、2 つのステップのセットアップを通じてライティングのデモを行います。最初のステップは、TWR-KW20 EVBを使用して、テストツールと呼ばれるPCツールを介して色相電球を制御することです。 次のステップは、PCテストツールの代わりにホストプロセッサとしてLS1021に移行することです。 KW20 USBドングル、LS1021A、Hue Bulbを使用しています。KW20 USBドングルは、Beekitを介してZigbeeコーディネーターとして構成され、このKW20 USBドングルを接続しLS1021A、LS1021Aオン/オフコマンドを発行して色相電球を切り替えます。その後、フリースケールのLS1021AとMKW20シリーズを使用して簡単なデモを作成できます

斯洛伐克布拉迪斯拉发理工大学 3KD 团队技术报告 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 为布拉迪斯拉发斯洛伐克理工大学 3KD 队（斯洛伐克）提交技术报告 - 2015 年 EMEA 总决赛 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 为布拉迪斯拉发斯洛伐克理工大学 3KD 队（斯洛伐克）提交技术报告 - 2015 年 EMEA 总决赛

Android CTS Verifier The Compatibility Test Suite Verifier is a supplement to the Compatibility Test Suite. The main difference lies in that the verifier is developed for tests that cannot run on their own so they require user input in order to be tested. These tests would include the audio quality, the touchscreen, accelerometer, camera, etc. There is no “best verifier option”, one CTS complements the other. In this document we will focus on how to perform the Verifier test. Requirements: A PC with the Android SDK installed. Your “Device Under Test” (your development board) Optional >> A second android device with compatible Wifi and Bluetooth Setup Steps: Install de Android SDK on your PC Download the appropriate CTS Verifier APK. The list of APK’s can be found here: https://source.android.com/compatibility/downloads.html Make sure that your Device Under Test has its system date and time set correctly. Install the CTS Verifier APK on the Device Under Test* For more information regarding ADB commands, follow this link: https://community.freescale.com/docs/DOC-102514 Initialization: After the setup is done, you should see the application installed: You will see the list of available tests for manual verification: Video Link : 4502 For each test, you will see detailed instructions to run it, and a “pass” and “fail” buttons. Video Link : 4530 Once you run each test, you will have the posibility to choose the outcome. (in some cases, pass/fail outcome will be determined automatically). The list of tests (for CTS Verifier 5.1_r2) is: Camera: FOV Calibration, Formats, ITS, Intents, Orientation, Video. Car: Car Dock Test Clock: Alarms and Timers Test Device Administration: Policy serialization test, screen lock test. Features: Hardware/Software feature summary Hardware: USB Accessory Test Job Scheduler: Charging constraints, connectivity constraints, idle mode constraints. Location: Battery saving mode test, location mode off test Managed provisioning: BYOD managed provisioning, device owner provisioning Networking: Bluetooth test, Wi-Fi direct test Notifications: CA Cert notification, CA Cert notificacion on boot, notification attention management, notification listener, notificacion package priority Other: Data backup, screen pinning, widget framework Projection: Projection cube, projection multitouch, projection offscreen, projection scrolling, projection video playback, projection widget Security: Keyguard password verification, SUID file scanner. Sensors: Accelerometer mearument, CTS Sensor batching, CTS Sensor integration, CTS sensor test, CTS single sensor test, magnetic field measurement, sensor batching. Streaming: Streaming video quality verifier. Exporting test results: Tap the “save disk” icon. A pop-up will show the path of the report that was created. Video Link : 4531 With the board connected to the PC through USB, pull the report using ADB: To download all reports run : adb pull /mnt/sdcard/ctsVerifierReports/ .

FTF_Austin_FTF-ACC-F1276_2015.pptx This session will explain how Freescale can enable customers to develop 76-81 GHz short and long range radar applications using the MPC577xK MCU, it will explain the concepts of the radar algorithms, including practical aspects such as SDADC or MIPI CSI sampling, Chirp Generation, Data Compression, R,V FFT, Detection and Tracking algorithms, and the benefits of the new Freescale IP that can allow them to improve their system resolution and accuracy. In this session customers will take away a detailed understanding of how to develop fast modulation radar systems using the MPC577xK MCU including the BOM cost advantages it also brings. This session will explain how Freescale can enable customers to develop 76-81 GHz short and long range radar applications using the MPC577xK MCU, it will explain the concepts of the radar algorithms, including practical aspects such as SDADC or MIPI CSI sampling, Chirp Generation, Data Compression, R,V FFT, Detection and Tracking algorithms, and the benefits of the new Freescale IP that can allow them to improve their system resolution and accuracy. In this session customers will take away a detailed understanding of how to develop fast modulation radar systems using the MPC577xK MCU including the BOM cost advantages it also brings. General Re: FTF_Austin_FTF-ACC-F1276_2015.pptx Hi Andrew Robertson I wanted to check to see if you had your final file. I need to do one last review and then convert it to PDF to include it on the FTF App and public community page. Please help to upload this by selecting "Edit" under Actions as soon as possible. Thanks! Re: FTF_Austin_FTF-ACC-F1276_2015.pptx I have loaded the Marcom reviewed version to this link to help document the review cycle. Here are comments after the Marcom review: I have approved this presentation after making minor changes to punctuation. I have other concerns to highlight: Slide 4 says: FMCW operation is independent of the speed or direction of travel of the target high precision. Andrew, is “target high precision” correct? No Summary and Conclusion section exists in this presentation. Andrew, please add a summary/conclusion and upload the final version based on the attached. Hi Andrew Robertson Please take Brian and John's notes into consideration when finalizing your presentation. Please make sure to use the latest version when making any changes. Once you have finalized your presentation please upload the final file here by selecting "Edit" under Actions and click Publish at the bottom of the page no later than Monday, June 15th. Please help to select the Category "4. Final Version - Ready for PDF and Web" when this final version is posted so I know to pull your file for PDF conversion. Re: FTF_Austin_FTF-ACC-F1276_2015.pptx Adding Deactivated user since he will be helping review this file for Lisa Bradley Re: FTF_Austin_FTF-ACC-F1276_2015.pptx Hi andrewrobertson​ I am reviewing a bunch of FTF presentations.  A few comments on yours.... Are you intending to put something after your summary and conclusions?  Can you...   Your closing thoughts, perhaps some URL's like freescale.com/adas or similiar The abstract refers to BOM cost advantages but I don't really see that in the slides (maybe slide 27) but it's a very small reference.  Just wondering if you should call it out more since it was important enough to mention in the abstract. Renee Fortenberry Re: FTF_Austin_FTF-ACC-F1276_2015.pptx Hi Lisa, I just wanted to make sure you were tagged to this file. It is ready for your review. Please let Andy know when you will be pulling the file in case he has additional changes he would like to make before your review. Lisa Bradley Re: FTF_Austin_FTF-ACC-F1276_2015.pptx PPT expert has completed the presentation review. The latest version is posted and ready for Marcom review @Lisa Bradley

基于wxWidgets的分布式信息与控制系统 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 他们开发的控制器采用i.MX53+Linux。 开发了构建分布式信息和控制系统的解决方案。 Prototmpy 已经运行了一年多。 示例： - 控制电磁搅拌（混合器） http://ontecom.com/en/catalog/ems / Rusal，克拉斯诺亚尔斯克。 - 泵站的监测和管理。 - 气候控制系统的监测和控制。 您可以创建智能家居系统和物联网。有使用 PLC（电力线通信）Qualcomm/Atheros 的经验。 在业余时间，我为 PLC（电力线通信）控制/监控组件智能家居开发了预算解决方案。 基于IEC 61131-3标准开发的软件——分布式信息管理系统。 该解决方案是跨平台的。单个系统中可能存在不同架构和不同操作系统的计算机。 此类信号同步控制器 ARM/Linux 和 x86 服务器（Win、Linux、VMS、...） 使用 wxWidgets。 有关这个主题的文章有，但是用俄语。

AMF-ACC-T1647 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> イーサネットは、自動車の車両通信で最も議論されているテクノロジーの1つになっています。このプレゼンテーションでは、車載イーサネットを網羅する規格の概要を説明します。また、さまざまなアプリケーション間でテクノロジーを実装する際の課題にも対処します。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> イーサネットは、自動車の車両通信で最も議論されているテクノロジーの1つになっています。このプレゼンテーションでは、車載イーサネットを網羅する規格の概要を説明します。また、さまざまなアプリケーション間でテクノロジーを実装する際の課題にも対処します。

S32K144 FlexCAN 擬似ネットワーキング STOP モードテストの例 S32DS.ARM.2.2 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ******************************************************************************** 詳細説明: FlexCAN 0 の Pretended Networking モードを利用し、FlexCAN モジュールが MCU を STOP モードからウェイクアップする方法を示します。 タイムアウト イベントおよびマッチ イベントによるウェイクアップが有効です。 また、ピン割り込みを使用して STOP モードを解除することも可能です。 MCU は SW3 ボタンの押下で STOP モードに移行します。 MCU は次のいずれかが発生すると STOP モードを終了します: - 8 秒間 CAN メッセージが受信されない (CAN PN タイムアウト イベント) - 標準 ID 0x554 または 0x555 のメッセージが受信される (CAN PN マッチ イベント) - SW2 ボタンが押下される (PTC12 割り込み) RUN モードでは青色 LED が減光し、ウェイクアップ要因ごとに減光速度が異なります。 ------------------------------------------------------------------------------ テストハードウェア: S32K144 EVB‑Q100 MCU: FS32K144UAVLL 0N57U Fsys: 160 MHz デバッガ: Lauterbach, OpenSDA ターゲット: internal_FLASH ******************************************************************************** 全般

FRDM-A-S32K344: Secure Encrypted Ethernet Demo Secure Encrypted Ethernet Communication using FRDM-A-S32K344  Find the code in Application Code Hub as Secure Encrypted Ethernet End Nodes This project implements a configurable secure encrypted Ethernet communication node that can operate in three different modes—Transmit (TX), Receive (RX) and Intruder —selected at build time using compile‑time macros. Depending on which macro is enabled during compilation, the firmware conditionally includes only the logic required for that mode. /* Macro for NODE selection: Select TX_BOARD, RX_BOARD or INTRUDER_BOARD and * flash its corresponding profile */ #define TX_BOARD (1u) /* TX_BOARD is selected */ #define RX_BOARD (0u) #define INTRUDER_BOARD (0u) TX Node Mode (TX_BOARD) - In this mode, the device encrypts an image and transmits Ethernet frames when the transmission button is pressed. If the encrypt button is pressed, the Ethernet frames will contain the encrypted image. If the encrypt button is not pressed, the Ethernet frames will contain the base image. RX Node Mode (RX_BOARD) - The device listens for incoming Ethernet frames and processes the data to display the received image in the LCD display. When the encrypt button is pressed the decryption is enabled. Intruder Node Mode (INTRUDER_BOARD) - The device listens for incoming Ethernet frames and processes the data to display the received image in the LCD display. Intruder does not have access to decryption. This project has the option to define if the on-board push buttons are used or external user push buttons connected to PTE24 and PTE25. /* Macro for BUTTON selection: Select INTERNAL_BUTTONS or EXTERNAL_BUTTONS and * flash its corresponding profile.*/ #define INTERNAL_BUTTONS (1u) // SW2 = Encryption, SW3 = Transmission #define EXTERNAL_BUTTONS (0u) // PTE24 = Encryption, PTE25 = Transmission   Application Description The application runs on an NXP S32K344 MCU and demonstrates a complete image encryption, transmission, reception, and optional encryption pipeline. The code encrypts an image using the HSE, transmits it over Ethernet, receives encrypted data, decrypts it using HSE, and displays it. The summarized functionality is the next: LCD Display Handling: Initializes an LCD via LPSPI1 and displays an embedded bitmap image AES-128 Encryption/Decryption (ECB mode): Uses Crypto_43_HSE AUTOSAR Crypto Driver, offloads all crypto operations to the Hardware Security Engine (HSE), splits an image into 64‑byte blocks, encrypts each block with AES‑128 ECB Ethernet Transmission (GMAC): Encapsulates encrypted image data into Ethernet frames, Sends frames over GMAC0 and receives incoming frames and reconstructs the encrypted image User Interaction via Buttons: SW3 starts transmission and SW2 grants encryption   Algorithm The main function initialize all pin routing, peripherals and LCD over SPI. Performs setup for Crypto Driver and HSE by loading a key and mark it as valid. (TX) The image stored as a bitmap in ImageDataAuto[] is split into blocks of 64 bytes in order to perform the encryption and store the encrypted output in EncryptedImage[] for secure Ethernet transmission. (TX) Ethernet frame is built manually and is broken into frames of 1024 bytes. (TX) Transmission starts when the transmit button is pressed. When all image data is sent then the transmission resets. (RX) Incoming Ethernet frames are processed in the emac_rx_callback(…) where the payload bytes are extracted and appended into the EncryptedImage[] array. (RX) Once all the image bytes arrives a flag is activated to show the image in the infinite loop. (Intruder) The intruder board can sniff the image sent as long as the Encrypted Button is not pressed. (Intruder) If the Encrypted Button is pressed, intruder board will receive the encrypted array and not be able to decrypt. Crypto Driver and HSE This project makes extensive use of the AUTOSAR Crypto Stack, specifically the Crypto_43_HSE driver and the HSE embedded hardware module as the accelerator performing all AES operations. Some of the key functions and features to understand are: Initialization of HSE Key Catalog: This configures the RAM and NVM key catalogs where the HSE stores key metadata. RetVal = Crypto_43_HSE_Exts_FormatKeyCatalogs(); Loading AES-128 Key into the HSE: The key is transferred into the HSEs secure storage. Crypto_43_HSE_KeyElementSet(APP_AES128_KEY_ID,KEY_MATERIAL_ELEMENT_ID_U32, App_au8Aes128EcbKey_1, APP_AES128_KEY_SIZE); Key Validation: Makes the key available to subsequent crypto jobs. Crypto_43_HSE_KeySetValid(APP_AES128_KEY_ID); AES-128 ECB Job Execution: The CPU does not perform AES operations. The request is passed to the HSE firmware, which executes AES‑128 ECB using its hardware crypto accelerators. Encryption and decryption are performed using their corresponding jobs: Crypto_43_HSE_ProcessJob(APP_SYMMETRIC_CDO_ID, &App_JobAes128EcbEncrypt); Crypto_43_HSE_ProcessJob(APP_SYMMETRIC_CDO_ID, &App_JobAes128EcbDecrypt); HSE-compatible non-cacheable buffers: HSE accesses memory via DMA and cannot read cache-only memory regions. The code places all data buffers exchanged with HSE in special sections defined by: #define CRYPTO_43_HSE_START_SEC_VAR_INIT_8_NO_CACHEABLE Boards: FRDM-A-S32K344 Categories: Communication, Security Peripherals: Siul2, Crypto 43 HSE, ETH 43 GMAC Toolchains: S32 Design Studio IDE 1. Software and Tools 1.1 FRDM Automotive Bundle for S32K3 The demo was developed using the FRDM Automotive Bundle for S32K3. To download and install the complete software and tools ecosystem, use the following link: S32K3 FRDM Automotive Board Installation Package. 1.2 Security Real-Time Drivers Crypto As the application uses cryptography and the Hardware Security Engine (HSE) peripheral, it is necessary to download the Security Real-time drivers Crypto 7.0.0 QLP02 and the S32K344 HSE Standard Firmware to the bundle by following the next steps: Click on the Software Library tab. bundleSoftwareLibrary.png Select S32K3 checkbox in the Devices tab to filter the results. bundleDevices.png Type Security Real-Time Drivers Crypto in the search bar and click in the checkbox to select it. Confirm that the version is 7.0.0_QLP02. bundleCryptoDrivers.png Type S32K344 HSE Standard Firmware in the search bar and click in the checkbox to select it. Confirm that the version is RTM 0.2.55.0. bundleHSE.png Click on Generate Bundle Installer button and confirm that the package contains all the drivers as shown. bundle.png 2. Hardware 2.1 Required Hardware Personal Computer Type-C USB cable Switch Gigabit Ethernet GS108 3 * Ethernet cable 3 * 2.8" TFT touch shield for Arduino 3 * FRDM-A-S32K344 FRDM-A-S32K344-TOP(cropped).png 2.2 Debugger Connector Connect the PEmicro debugger to the Cortex Debug connector Connect debugger USB to PC Power the FRDM-A-S32K344 using the USB-C cable or connect USB C cable directly to the board for power supply and debug capabilities 3. Setup 3.1 Import the Project into S32 Design Studio IDE Open S32 Design Studio IDE, in the Dashboard Panel, choose Import project from Application Code Hub. import_project_1.png Found the demo you need by searching the name directly. Open the project, click the GitHub link, S32 Design Studio IDE will automatically retrieve project attributes then click Next>. import_project_2.png Select main branch and then click Next>. import_project_3.png Select your local path for the repo in Destination->Directory: window. The S32 Design Studio IDE will clone the repo into this path, click Next>. import_project_4.png Select Import existing Eclipse projects then click Next>. import_project_5.png Select the project in this repo (only one project in this repo) then click Finish. import_project_6.png 3.2 Connect Hardware Before connecting the display to the board it is necessary to solder 3 SMD pads to enable SPI transmission. The pads correspond to SI, SO and SCK marked in the silkscreen as 11, 12 and 13 respectivelly (yellow circle in the image). To connect the display to the board, follow the next image to make sure the pins in the board marked by red coincide with the pins in the display marked by red. hardware.png 3.3 Generating, Building and Running the Example Import the HSE using FRDM-A-S32K344 project from Application Code Hub following the steps above. In Project Explorer, right-click the project and select Update Code and Build Project and then go to Debug. The project must be executed twice in order to enable the HSE in the board.Note: This is a mandatory step to compile the Secure Encrypted Ethernet Communication project. In Project Explorer, right-click the project and select Update Code and Build Project. This will generate the configuration (Pins, Clocks, Peripherals), update the source code and build the project using the active configuration (e.g. Debug_FLASH). Make sure the build completes successfully and the *.elf file is generated without errors. UpdateCodeAndBuildProject.png Press Yes in the SDK Component Management pop-up window to continue. If a error appears related to the NXP GCC 10.2 not installed, right click on it and select Quick Fix. Note: This is a mandatory step to compile the Secure Encrypted Ethernet Communication project. To generate the other executables, the macros must be modified to use the other node mode. In the app_cfg.h file within the src folder. Change the macro definition from:  #define TX_BOARD (1u)  to  #define TX_BOARD (0u)  and  #define RX_BOARD (0u)  to  #define RX_BOARD (1u) . To set the intruder, repeat previous steps but set  TX_BOARD  and  RX_BOARD  to  (0u)  and  INTRUDER_BOARD  to  (1u)  in the macro definition for the intruder board. Then clean project and build again to generate the RX node executable. Go to Debug and select Debug Configurations. Select GDB PEMicro Interface Debugging: DebugConfigurations.png Use the controls to control the program flow. Note: The GDB PEMicro Interface Debugging configuration uses default ports 6224 and 7224. In example are provided 2 debug configurations, one with default ports and another one with custom ports to support debugging of 2 boards simultaneously on the same PC. You must change the  C/C++ Application  path in the debug configuration to point to the generated *.elf file, one for TX node and one for RX node. In one launch configuration, select one board (for example USB1) and in the second launch configuration, select the other board (for example USB2). 4. Results When one board is connected as transmitter, one as receiver and other as intruder, using three ETH cables to the Switch, the image on the transmitter board will appear in the display, on the receiver and intruder board, the image will appear when the transmit button is pressed in the transmitter. If the encrypt button is pressed in both transmitter and receiver, the image will show complete but encrypted in the intruder. (function() { var wrapper = document.getElementById('lia-vid-6390689216112w960h540r430'); var videoEl = wrapper ? wrapper.querySelector('video-js') : null; if (videoEl) { if (window.videojs) { window.videojs(videoEl).ready(function() { this.on('loadedmetadata', function() { this.el().querySelectorAll('.vjs-load-progress div[data-start]').forEach(function(bar) { bar.setAttribute('role', 'presentation'); bar.setAttribute('aria-hidden', 'true'); }); }); }); } }})(); (view in My Videos) Questions regarding the content/correctness of this example can be entered as Issues within this GitHub repository or directly in the commentary section. Warning: For more general technical questions regarding NXP Microcontrollers and the difference in expected functionality, enter your questions on the NXP Community Forum This project implements a configurable secure encrypted Ethernet communication node with the transmission of a large data image. FRDM-Training MCU

ST7701 drivers Hello I'm trying to communicate with a ST7701 display controller. Are some examples available? Can anyone share if possible? I'm using an i.MX RT1170 board. In the SDK examples I found the drivers for the HX8394, RM68191 and RM68200 display controllers. I would like to find something similar for ST7701. Can anyone help me please? Thank you and kind regards, Francesco Solito Re: ST7701 drivers Hi @SolitoFrancesco, At the moment, we don't have any driver support in our SDKs for the ST7701 display controller. The integration with this controller would have to be done manually. It is important to adjust the resolution values, synchronization signals and clock frequencies of the LCDIF module to allow compatibility with the display controller. If using the EVK, you can use the SDK drivers and adjust the values of the following functions: BOARD_InitLcdifClock() BOARD_InitMipiDsiClock() BOARD_SetMipiDsiConfig() These functions along with the macros for the synchronization values and are all referenced on the "display_support.c" file, which will be the main file to focus on when adjusting the support for your display controller.   Also make sure to look into the following application note, as it goes into a lot more detail about how the setup for an LCD display works and other useful considerations: i.MX RT eLCDIF RGB Mode Use Case (nxp.com)    BR, Edwin. Re: ST7701 drivers Good morning I modified the files you mentioned, following the indications that I received from the display manufacturer and from the driver manufacturer. I'm able to write and read into the driver registers through MIPI. I can see the differential MIPI waveforms with oscilloscope (also after the "configuration" phase), but I'm still not able to see anything on the display. I'm using the demo example from NXP SDK called "mipi_dsi_compiance_test". Can you please try to help more? Thank you and kind regards, Francesco Solito Re: ST7701 drivers Hi @SolitoFrancesco, Have you been able to debug your code while running? Do you see any error message being printed? And what data patterns do you see on the data line? Do these patterns coincide with the expected ones described on the readme.md file? BR, Edwin. Re: ST7701 drivers Hello, I have the same situation (same driver and resolution, and the base is a test example that worked on the devboard). The controller is configured, and I can also read the statuses (without any errors), and the data on the DSI lines is present, but the screen displays nothing. Changing the videoMode in dsi_dpi_config from kDSI_DpiBurst to other modes also has no effect. It looks like the screen isn't accepting the video stream?  Re: ST7701 drivers Hello. The example project works correctly with the display DEMO_PANEL_RK055MHD091. Then I switched to the panel that I have to use in my final application. It has different resolution (480x800) and so I adapted the defines. Then I changed the drivers (fsl .h and .c files) and I'm able to communicate with my display. I can write and readback the registers. But after the configuration of the display, when the example project starts sending the image buffer, I can see the MIPI waveforms on the oscilloscope, but nothing on the display. Consider that the display is not broken, because I tried to turn on all the pixels through the dedicated command and I can see the screen completely white. What I don't understand is if the problem is in the configuration of the display or in something else that I have to adapt in the example project. I contacted the display manufacturer and the controller manufacturer, but I need as much help as possible from all sides. Is it possible to get the fsl drivers for the controller that is mounted in my display? It is a Sitronix ST7701. Please let me know. Thank you and kind regards, Francesco Re: ST7701 drivers Hello Rino I'm making a comparison between my settings and yours (at the end I'll upload here). In the meanwhile, what I noticed is that I'm using a ST7701, instead you are probably using a ST7701S (with S suffix). I think they are similar but I'm not sure. The thing that I noticed is that the display now works even if I don't make any initialization at all. It starts "slowly" and with low britghteness, but it works. Then, if I only sends the settings from 0xE0 to 0xEF (that aren't documented in the ST7701 datasheet), the display start up very fast and with the correct colors. It seems that all the other settings are not necessary (it sounds strange). Let's keep in touch. I'll share the comparison when I'm finished. Thank you very much again. Kind regards, Francesco Re: ST7701 drivers Hello Francesco,  I managed to get the display working. In the DisplayTFT_SetMipiDsiConfig function, add the line: dsiConfig.enableNonContinuousHsClk = true; for example, after these lines: DSI_GetDefaultConfig(&dsiConfig); dsiConfig.numLanes = DISPLAY_MIPI_DSI_LANE_NUM; dsiConfig.autoInsertEoTp = true; Assuming you have the display IC configured correctly (if necessary, I can share the configuration for my screen) and the display clock (my settings are around 26MHz). Best regards, Chris Re: ST7701 drivers Hello Rino Thank you very much for your suggestion. It seems to work also in my application. Great. I probably need to better setup something, but now I can see the image on the screen. Please if possible share your configuration, so I can compare with mine to better refine it. If I see something different I'll tell you here. Thank you again. Where did you came up the the enableNonContinuousHsClk setting? Kind regards, Francesco Re: ST7701 drivers Hello,  the file was created based on other drivers in the SDK. You can still change the delays to shorter ones. This morning, I confirmed the configuration sequence and made a few changes as recommended by the display manufacturer, but there was no further improvement, so I started taking a closer look at the DSI configuration itself. I know the clocks were fine, and so was the video mode (burst mode), so the only options left were those for the DSI itself. Familiarizing myself with (and other parts in docs): https://docs.nxp.com/bundle/AN13573/page/topics/continuous_vs_non-continuous_clock.html BR, Chris  Re: ST7701 drivers Hello Rino As promised, please find in attachment the settings comparison between yours and mine. I didn't go in details, but if me or you will find something interesting in the differences, please let's continue to write here. Kind regards, Francesco Re: ST7701 drivers Hello Francesco, Sorry for the delay. I looked through your comparison and noticed a lot of differences, partly due to the screens themselves (we have a glass/touch/screen sandwich, and there was a configuration fix for that – or at least that's what the supplier explained 🙂 ). Some settings, like power control, aren't required for startup, but for quality improvement (contrast/gamma settings). And what's funny is that the whole "Sunlight Readable Enhancement" thing, I think they called it, is required, regardless of whether we're running it or not. Based on this data, it automatically sets optimal parameters. If they're incorrect or missing (default values), it takes a while to automatically set them -> hence the slow startup, as you've noticed. The documentation itself can be quite irritating, many of the commands are undocumented, and without them, it's often impossible to fully start the screen. This isn't just with this model, I've encountered this with several other Sitronix models. Kind regards, Chris