tests: mimxrt1160_evk/mimxrt1166/cm7:samples/drivers/mbox_data/sample: drivers: mbox_data test Timeout

[hakehuang]

Describe the bug
mbox_data test is Timeout on v4.0.0-1877-g90ff9c0883b2 on mimxrt1160_evk/mimxrt1166/cm7
testcase path is samples/drivers/mbox_data/

see logs for details

To Reproduce
1.

scripts/twister --device-testing --device-serial /dev/ttyACM0 -p mimxrt1160_evk/mimxrt1166/cm7  -T samples/drivers/mbox_data --sub-test mimxrt1160_evk/mimxrt1166/cm7:samples/drivers/mbox_data/sample.drivers.mbox_data.real_hw

or

# cd samples/drivers/mbox_data/
# west build -b mimxrt1160_evk/mimxrt1166/cm7
# west flash

git bisect found below commit introduce this failure 2e8868c

commit 71fd4d9c98c7fe0845b70693e8daea46c6646b80
Author: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
Date:   Thu Nov 28 09:16:38 2024 +0100

    cmake: clear llvm bintool gapfill property

    The llvm-objcopy doesn't support a gap-fill argument, therefore clear
    the property to remove the error:
    > llvm-objcopy: error: unknown argument '--gap-fill'

    Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>


2e8868c16e5ecfab8e823096892e02dac037c222 is the first bad commit
commit 2e8868c16e5ecfab8e823096892e02dac037c222
Author: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>
Date:   Thu Nov 28 09:07:00 2024 +0100

    cmake: deprecate BUILD_NO_GAP_FILL and introduce type specific gap fill

    Deprecate BUILD_NO_GAP_FILL as it gives a false impression that gap
    filling can be disabled in binary files.
    Binary files are always gap filled due to the fact they contain no
    address information. Only option for binary files is to control the gap
    fill pattern. When no gap fill is enabled in binary files, then a
    default pattern is used by the tool, which usually is 0x00.

    Generally the pattern 0x00 leads to unnecessary flash writes, as a
    flash generally contains 0xFF after an erase.
    Therefore provide a gap fill pattern Kconfig setting instead, with
    default value of 0xFF.

    For hex-files, intel hex and s19, then gap filling is generally not
    needed but in order to still support cases where gap filling is required
    then this commit introduces BUILD_OUTPUT_HEX_GAP_FILL and
    BUILD_OUTPUT_S19_GAP_FILL. Both settings are disabled per default.

    Signed-off-by: Torsten Rasmussen <Torsten.Rasmussen@nordicsemi.no>

2. See error

Expected behavior
test pass

Impact

Logs and console output

*** Booting Zephyr OS build v4.0.0-1877-g90ff9c0883b2 ***
mbox_data Client demo started
Client send (on channel 3) value: 0
*** Booting Zephyr OS build v4.0.0-1877-g90ff9c0883b2 ***
mbox_data Client demo started
Client send (on channel 3) value: 0

    

Environment (please complete the following information):

• OS: (e.g. Linux )
• Toolchain (e.g Zephyr SDK)
• Commit SHA or Version used: v4.0.0-1877-g90ff9c0883b2

[hakehuang]

this case is ok on mimxrt1170_evk

[github-actions]

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

[github-actions]

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.