設計中の「シールド」のヘッダーが FRDM KL25Z ボードの穴と確実に揃うようにするにはどうすればよいですか? 私はFRDM-KL25Z開発ボードを使用したプロジェクトに取り組んでいます。私が設計している回路は、ボードのシールドとして十分に機能するほど小さいことに気付きました。これまで盾をデザインしたことがなかったので、SO作り方を学ぶのは良いことだと思いました。 シールドを開発ボードに接続できるように、シールドのヘッダーが開発ボードのヘッダーと揃っていることを確認する必要があります。これを簡単に実行できるボードの CAD モデルを見つけることができませんでした。これらの寸法を見つけるには、ノギスによる測定が唯一の選択肢ですか?私はノギスを持っていない。SOこれは問題になります。 Re: How to ensure headers on a "shield" I am designing will line up with holes on the FRDM FRDM-KL25Z はキャリア ボードの上に配置されるため、機械寸法だけでなくボードの外形も必要です。しかし、USB Type C コネクタを備えた新しいリビジョン (?) のデザインファイルが見つかりません。これらは入手可能でしょうか? ありがとうございます カルロス Re: How to ensure headers on a "shield" I am designing will line up with holes on the FRDM こんにちは@MelonM 、 ご投稿ありがとうございます。FRDM-KL25Z ボードは、Arduino UNO R3 シールド標準に準拠したピン配置で設計されています。関連データを取得するには、Arduino リファレンス・デザインをオンラインで見つけることができます。 あるいは、FRDM KL25Z デザインファイル ( FRDM-KL25Z|Freedom Development プラットフォーム|Kinetis ® MCU | NXP Semiconductors ) をダウンロードし、次のファイルを開いてデータを取得することもできます。 お役に立てれば幸いです。 よろしくお願いいたします。 セレステ --------------------------------------------------------------------------------------------------------------------- 注: この投稿が質問の答えである場合は、「解決策として承認」ボタンをクリックしてください。ありがとう！ --------------------------------------------------------------------------------------------------------------------- Re: How to ensure headers on a "shield" I am designing will line up with holes on the FRDM kicad でピン ヘッダーを適切な場所に配置するために必要なのは、添付画像に示されている 3 つの寸法だけだと思います。これらの次元はどこかに存在するはずですが、見つけることができませんでした。

imx93evk uuu フラッシュが Fail HID(W):LIBUSB_ERROR_NO_DEVICE(0.25 秒) で失敗しました 複数のビルド済みイメージと独自のイメージをフラッシュしてみました。すべて「Fail HID(W):LIBUSB_ERROR_NO_DEVICE(0.25s)」で失敗しました。何が問題なのか全く分かりません。 これは、LF_v6.12.3-1.0.0_images_IMX93EVK をフラッシュしようとしたときのものです。 uuu -V -b emmc_all ./imx-boot-imx93-11x11-lpddr4x-evk-sd.bin-flash_singleboot ./imx-image-full-imx93evk.wic nxp imx チップ用の uuu (ユニバーサル アップデート ユーティリティ) -- lib1.5.141 ビルドイン構成: PCTL チップ VID PID BCD バージョン ================================================== SDPS: MX8QXP 0x1fc9 0x012f [0x0002..0xffff] SDPS: MX8QM 0x1fc9 0x0129 [0x0002..0xffff] SDPS: MX8DXL 0x1fc9 0x0147 SDPS: MX28 0x15a2 0x004f SDPS: MX815 0x1fc9 0x013e SDPS: MX865 0x1fc9 0x0146 SDPS: MX8ULP 0x1fc9 0x014a SDPS: MX8ULP 0x1fc9 0x014b SDPS: MX93 0x1fc9 0x014e SDPS: MX95 0x1fc9 0x015d SDP: MX7D 0x15a2 0x0076 SDP: MX6Q 0x15a2 0x0054 SDP: MX6D 0x15a2 0x0061 SDP: MX6SL 0x15a2 0x0063 SDP: MX6SX 0x15a2 0x0071 SDP: MX6UL 0x15a2 0x007d SDP: MX6ULL 0x15a2 0x0080 SDP: MX6SLL 0x1fc9 0x0128 SDP: MX7ULP 0x1fc9 0x0126 SDP: MXRT106X 0x1fc9 0x0135 SDP: MX8MM 0x1fc9 0x0134 SDP: MX8MQ 0x1fc9 0x012b SDPU: SPL 0x0525 0xb4a4 [0x0000..0x04ff] SDPV: SPL1 0x0525 0xb4a4 [0x0500..0x9998] SDPV: SPL1 0x1fc9 0x0151 [0x0500..0x9998] SDPU: SPL 0x0525 0xb4a4 [0x9999..0x9999] SDPU: SPL 0x3016 0x1001 [0x0000..0x04ff] SDPV: SPL1 0x3016 0x1001 [0x0500..0x9998] FBK: 0x066f 0x9afe FBK: 0x066f 0x9bff FBK: 0x1fc9 0x0153 FB: 0x0525 0xa4a5 FB: 0x18d1 0x0d02 FB: 0x3016 0x0001 FB: 0x1fc9 0x0152 FB: 0x0483 0x0afb 組み込みスクリプトを実行します: uuu_バージョン 1.4.149 # @_flash.bin | wicイメージから抽出CANブートローダー # @_image [_flash.bin]| wic イメージを emmc に書き込みます。 # このコマンドは、i.MX6/7、i.MX8MM、i.MX8MQの場合に実行されます。 SDP: ブート -f ./imx-boot-imx93-11x11-lpddr4x-evk-sd.bin-flash_singleboot -scanlimited 0x800000 # このコマンドはROMがストリームモードをサポートしているときに実行されます # i.MX8QXP、i.MX8QM SDPS: boot -scanterm -f ./imx-boot-imx93-11x11-lpddr4x-evk-sd.bin-flash_singleboot -scanlimited 0x800000 # これらのコマンドはSPLを使用するときに実行され、SPLがない場合はスキップされます # SDPU は廃止されます。SDPUの代わりにSDPVを使用してください # { SDPU: 遅延1000 SDPU: write -f ./imx-boot-imx93-11x11-lpddr4x-evk-sd.bin-flash_singleboot -offset 0x57c00 SDPU: ジャンプ -scanlimited 0x800000 # } # これらのコマンドはSPLを使用するときに実行され、SPLがない場合はスキップされます # if (SPL は SDPV をサポート) # { SDPV: 遅延1000 SDPV: -f ./imx-boot-imx93-11x11-lpddr4x-evk-sd.bin-flash_singleboot -skipspl -scanterm -scanlimited 0x800000 を書き込みます SDPV: ジャンプ -scanlimited 0x800000 # } FB: ucmd setenv fastboot_dev mmc FB: ucmd setenv mmcdev ${emmc_dev} FB: ucmd mmc dev ${emmc_dev} FB: flash -raw2sparse all ./imx-image-full-imx93evk.wic FB: flash -scanterm -scanlimited 0x800000 ブートローダー ./imx-boot-imx93-11x11-lpddr4x-evk-sd.bin-flash_singleboot FB: ucmd 環境が存在する場合は emmc_ack; then ; それ以外の場合は setenv emmc_ack 0; fi; FB: ucmd mmc パートコンファレンス${emmc_dev} ${emmc_ack} 1 0 FB: 完了 既知の USB デバイスが表示されるまで待ちます... 新しいUSBデバイスが1:2で接続されました 1:2>コマンド開始:SDPS: boot -scanterm -f ./imx-boot-imx93-11x11-lpddr4x-evk-sd.bin-flash_singleboot -scanlimited 0x800000 4%1:2>失敗HID(W):LIBUSB_ERROR_NO_DEVICE(0.25秒) Re: imx93evk uuu flash fails with Fail HID(W):LIBUSB_ERROR_NO_DEVICE(0.25s) 私のCASEの解決策を見つけました: 新しいリリースの BSP は古いバージョンのボードをサポートしていません。 こちらと同じですhttps://community.nxp.com/t5/i-MX-Processors/HID-W-LIBUSB-ERROR-NO-DEVICE-4-when-flashing-IMX93EVk-with-uuu/mp/2183157#M241281 Re: imx93evk uuu flash fails with Fail HID(W):LIBUSB_ERROR_NO_DEVICE(0.25s) 私も同じ問題を抱えていました。原因は間違った画像を使用したことでした。特別にビルドされたflash.binである必要があります。つまり、u-boot make によってビルドされたものではありません。 Re: imx93evk uuu flash fails with Fail HID(W):LIBUSB_ERROR_NO_DEVICE(0.25s) 最新バージョンの uuu でも同じ問題が発生しました。 2 台のコンピューターで試しましたが、違いはありませんでした。 Re: imx93evk uuu flash fails with Fail HID(W):LIBUSB_ERROR_NO_DEVICE(0.25s) ああ、順番が間違っていました。 今それが表示されます。しかし、まだ同じエラーが発生します。 既知の USB デバイスが表示されるまで待ちます... 新しい USB デバイスが 1:2-BC57A0FA2C134B85 に接続されました 1:2-BC57A0FA2C134B85>スタートコマンド:SDPS: boot -scanterm -f ./imx-boot-imx93evk-sd.bin-flash_singleboot -scanlimited 0x800000 4%1:2-BC57A0FA2C134B85>HID失敗(W): LIBUSB_ERROR_NO_DEVICE (-4)(0.024秒) Re: imx93evk uuu flash fails with Fail HID(W):LIBUSB_ERROR_NO_DEVICE(0.25s) こんにちは@Beleaf ！ ブートスイッチはこの画像のようになるはずです。 Re: imx93evk uuu flash fails with Fail HID(W):LIBUSB_ERROR_NO_DEVICE(0.25s) 試してみましたが、この方法ではボードが検出されません (lsusb でも表示されません)。 USB1にコネクテッドしています。 ところで、SOご協力に本当に感謝しています。 Re: imx93evk uuu flash fails with Fail HID(W):LIBUSB_ERROR_NO_DEVICE(0.25s) こんにちは@Beleaf ！ 代わりに0011を使用してください Re: imx93evk uuu flash fails with Fail HID(W):LIBUSB_ERROR_NO_DEVICE(0.25s) ああ、その通りですね。残念でしたね。 私はそれを（1011に）変更しましたが、問題は残っています: FB: ucmd setenv fastboot_dev mmc FB: ucmd setenv mmcdev ${emmc_dev} FB: ucmd mmc dev ${emmc_dev} FB: flash -raw2sparse all ./imx-image-full-imx93evk.wic FB: flash -scanterm -scanlimited 0x800000 ブートローダー ./imx-boot-imx93evk-sd.bin-flash_singleboot FB: ucmd 環境が存在する場合は emmc_ack; then ; それ以外の場合は setenv emmc_ack 0; fi; FB: ucmd mmc パートコンファレンス${emmc_dev} ${emmc_ack} 1 0 FB: 完了 既知の USB デバイスが表示されるまで待ちます... 新しい USB デバイスが 1:1-BC57A0FA2C134B85 に接続されました 1:1-BC57A0FA2C134B85>スタートコマンド:SDPS: boot -scanterm -f ./imx-boot-imx93evk-sd.bin-flash_singleboot -scanlimited 0x800000 4%1:1-BC57A0FA2C134B85>HID失敗(W): LIBUSB_ERROR_NO_DEVICE (-4)(0.021秒) Re: imx93evk uuu flash fails with Fail HID(W):LIBUSB_ERROR_NO_DEVICE(0.25s) こんにちは@Beleaf ！ ブートスイッチがダウンロードモードではありません。 ボードをダウンロードモードにしてください。 よろしくお願いいたします！ チャビラ Re: imx93evk uuu flash fails with Fail HID(W):LIBUSB_ERROR_NO_DEVICE(0.25s) ああ、また、Windows からフラッシュしようとしましたが、代わりに LIBUSB_ERROR_PIPE が表示されました: 既知の USB デバイスが表示されるまで待ちます... 新しい USB デバイスが 1:1-BC57A0FA2C134B85 に接続されました 1:1-BC57A0FA2C134B85>スタートコマンド:SDPS: boot -scanterm -f .\imx-boot-imx93evk-sd.bin-flash_singleboot -scanlimited 0x800000 4%1:1-BC57A0FA2C134B85>HID(W)失敗: LIBUSB_ERROR_PIPE (-9)(0.047秒) Re: imx93evk uuu flash fails with Fail HID(W):LIBUSB_ERROR_NO_DEVICE(0.25s) はい、もちろんです: はい、ボードはノートPCに直接コネクテッドされており、すべての USB ポートを試しました。 Re: imx93evk uuu flash fails with Fail HID(W):LIBUSB_ERROR_NO_DEVICE(0.25s) こんにちは@Beleaf ！ ブートスイッチの写真を共有していただけますか? USB ハブを使用せずにボードをホスト コンピューターに接続していますか? Re: imx93evk uuu flash fails with Fail HID(W):LIBUSB_ERROR_NO_DEVICE(0.25s) こんにちは@Beleaf ！ NXP サポートにお問い合わせいただきありがとうございます。 非常に古いバージョンの uuu ツールを使用しています。最新のuuu ツールバージョンを使用してみてください。 よろしくお願いいたします！ チャビラ

