Hardfault in memset during startup of Zigbee stack

RE: Hardfault in memset during startup of Zigbee stack

Marte Myrvold — Thu, 18 Mar 2021 14:18:08 GMT

Hi,

Good to hear that it was solved. Do not hesitate to ask if you are experiencing any more issues down the road.

Best regards,

Marte

RE: Hardfault in memset during startup of Zigbee stack

patbra — Thu, 18 Mar 2021 08:05:55 GMT

This issue is no more relevant for us. We manage to solve it in another way. We are now using our own platform to build this example, and then it works fine.

Regards,

Patrik

RE: Hardfault in memset during startup of Zigbee stack

Marte Myrvold — Thu, 11 Mar 2021 07:17:22 GMT

Hi,

Our Zigbee team has seen some suspicious behavior when copying the content of the nrf_common.ld to the examples linker script. Could you please try reverting these changes and instead add the path to the nrf_common.ld script to the linker flags? It should be something like this, just align the path: "LDFLAGS += -L$(SDK_ROOT)/modules/nrfx/mdk"

Best regards,

Marte

RE: Hardfault in memset during startup of Zigbee stack

patbra — Wed, 10 Mar 2021 13:48:10 GMT

Yes this is how it is. The libraries (including ZBOSS) comes after the object files in the linker command.

/Patrik

RE: Hardfault in memset during startup of Zigbee stack

Marte Myrvold — Mon, 08 Mar 2021 12:15:05 GMT

Hi Patrik,

I got a response from them now. You should place the ZBOSS library after the object files in the linker command, so that when the linker looks for symbols, it doesn't take weak ones from the ZBOSS library.

Best regards,

Marte

RE: Hardfault in memset during startup of Zigbee stack

Marte Myrvold — Fri, 05 Mar 2021 14:17:12 GMT

Hi Patrik,

I have asked the Zigbee team for a clarification on this.

Best regards,

Marte

RE: Hardfault in memset during startup of Zigbee stack

patbra — Fri, 05 Mar 2021 10:13:56 GMT

Is this really correct? The ZBOSS library is not in the end of the linker command, but if I try to make it the other way, it doesn't link. And your Makefile looks like this:

# Libraries common to all targets
LIB_FILES += \
  $(SDK_ROOT)/external/zboss/lib/gcc/libzboss.ed.a \
  $(SDK_ROOT)/external/zboss/lib/gcc/nrf52840/nrf_radio_driver.a \
  
...  

# Add standard libraries at the very end of the linker input, after all objects
# that may need symbols provided by these libraries.
LIB_FILES += -lc -lnosys -lm -lstdc++

Regards,

Patrik

RE: Hardfault in memset during startup of Zigbee stack

Marte Myrvold — Fri, 05 Mar 2021 06:43:00 GMT

Hi Patrik,

Could you please check the linker command? The ZBOSS library must be placed at the end of the command.

Best regards,

Marte

RE: Hardfault in memset during startup of Zigbee stack

Marte Myrvold — Tue, 02 Mar 2021 06:23:54 GMT

Hi Patrik,

Thank you, I have forwarded this to the Zigbee team.

Best regards,

Marte

RE: Hardfault in memset during startup of Zigbee stack

patbra — Mon, 01 Mar 2021 19:50:05 GMT

We are using the this toolchain: https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads/9-2020-q2-update.

The linker script is "zigbee_multi_sensor_freertos_gcc_nrf52.ld". One note about the linker script, is that I was not able to include the nrf_common.ld file. Then I get the following:

c:/mbs/work/rf-network/mbstoolchains/gcc-arm-none-eabi-9-2020-q2/bin/../lib/gcc/arm-none-eabi/9.3.1/../../../../arm-none-eabi/bin/ld.exe: cannot open linker script file nrf_common.ld: No such file or directory
collect2.exe: error: ld returned 1 exit status
make: *** [/cygdrive/c/mbs/work/rf-network/products/multi_sensor_freertos2/abs-binary.mk:22: _output/products-multi_sensor_freertos2/NRF52_GCC-none-none-mbs_nrf_52840_v10/products-multi_sensor_freertos2.elf] Error 1

