Issue with Concurrent Execution on Cortex M33 and Cortex A55 with Ethos-U NPU

[TUANLAM95]

Dear NXP Technical Support,

I am currently experiencing an issue with concurrent execution on my system that involves a Cortex M33 and a Cortex A55 processor, along with the Ethos-U NPU.

System Configuration:

• Cortex A55: Running an AI image recognition application utilizing the Ethos-U NPU.
• Cortex M33: Running a peripheral control program.

Problem Description: When I run the peripheral control program on the Cortex M33, it executes correctly if the Cortex A55 is not performing any AI image recognition tasks with the Ethos-U NPU. However, when the AI image recognition application is running on the Cortex A55 and using the Ethos-U NPU, the Cortex M33 seems to stop executing my peripheral control program. Instead, it only runs the firmware_ethosu program.

Objective: I need to achieve concurrent execution of both the AI image recognition task on the Cortex A55 with Ethos-U NPU and my peripheral control program on the Cortex M33.

Details:

• Peripheral Control Program: Written for Cortex M33, it functions as expected when the Cortex A55 is idle or performing tasks that do not involve the Ethos-U NPU.
• AI Image Recognition Application: Runs on Cortex A55, utilizing the Ethos-U NPU.
• Observed Behavior: When the AI image recognition application is running, the Cortex M33 appears to only execute the firmware_ethosu and does not run my peripheral control program.

Could you please provide guidance or a solution that allows both programs to run simultaneously without interfering with each other? Any help or suggestions for debugging this issue would be greatly appreciated.

Thank you for your assistance.

Best regards,

[TUANLAM95]

