• State Not Answered
  • Replies 29 replies
  • Subscribers 66 subscribers
  • Views 1294 views
  • Users 0 members are here
Attachments (5) Download All
Nordic Case Info
  • Case ID: 324344
Options

Flash overflow?

BenA

Hello,

I'm trying to merge together a couple of sample projects to make a prototype (in particular, the LTE-BLE gateway, and AWS-IoT samples) - to run on the nRF 9160DK

When I try and compile, I get the following errors:

/opt/nordic/ncs/toolchains/20d68df7e5/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: zephyr/zephyr_pre0.elf section `text' will not fit in region `FLASH'

/opt/nordic/ncs/toolchains/20d68df7e5/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: region `FLASH' overflowed by 119504 bytes

How can I resolve this please? Or is it just too big to try and fit onto the Dev Kit?

Regards,

Ben

Parents
  • 0

    It looks that you and me both were only flashing only nRf91 core and not the other core.

    AS mentioned here in programming this sample, you need to change the switch and program HCI LPUART on nRF52 core to get a HCI response for the command. Right now it is timing out and creating a controlled hardfault exception.

    We both overlooked the opcode in the error message and did not see that this hardfault was a controlled exception. The BLE team have taken the feedback to improve the logs to give little more informative message so that our first instinct is not to panic looking at the hardfault and focus more on the opcode that caused it.

    Try flashing HCI LPUART code to nRF52 chip and you will see this problem goes away.

Reply
  • 0

    It looks that you and me both were only flashing only nRf91 core and not the other core.

    AS mentioned here in programming this sample, you need to change the switch and program HCI LPUART on nRF52 core to get a HCI response for the command. Right now it is timing out and creating a controlled hardfault exception.

    We both overlooked the opcode in the error message and did not see that this hardfault was a controlled exception. The BLE team have taken the feedback to improve the logs to give little more informative message so that our first instinct is not to panic looking at the hardfault and focus more on the opcode that caused it.

    Try flashing HCI LPUART code to nRF52 chip and you will see this problem goes away.

Children
Related