Multi Source Translation Content

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

Multi Source Translation Content

Discussions

Sort by:
LIBUSB_ERROR_NO_DEVICE Hi, I am having an issue while flashing.i am using an imx8mp processor. vougavent@vougavent-work-station1:~/Desktop/imx-yocto-bsp/build-wayland2/tmp/deploy/images/imx8mp-lpddr4-evk$ sudo uuu -v -b emmc_all imx-boot-imx8mp-lpddr4-evk-sd.bin-flash_evk core-image-weston-imx8mp-lpddr4-evk-20260725065928.rootfs.wic.bz2 uuu (Universal Update Utility) for nxp imx chips -- lib1.4.193 Build in config: Pctl Chip Vid Pid BcdVersion ================================================== 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 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 Run built-in script: uuu_version 1.4.149 # @_flash.bin | bootloader, which can extract from wic image # @_image [_flash.bin] | wic image burn to emmc. # This command will be run when i.MX6/7 i.MX8MM, i.MX8MQ SDP: boot -f imx-boot-imx8mp-lpddr4-evk-sd.bin-flash_evk -scanlimited 0x800000 # This command will be run when ROM support stream mode # i.MX8QXP, i.MX8QM SDPS: boot -scanterm -f imx-boot-imx8mp-lpddr4-evk-sd.bin-flash_evk -scanlimited 0x800000 # These commands will be run when use SPL and will be skipped if no spl # SDPU will be deprecated. please use SDPV instead of SDPU # { SDPU: delay 1000 SDPU: write -f imx-boot-imx8mp-lpddr4-evk-sd.bin-flash_evk -offset 0x57c00 SDPU: jump -scanlimited 0x800000 # } # These commands will be run when use SPL and will be skipped if no spl # if (SPL support SDPV) # { SDPV: delay 1000 SDPV: write -f imx-boot-imx8mp-lpddr4-evk-sd.bin-flash_evk -skipspl -scanterm -scanlimited 0x800000 SDPV: jump -scanlimited 0x800000 # } FB: ucmd setenv fastboot_dev mmc FB: ucmd setenv mmcdev ${emmc_dev} FB: ucmd mmc dev ${emmc_dev} FB: flash -raw2sparse all core-image-weston-imx8mp-lpddr4-evk-20260725065928.rootfs.wic.bz2/* FB: flash -scanterm -scanlimited 0x800000 bootloader imx-boot-imx8mp-lpddr4-evk-sd.bin-flash_evk FB: ucmd if env exists emmc_ack; then ; else setenv emmc_ack 0; fi; FB: ucmd mmc partconf ${emmc_dev} ${emmc_ack} 1 0 FB: done Wait for Known USB Device Appear... New USB Device Attached at 1:10 1:10>Start Cmd:SDPS: boot -scanterm -f imx-boot-imx8mp-lpddr4-evk-sd.bin-flash_evk -scanlimited 0x800000 33%1:10>Fail HID(W):LIBUSB_ERROR_NO_DEVICE(0.786s) i.MX 8 Family | i.MX 8QuadMax (8QM) | 8QuadPlus Re: LIBUSB_ERROR_NO_DEVICE Hi, Thank you for your interest in NXP Semiconductor products, In your setup do you use a custom board or an i.MX 8M Plus EVK? If you are using a custom board I would advise to modify the necessary code, focusing in memory and power necessary differences. Then confirming your porting is valid and being applied. The error is seen when using an invalid imx-boot firmware image, another reasons can be defective cables or some USB power sources reset, you could try using a wall mount USB charger. Regards, Re: LIBUSB_ERROR_NO_DEVICE Hi @JosephAtNXP , Sorry for the inconvenience,it was a simple current shortage that caused the issue,when i raised the current to the required level,everything is working fine.
View full article
LX2160ARDB: DDR検証 こんにちは、 LSDKからRCWファイル(rcw_2200_750_2900_19_5_2.bin)をSDカードにロードし、DDR構成パネルでRead SPDを実行すると、 「サポートされていない生カードリビジョンです。CLKをDQSスキュー値に手動で設定してください。」というメッセージが表示されます。 QCVSツールでLX2160ARDBのDDR検証を実行する方法 Priyaa_0-1788337942087.pngPriyaa_0-1788337942087.pngPriyaa_0-1788337942087.pngPriyaa_0-1788337942087.pngPriyaa_0-1788337942087.pngPriyaa_0-1788337942087.pngPriyaa_0-1788337942087.pngPriyaa_0-1788337942087.pngPriyaa_0-1788337942087.png Re: LX2160ARDB: DDR validation こんにちは、ジューン・ルーさん サポートありがとうございます USBの場合、コマンドの結果は (ビン)51% findcc cwtaps 0 (ビン)51% イーサネット接続用 (bin) 51% findcc cwtaps FSL07E3D5 (10.1.66.150):CodeWarrior TAP v2 Cortex-10 プローブチップ ブートローダー v1.0.1 オペレーティングシステム v1.0.5 1 今のところ、DDR検証のためにイーサネット接続を使ってさらに進めてもいいでしょうか? Re: LX2160ARDB: DDR validation (バイナリ)52%表示cc 0: USB接続の失敗 コマンドコンバーターは構成されていません これは、CWTAPがUSB接続から検出できないことを示しています。 USBケーブルの接続を確認し、CWTAPがホストPCに正しく認識されていることを確認してください。 また、以下のコマンドを実行して結果を共有してください。 (bin) 6% findcc cwtaps ありがとうございます。 Re: LX2160ARDB: DDR validation こんにちは、ジューン・ルーさん CodeWarrior バージョン- Priyaa_0-1788417354430.pngPriyaa_0-1788417354430.pngPriyaa_0-1788417354430.pngPriyaa_0-1788417354430.pngPriyaa_0-1788417354430.pngPriyaa_0-1788417354430.pngPriyaa_0-1788417354430.pngPriyaa_0-1788417354430.pngPriyaa_0-1788417354430.png (ビン)49% log v CCS Linuxリリースビルド 503.0.0.220812-p0 詳細ログ記録 (ビン)50%全て削除 (ビン)51%構成CCのCWTAPです。 (ビン)52%、CCを表示 0: USBオープン失敗 コマンドコンバーターは構成されていません (ビン)53% (bin) 53% source IDcode.tcl(bin) USB接続で利用可能なTAPをスキャンしています..... USB接続のTAPは見つかりませんでした ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + + 利用可能なリモート接続 + + 1 - CodeWarriorTAP - + 2 - GigabitTAP - + + x - 変更せずにスクリプトを終了 + ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 接続を指定してください: 「CONNECTION()」を読み取れません:配列にそのような要素はありません (ビン)54% (ビン)54% イーサネット経由で接続し、ターゲットにpingを送ることができます。CodeWarriorをv11.5.12にアップデートした後でも、SPDの読み取り時に「サポートされていない生カードリビジョンです。CLKをDQSスキュー値に手動で設定してください。」という同じメッセージが表示されます。 よろしくお願い申し上げます。 Re: LX2160ARDB: DDR validation CodeWarrior版は、QorIQ LSシリーズ(ARM v8 ISA)向けCodeWarrior開発スタジオについてHelp →から確認してください。 接続状態を確認するには、「CCS Windows Release Build 503.0.0.220812-p0.txt」に記載されている手順に従ってください。 まずUSB接続をテストし、その後イーサネット接続を試すことをおすすめします。 IPアドレスが変更されたようです。ターゲットに正常にpingが届くかどうか確認いただけますか? Re: LX2160ARDB: DDR validation こんにちは、ジューン・ルーさん CodeWarrior 11.5.0を使用しており、DIMMはLX2160ARDBに付属していた純正モジュールです。 CodeWarriorをアーカイブcom.freescale.armv8.11.5.12.GA.Lin.updatesite.221209.zipで更新バージョン11.5.12の場合 JTAGを検出できなくなりました Priyaa_0-1788412965825.pngPriyaa_0-1788412965825.pngPriyaa_0-1788412965825.pngPriyaa_0-1788412965825.pngPriyaa_0-1788412965825.pngPriyaa_0-1788412965825.pngPriyaa_0-1788412965825.pngPriyaa_0-1788412965825.pngPriyaa_0-1788412965825.png よろしくお願い申し上げます。 Re: LX2160ARDB: DDR validation あなたの指示通りに操作したところ、SPDを正常に読み取ることができました。 どのバージョンのCodeWarriorを使っているのか確認していただけますか?CodeWarrior 11.5.12ですか? また、そのDIMMは純正品ですか? ありがとうございます。 Re: LX2160ARDB: DDR validation こんにちは、ジューン・ルーさん FlexSPI経由で起動した後、u-bootでtftpboot経由でRCWファイルをロードし、以下のmmc書き込みコマンドを実行しました。 => tftpboot 0x90000000 rcw_2200_750_2900_19_5_2.bin => mmc dev 0; mmc write 0x90000000 8 1 => qixis_reset sd (このコマンドの実行中にD19の電源がオン/オフされました) また、DDR構成の場合、SPDから読み取ると「サポートされていない生カードリビジョンです。CLKをDQSスキュー値に手動で設定してください。」というエラーが表示されます。 Re: LX2160ARDB: DDR validation LSDKからRCWファイル(rcw_2200_750_2900_19_5_2.bin)をSDカードにロードするにはどうすればよいですか? D19は電源のオンオフを繰り返しましたか? QCVSツールでのDDRのLX2160ARDB検証については、以下を参照できます: QCVS_DDR_ユーザーガイド よろしくお願いします。 Re: LX2160ARDB: DDR validation こんにちは、ジューン・ルーさん イーサネット経由で接続し、テキストファイルに記載されている通りLX2160Aを見つけることができます Priyaa_0-1788427814124.pngPriyaa_0-1788427814124.pngPriyaa_0-1788427814124.pngPriyaa_0-1788427814124.pngPriyaa_0-1788427814124.pngPriyaa_0-1788427814124.pngPriyaa_0-1788427814124.pngPriyaa_0-1788427814124.png しかし、DDR設定ウィンドウでSPDを読み取ると、「サポートされていない生カードリビジョンです。CLKをDQSスキュー値に手動で設定してください。」と表示されます。 SPD値が正常に読み取られたことを確認するにはどうすればよいでしょうか? Re: LX2160ARDB: DDR validation (bin) 50%すべて削除 (bin) 51 % config cc cwtap:10.1.66.150 (バイナリ)52%表示cc (bin) 53% ソース IDcode.tcl もし「CCS Windows Release Build 503.0.0.220812-p0.txt」と同じものが見つかればLX2160A。 DDRの検証にはIPアドレス10.1.66.150のイーサネット接続を使うことができます。 よろしくお願いします。 Re: LX2160ARDB: DDR validation これが成功時のスクリーンショットです。 June_Lu_0-1788429917395.pngJune_Lu_0-1788429917395.pngJune_Lu_0-1788429917395.pngJune_Lu_0-1788429917395.pngJune_Lu_0-1788429917395.pngJune_Lu_0-1788429917395.png USBを使ってCWTAPに接続しました。プローブに正しいIPアドレスを設定する必要があります。 「接続診断」を成功裏に実行できましたか? June_Lu_1-1788430165643.pngJune_Lu_1-1788430165643.pngJune_Lu_1-1788430165643.pngJune_Lu_1-1788430165643.pngJune_Lu_1-1788430165643.pngJune_Lu_1-1788430165643.png Re: LX2160ARDB: DDR validation 接続診断が正常に完了しました Priyaa_0-1788431456696.pngPriyaa_0-1788431456696.pngPriyaa_0-1788431456696.pngPriyaa_0-1788431456696.pngPriyaa_0-1788431456696.png SPD読み取り後のDDR構成は以下のとおりです。 Priyaa_1-1788432417841.pngPriyaa_1-1788432417841.pngPriyaa_1-1788432417841.pngPriyaa_1-1788432417841.pngPriyaa_1-1788432417841.png DDRの検証が順調に開始されているか確認していただけますか? というのも、検証開始ボタンが有効になっているにもかかわらず、検証開始直後にキャンセルされてしまうという問題が発生しているからです。 Re: LX2160ARDB: DDR validation こんにちは、ジューン・ルーさん ユーザーガイドに従い、再びDDRの設定とSPDの読みのためのプロジェクトを作成しました。以下の通りです Priyaa_0-1788498272408.pngPriyaa_0-1788498272408.pngPriyaa_0-1788498272408.pngPriyaa_0-1788498272408.png DIMMモジュールはRDBのJ14、J17コネクタに挿入されます。 Re: LX2160ARDB: DDR validation あなたのスクリーンショットは私のものと同じではないようです。「戻る」ボタンと「キャンセル」ボタンがありません。 QCVS_DDR_User_Guide 1.1.1 に従いましたか?DDR設定ツールを使用していますか? よろしくお願いします。 Re: LX2160ARDB: DDR validation こんにちは、ジューン・ルーさん スイッチ(SW1)をRCWソースが存在するSDカードモードに変更した後、検証を行うことができました。 サポートありがとうございます... Re: LX2160ARDB: DDR validation SPDの読み取りは正常に完了したようですが、スクリーンショットは私の画面で表示されるものと若干異なっています。 DDR検証用にRCWソースが構成されているeMMCから起動するには、SW1[1:4]を1001に設定してください。 また、「ターゲット接続」がコネクテッドと表示されているか、スクリーンショットをご覧ください。 確認が完了したら、DDRの検証を進めることができます。 June_Lu_0-1788504721222.png Re: LX2160ARDB: DDR validation こんにちは、ジューン・ルーさん LX2160ARDBをSDカードから起動するには、u-bootソース内のDDRレジスタ値を変更する必要がありますか、それともDIMMのSPDから読み取りますか? ご説明いただけますでしょうか…ありがとうございます。 Re: LX2160ARDB: DDR validation DIMMスロットを備えた標準のLX2160ARDBでは、DDRレジスタは、インストールされているDIMMからSPDを読み取ることで自動的に構成されます。これはU-Bootではなく、TF-A BL2ステージ(ddr_init.c)によって処理されます。LX2160ARDBでカスタムDIMMを使用する場合にのみ、ATFソースを変更する必要があります。 もし新しい質問があれば、適切に追跡できるよう新しいスレッドを作成してください。このケースはかなりの間活動が停止しています。 ありがとうございます。
View full article
S32 Design Studio: Add UART to the Imported Project using AI Introduction In Tutorial 1, the AI agent imported the GPIO Blinking LED Demo and ran it on the FRDM-A-S32K312 board. This second article extends that project with two new features: a multi-color LED sequence, and a UART output that reports what the board is doing.   Using S32 Configuration Tools, you will map LPUART6 pins (PTA15 / PTA16), configure the peripheral at 115200 baud, regenerate code, and flash the firmware so the board echoes the current LED color over UART to a serial terminal.  Estimated time: ~20 minutes. System Architecture   Add UART to the Imported Project – system architecture overview   The components involved are:   FRDM-A-S32K312 – Target evaluation board. Runs GPIO Blinking LED firmware with LPUART6 enabled on PTA15 (RX) / PTA16 (TX). Transmits the current LED color over UART at 115200 baud. Host PC – Runs S32 Design Studio and the S32 Design Studio AI Support. A serial terminal (e.g. VS Code Serial Monitor) receives and displays the LED colour echo at 115200 / 8N1. Prerequisites   What you need before starting   Tutorial 1 completed — the GPIO Blinking LED Demo for FRDM-A-S32K312 must already be imported and building in S32 Design Studio One FRDM-A-S32K312 evaluation board + USB cable A serial terminal application (e.g. PuTTY, Tera Term, or VS Code Serial Monitor) S32 Design Studio AI Support configured (download, install and configure it following the steps from Installation & Usage Guide)   Note: This tutorial uses these paths: Installation: C:\NXP\2026\K3_kit\S32DS_3.6.8 Workspace: C:\NXP\2026\K3_kit\workspace_S32DS_3.6.8_K3_kit You can use any location. If you do, update the paths in the prompt to match. Connect the FRDM-A-S32K312 board to the PC via USB. Open Device Manager → Ports and note the virtual COM port number – you will need it for the serial terminal. Steps   Send the following prompts to your AI assistant in order. Each prompt is a complete, self-contained instruction.   Step 1 – Add RGB LED cycling (red → green → blue) In S32DS, use the dm-gpio-blinky-s32k312 project on a S32K312 FRDM board. Add pins PTA30 and PTA31 in the Pins tool (green and blue of the on-board RGB LED; red is the existing PTA29). In the existing blink cycle where the red LED is toggled, replace it with a switch-case that lights one color at a time, cycling red -> green -> blue, ~500 ms each. Important: these RGB LEDs are active-low. Confirm the polarity from the board schematic/user guide before writing GPIO values. Map: red=PTA29, green=PTA30, blue=PTA31. Then generate code and build (report any errors) and flash/run it. Use the s32ds-agentic-ai MCP server for all IDE/config/flash actions; if the MCP server disconnects at any point, stop immediately and notify me. AI will:   Open Pins Tool and add PTA30 (green) and PTA31 (blue) alongside existing PTA29 (red) Replace the existing blink loop with a switch-case cycling red → green → blue, ~500 ms each Respect active-low polarity, confirmed from board schematic/user guide Click Generate Code, build and report any errors Flash and run the firmware on the FRDM-A-S32K312 board Stop and notify the user immediately if the s32ds-agentic-ai server disconnects   Step 2 – Add UART functionality to echo the LED colour Add UART functionality to echo the color of the LED (RED, GREEN, BLUE) but keep it lightweight by using the LPUART IP-layer: - In Pins tool: map the PTA15 as LPUART6_RX and PTA16 as LPUART6_TX pins - In Peripherals tool: set LPUART_6 channel configured for baudrate 115200 / 8 data bits / no parity / 1 stop bit Then generate code and build (report any errors) and flash/run it. Use the s32ds-agentic-ai MCP server; if the MCP server disconnects at any point, stop immediately and notify me. AI will:   Open Pins Tool and map PTA15 → LPUART6_RX and PTA16 → LPUART6_TX Open Peripherals Tool and configure LPUART6: 115200 baud / 8 data bits / no parity / 1 stop bit Click Generate Code, build and report any errors Flash and run the firmware on the FRDM-A-S32K312 board Stop and notify the user immediately if the s32ds-agentic-ai server disconnects Verifying the Result   Work through this final check to confirm that both prompts completed successfully.   Final check Build completes with zero errors. Firmware is flashed and running on the FRDM-A-S32K312 board (RGB LED is blinking). Open a serial terminal at 115200 baud / 8N1 on the board's COM port. Confirm messages such as LED: RED, LED: GREEN, LED: BLUE appear in sync with the physical LED colour changes. Troubleshooting   Symptom Fix No UART output in serial terminal Open Pins Tool. Confirm PTA15 → LPUART6_RX and PTA16 → LPUART6_TX are routed. Regenerate code after any change. LPUART6 not found or not initialised Open Peripherals Tool. Verify LPUART6 is enabled and configured: 115200 baud / 8 data bits / no parity / 1 stop bit. Regenerate code if you make changes. LPUART6 absent at runtime Open Peripherals Tool › McuPartition. Enable LPUART6 in the partition configuration, then regenerate and rebuild. Garbled characters in serial terminal Baud rate mismatch. Confirm the terminal is set to 115200 and the peripheral configuration matches. Regenerate code after any baud rate change. Build errors after Generate Code Check that the generated LPUART6_init() call is present in main.c and that the correct header is included. Re-run Generate Code if source files are missing. LED colour not echoed over UART Confirm the UART transmit call is placed after each LED colour change in the main loop. Verify LPUART6_init() is called before the loop starts. Wrong COM port in serial terminal Open Device Manager → Ports and identify the virtual COM port assigned to the FRDM-A-S32K312 board. Use that port number in your terminal application. s32ds-agentic-ai server disconnects during operation Stop immediately and restart the MCP server following the setup instructions. Do not continue until the server is confirmed connected. File Reference   File Step Description src/main.c 2 Main firmware file — contains LED loop and LPUART6 transmit calls generate/src/Lpuart_Uart_Ip_PBcfg.c 1 Generated LPUART6 peripheral configuration generate/include/Lpuart_Uart_Ip_Cfg.h 1 Generated LPUART6 configuration header *.mex 1 S32 Configuration Tools project file (Pins, Clocks, Peripherals)   Map the pins, configure LPUART6 and regenerate – your board now reports every LED colour change over UART in about 20 minutes. Examples
View full article
S32 Design Studio: Add FreeMASTER Lite Configuration to Existing UART Project using AI Introduction In Tutorial 2, the application was extended to cycle the FRDM-A-S32K312 board's RGB LED through red, green, and blue, while sending corresponding status messages to a serial terminal. This third article shows how to add a FreeMASTER Lite server configuration using S32 Design Studio AI Support to an existing UART project on the FRDM-A-S32K312 board and create a browser dashboard that displays the current LED color – replacing the plain UART color echo.   Estimated time: ~20 minutes. System Architecture Add FreeMASTER to existing UART project – system architecture overview   The components involved are:   FRDM-A-S32K312 – Target evaluation board. Runs the existing UART project extended with FreeMASTER TSA, streaming the LED colour variable to the host over USB at 115200 baud. Host PC – Runs FreeMASTER Lite (fmlite.exe) on the board's COM port, 115200 baud, port 8090. Serves the LED colour dashboard to the browser. Prerequisites   What you need before starting   Tutorial 2 completed — the GPIO Blinking LED Demo with UART must already be imported and building in S32 Design Studio One FRDM-A-S32K312 evaluation board + USB cable Download and install FreeMASTER Lite (fmlite.exe) from LINK  Any modern browser (Chrome / Edge / Firefox) S32 Design Studio AI Support configured in your agent (download, install and configure it following the instruction from Installation & Usage Guide)    Note: This tutorial uses these paths: S32 Design Studio Installation: C:\NXP\2026\K3_kit\S32DS_3.6.8 Workspace: C:\NXP\2026\K3_kit\workspace_S32DS_3.6.8_K3_kit FreeMASTER Installation: C:\NXP\2026\K3_kit\FM_32 You can use any location. If you do, update the paths in the prompt to match. Connect the FRDM-A-S32K312 board to the PC via USB, open Device Manager → Ports (COM & LPT) and note the virtual COM port number. You must know this port before sending the prompt below — replace every COM# in the prompt with your own port (for example COM7), otherwise FreeMASTER Lite cannot open the serial connection to the board. Steps   Send the following prompt to your AI assistant. It is a complete, self-contained instruction. Replace COM# with the COM port of your board before sending.   Step 1 – Create FreeMaster Lite dashboard and server configuration Using FreeMaster Lite create a self contained web dashboard and the server configuration file in the project folder called dashboard. FreeMaster Lite is installed at c:\NXP\2026\K3_kit\FM_32\FreeMASTER Lite\fmlite.exe The dashboard should have a volatile variable that will be used to reflect the color of the RGB LED At the top should have the controls for the board serial connection, default: connection name "S32K312 RGB Board", COM#, 115200 baud, 8 data bits, no parity, 1 stop bit The board is connected on COM# - use this serial port for the FreeMaster Lite connection The project is a plain GPIO demo with no FreeMASTER driver - add whatever is needed on the target side so it can talk to FreeMaster Lite, then build and flash it in S32DS and confirm the color actually changes from the dashboard. Start FreeMaster server and run the dashboard at the end Use the s32ds-agentic-ai MCP server; if the MCP server disconnects at any point, stop immediately and notify user. AI will:   Create a self-contained web dashboard in the dashboard project folder Create a FreeMASTER Lite server configuration file in the same folder Add a volatile variable to reflect the RGB LED colour in the dashboard Add serial connection controls at the top (name: S32K312 RGB Board, COM#, 115200 baud, 8N1) Start the FreeMASTER Lite server and open the dashboard in the browser Stop and notify the user immediately if the s32ds-agentic-ai server disconnects Verifying the Result   Work through this final check to confirm that the prompt completed successfully.   Final check FreeMASTER Lite server is running with no errors. Open http://localhost:8090 in your browser. The LED colour dashboard loads and shows the current LED colour within ~5 seconds. The displayed colour changes in sync with the physical LED on the board. Troubleshooting   Symptom Fix ReadTSA returns count=0 TSA not enabled (FMSTR_USE_TSA 1) or FMSTR_Poll() missing. StartComm times out Wrong COM port in .fmcfg, baud mismatch, or board not powered. fmlite.exe exits immediately Activation code not entered, or path has spaces — wrap in quotes. LPUART0 baud rate wrong or peripheral not running Open Peripherals Tool. Verify LPUART0 is enabled and its clock source is set to AIPS_PLAT_CLK. Regenerate code if you change anything. LPUART0 absent at runtime Open Peripherals Tool › McuPartition. Enable LPUART0 in the partition configuration, then regenerate. FreeMASTER host times out or drops connection FMSTR_Poll() must be called frequently — place it in the main loop or a fast periodic task. The host requires low-latency responses. LPUART6 interrupts conflict with FreeMASTER Open Peripherals Tool (Platform). Disable LPUART6 interrupts — FreeMASTER operates in polling mode and does not use interrupt-driven UART. File Reference     File Step Description dashboard/led_color.html 1 LED colour dashboard dashboard/board_115200.fmcfg 1 FreeMASTER Lite server configuration src/main.c 1 Firmware with FreeMASTER TSA and LED colour variable   Add the FreeMASTER Lite configuration and dashboard – watch your board's LED colour live in the browser in about 20 minutes. Examples
View full article
Several gpu crashes/invalid output, when running opengl es cts Hi, For over three years we have been shipping a device on i.MX6QuadPlus, built on Yocto hardknott with Qt 6.3.2 on Weston. As the product grew we started getting more and more crash reports from users, and we could not find a cause in our own code or in Qt. Some of it we did fix - by retuning the DDR timings, disabling shadows in certain views, increasing some internal buffer sizes, and by running the app with GPU_VIV_EXT_RESOLVE=0 - but we still get reports, and a good part of them are GPU related and show up in the log like this: kernel: *** GPU DRV CONFIG *** kernel: Galcore version 6.4.3.336687 kernel: Galcore options: ... kernel: [galcore]: Stop driver to keep scene. That is the driver's own hang report - the monitor timer sees no progress, gckKERNEL_Recovery dumps the GPU state, and since recovery=0 the driver stops serving instead of resetting the core(recovery=1 is not an options for us, due needing to restart every gui application). The screen is frozen for good, Weston often cannot be killed even with SIGKILL, and the only way out is a power cut - which is quite bad for our customers. Since we had already tried a great many things at the Qt and application level and only got workarounds out of it, I decided to stop testing high-level functionality and test the OpenGL ES entry points directly instead - if they behave correctly the fault is ours, and if they do not then it is the driver/hardware fault(at least partial). I did that with VK-GL-CTS (https://github.com/KhronosGroup/VK-GL-CTS), first ported to Rust to make cross-compiling easy(still in progress, so only about half of the relevant cases could be checked so far). Case names are identical to upstream deqp-gles2/gles3/gles31, and everything passes on Mesa llvmpipe and on casual laptop on Ubuntu 24.04 with also mesa driver, so a failure on the board is a statement about the board. I ran it on the hardware over a weekend and with help of AI I was able to find and minimise 14 distinct defects, each now a standalone reproducer: a plain Rust project with no dependencies, cargo build and nothing else, GLSL in its own file.  (just run - runs locally, you can extract just arm parts, into only building step, to gather binary(you need to install first cargo install --locked cargo-zigbuild) Problems still present on 6.4.11.p4, the newest driver we can build for this part: 0001 GPU lockup - synchronization.inter_invocation.ssbo_atomic_read_write, alone, on a freshly booted board. Only a reboot clears it, and the process is unkillable so the reboot itself takes 8-10 minutes. 0002 GPU lockup - synchronization.inter_invocation.ssbo_atomic_overwrite, on its own. 0003 GPU lockup - ten of the twenty synchronization.inter_invocation.* cases hang alone, the other ten do not, so it is a boundary and not "compute is broken". All the atomic ssbo/image variants. All twenty swept ten runs each, every run from its own reboot. 0010 Link failure - 7 ubo cases where both stages read 47 members of the same std140 block. Either stage alone links, together they do not, glGetProgramInfoLog is empty, and nothing is near a limit the driver itself reports (3 blocks per stage vs 16, 704 bytes vs 65536). 47 reads is the least that does it, 46 links. 0011 Wrong result - shaders.invariance.highp.loop_*: two shaders computing invariant gl_Position from the same expression disagree by a few pixels of depth. 0013 Wrong status enum - fbo.completeness.size.distinct: a context requested as ES 2.0 reports ES 3.1, then answers completeness by the ES 2.0 rule and returns an enum ES 3.x does not define. Fixed by the 6.4.3.p2 -> 6.4.11.p4 jump: 0004 GPU lockup - image_load_store.cube.qualifiers.*_r32f (the r32ui/r32i ones beside them were fine) 0006 GPU lockup - image_load_store.* whenever the image is layered, 8 of 21 layered vs 0 of 7 over 2d, intermittent 0005 Client freeze - compute.indirect_dispatch.gen_in_compute.empty_command: glMapBufferRange never returns 0014 Client freeze - the same, via upload_buffer.empty_command, once a dispatch has already been mapped 0007 Wrong result - a chain of eighteen && in a compute shader that also declares an atomic counter comes out false when every term is true (44 of 2007 ssbo.layout cases) 0008 Compiler - the reserved-word table is for the wrong language version, both ways 0009 Wrong result - vec3 == vec3 false for two equal vectors, for a struct member returned through an inout parameter 0012 Compiler - mediump vec2(1.0, 1.0) compiles, where the ESSL 1.00 grammar has no place for a precision qualifier Tested on same board both times: i.MX6QP silicon rev 1.0, 2 GiB DDR, LVDS 1280x1024@60, Weston on fbdev with use-g2d=1, GL_RENDERER "Vivante GC2000+". old: hardknott, BSP imx-5.10.52-2.1.0, kernel 5.10.52, galcore 6.4.3.p2.336687, imx-gpu-viv 1:6.4.3.p2.2-aarch32, Weston 9.0.0.imx, Qt 6.3.2 new: wrynose, BSP imx-6.18.20-2.0.0, kernel 6.18.20, galcore 6.4.11.p4.1190909, imx-gpu-viv 1:6.4.11.p4.6-aarch32, Weston 10.0.5.imx, Qt 6.11.0 CONFIG_MXC_GPU_VIV=y, recovery=0 and stuckDump=0 on both; the timeout went 20000 -> 30000 ms and 6.4.11.p4 adds softReset=1. So the version bump helps, but some problems survived. We will be moving to i.MX8 soon because of i.MX6 availability, but our installed base keeps the i.MX6 hardware either way, so it would be good to see such problems fixed in future Is there any chance these get fixed in a newer version of the driver, even if that forces us to bump the Yocto version? I am afraid this class of problem may to some extent be present on i.MX8 as well, so has any testing with the Vulkan/OpenGL CTS been done, is it being done now, or is it planned? Because without passing that(plus some fuzzing like random executing of cts functions), I do not think our random crashes are fixable in the layers above the driver Re: Several gpu crashes/invalid output, when running opengl es cts Hello, The latest publicly released driver for i.MX 6/7 is imx-gpu-viv 6.4.11.p4.6 , shipped with the wrynose BSP (imx-6.18.20-2.0.0). The release notes describe that jump as bringing "bug fixes, performance optimizations" for the i.MX 6/7/8 line, which matches your observation that 8 of 14 defects were resolved between .p2 and .p4 . And yes, it is being done — but with important caveats by platform. For i.MX8 with Vivante (VSI) GPU — CTS is running. The internal Linux Factory test pipeline runs both opengl-es-cts and vulkan-cts packages against i.MX8 boards as part of every release candidate cycle. Defects found are tracked in the Linux Factory Jira project CTS on i.MX8M Nano, i.MX95. This means the Vivante GC7000-series GPUs in i.MX8M Plus, i.MX8QuadMax etc. do go through systematic conformance testing before each GA release. For i.MX9 with Mali / OSS Mesa  The release notes explicitly state for i.MX 95/952 with the Mesa OSS GPU stack: "OpenGL ES11, Vulkan 1.4.5, and OpenCL 3.0 basic features are working, but conformance tests are not passed."The Mali DDK default path on i.MX9 does pass CTS, but the open-source Panfrost/PanVK path is still being brought to conformance. For i.MX6 (GC2000+) specifically — CTS coverage is minimal No internal evidence was found of systematic deqp/CTS runs against the GC2000+ in the current Linux Factory pipeline. The GC2000+ only supports OpenGL ES 3.0 (not 3.1/3.2), and the test infrastructure appears to target the newer i.MX8/9 boards. Your work with VK-GL-CTS is the most thorough conformance-level testing of this specific IP that is visible in any internal channel.   The bottom line: a future i.MX6 driver patch is not guaranteed, but providing the standalone reproducers via your open support thread is the correct path. For your i.MX8 migration, the conformance situation for the Vivante GC7000-series is materially better than GC2000+, and systematic CTS testing is part of the release process — though even there, active driver bugs in galcore 6.4.11.p4 are still being discovered and filed.   Regards Re: Several gpu crashes/invalid output, when running opengl es cts I don't see an attachment, so looks that I forgot to add it, so I add it again
View full article
KE18F512VLH16 ECC RAM Single Bit Correction I have a follow up question related to @sean_dvorscak's post the other day (KE1 ECC RAM Single Bit Corrrection). @Celeste_Liu replied, ->> If implementing an optional scrub, please align the access according to the actual access size or scrub granularity, not blindly to the raw MCM_LMFAR value. Also don't use a fixed 4-byte access unless you first align the address appropriately and confirm the access size is valid. Can MCM_LMFATR[PEFSIZE] be used to determine the access size? If so, can this be used in tandem with MCM_LMFAR to implement a read-correct-writeback operation? For example, if MCM_LMFATR[PEFSIZE] is 3'b000 indicating an 8-bit access, can I perform an 8-bit read from the address indicated by MCM_LMFAR then perform an 8-bit write to the same address to correct the error. Similarly, if MCM_LMFATR[PEFSIZE] is 3'b010 indicating a 32-bit access, can I perform a 32-bit write to the address indicated by MCM_LMFAR without worrying about alignment? Re: KE18F512VLH16 ECC RAM Single Bit Correction Hello @rseigle77 , I have seen your post. Let me spend some time investigating this issue, and I will get back to you once I have more information. BR Celeste Re: KE18F512VLH16 ECC RAM Single Bit Correction Hello @rseigle77 , Regarding your question, I need to escalate it to our internal team for further investigation. According to our process, please provide the end application name. Thanks for your cooperation. BR Celeste Re: KE18F512VLH16 ECC RAM Single Bit Correction Hi @Celeste_Liu  - P7 is the name of the end application. Re: KE18F512VLH16 ECC RAM Single Bit Correction Hi @Celeste_Liu, is there any update on this? Re: KE18F512VLH16 ECC RAM Single Bit Correction Hello @rseigle77 , Sorry, I still haven't received a response from the internal yet. I'll follow up with them again and make this my top priority. As soon as I hear anything back, I'll let you know right away. BR Celeste Re: KE18F512VLH16 ECC RAM Single Bit Correction Thanks for the response @Celeste_Liu, but that does not answer my question regarding MCM_LMFATR[PEFSIZE]: "Can MCM_LMFATR[PEFSIZE] be used to determine the access size? If so, can this be used in tandem with MCM_LMFAR to implement a read-correct-writeback operation? For example, if MCM_LMFATR[PEFSIZE] is 3'b000 indicating an 8-bit access, can I perform an 8-bit read from the address indicated by MCM_LMFAR then perform an 8-bit write to the same address to correct the error. Similarly, if MCM_LMFATR[PEFSIZE] is 3'b010 indicating a 32-bit access, can I perform a 32-bit write to the address indicated by MCM_LMFAR without worrying about alignment?" Re: KE18F512VLH16 ECC RAM Single Bit Correction Hello @rseigle77 , Thanks for your patience. I got the reply from the internal. ECC "correction" means returning corrected data to the CPU, not fixing the underlying bit stored in SRAM. Automatic repair requires a separate scrub/write-back mechanism. The recommended flow to use software scrub: ECC corrects data on read. Single-bit error interrupt/status is raised. Refer to RM 6.3.1.1 Determining source of the interrupt. MCM_LMPECR[ER1BR]=1 Software reads the fault address. MCM_LMPEIR[PEELOC] = 5'h08 - a 1-bit correctable ECC event from SRAM_L, MCM_LMFAR indicates fault address. Software rewrites the corrected value back to the same address. New ECC syndrome is generated and stored. BR Celeste
View full article
How do I escalate an AT&T issue? Stuck with an AT&T issue that keeps getting passed around without a real fix? AT&T Escalation Support Team ((USA))
View full article
カラー/旧型スクリーン(IVI-SHELL搭載) IMX8QXP - スカースギャップ - L 6.6.52-weston 12-ivishell 更新された画面の前に、カラー/古い画面が表示されます。回避方法/解消方法/削除方法。 weston.ini [コア] #gbm-format=argb8888 アイドルタイム=0 shell=ivi-shell.so # use-g2d=1 ウィンドウの再描画=16 # pageflip-timeout=0 背景色=0x00000000 [libinput] touchscreen_calibrator=true [出力] 名前=LVDS-1 モード=1280x720@60 [アイヴィシェル] ivi-shell-user-interface=weston-ivi-shell-user-interface ivi-input-module=ivi-input-controller.so ivi-id-agent-module=ivi-id-agent.so input-method=ivi-input-controller(入力-コントローラ) ベースレイヤーID=1000 ベースレイヤーIDオフセット=10000 workspace-background-layer-id=2000 workspace-layer-id=3000 application-layer-id=4000 遷移期間=0 [デスクトップアプリデフォルト] デフォルトサーフェスID=2000000 デフォルトサーフェスID最大値=2001000 i.MX 8ファミリ | i.MX 8QuadMax (8QM) | 8QuadPlus Re: Coloured/Old Screen with IVI-SHELL こんにちは、 提案された方法を試してみましたが、状況は変わりませんでした。カラー画面(旧式の画面)がまだ表示されています。 他に何か提案や設定が必要なことはありますか? ありがとうございます。 VKS Re: Coloured/Old Screen with IVI-SHELL こんにちは、 背景色を0x00000000に変更し、gbm-formatのコメントを解除してみてください。 また、WestonのsystemdサービスにPre-startステップを追加して、Westonが初期化する前にディスプレイを消去することもできます: echo 1 > /sys/class/graphics/fbx/blank よろしくお願いいたします。 Re: Coloured/Old Screen with IVI-SHELL こんにちは、 最新情報のご提供ありがとうございます。 この問題は以前のweston-imx-10.0.1で報告されており、このパッチで解決済みです。 diff --git a/libweston/renderer-g2d/g2d-renderer.c b/libweston/renderer-g2d/g2d-renderer.c index 245a50de..d9df8b4e 100644 --- a/libweston/renderer-g2d/g2d-renderer.c +++ b/libweston/renderer-g2d/g2d-renderer.c @@ -2199,6 +2199,7 @@ drm_create_g2d_image(struct g2d_surfaceEx* g2dSurface, buffer->buf_vaddr = vaddr; buffer->buf_size = size; g2dSurface->base.planes[0] = buffer->buf_paddr; + memset(buffer->buf_vaddr, 0x00, size); g2dSurface->base.left = 0; g2dSurface->base.top = 0; g2dSurface->base.right = w; バッファを入手したときにmemsetを追加すれば、Weston開始時にバッファをクリアできます。 最新のweston-imx-15.0.1では、この点が変更され、ポートが必要になります。 社内チームはgl-rendererで問題が発生していないと確認したので、gl-rendererを使って問題を回避できるかどうか確認してもらえますか?(# use-g2d=1)。 また、動作をよりよく理解するために、画面に何が表示されているかを共有していただけると助かります。 よろしくお願いいたします。 Re: Coloured/Old Screen with IVI-SHELL こんにちは、 画像はこちらです。 はい、 use-g2d=1を使用することでカラー画面は回避できました。しかし、フレーム落ちが発生し、動画も再生されませんでした。 それともう一つ、もし私が使ったらuse-g2d=1、これはソフトウェアアクセラレーション用ですよね?でもフレームロスを避けるためにハードウェアアクセラレーションが必要です。確認してください。 ありがとうございます。 VKS
View full article
imx93 – USB Disconnect During UUU Serial Downloader Boot Dear NXP Team, We are currently debugging our i.MX93 custom board using the MIMX9352AVTXMAC processor. Our board uses LPDDR4 with a two-rank memory configuration. We are trying to program the onboard eMMC using UUU (Universal Update Utility). The board is configured in Serial Downloader / USB boot mode. The i.MX93 is detected correctly by UUU: uuu -lsusb uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.5.243-10-g59c7638 Connected Known USB Devices   Path   Chip   Pro   Vid   Pid   BcdVersion   Serial_no   ====================================================================   3:1   MX93   SDPS:   0x1FC9  0x014E   0x0001   We are using the following command to program the eMMC: sudo uuu -v -b emmc_all \ imx-boot-imx93evk-sd.bin-flash_singleboot \ image-imx93evk-20260905081644.rootfs.wic.zst UUU detects the i.MX93 and starts the SDPS boot command. However, immediately after starting the bootloader transfer, the USB connection is lost. The relevant UUU log is: uuu (Universal Update Utility) for nxp imx chips -- libuuu_1.5.243-10-g59c7638 Build in config:   Pctl   Chip     Vid   Pid   BcdVersion   Serial_No   ==================================================   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:   MX91     0x1fc9   0x0159   SDPS:   MX95     0x1fc9   0x015d   SDPS:   MX95     0x1fc9   0x015c   SDPS:   MX943     0x1fc9   0x0027   SDPS:   MX952/IMX937   0x1fc9   0x0028   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   FB:        0x1d6b   0x0104 Run built-in script: uuu_version 1.4.149 # @_flash.bin            | bootloader, which can extract from wic image # @_image   [_flash.bin] | wic image burn to emmc. # This command will be run when i.MX6/7 i.MX8MM, i.MX8MQ SDP: boot -f imx-boot-imx93evk-sd.bin-flash_singleboot -scanlimited 0x800000 # This command will be run when ROM support stream mode # i.MX8QXP, i.MX8QM SDPS: boot -scanterm -f imx-boot-imx93evk-sd.bin-flash_singleboot -scanlimited 0x800000 # These commands will be run when use SPL and will be skipped if no spl # SDPU will be deprecated. please use SDPV instead of SDPU # { SDPU: delay 1000 SDPU: write -f imx-boot-imx93evk-sd.bin-flash_singleboot -offset 0x57c00 SDPU: jump -scanlimited 0x800000 # } # These commands will be run when use SPL and will be skipped if no spl # if (SPL support SDPV) # { SDPV: delay 1000 SDPV: write -f imx-boot-imx93evk-sd.bin-flash_singleboot -skipspl -scanterm -scanlimited 0x800000 SDPV: jump -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-boot-imx93evk-sd.bin-flash_singleboot FB: flash -scanterm -scanlimited 0x800000 bootloader imx-boot-imx93evk-sd.bin-flash_singleboot FB: ucmd if env exists emmc_ack; then ; else setenv emmc_ack 0; fi; FB: ucmd mmc partconf ${emmc_dev} ${emmc_ack} 1 0 FB: done Wait for Known USB Device Appear... New USB Device Attached at 3:1-6A440AB426084436 3:1-6A440AB426084436>Start Cmd:SDPS: boot -scanterm -f imx-boot-imx93evk-sd.bin-flash_singleboot -scanlimited 0x800000 3%3:1-6A440AB426084436>Fail HID(W): LIBUSB_ERROR_NO_DEVICE (-4)(0.024s) While sending the boot command, we also monitored the Linux USB messages using dmesg. The i.MX93 USB device is disconnected and then enumerates again, refer the attached screenshot of the dmesg. We would appreciate your guidance on the following questions: Is this USB disconnect/re-enumeration expected during the i.MX93 SDPS bootloader handoff when using UUU? What does the following error indicate in this specific situation? Fail HID(W): LIBUSB_ERROR_NO_DEVICE (-4) Are there any specific requirements for the following signals during the SDPS-to-SPL/U-Boot handoff that we should verify on the custom board? POR_B RESET_B USB_VBUS USB_DP/DM Processor power rails LPDDR4 power rails System/reference clocks   Could you please provide a reference design, or software/boot configuration example for the i.MX93 MIMX9352AVTXMAC with a two-rank LPDDR4 memory configuration? In particular, we would like to confirm the recommended LPDDR4 device configuration, memory initialization/training configuration, and corresponding IMX_BOOT/SPL configuration for a two-rank memory design. We would appreciate your guidance on the above issue and request you to provide the relevant details, recommended configuration, and reference design/code for the two-rank LPDDR4 configuration. Thanks & Regards, Abishek Re: imx93 – USB Disconnect During UUU Serial Downloader Boot Hi @pengyong_zhang , Please refer the attached LPDDR4 schematics and configuration .mex for your reference. Regards, Abishek Re: imx93 – USB Disconnect During UUU Serial Downloader Boot Hi @AbishekDevan  1. This is not the expected behavior. 2. This error occurred because the device disconnected during the flashing process. please share the customer's DDR schematic file and configuration page. B.R Re: imx93 – USB Disconnect During UUU Serial Downloader Boot Hi @AbishekDevan  i cannot import your .mex file successfully. Please share a screenshot of your DDR configuration page. B.R
View full article
LPC55S0x CANFDは1Mbps(仲裁段階)および8Mbps(データ段階)をサポートできますか? こんにちは、NXPさん。 LPC55S0xは仲裁段階で1Mbps、データ段階で8Mbpsをサポートできますか? LPC55S0xのデータシートには見つかりません。 ありがとうございました。 LPC55xx Re: Can LPC55S0x CANFD support 1Mbps (arbitartion stage) and 8Mbps(data stage) こんにちは、ハリーさん。 わかった。 ありがとう。 Re: Can LPC55S0x CANFD support 1Mbps (arbitartion stage) and 8Mbps(data stage) こんにちは、 @jimmyli はい、LPC55S0x CAN-FDコントローラは、MCAN機能クロックが96 MHzで、外部CAN-FDトランシーバーおよび物理ネットワークが8 Mbit/sをサポートしている場合、1 Mbit/sの仲裁と8 Mbit/sのデータに設定可能です。 データシートにこれが直接記載されていない理由は、ビットレートが固定の最大値として指定されているのではなく、MCANクロックとNBTP/DBTPタイミングレジスタから導出されるためです。CANクロックはCANCLKDIV = 0(割り算)で、LPC55S0xの最大クロック周波数は96 MHzで、main_clkを使用できます。 BR ハリー
View full article
AT&Tで問題をエスカレートさせるにはどうすればよいですか? 誰も解決してくれないAT&Tの問題に悩まされていませんか?AT&Tエスカレーション サポート チーム(米国)
View full article
S32K118EVB2Q048:ADCの読み取り値が選択されたMCUの電源電圧と一致しない こんにちは、NXPチームの皆様、 私はS32K118EVB2Q048ボード(回路図SCH-47530 Rev A1)を使用してADCをテストしています。入力電圧が約3.3Vを超えると、誤った測定値が表示されます。 セットアップ: - MCU:S32K118(48-LQFP) - IDE:[S32 Design Studio版] - ドライバ:[RTDバージョン/SDKバージョン/ベアメタル] - ADCチャネル:[例:PTA7 – ADC0_SE3] - 解像度:12ビット - 入力:[外部直流電源/搭載ポテンショメータ] - ジャンパー:J10 = 2-3(5V)、J107、J15 - 基板電源:[USB / 12V] 問題: J10を2-3に設定してMCUを5Vで動作させています。 - 入力 4.10 V: 生データ = 4095。5Vの基準電圧であれば、約3358を期待していました。 - 4V~5Vの入力:常に4095(フルスケール)。 - 5Vで計算すると、入力電圧が高くなるにつれて誤差が大きくなります。 質問: SCH-47530 Rev A1では、J10を2~3に設定するだけでVDDAとADCの基準電圧が5Vになりますか?それとも他に何か変更する必要はありますか(J15、J107、抵抗など)? このEVBの動作するS32K118 ADCの例を5Vの基準でテストしたものを共有してもらえますか?また、解像度のために異なる異なる計算範囲も教えてもらえますか? Re: S32K118EVB2Q048: ADC readings do not match the selected MCU supply voltage こんにちは どのRTD/SDKバージョンを使っているか教えてもらえますか? また、PTA7を使っているのはわかりますが、ADC_POTも言及されていましたね。ADC_POTは接続されていません。なぜならR761はEVBに登録されていないからです: あなたはJ3.1ヘッダーを介してPTA7を使用しているものと想定します。 J10とJ107の両方が2-3に設定されていることを確認し、VDDを測定して、実際に5Vに設定されていることを確認してください。 RTDパッケージの Adc_Pdb_Ip_example_S32K118 を使い、メインをループに改造して SW 変換を始めるだけです: while(1) { /* Start a software trigger conversion */ Adc_Ip_StartConversion(ADCHWUNIT_0_VS_0_INSTANCE, ADC_IP_INPUTCHAN_EXT2, TRUE); /* Wait for the notification to be triggered and read the data */ while (notif_triggered != TRUE); notif_triggered = FALSE; delay(1000); } その後、電源ユニットで0Vから5Vの間で測定し、正しい値が確認できました。 ADC0_SE2 @3.3V: ADC0_SE2 @5V: 最後に、ADC_SC2[REFSEL]でREFSELが正しく設定されているか確認してください。 よろしくお願いします、 ジュリアン
View full article
About S32 Design Stdio's Functional Safety Evaluation Hello community: In the assessment of the project, I encountered some problems, and I would like to ask for help: one of the functional safety assessment is the confidence assessment of tools, and we need to assess whether the relevant tools in the software development process can meet the requirements of ASIL level, and how to ensure that S32DS, as a default tool that comes with the free software, can meet the functional safety level of software development? Is there any corresponding certificate or certification? Re: 关于S32 Design Stdio的功能安全评估 Hello Mike    We also meet this problem, can you share the documents to me.     Email: [email protected]  Re: 关于S32 Design Stdio的功能安全评估 Hi,  I sent you requested document via private message.  Re: 关于S32 Design Stdio的功能安全评估 Hi Mike,         If possible, could you please send the tool chain Classification report and Safety Manual to me?thanks; My email address:[email protected]; Re: 关于S32 Design Stdio的功能安全评估 Could you send my E-mail for the Tool Chain Classification Report and Tool Chain Safety Manual? Thank you very much. My E-mail is jiandong.chao @d aisch.com Re: 关于S32 Design Stdio的功能安全评估 Hi Mike, Can you send me the TCR and TSM documents to me [email protected]. Thank you. Shoubing Re: 关于S32 Design Stdio的功能安全评估 Could you send my E-mail? Thank you very much. My E-mail is [email protected] Re: 关于S32 Design Stdio的功能安全评估 Hi Mike, Could you send me a copy if you can? I'm also currently experiencing a problem regarding the functional safety assessment of the S32 DS, thanks! Re: 关于S32 Design Stdio的功能安全评估 Hello Derrick, We are only willing to provide the TCR and TSM documents at this time. Best regards, Mike Re: 关于S32 Design Stdio的功能安全评估 Hi Derrick, I need to check with my source for the documentation. I currently don't have access to the documents you requested. Best Regards, Mik Re: 关于S32 Design Stdio的功能安全评估 Hi,Mike: on this?I don't quite understand.Could you be more specific? Thanks! BR Derrick Re: 关于S32 Design Stdio的功能安全评估 Checking on this. Re: 关于S32 Design Stdio的功能安全评估 Hi,Mike: Can you send me the TCQR file and other files? thank you! BR! Derrick Re: 关于S32 Design Stdio的功能安全评估 I also need this document, please help to forward me a copy, thank you! [email protected] Re: 关于S32 Design Stdio的功能安全评估 Hi Derrick, I sent you the files on PM. Best Regards, Mike Re: 关于S32 Design Stdio的功能安全评估 Hi Mike, If possible, could you please send it to me.thanks BR! Derrick Re: 关于S32 Design Stdio的功能安全评估 Hello Derrick, There is no functional safety certified version of S32DS or the NXP GCC compiler. We have a Tool Chain Classification Report and a Tool Chain Safety Manual available if you are interested. Best Regards, Mike Re: 关于S32 Design Stdio的功能安全评估 Hi Mike, Thanks for the update. We have the same concern in our functional safety project and need tool assessment for S32DS 3.5. Could you please provide the corresponding Tool Chain Classification Report and Tool Chain Safety Manual? They will be very helpful for us to finish the S32DS tool assessment. Please send the documents to my email: [email protected]. Best regards, Lee
View full article
How Do I Escalate an Issue with AT&T? Stuck with an AT&T issue that nobody seems to resolve? AT&T Escalation Support Team ((USA))
View full article
JCOP4 P71 — AES-GCM and AES-CCM return NO_SUCH_ALGORITHM I am working with an NXP JCOP4 P71 card and am trying to understand why neither AES-GCM nor AES-CCM appears to be available. Card details: JCOP 4 P71 JCOP version: 4.7 R1.01.4 Platform ID: J3R3510236310400 ATR: 3BFA180000910131FE454A33523331302D333535FF JCOP Tools 6.15.0.11 Java Card Classic 3.0.5 Other crypto functionality such as AES-128 ECB, SHA-256, RSA, and secure random generation works correctly. However: * AES-GCM returns CryptoException.NO_SUCH_ALGORITHM * CryptoBaseX.ALG_AES_GCM also returns NO_SUCH_ALGORITHM * AEADCipher.ALG_AES_CCM also returns NO_SUCH_ALGORITHM Could someone clarify whether GCM and CCM are expected to be supported on this specific JCOP4 P71 configuration? In particular: 1. Are AES-GCM and AES-CCM supported for Platform ID J3R3510236310400? 2. Are these algorithms dependent on the specific OEF / card configuration? 3. Can they be enabled after issuance, or would a different JCOP4 card configuration be required? 4. Is there documentation showing which crypto algorithms are enabled for a given JCOP4 configuration? I mainly want to determine whether this is expected behavior for this card configuration or whether I am missing something in the setup. Smart Cards Re: JCOP4 P71 — AES-GCM and AES-CCM return NO_SUCH_ALGORITHM Hi @sameer_chawla , Please find the answers below: 1. No, AES-GCM and AES-CCM are not supported in JCOP 4, Platform ID J3R3510236310400 2. No, these algorithms are not supported by any configuration 3. No, they cannot be enabled, customer needs to implement them using the APIs available 4. Yes, "um4695xx - User guidance and administrator manual JCOP4 P71" lists available crypto algorithms There is also another document describing the available crypto algorithms on our JCOP platforms: an7459xx - AN14334 - Comparison between JCOP 4 P71, JCOP 4.5 P71 and JCOP 5 P71 CIPHER_AES_CCM: Not supported on JCOP 4, supported on JCPO 4.5/5 CIPHER_AES_GCM: Not supported on JCOP 4/4.5/5 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. -------------------------------------------------------------------------------
View full article
S32K118EVB2Q048: ADC readings do not match the selected MCU supply voltage Hi NXP team, I'm using the S32K118EVB2Q048 board (schematic SCH-47530 Rev A1) and testing the ADC. I'm getting wrong readings when the input voltage goes above about 3.3 V. Setup: - MCU: S32K118 (48-LQFP) - IDE: [S32 Design Studio version] - Driver: [RTD version / SDK version / bare-metal] - ADC channel: [e.g. PTA7 – ADC0_SE3] - Resolution: 12-bit - Input: [external DC power supply / on-board potentiometer] - Jumpers: J10 = 2-3 (5V), J107, J15  - Board powered from: [USB / 12V] Issue: I set J10 to 2-3 so the MCU runs at 5V. - Input 4.10 V: raw = 4095. With a 5V reference I expected about 3358. - Any input from 4 V to 5 V: always 4095 (full scale). - When I calculate with 5V, the error increases as the input voltage increases. Questions: On SCH-47530 Rev A1, is setting J10 to 2-3 enough to make VDDA and the ADC reference 5V, or do I need to change anything else (J15, J107, any resistor)? Can you share a working S32K118 ADC example for this EVB, tested with a 5V reference , can u also give ur calculated range for different for resolution  Re: S32K118EVB2Q048: ADC readings do not match the selected MCU supply voltage Hello  Can you share which RTD/SDK version you are using? Also, I can see you are using PTA7, however, you mentioned ADC_POT. ADC_POT is not connected as R761 is not populated on the EVB: I assume you are using PTA7 through the J3.1 header. Please confirm both J10, and J107 are set 2-3, and try to measure VDD to make sure it is indeed set at 5V. I used Adc_Pdb_Ip_example_S32K118 from RTD package, and simply modified main to loop and start a SW conversion: while(1) { /* Start a software trigger conversion */ Adc_Ip_StartConversion(ADCHWUNIT_0_VS_0_INSTANCE, ADC_IP_INPUTCHAN_EXT2, TRUE); /* Wait for the notification to be triggered and read the data */ while (notif_triggered != TRUE); notif_triggered = FALSE; delay(1000); } After this, I used a power supply to measure between 0 and 5V, and I could see the correct values. ADC0_SE2 @3.3V: ADC0_SE2 @5V: Lastly, check if REFSEL is correctly set in ADC_SC2[REFSEL]: Best regards, Julián
View full article
MPXV7002DP compatibility with LPG and Propane Hello, i am a student in my final year. i am currently working on a project where i have to measure the pressure difference in household LPG line. the normal pressure in the line is around 2.30 kPa to 3.60 kPa . i checked the data sheet of it but there is nothing clear about LPG compatibility. So if anyone tried this in past or any technical official can tell me about it . thanks . Re: MPXV7002DP compatibility with LPG and Propane Hello, As of February 2, 2026, the NXP MEMS Sensor products have been transferred to STMicroelectronics. Please reach out to STMicroelectronics for further information and support.
View full article
如何升级我的AT&T问题? 遇到AT&T的问题,一直被推来推去却始终得不到真正的解决?AT&T升级支持团队(美国)
View full article
彩色/旧屏幕,带 IVI-SHELL IMX8QXP - Scarthgap - L 6.6.52-weston 12-ivishell 在更新后的屏幕之前,会先显示彩色/旧屏幕。如何避免/清除/去除它。 weston.ini [核] #gbm-format=argb8888 空闲时间=0 shell=ivi-shell.so # 使用 g2d=1 重绘窗口=16 # 翻页超时=0 背景颜色=0x00000000 [libinput] touchscreen_calibrator=true [输出] 名称=LVDS-1 模式=1280x720@60 [ivi-shell] ivi-shell-user-interface=weston-ivi-shell-user-interface ivi-input-module=ivi-input-controller.so ivi-id-agent-module=ivi-id-agent.so 输入方法=ivi-输入控制器 基础层ID=1000 基础层 ID 偏移量=10000 工作区背景图层 ID=2000 工作区图层 ID=3000 应用程序层 ID=4000 过渡持续时间=0 [桌面应用程序默认] default-surface-id=2000000 default-surface-id-max=2001000 i.MX 8 系列 | i.MX 8QuadMax (8QM) | 8QuadPlus Re: Coloured/Old Screen with IVI-SHELL 你好, 我试了建议的方法,但问题依旧。彩色/旧式屏幕仍然显示。 还有其他建议或需要配置吗? 谢谢,此致敬礼! VKS Re: Coloured/Old Screen with IVI-SHELL 你好, 请尝试将背景颜色更改为 0x00000000 并取消注释 gbm-format。 您还可以尝试在 Weston systemd 服务中添加一个预启动步骤,以便在 Weston 初始化之前清除显示内容: echo 1 > /sys/class/graphics/fbx/blank 顺祝商祺! Re: Coloured/Old Screen with IVI-SHELL 你好, 谢谢你的更新。 这个问题之前在 weston-imx-10.0.1 版本中已经报告过,并通过以下补丁解决了: diff --git a/libweston/renderer-g2d/g2d-renderer.c b/libweston/renderer-g2d/g2d-renderer.c index 245a50de..d9df8b4e 100644 --- a/libweston/renderer-g2d/g2d-renderer.c +++ b/libweston/renderer-g2d/g2d-renderer.c @@ -2199,6 +2199,7 @@ drm_create_g2d_image(struct g2d_surfaceEx* g2dSurface, buffer->buf_vaddr = vaddr; buffer->buf_size = size; g2dSurface->base.planes[0] = buffer->buf_paddr; + memset(buffer->buf_vaddr, 0x00, size); g2dSurface->base.left = 0; g2dSurface->base.top = 0; g2dSurface->base.right = w; 获取缓冲区时添加 memset,可以在 weston 启动时清除缓冲区。 在最新的 weston-imx-15.0.1 版本中,情况发生了变化,需要一个端口。 内部团队已确认 gl-renderer 不存在此问题,因此,请您帮忙检查一下使用 gl-renderer 是否能避免此问题?(# use-g2d=1)。 另外,请分享您在屏幕上看到的内容,以便我们更好地了解问题所在。 顺祝商祺! Re: Coloured/Old Screen with IVI-SHELL 你好, 请查找图片。 是的,使用use-g2d=1 可以避免出现彩色屏幕。但我发现出现了丢帧现象,而且视频也无法播放。 还有一点,如果我使用`use-g2d=1`,这是为了软件加速,对吗?但我们需要硬件加速来避免丢帧。请检查并确认。 谢谢,此致敬礼! VKS
View full article
S32 Design Stdioの機能安全評価 コミュニティの皆さん、こんにちは。 プロジェクト評価中に問題が発生しており、ご支援をお願いいたします。機能安全評価の一つにツール信頼性評価があり、ソフトウェア開発プロセスで使用されるツールがASILレベル要件を満たしているかどうかを評価する必要があります。S32DSは無料でデフォルトで組み込まれているツールですが、ソフトウェア開発の機能安全レベル要件を満たしていることをどのように保証すればよいでしょうか?関連する証明書や認証はありますか? Re: 关于S32 Design Stdio的功能安全评估 こんにちは、マイク 私たちもこの問題に直面しています。文書を共有していただけますCANか。 メールアドレス: [email protected] Re: 关于S32 Design Stdio的功能安全评估 こんにちは、 要求された文書をプライベートメッセージで送信しました。 Re: 关于S32 Design Stdio的功能安全评估 こんにちは、マイク。 可能であれば、ツールチェーンの分類レポートとセーフティマニュアルを送っていただけますか? ありがとうございます。私のメールアドレス: [email protected]。 Re: 关于S32 Design Stdio的功能安全评估 ツールチェーン分類レポートとツールチェーンセーフティマニュアルを電子メールで送信していただけますか?どうもありがとうございます。私の電子メールは jiandong.chao @d aisch.com です。 Re: 关于S32 Design Stdio的功能安全评估 こんにちは、Mikeさん TCR および TSM 文書を[email protected]まで送っていただけますか。 よろしくお願いします。 シャビン Re: 关于S32 Design Stdio的功能安全评估 私のEメールを送っていただけますか?どうもありがとうございます。私のメールアドレスは[email protected]です。 Re: 关于S32 Design Stdio的功能安全评估 こんにちは、マイク。 もし可能であれば、コピーを送っていただけますか?現在、S32 DSの機能安全評価に関して問題が発生しています。よろしくお願いいたします。 Re: 关于S32 Design Stdio的功能安全评估 こんにちは、デリック。 現時点では、TCR および TSM ドキュメントのみを提供いたします。 よろしくお願いします、 マイク Re: 关于S32 Design Stdio的功能安全评估 こんにちは、デリック。 ドキュメントについてはソースに確認する必要があります。現時点では、ご依頼いただいた文書にアクセスできません。 よろしくお願いいたします。 ミック Re: 关于S32 Design Stdio的功能安全评估 こんにちは、マイク: これについて、よく分かりません。もう少し具体的に教えていただけますか? ありがとう! BR デリック Re: 关于S32 Design Stdio的功能安全评估 これについて確認中です。 Re: 关于S32 Design Stdio的功能安全评估 こんにちは、マイク: TCQR ファイルとその他のファイルを送信してもらえますか? ご協力の程、よろしくお願い申し上げます。 ブラッ! デリック Re: 关于S32 Design Stdio的功能安全评估 このファイルも必要です。コピーを転送していただけますか?ありがとうございます。 [email protected] Re: 关于S32 Design Stdio的功能安全评估 こんにちは、デリック。 ファイルをPMで送信しました。 よろしくお願いいたします。 Mike Re: 关于S32 Design Stdio的功能安全评估 こんにちは、マイク。 可能であれば、送っていただけますか。ありがとうございます。 ブラッ! デリック Re: 关于S32 Design Stdio的功能安全评估 こんにちは、デリック。 S32DS または NXP GCC コンパイラの機能安全認定バージョンはありません。ご興味があれば、ツール チェーン分類レポートとツール チェーンセーフティマニュアルをご利用いただけます。 よろしくお願いいたします。 Mike Re: 关于S32 Design Stdio的功能安全评估 こんにちは、Mikeさん 最新情報ありがとうございます。私たちの機能安全プロジェクトでも同じ懸念があり、 S32DS 3.5のツール評価が必要です。対応するツールチェーン分類報告書とツールチェーンセーフティマニュアルを教えていただけますか?これらは、S32DSツールの評価を完了させる上で非常に役立つでしょう。 書類は私のメールアドレス( [email protected] )までお送りください。 よろしくお願いいたします、リー
View full article