Yes, I have done that. But first, I need to run mcimx93evk_ethosu_apps_rpmsg without any modifications, and it is not running (following the instructions here: https://docs.nxp.com/bundle/AN13854/page/topics/deploy_procedure.html). Here is the error message:

u-boot=> tftp 0x80000000 ethosu_apps.bin;cp.b 0x80000000 0x201e0000 0x20000;
Could not get PHY for FEC0: addr 2
Could not get PHY for ethernet@428a0000: addr 1
phy_connect() failedFAILED: 0*** ERROR: `serverip' not set
u-boot=> bootaux 0x201e0000 0
Error: Image's address 0x201e0000 is invalid
Address should be memory from M core view,
For example: 0x1ffe0000 for TCML in secure
u-boot=>

[Zhiming_Liu]

Hi @TUANLAM95 

Do not load ethosu_apps, this is just a simple demo.Please use ethosu_apps_rpmsg. 

[TUANLAM95]

Yes, I will try again. Currently, I am facing an issue activating the AP1302 driver for imx93. Can you guide me on this?

[Zhiming_Liu]

Hi @TUANLAM95 

You can refer the evk dts about dts node.

https://github.com/nxp-imx/linux-imx/blob/lf-6.6.y/arch/arm64/boot/dts/freescale/imx93-11x11-evk.dts

[TUANLAM95]

We are encountering a kernel panic issue on the i.MX93 platform when booting the system. The error message indicates "Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000". This occurs during the initialization of the ap1302 driver.

[ 7.967148] debugfs: Directory '2-003d' with parent 'regmap' already present!
[ OK ] Started 7.976999] ap1302_mipi 2-003d: Requesting firmware /imx/camera/ap1302_ar1335_single_fw.bin
1;39mGetty on tty1.
[ 7.995154] ap1302_mipi 2-003d: Firmware header version : 1
[ 8.001580] ap1302_mipi 2-003d: Firmware description : Release 433 @ 1-12-2023 0:15:4 - AP1302-REV2-AR1335-REV2-IAS1MOD-AR1335CSSC080110 - No Clock - NO SIP
[ 8.033268] ap1302_mipi 2-003d: AP1302 revision 0.2.6 detected
[ 8.044193] rtc-pcf2131-i2c: probe of 2-0053 failed with error -5
[ OK ] Started Serial Gett[ 8.054218] ap1302_mipi 2-003d: AP1302 oscillator clock 40000000 hz (FP 0x00280000)
y on ttyLP0.
[ OK ] Reached target Login Prompts.
[ 8.083942] wm8962 0-001a: Failed to read ID register
Starting Weston, a Wayland…ositor, as a system service...
Starting WPA supplicant...
[ 8.162260] fsl_mc_err_probe: No ECC DIMMs discovered
[ 8.174338] ap1302_mipi 2-003d: AP1302 MIPI frequency 900000000 hz (FP 0x03840000)
[ 8.188137] ap1302_mipi 2-003d: ap1302_write_fw_window len 83104d
[ 8.191735] wm8962: probe of 0-001a failed with error -5
[ 8.229543] audit: type=1334 audit(1717405758.586:6): prog-id=9 op=LOAD
[ 8.250948] audit: type=1334 audit(1717405758.598:7): prog-id=10 op=LOAD
Starting Hostname Service...
[ 8.315157] audit: type=1334 audit(1717405758.670:8): prog-id=11 op=LOAD
[ 8.331462] audit: type=1334 audit(1717405758.690:9): prog-id=12 op=LOAD
Starting User Database Manager...
[ OK ] Started WPA supplicant.
[ OK ] Reached target Hardware activated USB gadget.
[ OK ] Started User Database Manager.
[ OK ] Started Hostname Service.
[ OK ] Created slice User Slice of UID 0.
Starting User Runtime Directory /run/user/0...
[ OK ] Created slice Slice /system/systemd-fsck.
[ OK ] Found device /dev/mmcblk1p1.
Starting File System Check on /dev/mmcblk1p1...
[ OK ] Finished User Runtime Directory /run/user/0.
Starting User Manager for UID 0...
[ 9.186313] audit: type=1006 audit(1717405759.542:10): pid=487 uid=0 old-auid=4294967295 auid=0 tty=(none) old-ses=4294967295 ses=1 res=1
[ 9.207393] audit: type=1300 audit(1717405759.542:10): arch=c00000b7 syscall=64 success=yes exit=1 a0=8 a1=ffffd27fe6b0 a2=1 a3=1 items=0 ppid=1 pid=487 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=1 comm="(systemd)" exe="/lib/systemd/systemd" key=(null)
[ 9.251400] audit: type=1327 audit(1717405759.542:10): proctitle="(systemd)"
[ 9.381280] audit: type=1334 audit(1717405759.738:11): prog-id=13 op=LOAD
[ OK ] Finished File System Check on /dev/mmcblk1p1.
Mounting /run/media/BOOT-mmcblk1p1...
[ 9.862166] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000
[ OK ] Mounted /run/media/B[ 9.875193] Mem abort info:
OOT-mmcblk1p1.
[ OK ] Started User Manager for UID 0.
[ 9.932277] ESR = 0x0000000096000044
[ 9.976305] EC = 0x25: DABT (current EL), IL = 32 bits
[ OK ] Started Session c1 [ 9.993424] SET = 0, FnV = 0
of User root[ 9.997406] EA = 0, S1PTW = 0
.
[ 10.003584] FSC = 0x04: level 0 translation fault
[ 10.017283] Data abort info:
[ 10.024599] ISV = 0, ISS = 0x00000044
[ 10.030656] CM = 0, WnR = 1
[ 10.035035] user pgtable: 4k pages, 48-bit VAs, pgdp=0000000085cef000
[ 10.042256] [0000000000000000] pgd=0000000000000000, p4d=0000000000000000
[ 10.049667] Internal error: Oops: 0000000096000044 [#1] PREEMPT SMP
[ 10.055934] Modules linked in: crct10dif_ce polyval_ce polyval_generic snd_soc_fsl_asoc_card snd_soc_imx_audmux snd_soc_imx_card layerscape_edac_mod snd_soc_wm8962 snd_soc_fsl_micfil ap1302(O+) rtc_pcf2131 flexcan snd_soc_fsl_sai snd_soc_fsl_utils snd_soc_fsl_xcvr can_dev imx8_media_dev(C) fuse
[ 10.081996] CPU: 0 PID: 217 Comm: (udev-worker) Tainted: G C O 6.1.55+g770c5fe2c1d1 #1
[ 10.091109] Hardware name: NXP i.MX93 11X11 EVK board (DT)
[ 10.096580] pstate: 20400009 (nzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 10.103529] pc : __memcpy+0x128/0x240
[ 10.107186] lr : i2c_put_dma_safe_msg_buf+0x58/0x60
[ 10.112057] sp : ffff80000abab5c0
[ 10.115358] x29: ffff80000abab5c0 x28: ffff000004555880 x27: ffff000004555e80
[ 10.122482] x26: 0000000000000000 x25: ffff000004555cd0 x24: 0000000000000002
[ 10.129607] x23: 00000000000000fa x22: 00000000fffee479 x21: 0000000000000000
[ 10.136730] x20: ffff80000abab758 x19: ffff000008556000 x18: 0000000000000000
[ 10.143854] x17: ffff80007602c000 x16: ffff800008000000 x15: 0000000000000000
[ 10.150978] x14: 0000000000000000 x13: 44c10e1a3748c516 x12: 020b024417b49031
[ 10.158102] x11: 0000000000000001 x10: 0000000000000a60 x9 : ffff80000abab470
[ 10.165226] x8 : ffff00007fb99000 x7 : 044c2caab91e0225 x6 : 7458460120ad233d
[ 10.172350] x5 : 0000000000002000 x4 : ffff000008558000 x3 : 0000000000000000
[ 10.179474] x2 : 0000000000002000 x1 : ffff000008556000 x0 : 0000000000000000
[ 10.186602] Call trace:
[ 10.189038] __memcpy+0x128/0x240
[ 10.192347] lpi2c_imx_xfer+0x6b8/0x9f4
[ 10.196178] __i2c_transfer+0x150/0x490
[ 10.200009] i2c_transfer+0x60/0x100
[ 10.203579] regmap_i2c_read+0x6c/0xb4
[ 10.207320] _regmap_raw_read+0xdc/0x160
[ 10.211240] regmap_raw_read+0x190/0x270
[ 10.215158] ap1302_probe+0xb78/0x1400 [ap1302]
[ 10.219688] i2c_device_probe+0x380/0x3d0
[ 10.223694] really_probe+0xbc/0x2dc
[ 10.227265] __driver_probe_device+0x78/0x114
[ 10.231616] driver_probe_device+0x3c/0x15c
[ 10.235793] __driver_attach+0x94/0x19c
[ 10.239624] bus_for_each_dev+0x78/0xd4
[ 10.243452] driver_attach+0x24/0x30
[ 10.247025] bus_add_driver+0x154/0x20c
[ 10.250853] driver_register+0x78/0x130
[ 10.254684] i2c_register_driver+0x48/0xd0
[ 10.258774] ap1302_i2c_driver_init+0x20/0x1000 [ap1302]
[ 10.264078] do_one_initcall+0x68/0x1ec
[ 10.267909] do_init_module+0x48/0x1d0
[ 10.271653] load_module+0x1774/0x1cd0
[ 10.275391] __do_sys_finit_module+0xac/0x104
[ 10.279742] __arm64_sys_finit_module+0x20/0x30
[ 10.284266] invoke_syscall+0x48/0x114
[ 10.288009] el0_svc_common.constprop.0+0xcc/0xec
[ 10.292707] do_el0_svc+0x2c/0xd0
[ 10.296015] el0_svc+0x2c/0x84
[ 10.299069] el0t_64_sync_handler+0xf4/0x120
[ 10.303330] el0t_64_sync+0x18c/0x190
[ 10.306985] Code: 927cec03 cb0e0021 8b0e0042 a9411c26 (a900340c)
[ 10.313067] ---[ end trace 0000000000000000 ]---

This issue seems to originate from the ap1302_probe function, which is called during the initialization of the ap1302 driver. The problem may be due to a NULL pointer being dereferenced within the kernel space.

We have checked the code, but couldn't identify the exact cause. Could you please assist us in debugging this issue?

[Zhiming_Liu]

The lpi2c3 bus is not working properly, you can see that rtc-pcf2131 also can't be probed. Is there any other core use it ? or check your hardware.

[TUANLAM95]

Thank you, I have resolved that issue. It was due to incorrect i2c configuration. However, I am now facing a new problem: After I write the firmware into the AP1302, I am not seeing the value 0xFFFF when reading data from the bootdata_state register. I have tried multiple times. Here is my log, including additional information about the write address and length each time.

root@imx93-11x11-lpddr4x-evk:~# dmesg | grep -E 'ap1302'
[ 7.735555] ap1302: loading out-of-tree module taints kernel.
[ 7.830846] ap1302_mipi 2-003d: AP1302 Driver: Driver Author TuanLam 02_24/06/03
[ 7.848385] ap1302_mipi 2-003d: vcc supply not found
[ 7.890130] ap1302_mipi 2-003d: Requesting firmware /imx/camera/ap1302_ar1335_single_fw.bin
[ 7.903827] ap1302_mipi 2-003d: Firmware header version : 1
[ 7.909807] ap1302_mipi 2-003d: Firmware description : Release 433 @ 1-12-2023 0:15:4 - AP1302-REV2-AR1335-REV2-IAS1MOD-AR1335CSSC080110 - No Clock - NO SIP
[ 7.939812] ap1302_mipi 2-003d: AP1302 revision 0.2.6 detected
[ 7.965640] ap1302_mipi 2-003d: AP1302 oscillator clock 40000000 hz (FP 0x00280000)
[ 7.978644] ap1302_mipi 2-003d: AP1302 MIPI frequency 140000000 hz (FP 0x008c0000)
[ 7.986912] ap1302_mipi 2-003d: ap1302_write_fw_window len start 83104d
[ 8.192013] ap1302_mipi 2-003d: ap1302_write_fw_window write_addr 0x8000
[ 8.205204] ap1302_mipi 2-003d: ap1302_write_fw_window write_size 8192KB
[ 8.403669] ap1302_mipi 2-003d: ap1302_write_fw_window write_addr 0x8000
[ 8.459685] ap1302_mipi 2-003d: ap1302_write_fw_window write_size 8192KB
[ 8.679342] ap1302_mipi 2-003d: ap1302_write_fw_window write_addr 0x8000
[ 8.727520] ap1302_mipi 2-003d: ap1302_write_fw_window write_size 8192KB
[ 8.985908] ap1302_mipi 2-003d: ap1302_write_fw_window write_addr 0x8000
[ 9.004873] ap1302_mipi 2-003d: ap1302_write_fw_window write_size 8192KB
[ 9.306429] ap1302_mipi 2-003d: ap1302_write_fw_window write_addr 0x8000
[ 9.319340] ap1302_mipi 2-003d: ap1302_write_fw_window write_size 8192KB
[ 9.639304] ap1302_mipi 2-003d: ap1302_write_fw_window write_addr 0x8000
[ 9.648633] ap1302_mipi 2-003d: ap1302_write_fw_window write_size 8192KB
[ 9.910659] ap1302_mipi 2-003d: ap1302_write_fw_window write_addr 0x8000
[ 9.933272] ap1302_mipi 2-003d: ap1302_write_fw_window write_size 8192KB
[ 10.148843] ap1302_mipi 2-003d: ap1302_write_fw_window write_addr 0x8000
[ 10.155585] ap1302_mipi 2-003d: ap1302_write_fw_window write_size 8192KB
[ 10.353236] ap1302_mipi 2-003d: ap1302_write_fw_window write_addr 0x8000
[ 10.359968] ap1302_mipi 2-003d: ap1302_write_fw_window write_size 8192KB
[ 10.557610] ap1302_mipi 2-003d: ap1302_write_fw_window write_addr 0x8000
[ 10.564335] ap1302_mipi 2-003d: ap1302_write_fw_window write_size 8192KB
[ 10.598682] ap1302_mipi 2-003d: ap1302_write_fw_window write_addr 0x8000
[ 10.605403] ap1302_mipi 2-003d: ap1302_write_fw_window write_size 1184KB
[ 15.682016] ap1302_mipi 2-003d: AP1302_BOOTDATA_STAGE not 0xFFFF : 000A (POLL -110)
[ 15.689688] ap1302_mipi 2-003d: ap1302_hw_init error_power
[ 15.696407] ap1302_mipi 2-003d: ap1302_hw_init error
[ 15.701417] ap1302_mipi 2-003d: Go to error cleanup
[ 15.708505] ap1302_mipi: probe of 2-003d failed with error -110

[TUANLAM95]

This is error log of AP1302: 

root@imx93-11x11-lpddr4x-evk:~# dmesg | grep -E 'ap1302'
[ 7.872581] ap1302: loading out-of-tree module taints kernel.
[ 7.904693] ap1302_mipi 2-003d: AP1302 Driver: Driver Author TuanLam 02_24/06/03
[ 7.905024] ap1302_mipi 2-003d: vcc supply not found
[ 7.906092] ap1302_mipi 2-003d: Requesting firmware /imx/camera/ap1302_ar1335_single_fw.bin
[ 7.915545] ap1302_mipi 2-003d: Firmware header version : 1
[ 7.955123] ap1302_mipi 2-003d: Firmware description : Release 433 @ 1-12-2023 0:15:4 - AP1302-REV2-AR1335-REV2-IAS1MOD-AR1335CSSC080110 - No Clock - NO SIP
[ 8.056284] ap1302_mipi 2-003d: AP1302 revision 0.2.6 detected
[ 8.185363] ap1302_mipi 2-003d: AP1302 oscillator clock 40000000 hz (FP 0x00280000)
[ 8.221003] ap1302_mipi 2-003d: AP1302 MIPI frequency 140000000 hz (FP 0x008c0000)
[ 8.230430] ap1302_mipi 2-003d: ap1302_write_fw_window write_addr 0x8000
[ 8.237601] ap1302_mipi 2-003d: ap1302_write_fw_window write_size 4094 Byte
[ 8.343322] ap1302_mipi 2-003d: ap1302_write_fw_window write_addr 0x8FFE
[ 8.355380] ap1302_mipi 2-003d: ap1302_write_fw_window write_size 4098 Byte
[ 8.499441] ap1302_mipi 2-003d: ap1302_write_fw_window write_addr 0x8000
[ 8.535018] ap1302_mipi 2-003d: ap1302_write_fw_window write_size 8192 Byte
[ 8.767351] ap1302_mipi 2-003d: ap1302_write_fw_window write_addr 0x8000
[ 8.816456] ap1302_mipi 2-003d: ap1302_write_fw_window write_size 8192 Byte
[ 9.053677] ap1302_mipi 2-003d: ap1302_write_fw_window write_addr 0x8000
[ 9.103327] ap1302_mipi 2-003d: ap1302_write_fw_window write_size 8192 Byte
[ 9.360006] ap1302_mipi 2-003d: ap1302_write_fw_window write_addr 0x8000
[ 9.371701] ap1302_mipi 2-003d: ap1302_write_fw_window write_size 8192 Byte
[ 9.680102] ap1302_mipi 2-003d: ap1302_write_fw_window write_addr 0x8000
[ 9.699784] ap1302_mipi 2-003d: ap1302_write_fw_window write_size 8192 Byte
[ 9.965519] ap1302_mipi 2-003d: ap1302_write_fw_window write_addr 0x8000
[ 9.973900] ap1302_mipi 2-003d: ap1302_write_fw_window write_size 8192 Byte
[ 10.182547] ap1302_mipi 2-003d: ap1302_write_fw_window write_addr 0x8000
[ 10.189371] ap1302_mipi 2-003d: ap1302_write_fw_window write_size 8192 Byte
[ 10.390068] ap1302_mipi 2-003d: ap1302_write_fw_window write_addr 0x8000
[ 10.396800] ap1302_mipi 2-003d: ap1302_write_fw_window write_size 8192 Byte
[ 10.597441] ap1302_mipi 2-003d: ap1302_write_fw_window write_addr 0x8000
[ 10.604161] ap1302_mipi 2-003d: ap1302_write_fw_window write_size 8192 Byte
[ 10.804789] ap1302_mipi 2-003d: ap1302_write_fw_window write_addr 0x8000
[ 10.811509] ap1302_mipi 2-003d: ap1302_write_fw_window write_size 1184 Byte
[ 10.895441] ap1302_mipi 2-003d: CRC mismatch: expected 0xfd87, got 0xcf01
[ 10.914506] ap1302_mipi 2-003d: log > 0040 1x
[ 10.918889] ap1302_mipi 2-003d: log > 2x
[ 10.922849] ap1302_mipi 2-003d: log > 3x
[ 10.926791] ap1302_mipi 2-003d: log > 4x
[ 10.930723] ap1302_mipi 2-003d: log > 5x
[ 10.934646] ap1302_mipi 2-003d: log > 6x
[ 10.938572] ap1302_mipi 2-003d: log > 7x
[ 10.942519] ap1302_mipi 2-003d: log > 8x
[ 10.946442] ap1302_mipi 2-003d: log > 9x
[ 10.950367] ap1302_mipi 2-003d: log > 10x
[ 10.954379] ap1302_mipi 2-003d: log > 11x
[ 10.958392] ap1302_mipi 2-003d: log > 12x
[ 10.962404] ap1302_mipi 2-003d: log > 13x
[ 10.966417] ap1302_mipi 2-003d: log > 14x
[ 10.970430] ap1302_mipi 2-003d: log > 15x
[ 10.974450] ap1302_mipi 2-003d: log > 16x
[ 10.978465] ap1302_mipi 2-003d: log > 17x
[ 10.982477] ap1302_mipi 2-003d: log > QMEM ERROR at address 0x0000d17a
[ 10.989001] ap1302_mipi 2-003d: log > GARFIELD_IRQ_SYS_QMEM_ERR_INTS = 0x00000080
[ 10.996569] ap1302_mipi 2-003d: log > SINF adr: 0x00400000
[ 11.002141] ap1302_mipi 2-003d: log > ERROR #015 @os/system.c:1230
[ 11.008353] ap1302_mipi 2-003d: log > Phase assigned: 0x0 done: 0x0 cnt: 0
[ 11.015233] ap1302_mipi 2-003d: log > Stopping...
[ 11.019938] ap1302_mipi 2-003d: log > 9 1x
[ 11.024033] ap1302_mipi 2-003d: log > 2x
[ 11.027959] ap1302_mipi 2-003d: log > 3x
[ 11.031889] ap1302_mipi 2-003d: log > 4x
[ 11.035811] ap1302_mipi 2-003d: log > 5x
[ 11.039736] ap1302_mipi 2-003d: log > 6x
[ 11.043663] ap1302_mipi 2-003d: log > 7x
[ 11.047589] ap1302_mipi 2-003d: log > 8x
[ 11.051515] ap1302_mipi 2-003d: log > 9x
[ 11.055440] ap1302_mipi 2-003d: log > 10x
[ 11.059453] ap1302_mipi 2-003d: log > 11x
[ 11.063466] ap1302_mipi 2-003d: log > 12x
[ 11.067478] ap1302_mipi 2-003d: log > 13x
[ 11.071490] ap1302_mipi 2-003d: log > 14x
[ 11.075503] ap1302_mipi 2-003d: log > 15x
[ 11.079516] ap1302_mipi 2-003d: log > 16x
[ 11.083527] ap1302_mipi 2-003d: log > 17x
[ 11.087534] ap1302_mipi 2-003d: log > NACK[0][1] 0x18 0x0000 W 0x0000 1x
[ 11.094235] ap1302_mipi 2-003d: log > 2x
[ 11.098160] ap1302_mipi 2-003d: log > 3x
[ 11.102084] ap1302_mipi 2-003d: log > 4x
[ 11.106009] ap1302_mipi 2-003d: log > 5x
[ 11.109936] ap1302_mipi 2-003d: log > 6x
[ 11.113862] ap1302_mipi 2-003d: log > 7x
[ 11.117788] ap1302_mipi 2-003d: log > 8x
[ 11.121716] ap1302_mipi 2-003d: log > 9x
[ 11.125652] ap1302_mipi 2-003d: log > 10x
[ 11.129667] ap1302_mipi 2-003d: log > 11x
[ 11.133686] ap1302_mipi 2-003d: log > 12x
[ 11.137787] ap1302_mipi 2-003d: log > 13x
[ 11.141884] ap1302_mipi 2-003d: log > 14x
[ 11.145901] ap1302_mipi 2-003d: log > 15x
[ 11.149918] ap1302_mipi 2-003d: log > 16x
[ 11.153933] ap1302_mipi 2-003d: log > 17x
[ 11.158042] ap1302_mipi 2-003d: log > NACK[0][2] 0x18 0x0001 W 0x0000 1x
[ 11.164781] ap1302_mipi 2-003d: log > 2x
[ 11.168714] ap1302_mipi 2-003d: log > 3x
[ 11.172642] ap1302_mipi 2-003d: log > 4x
[ 11.176566] ap1302_mipi 2-003d: log > 5x
[ 11.180491] ap1302_mipi 2-003d: log > 6x
[ 11.184418] ap1302_mipi 2-003d: log > 7x
[ 11.188344] ap1302_mipi 2-003d: log > 8x
[ 11.192270] ap1302_mipi 2-003d: log > 9x
[ 11.196196] ap1302_mipi 2-003d: log > 10x
[ 11.200250] ap1302_mipi 2-003d: log > 11x
[ 11.204275] ap1302_mipi 2-003d: log > 12x
[ 11.208290] ap1302_mipi 2-003d: log > 13x
[ 11.212304] ap1302_mipi 2-003d: log > 14x
[ 11.216312] ap1302_mipi 2-003d: log > 15x
[ 11.220324] ap1302_mipi 2-003d: log > 16x
[ 11.224336] ap1302_mipi 2-003d: log > 17x
[ 11.228348] ap1302_mipi 2-003d: log > NACK[0][3] 0x18 0x0002 W 0x
[ 11.234974] ap1302_mipi 2-003d: ERROR: 0x000f (file 0x00071975:1230)
[ 11.242344] ap1302_mipi 2-003d: SIPM_ERR [0] 0x0000 [1] 0x0000
[ 11.249552] ap1302_mipi 2-003d: WARNING [0] 0x0000 [1] 0x0000 [2] 0x000a [3] 0x0000
[ 11.257245] ap1302_mipi 2-003d: - WARN_SIPM_0_RTY
[ 11.261955] ap1302_mipi 2-003d: - WARN_SIPM_0_NO_ACK
[ 11.267466] ap1302_mipi 2-003d: Frame counters: ICP 0, HINF 0, BRAC 0
[ 11.274248] ap1302_mipi 2-003d: AF Pos: 0

[Zhiming_Liu]

Hi @TUANLAM95 

Are you adding your peripheral control program based on ethosu sdk project?

Best Regards

Zhiming

[TUANLAM95]

No, I am using MCUXpresso for VS Code, SDK_2.x_MCIMX93-EVK. I am using the sample project mcimx93evk_rgpio_led_output to edit peripheral control. I have tried running the project mcimx93evk_ethosu_apps_rpmsg, but it is not working.

[Zhiming_Liu]

Hi @TUANLAM95 

You may compare the difference of hardware initialization between mcimx93evk_rgpio_led_output and mcimx93evk_ethosu_apps_rpmsg, port the necessary code from mcimx93evk_rgpio_led_output to mcimx93evk_ethosu_apps_rpmsg.