STM32G070 compile error

[caoddx]

Description of defect

STM32G070xx does not seem to have TIM2 :

[Error] us_ticker_data.h@26,22: 'TIM2' undeclared

And has USART3_4_IRQn without USART3_4_LPUART1_IRQn :

[Error] serial_device.c@132,17: 'USART3_4_LPUART1_IRQn' undeclared (first use in this function)
[Error] serial_device.c@329,21: 'USART3_4_LPUART1_IRQn' undeclared (first use in this function)

Target(s) affected by this defect ?

Custom target inherits from MCU_STM32G070xx

Toolchain(s) (name and version) displaying this defect ?

GCC_ARM

What version of Mbed-os are you using (tag or sha) ?

mbed-os-6.4.0

What version(s) of tools are you using. List all that apply (E.g. mbed-cli)

mbed-cli

How is this defect reproduced ?

None

[ciarmcom]

@caoddx thank you for raising this issue.Please take a look at the following comments:

We cannot automatically identify a release based on the version of Mbed OS that you have provided.
Please provide either a single valid sha of the form #abcde12 or #3b8265d70af32261311a06e423ca33434d8d80de
or a single valid release tag of the form mbed-os-x.y.z .
E.g. 'mbed-os-6.4.0' has not been matched as a valid tag or sha.How can we reproduce your issue?

NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'.This indicates to us that at least all the fields have been considered.
Please update the issue header with the missing information, the issue will not be mirroredto our internal defect tracking system or investigated until this has been fully resolved.

[0xc0170]

We cannot automatically identify a release based on the version of Mbed OS that you have provided.
Please provide either a single valid sha of the form #abcde12 or #3b8265d70af32261311a06e423ca33434d8d80de
or a single valid release tag of the form mbed-os-x.y.z .
E.g. 'mbed-os-6.4.0' has not been matched as a valid tag or sha.How can we reproduce your issue?

@ARMmbed/mbed-os-maintainers this looks valid release to me, or why our script failed?

[ciarmcom]

Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers.
Internal Jira reference: https://jira.arm.com/browse/IOTOSM-2726

[0xc0170]

cc @ARMmbed/team-st-mcd

[jeromecoutant]

Hi
I confirm the issue.
Patch is coming soon