cmsis5/rtx2: ST: execution never leaves SystemInit

[bulislaw]

Description

• Type: Bug
• Priority: Blocker
• Branch: https://github.com/ARMmbed/mbed-os/tree/feature_cmsis5

---

Bug

Target
ST platfoms (tested with NUCLEO F401RE and F411RE)

Toolchain:
GCC_ARM ARM

We're trying to finalize CMSIS5/RTX2 (https://github.com/ARMmbed/mbed-os/tree/feature_cmsis5) update in next month or two, but we're having issues with ST platforms. When executing tests (eg mbed test -n tests-mbedmicro-rtos-mbed-basic -m NUCLEO_F401RE -vv) I'm getting a timeout. I had a bit of troubles trying to debug the issue, but as far as i can tell the execution never leaves SystemInit, it's stuck in TIM5_IRQHandler in an infinite loop. While stepping through the code it seems the interrupt was happening while trying to access SysTick counter (HAL_GetTick), but I'm not 100% sure.

@0xc0170 Could you ping some ST people, maybe they could have a look into it?
CC: @sg- @c1728p9

[0xc0170]

cc @bcostm @adustm @LMESTM @jeromecoutant

[bcostm]

Hi,
This test is ok on the master branch. I don't know if you can rebase your branch on top of master ?

mbedgt: test suite report:
+-----------------------+---------------+---------------------------------+--------+--------------------+-------------+
| target                | platform_name | test suite                      | result | elapsed_time (sec) | copy_method |
+-----------------------+---------------+---------------------------------+--------+--------------------+-------------+
| NUCLEO_F401RE-GCC_ARM | NUCLEO_F401RE | tests-mbedmicro-rtos-mbed-basic | OK     | 22.23              | shell       |
+-----------------------+---------------+---------------------------------+--------+--------------------+-------------+
mbedgt: test suite results: 1 OK
mbedgt: test case report:
+-----------------------+---------------+---------------------------------+---------------------------------+--------+--------+--------+--------------------+
| target                | platform_name | test suite                      | test case                       | passed | failed | result | elapsed_time (sec) |
+-----------------------+---------------+---------------------------------+---------------------------------+--------+--------+--------+--------------------+
| NUCLEO_F401RE-GCC_ARM | NUCLEO_F401RE | tests-mbedmicro-rtos-mbed-basic | tests-mbedmicro-rtos-mbed-basic | 1      | 0      | OK     | 22.23              |
+-----------------------+---------------+---------------------------------+---------------------------------+--------+--------+--------+--------------------+
mbedgt: test case results: 1 OK
mbedgt: completed in 26.92 sec

mbed-os version
65956d1 Merge pull request #3677 from c1728p9/armcc_linker_flags

[bulislaw]

I know it is ok on master and the feature branch is almost up to date with master anyway. But it seems to be broken (for all ST platforms I've tried) with the update to cmsis5/rtx2 and my debugging led me into bowels of the platform. It's the change we'll be landing soon on master and I'd like to have ST boards passing all the tests. Could you guys help us with debugging it please.

[bulislaw]

ping

[bcostm]

Hi,

I have installed the latest uVision V5.23 toolchain and generated a project using "mbed export" in order to start debugging.

But I have these 2 errors:

assembling irq_cm4f.s...
rtos\rtx2\TARGET_CORTEX_M\TARGET_RTOS_M4_M7\TOOLCHAIN_ARM\irq_cm4f.s(81): error: A1854E: Unknown opcode 'VSTMDBEQ', maybe wrong target CPU?
rtos\rtx2\TARGET_CORTEX_M\TARGET_RTOS_M4_M7\TOOLCHAIN_ARM\irq_cm4f.s(97): error: A1854E: Unknown opcode 'VLDMIAEQ', maybe wrong target CPU?

It's strange because when I compile with mbed test -vv -m NUCLEO_F401RE -t ARM --compile I don't have any error. Same with GCC_ARM build, no error.

Do you use a uvision project for your debug ?

[bulislaw]

I don't generally use windows, but yes when I was trying to debug this issue I was using uVision 5.20 (ARMC 5.06). It seems that the flag is correctly set __FPU_PRESENT as this platform has FPU. I'm not in the office and don't have access to windows machine right now to recheck that, can uVision debugger use binary built externally by mbed compile --profile debug -m NUCLEO_F401RE -t ARM?

[bcostm]

I don't know if this is feasible or not ? Anyway I have commented the 2 lines just to see if the rest was ok and I have now 4247 errors during linking...
But seems to be the same error:

*** Using Compiler 'V5.06 update 4 (build 422)', folder: 'C:\Keil_v5\ARM\ARMCC\Bin'
Build target 'mbed-os'
compiling main_blink_led.cpp...
linking...
.\BUILD\mbed-os.axf: Error: L6366E: analogin.o attributes are not compatible with the provided attributes .
Object analogin.o contains Build Attributes that are incompatible with the provided attributes.
    Tag_FP_arch = VFPv4 instructions were permitted, but only citing registers D0-D15 (=6)
    Tag_ABI_HardFP_use = This code should execute on the single-precision variant derived from Tag_FP_arch (=1)
    Tag_FP_HP_extension = Use of the optional half-precision extension to VFPv3/Advanced SIMDv1 was permitted (=1)
.\BUILD\mbed-os.axf: Error: L6367E: analogin.o(.rev16_text) attributes are not compatible with the provided attributes .
Object analogin.o contains Build Attributes that are incompatible with the provided attributes.
    Tag_FP_arch = VFPv4 instructions were permitted, but only citing registers D0-D15 (=6)
    Tag_ABI_HardFP_use = This code should execute on the single-precision variant derived from Tag_FP_arch (=1)
    Tag_FP_HP_extension = Use of the optional half-precision extension to VFPv3/Advanced SIMDv1 was permitted (=1)
.\BUILD\mbed-os.axf: Error: L6367E: analogin.o(.revsh_text) attributes are not compatible with the provided attributes .
Object analogin.o contains Build Attributes that are incompatible with the provided attributes.
    Tag_FP_arch = VFPv4 instructions were permitted, but only citing registers D0-D15 (=6)
    Tag_ABI_HardFP_use = This code should execute on the single-precision variant derived from Tag_FP_arch (=1)
    Tag_FP_HP_extension = Use of the optional half-precision extension to VFPv3/Advanced SIMDv1 was permitted (=1)
.\BUILD\mbed-os.axf: Error: L6367E: analogin.o(.rrx_text) attributes are not compatible with the provided attributes .
Object analogin.o contains Build Attributes that are incompatible with the provided attributes.
    Tag_FP_arch = VFPv4 instructions were permitted, but only citing registers D0-D15 (=6)
    Tag_ABI_HardFP_use = This code should execute on the single-precision variant derived from Tag_FP_arch (=1)
    Tag_FP_HP_extension = Use of the optional half-precision extension to VFPv3/Advanced SIMDv1 was permitted (=1)

...

[bulislaw]

Do you have similar issues on master?

[bcostm]

Yes same error on master.

[bulislaw]

OK, it explains a lot I did a rebase on monday. You mind creating a bug report for master?

[bulislaw]

@bcostm I manage to reproduce the issue with current master and only CMSIS changed, I prepared branch for F401 https://github.com/bulislaw/mbed-os/tree/st401_update_cmsis_no_rtx
Tested with tests-mbedmicro-rtos-mbed-threads (which hangs)