Instead I copied the contents of the file where the include was.

I have tried to experiment with the compiler and linker options, but unmodified, this is what we use in our platform:

CFLAGS:

-mthumb \
-mcpu=cortex-m4 \
-ffunction-sections \
-fdata-sections \
-mfloat-abi=hard -mfpu=fpv4-sp-d16 \
-ggdb3 \
-std=gnu11 \
-O0

LDFLAGS:

-mthumb \
-mcpu=cortex-m4 \
-mfloat-abi=hard -mfpu=fpv4-sp-d16 \
-lc -lm \
--specs=nano.specs \
-Wl,--gc-sections \
-ggdb3

/Patrik

RE: Hardfault in memset during startup of Zigbee stack

Marte Myrvold — Mon, 01 Mar 2021 06:28:53 GMT

Hi Patrik,

The Zigbee team is still trying to figure this out. Could you please share which linker you're using, and whether you're using other compiler or linker options than what is already present in the example in the SDK?

Best regards,

Marte

RE: Hardfault in memset during startup of Zigbee stack

Marte Myrvold — Fri, 26 Feb 2021 13:02:25 GMT

Hi Patrik,

Thank you, I have forwarded this information to our Zigbee team. As for the second question, I believe they meant without multiprotocol, and possibly without FreeRTOS as well. If you tried the light bulb example without making any changes to it, then that would be without FreeRTOS, so knowing that you got the same issue there is very helpful.

Best regards,

Marte

RE: Hardfault in memset during startup of Zigbee stack

patbra — Fri, 26 Feb 2021 12:49:47 GMT

I tried example "examples/zigbee/light_control/light_bulb" and I get the same issue here.
What do you mean with "Zigbee-only"? I try to run the example "multi_sensor_freertos" and that example doesn't use multi-protocol if that is what you mean?
Yes I use gcc-arm-none-eabi-9-2020-q2
The example use role ZB_ED_ROLE
The example use "#include "zb_mem_config_med.h"

I use the example as is from the SDK. The difference is that:

1. We use our own build system to compile and link

2. We use our version of FreeRTOS. This should be an unmodified FreeRTOS-Kernel 10.4.2 version

This is probably some stupid mistake on my side. I just can't figure out what. Maybe im missing some compile or link file. Or maybe some define in the Makefile that I have missed.

Regards,

Patrik

RE: Hardfault in memset during startup of Zigbee stack

Marte Myrvold — Thu, 25 Feb 2021 11:20:28 GMT

Hi Patrik,

Our Zigbee team have tried to reproduce the issue, but with no luck so far. They do have some questions that might help them solving it:

Do you experience this issue with other examples in our SDK?
Is this issue present in Zigbee-only configuration?
What toochain version are you using to compile this example? Is it gcc-arm-none-eabi-9-2020-q2?
What Zigbee role does the device have? (ZED/ZR)?
What memory config is used in your application? (zb_mem_config_min.h/med/max)?

Best regards,

Marte

RE: Hardfault in memset during startup of Zigbee stack

Marte Myrvold — Wed, 24 Feb 2021 13:58:02 GMT

Hi Patrik,

Thank you for the information. I will ask our Zigbee team internally if they have seen this issue before or might know what causes it. I will come back to you as soon as I hear back from them.

Best regards,

Marte

RE: Hardfault in memset during startup of Zigbee stack

patbra — Wed, 24 Feb 2021 13:50:56 GMT

I am not using memset(). It seems like it is used from the Zigbee stack in function zb_init_configurable_mem() according to the call stack I provided.

/Patrik

RE: Hardfault in memset during startup of Zigbee stack

Marte Myrvold — Wed, 24 Feb 2021 13:43:24 GMT

Hi Patrik,

Could you please share what you're using memset() for, and possibly a code snippet of where you're using it, just to see what you're doing? This would make it easier to try and figure out what it is that is failing.

Best regards,

Marte