bus fault: difference between 2 the same processors

[mh3]

Hello NXP,

I have received my second batch of hardware with the k64f processor on it. However i notice a difference between the first batch and the second batch. The first one runs the software and the second one immediately gets a BUS FAULT. You would say a hardware error but a sample project works like a charm. (dhcp4_client) What could cause the difference between the first batch and the second batch?

<err> os: ***** BUS FAULT *****
<err> os: Precise data bus error
<err> os: BFAR Address: 0x4003d014
<err> os: r0/a1: 0x4003d000 r1/a2: 0x2000f61c r2/a3: 0x4003d000
<err> os: r3/a4: 0x68000201 r12/ip: 0x00000777 r14/lr: 0x00014e9d
<err> os: xpsr: 0x61000000
<err> os: s[ 0]: 0x00000000 s[ 1]: 0x00025064 s[ 2]: 0x20000b78 s[ 3]: 0x00023285
<err> os: s[ 4]: 0x00000401 s[ 5]: 0x00000000 s[ 6]: 0x00000000 s[ 7]: 0x00000000
<err> os: s[ 8]: 0x00024efc s[ 9]: 0x00025064 s[10]: 0x00024efc s[11]: 0x0002423f
<err> os: s[12]: 0x00024ed4 s[13]: 0x00015733 s[14]: 0x2000acdd s[15]: 0x00025364
<err> os: fpscr: 0x00025364
<err> os: Faulting instruction address (r15/pc): 0x00023bc4
<err> os: >>> ZEPHYR FATAL ERROR 25: Unknown error on CPU 0
<err> os: Current thread: 0x20004d78 (unknown)
<err> os: Halting system

and the project config:

# Basic networking

CONFIG_NETWORKING=y

CONFIG_NET_IPV4=y

CONFIG_NET_IPV6=n

CONFIG_NET_TCP=y

CONFIG_NET_ARP=y

CONFIG_NET_UDP=y

CONFIG_DNS_RESOLVER=y

# MQTT

CONFIG_MQTT_LIB_TLS=n

CONFIG_MQTT_LIB=y

CONFIG_NET_SOCKETS=y

CONFIG_POSIX_API=y

CONFIG_JSON_LIBRARY=y

CONFIG_NEWLIB_LIBC=y

CONFIG_NEWLIB_LIBC_FLOAT_PRINTF=y

CONFIG_FPU=y

#memory

CONFIG_MAIN_STACK_SIZE=8192

# Network buffers

CONFIG_NET_BUF_RX_COUNT=64

CONFIG_NET_BUF_TX_COUNT=64

CONFIG_NET_PKT_RX_COUNT=64

CONFIG_NET_PKT_TX_COUNT=64

# DHCP specific configurations

CONFIG_NET_DHCPV4=y

CONFIG_NET_DHCPV4_OPTION_CALLBACKS=y

# Network management

CONFIG_NET_MGMT=y

CONFIG_NET_MGMT_EVENT=y

# Logging

CONFIG_LOG=y

CONFIG_NET_LOG=y

# Random number generation for MQTT message IDs

CONFIG_ENTROPY_GENERATOR=y

CONFIG_TEST_RANDOM_GENERATOR=y

#timers

CONFIG_COUNTER=y

#miscelanious

CONFIG_GPIO=y

CONFIG_SPI=n

CONFIG_SPI_ASYNC=n

CONFIG_ADC=y

CONFIG_JSON_LIBRARY=y

[Celeste_Liu]

Hello @mh3 ,

Thanks for your post.

To help you figure out the issue more accurately, could you please provide more information? You mentioned that you received two batches of K64 processors. Would it be convenient for you to tell me the receipt times of these two batches? Also, could you provide me with the mask information printed on the chips of these two batches? You can take photos like this.

Apart from the dhcp4_client encountering a bus fault on the second batch processors, have you tried other SDK demos? Do they also occur bus faults? In the second batch processors, does only a certain chip have a bus fault, or do all of them have this problem?

BRs,

Celeste