Skip to main content
APerd.1
Associate II
April 11, 2023
Question

How to fix "INTERNAL ERROR: list index out of range" when uploading an onnx model to STM32Cube.AI

  • April 11, 2023
  • 7 replies
  • 3135 views

Hello!

I'm getting the error: INTERNAL ERROR: list index out of range when uploading an onnx model to STM32Cube.AI and run analysis. I have validated my model with other tools like netron.app and it is correct. I would appreciate if anyone could help to figure out what could be the problem? I attach my model below in case someone can help me. Thanks in advance. Regards!

    This topic has been closed for replies.

    7 replies

    APerd.1
    APerd.1Author
    Associate II
    April 11, 2023

    I forgot to mention that this model was generated in Matlab with exportONNXNetwork function, in case it may be of help.

    fauvarque.daniel
    ST Employee
    April 11, 2023

    The error is in the import of the LSTM layer, probably due to the way Matlab exports the LSTM layer.

    I forwarded the network to the development team.

    Regards

    Daniel

    APerd.1
    APerd.1Author
    Associate II
    April 12, 2023

    Thanks! I would appreciate any feedback on the matter, cause I need to use lstm layers for my project.

    Regards.

    Alejandro

    APerd.1
    APerd.1Author
    Associate II
    April 27, 2023

    Hi @fauvarque.daniel​. Hope you're fine.

    Any feedback from the development team on the error in the import of the LSTM layer? I would appreciate any solution proposal to the problem.

    Regards

    Alejandro

    fauvarque.daniel
    ST Employee
    April 27, 2023

    Issue has been reproduced and fix is ongoing, normally the fix will be part of the next 8.1 release planned in June

    Regards

    Daniel

    APerd.1
    APerd.1Author
    Associate II
    April 29, 2023

    Thanks for your reply.

    Regards

    Alejandro

    wg_it
    Associate II
    May 12, 2023

    I have met the same problem. Have you solved it? Thank you very much

    APerd.1
    APerd.1Author
    Associate II
    May 13, 2023

    Hello @武 钢​ 

    No, I could not solve the problem. I expect the problem to be fixed for the next 8.1 release planned in June. @fauvarque.daniel​ reported the problem and fix is ongoing.