Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
rw612 TFM zephyr upstream support Dear NXP When do you plan to merge TFM support to for the RW612 to upstream zephyr? Thanks! Product: WiFi RW6XX Re: rw612 TFM zephyr upstream support Hi @rlinus, hope you are doing well. Currently we cannot provide a defined timeline for making TF-M support for the RW612 available in upstream Zephyr. In the meantime, using the NXP downstream Zephyr distribution is required for RW612 TF-M development, as it provides the current NXP-specific integration and validation. Please monitor future Zephyr releases for updates regarding upstream availability. In the meantime, please continue using the NXP downstream Zephyr repository for this use case.
View full article
请求使用 HyperLynx 进行 LPPDR4 仿真的时序模型 (.v)。 您好, 我正在使用 MIMX8ML8CVNKZAB 进行一个项目,并尝试使用 HyperLynx 模拟 LPDDR4 接口。 Hyperlynx 请求内存控制器的时序模型文件(*.v)。请问能否提供MIMX8ML8CVNKZAB的时序模型? 顺祝商祺! 布迪卡 Re: Request for timing model (.v) for LPPDR4 simulation using HyperLynx. 你好, 我们不提供芯片专用的Verilog设计文件,我们只是遵循JEDEC规范,而Hyperlynx提供了许多标准的.v文件。适用于不同DDR类型的文件。使用默认定时就足够了,例如: 顺祝商祺!
View full article
IC COD Please help confirm the COD (wafer location) for  MC9S12XDP512MAG Re: IC COD Hello Weijun Ni Thanks for reaching out. Unfortunately, COD/COA information is not allowed to be shared in community. Please kindly submit a ticket https://support.nxp.com/s/?language=en_US , we will help there Thanks for understanding Becky
View full article
[BUG] 模块名称冲突:wave511 下游驱动程序和 wave5 上游驱动程序冲突 你好, lf-6.18.20-2.0.0 内核 (6.18.y) 中的 NXP Wave511 VPU 驱动程序构建了一个与主线 Chips&Media Wave5 驱动程序同名的模块。任何同时启用这两个功能的配置,例如allmodconfig或allyesconfig ,都会导致版本失败。 细节: - 上游驱动程序(自 v6.8 起已合并到主线): drivers/media/platform/chips-media/wave5/    obj-$(CONFIG_VIDEO_WAVE_VPU) += wave5.o - NXP驱动程序: drivers/mxc/vpu/wave511/    obj-$(CONFIG_MXC_VIDEO_WAVE511) += wave5.o    obj-$(CONFIG_MXC_VIDEO_WAVE511_CTRL) += wave5-ctrl.o 这两个 Kconfig 符号是独立的,因此可以同时启用这两个模块。Kbuild 随后停止运行: error: the following would cause module name conflict: drivers/media/platform/chips-media/wave5/wave5.ko drivers/mxc/vpu/wave511/wave5.ko 即使没有触发检查, modules_install也会用一个 wave5.ko 文件覆盖另一个wave5.ko文件。 驱动程序绑定了不同的兼容模块( ti,j721s2-wave521c和nxp,wave511-vpu ),因此只有模块名称冲突。 重现步骤: make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- allmodconfig make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j$(nproc) modules 这个问题能否在即将发布的 Linux IMX 版本中得到解决? 感谢您提前给予的支持。 马修斯·巴博萨 Toradex i.MX 8 系列 | i.MX 8QuadMax (8QM) | 8QuadPlus i.MX 8M | i.MX 8M Mini | i.MX 8M Nano i.MX6 全部 Linux Re: [BUG] Module name conflict: wave511 downstream driver and upstream wave5 你好, 我正在 Toradex 电路板支持包。中添加 Wave511 驱动程序以支持 i.MX952,尽管所使用的处理器与下游内核中报告的错误无关。 我们为所有受电路板支持包。支持的 ARM64 SoC 构建了一个共享配置的内核,它是一个超集,可以启用许多模块。其中包括 CONFIG_VIDEO_WAVE_VPU。 这是主线内核中存在的驱动程序,它会安装“wave5.ko”。到模块目录。 我找到了一个变通方法。 由于无法在该通用配置中启用 WAVE511 驱动程序,因此我只对 i.MX SoC 执行了此操作,并禁用了它们的 CONFIG_VIDEO_WAVE_VPU。 我已经禁用了 OE 层中 i.MX 处理器的 CONFIG_VIDEO_WAVE_VPU,以便暂时启用 CONFIG_MXC_VIDEO_WAVE511 模块。 预期allmodconfig能够顺利构建,但当前的下游驱动程序破坏了这一点。这就是我举报它的原因。 Re: [BUG] Module name conflict: wave511 downstream driver and upstream wave5 你好, 此前未曾报告过此问题,目前也暂无解决方案计划。 你使用的是哪款处理器? 你试过禁用某个 Kconfig 选项或者在本地重命名模块吗? 顺祝商祺! Re: [BUG] Module name conflict: wave511 downstream driver and upstream wave5 你好, 谢谢你提供的详细信息,我已经将此事汇报给了内部团队。 我会尽快向您汇报我们这边的后续行动。 顺祝商祺! Re: [BUG] Module name conflict: wave511 downstream driver and upstream wave5 你好, 请查看内部团队的最新消息: 我在 lf-6.18.20-2.0.0 (nxp-imx/linux-imx) 的全新检出版本上重现了此问题,并确认根本原因与工单中的描述完全一致: 上游驱动程序/媒体/平台/芯片媒体/wave5/Makefile:obj-$(CONFIG_VIDEO_WAVE_VPU) += wave5.o NXP drivers/mxc/vpu/wave511/Makefile: obj-$(CONFIG_MXC_VIDEO_WAVE511) += wave5.o 这两个 Kconfig 符号是独立的,因此 allmodconfig/allyesconfig 会同时选择它们,导致 scripts/modules-check.sh 因报告的错误而中止。我通过向脚本提供包含两个真实模块路径的 modules.order 来重现完全相同的错误文本——与工单中引用的内容字节完全相同。还检查了较新的 lf-6.18.37-2.1.0 版本。标签:碰撞仍然存在。 建议的解决方法:将 drivers/mxc/vpu/wave511/Makefile 中 NXP 模块的构建目标从 wave5.o/wave5-ctrl.o 重命名为 wave511.o/wave511-ctrl.o。源文件名保持不变——这只是一个 Makefile 文件的更改,对驱动程序的功能/行为没有任何影响。我已验证它可以顺利构建,并且此更改生效后,scripts/modules-check.sh 不再标记冲突。 我考虑过另一种方案,即在 NXP Kconfig 中添加对 !VIDEO_WAVE_VPU 的依赖,但模块重命名是更持久的长期解决方案:它解决了实际的命名冲突,而不是依赖互斥(互斥会在 allmodconfig/allyesconfig 下悄悄删除一个驱动程序,并可能掩盖真正的版本问题),而且即使未来的板合并了这两个 IP 模块,它仍然是正确的。 仅下游影响:任何对 NXP Wave511 驱动程序硬编码 modprobe wave5 / wave5.ko 的内容(例如 yocto 配方或 rootfs 模块加载配置)都需要改用引用 wave511.ko。我在内核树中没有找到任何此类引用。 补丁将内部提供审核。 顺祝商祺!
View full article
ST25R500 Library Integration with NXP MWCT2016S Hi, I am currently working on a wireless charger project using the NXP MWCT2016S MCU integrated with the ST25R500 NFC reader. I would like to understand how to integrate the ST25R500 library package into the NXP non-AUTOSAR platform. Could you please guide me through the integration process and share any relevant documentation, application notes, or example projects? Your support would be greatly appreciated. Thank you for your assistance. Regards, rakY Re: ST25R500 Library Integration with NXP MWCT2016S Hi @rakYps21  The following links describe how to add and integrate custom libraries into S32DS/Eclipse. They may be useful for your intended application. HOWTO: Add a static library file into S32DS GCC project Creating and using Libraries with ARM gcc and Eclipse | MCU on Eclipse How to use Custom Library Names with GNU Linker and Eclipse | MCU on Eclipse Regarding the integration of the ST25R500 library, this falls outside the scope of our support, as it is a third-party software component and is not developed or maintained by NXP. Therefore, we are unable to provide guidance on the functionality, implementation, or debugging of that library. However, we can assist with topics related to the MWCT2016S, including its configuration, software package, drivers, and supported functionalities. BR, VaneB Re: ST25R500 Library Integration with NXP MWCT2016S Hi VaneB, Thank you for sharing the inputs. I have completed the initial configuration and integrated the ST files into our NXP software package. However, I need guidance on configuring and implementing the GPIO interrupt for the ST25R500 IRQ signal. I have completed some of the initial configurations for PTA18 (EIRQ0), as shown in the attached screenshots. However, I need further guidance on the required configurations and application-level implementation to ensure the interrupt is triggered and handled correctly. Could you please review my current configuration and guide me through the necessary steps to enable and handle the GPIO interrupt properly? Your support would be greatly appreciated. BR, Raky Re: ST25R500 Library Integration with NXP MWCT2016S Hi @rakYps21  Your configuration looks good. For the SIUL2 external interrupt, I recommend checking the thread SIUL2 external interrupt example project using S32K3 RTD without AUTOSAR. It goes into more detail about how to handle this. The example uses an older RTD version, but the general idea and configuration approach are still the same. Also, the RTD package includes Siul2_Icu_Ip_BlinkLed_S32K3xx examples for the different S32K3 variants. These examples configure a GPIO as an external interrupt, so they can be very useful as a reference. These two resources should give you a good starting point to better understand how the external interrupt works and how to configure it.
View full article
EB tresos Studio 32.1.4 Where could I download EB tresos Studio 32.1.4?  S32K3 Standard Software -> Automotive SW - EB tresos Studio / AUTOSAR Configuration Tool , on the path can only find EB tresos Studio 30.0.0 the highest. Re: EB tresos Studio 32.1.4 Hello Peter, I have followed your advice and checked how to apply for secure access, but the process is quite complicated. I don't intend to access highly classified documents; I only wish to download EB Tresos Studio 32.x.x. Is there a way to add EB Tresos Studio 32.x.x to my Product List? Thanks! Re: EB tresos Studio 32.1.4 Hello, Looking at the available versions: So the issue is most probably tied to your NXP SW account. Please follow the FAQ to gain further access: https://www.nxp.com/support/support/secure-access-rights:SEC-ACCESS Best regards, Peter Re: EB tresos Studio 32.1.4 Hello, My account email: [email protected] Thanks! Re: EB tresos Studio 32.1.4 Hello, Yes, there is a direct way if admin add it to your account. Please share with me account email you are using for it. Best regards, Peter Re: EB tresos Studio 32.1.4 Hello, It should be available at your SW account now. Best regards, Peter
View full article
HyperLynxを用いたLPPDR4シミュレーション用のタイミングモデル(.v)の要請。 こんにちは、 プロジェクトでMIMX8ML8CVNKZABを使っていて、HyperLynxを使ってLPDDR4インターフェースをシミュレートしようとしています。 Hyperlynxはメモリコントローラ用のタイミングモデルファイル(*.v)を要求します。MIMX8ML8CVNKZABのタイミングモデルを教えていただけますか? よろしくお願いいたします。 ブッディカ Re: Request for timing model (.v) for LPPDR4 simulation using HyperLynx. こんにちは、 私たちのチップには特別なVerilog Design Fileは提供していません。JEDEC仕様に従っています。Hyperlynxは多くの標準.vを提供しています異なるDDRタイプ用のファイル。デフォルトのタイミングを使用すれば十分です。例えば、次のようになります。 よろしくお願いいたします。
View full article
EB tresos Studio 32.1.4 哪里可以下载 EB tresos Studio 32.1.4?  S32K3 标准软件-> 汽车软件 - EB tresos Studio / AUTOSAR 配置工具,在该路径下只能找到 EB tresos Studio 30.0.0 最高版本。 Re: EB tresos Studio 32.1.4 你好,彼得, 我按照您的建议查看了如何申请安全访问权限,但这个过程相当复杂。 我无意访问高度机密的文件;我只想下载 EB Tresos Studio 32.x.x。有什么方法可以将 EB Tresos Studio 32.xx 添加到我的产品列表中吗? 谢谢! Re: EB tresos Studio 32.1.4 你好, 查看可用版本: 所以问题很可能与您的NXP软件帐户有关。 请参考常见问题解答以获取更多信息: https://www.nxp.com/support/support/secure-access-rights:SEC-ACCESS 顺祝商祺! Peter Re: EB tresos Studio 32.1.4 你好, 我的账户邮箱:[email protected] 谢谢! Re: EB tresos Studio 32.1.4 你好, 是的,如果管理员将其添加到您的帐户中,则有直接的方法。 请告诉我您用于此账户的邮箱地址。 顺祝商祺! Peter Re: EB tresos Studio 32.1.4 你好, 现在应该可以在您的SW账户中看到了。 顺祝商祺! Peter
View full article
ST25R500 库与 NXP MWCT2016S 的集成 您好, 我目前正在开发一个无线充电器项目,该项目使用NXP MWCT2016S MCU和ST25R500 NFC 读卡器。 我想了解如何将ST25R500库包集成到 NXP 非 AUTOSAR 平台中。 能否请您指导我完成集成过程,并分享任何相关的文档、应用笔记或示例项目? 非常感谢您的支持。 谢谢你的帮助。 此致, rakY Re: ST25R500 Library Integration with NXP MWCT2016S 你好@rakYps21 以下链接介绍了如何将自定义库添加到 S32DS/Eclipse 中并进行集成。它们可能对您的预期用途有所帮助。 操作指南:在 S32DS GCC 项目中添加静态库文件 使用 ARM gcc 和 Eclipse 创建和使用库 | Eclipse 上的 MCU 如何在 GNU 链接器和 Eclipse 中使用自定义库名称 | MCU on Eclipse 关于 ST25R500 库的集成,这超出了我们的支持范围,因为它是一个第三方软件组件,并非由 NXP 开发或维护。因此,我们无法提供有关该库的功能、实现或调试方面的指导。 但是,我们可以协助您解决与 MWCT2016S 相关的各种问题,包括其配置、软件包、驱动程序和支持的功能。 BR,VaneB Re: ST25R500 Library Integration with NXP MWCT2016S 嗨 VaneB, 感谢您分享您的想法。 我已经完成了初始配置,并将ST文件集成到我们的NXP软件包中。 但是,我需要有关配置和实现 ST25R500 IRQ 信号的 GPIO 中断的指导。 我已经完成了PTA18 (EIRQ0) 的一些初始配置,如附件截图所示。 但是,我需要进一步的指导,了解所需的配置和应用程序级别的实现,以确保中断能够被正确触发信号和处理。 请您查看一下我当前的配置,并指导我完成启用和正确处理 GPIO 中断的必要步骤? 非常感谢您的支持。 BR, 拉基 Re: ST25R500 Library Integration with NXP MWCT2016S 你好@rakYps21 您的配置看起来没问题。 对于 SIUL2 外部中断,我建议查看使用 S32K3 RTD 而不使用 AUTOSAR 的 SIUL2 外部中断示例项目线程。它会更详细地介绍如何处理这种情况。该示例使用的是较旧的 RTD 版本,但总体思路和配置方法仍然相同。 此外,RTD 软件包还包含针对不同 S32K3 变体的Siul2_Icu_Ip_BlinkLed_S32K3xx示例。这些示例将 GPIO 配置为外部中断,因此它们可以作为非常有用的参考。 这两个资源应该能帮助你更好地理解外部中断的工作原理以及如何配置它。
View full article
KW45 automotive bluetooth - drop in module? KiCad? Dear community,  as lesser experienced in the bluetooth radio domain I am looking for your help.  Our projekt needs  bluetooth  connectivity. The KW45 evaluation board has been used for POCs and early tests. Now e want the KW45 right on our board. Using KiCad we are not able to access the NXP reference design. And reading through the documentation lets me humble shrink the size of an ant. Or smaller. Seeing the many Forum posts I wonder if someone could share a ready made design that we could use?  We have a stable 3.3V supply and communicate with UART.  Its an Automotive retrofit application and should be as small as it could be. And thats already everthing we need.  Best regards Michael  KW45  Re: KW45 automotive bluetooth - drop in module? KiCad? Hello @Orbiter, Please note that the KW45 may have less features compared to newer devices. You may also want to consider the KW47 family, which offers several enhancements, including larger memory capacity, a dedicated CM33 radio core running at up to 64 MHz, has a 2.4 GHz Bluetooth Low Energy Core Version 6.x and supports Bluetooth channel sounding. In addition, the KW47 is pin-compatible with the KW45, which can simplify migration efforts. Please refer to AN14796 for more information on the feature differences and migration considerations. We only provide the KW45-EVK design files, along with this community post, which outline the best way to build a PCB first time right with KW45. BR Habib Re: KW45 automotive bluetooth - drop in module? KiCad? I understand its too hard for us. We will move towards a bluetooth modul SOC that basically "bolts on" instead.   Re: KW45 automotive bluetooth - drop in module? KiCad? Hello@Orbiter, If you are interested, you can contact one of our partners, who could help you develop a solution for an automotive environment. Additionally, you can consult the Wi-Fi® + Bluetooth® + 802.15.4 Partner Modules offered by our partners, some of which could also be an option for an automotive environment. However, these modules require a host processor. If this is an option you would like to explore, feel free to provide more information about your application so I can guide you on the available options. BR Habib
View full article
[BUG] Module name conflict: wave511 downstream driver and upstream wave5 Hello, The NXP Wave511 VPU driver in the lf-6.18.20-2.0.0 kernel (6.18.y) builds a module with the same name as the mainline Chips&Media Wave5 driver. Any config that enables both, such as allmodconfig or allyesconfig, fails the build. Details: - Upstream driver (in mainline since v6.8): drivers/media/platform/chips-media/wave5/    obj-$(CONFIG_VIDEO_WAVE_VPU) += wave5.o - NXP driver: drivers/mxc/vpu/wave511/    obj-$(CONFIG_MXC_VIDEO_WAVE511) += wave5.o    obj-$(CONFIG_MXC_VIDEO_WAVE511_CTRL) += wave5-ctrl.o The two Kconfig symbols are independent, so both modules can be enabled together. Kbuild then stops with: error: the following would cause module name conflict: drivers/media/platform/chips-media/wave5/wave5.ko drivers/mxc/vpu/wave511/wave5.ko Even where the check isn't hit, modules_install would overwrite one wave5.ko with the other. The drivers bind different compatibles (ti,j721s2-wave521c and nxp,wave511-vpu), so only the module name collides. Steps to reproduce: make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- allmodconfig make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j$(nproc) modules Could that be fixed in an upcoming Linux IMX release? Thank you in advance for your support, Matheus Barbosa Toradex i.MX 8 Family | i.MX 8QuadMax (8QM) | 8QuadPlus i.MX 8M | i.MX 8M Mini | i.MX 8M Nano i.MX6 All Linux Re: [BUG] Module name conflict: wave511 downstream driver and upstream wave5 Hello, I'm adding the Wave511 driver to support i.MX952 at Toradex BSP, although the processor in use is not relevant for the bug reported in the downstream kernel. We build the kernel with a shared config for all ARM64 SoCs that are supported by our BSP, its a super set that enables many modules. That includes CONFIG_VIDEO_WAVE_VPU. This is the kernel driver present at mainline that installs "wave5.ko" to modules directory. I've created a workaround  Since it is not possible to enable WAVE511 driver in that common config, I've done that just for i.MX SoCs and disabled CONFIG_VIDEO_WAVE_VPU for them as well. I've disabled CONFIG_VIDEO_WAVE_VPU at our OE layer for the i.MX processors to allow enabling CONFIG_MXC_VIDEO_WAVE511 as a module for now. It is expected that allmodconfig build cleanly, and the current downstream driver breaks this. That is the reason I'm reporting it. Re: [BUG] Module name conflict: wave511 downstream driver and upstream wave5 Hello, This issue have not been reported before and there are no plans to implement a solution yet. Which processor are you using? Did you try to disabling one Kconfig option or locally renaming the module? Best regards. Re: [BUG] Module name conflict: wave511 downstream driver and upstream wave5 Hello, Thank you for the details, I reported this with internal team. I will update you further actions in our side as soon as possible. Best regards. Re: [BUG] Module name conflict: wave511 downstream driver and upstream wave5 Hello, Please check the update from internal team: I reproduced this on a clean checkout of lf-6.18.20-2.0.0 (nxp-imx/linux-imx) and confirmed the root cause matches the ticket exactly: Upstream drivers/media/platform/chips-media/wave5/Makefile: obj-$(CONFIG_VIDEO_WAVE_VPU) += wave5.o NXP drivers/mxc/vpu/wave511/Makefile: obj-$(CONFIG_MXC_VIDEO_WAVE511) += wave5.o Both Kconfig symbols are independent, so allmodconfig/allyesconfig selects both and scripts/modules-check.sh aborts with the reported error. I reproduced the exact error text by feeding the script a modules.order containing the two real module paths – byte-identical to what's quoted in the ticket. Also checked the newer lf-6.18.37-2.1.0 tag: the collision is still present there. Recommended fix: rename the NXP module's build target in drivers/mxc/vpu/wave511/Makefile from wave5.o/wave5-ctrl.o to wave511.o/wave511-ctrl.o. Source filenames are untouched – this is a one-file Makefile change with no functional/behavioral impact on the driver. I verified it builds cleanly and that scripts/modules-check.sh no longer flags a conflict with this change in place. I considered the alternative of adding depends on !VIDEO_WAVE_VPU to the NXP Kconfig instead, but a module rename is the more durable fix long-term: it resolves the actual naming collision rather than relying on mutual exclusion (which would silently drop one driver under allmodconfig/allyesconfig and could mask real build issues), and it stays correct even if a future board combines both IP blocks. Only downstream impact: anything that hardcodes modprobe wave5 / wave5.ko for the NXP Wave511 driver (e.g. a yocto recipe or rootfs module-load config) would need to reference wave511.ko instead. I did not find any such reference inside this kernel tree. Patch will be provided internally for review. Best regards.
View full article
rw612 TFM zephyr 上游支持 尊敬的恩智浦半导体 你们计划何时将 RW612 的 TFM 支持合并到上游 Zephyr 版本中? 谢谢您! 产品:WiFi RW6XX Re: rw612 TFM zephyr upstream support 嗨@rlinus ,希望你一切都好。 目前我们无法提供明确的时间表,以便在上游 Zephyr 中提供对 RW612 的 TF-M 支持。与此同时,RW612 TF-M 的开发需要使用 NXP 下游 Zephyr 发行版,因为它提供了当前 NXP 特有的集成和验证。 请监测未来的Zephyr 版本,以获取有关上游可用性的更新信息。在此期间,请继续使用 NXP 下游 Zephyr 存储库来实现此用例。
View full article
KW45のオートモーティブBluetooth - ドロップインモジュール?KiCad? 親愛なるコミュニティの皆様へ Bluetooth無線分野に関しては経験が浅いため、皆様のご協力をお願いいたします。 私たちのプロジェクトにはBluetoothコネクティビティが必要です。KW45評価ボードはPOCや初期試験に使用されてきました。 今、私たちはKW45を私たちのボードに搭載したいのです。KiCadを使うとNXPのリファレンスデザインにアクセスできません。そしてドキュメントを読むことで、アリの大きさを謙虚に縮めることができます。あるいはもっと小さいサイズ。 フォーラムの投稿が多いのを見て、誰か使える既製のデザインを教えてもらえませんか?安定した3.3V電源を供給し、UARTで通信します。 これはオートモーティブの改修用車なので、できるだけ小さくするべきです。 そして、それだけで私たちに必要なものはすべて揃っている。 よろしくお願いいたします。 マイケル KW45 Re: KW45 automotive bluetooth - drop in module? KiCad? こんにちは、 @Orbiter さん、 KW45は、より新しい機種に比べて機能が少ない場合があることをご了承ください。また、 KW47ファミリ、 も検討すると良いでしょう。これは、より大きなメモリ容量、最大64MHzで動作する専用CM33無線コア、2.4GHzのBluetooth Low Energy Core Version 6.x、Bluetoothチャネルサウンディングのサポートなど、いくつかの強化機能を備えています。さらに、KW47はKW45とピン互換性があり、移行作業を簡素化できます。機能の違いや移行に関する考慮事項の詳細については、 AN14796を参照してください。 私たちは KW45-EVKデザインファイルと、この コミュニティ投稿のみを提供しており、KW45で初めてPCBを作る最良の方法をまとめています。 BR ハビブ Re: KW45 automotive bluetooth - drop in module? KiCad? 私たちには難しすぎることは理解しています。代わりに、基本的に「後付け」できるBluetoothモジュールSoCへと移行していく予定です。 Re: KW45 automotive bluetooth - drop in module? KiCad? こんにちは、 @Orbiter さん、 ご興味があれば、当社の パートナーのいずれかにご連絡ください。オートモーティブ環境向けのソリューション開発をお手伝いいたします。 さらに、パートナーが提供する Wi-Fi® + Bluetooth® + 802.15.4パートナーモジュール もご参照いただけます。これらのモジュールの一部はオートモーティブ環境向けのオプションにも対応可能です。しかし、これらのモジュールはホストプロセッサを必要とします。もしこの選択肢を検討したい場合は、アプリケーションについての詳細をお知らせいただければ、SO私がCAN利用可能な選択肢についてご案内いたします。 BR ハビブ
View full article
S32DS_Power_Win32_v2.1 install fail. rollbacked Always install fail and be rollbacked even by administrator. Followed is log informations: __________________________________________________________________________ Mon Oct 19 05:14:43 CST 2026 Free Memory: 25439 kB Total Memory: 40852 kB java.class.path: C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\InstallerData\IAClasses.zip C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\InstallerData\Execute.zip C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\InstallerData\Execute.zip C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\InstallerData\Resource1.zip C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\InstallerData\Resource1.zip C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\InstallerData C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\InstallerData ZGUtil.CLASS_PATH: C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\InstallerData\IAClasses.zip C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\InstallerData\Execute.zip C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\InstallerData sun.boot.class.path: C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\resources.jar C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\rt.jar C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\sunrsasign.jar C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\jsse.jar C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\jce.jar C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\charsets.jar C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\jfr.jar C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\classes java.ext.dirs: C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\ext C:\WINDOWS\Sun\Java\lib\ext java.version == 1.8.0_202 (Java 1) java.vm.name == Java HotSpot(TM) Client VM java.vm.vendor == Oracle Corporation java.vm.version == 25.202-b08 java.vm.specification.name == Java Virtual Machine Specification java.vm.specification.vendor == Oracle Corporation java.vm.specification.version == 1.8 java.specification.name == Java Platform API Specification java.specification.vendor == Oracle Corporation java.specification.version == 1.8 java.vendor == Oracle Corporation java.vendor.url == http://java.oracle.com/ java.class.version == 52.0 java.library.path == C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\Program Files\OpenSSL-Win64\bin;C:\StellarStudio-7.0\SDKS\TOOLS-1.4.0\HostTools\CoreUtils\bin;C:\HIGHTEC\toolchains\arm\v8.1.0\bin;C:\Program Files\Microsoft\jdk-11.0.12.7-hotspot\bin\server;C:\HighTec\toolchains\tricore\v4.6.3.0\bin;C:\Perl64\site\bin;C:\Perl64\bin;C:\HighTec\toolchains\tricore\v4.9.3.0\bin;C:\HighTec\licensemanager;C:\HighTec\toolchains\tricore\v4.6.6.1\bin;C:\HighTec/licensemanager;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\TortoiseSVN\bin;C:\Program Files\MATLAB\R2021a\runtime\win64;C:\Program Files\MATLAB\R2021a\bin;C:\Program Files (x86)\Microchip\xc16\v1.34\bin;C:\Program Files\dotnet\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.21.27702\bin\Hostx64\x86;C:\40_HexView;E:\openssl-1.1.1b\win32-release\bin;C:\Program Files\Microchip\xc16\v1.50\bin;C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\;C:\Program Files\Microsoft SQL Server\150\Tools\Binn\;C:\Program Files (x86)\IVI Foundation\VISA\WinNT\Bin\;C:\Program Files\IVI Foundation\VISA\Win64\Bin\;C:\Program Files (x86)\IVI Foundation\VISA\WinNT\Bin;C:\make;C:\Program Files\Vector SIL Kit 4.0.52\x86\bin;C:\Program Files\Vector SIL Kit 4.0.52\x86_64\bin;C:\Program Files (x86)\Vector CANdb++ 3.1\Exec32;C:\Program Files\Git\cmd;C:\Program Files\Git;C:\Program Files (x86)\Vector ICD Manager 2.1\\Exec32;C:\HIGHTEC\licensemanager;C:\Program Files\Polyspace\R2021b\polyspace\bin;C:\Users\Jie.SH.Wu\AppData\Local\Programs\Python\Python314\Scripts\;C:\Users\Jie.SH.Wu\AppData\Local\Programs\Python\Python314\;C:\Users\Jie.SH.Wu\AppData\Local\Microsoft\WindowsApps;D:\Program Files\Microsoft VS Code\bin;C:\Users\Jie.SH.Wu\.dotnet\tools;C:\Users\Jie.SH.Wu\AppData\Local\Programs\CodeBuddy CN\bin;. java.compiler == null java.home == C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre java.io.tmpdir == C:\Users\JIESH~1.WU\AppData\Local\Temp\ os.name == Windows 10 os.arch == x86 os.version == 10.0 path.separator == ; file.separator == \ file.encoding == GBK user.name == Jie.SH.Wu user.home == C:\Users\Jie.SH.Wu user.dir == C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows user.language == en user.region == null __________________________________________________________________________ Installed Feature(s) S32DSF of S32 Design Studio for Power Architecture Version 2.1 Install Begin: OCTOBER 19, 2026 5:02:33 PM CST Install End: OCTOBER 19, 2026 5:04:17 PM CST Installed by InstallAnywhere 18.0 Professional Build 5608 User Interactions ----------------- #Choose additional feature(s) #---------------------------- CHOSEN_FEATURE_LIST=S32DSF CHOSEN_INSTALL_FEATURE_LIST=S32DSF CHOSEN_INSTALL_SET=S32 Des #Choose Install Location #----------------------- USER_INSTALL_DIR=C:\\NXP\\S32DS_Power_v2.1 #Choose Shortcut Folder #---------------------- USER_SHORTCUTS=C:\\Users\\Jie.SH.Wu\\AppData\\Roaming\\Microsoft\\Windows\\Start Menu\\Programs\\NXP S32 Design Studio\\S32 Design Studio for Power Architecture Version 2.1 #Install #------- -fileOverwrite_C\:\\NXP\\S32DS_Power_v2.1\\_S32\ Design\ Studio\ for\ Power\ Architecture\ Version\ 2.1_installation\\resource\\iawin32.dll=Yes -fileOverwrite_C\:\\NXP\\S32DS_Power_v2.1\\_S32\ Design\ Studio\ for\ Power\ Architecture\ Version\ 2.1_installation\\resource\\win64_32_x64.exe=Yes -fileOverwrite_C\:\\NXP\\S32DS_Power_v2.1\\_S32\ Design\ Studio\ for\ Power\ Architecture\ Version\ 2.1_installation\\resource\\remove.exe=Yes -fileOverwrite_C\:\\NXP\\S32DS_Power_v2.1\\_S32\ Design\ Studio\ for\ Power\ Architecture\ Version\ 2.1_installation\\resource\\invoker.exe=Yes Summary ------- Installation: Unsuccessful. 48 Successes 24 Warnings 1 NonFatalErrors 1 FatalErrors Action Notes: None Install Log Detail: Check Disk Space: C:\NXP\S32DS__v2.1 Status: SUCCESSFUL Additional Notes: NOTE - Required Disk Space:7,110,809,247 Bytes Free Disk Space:52,016,885,760 Bytes Check Disk Space: C:\NXP\S32DS_Power_v2.1 Status: SUCCESSFUL Additional Notes: NOTE - Required Disk Space:7,110,809,247 Bytes Free Disk Space:52,016,885,760 Bytes Install Directory: C:\NXP\S32DS_Power_v2.1\jre Status: SUCCESSFUL Install JRE: C:\NXP\S32DS_Power_v2.1\jre Status: SUCCESSFUL Install Directory: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\ Status: SUCCESSFUL Additional Notes: NOTE - Directory already existed Execute Command: NET SESSION Status: SUCCESSFUL Install File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\vcredist_2013_x86.exe Status: SUCCESSFUL Expand Archive: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\vcredist.zip Status: SUCCESSFUL Install File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\vcredist_2010SP1_x86.exe Status: SUCCESSFUL Expand Archive: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\vcredist2010.zip Status: SUCCESSFUL Execute Command: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\vcredist_2013_x86.exe /quiet Status: SUCCESSFUL Execute Command: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\vcredist_2010SP1_x86.exe /quiet Status: SUCCESSFUL Install File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\clljni.dll Status: SUCCESSFUL Install File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\cllSvrUtility.exe Status: SUCCESSFUL Install File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\cllSvrUtility.exe.manifest Status: SUCCESSFUL Install File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\cll_app.dll Status: SUCCESSFUL Install File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\cll_app_libFNP.dll Status: SUCCESSFUL Install File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\cll_svr.dll Status: SUCCESSFUL Install File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\cll_svr_libFNP.dll Status: SUCCESSFUL Install File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\FnpCommsSoap.dll Status: SUCCESSFUL Install File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\FNP_Act_Installer.dll Status: SUCCESSFUL Install File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\x64\FnpCommsSoap.so Status: SUCCESSFUL Install File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\x64\libclljni.so Status: SUCCESSFUL Install File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\x64\libcll_app.so Status: SUCCESSFUL Install File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\x64\libcll_app_libFNP.so Status: SUCCESSFUL Install File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\x64\libcll_svr.so Status: SUCCESSFUL Install File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\x64\libcll_svr_libFNP.so Status: SUCCESSFUL Install File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\FNPLicensingService\FNPLicensingService Status: SUCCESSFUL Install File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\install_fnp.sh Status: SUCCESSFUL Install File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\license.jar Status: SUCCESSFUL Expand Archive: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\Activation.zip Status: SUCCESSFUL Execute Command: java "-Djava.library.path=C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86" -jar "C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\license.jar" install -prod S32DS-PA_v2.1 Status: SUCCESSFUL Execute Command: java "-Djava.library.path=C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86" -jar "C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\license.jar" verify -feature Activated -version 2.1 -prod S32DS-PA_v2.1 Status: SUCCESSFUL Execute Command: java "-Djava.library.path=C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86" -jar "C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\license.jar" run -feature Activated -version 2.1 -prod S32DS-PA_v2.1 Status: SUCCESSFUL Execute Command: java "-Djava.library.path=C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86" -jar "C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\license.jar" list Status: SUCCESSFUL Install Uninstaller: S32 Design Studio for Power Architecture Version 2.1(Install All Uninstaller Components) Status: SUCCESSFUL Install Directory: C:\NXP\S32DS_Power_v2.1\_S32 Design Studio for Power Architecture Version 2.1_installation\resource\ Status: SUCCESSFUL Install File: C:\NXP\S32DS_Power_v2.1\_S32 Design Studio for Power Architecture Version 2.1_installation\resource\iawin32.dll Status: SUCCESSFUL Install File: C:\NXP\S32DS_Power_v2.1\_S32 Design Studio for Power Architecture Version 2.1_installation\resource\win64_32_x64.exe Status: SUCCESSFUL Install File: C:\NXP\S32DS_Power_v2.1\_S32 Design Studio for Power Architecture Version 2.1_installation\resource\remove.exe Status: SUCCESSFUL Install File: C:\NXP\S32DS_Power_v2.1\_S32 Design Studio for Power Architecture Version 2.1_installation\resource\invoker.exe Status: SUCCESSFUL Install Uninstaller: S32 Design Studio for Power Architecture Version 2.1(Install All Uninstaller Components) Status: ERROR Additional Notes: ERROR - Error writing LaunchAnywhere components (Access Denied) Uninstall File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\vcredist_2013_x86.exe Status: WARNING Additional Notes: WARNING - The file does not exist Uninstall File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\vcredist_2010SP1_x86.exe Status: WARNING Additional Notes: WARNING - The file does not exist Uninstall File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\clljni.dll Status: WARNING Additional Notes: WARNING - The file does not exist Uninstall File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\cllSvrUtility.exe Status: WARNING Additional Notes: WARNING - The file does not exist Uninstall File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\cllSvrUtility.exe.manifest Status: WARNING Additional Notes: WARNING - The file does not exist Uninstall File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\cll_app.dll Status: WARNING Additional Notes: WARNING - The file does not exist Uninstall File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\cll_app_libFNP.dll Status: WARNING Additional Notes: WARNING - The file does not exist Uninstall File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\cll_svr.dll Status: WARNING Additional Notes: WARNING - The file does not exist Uninstall File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\cll_svr_libFNP.dll Status: WARNING Additional Notes: WARNING - The file does not exist Uninstall File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\FnpCommsSoap.dll Status: WARNING Additional Notes: WARNING - The file does not exist Uninstall File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\FNP_Act_Installer.dll Status: WARNING Additional Notes: WARNING - The file does not exist Uninstall File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\x64\FnpCommsSoap.so Status: WARNING Additional Notes: WARNING - The file does not exist Uninstall File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\x64\libclljni.so Status: WARNING Additional Notes: WARNING - The file does not exist Uninstall File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\x64\libcll_app.so Status: WARNING Additional Notes: WARNING - The file does not exist Uninstall File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\x64\libcll_app_libFNP.so Status: WARNING Additional Notes: WARNING - The file does not exist Uninstall File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\x64\libcll_svr.so Status: WARNING Additional Notes: WARNING - The file does not exist Uninstall File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\x64\libcll_svr_libFNP.so Status: WARNING Additional Notes: WARNING - The file does not exist Uninstall File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\FNPLicensingService\FNPLicensingService Status: WARNING Additional Notes: WARNING - The file does not exist Uninstall File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\install_fnp.sh Status: WARNING Additional Notes: WARNING - The file does not exist Uninstall File: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\license.jar Status: WARNING Additional Notes: WARNING - The file does not exist Uninstall Folder: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\FNPLicensingService Status: WARNING Additional Notes: WARNING - The path does not exist Uninstall Folder: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\x64 Status: WARNING Additional Notes: WARNING - The path does not exist Uninstall Folder: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86 Status: WARNING Additional Notes: WARNING - The path does not exist Uninstall Folder: C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll Status: WARNING Additional Notes: WARNING - The path does not exist Uninstall Folder: C:\NXP\S32DS_Power_v2.1\jre Status: SUCCESSFUL Remove Registry Entry: 5 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\null Status: SUCCESSFUL Error occurred while installing the following Action, hence rolling back the installation....! Action Name: Trigger Rollback Action Action Description: Trigger Rollback Action Error Details as below: This action rolls back the Installation. ====================STDERR ENTRIES================== __________________________________________________________________________ InstallAnywhere 2017 Version: 18.0 __________________________________________________________________________ Mon Oct 19 05:02:26 CST 2026 Free Memory: 12695 kB Total Memory: 15872 kB No Arguments java.class.path: C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\InstallerData\IAClasses.zip C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\InstallerData\Execute.zip C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\InstallerData\Execute.zip C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\InstallerData\Resource1.zip C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\InstallerData\Resource1.zip C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\InstallerData C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\InstallerData ZGUtil.CLASS_PATH: C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\InstallerData\IAClasses.zip C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\InstallerData\Execute.zip C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\InstallerData sun.boot.class.path: C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\resources.jar C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\rt.jar C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\sunrsasign.jar C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\jsse.jar C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\jce.jar C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\charsets.jar C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\jfr.jar C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\classes java.ext.dirs: C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\ext C:\WINDOWS\Sun\Java\lib\ext java.version == 1.8.0_202 (Java 1) java.vm.name == Java HotSpot(TM) Client VM java.vm.vendor == Oracle Corporation java.vm.version == 25.202-b08 java.vm.specification.name == Java Virtual Machine Specification java.vm.specification.vendor == Oracle Corporation java.vm.specification.version == 1.8 java.specification.name == Java Platform API Specification java.specification.vendor == Oracle Corporation java.specification.version == 1.8 java.vendor == Oracle Corporation java.vendor.url == http://java.oracle.com/ java.class.version == 52.0 java.library.path == C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\Program Files\OpenSSL-Win64\bin;C:\StellarStudio-7.0\SDKS\TOOLS-1.4.0\HostTools\CoreUtils\bin;C:\HIGHTEC\toolchains\arm\v8.1.0\bin;C:\Program Files\Microsoft\jdk-11.0.12.7-hotspot\bin\server;C:\HighTec\toolchains\tricore\v4.6.3.0\bin;C:\Perl64\site\bin;C:\Perl64\bin;C:\HighTec\toolchains\tricore\v4.9.3.0\bin;C:\HighTec\licensemanager;C:\HighTec\toolchains\tricore\v4.6.6.1\bin;C:\HighTec/licensemanager;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\TortoiseSVN\bin;C:\Program Files\MATLAB\R2021a\runtime\win64;C:\Program Files\MATLAB\R2021a\bin;C:\Program Files (x86)\Microchip\xc16\v1.34\bin;C:\Program Files\dotnet\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.21.27702\bin\Hostx64\x86;C:\40_HexView;E:\openssl-1.1.1b\win32-release\bin;C:\Program Files\Microchip\xc16\v1.50\bin;C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\;C:\Program Files\Microsoft SQL Server\150\Tools\Binn\;C:\Program Files (x86)\IVI Foundation\VISA\WinNT\Bin\;C:\Program Files\IVI Foundation\VISA\Win64\Bin\;C:\Program Files (x86)\IVI Foundation\VISA\WinNT\Bin;C:\make;C:\Program Files\Vector SIL Kit 4.0.52\x86\bin;C:\Program Files\Vector SIL Kit 4.0.52\x86_64\bin;C:\Program Files (x86)\Vector CANdb++ 3.1\Exec32;C:\Program Files\Git\cmd;C:\Program Files\Git;C:\Program Files (x86)\Vector ICD Manager 2.1\\Exec32;C:\HIGHTEC\licensemanager;C:\Program Files\Polyspace\R2021b\polyspace\bin;C:\Users\Jie.SH.Wu\AppData\Local\Programs\Python\Python314\Scripts\;C:\Users\Jie.SH.Wu\AppData\Local\Programs\Python\Python314\;C:\Users\Jie.SH.Wu\AppData\Local\Microsoft\WindowsApps;D:\Program Files\Microsoft VS Code\bin;C:\Users\Jie.SH.Wu\.dotnet\tools;C:\Users\Jie.SH.Wu\AppData\Local\Programs\CodeBuddy CN\bin;. java.compiler == null java.home == C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre java.io.tmpdir == C:\Users\JIESH~1.WU\AppData\Local\Temp\ os.name == Windows 10 os.arch == x86 os.version == 10.0 path.separator == ; file.separator == \ file.encoding == GBK user.name == Jie.SH.Wu user.home == C:\Users\Jie.SH.Wu user.dir == C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows user.language == zh user.region == null __________________________________________________________________________ Loading externalized properties ZGGfxUtil.loadImage: loading failed for: com/zerog/ia/installer/images/billboard_defaultNew.png RepositoryManager: Trying fallback repository location... # # INSTALLING VM: C:\NXP\S32DS_Power_v2.1\jre # System's temporary directory = C:\Users\Jie.SH.Wu\AppData\Local\Temp ==== License service installation log start: ==== ==== License service installation log end. ==== ==== License activation log start: ==== # # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x61878c19, pid=30876, tid=0x00007cac # # JRE version: Java(TM) SE Runtime Environment (8.0_202-b08) (build 1.8.0_202-b08) # Java VM: Java HotSpot(TM) Client VM (25.202-b08 mixed mode windows-x86 ) # Problematic frame: # C [cll_app.dll+0x18c19] # # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows # # An error report file with more information is saved as: # C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\hs_err_pid30876.log # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # ==== License activation log end. ==== ==== License list start: ==== # # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x61878c19, pid=17600, tid=0x0000623c # # JRE version: Java(TM) SE Runtime Environment (8.0_202-b08) (build 1.8.0_202-b08) # Java VM: Java HotSpot(TM) Client VM (25.202-b08 mixed mode windows-x86 ) # Problematic frame: # C [cll_app.dll+0x18c19] # # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows # # An error report file with more information is saved as: # C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\hs_err_pid17600.log # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # ==== License list end. ==== XMLScriptWriter: No Installation Objects were skipped 8. final log file name=C:\NXP\S32DS_Power_v2.1\_S32 Design Studio for Power Architecture Version 2.1_installation\Logs\S32_Design_Studio_for_Power_Architecture_Version_2.1_Install_10_19_2026_17_14_43.log ====================STDOUT ENTRIES================== C:\NXP\S32DS_Power_v2.1\jre C:\NXP\S32DS_Power_v2.1\jre\bin C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-console-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-datetime-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-debug-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-errorhandling-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-file-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-file-l1-2-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-file-l2-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-handle-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-heap-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-interlocked-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-libraryloader-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-localization-l1-2-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-memory-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-namedpipe-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-processenvironment-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-processthreads-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-processthreads-l1-1-1.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-profile-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-rtlsupport-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-string-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-synch-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-synch-l1-2-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-sysinfo-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-timezone-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-util-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-conio-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-convert-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-environment-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-filesystem-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-heap-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-locale-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-math-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-multibyte-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-private-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-process-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-runtime-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-stdio-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-string-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-time-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-utility-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\awt.dll C:\NXP\S32DS_Power_v2.1\jre\bin\bci.dll C:\NXP\S32DS_Power_v2.1\jre\bin\client C:\NXP\S32DS_Power_v2.1\jre\bin\client\jvm.dll C:\NXP\S32DS_Power_v2.1\jre\bin\client\Xusage.txt C:\NXP\S32DS_Power_v2.1\jre\bin\concrt140.dll C:\NXP\S32DS_Power_v2.1\jre\bin\dcpr.dll C:\NXP\S32DS_Power_v2.1\jre\bin\decora_sse.dll C:\NXP\S32DS_Power_v2.1\jre\bin\deploy.dll C:\NXP\S32DS_Power_v2.1\jre\bin\dtplugin C:\NXP\S32DS_Power_v2.1\jre\bin\dtplugin\deployJava1.dll C:\NXP\S32DS_Power_v2.1\jre\bin\dtplugin\npdeployJava1.dll C:\NXP\S32DS_Power_v2.1\jre\bin\dt_shmem.dll C:\NXP\S32DS_Power_v2.1\jre\bin\dt_socket.dll C:\NXP\S32DS_Power_v2.1\jre\bin\eula.dll C:\NXP\S32DS_Power_v2.1\jre\bin\fontmanager.dll C:\NXP\S32DS_Power_v2.1\jre\bin\fxplugins.dll C:\NXP\S32DS_Power_v2.1\jre\bin\glass.dll C:\NXP\S32DS_Power_v2.1\jre\bin\glib-lite.dll C:\NXP\S32DS_Power_v2.1\jre\bin\gstreamer-lite.dll C:\NXP\S32DS_Power_v2.1\jre\bin\hprof.dll C:\NXP\S32DS_Power_v2.1\jre\bin\instrument.dll C:\NXP\S32DS_Power_v2.1\jre\bin\j2pcsc.dll C:\NXP\S32DS_Power_v2.1\jre\bin\j2pkcs11.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jaas_nt.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jabswitch.exe C:\NXP\S32DS_Power_v2.1\jre\bin\java-rmi.exe C:\NXP\S32DS_Power_v2.1\jre\bin\java.dll C:\NXP\S32DS_Power_v2.1\jre\bin\java.exe C:\NXP\S32DS_Power_v2.1\jre\bin\JavaAccessBridge-32.dll C:\NXP\S32DS_Power_v2.1\jre\bin\JavaAccessBridge.dll C:\NXP\S32DS_Power_v2.1\jre\bin\javacpl.cpl C:\NXP\S32DS_Power_v2.1\jre\bin\javacpl.exe C:\NXP\S32DS_Power_v2.1\jre\bin\javafx_font.dll C:\NXP\S32DS_Power_v2.1\jre\bin\javafx_font_t2k.dll C:\NXP\S32DS_Power_v2.1\jre\bin\javafx_iio.dll C:\NXP\S32DS_Power_v2.1\jre\bin\javaw.exe C:\NXP\S32DS_Power_v2.1\jre\bin\javaws.exe C:\NXP\S32DS_Power_v2.1\jre\bin\java_crw_demo.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jawt.dll C:\NXP\S32DS_Power_v2.1\jre\bin\JAWTAccessBridge-32.dll C:\NXP\S32DS_Power_v2.1\jre\bin\JAWTAccessBridge.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jdwp.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jfr.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jfxmedia.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jfxwebkit.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jjs.exe C:\NXP\S32DS_Power_v2.1\jre\bin\jli.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jp2iexp.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jp2launcher.exe C:\NXP\S32DS_Power_v2.1\jre\bin\jp2native.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jp2ssv.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jpeg.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jsdt.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jsound.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jsoundds.dll C:\NXP\S32DS_Power_v2.1\jre\bin\keytool.exe C:\NXP\S32DS_Power_v2.1\jre\bin\kinit.exe C:\NXP\S32DS_Power_v2.1\jre\bin\klist.exe C:\NXP\S32DS_Power_v2.1\jre\bin\ktab.exe C:\NXP\S32DS_Power_v2.1\jre\bin\lcms.dll C:\NXP\S32DS_Power_v2.1\jre\bin\management.dll C:\NXP\S32DS_Power_v2.1\jre\bin\mlib_image.dll C:\NXP\S32DS_Power_v2.1\jre\bin\msvcp140.dll C:\NXP\S32DS_Power_v2.1\jre\bin\msvcr100.dll C:\NXP\S32DS_Power_v2.1\jre\bin\net.dll C:\NXP\S32DS_Power_v2.1\jre\bin\nio.dll C:\NXP\S32DS_Power_v2.1\jre\bin\npt.dll C:\NXP\S32DS_Power_v2.1\jre\bin\orbd.exe C:\NXP\S32DS_Power_v2.1\jre\bin\pack200.exe C:\NXP\S32DS_Power_v2.1\jre\bin\plugin2 C:\NXP\S32DS_Power_v2.1\jre\bin\plugin2\msvcr100.dll C:\NXP\S32DS_Power_v2.1\jre\bin\plugin2\npjp2.dll C:\NXP\S32DS_Power_v2.1\jre\bin\policytool.exe C:\NXP\S32DS_Power_v2.1\jre\bin\prism_common.dll C:\NXP\S32DS_Power_v2.1\jre\bin\prism_d3d.dll C:\NXP\S32DS_Power_v2.1\jre\bin\prism_sw.dll C:\NXP\S32DS_Power_v2.1\jre\bin\resource.dll C:\NXP\S32DS_Power_v2.1\jre\bin\rmid.exe C:\NXP\S32DS_Power_v2.1\jre\bin\rmiregistry.exe C:\NXP\S32DS_Power_v2.1\jre\bin\servertool.exe C:\NXP\S32DS_Power_v2.1\jre\bin\splashscreen.dll C:\NXP\S32DS_Power_v2.1\jre\bin\ssv.dll C:\NXP\S32DS_Power_v2.1\jre\bin\ssvagent.exe C:\NXP\S32DS_Power_v2.1\jre\bin\sunec.dll C:\NXP\S32DS_Power_v2.1\jre\bin\sunmscapi.dll C:\NXP\S32DS_Power_v2.1\jre\bin\t2k.dll C:\NXP\S32DS_Power_v2.1\jre\bin\tnameserv.exe C:\NXP\S32DS_Power_v2.1\jre\bin\ucrtbase.dll C:\NXP\S32DS_Power_v2.1\jre\bin\unpack.dll C:\NXP\S32DS_Power_v2.1\jre\bin\unpack200.exe C:\NXP\S32DS_Power_v2.1\jre\bin\vcruntime140.dll C:\NXP\S32DS_Power_v2.1\jre\bin\verify.dll C:\NXP\S32DS_Power_v2.1\jre\bin\w2k_lsa_auth.dll C:\NXP\S32DS_Power_v2.1\jre\bin\WindowsAccessBridge-32.dll C:\NXP\S32DS_Power_v2.1\jre\bin\WindowsAccessBridge.dll C:\NXP\S32DS_Power_v2.1\jre\bin\wsdetect.dll C:\NXP\S32DS_Power_v2.1\jre\bin\zip.dll C:\NXP\S32DS_Power_v2.1\jre\COPYRIGHT C:\NXP\S32DS_Power_v2.1\jre\lib C:\NXP\S32DS_Power_v2.1\jre\lib\accessibility.properties C:\NXP\S32DS_Power_v2.1\jre\lib\calendars.properties C:\NXP\S32DS_Power_v2.1\jre\lib\charsets.jar C:\NXP\S32DS_Power_v2.1\jre\lib\classlist C:\NXP\S32DS_Power_v2.1\jre\lib\cmm C:\NXP\S32DS_Power_v2.1\jre\lib\cmm\CIEXYZ.pf C:\NXP\S32DS_Power_v2.1\jre\lib\cmm\GRAY.pf C:\NXP\S32DS_Power_v2.1\jre\lib\cmm\LINEAR_RGB.pf C:\NXP\S32DS_Power_v2.1\jre\lib\cmm\PYCC.pf C:\NXP\S32DS_Power_v2.1\jre\lib\cmm\sRGB.pf C:\NXP\S32DS_Power_v2.1\jre\lib\content-types.properties C:\NXP\S32DS_Power_v2.1\jre\lib\currency.data C:\NXP\S32DS_Power_v2.1\jre\lib\deploy C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\ffjcext.zip C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\messages.properties C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\messages_de.properties C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\messages_es.properties C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\messages_fr.properties C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\messages_it.properties C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\messages_ja.properties C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\messages_ko.properties C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\messages_pt_BR.properties C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\messages_sv.properties C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\messages_zh_CN.properties C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\messages_zh_HK.properties C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\messages_zh_TW.properties C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\splash.gif C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\[email protected] C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\splash_11-lic.gif C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\[email protected] C:\NXP\S32DS_Power_v2.1\jre\lib\deploy.jar C:\NXP\S32DS_Power_v2.1\jre\lib\ext C:\NXP\S32DS_Power_v2.1\jre\lib\ext\access-bridge-32.jar C:\NXP\S32DS_Power_v2.1\jre\lib\ext\access-bridge.jar C:\NXP\S32DS_Power_v2.1\jre\lib\ext\cldrdata.jar C:\NXP\S32DS_Power_v2.1\jre\lib\ext\dnsns.jar C:\NXP\S32DS_Power_v2.1\jre\lib\ext\jaccess.jar C:\NXP\S32DS_Power_v2.1\jre\lib\ext\jfxrt.jar C:\NXP\S32DS_Power_v2.1\jre\lib\ext\localedata.jar C:\NXP\S32DS_Power_v2.1\jre\lib\ext\meta-index C:\NXP\S32DS_Power_v2.1\jre\lib\ext\nashorn.jar C:\NXP\S32DS_Power_v2.1\jre\lib\ext\sunec.jar C:\NXP\S32DS_Power_v2.1\jre\lib\ext\sunjce_provider.jar C:\NXP\S32DS_Power_v2.1\jre\lib\ext\sunmscapi.jar C:\NXP\S32DS_Power_v2.1\jre\lib\ext\sunpkcs11.jar C:\NXP\S32DS_Power_v2.1\jre\lib\ext\zipfs.jar C:\NXP\S32DS_Power_v2.1\jre\lib\flavormap.properties C:\NXP\S32DS_Power_v2.1\jre\lib\fontconfig.bfc C:\NXP\S32DS_Power_v2.1\jre\lib\fontconfig.properties.src C:\NXP\S32DS_Power_v2.1\jre\lib\fonts C:\NXP\S32DS_Power_v2.1\jre\lib\fonts\LucidaBrightDemiBold.ttf C:\NXP\S32DS_Power_v2.1\jre\lib\fonts\LucidaBrightDemiItalic.ttf C:\NXP\S32DS_Power_v2.1\jre\lib\fonts\LucidaBrightItalic.ttf C:\NXP\S32DS_Power_v2.1\jre\lib\fonts\LucidaBrightRegular.ttf C:\NXP\S32DS_Power_v2.1\jre\lib\fonts\LucidaSansDemiBold.ttf C:\NXP\S32DS_Power_v2.1\jre\lib\fonts\LucidaSansRegular.ttf C:\NXP\S32DS_Power_v2.1\jre\lib\fonts\LucidaTypewriterBold.ttf C:\NXP\S32DS_Power_v2.1\jre\lib\fonts\LucidaTypewriterRegular.ttf C:\NXP\S32DS_Power_v2.1\jre\lib\hijrah-config-umalqura.properties C:\NXP\S32DS_Power_v2.1\jre\lib\i386 C:\NXP\S32DS_Power_v2.1\jre\lib\i386\jvm.cfg C:\NXP\S32DS_Power_v2.1\jre\lib\images C:\NXP\S32DS_Power_v2.1\jre\lib\images\cursors C:\NXP\S32DS_Power_v2.1\jre\lib\images\cursors\cursors.properties C:\NXP\S32DS_Power_v2.1\jre\lib\images\cursors\invalid32x32.gif C:\NXP\S32DS_Power_v2.1\jre\lib\images\cursors\win32_CopyDrop32x32.gif C:\NXP\S32DS_Power_v2.1\jre\lib\images\cursors\win32_CopyNoDrop32x32.gif C:\NXP\S32DS_Power_v2.1\jre\lib\images\cursors\win32_LinkDrop32x32.gif C:\NXP\S32DS_Power_v2.1\jre\lib\images\cursors\win32_LinkNoDrop32x32.gif C:\NXP\S32DS_Power_v2.1\jre\lib\images\cursors\win32_MoveDrop32x32.gif C:\NXP\S32DS_Power_v2.1\jre\lib\images\cursors\win32_MoveNoDrop32x32.gif C:\NXP\S32DS_Power_v2.1\jre\lib\javafx.properties C:\NXP\S32DS_Power_v2.1\jre\lib\javaws.jar C:\NXP\S32DS_Power_v2.1\jre\lib\jce.jar C:\NXP\S32DS_Power_v2.1\jre\lib\jfr C:\NXP\S32DS_Power_v2.1\jre\lib\jfr\default.jfc C:\NXP\S32DS_Power_v2.1\jre\lib\jfr\profile.jfc C:\NXP\S32DS_Power_v2.1\jre\lib\jfr.jar C:\NXP\S32DS_Power_v2.1\jre\lib\jfxswt.jar C:\NXP\S32DS_Power_v2.1\jre\lib\jsse.jar C:\NXP\S32DS_Power_v2.1\jre\lib\jvm.hprof.txt C:\NXP\S32DS_Power_v2.1\jre\lib\logging.properties C:\NXP\S32DS_Power_v2.1\jre\lib\management C:\NXP\S32DS_Power_v2.1\jre\lib\management\jmxremote.access C:\NXP\S32DS_Power_v2.1\jre\lib\management\jmxremote.password.template C:\NXP\S32DS_Power_v2.1\jre\lib\management\management.properties C:\NXP\S32DS_Power_v2.1\jre\lib\management\snmp.acl.template C:\NXP\S32DS_Power_v2.1\jre\lib\management-agent.jar C:\NXP\S32DS_Power_v2.1\jre\lib\meta-index C:\NXP\S32DS_Power_v2.1\jre\lib\net.properties C:\NXP\S32DS_Power_v2.1\jre\lib\plugin.jar C:\NXP\S32DS_Power_v2.1\jre\lib\psfont.properties.ja C:\NXP\S32DS_Power_v2.1\jre\lib\psfontj2d.properties C:\NXP\S32DS_Power_v2.1\jre\lib\resources.jar C:\NXP\S32DS_Power_v2.1\jre\lib\rt.jar C:\NXP\S32DS_Power_v2.1\jre\lib\security C:\NXP\S32DS_Power_v2.1\jre\lib\security\blacklist C:\NXP\S32DS_Power_v2.1\jre\lib\security\blacklisted.certs C:\NXP\S32DS_Power_v2.1\jre\lib\security\cacerts C:\NXP\S32DS_Power_v2.1\jre\lib\security\java.policy C:\NXP\S32DS_Power_v2.1\jre\lib\security\java.security C:\NXP\S32DS_Power_v2.1\jre\lib\security\javaws.policy C:\NXP\S32DS_Power_v2.1\jre\lib\security\policy C:\NXP\S32DS_Power_v2.1\jre\lib\security\policy\limited C:\NXP\S32DS_Power_v2.1\jre\lib\security\policy\limited\local_policy.jar C:\NXP\S32DS_Power_v2.1\jre\lib\security\policy\limited\US_export_policy.jar C:\NXP\S32DS_Power_v2.1\jre\lib\security\policy\unlimited C:\NXP\S32DS_Power_v2.1\jre\lib\security\policy\unlimited\local_policy.jar C:\NXP\S32DS_Power_v2.1\jre\lib\security\policy\unlimited\US_export_policy.jar C:\NXP\S32DS_Power_v2.1\jre\lib\security\trusted.libraries C:\NXP\S32DS_Power_v2.1\jre\lib\sound.properties C:\NXP\S32DS_Power_v2.1\jre\lib\tzdb.dat C:\NXP\S32DS_Power_v2.1\jre\lib\tzmappings C:\NXP\S32DS_Power_v2.1\jre\LICENSE C:\NXP\S32DS_Power_v2.1\jre\README.txt C:\NXP\S32DS_Power_v2.1\jre\release C:\NXP\S32DS_Power_v2.1\jre\THIRDPARTYLICENSEREADME-JAVAFX.txt C:\NXP\S32DS_Power_v2.1\jre\THIRDPARTYLICENSEREADME.txt C:\NXP\S32DS_Power_v2.1\jre\Welcome.html C:\NXP\S32DS_Power_v2.1\_S32 Design Studio for Power Architecture Version 2.1_installation C:\NXP\S32DS_Power_v2.1\_S32 Design Studio for Power Architecture Version 2.1_installation\.com.zerog.registry.xml C:\NXP\S32DS_Power_v2.1\_S32 Design Studio for Power Architecture Version 2.1_installation\InstallScript.iap_xml C:\NXP\S32DS_Power_v2.1\_S32 Design Studio for Power Architecture Version 2.1_installation\Logs C:\NXP\S32DS_Power_v2.1\_S32 Design Studio for Power Architecture Version 2.1_installation\Logs\S32_Design_Studio_for_Power_Architecture_Version_2.1_Install_10_19_2026_16_45_25.log C:\NXP\S32DS_Power_v2.1\_S32 Design Studio for Power Architecture Version 2.1_installation\resource C:\NXP\S32DS_Power_v2.1\_S32 Design Studio for Power Architecture Version 2.1_installation\resource\iawin32.dll C:\NXP\S32DS_Power_v2.1\_S32 Design Studio for Power Architecture Version 2.1_installation\resource\invoker.exe C:\NXP\S32DS_Power_v2.1\_S32 Design Studio for Power Architecture Version 2.1_installation\resource\remove.exe C:\NXP\S32DS_Power_v2.1\_S32 Design Studio for Power Architecture Version 2.1_installation\resource\win64_32_x64.exe C:\NXP\S32DS_Power_v2.1\_S32 Design Studio for Power Architecture Version 2.1_installation\uninstaller.jar Re: S32DS_Power_Win32_v2.1 install fail. rollbacked Hello, Based on the installation log, the failure does not appear to be related to administrator privileges or disk space. The installation proceeds successfully through the file extraction, prerequisite installation, and licensing setup stages. However, it fails during the license activation step, where the licensing component crashes inside the native library cll_app.dll. This causes the installer to trigger a rollback of the entire installation. As a first troubleshooting step: 1. Removing any existing S32DS or FlexNet/FNP licensing service installations from the system. 2. Deleting or backing up the contents of the FlexNet licensing directory:     C:\ProgramData\FLEXnet 3. Temporarily disabling antivirus or endpoint protection software. 4. Running the installer from a short local path (for example, C:\Temp). Please provide the contents of the hs_err_pid*.log files if the issue persists, and we can further analyze the crash. Best regards, Peter Re: S32DS_Power_Win32_v2.1 install fail. rollbacked install success after temporarily disabling antivirus
View full article
S32DS_Power_Win32_v2.1 安装失败。回滚 即使是管理员操作,安装也总是失败并需要回滚。 以下是日志信息: __________________________________________________________________________ 2026年10月19日星期一 05:14:43 CST 可用内存:25439 kB 总内存:40852 kB java.class.path: C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\InstallerData\IAClasses.zip C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\InstallerData\Execute.zip C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\InstallerData\Execute.zip C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\InstallerData\Resource1.zip C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\InstallerData\Resource1.zip C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\InstallerData C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\InstallerData ZGUtil.CLASS_PATH: C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\InstallerData\IAClasses.zip C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\InstallerData\Execute.zip C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\InstallerData sun.启动.class.path: C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\resources.jar C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\rt.jar C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\sunrsasign.jar C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\jsse.jar C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\jce.jar C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\charsets.jar C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\jfr.jar C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\classes java.ext.dirs: C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\ext C:\WINDOWS\Sun\Java\lib\ext java.version == 1.8.0_202 (Java 1) java.vm.name == Java HotSpot(TM) 客户端虚拟机 java.vm.vendor == Oracle Corporation java.vm.version == 25.202-b08 java.vm.specification.name == Java 虚拟机规范 java.vm.specification.vendor == Oracle Corporation java.vm.specification.version == 1.8 java.specification.name == Java 平台 API 规范 java.specification.vendor == Oracle Corporation java.specification.version == 1.8 java.vendor == Oracle Corporation java.vendor.url == http://java.oracle.com/ java.class.version == 52.0 java.library.path == C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\Program Files\OpenSSL-Win64\bin;C:\StellarStudio-7.0\SDKS\TOOLS-1.4.0\HostTools\CoreUtils\bin;C:\HIGHTEC\toolchains\arm\v8.1.0\bin;C:\ProgramFiles\Microsoft\jdk-11.0.12.7-hotspot\bin\server;C:\HighTec\toolchains\tricore\v4.6.3.0\bin;C:\Perl64\site\bin;C:\Perl64\bin;C:\HighTec\toolchains\tricore\v4.9.3.0\bin;C:\HighTec\licensemanager;C:\HighTec\toolchains\tricore\v4.6.6.1\bin;C:\HighTec/licensemanager;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program文件\TortoiseSVN\bin;C:\Program Files\MATLAB\R2021a\runtime\win64;C:\Program Files\MATLAB\R2021a\bin;C:\Program Files (x86)\Microchip\xc16\v1.34\bin;C:\Program Files\dotnet\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.21.27702\bin\Hostx64\x86;C:\40_HexView;E:\openssl-1.1.1b\win32-版本\bin;C:\Program文件\Microchip\xc16\v1.50\bin;C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\;C:\Program Files\Microsoft SQL Server\150\Tools\Binn\;C:\Program Files (x86)\IVI Foundation\VISA\WinNT\Bin\;C:\Program Files\IVI Foundation\VISA\Win64\Bin\;C:\Program Files (x86)\IVI Foundation\VISA\WinNT\Bin;C:\make;C:\Program Files\Vector SIL Kit 4.0.52\x86\bin;C:\ProgramFiles\Vector SIL Kit 4.0.52\x86_64\bin;C:\ProgramFiles (x86)\Vector CANdb++ 3.1\Exec32;C:\Program Files\Git\cmd;C:\Program Files\Git;C:\Program Files (x86)\Vector ICD Manager 2.1\\Exec32;C:\HIGHTEC\licensemanager;C:\Program Files\Polyspace\R2021b\polyspace\bin;C:\Users\Jie.SH.Wu\AppData\Local\Programs\Python\Python314\Scripts\;C:\Users\Jie.SH.Wu\AppData\Local\Programs\Python\Python314\;C:\Users\Jie.SH.Wu\AppData\Local\Microsoft\WindowsApps;D:\Program Files\Microsoft VS Code\bin;C:\Users\Jie.SH.Wu\.dotnet\tools;C:\Users\Jie.SH.Wu\AppData\Local\Programs\CodeBuddy CN\bin;。 java.compiler == null java.home == C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre java.io.tmpdir == C:\Users\JIESH~1.WU\AppData\Local\Temp\ 操作系统名称 == Windows 10 操作系统架构 == x86 操作系统版本 == 10.0 路径分隔符 == ; 文件分隔符 == \ 文件编码 == GBK 用户名 == Jie.SH.Wu 用户主目录 == C:\Users\Jie.SH.Wu user.dir == C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows 用户语言 == en user.region == null __________________________________________________________________________ 已安装功能:S32 Design Studio for Power Architecture 版本 2.1 的 S32DSF 安装开始时间:2026年10月19日下午5:02:33(美国中部时间) 安装结束时间:2026年10月19日 下午5:04:17 CST 由 InstallAnywhere 18.0 专业版 5608 版本安装 用户交互 ----------------- #选择附加功能 #---------------------------- 已选功能列表=S32DSF 已选安装功能列表=S32DSF 已选安装集=S32 Des #选择安装位置 #----------------------- USER_INSTALL_DIR=C:\\NXP\\S32DS_Power_v2.1 #选择快捷方式文件夹 #---------------------- 用户快捷方式=C:\\Users\\Jie.SH.Wu\\AppData\\Roaming\\Microsoft\\Windows\\Start Menu\\Programs\\NXP S32 Design Studio\\S32 Design Studio for Power Architecture Version 2.1 #安装 #------- -fileOverwrite_C\:\\NXP\\S32DS_Power_v2.1\\_S32\Design\ Studio\ for\ Power\ Architecture\ Version\ 2.1_installation\\resource\\iawin32.dll=是 -fileOverwrite_C\:\\NXP\\S32DS_Power_v2.1\\_S32\Design\ Studio\ for\ Power\ Architecture\ Version\ 2.1_installation\\resource\\win64_32_x64.exe=是 -fileOverwrite_C\:\\NXP\\S32DS_Power_v2.1\\_S32\Design\ Studio\ for\ Power\ Architecture\ Version\ 2.1_installation\\resource\\remove.exe=是 -fileOverwrite_C\:\\NXP\\S32DS_Power_v2.1\\_S32\Design\ Studio\ for\ Power\ Architecture\ Version\ 2.1_installation\\resource\\invoker.exe=是 概括 ------- 安装失败。 48项成功 24个警告 1 非致命错误 1 致命错误 行动要点: 无 安装日志详情: 检查磁盘空间:C:\NXP\S32DS__v2.1 状态:成功 补充说明:注意 - 所需磁盘空间:7,110,809,247 字节;可用磁盘空间:52,016,885,760 字节 检查磁盘空间:C:\NXP\S32DS_Power_v2.1 状态:成功 补充说明:注意 - 所需磁盘空间:7,110,809,247 字节;可用磁盘空间:52,016,885,760 字节 安装目录:C:\NXP\S32DS_Power_v2.1\jre 状态:成功 安装 JRE:C:\NXP\S32DS_Power_v2.1\jre 状态:成功 安装目录:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\ 状态:成功 补充说明:注意 - 目录已存在。 执行命令:NET SESSION 状态:成功 安装文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\vcredist_2013_x86.exe 状态:成功 展开压缩文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\vcredist.zip 状态:成功 安装文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\vcredist_2010SP1_x86.exe 状态:成功 展开压缩文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\vcredist2010.zip 状态:成功 执行命令:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\vcredist_2013_x86.exe /quiet 状态:成功 执行命令:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\vcredist_2010SP1_x86.exe /quiet 状态:成功 安装文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\clljni.dll 状态:成功 安装文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\cllSvrUtility.exe 状态:成功 安装文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\cllSvrUtility.exe.清单 状态:成功 安装文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\cll_app.dll 状态:成功 安装文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\cll_app_libFNP.dll 状态:成功 安装文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\cll_svr.dll 状态:成功 安装文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\cll_svr_libFNP.dll 状态:成功 安装文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\FnpCommsSoap.dll 状态:成功 安装文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\FNP_Act_Installer.dll 状态:成功 安装文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\x64\FnpCommsSoap.so 状态:成功 安装文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\x64\libclljni.so 状态:成功 安装文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\x64\libcll_app.so 状态:成功 安装文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\x64\libcll_app_libFNP.so 状态:成功 安装文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\x64\libcll_svr.so 状态:成功 安装文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\x64\libcll_svr_libFNP.so 状态:成功 安装文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\FNPLicensingService\FNPLicensingService 状态:成功 安装文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\install_fnp.sh 状态:成功 安装文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\license.jar 状态:成功 展开压缩文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\Activation.zip 状态:成功 执行命令:java "-Djava.library.path=C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86"-jar "C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\license.jar"安装 -prod S32DS-PA_v2.1 状态:成功 执行命令:java "-Djava.library.path=C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86"-jar "C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\license.jar"验证 -功能已激活 -版本 2.1 -产品 S32DS-PA_v2.1 状态:成功 执行命令:java "-Djava.library.path=C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86"-jar "C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\license.jar"运行 -feature Activated -version 2.1 -prod S32DS-PA_v2.1 状态:成功 执行命令:java "-Djava.library.path=C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86"-jar "C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\license.jar"列表 状态:成功 安装卸载程序:S32 Design Studio for Power Architecture 版本 2.1(安装所有卸载程序元器件) 状态:成功 安装目录:C:\NXP\S32DS_Power_v2.1\_S32电源架构设计工作室 2.1 版_安装\资源\ 状态:成功 安装文件:C:\NXP\S32DS_Power_v2.1\_S32Power Architecture 设计工作室 2.1 版_installation\resource\iawin32.dll 状态:成功 安装文件:C:\NXP\S32DS_Power_v2.1\_S32Power Architecture 设计工作室 2.1 版_安装\资源\win64_32_x64.exe 状态:成功 安装文件:C:\NXP\S32DS_Power_v2.1\_S32Design Studio for Power Architecture Version 2.1_installation\resource\remove.exe 状态:成功 安装文件:C:\NXP\S32DS_Power_v2.1\_S32Power Architecture 设计工作室 2.1 版_installation\resource\invoker.exe 状态:成功 安装卸载程序:S32 Design Studio for Power Architecture 版本 2.1(安装所有卸载程序元器件) 状态:错误 补充说明:错误 - 写入 LaunchAnywhere 元器件时出错(访问被拒绝) 卸载文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\vcredist_2013_x86.exe 状态:警告 补充说明:警告 - 文件不存在 卸载文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\vcredist_2010SP1_x86.exe 状态:警告 补充说明:警告 - 文件不存在 卸载文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\clljni.dll 状态:警告 补充说明:警告 - 文件不存在 卸载文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\cllSvrUtility.exe 状态:警告 补充说明:警告 - 文件不存在 卸载文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\cllSvrUtility.exe.manifest 状态:警告 补充说明:警告 - 文件不存在 卸载文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\cll_app.dll 状态:警告 补充说明:警告 - 文件不存在 卸载文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\cll_app_libFNP.dll 状态:警告 补充说明:警告 - 文件不存在 卸载文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\cll_svr.dll 状态:警告 补充说明:警告 - 文件不存在 卸载文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\cll_svr_libFNP.dll 状态:警告 补充说明:警告 - 文件不存在 卸载文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\FnpCommsSoap.dll 状态:警告 补充说明:警告 - 文件不存在 卸载文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86\FNP_Act_Installer.dll 状态:警告 补充说明:警告 - 文件不存在 卸载文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\x64\FnpCommsSoap.so 状态:警告 补充说明:警告 - 文件不存在 卸载文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\x64\libclljni.so 状态:警告 补充说明:警告 - 文件不存在 卸载文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\x64\libcll_app.so 状态:警告 补充说明:警告 - 文件不存在 卸载文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\x64\libcll_app_libFNP.so 状态:警告 补充说明:警告 - 文件不存在 卸载文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\x64\libcll_svr.so 状态:警告 补充说明:警告 - 文件不存在 卸载文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\x64\libcll_svr_libFNP.so 状态:警告 补充说明:警告 - 文件不存在 卸载文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\FNPLicensingService\FNPLicensingService 状态:警告 补充说明:警告 - 文件不存在 卸载文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\install_fnp.sh 状态:警告 补充说明:警告 - 文件不存在 卸载文件:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\license.jar 状态:警告 补充说明:警告 - 文件不存在 卸载文件夹:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\FNPLicensingService 状态:警告 补充说明:警告 - 该路径不存在 卸载文件夹:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\x64 状态:警告 补充说明:警告 - 该路径不存在 卸载文件夹:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll\i86 状态:警告 补充说明:警告 - 该路径不存在 卸载文件夹:C:\Users\Jie.SH.Wu\AppData\Local\Temp\672195.tmp\cll 状态:警告 补充说明:警告 - 该路径不存在 卸载文件夹:C:\NXP\S32DS_Power_v2.1\jre 状态:成功 删除注册表项:5 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\null 状态:成功 安装以下操作时发生错误,因此已回滚安装……! 操作名称:触发回滚操作 操作说明:触发回滚操作 错误详情如下: 此操作会将安装回滚。 ====================标准错误输出条目=================== __________________________________________________________________________ InstallAnywhere 2017 版本:18.0 __________________________________________________________________________ 2026年10月19日星期一 05:02:26 CST 可用内存:12695 kB 总内存:15872 kB 没有争论 java.class.path: C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\InstallerData\IAClasses.zip C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\InstallerData\Execute.zip C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\InstallerData\Execute.zip C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\InstallerData\Resource1.zip C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\InstallerData\Resource1.zip C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\InstallerData C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\InstallerData ZGUtil.CLASS_PATH: C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\InstallerData\IAClasses.zip C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\InstallerData\Execute.zip C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\InstallerData sun.启动.class.path: C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\resources.jar C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\rt.jar C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\sunrsasign.jar C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\jsse.jar C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\jce.jar C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\charsets.jar C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\jfr.jar C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\classes java.ext.dirs: C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\lib\ext C:\WINDOWS\Sun\Java\lib\ext java.version == 1.8.0_202 (Java 1) java.vm.name == Java HotSpot(TM) 客户端虚拟机 java.vm.vendor == Oracle Corporation java.vm.version == 25.202-b08 java.vm.specification.name == Java 虚拟机规范 java.vm.specification.vendor == Oracle Corporation java.vm.specification.version == 1.8 java.specification.name == Java 平台 API 规范 java.specification.vendor == Oracle Corporation java.specification.version == 1.8 java.vendor == Oracle Corporation java.vendor.url == http://java.oracle.com/ java.class.version == 52.0 java.library.path == C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre\bin;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\Program Files\OpenSSL-Win64\bin;C:\StellarStudio-7.0\SDKS\TOOLS-1.4.0\HostTools\CoreUtils\bin;C:\HIGHTEC\toolchains\arm\v8.1.0\bin;C:\ProgramFiles\Microsoft\jdk-11.0.12.7-hotspot\bin\server;C:\HighTec\toolchains\tricore\v4.6.3.0\bin;C:\Perl64\site\bin;C:\Perl64\bin;C:\HighTec\toolchains\tricore\v4.9.3.0\bin;C:\HighTec\licensemanager;C:\HighTec\toolchains\tricore\v4.6.6.1\bin;C:\HighTec/licensemanager;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program文件\TortoiseSVN\bin;C:\Program Files\MATLAB\R2021a\runtime\win64;C:\Program Files\MATLAB\R2021a\bin;C:\Program Files (x86)\Microchip\xc16\v1.34\bin;C:\Program Files\dotnet\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\VC\Tools\MSVC\14.21.27702\bin\Hostx64\x86;C:\40_HexView;E:\openssl-1.1.1b\win32-版本\bin;C:\Program文件\Microchip\xc16\v1.50\bin;C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\;C:\Program Files\Microsoft SQL Server\150\Tools\Binn\;C:\Program Files (x86)\IVI Foundation\VISA\WinNT\Bin\;C:\Program Files\IVI Foundation\VISA\Win64\Bin\;C:\Program Files (x86)\IVI Foundation\VISA\WinNT\Bin;C:\make;C:\Program Files\Vector SIL Kit 4.0.52\x86\bin;C:\ProgramFiles\Vector SIL Kit 4.0.52\x86_64\bin;C:\ProgramFiles (x86)\Vector CANdb++ 3.1\Exec32;C:\Program Files\Git\cmd;C:\Program Files\Git;C:\Program Files (x86)\Vector ICD Manager 2.1\\Exec32;C:\HIGHTEC\licensemanager;C:\Program Files\Polyspace\R2021b\polyspace\bin;C:\Users\Jie.SH.Wu\AppData\Local\Programs\Python\Python314\Scripts\;C:\Users\Jie.SH.Wu\AppData\Local\Programs\Python\Python314\;C:\Users\Jie.SH.Wu\AppData\Local\Microsoft\WindowsApps;D:\Program Files\Microsoft VS Code\bin;C:\Users\Jie.SH.Wu\.dotnet\tools;C:\Users\Jie.SH.Wu\AppData\Local\Programs\CodeBuddy CN\bin;。 java.compiler == null java.home == C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\resource\jre java.io.tmpdir == C:\Users\JIESH~1.WU\AppData\Local\Temp\ 操作系统名称 == Windows 10 操作系统架构 == x86 操作系统版本 == 10.0 路径分隔符 == ; 文件分隔符 == \ 文件编码 == GBK 用户名 == Jie.SH.Wu 用户主目录 == C:\Users\Jie.SH.Wu user.dir == C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows user.language == zh user.region == null __________________________________________________________________________ 加载外部属性 ZGGfxUtil.loadImage:加载失败: com/zerog/ia/installer/images/billboard_defaultNew.png 仓库管理器:正在尝试备用仓库位置... # # 安装虚拟机:C:\NXP\S32DS_Power_v2.1\jre # 系统临时目录 = C:\Users\Jie.SH.Wu\AppData\Local\Temp ==== 许可证服务安装日志开始: ==== ==== 许可证服务安装日志结束。==== ==== 许可证激活日志开始: ==== # Java运行时环境检测到致命错误: # # 访问冲突异常 (0xc0000005),进程 ID 为 0x61878c19,进程 ID 为 30876,线程 ID 为 0x00007cac # # JRE 版本:Java(TM) SE 运行时环境 (8.0_202-b08) (内部版本 1.8.0_202-b08) # Java VM:Java HotSpot(TM) 客户端 VM (25.202-b08 混合模式 windows-x86) # 有问题的框架: # C [cll_app.dll+0x18c19] # # 核心转储写入失败。Windows 客户端版本默认情况下未启用小型转储文件。 # # 包含更多信息的错误报告文件已保存为: # C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\hs_err_pid30876.log # 如果您想提交错误报告,请访问: # http://bugreport.java.com/bugreport/crash.jsp # 该崩溃发生在 Java 虚拟机之外的本地代码中。 # 请查看有问题的帧,以了解在哪里报告错误。 # ==== 许可证激活日志结束。==== ==== 许可证列表开始: ==== # Java运行时环境检测到致命错误: # # 访问冲突异常 (0xc0000005),进程 ID 为 0x61878c19,进程 ID 为 17600,线程 ID 为 0x0000623c # # JRE 版本:Java(TM) SE 运行时环境 (8.0_202-b08) (内部版本 1.8.0_202-b08) # Java VM:Java HotSpot(TM) 客户端 VM (25.202-b08 混合模式 windows-x86) # 有问题的框架: # C [cll_app.dll+0x18c19] # # 核心转储写入失败。Windows 客户端版本默认情况下未启用小型转储文件。 # # 包含更多信息的错误报告文件已保存为: # C:\Users\Jie.SH.Wu\AppData\Local\Temp\I1792400320\Windows\hs_err_pid17600.log # 如果您想提交错误报告,请访问: # http://bugreport.java.com/bugreport/crash.jsp # 该崩溃发生在 Java 虚拟机之外的本地代码中。 # 请查看有问题的帧,以了解在哪里报告错误。 # ==== 许可证列表结束。==== XMLScriptWriter:未跳过任何安装对象 8. 最终日志文件名=C:\NXP\S32DS_Power_v2.1\_S32Design Studio for Power Architecture Version 2.1_installation\Logs\S32_Design_Studio_for_Power_Architecture_Version_2.1_Install_10_19_2026_17_14_43.log ====================标准输出条目=================== C:\NXP\S32DS_Power_v2.1\jre C:\NXP\S32DS_Power_v2.1\jre\bin C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-console-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-datetime-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-debug-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-errorhandling-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-file-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-file-l1-2-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-file-l2-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-handle-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-heap-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-interlocked-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-libraryloader-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-localization-l1-2-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-memory-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-namedpipe-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-processenvironment-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-processthreads-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-processthreads-l1-1-1.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-profile-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-rtlsupport-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-string-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-synch-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-synch-l1-2-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-sysinfo-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-timezone-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-core-util-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-conio-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-convert-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-environment-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-filesystem-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-heap-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-locale-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-math-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-multibyte-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-private-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-process-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-runtime-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-stdio-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-string-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-time-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\api-ms-win-crt-utility-l1-1-0.dll C:\NXP\S32DS_Power_v2.1\jre\bin\awt.dll C:\NXP\S32DS_Power_v2.1\jre\bin\bci.dll C:\NXP\S32DS_Power_v2.1\jre\bin\client C:\NXP\S32DS_Power_v2.1\jre\bin\client\jvm.dll C:\NXP\S32DS_Power_v2.1\jre\bin\client\Xusage.txt C:\NXP\S32DS_Power_v2.1\jre\bin\concrt140.dll C:\NXP\S32DS_Power_v2.1\jre\bin\dcpr.dll C:\NXP\S32DS_Power_v2.1\jre\bin\decora_sse.dll C:\NXP\S32DS_Power_v2.1\jre\bin\deploy.dll C:\NXP\S32DS_Power_v2.1\jre\bin\dtplugin C:\NXP\S32DS_Power_v2.1\jre\bin\dtplugin\deployJava1.dll C:\NXP\S32DS_Power_v2.1\jre\bin\dtplugin\npdeployJava1.dll C:\NXP\S32DS_Power_v2.1\jre\bin\dt_shmem.dll C:\NXP\S32DS_Power_v2.1\jre\bin\dt_socket.dll C:\NXP\S32DS_Power_v2.1\jre\bin\eula.dll C:\NXP\S32DS_Power_v2.1\jre\bin\fontmanager.dll C:\NXP\S32DS_Power_v2.1\jre\bin\fxplugins.dll C:\NXP\S32DS_Power_v2.1\jre\bin\glass.dll C:\NXP\S32DS_Power_v2.1\jre\bin\glib-lite.dll C:\NXP\S32DS_Power_v2.1\jre\bin\gstreamer-lite.dll C:\NXP\S32DS_Power_v2.1\jre\bin\hprof.dll C:\NXP\S32DS_Power_v2.1\jre\bin\instrument.dll C:\NXP\S32DS_Power_v2.1\jre\bin\j2pcsc.dll C:\NXP\S32DS_Power_v2.1\jre\bin\j2pkcs11.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jaas_nt.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jabswitch.exe C:\NXP\S32DS_Power_v2.1\jre\bin\java-rmi.exe C:\NXP\S32DS_Power_v2.1\jre\bin\java.dll C:\NXP\S32DS_Power_v2.1\jre\bin\java.exe C:\NXP\S32DS_Power_v2.1\jre\bin\JavaAccessBridge-32.dll C:\NXP\S32DS_Power_v2.1\jre\bin\JavaAccessBridge.dll C:\NXP\S32DS_Power_v2.1\jre\bin\javacpl.cpl C:\NXP\S32DS_Power_v2.1\jre\bin\javacpl.exe C:\NXP\S32DS_Power_v2.1\jre\bin\javafx_font.dll C:\NXP\S32DS_Power_v2.1\jre\bin\javafx_font_t2k.dll C:\NXP\S32DS_Power_v2.1\jre\bin\javafx_iio.dll C:\NXP\S32DS_Power_v2.1\jre\bin\javaw.exe C:\NXP\S32DS_Power_v2.1\jre\bin\javaws.exe C:\NXP\S32DS_Power_v2.1\jre\bin\java_crw_demo.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jawt.dll C:\NXP\S32DS_Power_v2.1\jre\bin\JAWTAccessBridge-32.dll C:\NXP\S32DS_Power_v2.1\jre\bin\JAWTAccessBridge.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jdwp.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jfr.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jfxmedia.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jfxwebkit.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jjs.exe C:\NXP\S32DS_Power_v2.1\jre\bin\jli.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jp2iexp.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jp2launcher.exe C:\NXP\S32DS_Power_v2.1\jre\bin\jp2native.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jp2ssv.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jpeg.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jsdt.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jsound.dll C:\NXP\S32DS_Power_v2.1\jre\bin\jsoundds.dll C:\NXP\S32DS_Power_v2.1\jre\bin\keytool.exe C:\NXP\S32DS_Power_v2.1\jre\bin\kinit.exe C:\NXP\S32DS_Power_v2.1\jre\bin\klist.exe C:\NXP\S32DS_Power_v2.1\jre\bin\ktab.exe C:\NXP\S32DS_Power_v2.1\jre\bin\lcms.dll C:\NXP\S32DS_Power_v2.1\jre\bin\management.dll C:\NXP\S32DS_Power_v2.1\jre\bin\mlib_image.dll C:\NXP\S32DS_Power_v2.1\jre\bin\msvcp140.dll C:\NXP\S32DS_Power_v2.1\jre\bin\msvcr100.dll C:\NXP\S32DS_Power_v2.1\jre\bin\net.dll C:\NXP\S32DS_Power_v2.1\jre\bin\nio.dll C:\NXP\S32DS_Power_v2.1\jre\bin\npt.dll C:\NXP\S32DS_Power_v2.1\jre\bin\orbd.exe C:\NXP\S32DS_Power_v2.1\jre\bin\pack200.exe C:\NXP\S32DS_Power_v2.1\jre\bin\plugin2 C:\NXP\S32DS_Power_v2.1\jre\bin\plugin2\msvcr100.dll C:\NXP\S32DS_Power_v2.1\jre\bin\plugin2\npjp2.dll C:\NXP\S32DS_Power_v2.1\jre\bin\policytool.exe C:\NXP\S32DS_Power_v2.1\jre\bin\prism_common.dll C:\NXP\S32DS_Power_v2.1\jre\bin\prism_d3d.dll C:\NXP\S32DS_Power_v2.1\jre\bin\prism_sw.dll C:\NXP\S32DS_Power_v2.1\jre\bin\resource.dll C:\NXP\S32DS_Power_v2.1\jre\bin\rmid.exe C:\NXP\S32DS_Power_v2.1\jre\bin\rmiregistry.exe C:\NXP\S32DS_Power_v2.1\jre\bin\servertool.exe C:\NXP\S32DS_Power_v2.1\jre\bin\splashscreen.dll C:\NXP\S32DS_Power_v2.1\jre\bin\ssv.dll C:\NXP\S32DS_Power_v2.1\jre\bin\ssvagent.exe C:\NXP\S32DS_Power_v2.1\jre\bin\sunec.dll C:\NXP\S32DS_Power_v2.1\jre\bin\sunmscapi.dll C:\NXP\S32DS_Power_v2.1\jre\bin\t2k.dll C:\NXP\S32DS_Power_v2.1\jre\bin\tnameserv.exe C:\NXP\S32DS_Power_v2.1\jre\bin\ucrtbase.dll C:\NXP\S32DS_Power_v2.1\jre\bin\unpack.dll C:\NXP\S32DS_Power_v2.1\jre\bin\unpack200.exe C:\NXP\S32DS_Power_v2.1\jre\bin\vcruntime140.dll C:\NXP\S32DS_Power_v2.1\jre\bin\verify.dll C:\NXP\S32DS_Power_v2.1\jre\bin\w2k_lsa_auth.dll C:\NXP\S32DS_Power_v2.1\jre\bin\WindowsAccessBridge-32.dll C:\NXP\S32DS_Power_v2.1\jre\bin\WindowsAccessBridge.dll C:\NXP\S32DS_Power_v2.1\jre\bin\wsdetect.dll C:\NXP\S32DS_Power_v2.1\jre\bin\zip.dll C:\NXP\S32DS_Power_v2.1\jre\版权所有 C:\NXP\S32DS_Power_v2.1\jre\lib C:\NXP\S32DS_Power_v2.1\jre\lib\accessibility.properties C:\NXP\S32DS_Power_v2.1\jre\lib\calendars.properties C:\NXP\S32DS_Power_v2.1\jre\lib\charsets.jar C:\NXP\S32DS_Power_v2.1\jre\lib\classlist C:\NXP\S32DS_Power_v2.1\jre\lib\cmm C:\NXP\S32DS_Power_v2.1\jre\lib\cmm\CIEXYZ.pf C:\NXP\S32DS_Power_v2.1\jre\lib\cmm\GRAY.pf C:\NXP\S32DS_Power_v2.1\jre\lib\cmm\LINEAR_RGB.pf C:\NXP\S32DS_Power_v2.1\jre\lib\cmm\PYCC.pf C:\NXP\S32DS_Power_v2.1\jre\lib\cmm\sRGB.pf C:\NXP\S32DS_Power_v2.1\jre\lib\content-types.properties C:\NXP\S32DS_Power_v2.1\jre\lib\currency.data C:\NXP\S32DS_Power_v2.1\jre\lib\deploy C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\ffjcext.zip C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\messages.properties C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\messages_de.properties C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\messages_es.properties C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\messages_fr.properties C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\messages_it.properties C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\messages_ja.properties C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\messages_ko.properties C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\messages_pt_BR.properties C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\messages_sv.properties C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\messages_zh_CN.properties C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\messages_zh_HK.properties C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\messages_zh_TW.properties C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\splash.gif C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\[email protected] C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\splash_11-lic.gif C:\NXP\S32DS_Power_v2.1\jre\lib\deploy\[email protected] C:\NXP\S32DS_Power_v2.1\jre\lib\deploy.jar C:\NXP\S32DS_Power_v2.1\jre\lib\ext C:\NXP\S32DS_Power_v2.1\jre\lib\ext\access-bridge-32.jar C:\NXP\S32DS_Power_v2.1\jre\lib\ext\access-bridge.jar C:\NXP\S32DS_Power_v2.1\jre\lib\ext\cldrdata.jar C:\NXP\S32DS_Power_v2.1\jre\lib\ext\dnsns.jar C:\NXP\S32DS_Power_v2.1\jre\lib\ext\jaccess.jar C:\NXP\S32DS_Power_v2.1\jre\lib\ext\jfxrt.jar C:\NXP\S32DS_Power_v2.1\jre\lib\ext\localedata.jar C:\NXP\S32DS_Power_v2.1\jre\lib\ext\meta-index C:\NXP\S32DS_Power_v2.1\jre\lib\ext\nashorn.jar C:\NXP\S32DS_Power_v2.1\jre\lib\ext\sunec.jar C:\NXP\S32DS_Power_v2.1\jre\lib\ext\sunjce_provider.jar C:\NXP\S32DS_Power_v2.1\jre\lib\ext\sunmscapi.jar C:\NXP\S32DS_Power_v2.1\jre\lib\ext\sunpkcs11.jar C:\NXP\S32DS_Power_v2.1\jre\lib\ext\zipfs.jar C:\NXP\S32DS_Power_v2.1\jre\lib\flavormap.properties C:\NXP\S32DS_Power_v2.1\jre\lib\fontconfig.bfc C:\NXP\S32DS_Power_v2.1\jre\lib\fontconfig.properties.src C:\NXP\S32DS_Power_v2.1\jre\lib\fonts C:\NXP\S32DS_Power_v2.1\jre\lib\fonts\LucidaBrightDemiBold.ttf C:\NXP\S32DS_Power_v2.1\jre\lib\fonts\LucidaBrightDemiItalic.ttf C:\NXP\S32DS_Power_v2.1\jre\lib\fonts\LucidaBrightItalic.ttf C:\NXP\S32DS_Power_v2.1\jre\lib\fonts\LucidaBrightRegular.ttf C:\NXP\S32DS_Power_v2.1\jre\lib\fonts\LucidaSansDemiBold.ttf C:\NXP\S32DS_Power_v2.1\jre\lib\fonts\LucidaSansRegular.ttf C:\NXP\S32DS_Power_v2.1\jre\lib\fonts\LucidaTypewriterBold.ttf C:\NXP\S32DS_Power_v2.1\jre\lib\fonts\LucidaTypewriterRegular.ttf C:\NXP\S32DS_Power_v2.1\jre\lib\hijrah-config-umalqura.properties C:\NXP\S32DS_Power_v2.1\jre\lib\i386 C:\NXP\S32DS_Power_v2.1\jre\lib\i386\jvm.cfg C:\NXP\S32DS_Power_v2.1\jre\lib\images C:\NXP\S32DS_Power_v2.1\jre\lib\images\cursors C:\NXP\S32DS_Power_v2.1\jre\lib\images\cursors\cursors.properties C:\NXP\S32DS_Power_v2.1\jre\lib\images\cursors\invalid32x32.gif C:\NXP\S32DS_Power_v2.1\jre\lib\images\cursors\win32_CopyDrop32x32.gif C:\NXP\S32DS_Power_v2.1\jre\lib\images\cursors\win32_CopyNoDrop32x32.gif C:\NXP\S32DS_Power_v2.1\jre\lib\images\cursors\win32_LinkDrop32x32.gif C:\NXP\S32DS_Power_v2.1\jre\lib\images\cursors\win32_LinkNoDrop32x32.gif C:\NXP\S32DS_Power_v2.1\jre\lib\images\cursors\win32_MoveDrop32x32.gif C:\NXP\S32DS_Power_v2.1\jre\lib\images\cursors\win32_MoveNoDrop32x32.gif C:\NXP\S32DS_Power_v2.1\jre\lib\javafx.properties C:\NXP\S32DS_Power_v2.1\jre\lib\javaws.jar C:\NXP\S32DS_Power_v2.1\jre\lib\jce.jar C:\NXP\S32DS_Power_v2.1\jre\lib\jfr C:\NXP\S32DS_Power_v2.1\jre\lib\jfr\default.jfc C:\NXP\S32DS_Power_v2.1\jre\lib\jfr\profile.jfc C:\NXP\S32DS_Power_v2.1\jre\lib\jfr.jar C:\NXP\S32DS_Power_v2.1\jre\lib\jfxswt.jar C:\NXP\S32DS_Power_v2.1\jre\lib\jsse.jar C:\NXP\S32DS_Power_v2.1\jre\lib\jvm.hprof.txt C:\NXP\S32DS_Power_v2.1\jre\lib\logging.properties C:\NXP\S32DS_Power_v2.1\jre\lib\management C:\NXP\S32DS_Power_v2.1\jre\lib\management\jmxremote.access C:\NXP\S32DS_Power_v2.1\jre\lib\management\jmxremote.password.template C:\NXP\S32DS_Power_v2.1\jre\lib\management\management.properties C:\NXP\S32DS_Power_v2.1\jre\lib\management\snmp.acl.template C:\NXP\S32DS_Power_v2.1\jre\lib\management-agent.jar C:\NXP\S32DS_Power_v2.1\jre\lib\meta-index C:\NXP\S32DS_Power_v2.1\jre\lib\net.properties C:\NXP\S32DS_Power_v2.1\jre\lib\plugin.jar C:\NXP\S32DS_Power_v2.1\jre\lib\psfont.properties.ja C:\NXP\S32DS_Power_v2.1\jre\lib\psfontj2d.properties C:\NXP\S32DS_Power_v2.1\jre\lib\resources.jar C:\NXP\S32DS_Power_v2.1\jre\lib\rt.jar C:\NXP\S32DS_Power_v2.1\jre\lib\security C:\NXP\S32DS_Power_v2.1\jre\lib\security\blacklist C:\NXP\S32DS_Power_v2.1\jre\lib\security\blacklisted.certs C:\NXP\S32DS_Power_v2.1\jre\lib\security\cacerts C:\NXP\S32DS_Power_v2.1\jre\lib\security\java.policy C:\NXP\S32DS_Power_v2.1\jre\lib\security\java.security C:\NXP\S32DS_Power_v2.1\jre\lib\security\javaws.policy C:\NXP\S32DS_Power_v2.1\jre\lib\security\policy C:\NXP\S32DS_Power_v2.1\jre\lib\security\policy\limited C:\NXP\S32DS_Power_v2.1\jre\lib\security\policy\limited\local_policy.jar C:\NXP\S32DS_Power_v2.1\jre\lib\security\policy\limited\US_export_policy.jar C:\NXP\S32DS_Power_v2.1\jre\lib\security\policy\unlimited C:\NXP\S32DS_Power_v2.1\jre\lib\security\policy\unlimited\local_policy.jar C:\NXP\S32DS_Power_v2.1\jre\lib\security\policy\unlimited\US_export_policy.jar C:\NXP\S32DS_Power_v2.1\jre\lib\security\trusted.libraries C:\NXP\S32DS_Power_v2.1\jre\lib\sound.properties C:\NXP\S32DS_Power_v2.1\jre\lib\tzdb.dat C:\NXP\S32DS_Power_v2.1\jre\lib\tzmappings C:\NXP\S32DS_Power_v2.1\jre\LICENSE C:\NXP\S32DS_Power_v2.1\jre\README.txt C:\NXP\S32DS_Power_v2.1\jre\release C:\NXP\S32DS_Power_v2.1\jre\THIRDPARTYLICENSEREADME-JAVAFX.txt C:\NXP\S32DS_Power_v2.1\jre\THIRDPARTYLICENSEREADME.txt C:\NXP\S32DS_Power_v2.1\jre\Welcome.html C:\NXP\S32DS_Power_v2.1\_S32电源架构设计工作室 2.1 版_安装 C:\NXP\S32DS_Power_v2.1\_S32Power Architecture 设计工作室 2.1 版_installation\.com.zerog.registry.xml C:\NXP\S32DS_Power_v2.1\_S32Design Studio for Power Architecture Version 2.1_installation\InstallScript.iap_xml C:\NXP\S32DS_Power_v2.1\_S32Design Studio for Power Architecture Version 2.1_installation\Logs C:\NXP\S32DS_Power_v2.1\_S32Design Studio for Power Architecture Version 2.1_installation\Logs\S32_Design_Studio_for_Power_Architecture_Version_2.1_Install_10_19_2026_16_45_25.log C:\NXP\S32DS_Power_v2.1\_S32Design Studio for Power Architecture Version 2.1_installation\resource C:\NXP\S32DS_Power_v2.1\_S32Power Architecture 设计工作室 2.1 版_installation\resource\iawin32.dll C:\NXP\S32DS_Power_v2.1\_S32Power Architecture 设计工作室 2.1 版_installation\resource\invoker.exe C:\NXP\S32DS_Power_v2.1\_S32Design Studio for Power Architecture Version 2.1_installation\resource\remove.exe C:\NXP\S32DS_Power_v2.1\_S32Power Architecture 设计工作室 2.1 版_安装\资源\win64_32_x64.exe C:\NXP\S32DS_Power_v2.1\_S32Design Studio for Power Architecture Version 2.1_installation\uninstaller.jar Re: S32DS_Power_Win32_v2.1 install fail. rollbacked 你好, 根据安装日志,故障似乎与管理员权限或磁盘空间无关。安装过程顺利完成文件提取、必备组件安装和许可设置阶段。但是,在许可证激活步骤中失败了,许可证元器件在本地库 cll_app.dll 中崩溃。这会导致安装程序触发信号整个安装的回滚。 作为初步故障排除步骤: 1. 从系统中删除任何现有的 S32DS 或 FlexNet/FNP 许可服务安装。 2. 删除或备份 FlexNet 许可目录的内容: C:\ProgramData\FLEXnet 3. 暂时禁用防病毒软件或终端保护软件。 4. 从较短的本地路径(例如 C:\Temp)运行安装程序。 请提供 hs_err_pid*.log 文件的内容如果问题仍然存在,请提供文件,以便我们进一步分析崩溃原因。 顺祝商祺! Peter Re: S32DS_Power_Win32_v2.1 install fail. rollbacked 暂时禁用杀毒软件后安装成功
View full article
KW45 车载蓝牙模块——即插即用型?KiCad? 亲爱的社区成员们: 由于我对蓝牙无线电功能域经验不足,所以想请教各位。 我们的项目需要蓝牙连接。KW45 评估板已用于 POC 和早期测试。 现在我们想把KW45直接加入到我们的板上。使用 KiCad 无法访问 NXP 参考设计。而通读文档让我谦卑地缩小到蚂蚁的体型。或者更小。 看到论坛上这么多帖子,我想知道是否有人可以分享一个现成的设计供我们使用?我们使用稳定的3.3V电源,并通过UART进行通信。 这是一个汽车改装应用,应该尽可能小巧。 这就是我们所需要的一切。 顺祝商祺! 迈克尔 KW45 Re: KW45 automotive bluetooth - drop in module? KiCad? 你好@Orbiter , 请注意,与较新的设备相比,KW45 的功能可能较少。您可能还想考虑KW47 系列,它提供了多项增强功能,包括更大的内存容量、运行频率高达 64 MHz 的专用的 CM33 无线电核心、2.4 GHz 低功耗蓝牙核心版本 6.x 以及支持蓝牙信道探测。此外,KW47 与 KW45 引脚兼容,这可以简化迁移工作。有关功能差异和迁移注意事项的更多信息,请参阅AN14796 。 我们仅提供KW45-EVK 设计文件,以及这篇社区帖子,其中概述了使用 KW45 一次性正确构建 PCB 的最佳方法。 BR 哈比卜 Re: KW45 automotive bluetooth - drop in module? KiCad? 我知道这对我们来说太难了。我们将转向采用“即插即用”的蓝牙模块SoC。 Re: KW45 automotive bluetooth - drop in module? KiCad? 你好@Orbiter , 如果您有兴趣,可以联系我们的合作伙伴,他们可以帮助您开发适用于汽车环境的解决方案。 此外,您还可以咨询我们的合作伙伴提供的Wi-Fi ® + Bluetooth ® + 802.15.4 合作伙伴模块,其中一些模块也可能适用于汽车环境。但是,这些模块需要主机处理器。如果您对此选项感兴趣,请随时提供更多关于您申请的信息,以便我能指导您了解可行的方案。 BR 哈比卜
View full article
MIMXRT1176DVMAB 的最小系统设计指南 尊敬的恩智浦技术支持团队: 我正在根据以下内容设计定制PCB: MIMXRT1176DVMAB 一款基于 Quectel 的网络产品 RG255CGL00AB-4M2-SGASA_A 调制解调器。我们的第一个版本运行良好,现在我们正在使用 i.MX RT1176 开发下一个版本。 MCU 将位于 Mac 和 Quectel 调制解调器之间,提供面向 Mac 的 USB 网络接口并转发互联网流量。它还可以处理调制解调器的启动和恢复、设备识别、流量限制和使用情况统计、诊断、安全固件更新以及远程车队管理,而无需配套应用程序。 请问您能否提供或指引我联系以下机构: 简明扼要 最小系统硬件设计指南 涵盖该部件的电源、时钟、启动配置、复位、外部闪存和编程/调试接口。 这 原理图符号和PCB封装CAD文件,最好是KiCad兼容格式。 任何与在定制PCB上实现MCU相关的参考原理图或应用笔记。 EVKB 原理图包含许多我们最初设计中不需要的外围设备,因此,一份专注于基本电路的参考资料将特别有帮助。 感谢您抽出时间提供帮助。 Re: Minimum-System Design Guide for MIMXRT1176DVMAB 嗨@Onyeka , 我建议先从MIMXRT1160/1170 处理器的硬件开发指南入手,因为它提供了有关板布局建议和设计清单的信息。此外,如果某些引脚将不使用,该指南还包含一个章节,其中提供了处理未使用引脚的建议。 关于 CAD 模型,您可以在i.MX RT1170产品页面的“购买/参数化”部分搜索特定零件编号来找到它们。 此致 巴勃罗
View full article
Minimum-System Design Guide for MIMXRT1176DVMAB Dear NXP Support Team, I am designing a custom PCB based on the MIMXRT1176DVMAB for a networking product built around the Quectel RG255CGL00AB-4M2-SGASA_A modem. Our first version is working well, and we are now developing the next version with the i.MX RT1176. The MCU will sit between the Mac and the Quectel modem, providing the Mac-facing USB network interface and forwarding internet traffic. It will also handle modem startup and recovery, device identity, traffic throttling and usage accounting, diagnostics, secure firmware updates, and remote fleet management, without requiring a companion app. Could you please provide or direct me to: A concise minimum-system hardware design guide covering power supplies, clocks, boot configuration, reset, external flash, and programming/debug interfaces for this exact part. The schematic symbol and PCB footprint CAD files, preferably in KiCad-compatible format. Any relevant reference schematics or application notes for implementing the MCU on a custom PCB. The EVKB schematics include many peripherals that are unnecessary for our initial design, so a focused reference for the essential circuitry would be particularly helpful. Thank you for your time and assistance. Re: Minimum-System Design Guide for MIMXRT1176DVMAB Hi @Onyeka, I would recommend starting with the Hardware Development Guide for the MIMXRT1160/1170 Processor, as it provides information about board layout recommendations and design checklists. Additionally, if some pins will be unused, the guide includes a section with recommendations for handling unused pins. Regarding CAD models, you can find them on the i.MX RT1170 product page by searching for the specific part number in the Buy/Parametrics section. Best Regards Pablo
View full article
[PN7221][Android16] カードを繰り返し素早くスワイプすると、NFCが使用できなくなる場合があります。 以下の2つのNFCファームウェアバージョンをテストしたところ、どちらも同じ問題が再現されました。 バージョン1:3.2.4 バージョン2:3.2.6 ログは添付ファイルとしてアップロードされています。問題が発生した場合は、HALを強制終了することで正常な動作に戻ります。 Re: [PN7221][Android16] 反复快速刷卡,概率出现nfc无法使用 バージョン03.02.06にアップグレードした後でテストしてみましたが、問題は依然として再現します。 Re: [PN7221][Android16] 反复快速刷卡,概率出现nfc无法使用 こんにちは、 @zhangkai さん。 ログにはFW: 03.02.C4と表示されていますが、これは一時的なバージョンです。FWを最新バージョン03.02.06にアップグレードしてください。 (nfc-NXPNFCC_FW/InfraFW/pn7220 at master · NXP/nfc-NXPNFCC_FW · GitHub) Re: [PN7221][Android16] 反复快速刷卡,概率出现nfc无法使用 クライアントは、3回の正常な操作の後、NFCの不具合が発生しました。ログには、カードを素早くスワイプした際に発生したフリーズと同様の問題が記録されています。ログファイル「20261020_194057_F802E693J0065.zip」を参照してください。症状としては、画面がオフになった後にNFCが動作しなくなることが挙げられます。 カードを素早く繰り返しスワイプするのは、私がこの問題を再現するために用いている方法です。 Re: [PN7221][Android16] 反复快速刷卡,概率出现nfc无法使用 こんにちは ご提供いただいたログによると、すべてタイムアウトエラーが発生しています。したがって、現在の状況はカード読み取り間隔が短すぎることが原因です。カードを頻繁に読み取ることはお勧めしません。 Re: [PN7221][Android16] 反复快速刷卡,概率出现nfc无法使用 ゆっくりとページを更新していますが、今のところ問題は再現できていません。 Re: [PN7221][Android16] 反复快速刷卡,概率出现nfc无法使用 最速の更新速度は約2回/秒、平均更新速度は約1回/秒です。 Re: [PN7221][Android16] 反复快速刷卡,概率出现nfc无法使用 こんにちは、 @zhangkai さん。 どうやらカードが詰まってしまい、復旧できずに再度カードを読み取ろうとしているようです。「繰り返し、素早く」とは、おおよそどのくらいの頻度でしょうか?速度が遅くなれば、この問題は解消されるでしょうか? Re: [PN7221][Android16] 反复快速刷卡,概率出现nfc无法使用 こんにちは、 @zhangkai さん。 パッチはメールで送信してください! BR ケリー Re: [PN7221][Android16] 反复快速刷卡,概率出现nfc无法使用 20分間繰り返しカードをスワイプしてみましたが、問題はまだ再現していません。 Re: [PN7221][Android16] 反复快速刷卡,概率出现nfc无法使用 カード1を先にスワイプしてからカード2をスワイプすると、システムがフリーズします。この問題はパッチとは無関係であることが確認されており、パッチを適用する前にも同様の現象が発生していました。 Re: [PN7221][Android16] 反复快速刷卡,概率出现nfc无法使用 メールパッチをインポートした後でも、問題は再現可能であり、以前よりもさらに速く再現します。以下の手順でテストすれば、確実に再現します。 1. まずカードをスワイプしてください。 2. カード2をもう一度スワイプすると、システムがフリーズします。 回复: [PN7221][Android16] 反复快速刷卡,概率出现nfc无法使用 こんにちは。この件に関して何か新しい進展はありましたか?どうやら問題は主にSIM 1とSIM 2を交互に切り替える際に発生し、それが原因でフリーズするようです。
View full article
EasyEVSE EVerest MPU 构建 — SE05x 中间件版本说明 使用 i.MX93 服务处理板设置 NXP EasyEVSE 平台。 我正在按照 EasyEVSE EVerest MPU 的说明操作,并使用以下清单文件: 分支:版本/everest-mpu-2.0 清单文件:imx-6.12.20-2.0.0_everest.xml 目标图像:imx-image-everest meta-nxp-everest-mpu README 指定 EdgeLock SE05x Plug & Trust 中间件版本为 04.07.01 (se05x_mw_v04.07.01.zip),但我目前只能在 NXP 下载网站上找到版本 04.08.01 (se05x_mw_v04.08.01.zip)。 版本/everest-mpu-2.0 是否支持中间件 04.08.01清单 和 imx-6.12.20-2.0.0_everest.xml? 具体应该更新哪个配方或配置文件?需要做哪些更改? 如果需要,中间件 04.07.01 是否仍然可以通过官方下载链接获取? Re: EasyEVSE EVerest MPU build — SE05x middleware version clarification 嗨@ChargeMeMaybe README 文件仅将 04.07.01 列为先决条件;04.x 系列版本之间没有重大的架构变化。您需要修改 bb 文件以使用 04.08.01 版本。 此致, 志明
View full article