vikasbalaga

@freddan80 and others, thanks for your quick response. > The runtime flow is slightly different. Ethos-U65 sits on an "ML island" (Cortex-M + Ethos-U subsystem, embedded) as part of a...

@freddan80 , I have modified the [arm_aot_compile.py](https://github.com/pytorch/executorch/commit/7e645a0bceb531e2202aa179940befdd945d6fe6) and I think I am able to generate ***.pte** model for **Ethos U65 backend**. The configuration details I picked based on my hardware...

[This](https://github.com/vikasbalaga/executorch_u65/tree/feat/arm_u65_support) points to the private branch I created by forking the repo. Thanks!

> I would suggest to start testing your model and executor_runner on u55 using the Corstone-300 target I have tried performing inference on Corstone-300 FVP by following the steps mentioned...

> The examples/arm/executor_runner-code and related CMake-scripts used to built it should be viewed as an example to get you started when building your own application... @AdrianLundell, I tried to build...

Hi, With that option, I can see the issue is fixed on simulator! But, I tried to do the same for the application that I have built by invoking the...

> This error suggests to me however that the network has not lowered probably since the add operator should be delegated to the Ethos-U rather than run on CPU, but...

I tried comparing **.map** file of my application with that of simulator and observed that in my app, the symbols from some of the libs `libportable_kernels.a, libportable_ops_lib.a,...` are not being...

Hi again, I have managed to overcome "`kernel not found`" issue by linking the libs with `--whole-archive` and also following selective build mentioned by @zingo. However, I have observed that...

@AdrianLundell , you are right! The unwanted symbols are coming from `libportable_kernels.a` as it is linked with `--whole-archive`. So, it looks like the `--whole-archive` is required only for `libarm_portable_ops_lib.a` and...