Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
LS1046A 的 TA_PROG_SFP 引脚始终连接至 1.8V 电源 你好 我使用的是 LS1046A。 从清单中,我了解到 “在安全启动编程期间只能提供 1.8 V 的电压。正常运行时,需要通过一个电阻器将该引脚下拉。 但由于某些原因,在我们的设计中,LS1046A 的 TA_PROG_SFP 引脚始终连接到 1.8V 电源。 请问这种设计有什么风险? 谢谢! Re: The TA_PROG_SFP pin of the LS1046A is always connected to a 1.8V power supply 你好@陈坤 希望这篇文章对你有所帮助、 不客气,很高兴能帮上忙。 如果还有什么需要我帮忙的,请随时联系我。 祝你愉快 顺祝商祺! Hector Villarruel S Re: The TA_PROG_SFP pin of the LS1046A is always connected to a 1.8V power supply 嗨,赫克托、 感谢您的回复。 Re: The TA_PROG_SFP pin of the LS1046A is always connected to a 1.8V power supply 你好@陈坤 希望这篇文章对你有所帮助、 关于您的问题 这种行为的后果将是熔丝会熔断,从而覆盖与之前相同的信息,并且无法再次对其进行编程。 请参阅第 4 节网络安全熔丝处理器 QorIQ LS1046A,LS1026A 数据表,修订版 4,2020 年 6 月中的以下信息。 要对 SFP 熔丝进行编程,用户需要在每次上电排序时为 TA_PROG_SFP 引脚提供 1.8 伏的电压。TA_PROG_SFP 只能在熔丝 编程周期内通电,每个设备限制为六个熔丝编程周期。所有其他 时间,TA_PROG_SFP 都应连接至 GND。 升高和降低 TA_PROG_SFP 的顺序要求如图 9 所示。为确保设备可靠性, 必须在表 4 中推荐的熔丝编程 温度范围内进行熔丝编程。 祝你愉快 BR、 赫克托-比利亚鲁埃尔
View full article
Synchronizing multiple EMIOS instances Is it possible to synchronize multiple EMIOS instances together? Currently, I am running EMIOS 1 and EMIOS 0 together to generate some PWMs, but there is a phase difference,which is variable and i cannot get rid of. From the following answer: https://community.nxp.com/t5/S32K/Synchronizing-eMIOS-instances/td-p/1423858, I see GTBE bit sets it for one emios instance, which I have done and works well. Can I do this somehow across multiple instances? Re: Synchronizing multiple EMIOS instances Hi@RChatterjee Sorry for the first reply and I made some modification according to the demo your provided: 1.Clean all eMIOSn->MCR.GTBE at beginning. 2.Enable eMIOSn->MCR.GTBE after init eMIOS_MCL IP_EMIOS_1->MCR |= eMIOS_MCR_GTBE_MASK; 3.Test Result:  PTD20 & PTB17 Re: Synchronizing multiple EMIOS instances Hi @Senlent , This is my config. I have it enabled for EMIOS 0 and EMIOS 1. However, the phase difference exists. Should this not happen then? PFA design files. The phase difference is between any of the emios 0 and emios 1 channels. Regards, Rounak Chatterjee. Re: Synchronizing multiple EMIOS instances Hi@RChatterjee yes,it can be done by enable the emios_mcl->globatimebase feature.
View full article
S32DS Licence Problem Hello, I am not able to reinstall S32DS due to a licence problem. (Fullfillment ID 197733417) I cannot return the licence or remove it from my account. I do not have S32DS currently installed. Also, what is the correct procedure so that this does not happen again? Thank you! Activation | Installation | Licensing | Installer Download Re: S32DS Licence Problem Hi @greyes  I think you are confused, the licenses shown are not for S32 Design Studio for the S32 platform, they are S32K3 software licenses. I cannot determine which one it is, but if you press the "Details" button it will send you to a page that provides all the details of the license. You can find the S32DS activation code directly on the IDE page: S32 Design Studio 3.5 > S32 Design Studio for S32 Platform v.3.5 > License Keys tab.  BR, VaneB
View full article
S32DS PA V2.1 install failed Hi team, Today, I found that the S32DS PA V2.1 installed on my computer wouldn't start properly, which will quit automatically just few seconds after launch, try to setup another workspace still same. So I uninstall it and try to reinstall again, but the installation program will roll back few seconds after I input the activation codes, I can install it on anther computer successfully, so I guess the activation code is ok. Anyone know how to solve this? Install log file show below errors: ..... Summary ------- Installation: Unsuccessful. 62 Successes 24 Warnings 1 NonFatalErrors 1 FatalErrors ..... S32 Design Studio for Power Architecture Version 2.1(Install All Uninstaller Components) Status: ERROR Additional Notes: ERROR - Error writing LaunchAnywhere components (Access Denied) ..... RepositoryManager: Trying fallback repository location... # # INSTALLING VM: d:\NXP\S32DS_Power_v2.1\jre # System's temporary directory = C:\Users\shinlitaike08\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=0x611a8c19, pid=3644, tid=0x00001db0 # # 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 # Re: S32DS PA V2.1 install failed Check File Permissions: Verify that your user account has full read/write permissions to the installation directory and temporary folders. Right-click on the installation directory (e.g., C:\NXP\S32DS_Power_v2.1) and check its security settings. Ensure your user account has "Full control." Re: S32DS PA V2.1 install failed I have found the solution for me, and it was related to permissions on the installation folder. I give the proper permissions to the installation folder, and then I was able to install the program. Re: S32DS PA V2.1 install failed Yes, I did it.  Re: S32DS PA V2.1 install failed Hi, Can you make sure you run the installer as Administratior? Stan Re: S32DS PA V2.1 install failed Hi I have the same issue,  I have attached the log I got. Re: S32DS PA V2.1 install failed Hi, Could you possibly try to re-install S32 Design Studio for PA again. Please use your existing activation code. We've extended the license. If it still does not work please let us know. Stan Re: S32DS PA V2.1 install failed Did you resolve it? Re: S32DS PA V2.1 install failed Hello, I've moved your post to correct box. Best regards, Peter
View full article
android 无法创建 Android 目录路径 嗨,大家好。 在 Android 移植过程中,我出于以下原因提出请求。 操作系统:安卓 13 CPU:imx8mini 在安卓系统上插入 SD 卡或 USB 存储器时,会自动创建以下目录 - Environment.DIRECTORY_ALARMS:保存警报音频文件(/mnt/sdcard/Alarms) - Environment.DIRECTORY_DCIM:保存相机拍摄的照片(/mnt/sdcard/DCIM) - Environment.DIRECTORY_DOWNLOADS:保存下载的文件 (/mnt/sdcard/Download) - Environment.DIRECTORY_MUSIC : 音乐 (/mnt/sdcard/Music) - Environment.DIRECTORY_MOVIES : 영상 파일 저장 (/mnt/sdcard/Movies) - Environment.DIRECTORY_NOTIFICATORS:存储用作通知声音的音频文件 (/mnt/sdcard/Notifications) - Environment.DIRECTORY_PICTURES : 그림 파일 저장 (/mnt/sdcard/Pictures) - Environment.DIRECTORY_PODCASTS:保存播客文件 (/mnt/sdcard/Podcasts) 是否有办法防止该目录发生这种情况 Re: android want not create Android Directory Path 你好 目录由 android 创建,这是必要的,但您可以使用 android studio 进行更改,并更改权限和加载器。 此致
View full article
澄清 iMX RT1176 的 OSC 24 MHz 模式 你能解释一下如何为外部 24 MHz 参考时钟配置 OSC_24M_CTRL 字段吗?不清楚以下寄存器位是什么: OSC_EN - 是启用引脚连接外部时钟源,还是启用内部 24 MHz RC? BYPASS_EN - 0 表示外部晶体,1 表示外部振荡器?还是其他方式? BYPASS_CLK - RM 中没有说明 0 和 1 值的含义。 与此同时,SDK 的时钟工具实际上显示了"OSC 模式的 3 个值" : 据我所知,3 种可用的 OSC 模式是这样影响 OSC_24M_CTRL 寄存器的: OSC 模式 BYPASS_EN BYPASS_CLK 时钟 工具说明 扩展晶体 24 MHz 0 0 外部晶体 24 MHz 扩展旁路时钟模式 1 0 外部晶体连接到 XTALI 时钟输入端 外部参考时钟 0 1 外部参考时钟连接到 XTALI 时钟输入 这三种模式有什么区别?为什么有三种模式(我只能想象出两种:被动 XTAL 连接或主动振荡器时钟连接器)。 是否可以在内部 RC 振荡器和外部时钟之间改变 OSC 24MHz 频率?(例如,根据是否存在可靠的时钟源,我希望回落到内部 24 MHz)。 Re: Clarify the OSC 24 MHz modes for iMX RT1176 你好,@aberger、 我检查了内部 RC 振荡器 48 MHz(除以 2)作为 24 MHz 时钟源的使用情况。这个 48 MHz 内部 RC 振荡器(除以 2)可直接用作 CCM 时钟根的时钟源,参见下面的时钟图: 它可用于外设和 CPU 内核,但内部 RC 振荡器不能用于 PLL,因为在时钟工具的时钟图中可以看到它。内部 RC 振荡器不够精确和稳定,不能用作 PLL 的时钟源。 所有 PLL 唯一可能的时钟源是外部晶体或外部振荡器。请忽略时钟工具中有关 MIMXRT1176 MCU 的 OSC 24 MHz 时钟元素的混乱评论(将被删除)。 因此,如果要使用内部 48 MHz RC 振荡器,必须禁用所有 PLL,并在 CCM(时钟根)中选择内部 48 MHz RC 振荡器时钟源。但我们仍然建议使用外部振荡器,以提高时钟的稳定性。 顺祝商祺! 马雷克-诺伊齐尔 Re: Clarify the OSC 24 MHz modes for iMX RT1176 你好,@aberger、 我已经查看了 i.MX RT1176 参考手册,其中有一份关于使用备用 RC 48MHz 内部参考时钟作为24 MHz 时钟源而不是外部 24 MHz 时钟源的声明。但是我不确定MCU是否可以在没有外部参考时钟的情况下完全工作(例如,USB需要稳定的时钟源,PLL需要稳定的24 MHz参考时钟)。此外,i.MX RT1176 数据表还规定了外部参考时钟的用法,它可以是晶体振荡器,也可以是外部振荡器。内部 RC 48 MHz 的修整频率为 +-2% ,并非精确的时钟源。 我将联系负责的设计团队,核实 i.MX RT1170 参考手册中的陈述以及推荐的 PLL 和其他内部模块的 24 MHz 时钟源。 顺祝商祺! 马雷克-诺伊齐尔 Re: Clarify the OSC 24 MHz modes for iMX RT1176 嗯,时钟工具似乎暗示 OSC 24 MHz 可以是"内部 RC 振荡器" 。 同时,RM 将 24 MHz 称为芯片上可用的晶振: 不管是 RC 振荡器还是 XTAL 振荡器,是否有可用的 24 MHz"片上" (即没有与 XTAL 或参考时钟的外部连接)? 如果我将时钟工具设置为"OSC 24 MHz disabled" ,XTALI 和 XTALO 引脚就会被禁用,但振荡器模块似乎仍有 24 MHz 信号输出(这表明 24 MHz 信号源在芯片上)。只有当我点击 OSC 24MHz 并选择"断开连接" 时,OSC 24MHz 块才会被标记为非活动。 Re: Clarify the OSC 24 MHz modes for iMX RT1176 你好@aberger 非常感谢您关注我们的产品并使用我们的社区。 Q1: OSC_EN - 是启用引脚连接外部时钟源,还是启用内部 24 MHz RC? A1:该位表示启用外部 24MHz XTALOSC。 Q2: BYPASS_EN - 0 表示外部晶体,1 表示外部振荡器?还是其他方式? A2: BYPASS_EN - 1,表示外部时钟源直接输入 XTALI 引脚。 问题 3: BYPASS_CLK - RM 中没有说明 0 和 1 值的含义。 答 3:我与恩智浦相关内部团队确认,BYPASS_CLK 信息不正确。在下一个发布的 RT1170RM 版本中,它将更改为 “保留”,因为此位没有功能。 问题 4: 是否可以在内部 RC 振荡器和外部时钟之间切换 OSC 24MHz?(例如,根据是否存在可靠的时钟源,我希望回落到内部 24 MHz)。 答 4:RT1170 系列芯片内部没有 24MHz RC 振荡器,它包含四个 RC 振荡器 -48MHz、32KHz、16MHz 和 400MHz。 希望它能帮到你。 如果您还有疑问,请告诉我。 敬上 MayLiu
View full article
s32k344 示例代码版本错误 在 S32 设计工作室中,我正在尝试版本示例代码。 但是大多数示例代码都显示版本错误。 在版本之前我必须做点什么吗? 1. adc_example_S32K344 2.mcu_example_S32K344 =============================== Re: S32k344 example code build error 亲爱的@Robin_Shen 按照你的建议,我卸载并重新安装了所有代码包都包含 S32D。 我成功地版本了代码。 谢谢! Re: S32k344 example code build error 您是在创建新项目时遇到该问题,还是在按照我视频中的所有步骤操作后仍遇到该问题? 您能在另一台电脑上重现该问题吗? 请尝试卸载 S32DS v3.6.1 然后重新安装 S32DS v3.6.1 + s32K3_S32 M27x 实时驱动程序 ASR R21-11 版本 6.0. 0。 Re: S32k344 example code build error 亲爱的@Robin_Shen 我试过用你上传的视频复制,但失败了(结果一样)。 Re: S32k344 example code build error 我不清楚您是如何导入 RTD 示例的。请参考视频中的步骤。我在构建时没有遇到任何错误。 (在 “我的视频” 中查看) Re: S32k344 example code build error 亲爱的@Robin_Shen 感谢您的支持。 [Test 1] 我尝试了 -> (但什么也没改),并点击 ,但遇到了另一个错误。 [Test 2] 我尝试了 -> (添加 [adc] 驱动程序)并点击 ,但遇到了另一个错误。 你能帮帮我吗? [测试 1] - 不做任何更改 == 版本结果。错误 ===== [测试 2] - 添加 [adc] 驱动程序 == 版本结果。错误 ===== Re: S32k344 example code build error 嗨,郑奎 请单击 description.txt 中提到的 更新代码 按钮: 3.生成、构建和运行示例应用程序 3.1 生成 S32 配置 在运行示例之前,需要生成配置。首先转到 S32 DS 中的 “项目资源管理器视图”,然后选择当前项目。选择 " S32 配置工具 " 菜单,然后单击所需的配置工具(引脚、插孔、外围设备等...)。点击其中任何一个都将生成所有元器件。进行所需的更改(如果有),然后单击 " S32 配置工具-> 更新代码 " 按钮 。 3.2 编译应用程序 选择要版本化的配置:左键单击 Eclipse 中版本按钮对应的向下箭头,选择 RAM/FLASH(DEBUG_RAM/DEBUG_FLASH) 。 使用 Project > 版本 来构建项目。 等待版本操作完成,然后继续执行下一步。检查编译器控制台中是否有错误消息;完成后, 应 创建 *.elf 二进制文件 。 祝好, Robin ------------------------------------------------------------------------------- 注: - 如果本帖回答了您的问题,请点击"Mark Correct" 按钮。谢谢! - 我们会在最后一次发帖后的 7 周内跟踪主题,之后的回复将被忽略 如果您以后有相关问题,请另开新主题并参考已关闭的主题。 -------------------------------------------------------------------------------
View full article
使用外部工具链 linux 内核版本在 ARM 上构建 Root 我正在尝试使用外部(官方 Arm 工具链)为 iMX6 板构建 Linux 版本,但我遇到了使用 sshd 的问题。 经过一番调查,官方的ARM工具链似乎带有Linux内核头文件 4.20 ,而我的实际内核是6.12。因此,sshd无法工作,因为某些缺失的系统调用会被 seccomp 阻止(例如 __NR_clock_gettime64 导致 SIGSYS) 问题是,是否有可能结合外部工具链使用实际的内核头文件? 以下是我目前掌握的情况 BR2_arm=y BR2_cortex_a9=y BR2_TOOLCHAIN_EXTERNAL=y BR2_LINUX_KERNEL=y BR2_LINUX_KERNEL_CUSTOM_VERSION=y BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="6.12.47" 我尝试添加 br2_package_host_linux_headers_custom_6_12 = 但它被忽略了。 Re: Buildroot on ARM with external toolchain linux kernel version 你好@rustyx 希望你一切都好。 不幸的是,恩智浦不支持 Buildroot,因此我无法为您的环境提供很多有用的信息。 您可以尝试在 yocto 环境中自行生成工具链。 请参见第 4.5.12 章如何在 i.MX Linux 用户指南的独立组网 (SA) 环境中版本 U-启动 和内核。 顺祝商祺! 萨拉斯
View full article
iMX8QXP I2C RPBUS配置 您好,NXP团队: 我们正在使用 iMX8QXP 作为我们的定制设计的 SoC。在 EVK 中,当我们禁用 imx8x-mek-rpmsg.dtsi 文件中的 i2c_rpbus_5、i2c_rpbus_15 节点时,A35 启动将失败。我们在M4端使用的是默认的电源模式应用程序。 因此,请让我们知道我们需要在什么基础上分配 i2c_rpbus 节点,以及如果我们希望将 M4 与 A35 一起使用,是否必须分配 i2c_rpbus 节点? 问候, 兰吉斯·库马尔。 回复:iMX8QXP I2C RPBUS 配置 嗨志明, 我们认为,一旦我们按照您的建议在 mek.h 文件中进行更改,问题就会得到解决。感谢您的支持。 如果出现任何其他问题,我们将与您核实。 问候, 兰吉斯·库马尔。 回复:iMX8QXP I2C RPBUS 配置 嗨志明, 我们在设计中使用了 2GiB 的 DRAM。您能否告诉我是否有任何更改地址的指南? 问候, 兰吉斯·库马尔。 回复:iMX8QXP I2C RPBUS 配置 嗨志明, 除了 dts、defconfig 和 board 文件的更改之外,我们没有修改 U-boot 源代码。在 imx-mkimage 编译中,我们使用“flash_linux_m4”标志来使用 M4 启动,使用“flash”标志来不使用 M4 启动。 问候, 兰吉斯·库马尔。 回复:iMX8QXP I2C RPBUS 配置 嗨志明, 请在附件(dtsi.zip)中查找 dtsi 文件。 此致, 兰吉斯·库马尔。 回复:iMX8QXP I2C RPBUS 配置 嗨志明, 我们已经收到了目标板,当我使用 M4 启动目标板时,由于 rpmsg.dtsi 文件中只有一个 i2c 总线(映射到 mek.dtsi 文件中的 i2c1),我们面临来自 imx-rproc 驱动程序的内核恐慌,而当我使用没有 M4 的主板启动目标板时,启动没有问题。下面附上内核崩溃的日志。 请仔细研究一下并告诉我这个问题的 RCA 是什么。 问候, 兰吉斯·库马尔。 回复:iMX8QXP I2C RPBUS 配置 嗨志明, 谢谢支持。 问候, 兰吉斯·库马尔 回复:iMX8QXP I2C RPBUS 配置 嗨志明, 感谢您的详细澄清。 我的问题是,在我们的目标设备中,我们不会拥有 rpmsg.dtsi 文件中提到的任何从属设备,所以在这种情况下我们可以禁用所有 i2c_rpbus 节点吗? 问候, 兰吉斯·库马尔 回复:iMX8QXP I2C RPBUS 配置 嗨志明, 谢谢你的信息。通过禁用 i2c_rpbus_5 中的从属设备,我们能够启动主板。 还有一个疑问,是否必须有 i2c_rpbus 节点,否则我们可以禁用所有 i2c_rpbus 节点及其相关的从属节点吗? 此致, 兰吉斯·库马尔。 回复:iMX8QXP I2C RPBUS 配置 嗨志明, 请在附件(kernel_error_logs.txt)中查找内核启动日志。 此致, 兰吉斯·库马尔
View full article
Migrating S32K144 project from S32 design studio for ARM to S32 design studio for S32 platform Hi NXP team, From the NXP website, we obtained the BCC SW Driver Package for MC33771C and MC33772C. We are trying to migrate the those example projects into S32 design studio for S32 platform (Version: 3.5). We followed the migration procedure from the following link: https://community.nxp.com/t5/S32-Design-Studio-Knowledge-Base/Video-Migrating-S32K1-projects-from-S32DS-for-ARM-and-SDK-3-0-x/ta-p/1296239 . However, the code is not migrating correctly, and we are unable to determine why. Please assist me in fixing this problem. Best regards, Hareesh Re: Migrating S32K144 project from S32 design studio for ARM to S32 design studio for S32 platform Hi @VaneB , Thanks for the assistance; everything is operating smoothly now. Best regards, Hareesh Re: Migrating S32K144 project from S32 design studio for ARM to S32 design studio for S32 platform Hi @Hareesh  For the S32SDK S32K1XX RTM 4.0.2, you need to install a service pack, this can be downloaded from S32 Design Studio 3.4 S32K1xx Service Pack 1 > S32 Design Studio IDE >  S32 Design Studio for S32 Platform v.3.4.  Re: Migrating S32K144 project from S32 design studio for ARM to S32 design studio for S32 platform Hi @VaneB , Following your advice, I installed S32DS v3.4. However, as you can see in the attached image below, when I attempted to migrate the project into S32DS, no project names were displayed. I can see several possibilities mentioned there after expanding the migration filter option. However, the files were associated with SDK S32K1xx 4.0.2 (see to the attached image below). However, all I see in my IDE is SDK S32K1xx 4.0.3 (see attached image below). There is no SDK S32K1xx 4.0.2 listed here. How can it be installed if SDK S32k1xx 4.0.2 is the only version that supports it? Could you please help me to address this problem? Best regards, Hareesh Re: Migrating S32K144 project from S32 design studio for ARM to S32 design studio for S32 platform Hi @Hareesh  I am afraid that looks like the migration feature of S32DS v3.5 is not as fully functional as S32DS v3.4. We recommend to move to S32DS v3.4.  I will inform the corresponding team of this issue. Sorry for the inconvenience.  Re: Migrating S32K144 project from S32 design studio for ARM to S32 design studio for S32 platform Hi @VaneB , Yes, there are no mistakes during the code's compilation. However, I am not receiving the project pins and drivers configurations (see screenshots attached), which ought to be provided as they appear in the linked video. Regards, Hareesh Re: Migrating S32K144 project from S32 design studio for ARM to S32 design studio for S32 platform Hi @Hareesh  As I mentioned in my previous response. The steps made were the ones provided in the video shared. Once the steps of code migration were done the errors presented were related to library inclusion, which can be solved with the information provided in my previous post.  Re: Migrating S32K144 project from S32 design studio for ARM to S32 design studio for S32 platform Hi @VaneB , Thanks for the update. Despite my following your instructions, it is not migrating. A snapshot of the migration window is attached. Also, for your reference I attached the project which need to be migrated into S32 design studio 3.5. Regards, Hareesh Re: Migrating S32K144 project from S32 design studio for ARM to S32 design studio for S32 platform Hi @Hareesh  I reproduced the steps of the video and the problems I faced were related to libraries inclusion.  These libraries are located in the Generated_Code file. To solve this problem you need to Rename the ".c" and the ".h", you need to delete the ".bak" of each. You also need to "Exclude from build" the Generated_Code file.  And need to include the file path at project properties.  B.R. VaneB
View full article
i.MX8MPのGPTに対する疑問 IMX8MPRMのドキュメントを読むと、利用可能なGPTが6つあることがわかります。 第12章では、GPTについて説明し、タイマーカウンターのキャプチャをトリガーするために使用できる2つの入力GPT_CAPTURE1とGPT_CAPTURE2があると述べています。 第8章「チップIOとPinmux」では、GPT1_CAPTURE1とGPT1_CAPTURE2という名前の2つのキャプチャ入力しか見つかりません。 6つのGPTのうち、GPT1だけがキャプチャ機能を使用できるということですか? ありがとうございます。よろしくお願いします。 Re:i.MX8MPのGPTについての疑問 はいそうです。
View full article
S32K312 スリープウェイクアップ 背景情報 現在、S32k312を使用してスリープおよびウェイクアップ機能を開発しています。以下の点についてご質問があります。ご助言をお願いいたします。 1. 高速スタンバイではなく通常ウェイクアップを使用しています。通常ウェイクアップモードでは、ウェイクアップソースをスタンバイRAMに保存できますか?現在、WISRレジスタから有効なウェイクアップソースを読み出すことができません。 2. オシロスコープで観察したところ、スリープ状態でウェイクアップソースを受信すると、K3はまずリセットしてからICU割り込みに入ることが分かりました。ウェイクアップはまずリセットされてからICU割り込みに入るのか、それともICU割り込みに入ってからリセットされるのかを知りたいです。 3. スリープ解除後、レベルエッジ割り込みによるウェイクアップを1回だけトリガーしました。ウェイクアップ後、WISRレジスタの値を見ると、ICUウェイクアップ機能で設定されたすべての割り込みが1回トリガーされたことがわかります。そのため、ウェイクアップソースA〜Bが2つ存在するのではないかと疑っています。方法AでMCUをウェイクアップすると、WISRはA〜Bの両方のウェイクアップイベントを同時に記録します。この問題の解決方法をご教示ください。 Re: S32K312 スリープウェイクアップ はい、おっしゃる通り、私のプログラムも同じように設計しています。例えば、同じウェイクアップソースとしてCANウェイクアップを使用しています。ウェイクアップメッセージを1回だけ送信すると、プログラムはウェイクアップしてからスリープ状態に戻ります。しかし、ウェイクアップメッセージを2回または3回送信すると、ソフトウェアは有効なウェイクアップソースを認識し、ウェイクアップ状態を維持できます。なぜでしょうか?ありがとうございます。 Re: S32K312 スリープウェイクアップ 1. 私のソフトウェアは有効なウェイクアップソースを検出すると、ウェイクアップ状態を維持します。この場合、MCUがスリープ状態になった後にウェイクアップイベントを1回だけトリガーすると、MCUはウェイクアップした後すぐに再びスリープ状態になります。これは、有効なウェイクアップソースが認識されていないためと考えられます。MCUがスリープ状態になった後に2回または3回トリガーされれば、有効なウェイクアップソースを認識し、ウェイクアップ状態を維持できます。したがって、K3プラットフォームでは、ウェイクアップイベントを1回だけトリガーすると、MCUをウェイクアップしてリセットすることしかできないと考えられます。2回目または3回目のウェイクアップイベントがない場合、MCUはリセット後すぐに再びスリープ状態になります。私の結論は正しいでしょうか?ありがとうございます。
View full article
hse secboot command failure based on SDK BSP40 Hi, Recently, I tested secboot feature based on SDK BSP40, but got the following error: root@nxp-s32g:~# hse-secboot -s -d /dev/mmcblk0 -k /boot/rsa2048_public.pem [INFO]hse-uio 40210000.mu0b: device hse-uio v2.1 open, instances: 1 Setting up secure boot libhse: initialized, firmware status 0x0920 [INFO] Retrieving IVT from device /dev/mmcblk0 [INFO] Enabling MUs [INFO] Dhse-uio 40210000.mu0b: device hse-uio v2.1 released, instances: 0 id not find previous SYSIMG, formatting NVM and RAM key catalogs [INFO] Importing RSA public key into NVM key catalog [INFO] Generating Secure Memory Region entry ERROR: invalid fip start offset! [ERROR] Failed to allocate space for FIP header ERROR: fip smr entry install failed! libhse: closed root@nxp-s32g:~# root@nxp-s32g:~# And the BSP39 works well. So would you please help to check the issue? Thanks, Zhantao 回复: hse secboot command failure based on SDK BSP40 This issue is fixed and the reason is no relationship with the public repo codes. So I will close this ticket soon. Thanks, Zhantao 回复: hse secboot command failure based on SDK BSP40 The error messages like "ERROR: invalid fip start offset!" is for debug to see the reason, so please ignore them on your side. Thanks, Zhantao
View full article
ROM Event on i.MX8M I want to get ROM Event on an RTOS application running on i.MX8MN. How can I get ROM Event of i.MX8M series? I read AN12853, but I couldn't figure out which one applies to i.MX8M. Re: ROM Event on i.MX8M Thanks for clarifying! Could successfully read from 0x0090E558 and the value there seem to make sense. Kind regards, Markus Re: ROM Event on i.MX8M Hi, Check the OCRAM starting from address 0x90E558. You should find the ROM event buffer there. The OCRAM address pointed to by 0x9E0 should correspond to the ROM event buffer. Regards, Re: ROM Event on i.MX8M Hi, I'm currently trying to get mainline u-boot v2025.01 running on an i.MX8MM on a custom board. However, we're stuck in the boot loader and don't get output via serial interface. So, I connected a J-Link base and read out the registers. Found out that SPL obviously returns to Boot ROM (as the PC is in the Boot ROM range when halting the Cortex-A53), so I wanted to read out the ROM event log buffer to get more info. Having found this post, I tried also with 0x9E0 as address, but the output doesn't seem to make sense: --- Cortex-A53 identified. J-Link>halt PC = 00000000000160C4 CPSR = 600003CD (AArch64, EL3h (SP_EL3) mode, IRQ masked, FIQ masked) SP = 0000000000901F40 ELR_EL1 = 2280006102140688 ELR_EL2 = A700010002088A08 ELR_EL3 = 0000000000016390 SP_EL0 = 01C0000202200002 SP_EL1 = 030C001080440040 SP_EL2 = 000000002002F0F3 SP_EL3 = 0000000000901F40 R0 = 000000000090CC90, R1 = 0000000000000006 R2 = 0000000000901DFB, R3 = 0000000000000000 R4 = 000000000000C1DC, R5 = 0000000000901DFC R6 = 0000000000000000, R7 = 0000000000000000 R8 = 0000000000000000, R9 = 0000000000000180 R10 = 0000000000000047, R11 = 0000000000000000 R12 = 000000000090B5E0, R13 = 000000000090B528 R14 = 0000000000004000, R15 = 000000000090B5E0 R16 = 0000000000000000, R17 = 0000000000000000 R18 = 0000000000000000, R19 = 0000000030350480 R20 = 000000000000000F, R21 = 000000000090E6D8 R22 = 000000000090C000, R23 = 0000000030350480 R24 = 0000000000000002, R25 = 0000000000910000 R26 = 0000000030390070, R27 = 0000000072000000 R28 = 0000000000000000, R29 = 0000000000901F40 R30 = 00000000000160C4, R31 = 0000000000000000 JMISC = 0000000000000008 J-Link>mem32 0x9E0 4 000009E0 = 0090E558 00000000 0090E6D8 00000000 J-Link> --- Is 0x9E0 the correct buffer address also for ixm8m Mini (not only for Nano)? AN12853 is not very clear in this regard... If this is correct, the read data doesn't make sense to me since the first 8 bits should be the ROM event ID (starting with 0x01), but were read as 0x00? Or did I make some mistake in interpreting here? Kind regards, Markus Re: ROM Event on i.MX8M Thanks for the reply. I was able to check the logs. Is there any documentation with details of the parameters? I am trying HAB and I found a log of 0xA0:Image authentication result in the ROM Event ID definition version 2, but I would like to know what that Parameter0 value means. Currently I only know that it is not 0xF0 and that it does not pass. Re: ROM Event on i.MX8M Hello @spthx  I hope you are doing very well. As you can see on the AN12853, the ROM event log buffer is located at a fixed address in the on-chip RAM: Please refer to the Mscale Series. Best regards, Salas.
View full article
IMX8DXL PCIe Endpoint enumeration Hello Everyone, It is related to PCIe link training + Enumeration. Our setup: Host: Intel with BIOS + Windows 10/Linux (debian) OS + PCIe Host Device: imx8dxl PCIe Endpoint I have imx8dxl configured as PCIe Endpoint. The link is up. [ 10.037555] pci_epf_test pci_epf_test.0: Failed to get private DMA rx channel. Falling back to generic one [ 10.037569] pci_epf_test pci_epf_test.0: Failed to get DMA channel [ 10.069805] imx6q-pcie 5f010000.pcie_ep: PCIe Gen.1 x1 link up [ 10.069841] imx6q-pcie 5f010000.pcie_ep: PCIe Gen.1 x1 link up [ 10.069855] imx6q-pcie 5f010000.pcie_ep: Link up, Gen1 Problem: imx8dxl PCIe endpoint device is not detected by Windows OS or Linux. Questions: 1. What could be possible cause for not getting detected, inspite Link is Up? 2. As per PCIe Spec, after device power on + stable clock + PERST, we have 20 ms for Link training and 100ms for enumeration, is this correct? if so, how to achieve this with imx8dxl with uboot + Kernel which takes around 5 seconds for complete boot? Re: IMX8DXL PCIe Endpoint enumeration attached the document from the link Re: IMX8DXL PCIe Endpoint enumeration I got the document at the link: https://community.nxp.com/t5/P-Series/Configuring-PCIe-ports-in-endpoint-mode-in-uboot-and-Linux/m-p/223974 Answer: We need to do it in Uboot. Recommended to repartition the PCI Express initialization code and move it ahead of other code blocks irrelevant to PCI Express. Snip: Because a PCI Express endpoint card seated in each PCI Express slot of a x86 PC motherboard is only one of the many components that the entire PC system interoperates with, the system BIOS can not wait forever to discover the PCI Express endpoint card. To synchronize the PCI Express endpoint discovery process between the x86 PC host and the PCI Express endpoint card, the PCI Express CEM Specification defines a 100-msec rule from the de-assertion time of the PERST# (slot reset) to the time that a PCI Express root complex (host) is allowed to probe the connected downstream endpoint. If a PCI Express endpoint card fails to respond the x86 PC host’s configuration cycle correctly at the time when the 100 msec expires, the host assumes it is malfunctioning. The x86 PC host BIOS might not wait for such PCI Express endpoint card to become available even the endpoint card might just need some more time to initialize itself. Such a PCI Express endpoint card would be disabled by the BIOS and become an undiscoverable PCI Express endpoint in the system. .... In general, introducing less than a 10msec delay is fine. However, any delay beyond 10msec reduces the 100msec budget allocated from the slot reset’s deassertion to the configure cycle being responded by PCI Express end point. Therefore, it is recommended to repartition the PCI Express initialization code and move it ahead of other code blocks irrelevant to PCI Express. Re: IMX8DXL PCIe Endpoint enumeration Dear NXP Support team, You expertise in this domain will be valuable direction to the project. Kindly share you solutions. We look forward to your response. Best regards, KK
View full article
Is there any other low-power mode besides standby for S32K344, such as sleep mode? Does S32K344 have sleep mode? Re: Is there any other low-power mode besides standby for S32K344, such as sleep mode? Hi@SCoder41 We first need to discuss the control method between S32K344 and your power management chip. If this is a control method of an IO port, it can generally be solved by the following methods 1. Pad Keeping feature, the IO port of S32K344 supports Pad Keeping feature, which allows the IO of S32K344 to maintain the state in RUN mode in Standby mode until the Pad Keeping feature is turned off 2. It can be achieved through some external switch circuits, such as setting a normally open or normally closed switch circuit according to the characteristics of your power management chip, so that the MCU control is only required in RUN mode. Re: Is there any other low-power mode besides standby for S32K344, such as sleep mode? Our S32K344 manages the power management chips that supply power to other modules, and requires S32K344 to enable these power management chips. If I wake up S32K344 from standby mode, it will perform a system reset from the reset handler to run the program, and other modules on our board will lose power. How can I solve this problem? Re: Is there any other low-power mode besides standby for S32K344, such as sleep mode? Our S32K344 manages the power management chips that supply power to other modules, and requires S32K344 to enable these power management chips. If I wake up S32K344 from standby mode, it will perform a system reset from the reset handler to run the program, and other modules on our board will lose power. How can I solve this problem? Re: Is there any other low-power mode besides standby for S32K344, such as sleep mode? Hi@SCoder41 Actually there should be only RUN mode and Standby mode, but in RUN mode you can enter VLSRun by lowering the main frequency, but it is still RUN mode. https://community.nxp.com/t5/S32K-Knowledge-Base/S32K3-Low-Power-Management-AN-and-demos/ta-p/1527724
View full article
Cannot write data at address 0x80000000 I am confirming the startup of a custom board using the LS1046A. I created the PBL on https://github.com/nxp-qoriq/atf.git to enable booting in QSPI mode. However, when executed, the console message stops at "NOTICE: BL2: Built: [date and time]." Following advice, I used the QCVS DDR tool to access the DDR, but both read and write failed. Additionally, when I ran [Diagnose Connection] in the [Target Connections] tab, an error was output in the [Test DDR memory access] section: "Cannot write data at address 0x80000000." What areas need to be modified on https://github.com/nxp-qoriq/atf.git to initialize the DDR for my custom board? Currently, I am creating a PBL based on the LS1046ARDB. Thanks. Re: Cannot write data at address 0x80000000 Yes, please use the parameters provided in DDRv tool. Re: Cannot write data at address 0x80000000 Thanks to you, the DDR initialization was successful. However, the third step was also necessary, so I will note it down. 3.In the ATF code, the erratum A09803 sets "ddr_out: address=0x1080114, value=0x401160", but in the DDRv tool-generated DDR initialization file, it was described as CCSR_BE_M(0x01080114, 0x00401150 | 0x00000020). Therefore, by modifying ddr_init.c to write 0x401170 to 0x114, it worked successfully. Is this a bug? Re: Cannot write data at address 0x80000000 1. First for new DDR bringing up on the a custom board, we suggest the customer use QCVS DDRv tool to do validation and optimization to get the optimized parameters to use them in atf source code. For QCVS DDRv tool usage, you could refer to the following document. https://www.nxp.com.cn/docs/en/user-guide/QCVS_DDR_User_Guide.pdf https://community.nxp.com/t5/Qonverge-Knowledge-Base/DDR-Controller-Configuration-on-LS2085-LS2080-Bringing-up/ta-p/1128310 You could use "read from SPD" method to create a QCVS DDR project, then connect to your custom board to do validation to get the optimized parameters and build to generate code ddr_init.c  and use it in ATF source code. 2. Modify atf source code according to your custom board. Go back to folder flexbuild_lsdk2108_github, and run the following command to get atf source code. $ flex-builder -c atf -m ls1046ardb -b qspi Go to atf source code folder components/firmware/atf/, please modify ddr controller initialization file plat/nxp/soc-ls1046a/ls1046ardb/ddr_init.c according to your custom board. Rebuild atf with the following command. $ flex-builder -c atf -m ls1046ardb -b qspi You will get atf images bl2_qspi.pbl and fip_uboot.bin in folder flexbuild_lsdk2108_github/build/firmware/atf/ls1046ardb/. Please deploy bl2_qspi.pbl at 0 and fip_uboot.bin at 0x100000 at QSPI flash.
View full article
How do I set a pin of S32K344 to open drain output mode How do I set a pin of S32K344 to open drain output mode.We have designed the hardware to be in an open drain output triggered mode, with a 5V pull-up,Our hardware schematic is shown in the following figure Re: How do I set a pin of S32K344 to open drain output mode Hello @SCoder41 , here's example for PTG29: #include "Siul2_Port_Ip.h" Siul2_Port_Ip_SetPinDirection(PORTG_H_HALF, 29-16, SIUL2_PORT_HI_Z); 16 shall be subtracted for the upper half port numbers. Best regards, Pavel Re: How do I set a pin of S32K344 to open drain output mode Which address should the first parameter of the function 'Siu l2 Port Ip_SetPinDirection' point to? Re: How do I set a pin of S32K344 to open drain output mode Hello @SCoder41 , important is RTD version. If you look to the link in the first reply, there is function  void Siul2_Port_Ip_SetPinDirection(Siul2_Port_Ip_PortType * const base, uint16 pin, Siul2_Port_Ip_PortDirectionType direction); which can help you. Best regards, Pavel Re: How do I set a pin of S32K344 to open drain output mode S32DS3.5 Re: How do I set a pin of S32K344 to open drain output mode How to set GPIO to "HighZ" mode Re: How do I set a pin of S32K344 to open drain output mode Hello @SCoder41 , there's no "true" open drain support on S32K344 (GPIO open drain? - NXP Community). But your application doesn't look like time critical (many MHz), so you can manage open drain mode easily by switching GPIO between "HighZ" mode and "ouput low" mode. Best regards, Pavel
View full article
MC9S12XEP100 Flash burner question MC9S12XEP100. Code Warrior 5.9.0, single chip, absolute assembler. I have a program, similar to the one I wrote using the MC9S12C64, but larger and more complex. I couldn't figure out the flash burner process for that one until I posted the question and Ladislav was able to explain it to me with his C64-FLASH-ASM test program. Using that I was able to get my program to work just fine. Now I am having the same issue using the MC9S12XEP100 processor. I was hoping there would be enough similarities in the process that I could adapt what I learned, but I'm having some difficulties. Is there a test program similar to the C64-FLASH-ASM, but specific to the MC9S12XEP100 in single chip, absolute assembler that I could study and see if I could get that to work? I'm attaching a basic test code that I am using to troubleshoot. Regards, Robert   Re: MC9S12XEP100 Flash burner question Hi Ladislav, Thanks so much for your detailed response. There are still a few minor errors in your comments, but no matter, I'm quite sure I know what you are doing and they really helped. Your screen shots of the memory window were a big revelation to me. I didn't know about the l, g and r suffix. That explains a lot. The spread sheet that compares the equivalent addresses also really helped in my education. I now feel I have a good understanding of what you have done and a better understanding of what the debugger can do. As a result of my new found knowledge I am realizing that I should be using EEPROM emulation. I have some questions about that in a separate thread.  Thanks once more for all your help and patience. Regards, Robert Re: MC9S12XEP100 Flash burner question Hi, I have found my notes contain copy/paste mistakes. I am not sure what are you looking at so more detailed comments. Moreover, I suppose the DFLASH is in erased status before it is written. Moreover, the question is how the RAM content is refreshed in your memory window. You should also check the setup lime it is done for DFLASH. The address 0x2100 is selected by compiler so the array is placed: Buffer[0] is at address 0x2100,0x2101    of a  local address space Buffer[1] is at address 0x2102,0x2103 Buffer[2] is at address 0x2104,0x2105 Buffer[3] is at address 0x2106,0x2106 Finally, it is good to understand local and global address space. The RAM 0x2100 is in local address space 0x2100 and in the global address space 0x0F_E100. Si memory map in attachment. ... and be careful when you show address space ... extension 'G  or 'L. For example 0FE100'G and 2100'L represents the same address from different views.    .... does no exist  .... the variable "buffer" in a local address space  ... the variable "buffer" in a global address space better comments of the original asm code..            ;---------------------------             ;err = DFLASH_Program(0x0000, &buffer[0], 4); //write 4 words to D Flash address 0x10_0000             ; GPAGE (0x10_.... ) is not used in the Addr variable because it is directly used in the DFLASH_Program routine             MOVW  #$0000,Addr  ; address to be written 0x(10)0000~0x(10)0007                        MOVB  #4,Cnt       ; number of words to be written             ;for example data to be written into DFLASH are 0x0123, 0x4567, 0x89AB, 0xCDEF             ; written global DFLASH address is 0x10_0000’G   … for data visualization in a debugger memory             ; window“ ’G ” must be added into memory address             LDX   #Buffer      ; Load the base address of the array into X register, the base address                                              ; is selected by compiler if you do not set exact address             LDD  #$0123      ; Load the hexadecimal value 0x0123 into D register             STD  0,X                ; Store the value at the 0th position of the array;  Buffer[0] = 0x0123             LDD  #$4567      ; Load the value 0x4567 into D register             STD  2,X                ; Store the value at the 1st position of the array;  Buffer[1] = 0x4567             LDD  #$89AB      ; Load the value 0x89AB into D register             STD  4,X                ; Store the value at the 2nd position of the array;  Buffer[2] = 0x89AB             LDD  #$CDEF     ; Load the value 0xCDEF into D register             STD  6,X                ; Store the value at the 3rd position of the array;  Buffer[3] = 0xCDEF             CALL  DFLASH_Program  ; note there is a status of verification in the Err variable after execution of this command             ;---------------------------             ;err = DFLASH_Program(0x0008, &buffer[0], 4); //write 4 words to eeprom address 0x0000             ;… at this place you should check whether Err value is OK to be sure entire write process has             ;     finished correctly. I am not doing it in this example.             ;---------------------------             ; write another set of data to a 8 bites higher address of the DFLASH             ; written global DFLASH address is 0x10_0008’G             MOVW  #$0008,Addr  ; address to be written  0x(10)0008~0x(10)000F                        MOVB  #4,Cnt       ; number of words to be written                        ;for example data to be written into DFLASH are 0xDEAD,0xBEEF,0xC0DE,0xCAFE             LDX   #Buffer      ; Load the base address of the array into X register, the base address                                              ; is selected by compiler if you do not set exact address             LDD  #$DEAD     ; Load the hexadecimal value 0xDEAD into D register             STD  0,X                ; Store the value at the 0th position of the array;  Buffer[0] = 0x0123             LDD  #$BEEF      ; Load the value 0xBEEF into D register             STD  2,X                ; Store the value at the 1st position of the array;  Buffer[1] = 0x4567             LDD  #$C0DE      ; Load the value 0XC0DE into D register             STD  4,X                ; Store the value at the 2nd position of the array;  Buffer[2] = 0x89AB             LDD  #$CAFE     ; Load the value 0xCAFE into D register             STD  6,X                ; Store the value at the 3rd position of the array;  Buffer[3] = 0xCDEF             CALL  DFLASH_Program  ; note there is a status of verifiction in the Err variable after execution of this command             ;---------------------------             ;err = DFLASH_Program(0x0008, &buffer[0], 4); //write 4 words to eeprom address 0x0000             ;… at this place you should check whether Err value is OK to be sure entire write process has             ;     finished correctly. I am not doing it in this example.             ;--------------------------- Best regards, Ladislav Re: MC9S12XEP100 Flash burner question Hi Daniel, Freescale USBDM (from China). I use it successfully to load programs. Does that answer your question? Regards, Robert Re: MC9S12XEP100 Flash burner question Hi Robert, I mean debugger like PE Micro Multilink (with revision), USBDM, ... Re: MC9S12XEP100 Flash burner question Hi Daniel, Code Warrior IDE V5.9.0 Build 5294 Special Edition. Regards, Robert Re: MC9S12XEP100 Flash burner question Hello @roberthiebert, What debugger do you use? The debugger can interpret the data as 0xCAFE because of ECC, for example. Regards, Daniel Re: MC9S12XEP100 Flash burner question I've spent a lot of time stepping through this code and recording all the variable and register states on each step. I think I have a pretty good understanding of what is happening here, but one thing in particular still has me puzzled. In this section of code: LDX #Buffer ; Load the base address of the array into X register LDD #$0123 ; Load the value 0123 into A register STD 0,X ; Store the value at the 0th position of the array X is loaded with $2100, the address of "Buffer" in RAM D is loaded with decimal 0123 Decimal 0123 is copied into the first two bytes of the "Buffer" array at address $2100 in RAM. Now, when I use the debugger to check the contents of RAM address $2100 I see $CA, $FE in the first two bytes, and they never change. Why is this and where are the example words stored? Regards, Robert  Re: MC9S12XEP100 Flash burner question Hi, The topic has already been processes... https://community.nxp.com/t5/S12-MagniV-Microcontrollers/S12-X-MCU-Security/ta-p/1111118 https://community.nxp.com/t5/S12-MagniV-Microcontrollers/Unsecuring-MC9S12XEP100MAG/m-p/617603 Best regards, Ladislav Re: MC9S12XEP100 Flash burner question Hi Ladislav, One more thing. I did some more research and I understand that in order for CW to be able to read the D-Flash the FSEC register needs to be set to $FE. I see that your code has done this, but I can't find out where and how you did it. Could you explain how I can do that in my code  please? Regards, Robert Re: MC9S12XEP100 Flash burner question Hi Ladislav, I have made some progress. To make a long story short, I discovered that my controller was secured. I don't know how that happened, but I was able to unsecure it and now your program is working the way you have shown in your last post. Now I am able to study your ASM code to make sure I understand it fully before I try to adapt  it it work in my code. I have one thing that is puzzling me though. If I am understanding you r code correctly, you have placed your test data to be burned to D-Flash, in RAM memory starting at Buffer: (address $2100). But when I look at that address all I ever see is $CA,$FE, repeat.  Why is this? Regards, Robert  Re: MC9S12XEP100 Flash burner question I have the memory set to refresh on halt, but no matter what I do, the memory never changes. I've tried setting breakpoints where I see you have highlighted, but nothing. I tired running the program and halting it at random points. No change. What am I doing wrong? Re: MC9S12XEP100 Flash burner question Hi, Do not step memory functions if the part of memory is displayed in the memory window of the debugger. Set refresh memory when halting First loop Second loop … after erase sector Second loop after writing data Second loop reading the data       Moreover, it is always suitable to disable possible interrupts to do not change registers. Create critical section which is not interrupted using CLI, SEI. Best regards, Ladislav Re: MC9S12XEP100 Flash burner question Hi again Ladislav, After stepping through the program again several times I noticed some other peculiar things. After running the FLASH_ERASE_VERIFY subroutine the returned "err" was $01. Which was expected. However, after any FLASH_PROGRAM subroutine "returned "err" was $40. The FLASH_READ  subroutine seems to work but it doesn't return the var_Data values I expected. It returns $FA, $CF first. $4 second. $BB $B6 third.  $46 $46 forth. The values at address $100000 are $FA, $CF, $00,$04,$BB, $B6, $46, $46. These are not the values that should have been burned to this address if I am understanding the program correctly. The values at address $2100 are $CA,$FE,$CA,$FE,$CA,$FE,$CA,$FE and they don't change. Something seems odd here. Regards, Robert  Re: MC9S12XEP100 Flash burner question Hi Ladislav, Thank you for that excellent attachment. It was just what I was looking for. It runs just fine on my controller, except for one thing. I can't seem to get the debugger to update the memory window, either for the RAM or the D-Flash. I when I single step through the program I expected to see the RAM addresses from $2100 to $2110 update with the appropriate steps. I'm not seeing this. I also expected to see the D-Flash addresses from $10000 to $100010 update as I step through, but I'm not seeing that either. Also, if I run the program and halt it, the memory locations are not updated. Are there some settings in the de-bugger that I don't have set right? Regards, Robert Re: MC9S12XEP100 Flash burner question I am very sorry but I see no issue to rebuilt C to ASM. C shows you principle and this C code is not a object oriented programming. It is simple Ansi C. Here you can see programming of D-Flash. (Not P-Flash, it is a little bit different but in principle very similar) ;************************************************************** ;* This stationery serves as the framework for a * ;* user application. For a more comprehensive program that * ;* demonstrates the more advanced functionality of this * ;* processor, please see the demonstration applications * ;* located in the examples subdirectory of the * ;* Freescale CodeWarrior for the HC12 Program directory * ;************************************************************** ; Include derivative-specific definitions INCLUDE 'derivative.inc' ; export symbols XDEF Entry, _Startup, main ; we use export 'Entry' as symbol. This allows us to ; reference 'Entry' either in the linker .prm file ; or from C/C++ later on XREF __SEG_END_SSTACK ; symbol defined by the linker for the end of the stack ;********************************************************************* OK EQU 0 ERASED EQU 1 NON_ERASED EQU 2 LENGTH_OUT_OF_RANGE EQU 3 ;********************************************************************* ; variable/data section MY_EXTENDED_RAM: SECTION ; Insert here your data definition. Buffer ds.w 4; Err ds.b 1; Addr ds.w 1; Cnt ds.b 1; var_i ds.b 1; var_j ds.b 1; var_Data ds.w 1; ;********************************************************************* ; code section MyCode: SECTION main: _Startup: Entry: ;--------------------------- LDS #__SEG_END_SSTACK ; initialize the stack pointer CLI ; enable interrupts ;--------------------------- EndlessLoop: ;--------------------------- ;EE_Init ... 0x0F //oscillator 16MHz -> divide by 0x0F to achieve FCLK 800kHz - 1.05MHz ;while(FSTAT_CCIF == 0); //wait if command in progress BRCLR FSTAT,#128,*+0 ;abs = 0001 ;FCLKDIV = fdiv; //osc = 16MHz LDAB #$0F STAB FCLKDIV ;--------------------------- ;DFLASH_Erase_Sector(0x0000); //erase first sector (256 bytes) MOVW #$0000,Addr CALL DFLASH_Erase_Sector ;--------------------------- ;err = DFLASH_Erase_Verify(0x0000, 16); //check if 16 words are erased - we will receive ERASED message MOVW #$0000,Addr MOVB #16,Cnt CALL DFLASH_Erase_Verify ; note there is a status of verification in the Err variable after execution of this command ;--------------------------- ;err = DFLASH_Program(0x0000, &buffer[0], 4); //write 4 words to D Flash address 0x0000 MOVW #$0000,Addr ; address to be written MOVB #4,Cnt ; number of words to be written ;for example data to be written into DFLASH are 0123, 4567, 89AB, CDEF LDX #Buffer ; Load the base address of the array into X register LDD #$0123 ; Load the value 0123 into A register STD 0,X ; Store the value at the 0th position of the array LDD #$4567 ; Load the value 4567 into A register STD 2,X ; Store the value at the 1st position of the array LDD #$89AB ; Load the value 89SB into A register STD 4,X ; Store the value at the 2nd position of the array LDD #$CDEF ; Load the value CDEF into A register STD 6,X ; Store the value at the 3rd position of the array CALL DFLASH_Program ; note there is a status of verifiction in the Err variable after execution of this command ;--------------------------- ;err = DFLASH_Program(0x0008, &buffer[0], 4); //write 4 words to eeprom address 0x0000 MOVW #$0008,Addr ; address to be written MOVB #4,Cnt ; number of words to be written ;for example data to be written into DFLASH are 0123, 4567, 89AB, CDEF LDX #Buffer ; Load the base address of the array into X register LDD #$DEAD ; Load the value 0123 into A register STD 0,X ; Store the value at the 0th position of the array LDD #$BEEF ; Load the value 4567 into A register STD 2,X ; Store the value at the 1st position of the array LDD #$C0DE ; Load the value 89SB into A register STD 4,X ; Store the value at the 2nd position of the array LDD #$CAFE ; Load the value CDEF into A register STD 6,X ; Store the value at the 3rd position of the array CALL DFLASH_Program ; note there is a status of verifiction in the Err variable after execution of this command ;--------------------------- ; get written data ;--------------------------- MOVW #$0000,Addr CALL DFLASH_Read STD var_Data MOVW #$0002,Addr CALL DFLASH_Read STD var_Data MOVW #$0004,Addr CALL DFLASH_Read STD var_Data MOVW #$0006,Addr CALL DFLASH_Read STD var_Data ;--------------------------- JMP EndlessLoop ; restart. ;--------------------------- ;********************************************************************* ;DFLASH_Read ;********************************************************************* DFLASH_Read: MOVB #$10, GPAGE LDX Addr GLDD X RTC ;********************************************************************* ;DFLASH_Program ;********************************************************************* DFLASH_Program: ;if((Cnt < 1) || (Cnt > 4)) LDAB Cnt CMPB #1 BCS LBL_DP1 CMPB #4 BLS LBL_DP2 ;return LENGTH_OUT_OF_RANGE; LBL_DP1: MOVB #LENGTH_OUT_OF_RANGE,Err RTC LBL_DP2: ;while(FSTAT_CCIF == 0); //wait if command in progress BRCLR FSTAT,#128,*+0 ;abs = 000e ;FSTAT = 0x30; //clear ACCERR and PVIOL MOVB #$30, FSTAT ;FCCOBIX = 0x00; CLR FCCOBIX ;FCCOB = 0x1110; MOVW #$1110,FCCOB ;FCCOBIX = 0x01; MOVB #$1,FCCOBIX ;FCCOB = address; MOVW Addr,FCCOB ;for(i=2; i<=Cnt+1; i++) //fill appropriate number of words to FCCOB CLRA LDX #Buffer LDAB Cnt INCB STAB var_j ; end variable of cycle LDAA #$2 ; start value of cycle LBL_DP3: ;FCCOBIX = A = 2 to {3,4,5}; STAA FCCOBIX ;FCCOB = *ptr; LDD 2,X+ STD FCCOB LDAA FCCOBIX INCA CMPA var_j BLS LBL_DP3 ;FSTAT_CCIF = 1; //launch command BSET FSTAT,#128 ;while(FSTAT_CCIF == 0); //wait for done BRCLR FSTAT,#128,*+0 ;abs = 004b ;return OK; MOVB OK,Err RTC ;********************************************************************* ;DFLASH_Erase_Verify ;********************************************************************* DFLASH_Erase_Verify: ;while(FSTAT_CCIF == 0); //wait if command in progress BRCLR FSTAT,#128,*+0 ;abs = 0001 ;FSTAT = 0x30; //clear ACCERR and PVIOL MOVB #$30,FSTAT ;FCCOBIX = 0x00; CLR FCCOBIX ;FCCOB = 0x1010; MOVW #$1010, FCCOB ;FCCOBIX = 0x01; MOVB #$1, FCCOBIX ;FCCOB = address; MOVW Addr, FCCOB ;FCCOBIX = 0x02; MOVB #$2, FCCOBIX ;FCCOB = number_of_bytes; MOVB Cnt,FCCOB ;FSTAT_CCIF = 1; //launch command BSET FSTAT,#128 ;while(FSTAT_CCIF == 0); //wait for done BRCLR FSTAT,#128,*+0 ;abs = 002b ;if(FSTAT_MGSTAT == 0) BRCLR FSTAT,#3,*+7 ;abs = 0037 BRA lbl_nonerased ;return ERASED; MOVB #ERASED, Err RTC lbl_nonerased: ;return NON_ERASED; MOVB #NON_ERASED, Err RTC ;********************************************************************* ;void DFLASH_Erase_Sector(unsigned int address) ;********************************************************************* DFLASH_Erase_Sector: ;while(FSTAT_CCIF == 0); //wait if command in progress BRCLR FSTAT,#128,*+0 ;abs = 0001 ;FSTAT = 0x30; //clear ACCERR and PVIOL MOVB #$30, FSTAT ;FCCOBIX = 0x00; CLR FCCOBIX ;FCCOB = 0x1210; MOVW #$1210, FCCOB ;FCCOBIX = 0x01; MOVB #$1, FCCOBIX ;FCCOB = address; MOVW Addr,FCCOB ;FSTAT_CCIF = 1; //launch command BSET FSTAT,#128 ;while(FSTAT_CCIF == 0); //wait for done BRCLR FSTAT,#128,*+0 ;abs = 0022 RTC ;********************************************************************* ;********************************************************************* ;********************************************************************* ;********************************************************************* ;********************************************************************* Re: MC9S12XEP100 Flash burner question I'm still working hard at trying to figure this "C" code out but getting nowhere. The code runs and says that the first 256 bytes in D Flash have been erased at $10_0000, but I don't see that. Then it says that buffer[0] has been written into $0_0000, $10_0008 and $10_0010, But I don't see that either. What am I missing here? Regards, Robert Re: MC9S12XEP100 Flash burner question I'm still not getting anywhere with this. I've tried to figure out the ASM by stepping through the code, but I really have to be able to understand what the program is doing in "C" first. I believe that it partitions the DFlash then erases it all. Then it writes 16 bytes that it had written into RAM into D FLash. I can find the bytes in RAM, but in no place in D Flash can I find where it has written them in.  Any suggestions would be greatly appreciated. Regards, Robert Re: MC9S12XEP100 Flash burner question Hi Ladislav, This is not easy stuff for me, but I was able to load your XEP100-DFLASH-CW47 program into my controller using a USBDM. I believe the program is running correctly. I expected to see the D-Flash address from $10_0000 loaded with $12, $34, $56, $78 $9A, $BC, $DE, $F0, but nothing is there. I also expected to see each of the remainder of the 256 byte sector loaded with $FF.  Perhaps my understanding of how the program is supposed to work is flawed? Regards, Robert Re: MC9S12XEP100 Flash burner question Hi Ladislav, Thanks again for your prompt reply and the files. I am not a "C" engineer and only have a basic knowledge of the language so the disassembly process will be challenging, but I'll give it my best shot. Regards, Robert Re: MC9S12XEP100 Flash burner question Hi, there are no similarities. It is 2 levels higher MCU with different memory organization. In this case I suggest to use DFLASH for data storage. There is no ASM code available but I believe it is not any problem to do it by disassembling C code. If you are C coding engineer it must be easy for you to rebuilt it to asm. Here is a C code and the project is attached. You can go/step through the ASM code in debugger to see how it works. I have also attached C code for PFLASH programming. Nothing easier but it does not require to  perform partitioning of this memory. There are some similarities in addresses but global address must be used for data E/W. Short (4000-7FFF) and PPAGE_Offset addresses are used for program execution. In the case of the MCU it will require more effort to understand how flash is organized and how it works. Moreover, to go from relocatable assembly of the single file project to the absolute assembly is easy. Directive EQU is used for data placement into RAM and ORG is used to place code in given PFLASH space. What is necessary to be understand is that for reading and writing DFLASH the global address must be used. However in the case of this memory it is solved easily because it has higher word (DPAFE ) always 0x10 so it is enough to send to the routine only offset in the range 0000-7FFF and full address is created in routine, for example DFLASH_Program.. I am sorry we do not have any empty space, resources or responsibility for such complex projects … plus in assembler. Best regards, Ladislav Re: MC9S12XEP100 Flash burner question Oops. I forgot to mention that when I try to erase the sectors I get an Access Error code. Regards, Robert Re: MC9S12XEP100 Flash burner question I'll try the attachment again
View full article
VSCodeで動作しないコンポーネントを管理しますか? みなさん Visual Studio Code での SDK コンポーネントの管理で問題が発生しています。「コンポーネントの管理」をクリックしても、何も起こりません。 この機能にアクセスするには、プロジェクトを右クリックし、[構成] → [コンポーネントの管理] を選択します。 インストールしたすべてのツールを示すスクリーンショットを添付しました。ご覧のとおり、SDKはリポジトリに適切に追加されています。 セットアップに欠けているものはありますか?他の誰かがこの問題に遭遇し、解決策を見つけましたか? どんな助けでも大歓迎です! Re:VSCodeで動作していないコンポーネントを管理しますか? ご返信ありがとうございます。VSCodeで直接作成されたプロジェクトで機能します-私はあなたの指示に従って新しいSDKの例を作成しました、そしてそれは示されているように機能しました。 しかし、私のメインプロジェクトはもともとMCUXpresso IDEで開発されていましたが、現在はVSCodeに移行しようとしています。この機能を MCUXpresso IDE で最初に作成されたプロジェクトで機能させる方法はありますか?
View full article