CST3.4.0 with HSM Hi, I am using latest CST-3.4.0 & I want to explore the CST-3.4.0 with third party HSM. I configured openssl.cnf as like below, openssl_conf = openssl_init [openssl_init] engines = engine_section [engine_section] pkcs11 = pkcs11_section [pkcs11_section] #Path to the Compiled OpenSSL PKCS11 from OpenSC - libp11 dynamic_path = /usr/lib/x86_64-linux-gnu/engines-1.1/libpkcs11.so MODULE_PATH = /home/jbhaijy/digicert/smtools-linux-x64/smpkcs11.so I run the CST with -b pkcs11 option to sign the images through HSM, but I am getting below errors. ./cst --verbose -b pkcs11 -i dev_spl.csf -o dev_spl.bin Install SRK Install CSFK Certificate not found. Public key certificate is invalid in file pkcs11:model=DigiCert%20PKCS%2311;manufacturer=DigiCert;serial=SS0123456789;token=Virtual%20PKCS%2311%20Token;id=%36%34%33%39%61%63%61%32%2D%35%36%61%30%2D%34%64%64%63%2D%39%36%30%39%2D%65%62%64%39%31%63%36%33%65%33%62%39;object=imx6-hab-csf2-key-test;type=private Please help me identify the problems here.  Thanks for you support.   Re: CST3.4.0 with HSM I am trying to accomplish the signature using Digicert for imx93 with AHAB. I am able to sign both os_cntr_signed.bin and  imx-boot-imx93-var-som-aski-sd.bin-flash_singleboot_gdet but once I try to verify them using ~/cst-4.0.0/linux64/bin/ahab_image_verifier I get a incoherent result: By doing: ahab_image_verifier os_cntr_signed.bin 0 0   I get Signature Block:  Version: 0  Length: 2648 bytes  Tag: 0x90  Certificate Offset: 0x0  SRK Table/Array Offset: 0x10  SRK Table:    Tag: 0xD7    Length: 2112 bytes    Version: 66    SRK Record:      Tag: 0xE1      Length: 527 bytes      Sign Algorithm: RSA             Hash Algorithm: SHA2_384             Key Size/Curve: RSA4096             SRK Flags: CA Flags             Modulus (N): ..... Signature verification failed While by doing: ahab_image_verifier imx-boot-imx93-var-som-aski-sd.bin-flash_singleboot_gdet 0 0    I get: Signature Block:  Version: 0  Length: 400 bytes  Tag: 0x90  Certificate Offset: 0x0  SRK Table/Array Offset: 0x10  SRK Table:    Tag: 0xD7    Length: 308 bytes    Version: 66    SRK Record:      Tag: 0xE1      Length: 76 bytes      Sign Algorithm: ECDSA             Hash Algorithm: SHA2_256             Key Size/Curve: PRIME256V1             SRK Flags: None             X Coordinate:  ....      Y Coordinate:  ... ...... Signature verification successful I used the same csf.cfg as input to cst-signer, thus same SRK Table and Digicert Token are used in cst's .csf files does anybody have a clue?! I also posted this question in here  Re: CST3.4.0 with HSM You can download from https://www.nxp.com/search?keyword=IMX_CST_TOOL Default this CST tool have HSM support but you need to configure your CSF to get it images signed from HSM.  Explore the documentation in this tool for further details. Re: CST3.4.0 with HSM Hi @jbhaijy  how to get latest cst with hsm, unable to find the latest.  Re: CST3.4.0 with HSM Hi @jbhaijy , Could you try the following changes to your openssl.cnf file? openssl_conf = openssl_def [openssl_def] engines = engine_section [engine_section] pkcs11 = pkcs11_section [pkcs11_section] engine_id = pkcs11 #Path to the Compiled OpenSSL PKCS11 from OpenSC - libp11 dynamic_path = /usr/lib/x86_64-linux-gnu/engines-1.1/libpkcs11.so MODULE_PATH = /home/jbhaijy/digicert/smtools-linux-x64/smpkcs11.so init = 0 Let me know if it solves the issue. Best regards, Hector. Re: CST3.4.0 with HSM Hi @hector_delgado  I followed the steps mentioned in the AN12812, Instead of SoftHSM we are using 3rd party HSM.  What could be the possible reasons? Regards, jbhaijy Re: CST3.4.0 with HSM Hi @jbhaijy , Have you followed all steps from our Application Note Using Code-Signing Tool with Hardware Security Module (https://www.nxp.com/webapp/Download?colCode=AN12812&location=null)? Even though it's an old guide, I believe it should still apply to our current CST release. Let me know if this was of any help. Best regards, Hector. Re: CST3.4.0 with HSM @hector_delgado  Thank for the reply.  We want to have CST signing solution for i.MX6 & i.MX8 both. Both are custom boards. I am running Ubuntu-22.04 VM.   Re: CST3.4.0 with HSM Hi @jbhaijy , I hope you're doing well! What i.MX are you using? Is it a custom board or one of our EVKs? Also, what distro and version of Linux are you using in your host environment?  Best regards, Hector.

