Target HW

[wh1674]

Is the DORY framework only compatible with commercial MCUs like GAP-8 as the target hardware, or can it also be used with custom architectures based on other PULP platforms?

[FrancescoConti]

Hi @wh1674 thanks for your question. It can be adapted to run on other PULPs, and we used it for some of our silicon prototypes, but we are currently working on another framework that will supersede DORY with better flexibility for that use-case.

[wh1674]

Thank you.
Is it possible to modify the architecture within the PULP platform (e.g., Pulpissimo) to use the C code output from Dory in runtime simulation?"

[Doraemon-DYX]

Hi @wh1674 thanks for your question. It can be adapted to run on other PULPs, and we used it for some of our silicon prototypes, but we are currently working on another framework that will supersede DORY with better flexibility for that use-case.

@FrancescoConti HI, what‘s the framework that will supersede DORY? Is that already open source?

[FrancescoConti]

Hi @wh1674 thanks for your question. It can be adapted to run on other PULPs, and we used it for some of our silicon prototypes, but we are currently working on another framework that will supersede DORY with better flexibility for that use-case.

@FrancescoConti HI, what‘s the framework that will supersede DORY? Is that already open source?

Yes it is: https://github.com/pulp-platform/deeploy
In terms of support, we do not yet support all the end-to-end cases that can be realized with DORY, otoh it can already do many things DORY can not (e.g., deploy to accelerators).

[Doraemon-DYX]

@FrancescoConti So, DORY will be deprecated?

[FrancescoConti]

Yes -- in the sense of "not further developed"