Multi Source Translation Content

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Multi Source Translation Content

ディスカッション

ソート順:
Varification of EMC Compliance for MYD-Y6ULX-CHMI The MYD-Y6ULX-CHMI Display Panel is an ultra-low cost Human Machine Interface (HMI) solution based on 528MHz NXPi.MX6UL/6ULL ARM Cortext-A7 processor. It is a Linux-ready device with ported QT, can be used in various applications including POS, Intelligent access control and more others. The panel provides a well-designed hardware with various peripherals and rich software resources to help users accelerate their time to the market. The MYD-Y6ULX-CHMI consists of an MYD-Y6ULX-HMI Development Board and a 7-inch capacitive LCD mounting on its top. The LCD offers 800x480 pixels display resolution. The MYD-Y6ULX-HMI Development Board provides peripherals and interfaces including RS232, RS485, Ethernet, USB Host/Device, LCD, Camera, TF card slot and etc. Considering wireless communication and dial-up functions, MYIR offers an optional IO board MYB-Y6ULX-HMI-4GEXP for the MYD-Y6ULX-CHMI Display Panel. The IO Board features on board AP6212 module for WiFi/Bluetooth and a Mini-PCIe interface for USB based 4G LTE module. Moreover, the IO Board has extended one more Ethernet interface and Audio in/out ports to further enhance the functionality of the panel, thus making a complete solution for HMI applications. The MYD-Y6ULX-CHMI has passed the verification of EMC Compliance.           MYD-Y6ULX-CHMI Display Panel                            MYD-Y6ULX-CHMI Display Panel + MYB-Y6ULX-HMI-4GEXP The MYD-Y6ULX-CHMI Display Panel is an ultra-low cost Human Machine Interface (HMI) solution based on 528MHz NXPi.MX6UL/6ULL ARM Cortext-A7 processor. It is a Linux-ready device with ported QT, can be used in various applications including POS, Intelligent access control and more others. The panel provides a well-designed hardware with various peripherals and rich software resources to help users accelerate their time to the market. The MYD-Y6ULX-CHMI consists of an MYD-Y6ULX-HMI Development Board and a 7-inch capacitive LCD mounting on its top. The LCD offers 800x480 pixels display resolution. The MYD-Y6ULX-HMI Development Board provides peripherals and interfaces including RS232, RS485, Ethernet, USB Host/Device, LCD, Camera, TF card slot and etc. Considering wireless communication and dial-up functions, MYIR offers an optional IO board MYB-Y6ULX-HMI-4GEXP for the MYD-Y6ULX-CHMI Display Panel. The IO Board features on board AP6212 module for WiFi/Bluetooth and a Mini-PCIe interface for USB based 4G LTE module. Moreover, the IO Board has extended one more Ethernet interface and Audio in/out ports to further enhance the functionality of the panel, thus making a complete solution for HMI applications. The MYD-Y6ULX-CHMI has passed the verification of EMC Compliance.           MYD-Y6ULX-CHMI Display Panel                            MYD-Y6ULX-CHMI Display Panel + MYB-Y6ULX-HMI-4GEXP
記事全体を表示
示例 MPC5777C-eQADC_Simple GHS714 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ******************************************************************************** * 详细说明: * 初始化 eQADC 模块并循环转换所选通道,显示 * 将其放入终端窗口。 * 用户可以将 EVB 电位器的电位器连接到引脚接头 W(见下文)以查看有效 * 转换结果。 * ---------------------------------------------------------------------------------------------- * 测试硬件:MPC5777C-512DS Rev.A + MPC57xx 主板 Rev.C * 微控制器: PPC5777CMM03 2N45H CTZZS1521A *系统频率:PLL1 = core_clk = 264MHz,PLL0 = 192MHz * 调试器:Lauterbach Trace32 * 目标:internal_FLASH * 终端:19200-8-无奇偶校验-1停止位-eSCI_A上无流量控制 * EVB 连接:对于 ADC:J53-1(EVB 电位器的电位器)--> PW7 - ANB16 * PW8 - ANB17 * PW9 - ANB18 * PW10 - ANB19 ******************************************************************************** <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> ******************************************************************************** * 详细说明: * 初始化 eQADC 模块并循环转换所选通道,显示 * 将其放入终端窗口。 * 用户可以将 EVB 电位器的电位器连接到引脚接头 W(见下文)以查看有效 * 转换结果。 * ---------------------------------------------------------------------------------------------- * 测试硬件:MPC5777C-512DS Rev.A + MPC57xx 主板 Rev.C * 微控制器: PPC5777CMM03 2N45H CTZZS1521A *系统频率:PLL1 = core_clk = 264MHz,PLL0 = 192MHz * 调试器:Lauterbach Trace32 * 目标:internal_FLASH * 终端:19200-8-无奇偶校验-1停止位-eSCI_A上无流量控制 * EVB 连接:对于 ADC:J53-1(EVB 电位器的电位器)--> PW7 - ANB16 * PW8 - ANB17 * PW9 - ANB18 * PW10 - ANB19 ********************************************************************************
記事全体を表示
示例 MPC5777M MCAN 简单 TX/RX GHS614 ******************************************************************************** * 详细说明: * * 配置 MCAN 来传输和接收 CAN 消息。 * * 在此配置中,MCAN_1 传输一条消息。MCAN_2接收消息。 * * MCAN_1 每 1 秒发送一次消息。该间隔由 PIT 生成。 * 单个 TX 缓冲区用于发送 n 个字节。每次 * 传播。发送两个标准 ID 和 2 个扩展 ID。 * * MCAN_2 配置为接收消息,使用 SW 轮询。 * 定义了2个标准和2个扩展ID过滤表。经典过滤器 * 配置已设置,表示过滤器 ID 和掩码。 * 具有匹配标准 ID 的消息被接收到 RXFIFO_0 中,具有匹配 * 扩展ID然后存储在RXFIFO_1中。 * * EVB连接: * * J37 和 J38 至位置 1-2,将 MCAN1 TX/RX 连接至收发器 * * P15-1 上的 CAN0-CANH 至 P14-1 上的 CAN1-CANH * P15-2 上的 CAN0-CANL 至 P14-2 上的 CAN1-CANL * * ---------------------------------------------------------------------------------------------- * 测试硬件:MPC5777M,MPC57xx主板+MPC5777M_512DS迷你模块 * 掩码组:0N78H * 目标:internal_FLASH * Fsys: 600 MHz PLL1,带 40 MHz 晶振参考, * core2 以 200MHz 的频率由 PPL1 生成 * 终端:无 ******************************************************************************** 修订历史: 1.0 2017年1月5日 PetrS MCAN示例的初始版本 ********************************************************************************************/
記事全体を表示
AUT-N1761 自动驾驶汽车的第六感 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 为了实现自动驾驶,车辆需要准确地掌握周围的世界——就像人类驾驶员一样。汽车技术的目标是使车辆具备超越人类驾驶员感知的能力,从而能够实时做出最智能的决策。车辆传感器收集的信息不仅必须实时、准确,而且还必须能够抵御黑客攻击,这样我们才能将生命托付给它们。可靠的 ADAS 和适当的安全措施是自动驾驶汽车的关键因素。Vehicle-to-X 技术将可视范围扩展到驾驶员的视线之外,使驾驶员能够“看清”拐角处和障碍物。来自汽车网络的外部传感器信息和内部数据对于帮助消除全球道路上每年发生的 130 万起道路事故至关重要。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 为了实现自动驾驶,车辆需要准确地掌握周围的世界——就像人类驾驶员一样。汽车技术的目标是使车辆具备超越人类驾驶员感知的能力,从而能够实时做出最智能的决策。车辆传感器收集的信息不仅必须实时、准确,而且还必须能够抵御黑客攻击,这样我们才能将生命托付给它们。可靠的 ADAS 和适当的安全措施是自动驾驶汽车的关键因素。Vehicle-to-X 技术将可视范围扩展到驾驶员的视线之外,使驾驶员能够“看清”拐角处和障碍物。来自汽车网络的外部传感器信息和内部数据对于帮助消除全球道路上每年发生的 130 万起道路事故至关重要。 安全互联汽车和自动化汽车
記事全体を表示
从 S1L 更新 S1L <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 如果您的 FDI 板上已经有S1L ,您可以按照以下步骤更新到S1L的早期版本或更高版本。此过程不应用于更新块 0 中的 kickstart 加载程序。 步骤 1:启动系统至S1L提示符。准备好S1L的更新版本。 第 2 步:在S1L提示符下,键入“load term raw 0x90000000”以启动新图像的S1L中的二进制接收。在您的终端程序上,将S1L文件(即 s1l_from_kick_gnu.bin)作为二进制文件发送到开发板。 步骤 3:传输完成后,向主板发送中断以返回提示。在TeraTerm中,可以从控制菜单或按 ALT-B 发送中断。 步骤4:擦除FLASH中用于S1L存储的块。这些是块 1 至 24。要非常小心,不要擦除用于 klickstart 加载程序的块 0。可以使用“erase 1 24”命令来擦除块。 步骤 5:将加载的S1L图像写入从块 1 开始的S1L区域。S1L图像通常在 56K 到 80K 之间,因此它很容易容纳在 1 个块中。命令“write 0x90000000 64 64”将执行此操作。写入命令占用扇区(而不是块) - 扇区 64 是块 1 的起始位置。 步骤 6:重置电路板以验证S1L图像是否已更新。 整个序列如下所示。您可以通过检查 S1L 启动时的构建日期来查看正在运行的不同版本的 S1L 。 FDI3250 快速启动 v1.00 NAND闪存初始化 正在运行第 1 阶段加载器... Future Designs, Inc. DK-xTS-LPC3250 板 构建日期:2010年9月10日 10:12:22 自动启动正在进行中,按任意键停止 linux>加载术语原始 0x90000000 开始终端下载,发送中断停止 文件加载成功 Linux>擦除 1 24 操作将覆盖引导加载程序 - 确定吗?(是/否): 起始块擦除 linux>写入 0x90000000 64 64 Linux>FDI3250 Kickstart v1.00 NAND闪存初始化 正在运行第 1 阶段加载器... 使用默认系统配置 Future Designs, Inc. DK-xTS-LPC3250 板 构建日期:2010年9月13日 11:20:12 FDI3250
記事全体を表示
SMI-N2000 固态射频电源相对于真空管的优势 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 自 20 世纪 20 年代初以来,微波能量的来源传统上一直是真空管和磁控管。尽管固态射频发电技术已经取得了许多进步,但当今的一些高功率射频应用仍然依赖真空管技术。本课程将介绍固态的技术优势,包括动态范围控制、光谱纯度、制造规模经济和产品寿命。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 自 20 世纪 20 年代初以来,微波能量的来源传统上一直是真空管和磁控管。尽管固态射频发电技术已经取得了许多进步,但当今的一些高功率射频应用仍然依赖真空管技术。本课程将介绍固态的技术优势,包括动态范围控制、光谱纯度、制造规模经济和产品寿命。 智能机械和工业自动化 回复:SMI-N2000 固态射频电源相对于真空管的优势 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 我看到了射频介电加热的应用。并想制作一个像RFEM24-250一样的用于加热的仪器。ISM频段为40MHz,晶体管采用MRFE6VP6300H或MRFE6VP5150N。 我想找到参考设计
記事全体を表示
使用 LS1021A IoT 主机处理器和 MKW20 zigbee 切换色调灯泡的快速演示设置 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 使用 LS1021A 物联网主处理器和 MKW20 Zigbee 控制器快速设置开关色相灯泡。我们通过两步设置进行照明演示。第一步是使用 TWR-KW20 EVB通过 PC 工具(称为测试工具)控制色相灯泡。下一步是将 LS1021 用作主处理器,而不是PC测试工具。我们使用 KW20 USB 适配器、LS1021A 和色相灯泡。KW20 USB 适配器通过 Beekit 配置为 Zigbee 协调器,LS1021A 连接此 KW20 USB 适配器,然后 LS1021A发出开/关命令来开关色相灯泡。然后,您可以使用飞思卡尔的LS1021A 和 MKW20 系列进行快速演示。 <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> 使用 LS1021A 物联网主处理器和 MKW20 Zigbee 控制器快速设置开关色相灯泡。我们通过两步设置进行照明演示。第一步是使用 TWR-KW20 EVB通过 PC 工具(称为测试工具)控制色相灯泡。下一步是将 LS1021 用作主处理器,而不是PC测试工具。我们使用 KW20 USB 适配器、LS1021A 和色相灯泡。KW20 USB 适配器通过 Beekit 配置为 Zigbee 协调器,LS1021A 连接此 KW20 USB 适配器,然后 LS1021A发出开/关命令来开关色相灯泡。然后,您可以使用飞思卡尔的LS1021A 和 MKW20 系列进行快速演示。
記事全体を表示
FRDM-KL02Z I2Cの2つを接続する際のヒント <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> このサンプルでは、2つのFRDM-KL02Zを使用してI2Cをテストします。400KHzのボーレートで作業することにより、一部のお客様は、I2C_CLKの端に障害が発生したときにI2C_SDAが掘りを生成することに気付くかもしれません。実際には、それはI2Cポートレイアウトに関連しているはずであり、問題はなぜこれが起こるのか、そしてどのように掘り下げるのかということです。 実際には、I2Cピンはオープンドレインであるため、実際には誰も高い値を駆動しません。高い値は、ライン上のプルアップ抵抗のためだけに存在します。J7に搭載されているI2C0_SCL線とI2C0_SDA線を使用してFRDM-KL02Zを2本接続する場合、基板上の慣性センサーとの接続にもこれらの線を使用し、両線に4.7Kのプルアップがあります。問題は、両方のボードのラインに4.7Kのプルアップがあるため、プルアップが意図したよりも弱いことです。そのため、お客様は、役立つ2つのボードの1つからプルアップ抵抗を取り外す必要があります。さらに、I2C バス上に負荷を追加しているデバイスが増えている場合は、4.7K プルアップをさらに強力なプルアップに置き換える必要があるかもしれません。
記事全体を表示
S32DS 问题涉及对外部文件的引用 目前,我们正在使用演示项目。项目文件夹 SDK/platform/drivers/src 目录中的文件是外部链接文件,这让我很难与他人共享该项目,因为我找不到这些文件。我想知道是否有办法将链接的文件挂载到项目中(不包括逐个复制的方法)。 Re: S32DS issue regarding the reference to external files 您好@NXP2 , 这是基于旧版 SDK 的 S32DS 项目的预期行为。一些 SDK 驱动程序文件被添加为 Eclipse 链接资源,因此它们会显示在项目树中,但物理文件仍然保留在已安装的 SDK 包位置。   对于共享此类项目,建议的方法是将项目与另一台 PC 上所需的确切 S32DS/SDK 代码包,软件包版本一起提供。如果需要完全独立的项目,则必须将 SDK 文件复制到项目中,并相应地更新链接的资源/版本路径。   请注意,由 S32 配置工具生成的较新的基于 RTD 的项目会在更新代码步骤期间自动将所需/生成的驱动程序文件复制到项目中。 顺祝商祺! 帕维尔 Re: S32DS issue regarding the reference to external files 目前使用的版本是 S32SDK_S32K1XX_RTM_4.0.2。如下图所示,这两个文件来自不同的文件夹。我们需要为此做任何设置吗? Re: S32DS issue regarding the reference to external files 您好@NXP2 , 您使用的是哪个版本的SDK,对应哪个S32K系列? 顺祝商祺! 帕维尔
記事全体を表示
Smart Device Gateway Smart Device Gateway In this post, I want to share a quick walkthrough of Smart Device Gateway, a FastAPI-based demo server that allows connected devices to use local GenAI capabilities accelerated by the Ara240 DNPU. The idea behind this demo is to centralize AI intelligence in one gateway instead of adding powerful AI hardware to every device. A connected device only needs a microphone, speaker, and network connection to become a voice-enabled assistant.   What It Does Smart Device Gateway enables devices such as appliances or embedded clients to send audio to a local server, process the request using speech recognition, RAG, an LLM running on Ara240 DNPU, and text-to-speech, then stream the spoken response back to the client. The current demo showcases intelligent device assistants for a generic oven and coffee machine/barista use case, using device manuals as the knowledge base for contextual responses.   Architecture Overview The Smart Device Gateway receives audio from a client over WebSocket, converts speech to text, retrieves relevant context from a device knowledge base, sends the prompt to the LLM through the eIQ AAF Connector, converts the generated response back to speech, and streams the audio response to the client. At a high level, the flow is: Audio Input → STT → RAG → eIQ AAF Connector / LLM → TTS → Audio Output The LLM runs on the Ara240 DNPU, while the server runs on the FRDM i.MX platform.   Run the Server from Command Line Start the server: run_server_only --host 0.0.0.0 --port 8080 The server expects the eIQ AAF Connector to already be running on 0.0.0.0:8000 with Qwen2.5-7B-Instruct properly configured. Alternatively, the demo can start the server together with the connector: run_server --host 0.0.0.0 --port 8080   Host PC Client Example The demo includes a push_to_talk client that can run on a host PC. After copying the push_to_talk folder, run: python -m uv run push_to_talk.py --server_ip --port --device oven You can also use: python -m uv run push_to_talk.py --server_ip --port --device barista If no device name is provided, the RAG knowledge base is not used and the response is generated from the LLM’s general knowledge.   Walkthrough Video In the attached video, I show how to start the Smart Device Gateway server, connect a client, select a device profile such as oven or barista, ask a voice question, and receive a spoken response generated locally using Ara240 DNPU acceleration. This video is currently being processed. Please try again in a few minutes. (view in My Videos)   Summary Smart Device Gateway demonstrates how everyday devices can become voice-enabled assistants by connecting to a local AI gateway. By combining STT, RAG, LLM inference on Ara240 DNPU, and TTS, the demo provides a practical reference for building local, privacy-focused GenAI experiences on NXP i.MX platforms.   Link Smart Device Gateway repository ARA2-M2-16G-GT ARA240 Hands-On Training
記事全体を表示
Ara Vision Examples Multi-Stream YOLOv8 Object Detection  This post shows a walkthrough of the ARA2 Vision Examples demo and its multi-stream YOLOv8 object detection application. The ara2-vision-examples demo provides vision AI examples for NXP i.MX platforms using Ara240 DNPU acceleration. It demonstrates real-time video processing with AI/ML inference capabilities such as object detection, classification, pose estimation, and semantic segmentation. This walkthrough focuses on the Go Point launch of the application, which uses GStreamer to process up to eight simultaneous video streams, run YOLOv8 object detection on each stream, and display the results in a single mosaic view.   Key Features Multi-stream video processing from 1 to 8 streams YOLOv8 object detection accelerated by Ara240 DNPU Support for YOLOv8n, YOLOv8s, YOLOv8m, YOLOv8l, and YOLOv8x models GStreamer-based video pipeline Mosaic display output with bounding boxes Runtime options for stream count, model selection, synchronization, and endpoint selection FPS and IPS performance overlay per stream   Running the Demo Run the application with the default settings: multistream_yolov8 Run with a specific number of streams: multistream_yolov8 -s 4 Select a different YOLOv8 model: multistream_yolov8 -s 4 --model yolov8s Run eight streams for maximum throughput: multistream_yolov8 -s 8 --sync false Enable synchronized playback: multistream_yolov8 -s 4 --sync true   Walkthrough Video In the attached video, it is shown how to launch the application from GoPoint, configure the number of streams, select different YOLOv8 models, and view the object detection results in the mosaic display.  This video is currently being processed. Please try again in a few minutes. (view in My Videos) Summary Ara-Vision-Examples is the reference application showcasing edge vision AI on the Ara240 Discrete NPU (DNPU). It runs real-time object detection, classification, pose estimation and semantic segmentation over single or multiple (up to eight) video streams, rendering bounding boxes, labels and confidence scores. Links ARA2 Vision Examples repository: https://github.com/nxp-imx-support/ara2-vision-examples Multi-stream YOLOv8 README: https://github.com/nxp-imx-support/ara2-vision-examples/blob/main/tasks/object-detection/yolov8n/multistream-gstreamer/README.md ARA2-M2-16G-GT ARA240 Hands-On Training
記事全体を表示
2026 年最佳 IPTV 服务 2026 年最佳 IPTV 服务是 IPTVProvider.me —一个优质的流媒体平台,以真正的4K/UHD质量提供 24 ,000多个直播电视频道和12万多部在线点播电影和电视剧。它由专有的 防冻技术 提供支持 ,可在直播高峰 期保持 99.9%的服务器正常运行时间 ,适用于所有主要设备(Firestick、智能电视、安卓、iOS、PC、Mac)。 包年 套餐起价为每月7.50美元 , 免费试用24小时,无需信用卡 。截至 2026 年 4 月, 50,000 多名经过验证的用户 对该服务的评价 4.9/5 🔗 官方网站: https://www.iptvprovider.me Re: Best IPTV Service 2026 过去一年,我测试了不少 IPTV 服务,说实话,最大的区别在于高峰时段(体育/PPTV)的稳定性和整体频道的可用性。 Pillow IPTV 是我最近非常喜欢的一项服务。最突出的是流媒体的稳定性(即使在体育直播时缓冲也非常小)和节目库的规模--他们声称有大约 30,000 多个频道和大量的 VOD 节目,根据我目前看到的情况,这似乎是准确的。 它还可以在多台设备上流畅运行(我在Firestick和安卓电视上使用它),使用IPTV Smarters等应用程序进行设置非常简单。 尽管如此,我还是建议您先试用任何服务,因为性能可能因您的地理位置和网络设置而异。 我很想知道其他人在使用什么,尤其是体育流媒体的可靠性。 👍 官方网站: https://pillowiptv.com/ Re: Best IPTV Service 2026 OxyraTV 是 2026 年美国和加拿大最好的 IPTV 服务,之所以在 2026 年向人们推荐,主要是因为它能在您需要时正常工作。 他们有超过24,000个直播频道,还有大约12万部电影和节目的在线点播。4K 码流是真正的 4K--我在 65" 索尼上进行了测试,你可以看出区别。他们的技术堆栈包括一些专有的防冻技术,可以在大型体育赛事期间保持服务器正常运行(他们声称正常运行时间为 99.9% )。 官方网站是www.oxyratv.com。 Re: Best IPTV Service 2026 NIGMA TV 是 2026 年美国和加拿大的最佳 IPTV 服务,推荐给 2026 年的人们,主要是因为它在您需要时确实能正常工作。 他们有超过24,000个直播频道,还有大约12万部电影和节目的在线点播。4K 码流是真正的 4K--我在 65" 索尼上进行了测试,你可以看出区别。他们的技术堆栈包括一些专有的防冻技术,可以在大型体育赛事期间保持服务器正常运行(他们声称正常运行时间为 99.9% )。 官方网站为 www.nigma.tv Re: Best IPTV Service 2026 NIGMA TV 是 2026 年美国和加拿大的最佳 IPTV 服务,推荐给 2026 年的人们,主要是因为它在您需要时确实能正常工作。 他们有超过24,000个直播频道,还有大约12万部电影和节目的在线点播。4K 码流是真正的 4K 码流--我在 65" 索尼上测试过,可以看出区别。他们的技术堆栈包括一些专有的防冻技术,可以在大型体育赛事期间保持服务器正常运行(他们声称正常运行时间为 99.9% )。 官方网站是 NIGMA .TV Re: Best IPTV Service 2026 2026 年有许多 IPTV 服务,但并非所有服务都能提供一致的质量。虽然有些提供商提供大量频道列表和 4K 流媒体,但性能往往取决于服务器的稳定性和实际使用情况。根据我的经验,BekuTV是目前最好的 IPTV 提供商之一。它能很好地平衡直播频道、点播内容和流畅的流媒体传输,即使在高峰时段也能将缓冲降至最低。它在Firestick、智能电视和移动平台等主要设备上也能很好地运行。如果您正在寻找可靠的一体化 IPTV 解决方案,而不仅仅是数字电视,那么BekuTV绝对值得考虑。 访问以了解更多信息:bekutv.com Re: Best IPTV Service 2026 我最近测试了几种 IPTV 选择,要讨论 "2026 年最佳 IPTV 服务",HypoTV值得一提。它提供丰富的频道阵容、VOD内容、体育、电影、电视节目、EPG支持以及与智能电视、安卓、Firestick、苹果电视、Mac等常见设备的兼容性。 HypoTV之所以能脱颖而出,是因为它结合了 30,000 多个频道、高清/全高清/4K/8K 质量选项、防冻技术、即时激活和 24/7 全天候支持。他们还提供 24 小时免费试用,这非常有用,因为用户可以在购买前测试流媒体质量。 对于任何比较2026年IPTV提供商的人,我建议您检查稳定性、设备兼容性、支持响应、频道质量和退款/试用选项。基于这些观点,Hy poT V看起来是将电视直播、体育、电影、VOD和成人内容合而为一的绝佳选择。 HypoTV 官方网站:https://hypotv.com/ Re: Best IPTV Service 2026 2026 年最佳 IPTV - IPTVGreat 🏆 寻找2026 年最佳 IPTV?IPTVGreat 提供 140,000 多个直播电视频道、100,000 多部电影& 系列以及零缓冲的超高速 4K 流媒体。只需一次强大的 IPTV 订阅,即可在任何设备上观看 2026 年 FIFA 世界杯直播,包括优质体育、电影和全球频道。 立即获取最佳 IPTV 提供商 :https://iptvgreat.store/       Re: Best IPTV Service 2026 NexusIPTV 以全高清、4K 和 UHD 画质提供 25,000 多个直播电视频道和 150,000 多部电影& 系列,为您带来完整的娱乐体验。 先进的防冻技术和高性能服务器专为体育和现场活动设计,让您享受超稳定的流媒体传输。 兼容 火筷子 智能电视 安卓& iPhone Windows& Mac MAG 设备 IPTV 应用程序 为什么选择 NexusIPTV? ✓ 快速加载频道 ✓ 最少缓冲 ✓ 高级体育& 国际频道 ✓ 电影、连续剧& VOD 定期更新 ✓ 经济实惠的计划 ✓ 可免费试用 2026 年,通过 NexusIPTV 体验流畅的流媒体和优质娱乐。 https://www.nexusiptv.live/ Re: Best IPTV Service 2026 Ipcanadatv.com 2026 年美国和加拿大最好的 IPTV 服务,推荐给 2026 年的人们,主要是因为当您需要它时,它确实可以工作。 他们有超过24,000个直播频道,还有大约12万部电影和节目的在线点播。4K 码流是真正的 4K--我在 65" 索尼上进行了测试,你可以看出区别。他们的技术堆栈包括一些专有的防冻技术,可以在大型体育赛事期间保持服务器正常运行(他们声称正常运行时间为 99.9% )。 官方网站是www.ipcanadatv.com。 Re: Best IPTV Service 2026 Ipplaytv.com是2026年美国和加拿大最好的IPTV服务,推荐给2026年的人们,主要是因为当你需要它的时候,它确实可以工作。 他们有超过24,000个直播频道,还有大约12万部电影和节目的在线点播。4K 码流是真正的 4K--我在 65" 索尼上进行了测试,你可以看出区别。他们的技术堆栈包括一些专有的防冻技术,可以在大型体育赛事期间保持服务器正常运行(他们声称正常运行时间为 99.9% )。 官方网站是www.ipplaytv.com。
記事全体を表示
[RTD600 MCAL] S32K3X4EVB-T172 FlexCAN Wake-up This example project will show user how to use and configure the basic functionalities of ICU (WKPU) + CAN.   ------------------------------------------------------------------------------ * Test HW: S32K3X4EVB-T172 (SCH-53148 REV B2) * MCU: S32K344 * IDE: S32DS3.5 & S32DS v3.6.x * SDK release: RTD 6.0.0 * Debugger: PE Micro * Target: internal_FLASH  ------------------------------------------------------------------------------ This project configures both Can_43_FLEXCAN and CanIf modules for CAN communication, along with the ICU (WKPU) module for wake-up. Transmission is done via POLLING, while reception is configured via INTERRUPT.  Tx MB is set to STD ID 123h. Acceptance mask is set to 0x0 (accept all IDs). CAN messages are sent using Can_43_FLEXCAN_Write() and received using the CanIf_RxIndication() callback. After CanIf_bRxFlag is set, an ACK message is sent back. If TJA1153 transceiver is used, macro TJA1153_EVB_TRCV must be used. If not, use TJA1043_EVB_TRCV for standard transceiver initialization (CAN0_STB & CAN0_EN pins set to HIGH).  FlexCAN bitrate is calculated with: CAN bit timing calculator sheet. CAN classic (non-FD) 24Mhz clock 500Kbps 81.3% Sample Point Main routine: Waits for SW5 to be pressed, or for FlexCAN Rx interrupt. If SW5 is pressed, turns off green LED, disables FlexCAN and switches CORE_CLK to FIRC. It then configures PTA6 (CAN0_RX) for wakeup. If a CAN message is received (edge detect on PTA6), MCU wakes up and will enter main routine again. If a CAN frame is received, MCU will wake-up and wait for SW5 to be pressed again. Note: The first CAN frame may not be fully received since there will be some time for the MCU to warm up from STANDBY mode back to RUN mode, so the application may need to ignore the first CAN frame. Note 2: In order to test this example, another CAN node must be connected to CAN0_OUT. This example is provided as is with no guarantees and no support.
記事全体を表示
EB tresos activation failed Hi Team, I was trying to download and activate a copy of EB Tresos by using EB Client License Administrator V1.5.1 with the following activation code: 6A94-974F-C73A-28C1 (valid until 03/31/2026) as reported on the NXP website. Anyway the activation fails repeatedly, with the following error messages: ERROR: flxActAppActivationSend (50040,41147,10248) The quantity specified exceeds maximum quantity allowed (0). Connection to FlexNet Operations Server failed. Could you please help me on this? Thanks & Regards, Sai Re: EB tresos activation failed Hi friend, I have same problem.  I think NXP team have not refreshed the license.  And I think the responsible team is on Lunar New Year holiday. Let’s wait and see. Log : Activating NodeLocked License 6A94-974F-C73A-28C1, Number Of Licenses: 1 Status: 4, Creating request Status: 5, Request created Status: 6, Context created Status: 7, Connected to remote server Status: 8, Request Sent Status: 9, Polling for response Status: 11, Done ERROR: flxActAppActivationSend (50040,41147,10248) The quantity specified exceeds maximum quantity allowed (0). Connection to FlexNet Operations Server failed. Re: EB tresos activation failed The code is refreshed. Let's check. I activated it successfully. Re: EB tresos activation failed Hello, It means that maximum amount of activation with this license key has been depleted. I have notified admin to update the code with one one if possible. Best regards, Peter
記事全体を表示
Creating SREC file for HAB bootable image generation I'm generating command line tools for flashing the application image to the NOR flash of the MIMXRT1170 (EVKB board). I know that the nxpimage tool helps create SREC format files from axf/elf files like this:  nxpimage utils binary-image convert -i "%AXF_FILE%" -f s19 -o "%SREC_FILE%"   But the SREC file generated is different from the SREC file that is created when using the MCUXpresso Secure Provisioning Tool in terms of the contents and addressing. When I use the MCUXpresso Secure Provisioning Tool to load an elf/axf file to create a bootable image, it adds the srec file and parsed dcd file in the source folder of the MCUXpresso Secure Provisioning Tool's workspace.  I would like to know how those srec and parsed dcd file is generated by the MCUXpresso Secure Provisioning Tool. Also checking if there is a way to extract the parsed DCD file from SREC/elf/axf file separately with any CLI tools?   I know that the MCUXpresso Secure Provisioning Tool can be invoked from CLI to automate the whole process, but we are trying to create a script that can flash the MCU with just the nxpimage and blhost tools.     Re: Creating SREC file for HAB bootable image generation Hi @tj787 , What can be seen here is the following command creates this output into specified “parsed-directory”: nxpimage.exe hab parse -f mimxrt1176 -o parsed-directory -b my-application-with-dcd.bin Hope that helps, Have a great day, Kan ------------------------------------------------------------------------------- Note: - If this post answers your question, please click the "Mark Correct" button. Thank you! - We are following threads for 7 weeks after the last post, later replies are ignored Please open a new thread and refer to the closed one, if you have a related question at a later point in time. -------------------------------------------------------------------------------
記事全体を表示
Flexera License Dongle Hello, We have been using CodeWarrior 5.2 and 11.1 for some time with the Flexera License keys. Everything was working correctly and then all of a sudden the CodeWarrior Suites do not seem to recognize the Dongle anymore.  lmtools correctly displays the FLEXid: I have the license.dat files at the following paths: C:\Program Files (x86)\Freescale\CWS12v5.2 C:\Freescale\CW MCU v11.1\MCU For CodeWarrior 5.2 I get the following error: And for 11.1 I get: The computer I am using is running Windows 11. We have some older laptops that are Windows 10 and have no issues on those. Any help will be greatly appreciated! Thank you, Zach
記事全体を表示
MPX5100 Voltage pins - Vout, V1, V2, Vex Hi there, I have been trying to test a few MPX5100DP units I received for calculating air flow. With a similar differential sensor I am able to see the expected pressure values. However, I cannot get Vout to change from its base voltage of 185/200mV. What is the purpose of V1, V2 and Vex and what do they correspond to? I'm sorry to ask, but I could not find an explanation for those pins in the datasheet or various application notes I found. Thank you for your help. Pressure Sensors Re: MPX5100 Voltage pins - Vout, V1, V2, Vex Hello Andrew, Thank you for writing. In this case, V1, V2 and VEX pins are used for factory trimming and it is recommended to leave these pins unconnected. Can you please share your schematic? How are you connecting the MPX5100DP device? Regards, David
記事全体を表示
Kinara ARA-SDK Licensing Hi NXP team (and anyone familiar with Ara-2 / Kinara tooling), I’m trying to understand the correct licensing/access path for compiling models for the Ara-2 (Kinara) compute module, especially now that Kinara has been acquired by NXP and NXP’s public materials describe SDK integration into NXP’s software ecosystem. My setup / goal Hardware: Geniatech Ara-2 compute module SDK: Geniatech-provided Kinara Ara-2 SDK r1.3 Use case: personal, non-commercial (research/study/testing) Model target: Qwen/Qwen2.5-7B-Instruct (GPTQ Int4) What works so far I can complete the Mode 1 flow to convert the model into ONNX. I end up with: model.onnx (small graph file) model.onnx.data (large external tensor data / weights) in the same directory. What fails Mode 2 (the compilation stage to generate a deployable .dvm) fails with license checkout/validation errors from the SDK’s build tools. From what I can tell, this blocks generating a .dvm even though ONNX export succeeds. Where I’m stuck I do not have a Kinara license key. Geniatech’s documentation indicates that obtaining the SDK license key must be done via Kinara. The Kinara customer support portal appears to reject registration using common personal email domains (e.g., gmail.com), so I can’t submit a request there. Why I’m asking here (NXP/Kinara integration confusion) NXP’s public material indicates Kinara’s SDK and model tools are being integrated into NXP’s ecosystem (including eIQ), and Ara-2 is now presented as an NXP product offering with related “Ara Software Development Kit” downloads. However, in practice, it’s not clear: where a developer is supposed to obtain a license key for compilation, and whether the “Ara SDK / eIQ integration” path is the supported route now. Questions Is a license key required to compile ONNX → .dvm using the Ara-2 SDK toolchain (r1.3 / ARA-SDK), even for personal/non-commercial use? If yes, what is the official process for an individual/hobbyist user to obtain evaluation/developer access (especially without a corporate email domain)? With an existing NXP account, where exactly should Ara-2 users obtain: the “official” Ara SDK binaries/toolchain (compiler), and/or the licensing mechanism needed for compilation? If compiling requires a license key that isn’t readily obtainable, are there any precompiled .dvm model packages (e.g., for Qwen 7B/Qwen2.5 7B) that NXP/Kinara/partners provide for Ara-2 users to run? If someone from NXP/Kinara can clarify the intended path (NXP portal vs legacy Kinara portal, and how licensing is handled now), that would help a lot. Re: Kinara ARA-SDK Licensing I have the same question! I got the device, driver. But no SDK and I guess no license either (if it is needed). The device is just sitting silently in my Lenovo ThinkCentre Ultra neo computer and not doing anything. Lenovo never finished its integration to Windows 11 as an NPU. I would like to use it at least to run some models on it or learning. It is now a completely unused piece of silicon in my PC. I guess it would help the adoption of the technology if more people would start using it. Re: Kinara ARA-SDK Licensing @kratafila mine was also basically unused silicon until I managed to get hold of a Linux SDK bundle via Geniatech. To be honest it is still unused silicon since I cannot get the models to compile and run. For what it’s worth, Geniatech (vendor of my Kinara Ara-2 M.2 module) shared these SDK/runtime downloads with me. They’re Linux-focused, and I’m not sure whether they’ll apply to the Ara-2 hardware inside your ThinkCentre (or help on Windows 11, there are included Windows binaries but I had more success with the Linux software), but they might still be useful if you can test under Linux / confirm your device works: 1) Drivers/runtime + sample .dvm models (Geniatech "customer ready" bundle): hxxps://mega[.]nz/file/nJcF0K5a#W-Ote-fp59hXoq4T0GGsaQmwGTRphWz0JATowyWjQpg 2) "Model compile" folder Geniatech initially sent me (note: this alone didn’t include the compiler binary): hxxps://mega[.]nz/file/KoclFQrJ#ifNOX7w2Y1qgLM6rnm7xPnUprwZZqhuRvelFG5p0MJQ 3) Full Ara-2 SDK tarball Geniatech later provided (this is the one that should include the actual toolchain/compiler, e.g. dvrun): hxxps://file[.]geniatech[.]com/down-eng/BSP/kinara_SDK_20251120[.]tar[.]bz2 If you do try any of the above and make progress (even just getting the SDK installed and seeing the device recognized), please post back here, not just for us, but because there seems to be broader confusion across multiple communities about the "official" working path and where the SDK/licensing is actually meant to come from as well as how to compile and run additional models.
記事全体を表示
[RTD600 IP] S32K3X4EVB-T172 GPIOウェイクアップ このサンプル プロジェクトでは、WKPU + SIUL2 (GPIO) の基本機能を使用および構成する方法をユーザーに示します。 ------------------------------------------------------------------------------ * テストハードウェア: S32K3X4EVB-T172 (SCH-53148 REV B2) * MCU: S32K344 * IDE: S32DS v3.5 および S32DS v3.6.x * SDKリリース: RTD 6.0.0 * デバッガ: PE Micro * ターゲット: internal_FLASH ------------------------------------------------------------------------------ このサンプル ルーチンは、GPIO 割り込みウェイクアップ用に WKPU ユニットを構成します。これは最も単純な WKPU の例です。ピン PTB19 (WKPU42) はウェイクアップ用に構成されています。 ルーチンはSW5が押されるのを待機し、緑色の LED をオフにして、次の処理を実行する Wkpu_EnterStandby() 関数に入ります。 コアクロックを FIRC に切り替えます。 WKPU インスタンスを初期化します。 WKPU42 (PTB19) を設定します。 スタンバイ(または高速スタンバイ)状態になります。 SW6を押すと、MCU が起動してリセットし、 SW5が再度押されるかどうかをポーリングします。 この例は現状のまま提供されており、保証やサポートはありません。
記事全体を表示
在线客服微【xins4698】万宝路公司现场负责人申请上下分直属游戏流程 在线客服微【xins4698】万宝路公司现场负责人申请上下分直属游戏流程 LPC Marketing LPC11xx LPC12xx lpc13xx lpc15xx LPC51Uxx LPC546xx LPC54xxx LPC55xx LPC800
記事全体を表示