2025-01-22 5:29 AM - edited 2025-01-22 5:38 AM
Hi,
It seems the X-CUBE-AZRTOS-F7 1.1.0 is based on ThreadX 6.1.7. But after select 'Enable BASEPRI support', it missed several files which exist in the official 6.1.7 release, they are:
tx_thread_interrupt_disable.S and _tx_thread_interrupt_restore.S.
Thanks.
'
Solved! Go to Solution.
2025-01-28 2:38 AM - edited 2025-01-29 8:06 AM
Hello @diverger ,
Thank you for reporting this issue:
Missing declaration of tx_thread_interrupt_restore.s and tx_thread_interrupt_disable.s in STMicroelectronics
X-CUBE-AZRTOS-F7.1.1.0_Configs.xml for the CM7 GNU.
I am escalating an internal ticket to the concerned team (ticket number:201630).
Thanks.
Mahmoud
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2025-01-22 6:06 AM
Hello @diverger ,
First let me thank you for posting.
I have created a project with STM32F722ICK6 and I have installed and enabled X-CUBE-AZRTOS-F7.
tx_thread_interrupt_disable.S and _tx_thread_interrupt_restore.S are well generated.
Thanks.
Mahmoud
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2025-01-24 6:26 PM - edited 2025-01-24 6:26 PM
Hi,
It's weird that your MCU is a F7 based on cortex-m7, but it shows 'cortex-m33' in the picture. In my case, I use STM32F769.
Please check it.
Thanks.
2025-01-27 7:37 AM
Hello @diverger ,
Further to your comment, I am using STM32CubeMX 6.13 and ThreadX version: 6.1.10 not 6.1.7.
Thanks.
Mahmoud
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2025-01-28 2:38 AM - edited 2025-01-29 8:06 AM
Hello @diverger ,
Thank you for reporting this issue:
Missing declaration of tx_thread_interrupt_restore.s and tx_thread_interrupt_disable.s in STMicroelectronics
X-CUBE-AZRTOS-F7.1.1.0_Configs.xml for the CM7 GNU.
I am escalating an internal ticket to the concerned team (ticket number:201630).
Thanks.
Mahmoud
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.