Skip to content

Commit 9db47e1

Browse files
Eugeniy Paltsevnashif
authored andcommitted
test: error_hook: check for exact SoCs instead of entire ARC EM family
The quirky behavior when accessing of 0x0 address is related to exact ARC SoCs/boards and not to entire ARC EM CPUs family. So check for exact SoCs configs (CONFIG_SOC_ARC_IOT and CONFIG_SOC_NSIM) instead of checking against CONFIG_CPU_ARCEM. Signed-off-by: Eugeniy Paltsev <[email protected]>
1 parent 8bcc85b commit 9db47e1

File tree

1 file changed

+1
-1
lines changed
  • tests/ztest/error_hook/src

1 file changed

+1
-1
lines changed

tests/ztest/error_hook/src/main.c

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ static void trigger_fault_illegal_instruction(void)
5151

5252
static void trigger_fault_access(void)
5353
{
54-
#if defined(CONFIG_CPU_ARCEM) || defined(CONFIG_CPU_CORTEX_M)
54+
#if defined(CONFIG_SOC_ARC_IOT) || defined(CONFIG_SOC_NSIM) || defined(CONFIG_CPU_CORTEX_M)
5555
/* For iotdk and ARC/nSIM, nSIM simulates full address space of memory,
5656
* so all accesses outside of CCMs are valid and access to 0x0 address
5757
* doesn't generate any exception.So we access it 0XFFFFFFFF instead to

0 commit comments

Comments
 (0)