HERO: Compiling OpenMP examples with only=pulp
#1
Hello,

I am trying to compile the mm-small example in https://github.com/pulp-platform/hero/tr...s/mm-small. I would like to build it only for the PULP accelerator.
For that I run make only=pulp. I get the following error:

herov2/pulp/sdk/pkg/sdk/dev/install/include/archi/pulp.h:31:10: fatal error: 'archi/chips/PULP_CHIP_STR/pulp.h' file not found

Please could you help me identify the source of the problem.

Thank you!
Reply
#2
Reviving this question

It seems like some mm-small, mm-large, and dma-perf are not buildable without the archi/chips/PULP_CHIP_STR/pulp.h file. After going through the build process for Hero, the only directory under archip/chips/ is bigpulp. Is there a way to build the PULP_CHIP_STR directory, or use a different pulp.h that's called from include/archi/pulp.h?
Reply
#3
This is a configuration issue rather than a missing build step.
As I know, in PULP Platform, PULP_CHIP_STR is a macro that resolves to the selected chip name at compile time. It’s not something that generates a directory automatically.
Reply
#4
Ah, got it—so I just need to make sure PULP_CHIP_STR is set correctly in the build configuration to match an existing chip folder, rather than expecting it to create a new directory automatically.
Reply
#5
(08-30-2023, 09:08 AM)darbyshaw Wrote: Hello,
I am trying to compile the mm-small example in https://github.com/pulp-platform/hero/tr...s/mm-smallslope. I would like to build it only for the PULP accelerator.
For that I run make only=pulp. I get the following error:
herov2/pulp/sdk/pkg/sdk/dev/install/include/archi/pulp.h:31:10: fatal error: 'archi/chips/PULP_CHIP_STR/pulp.h' file not found
Please could you help me identify the source of the problem.
Thank you!
Do you have the correct chip configuration set for the PULP accelerator in your project settings, as it may not be correctly defined or initialized?
Reply
#6
(03-17-2026, 09:08 AM)jerkyfault Wrote: Ah, got it—so I just need to make sure PULP_CHIP_STR is set correctly in the build configuration to match an existing chip folder, rather than expecting it to create a new directory automatically.

Could you explain it in more detail? I don't quite understand the issue.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)