Tips When Importing Custom Models into MCX eIQ Neutron NPU SDK Examples

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

Tips When Importing Custom Models into MCX eIQ Neutron NPU SDK Examples

Tips When Importing Custom Models into MCX eIQ Neutron NPU SDK Examples

When deploying a custom built model to replace the default models in MCUXpresso SDK examples, there are several modifications that need to be made as described in the eIQ Neutron NPU hands-on labs.

Here are some common issues and error messages that you might encounter when using a new custom model with the SDK examples and how to solve them. If there is an issue not covered here, then please make a new thread to discuss that issue. 

 


“Didn't find op for builtin opcode ‘<operator_name>’”

  • Need to add that operator to MODEL_GetOpsResolver function found in source\model\model_name_ops_npu.cpp
  • A full list of operators used by a model that can be copy-and-pasted into that file is automatically generated by Neutron Converter Tool with the dump-header-file option.
  • Make sure to also increase the size of the static array s_microOpResolver to match the number of operators

 

“resolver size is too small”

  • Need to increase the size of the static array s_microOpResolver in MODEL_GetOpsResolver function found in source\model\model_name_ops_npu.cpp to match the number of operators

 

 

“Failed to resize buffer”

  • The scratch memory buffer is too small for the model and needs to be increased.
  • The size of the memory buffer is set with the kTensorArenaSize variable found in the model data header file

 

“Internal Neutron NPU driver error 281b in model prepare!” or “Incompatible Neutron NPU microcode and driver versions!”

  • Ensure the version of the eIQ Neutron Converter Tool used to convert the model is the correct one that is compatible with the NPU libraries used by the SDK project. 
  • eIQ Toolkit v1.10.0 should be used with MCXUpresso SDK for MCX N 2.14.0. The Neutron Converter Tool version is 1.2.0+0X84d37e1f

 

 

Camera colors are incorrect on FRDM-MCXN947 board

  • Modify solder jumpers SJ16, SJ26, and SJ27 on the back of board to move them to the left (dashed line side) to connect camera signals properly. 
          anthony_huereca_0-1709071420874.png
  • This modification will disable Ethernet functionality on the board due to a signal conflict with EZH D0 and ENET_TXCLK. If your project needs both camera and Ethernet functionality, then only move SJ16 and SJ26 to the left (dashed line side) and then connect a wire from P1_4 (J9 pin to the left side of R58. Then in the pin_mux.c file in the project, instead of using PORT1_PCR4 for EZH_Camera_D0, use PORT3_PCR0. 

         anthony_huereca_1-1709071421059.png

 

 

         

 

Labels (2)
100% helpful (1/1)
Version history
Last update:
‎07-24-2024 03:47 AM
Updated by: