Mbed-os: Greentea FPGA testing fails with DISCO_H747I

[umbynos]

Description of defect

FPGA ci test shield fails most of the tests with DISCO_H747I

I'm trying to understand how FPGA testing works. I've cloned mbed-os repo, installed mbed-cli and run the generic tests with mbed-cli test -t GCC_ARM --greentea -m auto and everything is OK.
I then added FPGA_CI_TEST_SHIELD in targets.json as stated there. But after connecting the FPGA CI shield and running mbed-cli test -t GCC_ARM --greentea -n tests-mbed_hal_fpga_ci_test_shield-spi -v some tests are failing.
I've attached the execution output
test_execution_fpga_spi.log
The only test working is pwm one. Every other FPGA test shows similar problems.

Target(s) affected by this defect ?

As far as I know DISCO_H747I

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

GCC_ARM 9.2.1

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

475621c

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

mbed-cli 1.10.2

How is this defect reproduced ?

mbed-cli test -t GCC_ARM --greentea -n tests-mbed_hal_fpga_ci_test_shield-spi -v with FPGA CI shield attached

[ciarmcom]

@umbynos 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. '(#475621ce36bf)' has not been matched as a valid tag or sha.
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]

@ARMmbed/team-st-mcd Please review

[ciarmcom]

@umbynos it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@umbynos it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@umbynos it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[0xc0170]

I updated the SHA.

@ARMmbed/team-st-mcd Please review. Are you able to reproduce these reported failures?

[jeromecoutant]

@ARMmbed/team-st-mcd Please review. Are you able to reproduce these reported failures?

yes.... :-(

[jeromecoutant]

Hi
Could you try #13073 ?
Regards,

[umbynos]

Hello! I've tried your PR with the fixes but something it's still broken: tests are working fine except for
mbed_timing_fpga_ci_test_shield-watchdog.log, mbed_hal_fpga_ci_test_shield-gpio.log, mbed_hal_fpga_ci_test_shield-gpio_irq.log.

[umbynos]

Actually the problem it's not solved for me.

[jeromecoutant]

Yes, it's good to have merge #13073, but @adbridge could you keep this issue opened
Thx

[adbridge]

@jeromecoutant it seems that was a Github automatic response because I merged #13073 and they were linked ! I will reopen it.

[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/MBOTRIAGE-2701

[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-2212