SJA1105Q MAC to MAC connection issue Hi experts! I am using SJA1105Q board with RGMII connection like this  and I used the sja1105 configuration tool  with sja1105QS.py to generate the code for static configuration. and I found the connection between the two phys is OK but the MCU to SJA1105 (MCU --> port3 or port4 phy) isnot OK. My code about configuration for sja1105 is here. rc = sja1105_check_device_id(priv);// check sja1105 device id if (rc < 0) { printk("================lyl======== cannot find device id\n"); dev_err(dev, "Device ID check failed: %d\n", rc); return rc; } // write static config code to sja1105. int sizecfg = sizeof(configBurst0_0); for(i = 0; i < sizecfg; i += 256) { // write every single 64 4-bytes(32bits).      rc = sja1105_xfer_buf(priv, SPI_WRITE, 0x20000 + i/4,      &configBurst0_0[i], (((sizecfg - i) > 256) ? 256 : (sizecfg - i)));      printk("================lyl======== sja1105_xfer_buf addr=0x%x, rc=%d, i=%d,                     sizecfg=%d\n",       (0x20000 + i/4), rc, i, sizecfg); } //config clock source for RGMII port0 to port4 u8 value2[] = {0x0B,0x00,0x08,0x00};//RGMII_TX_CLK_x to be written is 0x0B000800. rc = sja1105_xfer_buf(priv, SPI_WRITE, 0x10001C, value2, 4); rc = sja1105_xfer_buf(priv, SPI_WRITE, 0x100016, value2, 4); rc = sja1105_xfer_buf(priv, SPI_WRITE, 0x100022, value2, 4); rc = sja1105_xfer_buf(priv, SPI_WRITE, 0x100028, value2, 4); rc = sja1105_xfer_buf(priv, SPI_WRITE, 0x10002e, value2, 4); I sent ethernet packet through MCU and I got err counter register. for example,  ==lyl==  0x1400 rc=0,result=[0x1,0x2,0x3,0x4] means reading register 0x1400 is 0x01020304. Could anyone tell me what is wrong with the configuration? PS: MCU to SJA1105 connection is SJA1105 port 0 (MAC to MAC) My MCU is TDA4VM(TI). Re: SJA1105Q MAC to MAC connection issue Hi, I've also encountered a similar problem. May I ask if you have found the reason? Best Regards, xianlong

How to test if A1006 is working properly <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> I have successfully mounted the A1006 to the i2c circuit, how can I detect if the circuit is working or not. I can use i2cdetect and i2cdump commands in linux system, but the detected registers are all 01, not quite sure, whether it is working or not. 回复： 如何检测A1006是否正常工作 I need support for this ic, can you share?   Re: 如何检测A1006是否正常工作 Hi, It is not the right way with A1006, please kindly refer to Get Started with the KIT-A1006-Shield | NXP  for details. Hope that helps, Have a great day, Kan ------------------------------------------------------------------------------- Note: - If this post answers your question, please click the "Mark Correct" button. Thank you! - We are following threads for 7 weeks after the last post, later replies are ignored Please open a new thread and refer to the closed one, if you have a related question at a later point in time. -------------------------------------------------------------------------------

A1006 client certificate is not usable I want to validate and extract public key from the client certificate stored in Rapid IOT's A1006 authenticator secure element. In fact, I am not able to parse it.  My workflow: Read certificate from the A1006 chip  (using ATMO_MK64F_Auth_GetCert)  Convert it to base64 (using RPK_Base64_Encode) Debug print on the serial console (using ATMO_PLATFORM_DebugPrint) I am printing the certificate character by character using ATMO_PLATFORM_DebugPrint since the function seems not supporting string longer than 64 characters. The base64 encoded certificate: TlhQIFN5c3RlbVJhcGlkIElvVCAgIASSc/L4Ufmi2AJELjQ/6c1dBLaoSwDRko7jrmtOvJkqe+rUIVAe44X4xTA8Ahx8Y9Usm48QYQfCNVYFL2z8v2IyYjxNya3BXw2+AhxvnILvfKv8UYHx3/pHymAfGkOuDjFHNoo85FbiAAA= I stored the certificate to a file (cert.pem) and made it PEM format: -----BEGIN CERTIFICATE----- TlhQIFN5c3RlbVJhcGlkIElvVCAgIASSc/L4Ufmi2AJELjQ/6c1dBLaoSwDRko7j rmtOvJkqe+rUIVAe44X4xTA8Ahx8Y9Usm48QYQfCNVYFL2z8v2IyYjxNya3BXw2+ AhxvnILvfKv8UYHx3/pHymAfGkOuDjFHNoo85FbiAAA= -----END CERTIFICATE----- When I tried to parse: $ openssl x509 -in cert.pem  -text  -noout unable to load certificate 4618929600:error:0D0680A8:asn1 encoding routines:asn1_check_tlen:wrong tag:crypto/asn1/tasn_dec.c:1130: 4618929600:error:0D07803A:asn1 encoding routines:asn1_item_embed_d2i:nested asn1 error:crypto/asn1/tasn_dec.c:290:Type=X509 4618929600:error:0906700D:PEM routines:PEM_ASN1_read_bio:ASN1 lib:crypto/pem/pem_oth.c:33: I also tried to Debug print the certificate in base16 hex: 4E58502053797374656D526170696420496F54202020049273F2F851F9A2D802442E343FE9CD5D04B6A84B00D1928EE3AE6B4EBC992A7BEAD421501EE385F8C5303C021C7C63D52C9B8F106107C23556052F6CFCBF6232623C4DC9ADC15F0DBE021C6F9C82EF7CABFC5181F1DFFA47CA601F1A43AE0E3147368A3CE456E20000 I can confirm the content of the certificate (hex base16) above is same as the value of the BLE characteristic aa386522826cc0cdaccf40096d5876de which also read the certificate ( I checked the  OOB example code in MCUXpresso).  I assume the format is x509 DER format stored in the A1006. Is the certificate further encrypted or corrupted? Rapid IoT 回复： A1006 client certificate is not usable v jesssaid  大家好！ 回复： A1006 client certificate is not usable 还有谁在开发A1006 IC 的一起交流一下还有谁在开发A1006 IC 的一起交流一下Anyone else developing A1006 IC's, let's talk! Re: A1006 client certificate is not usable Hello, Sorry for the inconvenience this might cause you. But you need to sign the NDA and that you will need also to register with a company email. You can also ask in the for one of the distributors available in the following link Distributor Network | NXP   .  Regards,  Estephania  Re:  A1006 client certificate is not usable Hi,  I tried to register in Docstore using the same email registered with NXP community but it was rejected due to non-company email. I again tried with my company email but I was asked to provide NDA between my company and NXP.  My company has nothing to do with Hackster.io contest so they are not going to help me in NDA. Is there any other way to access the library you mentioned in the last reply? Thanks, Naveen Re: A1006 client certificate is not usable Hello,  I believe this might help you, the X.509 cert is a compressed certificate and needs to be decompressed before being parsed so in order to use it as you want you you will need to decompress it.  I would strongly recommend you to register in Docstore and check for the Host Library for the A1006 as you will find some examples and functions to achieve what you are trying to do.  Please check this videos on the Docstore registration Docstore tutorial part 1: User Registration|NXP   Docstore tutorial part 2: portal usage|NXP   And once you get access to the library you might useful the a1006_decompressCert function, so check for it and its usage.  Regards,  Estephania  Re:  A1006 client certificate is not usable Hi, The  ATMO_MK64F_Auth_GetCert  is a wrapper of A1006_Get_Cert. The A1006_Get_Cert did not work directly. The ATMO_MK64F_Auth_GetUid is returning the UID correctly and the ATMO_MK64F_Auth_GetCert returns correct size response but for some reason it is not parsable. My task is simple: get cert from A1006 which should be valid/parsable. Can’t you reproduce it at your end? By the way I am one of the contestants of the Rapid IOT at Hackster.io and this is a blocking issue for my project. Thank you in advance, Naveen Re: A1006 client certificate is not usable Hello,  By any chance, do you have the same behavior by using the A1006_Get_Cert(uint8_t *cert) API?  Regards 回复： A1006 client certificate is not usable I need to use the A1006UK chip. Engineers who have done it have contacted me. Thank you very much, vx jesssaid

