Skip to main content
Associate III
May 16, 2025
Solved

GRU layer support on ST Edge AI

  • May 16, 2025
  • 1 reply
  • 564 views

 

Hello everyone,

I have a GRU-based model that I trained using PyTorch and then exported to ONNX. I'm trying to run it on various ST boards.

According to this documentation: ST Neural-ART Operator Support
it seems that the Neural-ART accelerator does not support the GRU layer. However, from what I understand, other ST Edge AI boards should support it—with some limitations described here: ONNX Supported Ops

That said, when I try to compile the model using the ST Edge AI Developer Cloud, I get the following error:

TOOL ERROR: operands could not be broadcast together with shapes (512,) (256,)

This is the same issue I previously encountered here: Community Thread - GRU/LSTM Model Issue

At this point, I'm not sure whether GRU layers are simply not supported at all, or if there's a way to make them work under specific conditions.

I'm attaching the ONNX model in case it helps.

Thanks in advance for any support or suggestions!

Best answer by Julian E.

Hello @Dresult,

 

This issue was fixed internally and the fix should be part of the next st edge ai core update (v2.2)

 

Have a good day,

Julian

1 reply

Julian E.
Technical Moderator
May 22, 2025

Hello @Dresult,

 

Sorry for all these issues. GRU and LSTM are still badly supported.

Our team is working on it but also on a lot of other subject.

I opened an internal ticket with your model. 

 

I will try to keep you informed but it may take a lot of time before being worked one.

 

Have a good day,

Julian

​In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
DresultAuthor
Associate III
May 22, 2025

Thanks Julian, I really appreciate that.

Don't worry, I asked mainly to understand if it was a problem of my model or not...

Julian E.
Julian E.Best answer
Technical Moderator
June 24, 2025

Hello @Dresult,

 

This issue was fixed internally and the fix should be part of the next st edge ai core update (v2.2)

 

Have a good day,

Julian

​In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.