Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
zephyr usbhs Sleep and wake up functions are not supported I tested this example while debugging LPC55s28: samples/subsys/usb/hid-mouse CONFIG_USB_DEVICE_REMOTE_WAKEUP=y was set in samples/subsys/usb/hid-mouse/prj.conf, but after compiling the project: int usb_dc_wakeup_request(void) is not supported in drivers/usb/device/usb_dc_mcux.c; Please tell me how to solve this. I also used MCUXpressoIDE to generate a copy of lpcxpresso55s28_dev_suspend_resume_hid_mouse_bm\source\mouse.c, However, it is not possible to add examples to drivers/usb/device/usb_dc_mcux.c in zephyr. I think this also needs to support low power control. Is there a successful example in zephyr? Thank you very much. Re: zephyr usbhs Sleep and wake up functions are not supported Will nxp mcu with usb support zephyr with low power consumption in the future? Re: zephyr usbhs Sleep and wake up functions are not supported Hi @hskating  Sorry,  we currently do not support USB low power control on LPC55s28 Zephyr. BR Harry
View full article
yolo11 オブジェクト検出 int8 量子化モデル (eiq を使用) はオブジェクトを検出しません YOLOv11 オブジェクト検出モデルがありました。私は yolo11n.pt モデルを ONNX 形式に変換しました。その後、ONNXモデルを簡略化して onnxsim。次に、 onnx2tf では、モデルを SavedModel (.pb) 形式に変換しました。その後、NXPのeIQツールキットを使用して、この.pbファイルを変換しました。モデルを INT8 量子化モデルに変換します。このために、キャリブレーション データセットとして COCO128 データセット (100 枚以上の画像) を使用しました。 モデルは正常に変換されましたが、オブジェクトが検出されません。一方、Ultralytics エクスポート API を使用して取得された INT8 モデルでは、正しい検出が生成されます。両モデルの内部重みを確認したところ、それらは異なり、同じ画像に対するモデル出力も大きく異なっていました。 .pb の変換を手伝ってください検出が期待どおりに行われるように、モデルを正しく作成します。 i.MX 8ファミリ | i.MX 8QuadMax (8QM) | 8QuadPlus i.MX 8M | i.MX 8M ミニ | i.MX 8M ナノ Re: yolo11 object detection int8 quantized model using eiq does not detect objects こんにちは、swapnildaphal: yolo 公式 Ultralytics エクスポート API によって取得された INT8 モデルも、内部的に onnx2tf API を呼び出します。これは、あなたが言及した方法と同じである必要があります: yolo11n.pt -> yolo11.onnx -> yolo11_sim.onnx -> yolo11 tensorflow 保存モデル -> tftlie int8 モデル。 EIQツールキットの場合、.pbモデルは int8quantized に変換され、tflite の量子化コードもカプセル化されます。SO、Tensorflow で保存されたモデルを取得した後、次のコードを使用して量子化テストを実行できます。指定されたモデルの前処理方法は、量子化時の元の前処理方法と一致している必要があることに注意してください。 SO、Ultralytics の変換 API を介して TensorFlow 保存モデルを生成し、次に tflite の公式量子化ツールを呼び出してモデルを量子化することができます。 よろしくお願いします。 ダニエル
View full article
NTAG 424 no login possible after key 0 change Hi all, i'm facing a strange behaviour that i can't solve. I completed all my steps to configure a #NTAG424 for a security platform: everything is ok BUT one last thing I had to change all the 5 keys and started with this "loop" for 4 to 0: Login with key 0 Change key X I'm aware that changing K0 is different from K4-1 and the response is 91-00 so seems everything is correct. Now the problem: i can login with all the kyes 4-1 but with K0 i get a 91-AE in login part 2. I suppose that the encryption is wrong so the key is different from what i think, but i checked a lot of time the code and is ok. I only changet the cryptogram calculation as per data sheet and AN12196.  Any hint? Thank Re: NTAG 424 no login possible after key 0 change Hello @MPucci , Have you already implemented ChangeKey 0 and 1-4 in your post? I am currently implementing this, but I have encountered some issues. I am unable to successfully modify Key1-4 to respond to 911E, and after modifying Key0, the authentication response is 91AE. I would like to seek some help from you, and I would greatly appreciate it. Re: NTAG 424 no login possible after key 0 change Hello @KaiLi  I didn't see 6.16.2 in AN12196. Is it because the version of the document is different? Any hints? Thank you! Re: NTAG 424 no login possible after key 0 change Hello @MPucci  Thanks for contacting us and based on your issue description, it's recommended that you try the steps of chapter 6.16.2 of AN12196. For example: 1. Authentication by keyNo 0x00 2. input the New key  3. execute ChangeKey command 4. double check using the new key to authenticate NTAG424. BR Kelly Re: NTAG 424 no login possible after key 0 change Some more info: i know is not correct but i use the same RndA in all login before change the keys. I can't identify the root of the issue, but if i use 5 different RndA in login, no problems with keys (even K0), if i use the same RndA in login, K0 is corrupted. So for now the problem is solved, without knowing the cause.
View full article
i.MX8MP Secure boot - HAB errors using HSM Signatures Hi NXP, I'm working on enabling secure boot on a board based on the i.MX8M Plus. Secure boot works correctly when using certificates, keys, and signatures generated with the CST Tool version 4.0.0. Running hab_status shows no events in this case. However, on another board, when we attempt the secure boot process using certificates, keys, and signatures generated in our internal PKI environment, hab_status reports multiple errors. Below, I’ve included the CSF files and the HAB events we’re encountering. We are using "HSM Mode" and have configured the signature size accordingly. We would like to understand which options or parameters we should use when generating signatures—particularly if we want to simulate the process using an OpenSSL command. Thank you in advance for your support. Best regards, Christophe Guerreiro i.MX 8M | i.MX 8M Mini | i.MX 8M Nano Security Re: i.MX8MP Secure boot - HAB errors using HSM Signatures So, here an update. It appears that when using 4 certificates, the SRK_TABLE is bigger. As our signature are big, this leads on big CSF Binary and get overlapped as some Memory zone are used for other functions. We need to try to reduce the CMS content as it was recommended. I will update the ticket here once this is done. Re: i.MX8MP Secure boot - HAB errors using HSM Signatures Hi @se_cguerr, CC @anda_despotovici, @ZeeFrench, Following our call yesterday, we were able to successfully simulate your use case, and we have a properly signed image. To answer your questions above, here is example command to generate CMS signature with OpenSSL: openssl cms -sign -md sha256 -outform DER -nosmimecap -nocerts -binary -in ${csf_sigreq_file} -out ${csf_sig_file} -signer ${csf_crt} -inkey ${csf_key} -passin file:../keys/key_pass.txt  I assume for this one you have the same command as shown during the call. As per your request here is the command to verify the generated signature: openssl cms -verify -in ${csf_sig_file} -inform DER -binary -content ${csf_sigreq_file} -certsout /dev/null -certfile ${csf_crt} -noverify -out verified_csf_output.txt Duplicate these commands for IMG. Duplicate signing process for SPL & FIT. In my case, the size of output signature size is 509 bytes. Therefore I modify my CSF headers and set  [Header] Signature Size = 509 Regarding the current limitation of your signing room—which only supports signing a provided hash and not raw content, there’s an important update worth noting. As of OpenSSL >= 3.2, an undocumented feature allows you to pass a precomputed hash using the -digest option. I’ve tested this on my side, and it works as expected. Updated Signing Process: Compute the hash of the content externally. csf_sigreq_digest=$(openssl dgst -sha256 ${csf_sigreq_file} | awk '{printf $2}') Sign the precomputed hash using the -digest option. $OPENSSL_PATH/openssl cms -sign -md sha256 -outform DER -nosmimecap -nocerts -binary -digest ${csf_sigreq_digest} -out ${csf_sig_file} -signer ${csf_crt} -inkey ${csf_key} -passin file:../keys/key_pass.txt Verify: $OPENSSL_PATH/openssl cms -verify -in ${csf_sig_file} -inform DER -binary -content ${csf_sigreq_file} -certsout /dev/null -certfile ${csf_crt} -noverify -out verified_csf_output.txt I hope this helps. Let us know if this works for you. Best Maro Re: i.MX8MP Secure boot - HAB errors using HSM Signatures See below files mentionned in my first post. I've read the UG10106.  We are using the CST in HSM mode while we get a signature request. We inject back the signature on the appropriate unique tag and rebuild the flash.bin file. This  procedure works with certificates/keys generated from CST. We don't use PKCS#11 in our case. We are using a signing room. Thanks for your fast reply. Regards, Christophe Re: i.MX8MP Secure boot - HAB errors using HSM Signatures Hello, I am not able to see the CSF files and HAB events mentioned in the description. Could you please confirm if you have followed the procedure described in CST UG in chapter Using CST with Hardware Security Module? If not, is anything that requires a different approach on your side? Thank you. Anda
View full article
サスペンド中のGPIOステータスをRAMに保存する こんにちは、NXPチームの皆様、 当社では、カスタムデザインボードのリファレンスとして s32g399ardb3 を使用し、BSP35 を使用しています。 低アクティブ GPIO (PB_12) があり、デフォルトで P3_3V_IO3P3 を使用してハイにプルアップします。 私はBSP UM Chapter「23.3」に従いました「RAM にサスペンド」を選択すると、ボードが RAM にサスペンドされます。 しかし、P3_3V_IO3P3 が閉じて PB_12 が低くなります。 現在、この GPIO ダイナミックは当社の Linux カーネル ドライバによって制御されていますが、サスペンド関連の機能を追加した後も、GPIO ステータスは依然として高失敗のままです。 ATF で GPIO 動的制御を移動する必要がありますか? よろしくお願いします。 Re: Keeping GPIO status during suspend to RAM こんにちは、GG0712 ご返信よろしくお願いします。 S32G は I2C を使用して PMIC を制御します。一般的に、A コアで PMIC を操作できますが、そのためのコードとドキュメントは提供されていません。 また、PB_12 は VDD_IO_B ドメインなので、ピンをプルアップする場合は VDD_IO_B の電圧が必要です。VDD_IO_B 電圧を設定するときに、ピン PB_12 の内部プルアップを試すことができます。 電源の詳細については、AN14063 を CAN 参照してください。 お役に立てれば幸いです。 BR ジョーイ Re: Keeping GPIO status during suspend to RAM こんにちは@Joey_z 、 現在 M コアを使用していない場合でも、このCAN方法は機能しますか? よろしくお願いします。 Re: Keeping GPIO status during suspend to RAM こんにちは、 GG0712 ご返信よろしくお願いします。 これは M コア PMIC モジュールの設定方法で、次の図のように S32DS IDE を使用します。 スタンバイモードを維持しながら、LDO3 およびその他の vr5510 出力電圧をCAN設定します。 この設定は M Core 用で、S32G は I2C4 を使用して vr5510 に接続します。Aコアに12C4を使用してLDO3_3v3を維持する方法です。 お役に立てれば幸いです。 BR ジョーイ Re: Keeping GPIO status during suspend to RAM こんにちは@Joey_z 、 あなたの写真を通してLDO3_3v3を設定するにはどうすればいいでしょうか? よろしくお願いします。 Re: Keeping GPIO status during suspend to RAM こんにちは、 GG0712 ご返信よろしくお願いします。 RMS32G3.pdf および添付ファイルの S32G_IOMUX.xlsx を参照してください。スタンバイ中は PB_12 状態のパッドがパワーダウン モードに設定されます。 SO、スタンバイ段階ではピンを高レベル電圧に設定できると思います。 このピンをプルアップするために LDO3_3v3 を設定し、LDO3_3v3 の電圧を維持するように vr5510 を設定することができます。 また、スタンバイ段階では、ウェイクアップ ピンを高レベル電圧として選択することもCAN。 お役に立てれば幸いです。 BR ジョーイ Re: Keeping GPIO status during suspend to RAM こんにちは、Joey_zさん 私たちはデザインボードを使用し、PB_12 を GPIO として使用します。 よろしくお願いします。 Re: Keeping GPIO status during suspend to RAM こんにちは、 GG0712 お問い合わせいただきありがとうございます。 RDB3ボードを使用していますか?そして、GPIO (PB_12) を FLEX_LIN2_RX の機能として使用しますか? BR ジョーイ
View full article
S32K312+RTD400+UART FIFO I used S32K312+RTD400 to test the UART POLLING mode. I set the FIFO to 4 datawords, the water value to 2, the timer to 250us, and the baud rate to 230,400 Question: If send_time is set to 4, the sent data will not be lost. When it is greater than 4, some data will be lost. Are 4 words 4 8-bit data? The manual mentions that the DATA register Supports 8-bit, 16-bit, or 32-bit writes, each type of write performing a separate function. An 8-bit write to DATA[7:0] pushes {CTRL[R8T9], CTRL[R9T8], DATA[7:0]} the transmit FIFO with TSC clear. A 16-bit or 32-bit write pushes the data written into the FIFO and does not update the value of CTRL[R8T9] or CTRL[R9T8]. Reads and writes of this register are also involved in the automatic flag clearing mechanisms for some of the LPUART status fields. Can I arbitrarily understand that FIFO is 32-bit? Then, how can I directly write a 32-bit value? In addition, I want to implement a system where, at intervals of 250us, the remaining space of the TXCOUNTER in water is checked. If it does not exceed the value set for water, an appropriate amount of data is placed in the FIFO. If it exceeds water, no action is taken. What modifications do I need to make based on the current code? Re: S32K312+RTD400+UART FIFO Hi, yes, FIFO can be seen as 32bit (word), but here the “word” means single character transmitted/received, which can be programmed to have length of 7-bit, 8-bit, 9-bit or 10-bit. So every write/read to/from FIFO is for single character. FIFO depth is 4 words, cannot be configured by TXFIFOSIZE/RXFIFOSIZE, those are read only fields. In your PIT interrupt you need not to check TDRE and RDRF flags, I think. RXCOUNT says how many words can be read from FIFO, so how many times Lpuart_Uart_Ip_Getchar can be called. (4-TXCOUNT) indicates how many words can be written to FIFO, that is how many times Lpuart_Uart_Ip_Putchar can be called. BR, Petr
View full article
PCA9633TK,芯片输出逻辑被颠倒的问题 PCA9633TK,我们为该芯片使用带有 5V 电源的 8 引脚代码包。我们使用两个输出,即 LED0 和 LED1,而 LED2 和 LED3 则处于悬浮状态,未被使用。 目前正在直接测试 PCA9633TK 的输入和输出,没有连接 LED。IIC 配置的 PWM0 值为 240,但是 LED0 输出的波形占空比非常低。IIC 配置的 PWM0 值为 15,但是 LED0 输出的波形占空比非常高。PCA9633 的输入和输出逻辑是相反的。寄存器配置如下: Address 0x00: Data 0x 01; Address 0x01: Data 0x 07; //INVRT=0 Address 0x02: Data 0x 28; Address 0x03: Data 0x 46; Address 0x08: Data 0x 0A; //LEDOUT=10 其他寄存器未配置。 造成这种现象的可能原因是什么? Re: PCA9633TK, The problem of chip output logic being reversed 亲爱的 Tanpo1989、 PCA9633 数据表中没有使用 "低边 LED 驱动器 "这一短语,但它清楚地描述了默认极性和行为: LED 输出为电流灌 LED 输出驱动器可配置为开漏(仅灌)或图腾极(灌和有限源)。在这两种情况下,LED 都打算从 VDD 连接到 LEDx 引脚,因此当输出处于低电平时,设备会反向电流。其表述如下 "LED 输出驱动器可编程为 5 V 下具有 25 mA 灌电流能力的开漏或 5 V 下具有 25 mA 灌电流、10 mA 源电流能力的图腾柱"。 默认开机状态 = 高电平(LED 关闭) RESET 后,输出为高电平,这意味着 LED 处于关闭状态。这意味着 LOW = LED 亮起。 致以最崇高的敬意 约瑟夫 Re: PCA9633TK, The problem of chip output logic being reversed 感谢您的回复。 PCA9633 手册在什么地方说明它是低边沿 LED 驱动器?表现为高 PWM 值 → 更长的低电平时间 → 在示波器上显示为低电平占空比。 Re: PCA9633TK, The problem of chip output logic being reversed 亲爱的 Tanpo1989、 当 PCA9633 用作低压侧 LED 驱动器时,在没有 LED/负载的情况下探测引脚电压,您看到的正是 PCA9633 的设计功能。 发生了什么?PCA9633 是一款低压侧 LED 驱动器。通过 INVRT=0 ,LED 引脚在 LED 本应亮起时变为低电平。因此,如果测量引脚电压,占空比看起来是反相的: PWM 值高 → 低电平时间长 → 高电平占空比小。 低 PWM 值 → 低电平时间短 → 高电平占空比大。 原因:您测量的是电压,而不是 LED 亮度。芯片按设计运行。 您的配置:将 LED 从 VDD 灌入 LEDn 正确。 LEDOUT=10 表示 PWM 控制, INVRT=0 表示正常。 选项: 真正的 LED:保持原样。 用于无 LED 的台架测试: 反转示波器通道或测量低占空比,或 暂时设置 INVRT=1 (但随后亮度与 PWM 会翻转)。 在 VDD 上添加一个电阻,以模拟负载。 底线:“反向” 效果仅仅是因为输出反向电流,因此 LOW = ON。 致以最崇高的敬意 约瑟夫
View full article
i.MX 8M Plus docker 无法正常工作“无效主机头” 你好, 对于我们的 i.MX 8M Plus EVK 板,我们从链接https://github.com/nxp-imx/meta-imx/tree/mickledore-6.1.55-2.2.0中的 mickledore 分支“mickledore-6.1.55-2.2.0”构建 yocto 源。 在 EVK 板上构建并刷新图像后,我们发现 docker 不起作用。以下命令如下。 root@imx8mpevk:~# uname -a Linux imx8mpevk 6.1.55+g770c5fe2c1d1#1 SMP PREEMPT 11 月 21 日星期二 23:45:58 UTC 2023 aarch64 GNU/Linux root@imx8mpevk:~# root@imx8mpevk:~# systemctl 启动docker root@imx8mpevk:~# root@imx8mpevk:~#docker pull hello-world 使用默认标签:最新 最新:从 library/hello-world 中提取 摘要:sha256:a26bff933ddc26d5cdf7faa98b4ae1e3ec20c4985e6f87ac0973052224d24302 状态:图像已针对 hello-world:latest 更新 docker.io/library/hello-world:latest root@imx8mpevk:~# root@imx8mpevk:~#docker运行hello-world http:无效的主机头 root@imx8mpevk:~# 另请参阅下面的 docker journalctl 日志。 root@imx8mpevk:~# journalctl -xefu docker 4月24日 12:23:20 imx8mpevk systemd[1]:正在启动 Docker 应用程序容器引擎... -- 主题:docker.service 单元的启动作业已开始执行 -- 定义者:systemd -- 支持: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- 单元 docker.service 的启动作业已开始执行。 -- -- 作业标识符为 1630。 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.465195235Z”level=info msg="正在启动" 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.471783509Z”level=info msg="[core] [Channel #1] 频道已创建" module=grpc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.471879134Z”level=info msg="[core] [通道#1] 原始拨号目标是:\"unix:///run/containerd/coc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.472032885Z”level=info msg="[core] [Channel #1] 解析的拨号目标是:{Scheme:unix Authority: Endpoc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.472097885Z”level=info msg="[core] [频道 #1] 频道权限设置为 \"localhost\"" module=grpc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.472945263Z”level=info msg="[核心] [通道 #1] 解析器状态已更新: {\n \"地址\": [\n {c 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.476382650Z”level=info msg="[core] [频道 #1] 频道切换到新的 LB 策略 \"pick_first\"" moc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.479532287Z”level=info msg="[core] [频道 #1 子频道 #2] 子频道已创建" module=grpc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.479762788Z”level=info msg="[core] [Channel #1 SubChannel #2] 子通道连接更改为 CONNc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.479931288Z”level=info msg="[core] [通道 #1 子通道 #2] 子通道选择一个新地址 \"/run/c 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.480056039Z”level=info msg="[core] [通道 #1] 通道连接状态更改为 CONNECTING" module=grc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.488533820Z”level=info msg="[core] [Channel #1 SubChannel #2] 子通道连接更改为 READc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.488714945Z”level=info msg="[core] [Channel #1] 通道连接更改为 READY" module=grpc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.496465474Z”level=info msg="[core] [Channel #4] 频道已创建" module=grpc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.496565849Z”level=info msg="[core] [通道#4] 原始拨号目标是:\"unix:///run/containerd/coc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.496669974Z”level=info msg="[core] [Channel #4] 解析的拨号目标是: {Scheme:unix Authority: Endpoc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.496746725Z”level=info msg="[core] [频道 #4] 频道权限设置为 \"localhost\"" module=grpc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.496911225Z”level=info msg="[核心] [通道 #4] 解析器状态已更新: {\n \"地址\": [\n {c 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.497074476Z”level=info msg="[core] [频道 #4] 频道切换到新的 LB 策略 \"pick_first\"" moc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.497270102Z”level=info msg="[core] [频道 #4 子频道 #5] 子频道已创建" module=grpc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.497479852Z”level=info msg="[core] [Channel #4 SubChannel #5] 子通道连接更改为 CONNc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.497737228Z”level=info msg="[core] [通道 #4 子通道 #5] 子通道选择一个新地址 \"/run/c 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.497770104Z”level=info msg="[core] [通道 #4] 通道连接更改为 CONNECTING" module=grc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.498877358Z”level=info msg="[core] [Channel #4 SubChannel #5] 子通道连接更改为 READc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.499128733Z”level=info msg="[core] [Channel #4] 通道连接更改为 READY" module=grpc 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.597137716Z”level=info msg="正在装载容器:开始。" 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.881553755Z”level=warning msg="无法加载 IPSEC 规则所需的模块:协议不支持" 4月24日 12:23:21 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:21.893731300Z”level=info msg="默认网桥(docker0)分配了IP地址172.17.0.0/16。D” 4月24日 12:23:22 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:22.029149067Z”level=info msg="装载容器:完成。" 4月24日 12:23:22 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:22.246174432Z”level=warning msg="警告:不支持 CPU CFS 配额" 4月24日 12:23:22 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:22.246261186Z”level=warning msg="警告:不支持 CPU CFS 周期" 4月24日 12:23:22 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:22.246296437Z”level=warning msg="警告:没有 blkio throttle.read_bps_device支持” 4月24日 12:23:22 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:22.246344064Z”level=warning msg="警告:没有 blkio throttle.write_bps_device支持” 4月24日 12:23:22 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:22.246379941Z”level=warning msg="警告:没有 blkio throttle.read_iops_device支持” 4月24日 12:23:22 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:22.246413692Z”level=warning msg="警告:没有 blkio throttle.write_iops_device支持” 4月24日 12:23:22 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:22.246501321Z”级别=信息消息=“Docker守护进程”提交=219f21bf07502b447095649b5a2764661737f164 graphdrive 4月24日 12:23:22 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:22.247150101Z”level=info msg="守护进程已完成初始化" 4月24日 12:23:22 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:22.323320938Z”level=info msg="[core] [Server #7] 服务器已创建" module=grpc 4 月 24 日 12:23:22 imx8mpevk systemd[1]:已启动 Docker 应用程序容器引擎。 -- 主题:docker.service 单元的启动作业已成功完成 -- 定义者:systemd -- 支持: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- 单元 docker.service 的启动作业已成功完成。 -- -- 作业标识符为 1630。 4月24日 12:23:22 imx8mpevk dockerd[1393]:时间=“2024-04-24T12:23:22.347791050Z”level=info msg="API 监听 /run/docker.sock" ^C root@imx8mpevk:~# 请分享您的意见 谢谢 回复:i.MX 8M Plus docker 无法正常工作“无效的主机头” 你好 降级 go 包后。docker 工作正常。 参考链接: https ://github.com/moby/moby/issues/46614#issuecomment-1757751921 谢谢
View full article
闪光测试 您好,NXP团队, 我正在尝试使用你的功能检查我的闪存区域: FS_CM33_FLASH_HW16 (); 不幸的是它不起作用,返回值是常量 null。 我的 µC 设备是 LPC5536。有没有示例可以测试我的 lpc5536? 回复:闪光测试 你好,Hang, 谢谢您的支持!! 回复:闪光测试 嗨,Hang, 我已经向您发送了我的项目的链接。此外,还可以通过“MCUexpressoIDE”设置此示例。 我的项目配置:SDK向导->LPCxpresso55s36评估板(sdk_2.xlpc55s36)->组件(其他 -> 安全)NXP-Safety-IEC60730 ->高级项目设置(默认)。就这些。之后,您可以运行该项目,并且应该会出现 flash-error 错误 BR 托马斯 回复:闪光测试 你好,Hang, 目前我使用 LPC55S3x-EVK 板测试“lpcxpresso55s36_safety_iec60730b_Flash_Test”项目。如果我运行该项目,我会得到相同的错误代码“2”-> Flash-Test 错误。 您还可以在 LPC55s3x 套件上评估该项目吗? 回复:闪光测试 你好,Hang, 感谢您的快速回复。我已经测试了flashiap-example,它可以正常工作。当我添加 IEC60730b 库并测试FS_CM33_FLASH_HW16 () 函数,它返回 NULL。(CRC 故障)。我使用 LPC5536 µController……我需要为 HW-CRC 单元激活任何功能吗?
View full article
S32K312 は CAN エラー コールバック問題に入ることができません こんにちは、環境はDS3.5+RTD3.0.0です S32K312_CAN_TX_RX_using_MB_Interruptルーチンにおいて、CANラインが切断されているかCANHとCANLが短絡している場合、error_callback()に遷移しません。main_can_task()では、FLEXCAN_STATUS_BUSYが2(ビジー状態)として読み出されます。error_callback()に遷移する可能性のあるエラーの種類は何でしょうか?解析にご協力ください。 デモプログラムを添付します。 ありがとう!
View full article
LPC824 - Setting Code Read Protection (CRP) Hello! I was hoping to understand more about the Code Read Protection on the LPC824 microcontroller. From what I've been reading, it sounds like the Code Read Protection isn't a dedicated register, but rather just a specific location in memory. Is this correct? Why it matters to me - I have a production released binary that was compiled without "Enable automatic placement of Code Read Protection field in image" selected. I'd like to enabled Code Read Protection after programming the binary. If I simply write 0x87654321 to memory location 0x02FC, is it possible that I overwrite a functional part of my binary? Thank you! LPC800 Re: LPC824 - Setting Code Read Protection (CRP) Hello @kwagner  No, wont' corrupt your software. The important is please read CRP level definition carefully and config  the right CRP. BR Alice Re: LPC824 - Setting Code Read Protection (CRP) Hi Alice, Thanks for the information! If I overwrite memory locations 0x02FC - 0x02FF in my binary, is that dangerous? Is this memory location specifically set aside for CRP or could this corrupt my software? Thanks! Re: LPC824 - Setting Code Read Protection (CRP) Hello @kwagner  1)"From what I've been reading, it sounds like the Code Read Protection isn't a dedicated register, but rather just a specific location in memory. Is this correct?" ->> Yes. 2) The minimum size of flash write and erase is 64 bytes.  Recommend you read out flash, then change the CRP configuration. Then program the whole flash again using new image. BR Alice
View full article
LLCE Firmware load failure in S32g274a whewn booting QSPI Hi all, we are using S32g274a, in which all the LIN cores are used as UART, we are also using interrupt forwarding for LIN cores to get interrupt whenever there is an rx data.Everything works perfectly with the debugger. but the issue we are facing is that when we flash the image into the external boot memory like qspi flash and boot from it, the code is stopped  at the llce_firmware_load(). is there any way we can fix this issue? S32G2  #LLCE Re: LLCE Firmware load failure in S32g274a whewn booting QSPI Hello @naveenkumar_muthusamy  As discussed in the support ticket, the LLCE problem was caused by a missing initialization of the LLCE module.  And also as discussed, this topic was solved. Best regards,  Alejandro Re: LLCE Firmware load failure in S32g274a whewn booting QSPI hello @naveenkumar_muthusamy,  thanks for the clarification on the RTD version and thanks for opening a ticket with the details. I will try to reproduce your problem with my board.  Please let me know in which channel you preferer to continue the discussion,  here in the community or int the support ticket. Best regards, Alejandro Re: LLCE Firmware load failure in S32g274a whewn booting QSPI Hi @alejandro_e , below is the current Linker file we are using in which you can see that the size of RAM is changed. MEMORY { int_itcm : ORIGIN = 0x00000000, LENGTH = 0x00000000 /* 0KB - Not Supported */ int_dtcm : ORIGIN = 0x20000000, LENGTH = 0x00010000 /* 64K */ int_sram_shareable : ORIGIN = 0x22C00000, LENGTH = 0x00004000 /* 16KB */ /* int_sram : ORIGIN = 0x34000000, LENGTH = 0x00400000 */ /* 4MB */ /* int_sram_stack_c0 : ORIGIN = 0x34400000, LENGTH = 0x00002000 */ /* 8KB */ /* int_sram_stack_c1 : ORIGIN = 0x34402000, LENGTH = 0x00002000 */ /* 8KB */ /* int_sram_stack_c2 : ORIGIN = 0x34404000, LENGTH = 0x00002000 */ /* 8KB */ /* int_sram_no_cacheable : ORIGIN = 0x34500000, LENGTH = 0x00100000 */ /* 1MB, needs to include int_results */ /* ram_rsvd2 : ORIGIN = 0x34600000, LENGTH = 0 */ /* End of SRAM */ int_sram : ORIGIN = 0x34000000, LENGTH = 0x00200000 int_sram_stack_c0 : ORIGIN = 0x34200000, LENGTH = 0x00002000 /* 8KB */ int_sram_stack_c1 : ORIGIN = 0x34202000, LENGTH = 0x00002000 /* 8KB */ int_sram_stack_c2 : ORIGIN = 0x34204000, LENGTH = 0x00002000 /* 8KB */ int_sram_no_cacheable : ORIGIN = 0x34206000, LENGTH = 0x00100000 /* 1MB, needs to include int_results */ ram_rsvd2 : ORIGIN = 0x34800000, LENGTH = 0 /* End of SRAM */ LLCE_CAN_SHAREDMEMORY : ORIGIN = 0x43800000 LENGTH = 0x3C800 LLCE_LIN_SHAREDMEMORY : ORIGIN = 0x4383C800 LENGTH = 0xa0 LLCE_BOOT_END : ORIGIN = 0x4383C8A0 LENGTH = 0x50 LLCE_MEAS_SHAREDMEMORY : ORIGIN = 0x4384FFDF LENGTH = 0x20 } for the above linker file,  In IVT tool, we use the RAM_START_ADDRESS as 0x34000000 and RAM_ENTRY_ADDRESS in 0x34207000. for this we are atleast seeing some logs, LLCE is not working but atleast the we can confirm that QSPI boot is working, the above values are taken from the MAP file in the project. also when we revert back to the older linker file which is like below, MEMORY { int_itcm : ORIGIN = 0x00000000, LENGTH = 0x00000000 /* 0KB - Not Supported */ int_dtcm : ORIGIN = 0x20000000, LENGTH = 0x00010000 /* 64K */ int_sram_shareable : ORIGIN = 0x22C00000, LENGTH = 0x00004000 /* 16KB */ int_sram : ORIGIN = 0x34000000, LENGTH = 0x00400000 /* 4MB */ int_sram_stack_c0 : ORIGIN = 0x34400000, LENGTH = 0x00002000 /* 8KB */ int_sram_stack_c1 : ORIGIN = 0x34402000, LENGTH = 0x00002000 /* 8KB */ int_sram_stack_c2 : ORIGIN = 0x34404000, LENGTH = 0x00002000 /* 8KB */ int_sram_no_cacheable : ORIGIN = 0x34500000, LENGTH = 0x00100000 /* 1MB, needs to include int_results */ ram_rsvd2 : ORIGIN = 0x34600000, LENGTH = 0 /* End of SRAM */ /* int_sram : ORIGIN = 0x34000000, LENGTH = 0x00200000 */ /* 4MB */ /* int_sram_stack_c0 : ORIGIN = 0x34200000, LENGTH = 0x00002000 */ /* 8KB */ /* int_sram_stack_c1 : ORIGIN = 0x34202000, LENGTH = 0x00002000 /* 8KB */ /* int_sram_stack_c2 : ORIGIN = 0x34204000, LENGTH = 0x00002000 /* 8KB */ /* int_sram_no_cacheable : ORIGIN = 0x34206000, LENGTH = 0x00100000 /* 1MB, needs to include int_results */ /* ram_rsvd2 : ORIGIN = 0x34800000, LENGTH = 0 /* End of SRAM */ LLCE_CAN_SHAREDMEMORY : ORIGIN = 0x43800000 LENGTH = 0x3C800 LLCE_LIN_SHAREDMEMORY : ORIGIN = 0x4383C800 LENGTH = 0xa0 LLCE_BOOT_END : ORIGIN = 0x4383C8A0 LENGTH = 0x50 LLCE_MEAS_SHAREDMEMORY : ORIGIN = 0x4384FFDF LENGTH = 0x20 } for the above the RAM_START_ADDRESS and RAM_ENTRY_ADDRESS as per Map file is 0x34000000 and 0x34501000, but when create blob image and try booting, we are not seeing any logs, is anything wrong i am doing, can you help on this? Re: LLCE Firmware load failure in S32g274a whewn booting QSPI Hi @alejandro_e , i have created a support and shared the files. and also RTD we are using is 3.2.0 and LLCE is 1.4.0. in IVT tool and image_table only application bootloader is added. RAM_START_ADDRESS 0x34000000 RAM_ENTRY_ADDRESS 0x34207000. we are exporting image after updating the above address and then exporting blob image. Re: LLCE Firmware load failure in S32g274a whewn booting QSPI Hello @naveenkumar_muthusamy,  Thanks a lot for the information. Although it may not be the source of the problem, I recommend upgrading the LLCE version 1.0.5, which is the one tested with the RTD 4.0.0, as you can see in its release notes [Release Notes for LLCE, Version 1.0.5, 16 December 2022]: About the problem: can you share your IVT configuration? did you follow any guide to create the IVT? If possible, please share your project so I may have a better understanding of it, if you prefer you can open a support ticket so you can upload your files privately: Thanks in advance for the information. Re: LLCE Firmware load failure in S32g274a whewn booting QSPI Hi @alejandro_e , yes we are using the M7 core in our project and we are using custom board. we have never tried to boot from the QSPI, this is the first time we are doing this. we were using JTAG for our development purpose and LLCE was working smoothly in JTAG but when we try to boot from QSPI flash we are facing issues exactly in this function as i confiemed it by placing debug prints before calling the llce_firmware_load and after. as soon as llce_firmware_load is called, the code hangs or stops and nothing is executed after that. we are using IVT tool in S32DS to create the blob image and we flash it using S32 flash tool., we have used lin_llce_example project. we are using LLCE version 1.0.4 and RTD 4.0.0 Re: LLCE Firmware load failure in S32g274a whewn booting QSPI Hello @naveenkumar_muthusamy,  Can you provide more information about your setup? I understand you are using Core M7 for this project, is my understanding correct? I understand you are using a custom board instead of an RDB2, is my understanding correct? What is the version of the LLCE FW you are using? What is the version of the RTD you are using? Did you start your project from an example? if so, which one? Have you being able to boot a LLCE application from the QSPI in the past? Can you describe the general process you are following yo build and flash the binary into the QSPI flash? How are you identifying that the program is blocking executing in the mentioned function, llce_firmware_load(). Thanks in advance for the information.
View full article
定制板imxrt1020启动问题 我们的定制板配有 imxrt1020 和外部 QSPI(IS25LP064A)闪存,我们遇到了一些“新手问题”。我们发现有些电路板在生产后立即运行我们的程序而没有任何问题,但对于有些电路板,我们需要执行一些操作。 我们主要使用 cortex-debug 和 JLink,但也使用 MCUXpresso SDK 示例进行测试。 我们在一些(50%)主板上看到的一些症状是 无法从闪存(仅 RAM)调试 MCUXpresso 示例 启动调试后,需要在 cortex-debug 中进行额外的“重置”,以便程序启动 当刷新程序并关闭电源时,程序“丢失”(重新打开电源后无法启动) 大多数董事会都没有看到上述任何问题。我们解决这个问题的方法是在 Boot Utility 工具中生成一个图像并将其下载到主板上。在 RAM 中运行闪存组件 SDK 示例似乎也能修复该问题。 因此,这似乎与正确设置闪光灯有关。 我想知道,为什么这种情况只发生在某些 imxrt1020 控制器上?您知道启动映像(FCB、IVT、启动数据等)的哪个部分负责修复该问题吗?或者启动实用程序是否在后台执行一些其他相关的操作? 是否必须创建并下载图像才能使该控制器与外部 QSPI 闪存正确配合使用? i.MXRT 102x 回复:定制板 imxrt1020 启动问题 你好,Pavel,我上周测试了这个方法,但没有解决问题。我认为它可能与这个问题有关,至少在运行 SDK flash 示例后它运行得更好。 已解决:使用 Segger JLINK 编程器对 MIMXRT1052 进行生产编程 - NXP 社区 回复:定制板 imxrt1020 启动问题 您好,我叫帕维尔,我将支持我们的案件,让我了解您的案件,当我有更多信息时,我会与您联系。 此致, 帕维尔
View full article
MPC5777C optimizations for dual-core execution in S32DS Hello, Now that I have a stable dual-core execution environment for my MPC5777CEVB (thanks to your answers in previous posts, by the way!), I am trying to get into finer detail so that I can get the best performance and predictability for this MCU. During my experiments, many questions came into mind: - Would it be beneficial (in terms of reduced resource contention) to make cpu0 run code from one PFLASH bank and cpu1 run code from another one? In this case, would it be useful to split PFLASH in several TLB entries? - Same question for SRAM: considering it is split in three banks, is there any optimal way of splitting it into cores? I was thinking about having one TLB entry for a shared 64KB space with write-through cache policy and platform coherency, then 192KB for cpu1 and 256KB for cpu0 but I do not know if there is any gain from binding one core to XBAR slave port 2 and the other to XBAR slave port 4, neither if there is some extra care to take about XBAR slave port 2 as (if I understood it correctly) there is more than one memory bank there. - Although the EVB comes a MMO3 part number, I intend to use MMO4 chips in actual development. Will the EVB work fine with the MMO4 chip? May I run it at its maximum frequency? Speaking of which, some documentation parts state the maximum frequency as 300MHz and others as 306MHz. Which one is correct? - Does the maximum EBI CLKOUT remain at 66MHz for MMO4 part numbers? In this case, shall I divide platform clock by 3 and use 50(51?)MHz as CLKOUT? - I was using PIT0 as a trigger to run code in both cores simultaneously (to estimate the interference one gets form the other). How can I make sure both cores received the interrupt before one of them sets PIT_TFLG0[TIF]? - When running some code at both cores (both reading from the same Flash addresses, some reads from the same RAM addresses and some reads (and all writes) to different RAM addresses, cpu0 was quicker than cpu1 (~743us vs. ~799us) with round-robin XBAR arbitration policy. When I changed it to priority-based, times remained about the same, but a little slower for both cores (~748us vs. ~805us). In all cases, I am measuring time using each core's own TBL/TBU registers to minimize resource contention. Why was round-robin better for both cores? - Finally, is there any example or documentation of SDA usage in the S32DS environment? Thanks, Ricardo Re: MPC5777C optimizations for dual-core execution in S32DS Maybe you need to enable it as follows: https://www.nxp.com.cn/docs/en/release-note/S32SDK_Power_Architecture-RN.pdf Regarding interrupts: Interrupts request is triggered in the same cycle for both cores. ISR Handling is however application specific. Re: MPC5777C optimizations for dual-core execution in S32DS Hi David, Thanks for all the answers! I will focus on the ones I might have not understood: - I was using PIT0 as a trigger to run code in both cores simultaneously (to estimate the interference one gets form the other). How can I make sure both cores received the interrupt before one of them sets PIT_TFLG0[TIF]? I am not sure if I understand this point completely, but INTC is capable to send Interrupt request sent to both cores (INTC_PSRn[PRC_SELn] = 0b). Indeed, I am sending the interrupt to both cores. When looking at the example provided in the S32DS knowledge base, only one core serviced the interruption and it had to set PIT_TFLG0[TIF] (apparently, to reset the interrupt until PIT0 sets it again). I would like to know if the interrupt is sent to both cores in the same clock cycle, so that if one of them sets PIT_TFLG0[TIF] as soon as the ISR function starts, there is no risk of the other core "not seeing" the interrupt because one of them cleared it. - Finally, is there any example or documentation of SDA usage in the S32DS environment? What you mean by ‚SDA’ abbreviation? My bad! I am referring to the Small Data Areas. While I could make them work in the GHS environment, I cannot understand how gcc handles them... it was creating .sdata and .sbss sections and allocating things there by default, but it did not look like it was doing accesses indexed by r13. Re: MPC5777C optimizations for dual-core execution in S32DS Answers embedded: - Would it be beneficial (in terms of reduced resource contention) to make cpu0 run code from one PFLASH bank and cpu1 run code from another one? In this case, would it be useful to split PFLASH in several TLB entries? There are two dedicated flash ports, they are not split according address, so there is not need to create multiple TLB entries.   - Same question for SRAM: considering it is split in three banks, is there any optimal way of splitting it into cores? I was thinking about having one TLB entry for a shared 64KB space with write-through cache policy and platform coherency, then 192KB for cpu1 and 256KB for cpu0 but I do not know if there is any gain from binding one core to XBAR slave port 2 and the other to XBAR slave port 4, neither if there is some extra care to take about XBAR slave port 2 as (if I understood it correctly) there is more than one memory bank there. SRAM is split into two halves according address line 18 (see Table 9-2. XBAR slave port assignments). It can be beneficial if one core accesses slave port 2 and second core accesses slave port 4 (or otherwise) as both accesses goes in parallel. - Although the EVB comes a MMO3 part number, I intend to use MMO4 chips in actual development. Will the EVB work fine with the MMO4 chip? May I run it at its maximum frequency? Speaking of which, some documentation parts state the maximum frequency as 300MHz and others as 306MHz. Which one is correct? 300MHz is maximum not modulated frequency, 306MHz includes frequency modulation. - Does the maximum EBI CLKOUT remain at 66MHz for MMO4 part numbers? In this case, shall I divide platform clock by 3 and use 50(51?)MHz as CLKOUT? EBI maximum frequency remains the same, what actually means with 300MHz variant you will have to use lower EBI frequency than with 264MHz version as CLKOUT divider does not offer more options. - I was using PIT0 as a trigger to run code in both cores simultaneously (to estimate the interference one gets form the other). How can I make sure both cores received the interrupt before one of them sets PIT_TFLG0[TIF]? I am not sure if I understand this point completely, but INTC is capable to send Interrupt request sent to both cores (INTC_PSRn[PRC_SELn] = 0b). - When running some code at both cores (both reading from the same Flash addresses, some reads from the same RAM addresses and some reads (and all writes) to different RAM addresses, cpu0 was quicker than cpu1 (~743us vs. ~799us) with round-robin XBAR arbitration policy. When I changed it to priority-based, times remained about the same, but a little slower for both cores (~748us vs. ~805us). In all cases, I am measuring time using each core's own TBL/TBU registers to minimize resource contention. Why was round-robin better for both cores? You may also pay attention to parking control. Ideally how I already answered is to access different SRAM half of by each core, different flash address by each core (there is internal pre-fetch buffers, but access to same address does not run simultaneously and may cause wait states). - Finally, is there any example or documentation of SDA usage in the S32DS environment? What you mean by ‚SDA’ abbreviation?
View full article
关于 MPC5775B 的 MCAL BSP 支持咨询 尊敬的恩智浦支持团队,     我们最近购买了 MPC5775B BMS 和 VCU 参考设计(RDVCU5775EVM) 假设支持 MCAL BSP适用于 MPC5775B微控制器。但是,我无法在您的网站上找到针对此特定控制器的任何 MCAL 包。 您能否指导我在哪里可以获得 此 MCU 有MCAL BSP吗?如果它尚未公开,请让我知道访问它的过程。 期待您的回复。 回复:关于 MPC5775B 的 MCAL BSP 支持问题 感谢提供的所有解决方案。它起作用了,现在我可以配置 MCAL 的驱动程序了。 但我唯一关心的组件是 RTOS(免费 RTOS)。当不建议使用 SDK 时,我现在该如何应用 RTOS 功能?我只能使用 SDK 的 RTOS 功能吗?或者最好的方法是什么? 回复:关于 MPC5775B 的 MCAL BSP 支持问题 你好,请帮我解决以上问题 回复:关于 MPC5775B 的 MCAL BSP 支持问题 好的!谢谢。也请帮助我解决其他问题 回复:关于 MPC5775B 的 MCAL BSP 支持问题 请帮助我解决这些问题 回复:关于 MPC5775B 的 MCAL BSP 支持问题 你好, 我正在使用 MPC5775B 微控制器,并已为该设备导入了 Power Architecture SDK。我现在需要一个兼容的 MCAL 包来配置驱动程序并与 RTOS 集成。 请您确认一下: Power Architecture SDK 是否支持与 MCAL 集成? 是否有适用于 MPC5775B 的官方 MCAL 包?如果有的话,我可以在哪里下载它? 将 MCAL 与 EB tresos Studio 集成以符合 AUTOSAR 要求的推荐方法是什么? 任何指导或文档参考都将不胜感激。 提前致谢! 回复:关于 MPC5775B 的 MCAL BSP 支持问题 您好,我获得了 tresos studio 的产品密钥。我激活了许可证,但无法获取 .lic文件广告现在无法访问 tresos 工作室。请帮助我 回复:关于 MPC5775B 的 MCAL BSP 支持问题 谢谢您的回复。 回复:关于 MPC5775B 的 MCAL BSP 支持问题 感谢您的快速回复, 您确定 MPC5777C 的 MCAL 满足我们对 MPC5775B 的要求吗?MCU系列号不同。
View full article
NCJ29D5の安全なNVストレージエリアにあるキーをTrace32で削除できますか? こんにちは、皆さん。 私はUCJ29D5を使ってUWBレンジングを行っています。 キーをNVエリアに保存することに成功しましたが、trace32を使ってキーを消去する方法はありますか? 'FLASH.ERASE'コマンドで試してみましたが、失敗しました。 メモリ領域は保護領域だと思いますが、何か方法を知りたいです。 ありがとうございます。
View full article
NXP S32K324-ADC0チャンネル49の内部温度読み取りに関する問題 NXPサポートチームの皆様へ ADCハードウェアインスタンス0、チャンネル49を使用してS32K324マイクロコントローラの内部温度センサーを読み取ろうとしたときに問題が発生しました。 私のVREF電圧は3.3V(0x35)に設定されていますが、取得している温度の測定値が期待値と一致しません。     この問題を解決し、正確な温度測定値を得るのに役立つガイダンスや参考資料を教えてください。   よろしくお願いします。 ランジット・クマール Re: NXP S32K324-ADC0チャンネル49の内部温度読み取りに関する問題 こんにちは @ランジス・クマール あなたの新しい質問が何なのかよくわかりません? 私の前の返信では、私はあなたにテストデモを提供しました、そして私はあなたのプロジェクトを見たことがありません。 Re: NXP S32K324-ADC0チャンネル49の内部温度読み取りに関する問題 親愛なるセンレント、 共有ビデオであなたが言った手順に従って、S32K324コントローラーの内部温度センサーを読みました。しかし、安定した、または期待する温度値が得られません。前回の投稿で述べたように、内部の温度センサーからADCの生の値を読み取っていますが、温度の測定値は突然の急上昇を示しており、一定ではありません。 参考までに、コントローラーの近くに外部温度センサーも使用しています。これは、32〜35°Cの安定した温度範囲を示しています。対照的に、内部の温度センサーの読み取り値は負の値と変動値を示しています。 問題とそのために開発したソフトウェアを紹介するビデオを添付しました。取得した値が正しいかどうか、または私のアプローチに問題があるかどうかを確認するのを手伝ってもらえますか?内部温度センサーのデータを正しく読み取って解釈するためのガイダンスやサンプルコードをいただければ幸いです。 再開まで今しばらくお待ちください。 よろしくお願いします。 ランジット・クマール Re: NXP S32K324-ADC0チャンネル49の内部温度読み取りに関する問題 こんにちは @ランジス・クマール あなたのビデオからは、内部温度センサーの生の値すら読んでいないようです。 参考までに、非常に基本的な例を作成しました。ハードウェアはS32K344、RTDは3.0.0+P07です。 Re: NXP S32K324-ADC0チャンネル49の内部温度読み取りに関する問題 親愛なるセンレント、 あなたの提案に従い、提供されたリンクを参照して、RTD 3.0.0を使用してNXP S32K324コントローラーの内部温度センサーを読み取ろうとしました。しかし、私が得ている値は期待した結果と一致しません。 内部温度センサーのデータを読み取って変換する正しい手順を示すサンプルコードまたはリファレンス実装を教えてください。 さらに、私たちの用途に適した閾値温度値を決定する方法についてご指導いただければ幸いです。 参考のために関連文書を添付しました。この問題を解決するのを手伝ってください。 再開まで今しばらくお待ちください。 よろしくお願いいたします。 ランジット・クマール Re: NXP S32K324-ADC0チャンネル49の内部温度読み取りに関する問題 こんにちは @ランジス・クマール 参考までに、このリンクにも同様のデモがあります https://community.nxp.com/t5/S32K/S32K344-Temperature-Sensor/m-p/1876707#M35929 それでも質問がある場合は、基本的なプロジェクトを教えてください。確認のお手伝いをします
View full article
i.mx RT 1175 SDRAM J-Link 启动脚本 使用 SDRAM 将 J-Link 连接/接口到 i.MX RT 1175 M7 核心时出现问题。看到一篇有 M4 代码但没有 M7 的帖子。从 NXP 文档中看到的所有内容来看,M7 首先启动。使用 J-link 或 PE Micro 编程器时,在评估板上将 SDK 示例程序运行在 SDRAM 上会失败。然而,使用内置 LS 编程器时,同一程序在评估板上运行良好。如果是使用内部存储器运行的 SDK 示例程序,那么这三个编程器都可以正常工作。
View full article
MPC5746R User Mode Machine Check Exception on Accessing SIUL2 ports Good Afternoon I am attempting to run application code in USER mode but every time I attempt to write to an SIUL2 port register I get a machine check error.  The OS is relatively simple and accesses the application through a jump block after setting up the base system for the application to run (I hope). No memory protection blocks are changed from their default values except the AIPS which (for now) I have set to maximum permissions (everything is usable by everyone) but I still get a machine check exception each time I try to initialise an SIUL2 port. I have no issues with the DSPI block or the TPU blocks so I don't think it is a general peripheral issue. I have attached what I hope are the relevant parts of the OS and application, I apologise it is so little but I had to fight to be able to send this. The two OS files attached are the relevant startup code and the OS code is the first file the application runs when initialising. Any suggestions or better yet absolute answers would be much appreciated. Re: MPC5746R User Mode Machine Check Exception on Accessing SIUL2 ports Peter Thanks for the quick response. Chapter 80 took some figuring out but in the end I managed to get my head around what it was saying and implemented you suggestion and this works fine. Regards David Re: MPC5746R User Mode Machine Check Exception on Accessing SIUL2 ports Hello, I expect that the issue is in register protection. As you can see SIUL is protected, but DSPI or eTPU are not. You need to allow access in user mode to SIUL module registers in register protection. Set UAA bit for SIUL to 1. Best regards, Peter
View full article
MKL03 从 VLSS3 唤醒后崩溃。 您好,NXP 支持人员。   我正在调试为 MKL03Z32VFK4R 制作的应用程序。 该系统由 3 伏电池供电,大部分时间保持 VLSS3 低功耗模式。 LLWU_P4 引脚(在该 MCU(微控制器)中为 PTB0)配置为在上升沿唤醒。 有一个开关连接到 PTB0,按下时会产生上升沿,从而唤醒 MCU。 唤醒后,执行一些任务,最后返回VLLS3模式。   应用程序运行正常,但有时会间歇性崩溃。 我使用 Nordic Semiconductors 的 PPK2(Power Profiler Kit 2)进行了一些捕获。   我连接了配置为 3 伏电源的 PPK2 来代替电池。 这样我就排除了电池电量低的可能性。 我还连接了 PPK2 的第二个 USB,以保证高达 1000 mA 的供电能力。 我还将 MCU 的 I/O 引脚连接到 PPK2 上的数字输入 D0。 我对 I/O 引脚进行了编程,以切换每行执行的代码,最初的目的是找出它卡在了哪里。   下面我给出一组数字:   图 1:显示连续成功的 PTB0 开关按压循环;   图 2:详细显示了有效的循环。   图03:显示停止的循环,观察时间线,在这种情况下,停止需要5分28秒多一点的时间;   图04:显示崩溃循环,但MCU已恢复;   图 5:放大显示几乎停止的循环的最后部分。注意,D0 开始显示出 toogle 动态,显然与图 04 类似。   我做了几次测试,发现该问题是间歇性的。 有时崩溃会在最初几个周期内发生,有时会持续很长时间,就像本例一样,崩溃发生在 5 分钟以上之后。 我想到了几个假设: 1 - 我认为可能是 VLLS3 唤醒后 ACKISO 标志未被“清除”。 但 MCU 继续崩溃,甚至无条件“清除” ACKISO 标志。 我注释掉了清除 ACKISO 的行,只是为了看看是否会导致 MCU 崩溃。 令人惊讶的是,MCU 并没有崩溃,并且像没有造成任何影响一样正常工作。   2 - 最初,程序调用函数“InitLLWU”,该函数配置LLWU以检测引脚LLWU_P4(PTB0)上的正边沿并启用LLWU中断。 然后调用函数“enter_vlls(3)”进入VLSS3模式。 我尝试将“InitLLWU”函数放在“enter_vlls(3)”函数中,在这种情况下,我在调用__WFI之前放置了“InitLLWU”一行。 我认为崩溃的原因是在 MCU 进入 VLSS3 模式之前发生的 LLWU 中断,但即使在这一改变之后,崩溃仍然发生。   3-一开始我以为图03所示的崩溃表示MCU被唤醒,重启损坏并导致MCU崩溃。 还有一些情况,例如图 04 和 05 中所示的情况,看起来像是崩溃的情况,但 MCU 设法恢复了。 尽管图 04 的初始部分没有出现切换,但在图 05 所示的最终部分中,切换动态与图 02 所示的非常相似。 起初我以为问题可能是由于进入 VLLS3 之前的设置不当造成的。 尽管循环无效,但 MCU 设法恢复,所以我认为问题发生在唤醒之后,可能是部分重置不成功,或者某些初始化失败。   这些是我迄今为止进行的测试和得出的结论。 如果有人有过类似的经历并能给我任何建议,我将不胜感激。   此致。 回复:从 VLSS3 唤醒后 MKL03 崩溃。 你好 Celeste_Liu,抱歉这么晚才回复。 我设法发现了这个问题。 问题与低功耗模式无关,而是与 MKL03Z32VFK4R 的第 19 个引脚有关。 我发现,在唤醒后发生部分复位后,引脚 19 恢复为默认配置,即 NMI(不可屏蔽中断)功能。 我使用引脚 19 作为 GPIO 输入,即作为 PTB5 来读取开关的状态。 我相信重置后,在将引脚配置为 PTB5 之前,一些噪音会激活 NMI 处理程序。 由于我不使用 NMI 函数,我看到默认的 NMI 处理程序是一个锁定处理器的 while(1){} 循环。 根据我在帖子中找到的指导,我通过禁用 NMI 选项解决了该问题: https://community.nxp.com/t5/MCUXpresso-General/debug-problem-on-KL03Z8/mp/949741 我将Flash_Config word4改为0xFFFF3BFE,并做了多次测试,确认问题已经解决。 我感谢你们的支持。 回复:从 VLSS3 唤醒后 MKL03 崩溃。 你好 Celeste_Liu,非常感谢你的反馈。 我在我的项目中没有使用 CMP 比较器模块。 您是否认为即使如此,ERR008010 勘误表仍然有意义? 无论如何,您能向我展示解决方法所建议的代码是什么样的吗? 此致。
View full article