HSE firmware installation Hi,      I want to install the HSE firmware, but i am facing one error with the package given C:\NXP\S32K3_HSE_DemoExamples_1_0_0\S32K3_HSE_DemoExamples\Device_Configuration\S32K344_HSE_FW_INSTALL. error make: *** [makefile:38: S32K312_HSE_FW_INSTALL.elf] Error 1 Kindly let me know the solution. is there any firmware available for s32k312 for HSE fw installation? Re: HSE firmware installation Hello guys are you able to solve the error.If yes please help us with this  Re: HSE firmware installation Does someone solve the problem?  I am issuing same steps with you. I tried both full_mem and ab_swap. both failed.. Re: HSE firmware installation Hi, I think I found a solution. In the memory view, the byte order will be reversed if you select "Hex" or "Hex Integer". The register was set for me, but these views confused me. Re: HSE firmware installation Hi, The "3.3.1 MU Installation steps by host in AB_SWAP configuration" chapter of HSE_B Firmware Reference Manual starts by the following lines: "Write 0xA5 on register DCMRWP1 (0x402AC400, [24:31 bits]) followed by functional reset. This will set Bit 1 in HSE GPR (0x4039C028) indicating SBAF has activated MU0 for installation." but it wasn't mentioned in this thread. Is it necessary to set DCMRWP1 register or is it implemented somehow in the example? Regards, Sandor Re: HSE firmware installation Hello, Any update here? Re: HSE firmware installation Hi, Has the problem been solved? What causes this? My side is also the status register can not be set "1", can you share how to solve? Re: HSE firmware installation Hi @lukaszadrapa , I performed HSE FW erase as you mentioned, and it worked. However, I can not install it back. How to install HSE FW again? Best regards, Yetkin Re: HSE firmware installation Hi @lukaszadrapa ! Regarding the discussion, I'm trying to swap the S32K344 board as well. I followed the following steps: 1) Download the S32K3_HSE_DemoExamples_1_0_0, went for the a/b swap, changed the linker file by adding the .pink file. 2) I compiled the project and ran it, in run time, the code keeps on the following step: /* Wait for HSE to initialize(read status bits) after installation */ while((HSE_STATUS_INIT_OK & HSE_MU_GetHseStatus(0)) == 0) { gInstallHSEFwTest = FW_NOT_INSTALLED; /* Please generate a reset to allow installation */ } 3) I tried to both push the RST button on the board and also powering it off and on again, but apparently it isn`t changing anything.  Did I forget a step? Thank you! Re: HSE firmware installation HI Lucas , when can we connect, please provide time and link to connect. Re: HSE firmware installation I'm running out of time today but tomorrow morning should be ok. I will let you know early in the morning when I'm available. Re: HSE firmware installation Or you can create  video for the debug settings and debugging the firmware and then share with me. Re: HSE firmware installation Hi Lucas , i tried but its same. Can we connect for a call hardly 10 minutes if possible? please let me know so i will share the invite. Re: HSE firmware installation There's elf file in the project I already shared: https://community.nxp.com/pwmxy87654/attachments/pwmxy87654/S32K/32120/1/HSE_Install_FW.zip I compared the elf with my current project which I tested today and it's identical, no changes. I had brand new chip, so I used default hse_disabled version. If HSE feature flash is already enabled but HSE FW is not installed yet, you should use hse_enabled. And once AB swap is installed, you should use ab_swap. But I don't think this could be wrong because Pemicro should show some error if it can't erase or program the flash. Even if you use hse_disabled when HSE feature flag is programmed, it will probably still work. To install the firmware also to passive block, two resets are needed (or two power cycles, it doesn't matter): Re: HSE firmware installation Hi Lucas,            Thanks for your reply, Can you please share your .elf file. Why you power cycled the board 2 time, is it mandatory to reset is 2 time or power on 2 times? what was the setting during flash, is it ab_sawp.arp or hse_enabled.arp in the advance setting? ? Re: HSE firmware installation I used another brand new board for my test and I used exactly the same project I sent you earlier. I loaded the project by S32DS via in-built Pemicro OpenSDA interface, run the project, power cycled the board 2x and then I can see that the bit in HSE GPR is set and FW is installed. Once the HSE FW is installed, it's necessary to change the flash algorithm in Pemicro settings: That's because some parts of flash are allocated for HSE when the HSE feature flag is enabled or when AB swap FW is installed. Pemicro needs to be informed about this. Re: HSE firmware installation HI Lucas,           I tried with different board with same firmware project what you shared but the result is same as earlier. Last bit of the HSE GPR register is not getting set. Can you please try with PE Micro debugger and try to find the root cause of the problem. We dont have lauterbach debugger here. i am sharing the picture of the memory with different board. Re: HSE firmware installation Hi Lucas,          I dont have debugger PE micro. Does this trace32 power view works with PE micro? How to trigger the service via MU in debugger with PE micro and s32DS? is there any example code? How can i erase the controller with S32DS? Is there any example code or should i use the API FLASH_EraseBlock(dst); ? Re: HSE firmware installation This is new feature and I didn't find API for that in RTD or in HSE DEMO examples. So, I used minimalist option and I simply triggered the service via MU in debugger. Here is the description of the service from API manual: c:\NXP\HSE_FW_S32K312_0_2_40_0\docs\S32K312_HSE_Service_API_Reference_Manual.pdf So, the service ID is 0x57 and no parameters are needed. Just write 0x57 somewhere to RAM and then write address of this RAM word to Message Unit MU_0, register TR[1]. That's all. Then you will see the response in RR[1]. If the HSE FW was installed, you should get HSE_SRV_RSP_OK which is value 0x55A5AA33. Here's how it looks in my debugger: Re: HSE firmware installation I am trying to use FLASH_EraseBlock((uint32_t*)HSE_SRV_ID_ERASE_FW); but it goes into the hard fault. Can you please explain the steps to erase the memory.  Should i comment the import of the hse fw file in linker file befor applying this erase? how it will be done, please explain. Re: HSE firmware installation Hi Lucas,        Which api you had used to erase the controller with HSE_SRV_ID_ERASE_FW? Please provide the API . Re: HSE firmware installation Attached is whole project. Re: HSE firmware installation Dis you used the project which i shared with you? Kindly share your main program with me. Re: HSE firmware installation Hi Lucas,            Can you please share your main program. i have only one board with me and its new one. Re: HSE firmware installation I got new board right now. Here's the result of my test: I was able to successfully install the firmware using your project. I just uncommented checking of the HSE feature flag. That was the only change I did.  After that, I could successfully erase the firmware using service HSE_SRV_ID_ERASE_FW. I'm still not sure why it does not work on your side. Do you have more boards? Are all of them showing the same behavior? Regards, Lukas Re: HSE firmware installation Hi Lucas    Any update on this? Re: HSE firmware installation I tried the firmware with the condition on the feature flag  but again the hse gpr resgiter is not getting updated. Re: HSE firmware installation Small problem on my side - I found that I already have firmware 2.6.0 on both my boards and it can't be erased (this feature was added in version 2.40.0). I will get brand new board on Monday and I will test it. I checked the project anyway and I can see nothing wrong. I would just not program the HSE feature flag unconditionally after each reset. I will let you know the results of my test on Monday. Regards, Lukas Re: HSE firmware installation Please debug it and check why hse gpr register bit is not getting set and installation is  not completing by sbaf. Re: HSE firmware installation Please find the project. Re: HSE firmware installation Hi @vikmonti7804  could you please share that project? I will test it on my side. Thanks, Lukas Re: HSE firmware installation Hi,           kindly check the image attached, the header of the AB_Swap is also there in the memory so it means the firmware is flashed in the memory, the utest area has value AABBCCDDDDCCBBAA it means utest is enabled, the HSE GPR register bit 0 is not getting set, i dont know why? it means after reset the SBAF is not installing the hse firmware in secure memory region. kindly help on urgent basis. Re: HSE firmware installation Hi,      I am just following the example code given for the s32k344, so i created same project for the s32k312 and imported the binary from the linker file, i see the 0xAABBCCDD  at 0x1B000000 location in memory window, what can be the problem. Every thing is same as per the example code as s32k344, only i changed the memory location in linker file. Can you please help on urgent basis, or can we connect online for debugging purpose on small call. please find the snippet of the linker file and program. Re: HSE firmware installation I don't think the HSE GPR is defined in peripheral structure, so it's necessary to check the memory directly. If you can see 0xC1010000 at 0x4039C028, the HSE FW is obviously not installed. Is the HSE feature flash at 0x1B000000 programmed? And one more thing - I can remember that that if you use "without IVT" method to install the firmware, there can't be valid IVT in the flash. Otherwise it does not work. If you loaded the pink/bin file together with some project, it's necessary to remove the IVT. Or "with IVT" method must be used. Regards, Lukas Re: HSE firmware installation Hi Lucas ,           I am not able to see this register in any peripheral window in S32DS, Can you please tell me exactly where i can see. i can see the value 0xC1010000 at 0x4039C028 address. Re: HSE firmware installation Hi,    Actually i have created a project for s32k312  but when i am running it in debug mde i see it directly jumping to default hander not going into main, can you please help with this issue, why this is happening. i see the binary is place in flash but utest is not enabled due to not going into main. kindly help. Re: HSE firmware installation You can check bit 0 in HSE GPR status register at 0x4039C028. If it is '1', it means that "HSE FW is present and SBAF Booted HSE Firmware". You can find this in HSE_B Firmware Reference Manual rev 2.2. Regards, Lukas Re: HSE firmware installation Hi ,   If I am able to install the HSE firmware successfully, how to verify this firmware is installed in the secure memory correctly or successfully in the memory. please let me know any method or check the memory? Thank You Re: HSE firmware installation The firmware is provided in encrypted form as a binary file. Yes, HSE FW installation package contains only the binary (pink) file and corresponding API headers. For Lauterbach users, there's also HSE DEMOAPP which helps to install the firmware and examine HSE features: But notice that the demo works with Lauterbach debugger only. It won't work with Pemicro. As you can read in the mentioned application note or in HSE FW RM, the firmware can be installed with or without IVT. Installation without IVT is easier but you need a tool which is able to load raw binary file to the flash which is not the case of Pemicro debugger. In this case, "with IVT" method is more convenient. We do not provide S32K344_HSE_FW_INSTALL for each derivative. This is just an example showing how it can be done and it's up to users to create own solution (each customer has different requirements and production tools/capabilities). What to do: You can create new application project directly for S32K312 in S32 Design Studio. Then copy the source files from S32K344_HSE_FW_INSTALL, update HseFwHeader_StartAddress in boot_header.c. Then modify the linker file - use linker file from S32K344_HSE_FW_INSTALL as a template. If you read the readme.md file as I suggested earlier, there must be a link to the bin/pink file, so it is linked to the project. Then, the code will only enable HSE feature flag by programming any value different from 0xFFFFFFFFFFFFFFFF at address 0x1B000000. Then all the conditions for installation are satisfied - HSE feature flag is enabled, IVT points to valid pink image in flash, so SBAF will install the firmware after next reset. Regards, Lukas Re: HSE firmware installation HI,   the Firmware for the s32k312 is only the file like interface and host, it is not complete project which can flash the HSE firmware binary to controller like s32k344 hse demo example. I am facing a issue to flash the HSE firmware binry to cntroller as NXP provided only .bin file, i have used the PE micro and eval board built in debugger which is unable to do so, it can support only .elf and .hex file. kindly help me to flash the .bin to controller. Re: HSE firmware installation Hi ,  The HSE firmware package foe the S32K312 is only having the bin files and some interface and host files for the creation of the project. It is not the complete project like HSE demo example for s32k344. I am also facing the issue to flash this binary of HSE firmware with the eval board debugger as well as PE micro debugger because it supports only .elf and hex file. kindly help me to flash the binary to the eval board. Re: HSE firmware installation Hi @vikmonti7804  The HSE FW can be found in S32K3 Standard Software package: https://www.nxp.com/webapp/swlicensing/sso/downloadSoftware.sp?catid=SW32K3-STDSW-D Open the "Automotive SW - S32K3 - HSE Firmware" and you will see all available versions including version for S32K312. Mentioned example S32K344_HSE_FW_INSTALL shows an option how to install the firmware. I recommend to read the description: c:\NXP\S32K3_HSE_DemoExamples_1_0_0\S32K3_HSE_DemoExamples\Device_Configuration\S32K344_HSE_FW_INSTALL\Readme.md We also provide document AN744810 “HSE FW install for S32K3xx” which describes how to install the firmware. It can be found in Documentation in Secure Files section: https://www.nxp.com/products/processors-and-microcontrollers/s32-automotive-platform/s32k-auto-general-purpose-mcus/s32k3-microcontrollers-for-automotive-general-purpose:S32K3 Regards, Lukas Re: HSE firmware installation #hello@vikmonti7804  did u get the solution for the above problem that is programm getting stuck at below ..please hep us    if yes please please help us we are trying alot still we are not getting what to do ? Thank u Re: HSE firmware installation #Hello@lukaszadrapa , Please help us we need your help. Our HSE firmware is flashed successfully, but the firmware is not starting after flashing. The system gets stuck at the same point every time and does not continue execution. I am not sure why this is happening. I have a few doubts: Before flashing the firmware, do we need to run any other project like the Key Catalog example or any prerequisite configuration? Earlier, we had flashed HSE Firmware version 2.1, but now we changed the firmware to version 2.55. Could this version change cause the issue? The SBUF version we are reading is 0x00500000. Is this expected for firmware version 2.55? Do we need to make any specific changes in the HSE_FW_INSTALL application code when updating to the new firmware version? we have API provided along with firmware where we need to use them ? Please please guide us on what might be causing the firmware not to start. Thank you Re: HSE firmware installation hello @lukaszadrapa please help us our firmware code itself stucking at  i dont know why this is happening please help us  firmware flshing i did and verified i dont know why my firmware is not initiating ..please help us  Thank u Re: HSE firmware installation # Hello@sandor_b  Did you receive any update regarding this issue? We are also facing the same problem — our program is getting stuck at that line. If you have found a solution, could you please share it? It would really

在 MPC5775 硬件设计中不使用 ENGCLK PIN 时如何处理它 您好， 在 MPC5775E 硬件设计中不使用 ENGCLK PIN 时，是否需要考虑如何处理它？ 可以把它浮空吗？还是通过电阻器下拉？如果通过电阻器下拉，对电阻器有什么要求？ 感谢您的帮助！ Re: How to deal with the ENGCLK PIN when it's not be used in MPC5775 hardware design @davidtosenovjan，您建议将PCR214 的 OBE 标志 设置为低，但恩智浦 MCAL 是否允许这样做？ 我们使用 Vector 基于 MPC5777C_MCAL v4_3_RTM_1_0_2_0 MCAL 的 DaVinci 配置器，但无法将 OBE 标志配置为低。 此致敬礼， 罗马 Re: How to deal with the ENGCLK PIN when it's not be used in MPC5775 hardware design 你好，由于它是仅限输出的引脚，我建议你让它浮空并禁用输出缓冲器，即清除 SIU_PCR214 (OBE) 以降低 EMI。

TempSense データはSO奇妙です。 私は s32k314、s32ds 3.6.1 バージョンを使用しています。 MCU TempSense を読み取るためのソースコードを作成します。 MCU TempSense データからデータを取得すると、データが SO 奇妙になります。 Adc_Sar_Ip_TempSenseGetTemp 関数を使用する前に、Adc_Sar_Ip_TempSenseEnable(1U) を使用します。 理由パラメータ 1 は、ADC 構成によって ADC1 に TempSense ADC チャネルを作成するためです。 1. なぜデータはSO奇妙なのか? 2. 何かしなければなりませんか? 3. 最初の画像を見ると、ADC 解像度は 14 です。SO tempSens 解像度は 14 ビットですか? 助けてくれてありがとう。 Re: TempSense data is so weird.. @センレント ハードウェアエンジニアがハードウェアをチェックします。SOデータが不安定だと分かりました。 供給するvref電圧は5.0Vですが、vrefは不安定です（4.1V〜5.8V）。 RTD バージョンは 4.0.0 です。 助けてくれてありがとう。 Re: TempSense data is so weird.. こんにちは@rlaxortn あなたのRTDバージョンは何ですか? Re: TempSense data is so weird.. @センレント 1. 申し訳ありません、それは私の間違いです。VREF は絶対に 5.0V です。SO私はすでに値0x50を変更しています。 しかし結果は同じです。 2. 現在の値よりも大きい値を設定します。 しかし、それは解決策ではないと思います。データの揺れはCAN捉えられますが、値は変です。 前の写真を見ると、気温は少なくとも 150 度を超えています。 Re: TempSense data is so weird.. こんにちは@rlaxortn 前回の回答では、「 MCU の電源電圧が 3.3V であるため 」 と おっしゃっていました。ここで、「 MCU VREFH は 5.0V です」と言います。本気ですか？ あなたの設定では、TempSense電圧供給は0x53、つまり5.3Vです。 ADC電圧リファレンスは53->0x35->3.5Vです 私たちは長い間話し合ってきましたが、あなたは同じ間違いを繰り返しています。 VREFH が 5V の場合は、両方の値を 0x50 に設定する必要があります。 次に、安定性を向上させるために、次のパラメータをより大きな値に設定して再度テストCAN。 Re: TempSense data is so weird.. @センレント 1. ソースコードを渡すのは難しいです。しかし、イメージキャプチャによって ADC 構成を提供することはCAN。それでいいでしょうか? 2. MCU VREFH は 5.0V、VREFL は 0V です。 Re: TempSense data is so weird.. こんにちは@rlaxortn 提供されたデータによると、ADC サンプリング結果は大きく変動します。これは、ADC サンプリング構成に何らかの問題があることが原因です。 1. プロジェクトをご提供いただければ、ADC設定の確認をお手伝いします 2. 現在のハードウェアの ADC リファレンス電圧を確認し、VREFH の実際の電圧をテストしてください。 Re: TempSense data is so weird.. @センレント 1. Tempsenseの電源電圧はどうすればわかりますか？MCUの動作電源がTEMPsenseの電源電圧ではないのでしょうか？それとも、TempsenseにはADCチャネルのように電圧を取得するための別のピンがあるのでしょうか？ 2. MCU 電源電圧は 3.3V であるため。SO、TempSense 電源電圧を 50(0x32) -> 3.2V に設定しました。 3. とにかくTempsense電源電圧をテストします、0x50（5.0V）、0x15(1.5V)、0x33(3.3V)。 0x50 を設定すると。 (TemperatureRaw は整数値、mcuTempData は印刷用の浮動小数点数です) 例) 2205 -> 0x89D 0x33(3.3V)を設定すると (TemperatureRaw は整数値、mcuTempData は印刷用の浮動小数点数です) 例) 2537->0x9e9 0x15(1.5V)に設定すると 例) 5515->0x158B Re: TempSense data is so weird.. こんにちは@rlaxortn ADC リファレンス電圧は 3.2V ですか? Re: TempSense data is so weird.. こんにちは@rlaxortn 訂正させてください。私の回答にはいくつか誤りがありました。 使用されたデータ形式はS11.4でした。 したがって、実際の値は、元の16ビット符号付き数値÷16となります。 例： 1.0×15 = 21 / 16 = 1.3125V 2.0×35 = 53 / 16 = 3.3125V 3.0×50 = 80 / 16 = 5V

如何从 Gui-Guider v1.9.1 获取详细的编译日志？ 我正在将一个项目从 Gui-Guider v1.5.0 升级到 Gui-Guider v1.9.1，但无法编译。它没有告诉我原因。我想知道如何获得未经过滤的实际编译日志（或如何从命令行执行命令）。 日志只显示 ... Compiling /home/user/GUI-Guider-Projects/Project2/lvgl-simulator/../generated/images/_fan_inverse2_64x64_alpha_48x48.c Compiling /home/user/GUI-Guider-Projects/Project2/lvgl-simulator/../generated/images/_nxcp_page_left_alpha_64x64.c Compiling /home/user/GUI-Guider-Projects/Project2/lvgl-simulator/../generated/images/_stop_pressed_alpha_64x64.c Compiling /home/user/GUI-Guider-Projects/Project2/lvgl-simulator/../generated/images/_system_alpha_135x100.c Compiling /home/user/GUI-Guider-Projects/Project2/lvgl-simulator/../generated/images/_tools_alpha_135x100.c Compiling /home/user/GUI-Guider-Projects/Project2/lvgl-simulator/../generated/guider_fonts/lv_font_NanumGothic_ExtraBold_24.c make: *** [Makefile:96: build/object/main.o] Error 1 make: *** Waiting for unfinished jobs.... Compilation failed! 我猜是链接阶段出了问题，但我不知道发生了什么。 如果我进入 Project2/lvgl-simulator 目录，并键入"make VERBOSE=1" 试图获取更多信息/控制权，它只会给出以下错误： Compiling /home/user/GUI-Guider-Projects/Project2/lvgl-simulator/main.c main.c:21:10: fatal error: widgets_init.h: No such file or directory 21 | #include "widgets_init.h" | ^~~~~~~~~~~~~~~~ compilation terminated. make: *** [Makefile:96: build/object/main.o] Error 1 这个奇怪的"widgets_init.h"在 Gui-Guider 内部编译时不会出现该错误，而且在穷举式递归 "查找 "中也没有发现 widgets_init.h文件，所以我真的很难弄清发生了什么或如何继续。 谁能告诉我如何从 Gui-Guider v1.9.1 中获取真正的调试日志？ 这个项目在 v1.5 版本下编译得很好，所以在新环境中一定有什么地方不同了。如果我能从链接命令中看到实际错误，可能就一目了然了。 此外，"widgets_init.h" 、我在哪里可以找到它？为什么在 Gui-Guider 内部编译时不会出现这种情况？ 感谢您的帮助。 Re: How to get detailed compile logs from Gui-Guider v1.9.1? 你好@AbelianMeme 能否共享您的项目，以便我重现这个问题？ BR 哈利

SA676DK/01 Hello! Could you please let me know if you have a Materials Declaration for the component SA676DK/01? Can you help with identifying the date code? Also, is it mandatory to see copper on the cross-section of the leads, or not? Thank you! Re: SA676DK/01 Hello Anton, I am sorry to say we cannot even confirm as this product is no longer supported and we do not have any related documentation at the disposal. We are very sorry for the inconvenience caused. Thank you for your understanding. Have a nice day. Best regards Pavla Re: SA676DK/01 Hello! Thank you for your response! I’d like to ask one more thing — is it acceptable for there to be no visible copper on the cut edges of the leads, so that the leads are completely covered with tin? I've attached a photo. Re: SA676DK/01 Dear Anton Kroessen, SA676DK/01 is obsolete part discontinued a long time ago. Therefore we do not have material composition at the disposal anymore. The only document I found with Alldatasheet: https://www.alldatasheet.com/datasheet-pdf/view/1072418/NXP/SA676.html Regarding the date code I would recommend you to contact a distributor where you bought the part. Thank you. Have a nice day. Pavla 

i.mx 93 evk へのカメラ移植と Zephyr こんにちは、みんな！初心者です NXP i.MX93 EVK のサポートに関する Zephyr のドキュメントを読みました。何が最善のアプローチなのか少し混乱しています。私の主な使用CASEはカメラの移植SO、Zephyr を A55 コアに移植する必要があると理解しています。Zephyr のリポジトリでいくつかの実験例を見たことがありますが、MIPI-CSI の公式サポートはありません。 もう 1 つの質問は、Zephyr を A55 と M33 の両方で実行する必要があるのか、それとも A55 だけで実行する必要があるのかということです。 ありがとう！ Re: camera porting and zephyr on i.mx 93 evk こんにちは@csalitre FRDM-93 ボード用の Bar スキャナー デモを開発中です。このデモは Zephyr OS、A55 コアで実行され、MIPI-CSI をサポートします。これはお客様の要件に非常に似ています。 よろしくお願いします。 ダニエル Re: camera porting and zephyr on i.mx 93 evk こんにちは、 i.MX93 の場合、リアルタイム制御には Zephyr が通常 M33 上で使用され、カメラとメディアのパイプラインは A55 上の Linux で処理されます。A55 上の Zephyr は現在、主に初期のドライバー導入に適しています。公式の MIPI-CSI カメラ サポートは、Zephyr ではまだ利用できません。 役に立つと思われる関連するアップストリームリファレンス: Linux カメラ ドライバ https://web.git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=fa9e6df636fb8b3b27570f38c53640c9e2b02f79 https://patchew.org/linux/[email protected]/[email protected]/ https://web.git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=5bd6b8c1bb2d49d5ff15c7c47d6b33d2d38785f0 Zephyrカメラドライバ https://github.com/zephyrproject-rtos/zephyr/commit/c784481ca039ccd606a192ee07bc83f6b0117e59 Silicon Signalsのカメラブリンドアップガイド https://siliconsignals.io/blog/v4l2-camera-stack-step-by-step-guide-for-custom-devices/ これが役に立つことを願います。

如何在 i.MX93 MaaxBoard (Cortex-M33) 上使用没有 TMR 输入的 GPIO 进行输入捕获？ 嗨，恩智浦社区、 我正在使用 MaaxBoard i.MX93 （Cortex-M33），正在尝试使用 TPM 外围设备（计时器）实现 输入捕获 。我知道要想正确捕获输入，GPIO 必须通过 IOMUX 支持 TPMX _Channely。 但是，我在 GPIO 引脚（例如 GPIO3_IO05）上有信号，它不支持 IOMUX 中的 TPM 捕获。 我能够通过 gpio_pinRead () 读取它的值并看到它在切换，但我想测量 脉冲宽度或 频率 （即高时间、低时间或边 缘时间戳）。 我的问题 是否有任何解决方法可以使用非 TMR 连接的 GPIO 进行输入捕获（例如，使用中断或轮询）？ 如果是，如何使用 SysTick 或其他定时器配置带有精确时间戳记录的 GPIO 中断？ 适用于 i.MX 93 的 MCUXpresso SDK 中是否有显示基于 GPI O 中断的边缘定时或脉冲测量的示例？ 关于通过 GPIO 上的纯软件方法进行精确定时测量的任何建议或最佳实践都将有所帮助。 谢谢您！ i.MX93 TPMS-SW MCXC Re: How to use GPIO without TMR input for input capture on i.MX93 MaaxBoard (Cortex-M33)? @Manuel_Salas 我试过只更改 app.h 中的配置部分，但检查后发现不起作用？ 我一直在开发 Maaxboard OSM93 板，里面我没有得到这个板的引脚，在用正确的引脚更新 pinmux 之后它也行不通？ Re: How to use GPIO without TMR input for input capture on i.MX93 MaaxBoard (Cortex-M33)? 你好@Manjunathb 您能试试 SDK 中的 TPM 示例吗？ 无需任何修改即可运行。 顺祝商祺！ 萨拉斯 Re: How to use GPIO without TMR input for input capture on i.MX93 MaaxBoard (Cortex-M33)? 你好@Manuel_Salas 我更新了 app.h和pinmux.c内部输入捕获驱动程序代码，尽管它不起作用。 当特定的引脚变高和低电平时，它无法触发信号（无法读取输入值）有什么问题？ i.MX93 TPMC-PEXPERT Re: How to use GPIO without TMR input for input capture on i.MX93 MaaxBoard (Cortex-M33)? 你好@Manjunathb 希望你一切都好。 遗憾的是，我们没有一个不使用 TPM PAD 的例子。 但查看一下 MaaxBoard，似乎可以用 GPIO12 来实现： 你可以使用 SDK 上的 TPM 示例，因为使用的是 PAD： 顺祝商祺！ 萨拉斯

TEF82XX ATB Issue Hello, I would like to test by bypassing the ADC and directly testing the RX to the analog port. We will use a spectrum analyzer to view the internal analog signals. May I ask where the relevant registers are located? Because I only saw the clock and power control related registers for the ADC and ATB. There is no reserved ATB port? Or is the RC receiving data default sent to the ADC and ATB port and no need for switching?  In register R2M0A_LO_INTERFACE_CONTROL_U16:0x000, I saw the enable settings for buffers B3, B2, and B1. However, I couldn't find the corresponding positions in the schematic. Could you please help me identify the locations? Or is it that the TEF82xx does not have these buffers? Re: TEF82XX ATB Issue Hello, I was talking with TEF82xx FAE and the ATB is internal and wont be discussed with customer. I recommend you to get in touch with NXP FAE/Sales for further questions as such will require NDA at minimum, Best regards, Peter 回复： TEF82XX ATB Issue Buffers B1 to B4 have been found in the data sheet. Thank you.

Can_Llce_DS_Can2Can の例を変更して物理 CAN ピンで送信するにはどうすればよいでしょうか? こんにちは、コミュニティの皆様 私は、 S32 Design Studio 3.5に含まれ、 S32G-VNP-RDB3ボード上で実行されるCan_Llce_DS_Can2Can_S32G399A_M7の例を使用しています。Multilink Universalデバッガーを使用して、プロジェクトをM7_0 コアにロードしています。 例の説明によると、このデモはCAN_LLCE ドライバの内部 CAN2CAN ルーティング機能を示しています。ただし、必要なのは、この例を変更して、CAN メッセージがコントローラの CAN ピンで物理的に送信され、 PCAN-USB FDなどの外部アナライザーを使用してキャプチャできるようにすることです。 構成ファイル (Can_43_LLCE_VS_0_PBcfg.c) を確認したところ、Can2Can ルーティング エントリを参照する高度なフィルター (Llce_Can_AdvancedFilterType) が使用されていることに気付きました。私の理解する限り、これはフレームが物理バスから出ていくことはないことを意味します。 私の目標: 内部配線を削除する 通常のフィルタとHOHを設定して、物理CANピンを介した送信を許可します。 外部スニファー（PCAN）でCANメッセージを視覚化する 質問: これを実現するためにこの例を変更するための公式ガイドや推奨事項はありますか? 高度なフィルターを削除して CAN_43_LLCE_RECEIVE と CAN_43_LLCE_TRANSMIT を使用するだけで十分ですか、それとも追加の変更 (トランシーバの設定、ピン構成、クロックなど) が必要ですか? サポートをよろしくお願いいたします！ Re: How to modify Can_Llce_DS_Can2Can example to transmit on physical CAN pins? こんにちは@aarfer3800 例を視覚的に表すには、インストール ディレクトリの llce_sample_app_af にある README ファイルを参照してください。そこには次の内容が記載されています。 main.c ファイルには、現在の構成でメッセージ フローがどのように機能するかを説明するコメントが含まれています。ConfigTools を使用して、高度なフィルターと LLCE の構成を確認および調整することもCANます。 デモ アプリケーションに示されているように、データはコントローラ 1 からコントローラ 0 に外部的に送信されます。その後、同じメッセージがチャネル 15 に内部的にルーティングされ、フレームはコントローラ 14 に外部的に転送されます。 このシナリオでは、高度なフィルターを削除すると、コントローラ 0 からチャネル 15 へのメッセージは内部的にルーティングされず、チャネル 15 とコントローラ 14 間の送信は行われません。 ご不便をおかけして申し訳ございませんが、お客様のアプリケーションを満たす具体的な例がございませんので、開発プロセスはお客様側で実行していただく必要があります。 実装中に問題が発生した場合は、お気軽にお問い合わせください。他に何かお手伝いできることがございましたら、遠慮なくお知らせください。

MIMXRT595-EVK SPI 信号电压问题 - 获得 1.8V 而非 3.3V 电压 我的 MIMXRT595-EVK 上的 SPI 信号输出电压为1.8V，而不是 3.3V。我的 SPI 设备需要 3.3V 的电压。 硬件：MIMXRT595-EVK + Zephyr v4.1.0 SPI：HS_SPI1（引脚 PIO1_3、PIO1_4、PIO1_5） 当前配置 设备树（叠加层）： & hs_spi1 { #address-cells =;<1> #size-cells =;<0> 测试设备：spi-device @0 { 兼容 = " spi-device "; reg =;<0> spi-max-frequency = < <80000000> 80000000 >;};}; 引脚配置：（DTiS 文件） pinmux_flexcomm16_spi: pinmux_flexcomm16_spi { group0 { pinmux = , , ; input-enable; slew-rate ="normal"; drive-strength ="high"; }; }； 问题 如何为 3.3V 操作配置 I/O 功能域？ Zephyr v4.1.0 中 PCA9420 PMIC 的正确配置是什么？ 我需要将板跳线设置为 3.3V 吗？ 其他信息 出现 Kconfig 错误：未定义符号 PMIC_PCA9420 示波器确认输出电压为 1.8V 显示器 SPI 通信需要 3.3V 电压 寻找：正确的设备树配置或 PMIC 设置以获得 3.3V SPI 信号。 Re: MIMXRT595-EVK SPI Signal Voltage Issue - Getting 1.8V Instead of 3.3V 你好@luqman82303 感谢您的联系！ 根据 DS，您需要的 SPI 接口引脚（HS_SPI1（引脚 PIO1_3、PIO1_4、PIO1_5））不支持3.3v 电源。这意味着它们无法提供 3.3v 电压。 因此，您仍然可以通过实现自己制造的外部电压等级转换器适配器电路来使用它们。作为替代方案，请检查使用 VDDIO_3 引脚是否可行， 因为 VDDIO_3 可以支持 1.8V 和 3.3V。为此，您可以首先使用我们的配置工具引脚工具检查 VDDIO_3 引脚上的 SPI 复用替代方案。根据我在 EVK 上看到的情况，VDDIO_3 已经被供电到 3.3 伏。因此，这可能是一个可行的解决方案。 此外，请检查这些引脚是否可以从 EVK 引出并连接，如果不能，您就必须进行定制设计来测试它们。 我还没有讨论 PMIC 设置和您遇到的错误，因为我想指出 VDDIO_3 引脚选项。 迪亚戈

Copy: [RTD] MPU cache setting for multicore in RTD's SW arch This post is a copy from here Hi: customer use case: multicore , single image . multicore share the same code and data area. questions: for this use case, it is needed to set the section such as 'mcal_data, mcal_bss' in each core's MPU with shareable attribution ? because according to ARM manual , once this MPU set to shareable, it's lost cache function. and will lost a lot of performance for total application. if RTD internal can help solved data consistency issue here, and no need to set shareable, it could be very great for performance improvment. Please help confirmed with SW team , thanks ! Best regards ives CHENG Priority: MEDIUM RTD Re: Copy: [RTD] MPU cache setting for multicore in RTD's SW arch Hi @Luis_Garabo , You means a project that uses single elf,  some modules like: CAN uses 2 cores: core 0 and core 1. but PWM just use only one core 0. Then, you want to can_bss, can_data was assigned into shareable memory, but pwm_bss, pwm_data was assigned into non-shareable memory, right? If RTD driver supports this, we will need to divide memory for all modules, like: for multiple cores used: Eth_bss_shareable, Can_bss_shareable,... and for modules just use only one core: Eth_bss_core0, Eth_bss_core 1, Can_bss_core0, Can_bss_core1,... And in linker file, we need to divide each memory region for these parts of each modules, and these memory regions were fixed with size although we don't know how much memory these modules used. Anyway, this is too complicated from my point of view. If you want to support it in your case, you can change MemMap.h and linker file by yourself. Best regards, Nhi Re: Copy: [RTD] MPU cache setting for multicore in RTD's SW arch Hi Nhi, Thanks for the answer. Now,  What about the following. For some MCAL module which used only on 1 core, could the RTD driver provide the options to decoupled this part’s data, and let user to place in suitable sections? For example, a multicore system where the PWM is controlled and usage is on core0, then all PWM data can be cacheable on core0. Current RTD integrates all module’s data into MCAL_data, bss … The suggestion is to provide a switch to generate a standalone section for each module It could be placed in BASENXP to generate a suitable memory map file. Could this be possible? Best Regard, Luis Re: Copy: [RTD] MPU cache setting for multicore in RTD's SW arch Hi @Luis_Garabo , For the case multiple core with single elf, you just have only one linker file as below: mcal_bss, mcal_data are included in int_sram and you will have to set this memory region to shareable to multiple cores can access to it. For multiple cores with multiple elf, each core uses a linker file, so mcal_data, mcal_bss is individual memory regions and you can set them to non-shareable as below: For case 1, if you don't want to set mcal_data, mcal_bss to shareable but still want it operates in multiple cores, this means that for example if you have a variable A, in core 0, you store A to memory region of core 0, core 1 you store A to memory region core 1, but you just have 1 elf, this means that A is declared by 2 times. This is impossible from my point of view. I don't think that RTD driver can do anything in this case, if you want to use cache, you can switch to case multiple elf. Best regards, Nhi

Copy: [RTD] Recommend build optimized options change This post is a copy from here Hi:  since more and more customer are caring about performance of device. but our RTD still using size optimized options in the manual (-Os/ Osize ) this will caused some performance issue in some applications. Could you please help suggest SW change the standard build options to  -O1(or O2 in GCC) -Ogeneral ( GHS) for better performance ? this will help customer improve our device performance. Best regards Ives CHENG Priority: MEDIUM RTD Re: Copy: [RTD] Recommend build optimized options change Hi @Luis_Garabo, I answered directly to Ives Cheng in your attached link. Best regards, Dan

TEA1716T PFC current sense pin We are having trouble with our product malfunctioning due to noise entering pin 4 "SNSCURPFC" of the TEA1716T. Therefore, we would like to connect a capacitor to remove the noise entering pin 4 to GND. Is it possible to connect a capacitor between pin 4 "SNSCURPFC" and GND to stabilize the PFC operation of the TEA1716T? And please tell me up to what pF a capacitor can be connected. Re: TEA1716T PFC current sense pin Thanks for the reply. The problem is solved! Re: TEA1716T PFC current sense pin Yes you can! Re: TEA1716T PFC current sense pin Thank you for reply. Noise interference on pin 4 "SNSCURPFC" caused the PFC OCP to malfunction. Inserting a Cstart(soft) capacitor did not improve the situation, but connecting a 220pF capacitor between pin 4 and GND fixed the malfunction. Is it permissible to connect a capacitor between pin 4 and GND?   Re: TEA1716T PFC current sense pin Hi We recommend current sense circuit below,what kind of noise did you found? If the high frequency noise you can try to connect nf level capacitor to try test.

Usage of diag functions in the etpu_resolver.h file of the MCSPTR2AK396_PMSM_FOC_3Sh_SwRes project 1. How to use the DIAG interface as shown in the figure? 2. And what is the usage of the variable chan_num_diag in the structure resolver_instance_m1 during the initialization of the function fs_etpu_resolver_init? 3. Is this channel an output interface? 4. Does it output the internal errors of ETPU? 5. How should I use it? Note: I have not used the configuration functions of RTD and MCAL. All codes are written manually. Re: Usage of diag functions in the etpu_resolver.h file of the MCSPTR2AK396_PMSM_FOC_3Sh_SwRes proje Thank you for your interest in our products and for contributing to our community. For more details about eTPU RDC function implementation please refer to eTPURDCCUG - eTPU RDC and RDC Checker User Guide. On the other hand, you could refer to EV-INVERTERGEN3, which use the S32K3 eTPU software AUTOSAR 4.7 Version 2.0.0 Code Drop 04. I hope this information is helpful.