hci_lpuart - v290 - 91x - RAM overflowed

Hello,

hci_lpuart builds fine in VS v290 with thingy91/nrf52840.

If trying with thingy91x/nrf5340/cpuapp/ns,
build is going ok until the very end when RAM overflowed message stops the build,

region `RAM' overflowed by 267184 bytes
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.

This case mentions Case ID's of ongoing hci_lpuart issues, maybe its 91x:
339543
338886
(not sure how to search for Case ID, in search box or by URL string)
The docs for hci_lpuart mentions thingy91, maybe ok for 91x too.

thank-you,

  • Hello, 

    The docs for hci_lpuart mentions thingy91, maybe ok for 91x too.

    Yes, it should work for the Thingy:91x as well.

    If trying with thingy91x/nrf5340/cpuapp/ns,
    build is going ok until the very end when RAM overflowed message stops the build,

    I also see this issue, but building for thingy91x/nrf5340/cpuapp does not give this issue. You should be able to use this build for the nRF5340 on the Thingy:91x. Did you try this? I did not test on my side unfortunately.

    This case mentions Case ID's of ongoing hci_lpuart issues, maybe its 91x:

    The cases that are mentioned in this ticket are private tickets from the same customer. 

    Kind regards,
    Øyvind

  • I did try thingy91x/nrf5340/cpuapp, but this would have led to my next case.
    Was looking at keeping these two issues separate.
    Once the non ns hci_lpuart sysbuild is compiled and in the process of being flashed from VS,
    nrfutil not found error comes up,

    -- west flash: using runner nrfutil
    -- runners.nrfutil: mass erase requested
    -- runners.nrfutil: reset after flashing requested
    FATAL ERROR: required program nrfutil not found; install it or add its location to PATH

    Tried flashing 91x on VS Win11 and Ubuntu 24.04.2 LTS and same nrfutil result.
    If you then try to flash nrf9160-dk or thingy:91 on VS, no issues with nrfutil and flashing is normal.
    Tried also with blinky, wifi_scan, lte_ble_gateway sysbuild for 91x and all end up with nrfutil not found.

    thank-you,

  • Simon said:
    Tried flashing 91x on VS Win11 and Ubuntu 24.04.2 LTS and same nrfutil result.

    Have you installed nrfutil on your computernrfjprog is officially deprecated and is being replaced by nRF Util.

    Please download and retry. 

    Kind regards,
    Øyvind

  • Now when trying to flash non ns thingy91x/nrf5340/cpuapp sysbuild on VS v290 and switch set to nrf53,

    -- west flash: using runner nrfutil
    -- runners.nrfutil: mass erase requested
    -- runners.nrfutil: reset after flashing requested
    -- runners.nrfutil: Flashing file: /home/simon/ncs_apps/hci_lpuart-91x-v290/build_3a/merged_CPUNET.hex
    -- runners.nrfutil: Erasing flash and UICR
    -- runners.nrfutil: Programming image
    Error: One or more batch tasks failed:
     * 960023012: [Probe] Device error: Memory access error at 0x01008800. Probably a memory protection issue. Probe access is Secure (Generic)
    FATAL ERROR: command exited with status 1: nrfutil --json device x-execute-batch --batch-path /home/simon/ncs_apps/hci_lpuart-91x-v290/build_3a/generated_nrfutil_batch.json --serial-number 960023012
     *  The terminal process terminated with exit code: 1.
     *  Terminal will be reused by tasks, press any key to close it
    .
    Gave a try using v3.0.0-preview1 thingy91x/nrf5340/cpuapp/ns, and same ram overflowed.
    /home/simon/ncs/toolchains/aedb4c0245/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 `bss' will not fit in region `RAM'
    /home/simon/ncs/toolchains/aedb4c0245/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd: region `RAM' overflowed by 267168 bytes
    collect2: error: ld returned 1 exit status

    thank-you,

  • Hello,

    I see from the board files, particularly the file:

    NCS v2.9.0\nrf\boards\nordic\thingy91x\board.cmake

    Line 8-12 should be:

    elseif(CONFIG_BOARD_THINGY91X_NRF5340_CPUAPP OR CONFIG_BOARD_THINGY91X_NRF5340_CPUAPP_NS)
      board_runner_args(nrfjprog)
      board_runner_args(nrfutil "--nrf-family=NRF53")
      board_runner_args(jlink "--device=nrf5340_xxaa_app" "--speed=4000")
    elseif(CONFIG_BOARD_THINGY91X_NRF5340_CPUNET)

    Note that there are two corrections on line 8. 

    Try this, and see if it helps.

    Best regards,

    Edvin

Related