xtensa hifi_mini SOC does not build

[zephyrbot]

Reported by Andrew Boie:

In file included from /projects/zephyr4/arch/xtensa/include/xtensa_rtos.h:199,
                 from /projects/zephyr4/arch/xtensa/include/xtensa_api.h:10,
                 from /projects/zephyr4/include/arch/xtensa/xtensa_irq.h:9,
                 from /projects/zephyr4/include/arch/xtensa/arch.h:26,
                 from /projects/zephyr4/include/arch/cpu.h:23,
                 from /projects/zephyr4/include/kernel.h:3559,
                 from /projects/zephyr4/kernel/include/kernel_structs.h:10,
                 from /projects/zephyr4/arch/xtensa/core/offsets/offsets.c:30:
/projects/zephyr4/arch/xtensa/include/xtensa_timer.h:43:2: error: #error "This Xtensa configuration is unsupported, it has no timers."
/projects/zephyr4/arch/xtensa/include/xtensa_timer.h:73:2: error: #error "There is no suitable timer in this Xtensa configuration."
/projects/zephyr4/./Kbuild:97: recipe for target 'arch/xtensa/core/offsets/offsets.o' failed

(Imported from Jira ZEP-2023)

[zephyrbot]

by Andrew Boie:

We need to either implement a working timer, or remove this un-buildable SOC from the tree.

[zephyrbot]

by Mazen NEIFER:

I can't reproduce this issue. Here hifi_mini builds correctly.
Please indicate if this is specific to a given test or all of them?
Can you please check your core configuration? Did you disable timer before building the core?

[zephyrbot]

by Mazen NEIFER:

The reason for this to not work is that hifi_mini core does not ship with an internal timer in its default configuration.
One need to add manually a timer in order for that core to work properly.
I've provided to Steve a suitable hifi_mini configuration and he is going to provide a default package with suitable cores.
So let's wait on this ticket.

[zephyrbot]

by Andrew Boie:

Drop priority to low, this is not a major loss of functionality, we just have a SOC configuration that can't currently run Zephyr and we are waiting for an alternative configuration from Cadence.

[galak]

Is this still an issue?